Journal-Based Replication via Virtual Service Layer

Resolve Bottlenecks,
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 system shutdowns due to backlog and limited recovery points in time.

Innovation Solution

A system that integrates journal-based replication with a virtual service layer, enabling interception and splitting of I/O operations to create a continuous data protection image across multiple sites, allowing for dynamic adaptation to changing transaction rates and ensuring data consistency across geographic locations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If journaling is used to provide continuous data protection, then recovery to any specified point in time is enabled, but the backup site cannot keep pace with high data transaction rates at the production site

Engineering Contradiction:

Improverecovery point precisionVSAvoiddata transaction throughput

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

A virtual service layer is introduced as an intermediary between the production site and the backup site. This layer includes a splitter that intercepts I/O operations and a journal-based replication appliance that processes changes asynchronously, allowing the backup site to follow production changes without forcing production to slow down.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically adapts to changing data transaction rates by using asynchronous journal processing. The replication rate can vary based on production workload conditions, allowing the system to maintain continuous protection during high transaction periods without creating a fixed bottleneck.

Inventive Principle:

Principle #15Dynamics

2Reliability

If the backup site processes every data transaction at the production site, then data consistency is maintained, but the production site is forced to slow down or shut down

Engineering Contradiction:

Improvedata consistencyVSAvoidproduction throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

Instead of synchronous processing, the system uses periodic or asynchronous journal processing. The backup site processes journal entries at its own pace, periodically catching up with production changes without interfering with ongoing production transactions.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The virtual service layer acts as a mediator that decouples production and backup operations. The splitter intercepts I/O operations and the journal-based replication appliance processes them asynchronously, ensuring data consistency is maintained without forcing production to slow down.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If conventional backup systems are used, then data protection is provided, but recovery time is long and data loss occurs between backup points

Engineering Contradiction:

Improvedata protectionVSAvoidrecovery time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system provides continuous data protection through ongoing journal-based replication. Instead of periodic backups, data is continuously tracked and replicated in real-time, eliminating gaps between backup points and enabling immediate recovery to any point in time.

Inventive Principle:

Principle #20Continuity of useful action

Solution Approach 2:

Journal entries are created and maintained in advance as production changes occur. This preliminary recording of changes enables rapid recovery without needing to re-process entire datasets, as the journal provides a ready-to-apply history of changes.

Inventive Principle:

Principle #10Preliminary action

4Reliability

If the backup site processes data transactions synchronously, then data consistency is ensured, but system downtime increases during recovery

Engineering Contradiction:

Improvedata consistencyVSAvoidrecovery duration

Core Design Contradiction:

ReliabilityVSDuration of action of moving object

Solution Approach 1:

The system uses asynchronous or periodic journal processing rather than synchronous processing. This allows the backup site to process changes at its own pace, maintaining consistency while enabling faster recovery by avoiding the need to wait for all production transactions to complete.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

Journal entries are prepared in advance and stored for later application. During recovery, these pre-prepared entries can be applied quickly without needing to re-process production transactions, significantly reducing recovery duration while maintaining data consistency.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS8429362B1Journal based replication with a virtual service layer

Publication Date: 2013.04.23 EMC IP HLDG CO LLC

AI summary

A system, program product, and computer implemented method for data replication, comprising enabling a virtual service layer to consume a storage medium of a site and map the storage medium of the site as one or more virtual storage volumes, enabling the virtual service layer to present the one or more virtual storage volumes for consumption by a host, enabling a splitter of the site to intercept I/O written to the one or more virtual storage volumes, splitting intercepted I/O to a journal based replication appliance, and enabling the journal based replication appliance to create a continuous data protection image of the data written to one or more virtual storage volumes.