# US 2023/0409539 A1 · Techniques for maintaining snapshot data consistency during file system cross-region replication

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

- Number: US 2023/0409539 A1
- Document ID: US20230409539A1
- Status: Published application
- Kind: A1
- Application number: 18/169,124
- Filed: 2023-02-14
- Published: 2023-12-21
- Earliest claimed: 2022-06-16
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Vikram Singh Bisht; Niharika Salady; Parth Singhal; Satish Kumar Kashi Visanathan
- Web page: https://patentgrep.com/patent/US20230409539A1

## 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 efficient replication and maintaining snapshot data consistency during file storage replication between file systems in different cloud infrastructure regions. In certain embodiments, snapshot creation and deletion requests that occur during cross-region replications may be temporarily withheld until appropriate times to execute such requests safely, depending on the timing relationship between such requests and cross-region replication cycles.

## Claims

### Claim 1

A method, comprising:
generating, by a computing system, a snapshot of a source file system in a source region;
performing, by the computing system, a first cross-region replication and a second cross-region replication between the source file system in the source region and a target file system in a target region, the source region and the target region being in different regions;
receiving, by the computing system, a snapshot deletion request in the source file system to delete the snapshot;
determining, by the computing system, a timing of the snapshot deletion request in the source file system;
performing, by the computing system, a first operation in accordance with the timing of the snapshot deletion request being determined to be during the first cross-region replication; and
performing, by the computing system, a second operation in accordance with the timing of the snapshot deletion request being determined to be between the first and the second cross-region replications.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first operation comprises withholding the snapshot deletion request by the source file system until an end of the first cross-region replication.

### Claim 3 (depends on 2)

The method of claim 2, wherein withholding the snapshot deletion request comprises storing metadata information of the snapshot by the source file system in a database for communicating to the target file system.

### Claim 4 (depends on 2)

The method of claim 2, wherein withholding the snapshot deletion request comprises:
transferring the snapshot by the source file system to the target file system to complete the first cross-region replication; and
deleting the snapshot by the target file system at the end of the second cross-region replication.

### Claim 5 (depends on 1)

The method of claim 1, wherein the second operation comprises deleting the snapshot by the source file system without transferring the snapshot to the target file system.

### Claim 6 (depends on 1)

The method of claim 1, further comprising determining a second timing of generating the snapshot of the source file system.

### Claim 7 (depends on 6)

The method of claim 6, further comprising transferring the generated snapshot to the target file system during the second cross-region replication in accordance with the second timing of the snapshot generation being determined to be during the first cross-region replication and in accordance with the timing of the snapshot deletion request being determined to be after the second cross-region replication.

### Claim 8

A non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
generating, by a computing system, a snapshot of a source file system in a source region;
performing, by the computing system, a first cross-region replication and a second cross-region replication between the source file system in the source region and a target file system in a target region, the source region and the target region being in different regions;
receiving, by the computing system, a snapshot deletion request in the source file system to delete the snapshot;
determining, by the computing system, a timing of the snapshot deletion request in the source file system;
performing, by the computing system, a first operation in accordance with the timing of the snapshot deletion request being determined to be during the first cross-region replication; and
performing, by the computing system, a second operation in accordance with the timing of the snapshot deletion request being determined to be between the first and the second cross-region replications.

### Claim 9 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the first operation comprises withholding the snapshot deletion request by the source file system until an end of the first cross-region replication.

### Claim 10 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein withholding the snapshot deletion request comprises storing metadata information of the snapshot by the source file system in a database for communicating to the target file system.

### Claim 11 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein withholding the snapshot deletion request comprises:
transferring the snapshot by the source file system to the target file system to complete the first cross-region replication; and
deleting the snapshot by the target file system at the end of the second cross-region replication.

### Claim 12 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the second operation comprises deleting the snapshot by the source file system without transferring the snapshot to the target file system.

### Claim 13 (depends on 8)

The non-transitory computer-readable medium of claim 8, the operations further comprising determining a second timing of generating the snapshot of the source file system.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13, the operations further comprising transferring the generated snapshot to the target file system during the second cross-region replication in accordance with the second timing of the snapshot generation being determined to be during the first cross-region replication and in accordance with the timing of the snapshot deletion request being determined to be after the second cross-region replication.

### Claim 15

A 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:
create a snapshot of a source file system in a source region;
perform a first cross-region replication and a second cross-region replication between the source file system in the source region and a target file system in a target region, the source region and the target region being in different regions;
receive a snapshot deletion request in the source file system to delete the snapshot;
determine a timing of the snapshot deletion request in the source file system;
perform a first operation in accordance with the timing of the snapshot deletion request being determined to be during the first cross-region replication; and
perform a second operation in accordance with the timing of the snapshot deletion request being determined to be between the first and the second cross-region replications.

### Claim 16 (depends on 15)

The system of claim 15, wherein the first operation comprises withholding the snapshot deletion request by the source file system until an end of the first cross-region replication.

### Claim 17 (depends on 16)

The system of claim 16, wherein withholding the snapshot deletion request comprises:
transferring the snapshot by the source file system to the target file system to complete the first cross-region replication; and
deleting the snapshot by the target file system at the end of the second cross-region replication.

### Claim 18 (depends on 15)

The system of claim 15, wherein the second operation comprises deleting the snapshot by the source file system without transferring the snapshot to the target file system.

### Claim 19 (depends on 15)

The system of claim 15, wherein the system is further caused to determine a second timing of generating the snapshot of the source file system.

### Claim 20 (depends on 19)

The system of claim 19, wherein the system is further caused to transfer the generated snapshot to the target file system during the second cross-region replication in accordance with the second timing of the snapshot generation being determined to be during the first cross-region replication and in accordance with the timing of the snapshot deletion request being determined to be after the second cross-region replication.
