Hash-Based Replication Transition for Storage Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data storage systems face challenges in transitioning from asynchronous replication to synchronous replication, resulting in long transition times and disruptive performance impacts, as they often require full resynchronization and hold incoming I/Os.

Innovation Solution

A method and system that enable a non-disruptive transition from asynchronous to synchronous replication by using snapshot mechanisms and hash-based replication, allowing for simultaneous execution of asynchronous and synchronous replication commands, and spreading the transition impact over minutes or hours, without full resynchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full resynchronization is performed during transition from asynchronous to synchronous replication, then data consistency is improved, but transition time increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidtransition time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by capturing a snapshot of the production data before transitioning to synchronous replication. This snapshot serves as a pre-prepared baseline that eliminates the need for full resynchronization during the transition, allowing the system to achieve data consistency through incremental synchronization rather than complete data transfer.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The transition process is segmented into distinct phases: capturing a snapshot, identifying changed blocks through hash comparison, and synchronizing only those specific blocks. This segmentation allows the system to avoid full resynchronization by focusing only on the portions of data that have changed, significantly reducing transition time while maintaining data consistency.

Inventive Principle:
Principle #1Segmentation

2Reliability

If incoming I/Os are held during replication transition, then data consistency is improved, but system performance deteriorates

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adjusts replication behavior during transition by operating in a hybrid mode where synchronous replication is applied only to identified changed blocks while asynchronous replication continues for unchanged data. This dynamic approach allows I/O operations to proceed without being held, maintaining system performance while achieving data consistency for the specific blocks that require synchronization.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Instead of applying uniform synchronous replication to all data (which would hold all I/Os), the system applies synchronous replication locally only to the specific blocks that have changed since the snapshot. This localized approach maintains data consistency for changed blocks while allowing other I/O operations to proceed asynchronously, preventing overall system performance deterioration.

Inventive Principle:
Principle #3Local quality

3Reliability

If full resynchronization is performed during replication transition, then data consistency is improved, but computational resources increase

Engineering Contradiction:
Improvedata consistencyVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system extracts and identifies only the specific data blocks that have changed since the snapshot using hash value comparison. By taking out only the changed blocks for synchronization rather than processing all data, the system significantly reduces computational resource requirements while maintaining data consistency for the relevant portions of the dataset.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs partial action by synchronizing only the changed blocks identified through hash comparison rather than performing excessive full resynchronization of all data. This partial approach achieves the necessary data consistency with minimal computational overhead, avoiding the wasteful expenditure of resources on unchanged data.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10534547B2Consistent transition from asynchronous to synchronous replication in hash-based storage systems
Publication Date: 2020.01.14 EMC IP HLDG CO LLC
  • US10534547B2 patent drawing
  • US10534547B2 patent drawing
  • US10534547B2 patent drawing

AI summary

A System, computer program product, and computer-executable method of transitioning replication on a data storage system including a production site and a replication site from asynchronous replication to synchronous replication, the System, computer program product, and computer-executable method including receiving a request to transition from asynchronous replication to synchronous replication and changing the data storage system to a transition mode, wherein the data storage system transitions the data storage system from using asynchronous replication to synchronous replication.