# US 2026/0019253 A1 · End-to-end restartability of cross-region replication using a common snapshot

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0019253 A1
- Document ID: US20260019253A1
- Status: Published application
- Kind: A1
- Application number: 19/331,462
- Filed: 2025-09-17
- Published: 2026-01-15
- Earliest claimed: 2022-06-16
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Parth Singhal; Vikram Singh Bisht; Satish Kumar Kashi Visvanathan; Niharika Salady
- Web page: https://patentgrep.com/patent/US20260019253A1

## CPC

- G06F 11/1451: {by selection of backup contents}
- G06F 9/505: {considering the load}
- G06F 11/1417: {Boot up procedures}
- G06F 11/1464: {for networked environments}
- G06F 11/2023: {Failover techniques}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2038: {with a single idle spare processing component}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)}
- G06F 16/11: File system administration, e.g. details of archiving or snapshots (error detection or correction of the data by redundancy in operations G06F11/14)
- G06F 16/119: {Details of migration of file systems (migration mechanisms in storage systems G06F3/0647)}
- G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)}
- G06F 16/1756: {based on delta files}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 16/1844: {Management specifically adapted to replicated file systems}
- G06F 16/185: Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof (details of archiving G06F16/11)
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- H04L 9/0819: {Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062)}
- H04L 9/0836: {using tree structure or hierarchical structure}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- G06F 11/2048: {where the redundant components share neither address space nor persistent storage}
- G06F 16/1774: {Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files}
- G06F 16/2246: {Trees, e.g. B+trees}
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

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.

## Claims

### Claim 1

A method, comprising:
performing, by a computing system, a first cross-region replication process between a source file system in a source region and a target file system in a target region;
receiving, by the computing system, a request to perform a second cross-region replication process;
comparing, by the computing system, a first source provenance identifier from a first source snapshot in the source file system to a first target provenance identifier from a first target snapshot in the target file system;
determining, by the computing system, whether the first source provenance identifier matches the first target provenance identifier;
in accordance with a determination that the first source provenance identifier matches the first target provenance identifier:
restarting, by the computing system, the first cross-region replication by performing the second cross-region replication using the first source snapshot that corresponds to the first source provenance identifier; and
in accordance with a determination that the first source provenance identifier does not match the first target provenance identifier:
aborting, by the computing system, the second cross-region replication.

### Claim 2 (depends on 1)

The method of claim 1, further comprising pausing, by the computing system, the first cross-region replication process based at least in part on a triggering event.

### Claim 3 (depends on 1)

The method of claim 1, wherein at least one of the first source snapshot or the first target snapshot comprises at least one of identification of the first cross-region replication, first unique identifications of snapshots in the source file system, or second unique identifications of snapshots in the target file system.

### Claim 4 (depends on 1)

The method of claim 1, wherein the second cross-region replication process comprises a restart of the first cross-regional replication process.

### Claim 5 (depends on 4)

The method of claim 4, wherein the request to perform the second cross-region replication process comprises requesting:
the restart of the first cross-regional replication process based at least in part on a common snapshot as identified by the comparison of the first source provenance identifier and the first target provenance identifier; and
for continuing a same data flow direction as the first cross-region replication process.

### Claim 6 (depends on 1)

The method of claim 1, wherein the request to perform the second cross-region replication process comprises requesting for a reverse cross-region replication process.

### Claim 7 (depends on 6)

The method of claim 6, wherein the reverse cross-region replication process comprises:
identifying a latest common snapshot between the source file system and the target file system;
generating deltas, by the target file system, based at least in part on differences between the latest new snapshot and the latest common snapshot in the target file system;
transferring the deltas from the target file system to the source file system; and
applying the deltas, by the source file system, to the latest common snapshot in the source file system to generate a restartable base snapshot in the source file system.

### Claim 8 (depends on 7)

The method of claim 7, wherein transferring the deltas from the target file system to the source file system further comprises uploading the deltas from the target file system to an object storage located in a source region, and downloading the deltas from the object storage to the source file system.

### Claim 9

A non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors of a computing system, cause the one or more processors to perform operations comprising:
performing, by a computing system, a first cross-region replication process between a source file system in a source region and a target file system in a target region;
receiving, by the computing system, a request to perform a second cross-region replication process;
comparing, by the computing system, a first source provenance identifier from a first source snapshot in the source file system to a first target provenance identifier from a first target snapshot in the target file system;
determining, by the computing system, whether the first source provenance identifier matches the first target provenance identifier;
in accordance with a determination that the first source provenance identifier matches the first target provenance identifier:
restarting, by the computing system, the first cross-region replication by performing the second cross-region replication using the first source snapshot that corresponds to the first source provenance identifier; and
in accordance with a determination that the first source provenance identifier does not match the first target provenance identifier:
aborting, by the computing system, the second cross-region replication.

### Claim 10 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein the operations further comprise pausing, by the computing system, the first cross-region replication process based at least in part on a triggering event.

### Claim 11 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein at least one of the first source snapshot or the first target snapshot comprises at least one of identification of the first cross-region replication, first unique identifications of snapshots in the source file system, or second unique identifications of snapshots in the target file system.

### Claim 12 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein the second cross-region replication process comprises a restart of the first cross-regional replication process.

### Claim 13 (depends on 12)

The non-transitory computer-readable medium of claim 12, wherein the request to perform the second cross-region replication process comprises requesting:
the restart of the first cross-regional replication process based at least in part on a common snapshot as identified by the comparison of the first source provenance identifier and the first target provenance identifier; and
for continuing a same data flow direction as the first cross-region replication process.

### Claim 14 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein the request to perform the second cross-region replication process comprises requesting for a reverse cross-region replication process.

### Claim 15

A computing system, comprising:
one or more processors; and
one or more computer readable media storing computer-executable instructions that, when executed by the one or more processors, cause the system to:
perform, by the computing system, a first cross-region replication process between a source file system in a source region and a target file system in a target region;
receive, by the computing system, a request to perform a second cross-region replication process;
compare, by the computing system, a first source provenance identifier from a first source snapshot in the source file system to a first target provenance identifier from a first target snapshot in the target file system;
determine, by the computing system, whether the first source provenance identifier matches the first target provenance identifier;
in accordance with a determination that the first source provenance identifier matches the first target provenance identifier:
restart, by the computing system, the first cross-region replication by performing the second cross-region replication using the first source snapshot that corresponds to the first source provenance identifier; and
in accordance with a determination that the first source provenance identifier does not match the first target provenance identifier:
abort, by the computing system, the second cross-region replication.

### Claim 16 (depends on 15)

The system of claim 15, wherein the system is further caused to pause, by the computing system, the first cross-region replication process based at least in part on a triggering event.

### Claim 17 (depends on 15)

The system of claim 15, wherein at least one of the first source snapshot or the first target snapshot comprises at least one of identification of the first cross-region replication, first unique identifications of snapshots in the source file system, or second unique identifications of snapshots in the target file system.

### Claim 18 (depends on 15)

The system of claim 15, wherein the second cross-region replication process comprises a restart of the first cross-regional replication process.

### Claim 19 (depends on 18)

The system of claim 18, wherein the request to perform the second cross-region replication process comprises requesting:
the restart of the first cross-regional replication process based at least in part on a common snapshot as identified by the comparison of the first source provenance identifier and the first target provenance identifier; and
for continuing a same data flow direction as the first cross-region replication process.

### Claim 20 (depends on 19)

The system of claim 19, wherein the request to perform the second cross-region replication process comprises requesting for a reverse cross-region replication process.
