Asynchronous Replication Snapshot Recovery for Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Asynchronous data replication interruptions can lead to inconsistent states between primary and secondary storage objects, making it difficult to recover data to a precise point in time due to unordered updates during resumed replication.

Innovation Solution

Automatically generating snapshots of replica storage objects upon detection of asynchronous replication interruption, accumulating updates during the interruption, and resuming asynchronous replication when the interruption ends, ensuring consistent data recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If asynchronous replication is resumed after interruption, then data transfer continues, but updates are applied in unpredictable order causing inconsistency

Engineering Contradiction:
Improvedata transfer continuityVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by detecting replication interruptions and automatically generating snapshots of the replica storage object before resuming replication. This preliminary snapshot creation ensures that a consistent recovery point is established prior to applying subsequent updates, preventing the inconsistency problem that would otherwise occur when updates are applied in unpredictable orders after resumption.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If snapshots are created frequently to ensure consistency, then data recovery precision improves, but storage and memory resources are consumed

Engineering Contradiction:
Improverecovery point precisionVSAvoidstorage resources
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

Instead of creating snapshots frequently and uniformly, the system applies local quality by creating snapshots selectively only when replication interruptions is detected. This targeted approach ensures that snapshots are generated precisely where needed (at interruption points) rather than continuously, thereby maintaining recovery precision while minimizing unnecessary consumption of storage and memory resources.

Inventive Principle:
Principle #3Local quality

3Loss of substance

If replication updates are accumulated during interruption, then data loss is minimized, but the complexity of managing unordered updates increases

Engineering Contradiction:
Improvedata lossVSAvoidupdate management complexity
Core Design Contradiction:
Loss of substanceVSDevice complexity

Solution Approach 1:

The system introduces an intermediary mechanism by automatically detecting replication interruptions and generating snapshots that serve as intermediary recovery points. These snapshots act as mediators that organize and structure the accumulated updates, allowing the system to minimize data loss while reducing the complexity of managing unordered updates through automated snapshot-based recovery point establishment.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240330126A1Automated restart of asynchronous remote replication after failures
Publication Date: 2024.10.03 DELL PROD LP
  • US20240330126A1 patent drawing
  • US20240330126A1 patent drawing
  • US20240330126A1 patent drawing

AI summary

A disaster recovery storage array automatically generates snapshots of replica storage objects responsive to detection of interruption of asynchronous replication of production storage objects of a primary storage system to the replica storage objects. The primary storage array accumulates updates to the production storage objects over a plurality of asynchronous replication cycles during the interruption. Asynchronous replication automatically resumes when the interruption ends. Accumulation of updates and resumption of asynchronous replication may be performed iteratively if there are multiple interruptions before the replica storage objects are consistent with the production storage objects. The snapshots are automatically discarded after the replica storage objects are made consistent with the production storage objects.