Managing a deletion of a volume referenced by a snapshot of a consistency group

• US 10,241,869 B2
• Filed: 03/08/2017
• Issued: 03/26/2019
• Est. Priority Date: 03/08/2017
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Atia, Ohad, Avraham, Amalia, Harel, Ran, Marx, Alon
• Primary Examiner(s): Rossiter, Sean D
• Assistant Examiner(s): Choi, Charles J
• Application Number:
  US15/452,852
• Publication Number:
  US 20180260119A1
• Time in Patent Office: 748 Days
• Field of Search: None
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0614 Improving the reliability of storage systems
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0652 Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0673 Single storage device

Abstract

When a volume that was once associated with a consistency group and is to be deleted from the storage system, the to be deleted volume is designated as a ghost volume within the storage system, and the deletion of the ghost volume from the storage system is delayed until there are no snapshots that include a pointer to the ghost volume. The storage system may include a counter that counts the number of instances all volumes within a consistency group are pointed to or that counts the number of instances that only ghost volumes are pointed to. The storage system may reference this count to determine whether to immediately delete or delay the deletion of the volume from the storage system.

Claims

1. A method of managing a deletion of volume referenced by a snapshot of a consistency group, the method comprising:

designating a to-be deleted original volume as a ghost volume within a consistency group stored within a storage system, the consistency group, subsequent to the designation of the ghost volume, comprising the ghost volume and a plurality of original volumes;

identifying a preexisting point-in-time snapshot of the consistency group that existed prior to the designation of the ghost volume, the preexisting point-in-time snapshot, subsequent to the designation of the ghost volume, comprising a plurality of pointers that each point to a different one of the plurality of original volumes of the consistency group and an orphaned pointer that points to the ghost volume;

subsequent to the designation of the ghost volume, taking a present point-in-time snapshot of the consistency group, the present point-in-time snapshot consisting of a plurality of pointers that each point to a different one of the plurality of original volumes of the consistency group; and

preventing deletion of the ghost volume from the storage system until there are no point-in-time snapshots of the consistency group that comprise a orphaned pointer that points to the ghost volume.

2. The method of claim 1, further comprising:

receiving an instruction to delete the to-be deleted original volume from the storage system; and

deleting the preexisting point-in-time snapshot of the consistency group from the storage system.

3. The method of claim 1, wherein preventing deletion of the ghost volume from the storage system comprises:

determining a number of point-in-time snapshots of the consistency group that comprise a orphaned pointer that points to the ghost volume.

4. The method of claim 3, wherein determining the number of point-in-time snapshots of the consistency group that comprise an orphaned pointer that points to the ghost volume comprises:

incrementing applicable original volume snapshot count fields within a data structure when a point-in-time snapshot that comprises pointers that point to applicable original volumes is taken and stored within a snapshot repository; and

decrementing applicable original volume snapshot count fields within the data structure when a point-in-time snapshot that comprises pointers that point to applicable original volumes is deleted from the snapshot repository.

5. The method of claim 1, wherein designating the to-be deleted original volume as the ghost volume comprises:

setting a ghost volume bit associated with an address of the to-be deleted original volume to designate the to-be deleted original volume as the ghost volume.

6. The method of claim 1, wherein designating the to-be deleted original volume as the ghost volume comprises:

setting as active a ghost volume field within a data structure that tracks which original volumes are designated as ghost volumes to designate the to-be deleted original volume as the ghost volume.

7. The method of claim 1, wherein the ghost volume is:

a to-be deleted volume from the storage system;

that is or was associated with a consistency group that which snapshots exist within the storage system that contain a pointer that points to the to-be deleted volume;

is not deleted from the storage system until there are no point-in-time snapshots within the storage system that contain the pointer that points to the to-be deleted volume;

subsequent the designation as the ghost volume, is not snapped in future point-in-time snapshots of the associated consistency group;

is hidden from and not provided to a requesting computer when the computer reads the associated consistency group; and

is modifiable and accessible only by the storage system.

8. A computer program product for managing a deletion of a volume referenced by a snapshot of a consistency group, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions readable by a storage system to cause the storage system to:

designate a to-be deleted original volume as a ghost volume within a consistency group stored within the storage system, the consistency group, subsequent to the designation of the ghost volume, comprising the ghost volume and a plurality of original volumes;

identify a preexisting point-in-time snapshot of the consistency group that existed prior to the designation of the ghost volume, the preexisting point-in-time snapshot, subsequent to the designation of the ghost volume, comprising a plurality of pointers that each point to a different one of the plurality of original volumes of the consistency group and an orphaned pointer that points to the ghost volume;

subsequent to the designation of the ghost volume, take a present point-in-time snapshot of the consistency group, the present point-in-time snapshot consisting of a plurality of pointers that each point to a different one of the plurality of original volumes of the consistency group; and

