# US 2025/0165176 A1 · Testing Replica Data Using Modifiable Cloned Images

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

- Number: US 2025/0165176 A1
- Document ID: US20250165176A1
- Status: Published application
- Kind: A1
- Application number: 18/929,044
- Filed: 2024-10-28
- Published: 2025-05-22
- Earliest claimed: 2019-09-13
- Assignees: Pure Storage, Inc.
- Applicants: Pure Storage, Inc.
- Inventors: DAVID GRUNWALD; THOMAS GILL; RONALD KARR; JOHN COLGROVE; LARRY TOUCHETTE; LAWRENCE MERTES
- Web page: https://patentgrep.com/patent/US20250165176A1

## 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

Creating a modifiable cloned image of a dataset, including: generating, based on a dataset stored within a source data repository, a tracking copy of replica data on a target data repository; generating, after receiving an indication to begin accepting modifications to the tracking copy of the replica data, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data; and responsive to a storage operation directed to the target data repository, modifying the cloned image of the dataset without modifying the tracking copy of the replica data.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method comprising:
making available a clone, on a target data repository, of a tracking copy of replica data, wherein the tracking copy maintains updates to the replica data that are received from a source data repository; and
based on an instruction to modify the tracking copy, applying one or more modifications to the clone instead of applying the one or more modifications to the tracking copy.

### Claim 22 (depends on 21)

The method of claim 21 further comprising making the clone available in response to a promotion event promoting the tracking copy, wherein the promotion event includes a detected failure, an impending failure, a detected change in performance, or a user-initiated promotion event.

### Claim 23 (depends on 21)

The method of claim 21, wherein making the clone available further comprises generating a point-in-time image of the tracking copy.

### Claim 24 (depends on 23)

The method of claim 23, wherein the point-in-time image represents one or more updates to the replica data that are described in one or more lightweight checkpoints.

### Claim 25 (depends on 21)

The method of claim 21, wherein metadata describing one or more updates to a dataset at the source data repository references content identifiers on the 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 26 (depends on 25)

The method of claim 25, wherein metadata describing one or more updates to the dataset includes one or more ordered checkpoints that specify the one or more updates to the dataset.

### Claim 27 (depends on 26)

The method of claim 26, wherein a quantity of updates described by a given checkpoint depend on a configurable data replication setting.

### Claim 28 (depends on 26)

The method of claim 26, further comprising receiving, at the target data repository from the source data repository and independent from receiving metadata including the one or more checkpoints describing the one or more updates to the dataset, data corresponding to the one or more updates to the dataset.

### Claim 29 (depends on 28)

The method of claim 28, wherein generating the tracking copy of replica data on the target data repository includes applying, in order, the one or more updates corresponding to the data received from the source data repository.

### Claim 30 (depends on 21)

The method of claim 21 wherein the clone is modifiable without modifying the tracking copy of the replica data.

### Claim 31

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:
making available a clone, on a target data repository, of a tracking copy of replica data, wherein the tracking copy maintains updates to the replica data that are received from a source data repository; and
based on an instruction to modify the tracking copy, applying one or more modifications to the clone instead of applying the one or more modifications to the tracking copy.

### Claim 32 (depends on 31)

The storage system of claim 31, further comprising computer program instructions that, when executed by the computer processor, carry out the step of making the clone available in response to a promotion event promoting the tracking copy, wherein the promotion event includes a detected failure, an impending failure, a detected change in performance, or a user-initiated promotion event.

### Claim 33 (depends on 31)

The storage system of claim 31, wherein a replica link specifying a replica configuration changes direction of data replication from the target data repository to the source data repository.

### Claim 34 (depends on 31)

The storage system of claim 31, wherein a snapshot of the clone is created that describes modifications made to the clone by one or more storage operations directed to the target data repository from a host computing device.

### Claim 35 (depends on 31)

The storage system of claim 31, wherein metadata describing one or more updates to a dataset at the source data repository references content identifiers on the respective source data repository and target data repository, wherein the content identifiers are a basis 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 36 (depends on 35)

The storage system of claim 35, wherein the program instructions, when executed by the computer processor, further cause the storage system to carry out the steps of receiving, at the target data repository from the source data repository and independent from receiving metadata including checkpoints describing one or more updates to the dataset, data corresponding to the one or more updates to the dataset.

### Claim 37 (depends on 31)

The storage system of claim 31, wherein generating the tracking copy of replica data on the target data repository includes applying, in order, one or more updates corresponding to data received from the source data repository.

### Claim 38 (depends on 35)

The storage system of claim 35, wherein metadata describing one or more updates to the dataset at the source data repository includes one or more ordered checkpoints that specify the one or more updates to the dataset.

### Claim 39 (depends on 38)

The storage system of claim 38, wherein a quantity of updates described by a given checkpoint depend on a configurable data replication setting.

### Claim 40

A computer program product disposed on a non-transitory computer readable medium, wherein the computer program product includes computer program instructions that, when executed, carry out the steps of:
making available a clone, on a target data repository, of a tracking copy of replica data, wherein the tracking copy maintains updates to the replica data that are received from a source data repository; and
based on an instruction to modify the tracking copy, applying one or more modifications to the clone instead of applying the one or more modifications to the tracking copy.
