Storage Resynchronization Compliance Data Preservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Resynchronization operations in disaster recovery scenarios often delete compliance data stored in destination storage volumes, violating compliance policies, as they modify the volumes to mirror the source storage volume which does not contain the new compliance data.
Innovation Solution
Implementing techniques such as cloning storage volumes, copying compliance data to source storage volumes, or moving compliance data to local volumes before resynchronization to preserve compliance data during the reestablishment of disaster recovery relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a resynchronization operation is performed to reestablish the disaster recovery relationship between storage volumes, then the disaster recovery relationship is restored and data consistency is achieved, but compliance data stored in the destination volume is deleted, violating compliance policies
Solution Approach 1:
The system performs preliminary identification of compliance data in the destination storage volume before the resynchronization operation begins. By detecting WORM-locked files and their locations in advance, the system can preserve these files during resynchronization by creating exclusions or snapshots, allowing the disaster recovery relationship to be restored without losing compliance data.
Solution Approach 2:
The patent introduces an intermediary compliance data detection and preservation mechanism that acts as a mediator between the resynchronization process and the compliance data. This intermediary layer identifies compliance data, prevents its deletion during resynchronization, and ensures both the disaster recovery relationship restoration and compliance data preservation are achieved simultaneously.
2Stability of the object's composition
If the destination storage volume is modified to mirror the source storage volume during resynchronization, then data consistency between volumes is achieved, but new compliance data created during the broken disaster recovery relationship is lost
Solution Approach 1:
Before the resynchronization operation modifies the destination volume to mirror the source volume, the system performs preliminary detection of compliance data that exists in the destination but not in the source. This preliminary identification allows the system to preserve these newly created compliance data files during the mirroring process, maintaining both data consistency for non-compliance files and preservation of compliance data.
Solution Approach 2:
The system extracts compliance data from the general data set in the destination storage volume by identifying files with WORM locks or compliance markers. This extraction creates a separate protection category for compliance data, allowing the resynchronization operation to modify non-compliance data for consistency while leaving extracted compliance data untouched.
3Loss of information
If the resynchronization operation is blocked to prevent compliance data deletion, then compliance policies are maintained, but the disaster recovery relationship cannot be reestablished
Solution Approach 1:
Instead of blocking the resynchronization operation, the system performs preliminary detection and preservation of compliance data before resynchronization begins. This preliminary action allows the operation to proceed without blocking, restoring the disaster recovery relationship while simultaneously protecting compliance data through pre-established preservation mechanisms such as snapshots or exclusion lists.
Solution Approach 2:
The patent introduces an intermediary compliance preservation mechanism that mediates between the resynchronization operation and compliance data. This intermediary allows the resynchronization to proceed and reestablish the disaster recovery relationship while simultaneously protecting compliance data through detection and preservation actions, eliminating the need to block the operation.
Data Source
AI summary
One or more techniques and/or computing devices are provided for implementing resynchronization operations. For example, a disaster recovery relationship may be established between a source storage volume, hosted by a source storage node, and a destination storage volume hosted by a destination storage node, such that data is replicated from the source storage volume to the destination storage volume for disaster recovery purposes. If the disaster recovery relationship breaks, then new compliance data, locked down into a write once read many state, may be created at the destination storage volume. A resynchronization operation may be performed to reestablish the disaster recovery relationship, while preserving the new compliance data so that a compliance policy is not violated. For example, cloned storage volumes, copying compliance data to source storage volumes before resynchronization, and/or moving compliance data to local volumes may be used to implement resynchronization operations while preserving compliance data.