Xcopy Command Replication Synchronization Logic
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, leading to potential system shutdowns due to backlog of un-logged transactions and limited recovery points in time.
Innovation Solution
Implementing the xcopy command in a replication environment with a splitter and journaling system, where the system determines if source and target LUNs are replicated and synchronized, allowing the xcopy command to proceed only when conditions are met, and handling scenarios where LUNs are not fully replicated or synchronized by emulating or pausing the command.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If journaling is used to enable continuous data protection and rollback to any point in time, then data recovery flexibility is improved, but the backup site cannot keep pace with high data transaction rates at the production site, leading to system shutdowns
Solution Approach 1:
The patent segments the journaling process by implementing separate write paths: a fast path for synchronous replication that maintains performance, and an asynchronous path for comprehensive journaling that enables point-in-time recovery. This segmentation allows the system to handle high transaction rates while maintaining recovery flexibility.
Solution Approach 2:
The system dynamically adjusts its journaling behavior based on transaction rates and recovery requirements. When transaction rates are high, the system optimizes for performance by using the fast path. When recovery flexibility is needed, it switches to comprehensive journaling, allowing adaptive response to changing operational conditions.
2Reliability
If the backup site logs all data transactions to enable continuous protection, then data protection completeness is improved, but the overhead causes the backup site to fall behind production site transactions
Solution Approach 1:
The patent implements preliminary action by pre-establishing multiple write paths and synchronization mechanisms before transaction backlogs occur. The system proactively manages journaling operations to prevent backlog accumulation, ensuring that data protection completeness is maintained without time loss.
Solution Approach 2:
The patent introduces an intermediary layer that mediates between the production site and backup site. This intermediary manages the journaling process, buffering and smoothing transaction flows to prevent the backup site from falling behind while maintaining complete data protection.
3Reliability
If the system forces the production site to slow down to match backup site capacity, then transaction logging completeness is improved, but production site performance deteriorates
Solution Approach 1:
The patent uses copying by creating multiple representations of transaction data in different formats and locations. Instead of forcing the production site to slow down, the system copies transaction information through multiple paths (synchronous and asynchronous), allowing the production site to maintain high speed while ensuring complete logging.
Solution Approach 2:
The system changes parameters dynamically by adjusting journaling depth, synchronization timing, and write path selection based on current transaction rates and system load. This allows the production site to maintain high transaction rates while the system adapts logging completeness to match capacity requirements.
Data Source
AI summary
A method, system and program product for implementing the xcopy command in a replication environment, the replication environment having a production site, a splitter, and a replication site, wherein the replication site has a journal, comprising, determining if the source and target LUNs of the xcopy command are replicated, based on a determination that both source and target LUNs are replicated, determining if the production and replication LUNs are synchronized, based on a positive determination that the LUNs are synchronized, and performing the xcopy command on the replication.