Dynamic Replication Mode Switching for Data Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face challenges in minimizing downtime during recovery and keeping pace with high data transaction rates at production sites, leading to potential shutdowns due to the overhead of journaling, which limits the ability to roll back to any specified point in time effectively.
Innovation Solution
A method and system that dynamically switch between snapshot hot push and continuous replication, using a dirty bitmap to track changes and allowing for lower latency and greater point-in-time mobility, enabling replication systems to adapt to changing data transaction rates without allocating additional disk space and allowing I/O operations during data transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If journaling is used for continuous data protection, then the ability to roll back to any specified point in time is improved, but the overhead causes the backup site to not keep pace with high data transaction rates, leading to production site shutdowns
Solution Approach 1:
The system dynamically switches between two replication modes (snapshot hot push and continuous replication with journaling) based on current workload conditions. When transaction rates are high, it uses snapshot hot push to avoid journaling overhead; when rates are lower, it uses continuous replication for better point-in-time recovery. This dynamic adaptation resolves the contradiction by adjusting the protection mechanism to match current productivity demands.
Solution Approach 2:
The system changes the operational parameters of data replication by switching between different replication modes. It monitors transaction rates and adjusts the replication strategy accordingly, changing from journal-based continuous replication to snapshot-based replication when transaction rates exceed thresholds, thereby maintaining both reliability and productivity.
2Loss of time
If continuous replication is used to minimize downtime during recovery, then the recovery time is improved, but the system cannot handle high data transaction rates without forcing production site shutdown
Solution Approach 1:
The replication system dynamically adjusts its operation mode based on real-time transaction rate monitoring. During high transaction periods, it switches to snapshot hot push mode which allows I/O operations during data transfer and does not require production site shutdown, thus maintaining productivity while still enabling recovery capability.
Solution Approach 2:
The snapshot hot push mode enables continuous I/O operations during the data transfer process, allowing the production site to remain operational without shutdown. This maintains the continuity of useful action (data processing) while still achieving replication for recovery purposes, thereby reducing the impact on productivity during the replication process.
3Productivity
If snapshot hot push is used to allow I/O operations during data transfer, then productivity is improved, but the ability to recover to any specified point in time is reduced compared to continuous replication
Solution Approach 1:
The system creates a universal data protection solution that can operate in multiple modes (snapshot hot push and continuous replication with journaling) depending on requirements. The snapshot hot push mode provides productivity benefits with adequate recovery capability for recent history, while continuous replication provides enhanced point-in-time recovery. This multi-functionality allows the system to satisfy different recovery needs while maintaining productivity.
4Stability of the object's composition
If the backup site processes all data transactions to keep pace with the production site, then data consistency is improved, but the overhead causes the system to choke and force production site shutdown
Solution Approach 1:
The system dynamically selects the replication mode based on transaction rate conditions. During high transaction periods, snapshot hot push is used which captures data at snapshot intervals rather than processing every transaction, reducing the processing overhead at the backup site while maintaining acceptable data consistency. During lower transaction periods, continuous replication ensures full consistency. This dynamic approach prevents system choke points.
Solution Approach 2:
The snapshot hot push mode implements partial action by replicating data at snapshot intervals rather than processing every single transaction in real-time. This partial replication approach reduces the backup site's processing burden and prevents system overload, while still providing sufficient data consistency for recovery purposes without requiring production site shutdown.
Data Source
AI summary
A method, system, and computer program product for data replication, comprising dynamically changing between snapshot hot push and continuous replication; wherein snapshot hot push denotes a replication mode where a snapshot is pushed from the production site to the replication site while IO occurs to the production site.