Synchronous Remote Snapshot Replication Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for remotely replicating snapshots in data storage networks require significant manual effort and resource consumption, leading to performance degradation, especially with high write activity and frequent snapshot creation.
Innovation Solution
A method that suspends new write requests, records outstanding requests, activates snapshots, and resumes processing while concurrently replicating write operations, allowing for independent and concurrent application of outstanding write requests to create a remote replica of the snapshot, thereby reducing manual intervention and resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual methods are used for remotely replicating snapshots, then replication can be performed, but significant manual effort and resource consumption are required, leading to performance degradation
Solution Approach 1:
The system automatically performs snapshot replication without manual intervention. The storage system autonomously identifies snapshots, determines their replication status, and initiates replication processes, eliminating the need for manual operations while maintaining system performance through optimized resource management.
Solution Approach 2:
The system determines replication status and prepares replication processes in advance before actual data transfer. By pre-assessing which snapshots need replication and organizing replication tasks beforehand, the system reduces peak resource consumption and avoids performance degradation during active replication operations.
2Reliability
If frequent snapshots are created with high write activity, then data protection is improved, but resource consumption increases and performance degradation occurs
Solution Approach 1:
The system performs replication selectively based on determined replication status rather than replicating all snapshots uniformly. By applying replication only where necessary and using optimized replication processes for different snapshot types, resource consumption is reduced while maintaining comprehensive data protection.
Solution Approach 2:
The system dynamically adjusts replication parameters and resource allocation based on system conditions, snapshot characteristics, and replication status. This allows frequent snapshot creation for data protection while optimizing resource usage to prevent performance degradation under varying workloads.
3Productivity
If snapshot replication is performed concurrently with write operations, then efficiency is improved, but complexity of coordination increases
Solution Approach 1:
The system divides snapshot replication into distinct phases and processes, separating replication determination from execution. By segmenting the replication workflow and assigning different processes to specific tasks, the system enables concurrent operations while managing coordination complexity through structured process separation.
Data Source
AI summary
Snapshots from a first LSU (R1) on a first storage system (A1) may be replicated to a second replica LSU (R2) on a second storage system (A2), for example, concurrently to remotely replicating (e.g., synchronously) write operations for R1 to R2. A process, P, on A1 executing the replication of the snapshots from R1 to R2 may be a separate process than the one or more processes on A1 executing remote replication of write operations for R1 to R2. During a consistency window on A1, outstanding write operations for R1 at the time the consistency window opened may be logged, and a pair of snapshots, SS11 and SS12 may be activated on R1 and R2, respectively. After the consistency window has closed, the SS12 snapshot metadata and snapshot data may be updated based on the outstanding write operations.