Journal-Based Data Replication Using Xcopy for High-Throughput Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data protection systems face challenges in maintaining continuous data protection, as they struggle to keep pace with high data transaction rates at production sites, leading to potential shutdowns due to backlog and limited recovery points in time.

Innovation Solution

Implementing a method that utilizes the xcopy command in a journal-based replication environment, where data is read from and written to undo and DO streams, allowing for efficient data replication and recovery by leveraging the extended copy command to manage metadata and data movement within storage arrays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional journaling is used for continuous data protection, then data recovery capability is improved, but the backup site cannot keep pace with high data transaction rates at the production site

Engineering Contradiction:
Improvedata recovery capabilityVSAvoiddata transaction processing rate
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the data replication process into distinct streams: a DO (data outgoing) stream for capturing changes from the production site and an UNDO stream for storing undo information. This segmentation allows parallel processing of data transactions and undo operations, enabling the backup site to keep pace with high data transaction rates while maintaining continuous recovery capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by capturing undo information immediately when data changes occur at the production site, before the changes are permanently committed. The journaling mechanism records undo entries in advance, allowing the backup site to prepare recovery operations ahead of time and avoid bottlenecks during high transaction periods.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If data replication operates at the application level or file system level, then implementation complexity is reduced, but data consistency and recovery precision are compromised

Engineering Contradiction:
Improveimplementation complexityVSAvoiddata consistency and recovery precision
Core Design Contradiction:
Device complexityVSManufacturing precision

Solution Approach 1:

The patent introduces an intermediary mechanism at the data block level that bridges the gap between simplicity and precision. The journaling system acts as a mediator, capturing detailed block-level changes without requiring complex application-level integration. This intermediary layer provides precise data consistency and recovery capability while maintaining relatively simple implementation through standardized block-level operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the backup site processes every data transaction synchronously, then data consistency is improved, but the production site may be forced to shut down due to backlog

Engineering Contradiction:
Improvedata consistencyVSAvoidproduction site throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamics by allowing the replication process to adapt its behavior based on workload conditions. The journaling mechanism can dynamically adjust processing speed and buffer usage, capturing undo information asynchronously when the production site is under high load while maintaining data consistency through proper journaling protocols. This dynamic adaptation prevents production shutdowns while ensuring recovery capability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9535801B1Xcopy in journal based replication
Publication Date: 2017.01.03 EMC IP HLDG CO LLC
  • US9535801B1 patent drawing
  • US9535801B1 patent drawing
  • US9535801B1 patent drawing

AI summary

A method, system, and program product for data replication, comprising reading do metadata, xcopying data from a storage medium to an undo stream, xcopying data from a do stream to the storage medium, and updating do meta data and the undo meta data.