Star Replication System for Continuous Data Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face challenges in maintaining continuous data protection, particularly in keeping pace with high data transaction rates at production sites without slowing them down, leading to potential backlogs and system shutdowns.
Innovation Solution
A method and system for performing data replication and backup that involves a five-state journaling process, where data is replicated from a production site to a backup site, and then from the backup site to a secondary backup site, enabling dynamic adaptation to changing transaction rates and minimizing downtime during recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If journaling is used for continuous data protection, then data can be recovered to any specified point in time, but the backup site cannot keep pace with high data transaction rates at the production site
Solution Approach 1:
The patent segments the replication process into multiple independent replication technologies operating in parallel. Different replication methods (synchronous, asynchronous, continuous data protection) are applied to different data streams or time periods, allowing the system to handle high transaction rates while maintaining precise recovery points through the CDP component.
Solution Approach 2:
The system dynamically changes replication parameters based on transaction rates and recovery requirements. When transaction rates are high, the system adjusts replication frequency and method, switching between synchronous and asynchronous modes, or between full replication and incremental replication, to balance throughput and recovery precision.
2Reliability
If the backup site processes every data transaction, then data protection is maintained, but the production site must slow down causing downtime
Solution Approach 1:
The patent applies partial replication by selecting which data transactions to replicate based on priority, size, and recovery requirements. Not every data transaction is replicated in real-time; instead, high-priority transactions are replicated immediately while lower-priority ones are batched or replicated asynchronously, maintaining data protection integrity without forcing production slowdowns.
Solution Approach 2:
The patent introduces an intermediary replication management layer that sits between the production site and backup site. This intermediary intelligently routes, buffers, and prioritizes data transactions, smoothing the flow of data to the backup site and preventing backup processing bottlenecks from causing production downtime.
3Device complexity
If a single replication technology is used, then the system is simple to manage, but it cannot adapt dynamically to changing data transaction rates
Solution Approach 1:
The patent implements a universal replication framework that can perform multiple replication functions through a single integrated system. The system supports synchronous replication, asynchronous replication, continuous data protection, incremental replication, and full replication all within one architecture, allowing dynamic adaptation to changing transaction rates without requiring separate systems for each mode.
Solution Approach 2:
The patent creates a dynamic replication system that automatically adjusts its behavior based on real-time conditions. The system monitors transaction rates, storage capacity, network bandwidth, and recovery requirements, then dynamically switches between different replication technologies and strategies. This dynamic adaptation allows the system to handle varying workloads efficiently while maintaining manageable complexity through automated decision-making.
Data Source
AI summary
Example embodiments of the present invention relate to a method, a system, and a computer program product for performing data replication and backup. The method comprises performing a first data replication of a production site storage to a replication site storage and performing a first backup of the production site storage to a production site backup storage. A second data replication then may be performed from the production site backup storage to a backup site backup storage.