# US 2021/0240568 A1 · Remote Data Forwarding Using a Nocopy Clone of a Production Volume

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

- Number: US 2021/0240568 A1
- Document ID: US20210240568A1
- Status: Published application
- Kind: A1
- Application number: 16/776,615
- Filed: 2020-01-30
- Published: 2021-08-05
- Earliest claimed: 2020-01-30
- Assignees: EMC IP Holding Company LLC
- Applicants: Emc IP Holding Company LLC
- Inventors: Akshay Kumar Srivastava; Sandeep Chandrashekhara; Michael Ferrari; Deepak Vokaliga; Darren Fernandes
- Web page: https://patentgrep.com/patent/US20210240568A1

## CPC

- G06F 11/1451: {by selection of backup contents}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 11/1456: {Hardware arrangements for backup}
- G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)}
- G06F 16/214: {Database migration support}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 11/1469: {Backup restoration techniques}
- 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 remote data facility includes a primary storage volume on a first storage system mirrored to a backup storage volume on a second storage system. A nocopy clone of a production volume is added to the primary storage volume. A define process is used to cause the tracks of the nocopy clone to point to backend allocations of tracks of memory of the production volume. As tracks of the nocopy clone are defined, corresponding flags are marked as invalid to cause data associated with the tracks to be replicated across the remote data facility to the backup storage volume. Incremental clones can be added to the primary storage volume, defined, and replicated on the remote data facility using the same process. Nocopy clones and target-less nocopy snapshots of the backup storage volume are used to restore the production volume using failover/failback mechanisms of the remote data facility.

## Claims

### Claim 1

A non-transitory tangible computer readable storage medium having stored thereon a computer program for remote data forwarding on a remote data facility, the computer program including a set of instructions which, when executed by a computer, cause the computer to perform a method comprising the steps of:
creating a nocopy clone of a production volume, the production volume having data stored on backend allocations of tracks of memory;
defining a remote data facility to include a primary storage volume R1 on the first storage system and a backup storage volume R2 on a second storage system;
adding the nocopy clone of the production volume to the primary storage volume R1 of the remote data facility; and
replicating the nocopy clone of the production volume from the primary storage volume R1 to the backup storage volume R2 on the remote data facility.

### Claim 2 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, wherein the nocopy clone of the production volume has pointers to the backend allocations of the tracks of memory but does not contain a copy of data contained in the tracks of memory.

### Claim 3 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, wherein the step of replicating comprises:
using a define process to cause tracks of the nocopy clone to point to the backend allocations of the tracks of memory of the production volume;
setting an invalid flag for each track of the nocopy clone in a first data structure associated with the remote data facility;
for each invalid flag in the first data structure, copying the respective backend allocation of memory on the remote data facility to the backup storage volume R2; and
after copying the respective backend allocation on the remote data facility, clearing the respective invalid flag.

### Claim 4 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, wherein the backend allocations are tracks of memory of a set of managed devices of a first storage system.

### Claim 5 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, further comprising:
creating a nocopy incremental clone of the production volume, the nocopy incremental clone containing pointers to tracks of the production volume that have changed since creation of a previous clone of the production volume; and
adding the nocopy incremental clone of the production volume to the primary storage volume R1 of the remote data facility.

### Claim 6 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, wherein the step of replicating the nocopy clone of the production volume from the primary storage volume R1 to the backup storage volume R2 on the remote data facility comprises creation of a replica volume at the second storage system.

### Claim 7 (depends on 6)

The non-transitory tangible computer readable storage medium of claim 6, further comprising:
creating a backup nocopy clone of the backup storage volume on the second storage system; and
linking the backup nocopy clone of the replica volume to the backup storage volume R2.

### Claim 8 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, further comprising:
creating a nocopy target-less snapshot of the backup storage volume on the second storage system;
linking the nocopy target-less snapshot to the backup storage volume R2; and
using a failover/failback mechanism of the remote data facility to restore data of the nocopy target-less snapshot to the primary storage volume R1.

### Claim 9

A method of remote data forwarding on a remote data facility, comprising:
creating a nocopy clone of a production volume, the production volume having data stored on backend allocations of tracks of memory;
defining a remote data facility to include a primary storage volume R1 on the first storage system and a backup storage volume R2 on a second storage system;
adding the nocopy clone of the production volume to the primary storage volume R1 of the remote data facility; and
replicating the nocopy clone of the production volume from the primary storage volume R1 to the backup storage volume R2 on the remote data facility.

### Claim 10 (depends on 9)

The method of claim 9, wherein the nocopy clone of the production volume has pointers to the backend allocations of the tracks of memory but does not contain a copy of data contained in the tracks of memory.

### Claim 11 (depends on 9)

The method of claim 9, wherein the step of replicating comprises:
using a define process to cause tracks of the nocopy clone to point to the backend allocations of the tracks of memory of the production volume;
setting an invalid flag for each track of the nocopy clone in a first data structure associated with the remote data facility;
for each invalid flag in the first data structure, copying the respective backend allocation of memory on the remote data facility to the backup storage volume R2; and
after copying the respective backend allocation on the remote data facility, clearing the respective invalid flag.

### Claim 12 (depends on 9)

The method of claim 9, wherein the backend allocations are tracks of memory of a set of managed devices of a first storage system.

### Claim 13 (depends on 9)

The method of claim 9, further comprising:
creating a nocopy incremental clone of the production volume, the nocopy incremental clone containing pointers to tracks of the production volume that have changed since creation of a previous clone of the production volume; and
adding the nocopy incremental clone of the production volume to the primary storage volume R1 of the remote data facility.

### Claim 14 (depends on 9)

The method of claim 9, wherein the step of replicating the nocopy clone of the production volume from the primary storage volume R1 to the backup storage volume R2 on the remote data facility comprises creation of a replica volume at the second storage system.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
creating a backup nocopy clone of the backup storage volume on the second storage system; and
linking the backup nocopy clone of the replica volume to the backup storage volume R2.

### Claim 16 (depends on 9)

The method of claim 9, further comprising:
creating a nocopy target-less snapshot of the backup storage volume on the second storage system;
linking the nocopy target-less snapshot to the backup storage volume R2; and
using a failover/failback mechanism of the remote data facility to restore data of the nocopy target-less snapshot to the primary storage volume R1.
