Disaster Recovery Storage Takeover Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional disaster recovery systems face challenges in efficiently replicating data from a primary to a secondary site after a prolonged failure, leading to potential data loss and system shutdowns due to synchronization issues and inability to handle changes during DR testing.
Innovation Solution
A mechanism for disaster recovery production takeover is implemented, allowing the DR system to transfer ownership of storage devices and synchronize data, enabling seamless replication and continuation of production without shutting down the DR system, even during replication processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a synchronization operation is performed to reconcile changes after primary system revival, then data consistency is improved, but system shutdown and loss of productivity occur during the synchronization process
Solution Approach 1:
The patent implements a takeover operation that performs preliminary actions before full synchronization is complete. The DR system can assume production status and begin serving requests while the synchronization process continues in the background, allowing the system to transition to a new state without requiring a complete shutdown for synchronization.
Solution Approach 2:
The system dynamically adjusts its operational state during the takeover process. The DR system transitions from a passive backup state to an active production state while synchronization operations continue, allowing the system to adapt its functionality based on the current phase of the disaster recovery process rather than requiring static shutdown states.
2Reliability
If the DR system operates in test mode to validate DR plan execution, then DR plan reliability is improved, but replication of primary site changes to secondary site is blocked
Solution Approach 1:
The patent separates the test mode operation from the replication process. The DR system can enter a test mode that validates DR plan execution independently, while replication operations continue separately. This extraction allows testing functionality to be validated without blocking the data replication stream from primary to secondary sites.
3Ease of manufacture
If conventional replication systems are used to return production to original site, then data replication is simplified, but shutdown of DR system is required for multiple source systems
Solution Approach 1:
The takeover operation performs preliminary actions to prepare the DR system for production status before completing the full transition. This allows the DR system to begin serving multiple source systems while the replication process continues, eliminating the need to shut down the DR system for each source system transition.
Data Source
AI summary
Various embodiments for disaster recovery (DR) production takeover in a computing environment by a processor device are provided. If, for a designated storage system operable in the computing environment, a takeover operation may be executed, and a DR storage system has validly replaced the designated storage system using a replacement process, a withdrawal of a DR mode of operation is performed, and ownership of at least one storage device operable in the computing environment is transferred to the DR storage system. The replacement process authorizes the DR storage system to transfer the ownership while withdrawn from the DR mode of operation.