Cascaded FlashCopy Restore with Cleaning Data Write
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cascaded FlashCopy implementations in storage area networks face limitations in managing multiple backup processes, particularly in scalable restore operations and maintaining recovery points, due to dependencies between data targets and the need for cleaning operations, which can lead to unnecessary storage allocation and reduced ability to manage snapshots and clones effectively.
Innovation Solution
A method and system for handling multiple backup processes by detecting storage volumes in cascades, performing restore operations, and executing cleaning data writes from the restoration source volume to the next volume, allowing for immediate restoration without waiting for ongoing copy operations to complete, while separating clones and snapshots into different cascades to reduce cleaning operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If FlashCopy is used to create point-in-time copies for backup, then data redundancy and reliability are improved, but the complexity of managing multiple backup processes and dependencies between data targets increases
Solution Approach 1:
The patent segments backup processes into distinct types (clone and snapshot) with different dependency characteristics. Clone operations create independent copies, while snapshot operations create dependent copies. This segmentation allows the system to manage different backup scenarios separately, reducing the complexity of handling mixed backup processes in a cascaded environment.
Solution Approach 2:
The patent introduces a reverse FlashCopy operation that allows restoring data from target volumes back to source volumes. This inversion capability enables flexible recovery operations where the traditional source-target relationship can be reversed, providing additional flexibility in managing backup processes and resolving dependency issues.
2Ease of operation
If cleaning operations are performed to remove dependencies between target volumes, then restore operations can proceed, but storage space is wasted due to unnecessary allocation
Solution Approach 1:
The patent performs preliminary identification and classification of backup process types before executing cleaning operations. By pre-determining whether a volume is part of a clone or snapshot cascade, the system can prepare appropriate recovery strategies in advance, avoiding unnecessary cleaning operations and preserving storage space while still enabling restore operations when needed.
Solution Approach 2:
The patent uses copy-on-write technology as the foundation for creating point-in-time copies. This copying mechanism allows data to be copied only when changes occur, rather than requiring complete data migration during backup. The copy-on-write approach reduces the impact of cleaning operations and minimizes storage space requirements while maintaining the ability to perform restore operations.
3Quantity of substance
If cascaded FlashCopy implementations are used to create multiple backup levels, then recovery points are retained, but the ability to manage snapshots and clones effectively is reduced
Solution Approach 1:
The patent segments the backup hierarchy into distinct clone and snapshot cascades, each with its own management rules. Clone cascades maintain complete independent copies, while snapshot cascades maintain dependent copies with explicit dependency chains. This segmentation enables effective management of multiple backup levels by applying appropriate management strategies to each cascade type separately.
Solution Approach 2:
The patent implements feedback mechanisms that continuously monitor the state of backup volumes and their dependencies. By tracking which volumes are part of clone versus snapshot cascades and monitoring dependency relationships, the system can dynamically adjust management operations to maintain effectiveness in cascaded environments, enabling proper handling of both snapshots and clones simultaneously.
Data Source
AI summary
In one aspect of the present description, handling multiple backup processes comprises detecting that a defined storage volume is present in a first cascade of storage volumes; detecting that the defined storage volume is present in a second cascade of storage volumes; receiving a data write for a last storage volume in the first cascade of storage volumes; and performing a cleaning data write on the defined storage volume in the second cascade of storage volumes, wherein the cleaning data write corresponds to the received data write. Other aspects may be utilized, depending upon the particular application.