prevent deletion of the ghost volume from the storage system until there are no point-in-time snapshots of the consistency group that comprise a orphaned pointer that points to the ghost volume.

9. The computer program product of claim 8, wherein the program instructions are further readable by the storage system to cause the storage system to:

receive an instruction to delete the to-be deleted original volume from the storage system; and

delete the preexisting point-in-time snapshot of the consistency group from the storage system.

10. The computer program product of claim 8, wherein the program instructions that cause the storage system to prevent deletion of the ghost volume from the storage system are further readable by the storage system to cause the storage system to:

determine a number of point-in-time snapshots of the consistency group that comprise a orphaned pointer that points to the ghost volume.

11. The computer program product of claim 10, wherein the program instructions that cause the storage system to determine the number of point-in-time snapshots of the consistency group that comprise the orphaned pointer that points to the ghost volume are further readable by the storage system to cause the storage system to:

increment applicable original volume snapshot count fields within a data structure when a point-in-time snapshot that comprises pointers that point to applicable original volumes is taken and stored within a snapshot repository; and

decrement applicable original volume snapshot count fields within the data structure when a point-in-time snapshot that comprises pointers that point to applicable original volumes is deleted from the snapshot repository.

12. The computer program product of claim 8, wherein the program instructions that cause the storage system to designate the ghost volume are further readable by the storage system to cause the storage system to:

set a ghost volume bit associated with an address of the to-be deleted original volume to designate the to-be deleted original volume as the ghost volume.

13. The computer program product of claim 8, wherein the program instructions that cause the storage system to designate the ghost volume are further readable by the storage system to cause the storage system to:

set as active a ghost volume field within a data structure that tracks which original volumes are designated as ghost volumes to designate the to-be deleted original volume as the ghost volume.

14. The computer program product of claim 8, wherein the ghost volume is:

a to-be deleted volume from the storage system;

that is or was associated with a consistency group that which snapshots exist within the storage system that contain a pointer that points to the to-be deleted volume;

is not deleted from the storage system until there are no point-in-time snapshots within the storage system that contain the pointer that points to the to-be deleted volume;

subsequent the designation as the ghost volume, is not snapped in future point-in-time snapshots of the associated consistency group;

is hidden from and not provided to a requesting computer when the computer reads the associated consistency group; and

is modifiable and accessible only by the storage system.

15. A storage system comprising:

a consistency group repository comprising a consistency group that comprises a plurality of original volumes and a designated ghost volume;

a snapshot repository comprising;

a first point-in-time snapshot of the consistency group taken prior to the designation of the ghost volume, the first point-in-time snapshot comprising a first plurality of pointers that each point to a different one of the plurality of original volumes and an orphaned pointer that points to the ghost volume;

a second point-in-time snapshot of the consistency group taken subsequent to the designation of the ghost volume, the second point-in-time snapshot consisting of a second plurality of pointers that each point to a different one of the plurality of original volumes; and

a snapshot manager stored upon a computer readable storage medium within the storage system that when called by the storage system, causes the storage system to prevent deletion of the ghost volume from the storage system until there are no point-in-time snapshots of the consistency group that comprise a orphaned pointer that points to the ghost volume.

16. The storage system of claim 15, wherein the snapshot manager further allows the storage system to receive an instruction to delete an original volume from the storage system and wherein the snapshot manager further causes the storage system to delete the first point-in-time snapshot of the consistency group.

17. The storage system of claim 15, wherein the snapshot manager further causes the storage system to determine a number of point-in-time snapshots of the consistency group that comprise an orphaned pointer that points to the ghost volume.

18. The storage system of claim 15, wherein the snapshot manager further causes the storage system to increment applicable original volume snapshot count fields within a data structure when a point-in-time snapshot that comprises pointers that point to applicable original volumes is taken and stored within a snapshot repository;

and to decrement applicable original volume snapshot count fields within the data structure when a point-in-time snapshot that comprises pointers that point to applicable original volumes is deleted from the snapshot repository.

19. The storage system of claim 15, wherein the snapshot manager further causes the storage system to set a ghost volume bit associated with an address of an original volume to active to designate the ghost volume.

20. The storage system of claim 15, wherein the ghost volume is:

a to-be deleted volume from the storage system;

that is or was associated with a consistency group that which snapshots exist within the storage system that contain a pointer that points to the to-be deleted volume;

is not deleted from the storage system until there are no point-in-time snapshots within the storage system that contain the pointer that points to the to-be deleted volume;

subsequent the designation as the ghost volume, is not snapped in future point-in-time snapshots of the associated consistency group;

is hidden from and not provided to a requesting computer when the computer reads the associated consistency group; and

is modifiable and accessible only by the storage system.