Snapshot Replication Skipping for RPO Maintenance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional disaster recovery solutions face challenges in maintaining an acceptable recovery point objective (RPO) due to latency issues in synchronous replication and potential data loss in asynchronous replication, particularly when the secondary storage device experiences lag caused by high I/O load, network link speed reductions, or failures.
Innovation Solution
The solution involves skipping one or more snapshots during the snapshot replication process based on time-related parameters or delta data-related parameters to maintain an established recovery point objective, using a time-based module and a delta data-based module to determine which snapshots to replicate and which to skip, thereby mitigating the effects of replication lag.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous replication is used to ensure data consistency, then data reliability is improved, but system latency increases
Solution Approach 1:
The patent segments the replication process into synchronous and asynchronous phases. Critical data is replicated synchronously to ensure consistency, while non-critical data uses asynchronous replication to reduce latency. This segmentation allows the system to achieve both data reliability and reduced time loss by applying different replication strategies to different data portions.
Solution Approach 2:
The patent applies local quality by differentiating replication approaches based on data characteristics. Hot data and mission-critical data receive synchronous replication for maximum reliability, while cold data and less critical information use asynchronous replication to minimize latency. This localized application of replication quality optimizes the balance between reliability and time performance.
2Speed
If asynchronous replication is used to reduce latency, then replication speed is improved, but data loss risk increases
Solution Approach 1:
The patent implements preliminary action by capturing snapshots of data at predetermined intervals before potential data loss can occur. These snapshots serve as safety checkpoints that prevent complete data loss even when asynchronous replication experiences delays. The system proactively creates recovery points in advance, ensuring that data integrity is maintained despite the asynchronous nature of replication.
Solution Approach 2:
The patent employs feedback mechanisms to monitor the replication status and data consistency between primary and secondary storage systems. When discrepancies or lag are detected, the system adjusts replication frequency and triggers additional snapshots to maintain data integrity. This feedback loop ensures that asynchronous replication maintains acceptable data loss prevention levels while preserving speed benefits.
3Reliability
If replication rate is increased to meet RPO, then recovery point objective is improved, but system resource consumption increases
Solution Approach 1:
The patent implements dynamic replication rate adjustment based on system conditions, data change frequency, and RPO requirements. The replication rate is not fixed but adapts in real-time, increasing during periods of low system load and decreasing when resources are constrained. This dynamic approach allows the system to meet RPO compliance while optimizing resource consumption by avoiding unnecessary replication during stable periods.
Solution Approach 2:
The patent changes key parameters such as replication interval, snapshot frequency, and data selection criteria based on system state and RPO requirements. When resources are abundant, the system increases replication frequency and reduces interval between snapshots. When resources are constrained, it adjusts parameters to maintain minimal RPO compliance with reduced resource usage. This parameter flexibility resolves the contradiction between RPO achievement and resource consumption.
4Reliability
If all snapshots are replicated to ensure complete data recovery, then data completeness is improved, but replication time increases
Solution Approach 1:
The patent applies partial action by selectively replicating only the most critical snapshots and data portions rather than all snapshots. The system identifies and prioritizes snapshots based on data importance, change frequency, and RPO requirements, replicating only those necessary to meet recovery objectives. This partial replication approach maintains data completeness for critical information while significantly reducing overall replication time and resource expenditure.
Solution Approach 2:
The patent extracts and separates critical data from non-critical data, replicating only the essential portions needed to meet RPO requirements. By extracting the most important snapshots and data elements for replication while leaving less critical data for optional or delayed replication, the system achieves data completeness for recovery purposes without the time cost of replicating every single snapshot.
Data Source
AI summary
Technologies are described herein for skipping snapshots during a snapshot replication process in order to maintain an established recovery point objective. A first snapshot is selected after a previously replicated snapshot. A creation time of the first snapshot is retrieved. A difference between a current time and the creation time of the first snapshot is computed. A determination is made as to whether the difference is less than a recovery point objective. If the difference is less than a recovery point objective, then the first snapshot is replicated in the snapshot replicated process. If the difference is not less than a recovery point objective, then the first snapshot is skipped through the snapshot replication process.