Triangular Asynchronous Replication Failover Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data replication systems, such as synchronous and asynchronous RDF systems, face challenges with high latency and data consistency issues, especially over long distances, and require significant overhead in maintaining data mirroring relationships, which can lead to data loss during failures.

Innovation Solution

Implementing a triangular asynchronous replication system that involves swapping primary and backup groups between data centers, creating data mirroring relationships, and initiating multisession control to ensure synchronous and asynchronous mirroring, thereby reducing latency and ensuring data consistency across geographically dispersed backup devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous RDF transfer is used, then data consistency between primary and secondary storage devices is ensured, but write latency increases due to waiting for acknowledgment

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

Solution Approach 1:

The system performs preliminary actions by pre-positioning backup data at intermediate storage locations before failure occurs. When the primary storage device fails, the system can immediately activate pre-prepared backup copies without waiting for real-time synchronization, thus maintaining data consistency while reducing recovery time and latency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces intermediate storage devices as mediators in the data replication architecture. These intermediaries receive and hold backup copies of data, allowing the primary storage device to acknowledge writes immediately without waiting for final destination confirmation. This intermediary layer decouples the write acknowledgment from the complete replication chain, reducing latency while ensuring data consistency through the intermediary's reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If asynchronous RDF transfer is used, then write latency is reduced, but data consistency and recoverability cannot be guaranteed

Engineering Contradiction:
Improvewrite latencyVSAvoiddata consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-positioning backup data at intermediate storage locations before failure occurs. When the primary storage device fails, the system can immediately activate pre-prepared backup copies without waiting for real-time synchronization, thus maintaining data consistency while reducing recovery time and latency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where intermediate storage devices send acknowledgments to the primary storage device once data has been successfully received and stored. This feedback loop allows the primary device to know when backup is complete without waiting for the final destination, enabling asynchronous operation with guaranteed data consistency through confirmed delivery.

Inventive Principle:
Principle #23Feedback

3Loss of time

If semi-synchronous RDF transfer is used, then some latency is reduced, but bottlenecks are delayed rather than eliminated as previous transfers must be acknowledged before new transfers begin

Engineering Contradiction:
Improvewrite latencyVSAvoidtransfer throughput
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The patent segments the data replication process into multiple independent parallel streams through the use of intermediate storage devices. Instead of a single sequential chain where each transfer must complete before the next begins, the system creates multiple segments that can operate simultaneously, with the primary storage device able to initiate multiple backup transfers in parallel, thus eliminating bottlenecks while maintaining data consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system ensures continuity of useful action by implementing a pipeline architecture where data transfer never stops. While one transfer is being acknowledged, another is already in progress to the next intermediate node. This continuous flow eliminates idle waiting time and maintains constant productivity, as the primary storage device is always engaged in some form of data replication activity without interruption.

Inventive Principle:
Principle #20Continuity of useful action

4Adaptability or versatility

If multiple host systems access a single storage device, then data sharing is enabled, but complexity of managing access and consistency increases

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidaccess management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the storage system into multiple independent storage devices, each capable of handling host access independently. This segmentation allows different host systems to access different storage devices simultaneously without interfering with each other, reducing access management complexity while maintaining data sharing capability. Each storage device operates as an independent unit with its own backup chain, simplifying the overall system management.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7647525B2Resumption of operations following failover in connection with triangular asynchronous replication
Publication Date: 2010.01.12 EMC IP HLDG CO LLC
  • US7647525B2 patent drawing
  • US7647525B2 patent drawing
  • US7647525B2 patent drawing

AI summary

Handling failure of a primary group at a first data center that is part of plurality of data centers providing triangular asynchronous replication includes creating a data mirroring relationship between at least one storage volume at a second data center having a synchronous backup group that is part of the plurality of data centers and at least one storage volume at a third data center having an asynchronous backup group that is part of the plurality of data centers and resuming work at the third data center. Handling failure of a primary group at a first data center may also include synchronizing the at least one storage volume at the second data center with the at least one storage volume at the third data center prior to resuming work at the third data center.