Remote data forwarding using a nocopy clone of a production volume
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.
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 R 1 on the first storage system and a backup storage volume R 2 on a second storage system;
adding the nocopy clone of the production volume to the primary storage volume R 1 of the remote data facility; and
replicating the nocopy clone of the production volume from the primary storage volume R 1 to the backup storage volume R 2 on the remote data facility;
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 R 2 ; and
after copying the respective backend allocation on the remote data facility, clearing the respective invalid flag.
2. 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.
3. 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.
4. 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 R 1 of the remote data facility.
5. 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 R 1 to the backup storage volume R 2 on the remote data facility comprises creation of a replica volume at the second storage system.
6. The non-transitory tangible computer readable storage medium of claim 5 , 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 R 2 .
7. 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 R 2 ; 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 R 1 .
8. 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 R 1 on the first storage system and a backup storage volume R 2 on a second storage system;
adding the nocopy clone of the production volume to the primary storage volume R 1 of the remote data facility; and
replicating the nocopy clone of the production volume from the primary storage volume R 1 to the backup storage volume R 2 on the remote data facility;
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 R 2 ; and
after copying the respective backend allocation on the remote data facility, clearing the respective invalid flag.
9. The method of claim 8 , 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.
10. The method of claim 8 , wherein the backend allocations are tracks of memory of a set of managed devices of a first storage system.
11. The method of claim 8 , 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 R 1 of the remote data facility.
12. The method of claim 8 , wherein the step of replicating the nocopy clone of the production volume from the primary storage volume R 1 to the backup storage volume R 2 on the remote data facility comprises creation of a replica volume at the second storage system.
13. The method of claim 12 , 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 R 2 .
14. The method of claim 8 , 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 R 2 ; 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 R 1 .