Continuous Data Protection Clone Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face challenges such as system shutdown during backups, limited recovery points, and lengthy data recovery processes, which hinder continuous data protection and minimize downtime during disasters.
Innovation Solution
The method involves creating and maintaining clones in continuous data protection systems using a five-state journaling process, allowing for the replication of data volumes with journaling capabilities to enable rollback to any point in time, and managing clones across multiple storage arrays to enhance data accessibility and recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional tape backup drives are used for data protection, then data can be stored periodically, but the system requires shutdown during backup and recovery takes a long time
Solution Approach 1:
The patent creates a clone (copy) of the production volume that can be accessed independently. The clone is initialized from the production volume and can be mounted and accessed without affecting the production system, eliminating the need for system shutdown during backup operations.
Solution Approach 2:
The clone is pre-initialized from the production volume before any recovery operation is needed. This preliminary copying action allows the recovery process to start immediately by mounting the existing clone, rather than performing a lengthy backup operation at the time of recovery.
2Reliability
If conventional tape backup drives are used for data protection, then data can be stored periodically, but recovery is limited to specific time points and takes a long time
Solution Approach 1:
The clone serves as a pre-prepared copy of the production volume at a specific point in time. When recovery is needed, the clone can be mounted immediately and accessed without waiting for lengthy restore operations, significantly reducing recovery time.
Solution Approach 2:
The clone is pre-initialized from the production volume, capturing the data state at initialization time. This preliminary action stores a ready-to-use copy that can be immediately mounted for recovery, eliminating the need for time-consuming restore operations.
3Reliability
If continuous data protection with journaling is implemented, then recovery to any point in time is enabled, but system complexity increases
Solution Approach 1:
The system is divided into distinct components: the production volume, the clone, and the journal. Each component has a specific function, and they operate semi-independently. The journal records changes separately, the clone stores the base state, and the production volume continues normal operations, simplifying the overall system management.
Solution Approach 2:
The journal acts as an intermediary between the production volume and the clone. It records all changes made to the production volume, allowing the system to replay or undo changes to achieve recovery to any point in time, without directly modifying the clone or production volume structure.
4Adaptability or versatility
If multiple clones are maintained across storage arrays, then data accessibility is enhanced, but storage resource management becomes more complex
Solution Approach 1:
The clone management system provides multiple functions: the clone can be used for recovery, for testing, for development, or as a backup production system. This multi-functionality enhances data accessibility and versatility while the system manages the clone uniformly regardless of its intended use.
Solution Approach 2:
The system dynamically manages clone states, allowing clones to be created, mounted, dismounted, and deleted as needed. The clone can be initialized from the production volume, mounted for access, and later deleted when no longer needed, providing flexible resource management that adapts to changing requirements.
Data Source
AI summary
In traditional storage arrays, the number of clones permitted inside the storage array may be limited by the amount of available storage. Further, clones stored on the array may require significant storage resources. Thus, the number of clone stored by the storage array may also be limited by the storage system memory and not just by the disk space. Accordingly, example embodiments of the present invention allow for creating and maintaining a plurality (e.g., an unlimited number) of thin asynchronous clones in storage, even if replica storage is capable of storing only a limited number of snapshots. Further, example embodiments of the present invention allow clones to be freely attached and detached from the replication environment for various purposes.