# US 2023/0266908 A1 · Uniform Model For Distinct Types Of Data Replication

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

- Number: US 2023/0266908 A1
- Document ID: US20230266908A1
- Status: Published application
- Kind: A1
- Application number: 18/297,452
- Filed: 2023-04-07
- Published: 2023-08-24
- Earliest claimed: 2019-09-13
- Assignees: Pure Storage, Inc.
- Applicants: Pure Storage, Inc.
- Inventors: DAVID GRUNWALD; THOMAS GILL; RONALD KARR; MATTHEW FAY; LUKE PAULSEN; JOHN COLGROVE
- Web page: https://patentgrep.com/patent/US20230266908A1

## CPC

- G06F 3/065: {Replication mechanisms}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 3/0614: {Improving the reliability of storage systems}
- G06F 3/0616: {in relation to life time, e.g. increasing Mean Time Between Failures [MTBF]}
- G06F 3/0656: {Data buffering arrangements}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F 11/108: {Parity data distribution in semiconductor storages, e.g. in SSD}
- G06F 11/1435: {using file system or storage system metadata}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1458: {Management of the backup or restore process}
- G06F 11/1484: {involving virtual machines}
- 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/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/1844: {Management specifically adapted to replicated file systems}
- G06F 16/1858: {Parallel file systems, i.e. file systems supporting multiple processors}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/383: using metadata automatically derived from the content
- 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)

## Abstract

A uniform model for distinct types of data replication, including receiving, at a source data repository, an update to a dataset; generating, based on the update to the dataset, both metadata describing the update to the dataset and also a metadata representation of the dataset; and initiating, based on the same metadata describing the update to the dataset and also based on the same metadata representation of the dataset, either a first type of data replication or a second type of data replication from among a plurality of types of data replication.

## Claims

### Claim 1

A method comprising:
receiving an update to a dataset that is being replicated with a first type of replication;
generating, based on the received update, a metadata representation of the dataset that can be shared between different types of replication, the metadata representation including one or more logical representations of portions of the dataset; and
based on the metadata representation created during the first type of replication, replicating the update using a second type of replication.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first type of data replication is a distinct type of data replication from the second type of data replication.

### Claim 3 (depends on 2)

The method of claim 2, wherein the first type of data replication and the second type of data replication are among a plurality of types of data replication, including synchronous replication, configurable asynchronous data replication, periodic data replication, snapshot-based data replication, continuous data replication, and a combination of configurable asynchronous data replication and dynamically determined snapshot updates.

### Claim 4 (depends on 3)

The method of claim 3, wherein the dynamically determined snapshot updates are based on asynchronous data replication not occurring with sufficient frequency to prevent surpassing a backlog threshold.

### Claim 5 (depends on 4)

The method of claim 4, wherein subsequent to sending one or more snapshot updates from a source data repository to a target data repository, asynchronous data replication continues from the source data repository to the target data repository without snapshots while the data replication occurs with sufficient frequency to prevent surpassing the backlog threshold.

### Claim 6 (depends on 1)

The method of claim 1, wherein the metadata references content identifiers on a respective source data repository and target data repository, wherein the content identifiers are a basis for avoiding transfer of data based on identifying content on the target data repository that is the same as content on the source data repository, and wherein content is identified as being the same based on sharing a common definition for respective content identifiers on the source data repository and the target data repository.

### Claim 7 (depends on 1)

The method of claim 1, wherein the logical representations include metadata object nodes, wherein leaf nodes include pointers to respective data objects.

### Claim 8 (depends on 1)

The method of claim 1, wherein the metadata includes one or more metadata objects that are representative of content of the dataset as distinct from one or more content identifiers used to identify the dataset.

### Claim 9

A storage system that includes a computer memory and a computer processor, the computer memory including program instructions that, when executed by the computer processor, cause the storage system to carry out the steps of:
receiving an update to a dataset that is being replicated with a first type of replication;
generating, based on the received update, a metadata representation of the dataset that can be shared between different types of replication, the metadata representation including one or more logical representations of portions of the dataset; and
based on the metadata representation created during the first type of replication, replicating the update using a second type of replication.

### Claim 10 (depends on 9)

The storage system of claim 9, wherein the first type of data replication is distinct type of data replication from the second type of data replication.

### Claim 11 (depends on 10)

The storage system of claim 10, wherein the first type of data replication and the second type of data replication are among a plurality of types of data replication, including synchronous replication, configurable asynchronous data replication, periodic data replication, snapshot-based data replication, continuous data replication, and a combination of configurable asynchronous data replication and dynamically determined snapshot updates.

### Claim 12 (depends on 11)

The storage system of claim 11, wherein the dynamically determined snapshot updates are based on asynchronous data replication not occurring with sufficient frequency to prevent surpassing a backlog threshold.

### Claim 13 (depends on 12)

The storage system of claim 12, wherein subsequent to sending one or more snapshot updates from a source data repository to a target data repository, asynchronous data replication continues from the source data repository to the target data repository without snapshots while the data replication occurs with sufficient frequency to prevent surpassing the backlog threshold.

### Claim 14 (depends on 13)

The storage system of claim 13, wherein data and metadata included within a snapshot is excluded from subsequent data and metadata transfers in subsequent asynchronous data replication transfers from the source data repository to the target data repository.

### Claim 15 (depends on 9)

The storage system of claim 9, wherein the metadata describing the update to the dataset is included within an ordered log of metadata comprising one or more checkpoints.

### Claim 16 (depends on 9)

The storage system of claim 9, wherein the logical representations include metadata object nodes, wherein leaf nodes include pointers to respective data objects.

### Claim 17 (depends on 9)

The storage system of claim 9, wherein the metadata includes one or more metadata objects that are representative of content of the dataset as distinct from one or more content identifiers used to identify the dataset.

### Claim 18

An apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:
receiving an update to a dataset that is being replicated with a first type of replication;
generating, based on the received update, a metadata representation of the dataset that can be shared between different types of replication, the metadata representation including one or more logical representations of portions of the dataset; and
based on the metadata representation created during the first type of replication, replicating the update using a second type of replication.

### Claim 19 (depends on 18)

The apparatus of claim 18, wherein the logical representations include metadata object nodes, wherein leaf nodes include points to respective data objects.

### Claim 20 (depends on 18)

The apparatus of claim 18, wherein the metadata includes one or more metadata objects that are representative of content of the dataset as distinct from one or more content identifiers used to identify the dataset.
