Storage Replication Session Preservation for Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems face inefficiencies in failover and failback processes, particularly in replicating production host data across multiple sites, as they require copying entire data sets, leading to high costs and resource utilization inefficiencies.
Innovation Solution
The method involves preserving replication by updating a non-current version of a storage object on a second storage node to match the current version on a first storage node, allowing replication to resume without transferring the entire current version, thereby reducing the need for costly data transfers and enhancing resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a new asynchronous replication session is created from Site B to Site C after failover, then replication can resume, but the entire production host data must be copied from Site B to Site C first, increasing data transfer costs and time
Solution Approach 1:
The system preserves the asynchronous replication session from Site A to Site C in a hibernated state during failover, so that when Site B becomes the new production site, replication can resume by simply activating the preserved session and syncing changes since failover, rather than performing a complete data copy
Solution Approach 2:
Instead of copying the entire production host data set from Site B to Site C, the system only copies the changes (deltas) that occurred since the failover event, significantly reducing data transfer volume while maintaining replication integrity
2Reliability
If the entire current version of the storage object is transferred from the first storage node to the second storage node, then replication can be established, but resource utilization decreases and operational costs increase
Solution Approach 1:
The replication process is segmented into two phases: (1) preserving the replication session and storage object state, and (2) syncing only the changes since termination. This segmentation avoids transferring the entire data set and only moves the necessary incremental changes
Solution Approach 2:
The system changes the replication approach from full-data-transfer to incremental-change-synchronization, fundamentally altering the parameter of data transfer volume from 'entire storage object' to 'changes since termination'
Data Source
AI summary
A technique preserves replication to a storage node. The technique involves, from a first storage node, sending a replication query to a second storage node. The technique further involves, in response to the replication query sent to the second storage node, receiving replication session data from the second storage node. The replication session data describes replication which has terminated from a third storage node to the second storage node for a particular storage object. The technique further involves, based on the replication session data, establishing replication from the first storage node to the second storage node for the particular storage object to preserve use of the particular storage object.