Cross-Region File Replication Restart Using Common Snapshots

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing file system replication technologies face challenges in efficiently restarting replication processes due to failures, interruptions, or infrastructure changes, particularly in cross-region setups, leading to potential corruption and resource wastage, and lack effective checkpoint mechanisms for ensuring deterministic restarts and atomic transactions across different geographic regions.

Innovation Solution

The implementation of cross-region replication techniques that utilize restartable base snapshots, delta generation and application, and secure data transfer mechanisms, including Object Store and separate key management, to ensure reliable and scalable restart operations across different cloud infrastructure regions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cross-region replication is restarted after failures or interruptions, then replication continuity is restored, but data corruption and resource wastage may occur without proper checkpoint mechanisms

Engineering Contradiction:

Improvereplication continuityVSAvoiddata corruption

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by creating and storing checkpoint snapshots at predetermined intervals during the replication process. These checkpoints are prepared in advance so that when a failure occurs, the system can immediately restore to the most recent valid checkpoint without risking data corruption or resource wastage during restart.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements beforehand cushioning by maintaining multiple checkpoint snapshots that serve as safety buffers. When failures or interruptions occur, these pre-established checkpoints cushion the system against data corruption by providing known-good restore points, eliminating the need to restart from scratch and preventing resource wastage.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Device complexity

If cross-region replication is restarted without checkpoint mechanisms, then system complexity is reduced, but deterministic restarts and atomic transactions cannot be ensured

Engineering Contradiction:

Improvesystem complexityVSAvoiddeterministic restart capability

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The system uses copying by creating checkpoint snapshots that are stored separately from the active replication data. These snapshot copies serve as immutable reference points that enable deterministic restarts. The copying mechanism allows the system to restore to exact previous states without complex recalculation, ensuring atomic transactions while maintaining manageable system complexity.

Inventive Principle:

Principle #26Copying

3Stability of the object's composition

If replication restarts from the beginning after interruptions, then data consistency is simplified, but resource consumption increases significantly

Engineering Contradiction:

Improvedata consistencyVSAvoidresource consumption

Core Design Contradiction:

Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by establishing checkpoint snapshots at regular intervals during replication. When an interruption occurs, the system can resume from the most recent checkpoint rather than restarting from the beginning. This preliminary checkpointing maintains data consistency while dramatically reducing resource consumption by avoiding redundant replication of already-synchronized data.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements discarding and recovering by identifying and discarding the portion of replication work that needs to be redone after an interruption. By recovering from the most recent valid checkpoint, the system discards only the minimal necessary work (data generated since the checkpoint) rather than repeating all replication operations, thus maintaining consistency while minimizing resource consumption.

Inventive Principle:

Principle #34Discarding and recovering

4Ease of manufacture

If cross-region replication lacks restartability mechanisms, then implementation simplicity is maintained, but failures and infrastructure changes cause replication breakdown

Engineering Contradiction:

Improveimplementation simplicityVSAvoidreplication resilience

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically creating and storing checkpoint snapshots during normal replication operations. This preliminary preparation enables the system to handle failures and infrastructure changes resiliently without requiring complex restart logic. The checkpoints are established in advance, allowing simple resume-from-checkpoint operations that maintain replication reliability while keeping the implementation straightforward.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20260019253A1End-to-end restartability of cross-region replication using a common snapshot

Publication Date: 2026.01.15 ORACLE INT CORP

AI summary

Techniques are described for performing different types of restart operations for a file storage replication between a source file system and a target file system in different cloud infrastructure regions. In certain embodiments, the disclosed techniques perform a restart operation to terminate a current cross-region replication by synchronizing resource cleanup operations in the source file system and the target file system, respectively. In other embodiments, disclosed techniques perform a restart operation to allow a customer to reuse the source file system by identifying a restartable base snapshot in the source file system without dependency on the target file system.