Abort Command Handling in Data Replication Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data replication systems face challenges in keeping pace with high data transaction rates at production sites, leading to potential shutdowns due to backlog and inefficiencies in journaling processes, which limits continuous data protection and recovery capabilities.
Innovation Solution
The system processes abort commands without pausing replication, allowing for background synchronization and handling of aborted IOs by discarding or overwriting them, ensuring continuous operation and minimizing downtime during data recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If journaling is used to provide continuous data protection, then recovery capability to any point in time is improved, but the backup site cannot keep pace with high data transaction rates at the production site
Solution Approach 1:
The patent extracts the abort command handling logic from the main replication processing path. By separating the handling of abort commands (which indicate failed or unnecessary transactions) from the normal replication flow, the system can discard these problematic transactions without blocking the entire replication process, thus maintaining high processing rates while preserving continuous protection capability.
Solution Approach 2:
The system changes the state management parameter by introducing an 'aborted' flag in the replication state machine. This allows the system to track and differentiate between successful and aborted transactions, enabling selective processing where aborted transactions are discarded and successful ones continue through normal replication, thereby maintaining throughput while ensuring data protection.
2Reliability
If the backup site processes every data transaction to maintain continuous protection, then data protection completeness is improved, but the production site may be forced to shut down due to backlog
Solution Approach 1:
The patent converts the harmful effect of abort commands (which indicate transaction failures or unnecessary operations) into a beneficial filtering mechanism. By processing and identifying abort commands, the system can discard these unnecessary transactions from the replication backlog, preventing them from causing production site shutdowns while still maintaining complete protection for successful transactions.
Solution Approach 2:
The system dynamically adjusts its replication behavior based on transaction outcomes. When a transaction is marked as aborted, the system dynamically changes its state to discard this transaction rather than forcing it through the normal replication process. This dynamic adaptation allows the system to maintain data protection completeness for valid transactions while avoiding the time loss and downtime caused by processing failed transactions.
3Device complexity
If abort commands are processed through normal replication flow, then system simplicity is maintained, but replication may pause and system availability decreases
Solution Approach 1:
The patent segments the replication processing into distinct paths: one for normal successful transactions and another for abort commands. By creating this segmentation in the processing flow, the system can handle aborted transactions separately (discarding them) without interrupting the normal replication process, thus maintaining system availability while adding only minimal complexity through the segmentation mechanism.
Data Source
AI summary
A system, method, and computer product for data replication comprising receiving an IO, receiving an IO abort command, the IO abort command specifying an IO to be aborted, determining if the IO was sent to a DPA by a splitter.