Writable Backup Clone for Storage Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current storage systems typically provide only read-only backup copies, which are inadequate for environments needing writable backup copies, such as those requiring data consistency and recovery in server environments like Windows-based systems using volume shadow services (VSS).
Innovation Solution
The method involves setting a recovery indicator for a storage space, replicating it to create a read-only copy, and using a clone of the logical object for recovery, allowing writes to the clone, and then generating a second read-only copy to capture changes, ensuring data consistency and enabling auto-recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a read-only backup copy is created, then data consistency and integrity are maintained, but the ability to perform recovery operations and maintain consistency with the original storage space is lost
Solution Approach 1:
The backup copy is segmented into two distinct parts: a read-only base copy for data consistency and integrity, and a writable clone layer for recovery operations. This segmentation allows each part to serve its specific function independently while working together as a unified backup system.
Solution Approach 2:
A clone is introduced as an intermediary between the read-only backup copy and the original storage space. The clone can be written to for recovery operations, and changes are subsequently applied back to the original space, enabling the backup to serve both as a consistent snapshot and as a writable recovery target.
2Adaptability or versatility
If a writable backup copy is created, then recovery operations can be performed, but data consistency and integrity may be compromised
Solution Approach 1:
The backup structure is segmented into a read-only base copy that preserves data consistency and a writable clone layer that enables recovery operations. The read-only layer ensures integrity while the writable layer provides recoverability.
Solution Approach 2:
The read-only backup copy is created first as a preliminary action to establish data consistency and integrity. Only after this foundation is established does the system allow creation of the writable clone layer for recovery operations, ensuring consistency is maintained throughout the process.
3Adaptability or versatility
If a clone is created for recovery operations, then writable access is enabled, but additional storage space and system complexity are required
Solution Approach 1:
The writable clone is nested within or associated with the read-only backup copy structure. The clone operates within the context of the existing backup infrastructure, utilizing the same storage devices and management mechanisms, thereby minimizing additional complexity while enabling writable capability.
Data Source
AI summary
Method and system for performing recovery for a replicated copy of a storage space presented as a logical object is provided. An attribute associated with the logical object for enabling the recovery is set and when the storage space is replicated the attribute is stored as metadata for the replicated copy of the storage space. Based on the attribute, a clone of the logical object is presented as a writable option to write to the first replicated copy. After the write operation where information is written to the clone, a second replicated copy with the clone information is created. The clone is deleted after the second copy is generated.