Replication Journaling for Concurrent Historical Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face challenges in maintaining continuous data protection by keeping pace with high data transaction rates at production sites without slowing them down, leading to potential production site shutdowns due to backlog of un-logged transactions at backup sites.
Innovation Solution
A method and system that enable concurrent host access at a replica site to a point in time different than the current time, using a five-state journaling process and snapshot mechanisms to manage data replication, allowing for efficient data protection and recovery while minimizing downtime and data lag.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data replication is performed at high transaction rates at the production site, then data protection completeness is improved, but the backup site cannot keep pace leading to transaction backlog and potential production shutdown
Solution Approach 1:
The patent segments the journaling process into five distinct states (pending, in-progress, committed, rolled-back, and abandoned) to differentiate and manage various stages of data replication. This segmentation allows the system to handle high transaction rates by processing transactions through multiple states rather than requiring complete processing at each stage, thereby preventing backlog accumulation while maintaining data protection completeness.
Solution Approach 2:
The system dynamically adjusts transaction processing based on the state of replication. Transactions can transition between different states depending on replication progress and system conditions, allowing the backup site to adapt to changing data transaction rates without forcing production site shutdowns. This dynamic state management enables flexible handling of replication delays.
2Productivity
If journaling overhead is reduced to maintain production site performance, then production productivity is improved, but data protection reliability deteriorates due to incomplete transaction logging
Solution Approach 1:
The patent implements partial action by allowing transactions to be marked as committed even when replication to the backup site is not yet complete. This enables the production site to continue processing without waiting for backup completion, maintaining high productivity while still providing data protection. The system accepts that not all transactions are fully replicated at all times, but maintains sufficient protection through the state-based approach.
Solution Approach 2:
The five-state journaling system acts as an intermediary layer between the production site and backup site. It buffers and manages transaction states, allowing the production site to operate at full speed while the backup site processes transactions at its own pace. The journal states serve as the intermediary mechanism that decouples the performance requirements of the two sites.
3Adaptability or versatility
If continuous data protection is implemented with traditional journaling, then any point in time recovery is enabled, but system complexity increases due to multiple data transactions required at backup site
Solution Approach 1:
The patent changes the parameter of transaction state tracking from a simple binary (logged/not logged) to a five-state model. This parameter change enables more flexible recovery options while managing complexity through standardized state transitions. The system can recover to any point in time by restoring transactions to appropriate states based on the recovery point requirements.
Solution Approach 2:
The system creates simplified copies of transaction states at the backup site rather than requiring complete replication of all processing logic. The five-state journal entries are copied and managed independently, allowing point-in-time recovery without duplicating the entire production system complexity at the backup site.
Data Source
AI summary
Example embodiments of the present invention relate to a method, a system, and a computer program product for enabling concurrent host access at a replica site to a point in time different than a current point in time of a replication environment. The method includes performing data protection from a production site to a replica site in a replication environment and enabling concurrent host access at the replica site to a point in time different than a current point in time of the replication environment.