Continuous Data Protection Hot Standbys for Lower Source Load
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems that generate hot standbys for continuous data protection-enabled objects by sending real-time updates from a primary site to a disaster recovery site reduce the performance of the primary site due to resource utilization, and restoring from backups can be time-consuming and may not meet recovery time objectives (RTOs).
Innovation Solution
A data management plan orchestrator analyzes user-specified data protection intents to determine configurations for continuous data protection (CDP) and sync-replication, enabling write filters and CDP services to minimize performance impact while generating hot standbys, and employs techniques to roll back or forward hot standbys efficiently to meet RPO and RTO requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If real-time updates are sent from primary site source system to disaster recovery site system, then hot standby is generated and maintained, but performance of primary site source system is reduced due to resource utilization
Solution Approach 1:
The patent extracts the data replication function from the source system by introducing a separate backup system that receives data from the source system and independently generates hot standbys. This separation removes the performance burden of real-time replication from the source system while maintaining hot standby availability at the disaster recovery site.
Solution Approach 2:
The backup system acts as an intermediary between the source system and the disaster recovery site system. It receives data from the source system, processes it, and sends updates to the disaster recovery site, thereby shielding the source system from the performance impact of maintaining hot standbys.
2Reliability
If real-time updates are sent from primary site source system to disaster recovery site system, then hot standby is generated and maintained, but resource utilization increases
Solution Approach 1:
The patent extracts the resource-intensive replication process from the source system and relocates it to a dedicated backup system. This extraction reduces resource utilization at the source system while maintaining the ability to generate and maintain hot standbys at the disaster recovery site.
Solution Approach 2:
The backup system performs preliminary data processing and replication in advance, preparing data for hot standby generation before it is needed. This preliminary action reduces the need for intensive real-time resource utilization at the source system during critical operations.
3Reliability
If restoration is performed from backups, then data recovery is achieved, but time required for restoration increases
Solution Approach 1:
The patent implements preliminary action by continuously generating and maintaining hot standbys that are pre-prepared and ready for immediate use. When disruption occurs, these pre-prepared hot standbys can be activated instantly, eliminating the time-consuming restoration process associated with traditional backup methods.
Solution Approach 2:
The system creates and maintains copies of data in the form of hot standbys at the disaster recovery site. These copies are kept synchronized with the source system and can be immediately activated upon disruption, avoiding the need to restore data from backups and significantly reducing recovery time.
Data Source
AI summary
A stream of data changes to content of an object associated with a source system is received. A hot standby version of at least a portion of the object maintained at a recovery system is updated by streaming the received stream of data changes to the recovery system. It is determined that a gap exists in the stream of data changes. In response to determining that the gap exists in the stream of data changes, a reference snapshot is requested from the source system. A current state of the hot standby version of at least the portion of the object maintained at the recovery system is caused to be updated to a state of the portion of the object associated with the reference snapshot.