Writeable Snapshot Replication via Journal Interception

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data protection systems face challenges in maintaining continuous data protection, particularly in keeping pace with high data transaction rates at production sites without causing downtime or data backlog, due to the overhead of journaling processes.

Innovation Solution

A method and system for replicating writeable snapshots in a continuous replication environment by intercepting snapshot creation commands, allowing snapshot creation, and using a journal to manage data transactions, enabling efficient data recovery and minimizing downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If journaling is used for continuous data protection, then data recovery capability is improved, but system performance deteriorates due to overhead

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates a copy of the snapshot command in the journal at the replication site, allowing the production site to proceed without waiting for the backup site to process the snapshot. This copying mechanism enables the production site to maintain high performance while the backup site processes the snapshot copy, thus resolving the contradiction between data recovery capability and system performance.

Inventive Principle:
Principle #26Copying

2Reliability

If snapshot creation is intercepted and processed at replication site, then data consistency is improved, but replication latency increases

Engineering Contradiction:
Improvedata consistencyVSAvoidreplication latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by placing the snapshot command in the journal before actual snapshot creation occurs. This allows the snapshot to be recorded and acknowledged at the production site first, and then processed at the backup site without blocking the production workflow, thus maintaining data consistency while minimizing replication latency.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If continuous data protection is implemented, then data loss prevention is improved, but downtime during recovery increases

Engineering Contradiction:
Improvedata loss preventionVSAvoidrecovery downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-creating snapshots and recording them in the journal before they are needed for recovery. This allows the backup site to have ready-to-use recovery points, significantly reducing the downtime required during actual recovery operations while maintaining continuous data protection and preventing data loss.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9965306B1Snapshot replication
Publication Date: 2018.05.08 EMC IP HLDG CO LLC
  • US9965306B1 patent drawing
  • US9965306B1 patent drawing
  • US9965306B1 patent drawing

AI summary

A computer implemented method, system, and program product for replicating writeable snapshots in a continuous replication environment, the method comprising intercepting a command to create a snapshot of a virtual volume, putting a snapshot create message in a journal at a replication site; and allowing the creation of the snapshot.