Managing data in a storage system

• US 9,965,217 B2
• Filed: 01/25/2017
• Issued: 05/08/2018
• Est. Priority Date: 05/20/2013
• Status: Active Grant

• Current Assignee: Kaminario Limited
• Original Assignee: Kaminario Limited
• Inventors: Gordon, Eyal, Koren, Benny, Atzmony, Yedidia, Tal, Doron, Fienblit, Shachar, Steinberg, Ilan
• Primary Examiner(s): Ruiz, Aracelis
• Application Number:
  US15/415,274
• Publication Number:
  US 20170131913A1
• Time in Patent Office: 468 Days
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• 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/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0614 Improving the reliability of storage systems
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0665 at area level, e.g. provisioning of virtual or logical volumes
• 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/0671 In-line storage system
• CPC Class Codes: G06F 3/0683 Plurality of storage devices

Abstract

According to an aspect of the presently disclosed subject matter, there is provided a system for managing data in a storage system, the system including a storage layer which provides storage resource, and a snapshot layer that includes: a volume-version data structure, a chunk-version data structure and a IO handler.

Claims

1. A method of managing data in a storage system, comprising:

maintaining a volume-version data structure including logical unit (LU) volume entries for a LU volume and for snapshot volumes associated with the LU volume, wherein for each volume a respective volume identifier (ID) is kept, and for each snapshot a timestamp for a snapshot operation and an indication of a connection between a respective target volume and a source volume are kept;

maintaining a chunk-version data structure that is uniquely associated with a volume ID and a logical chunk address combination;

including in the chunk-version data structure one or more chunk-version data elements, each chunk version data element including a timestamp at a corresponding write to the respective logical chunk address in the respective volume and a pointer to storage resources associated with the chunk-version data element.

2. The method according to claim 1, wherein responsive to an instruction to create a new snapshot volume where a source of the snapshot is the LU volume or a snapshot volume that is associated with the LU volume, updating the volume-version data structure with:

a volume ID reference for the new snapshot-volume, an indication of a connection between the new snapshot-volume and the source, and a timestamp for the snapshot operation.

3. The method according to claim 2, wherein further in response to the instruction to create a new snapshot volume suspending IO to the source volume and incrementing a timestamp for the snapshot operation, and once the snapshot operation is complete, enabling IOs to the source volume to resume.

4. The method according to claim 1, further comprising responsive to receiving a write command in the storage system:

determining with which snapshot layer chunk the write command is associated; and

determining whether there is an existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated.

5. The method according to claim 4, wherein in case there is no existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated, generating a new chunk version data structure that is uniquely associated with the volume ID and with a logical chunk address of the snapshot layer chunk with which the write command is associated, and generating in the chunk-version data structure a chunk-version data element including a current timestamp and a pointer to storage resources that were allocated for this chunk-version data element.

6. The method according to claim 5, wherein the timestamp is a logical timestamp, and wherein the logical timestamp is incremented as a result of a volume create, a snapshot create or a revert operation.

7. The method according to claim 4, wherein in case there is an existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated, determining whether a new chunk version data element needs to be generated or whether an existing chunk version data element can be overwritten.

8. The method according to claim 7, wherein in case it is determined that a new chunk version data element needs to be generated, allocating storage resources for the new chunk version data element.

9. The method according to claim 8, further comprising requesting allocation of storage resources for the new chunk version data element from a free storage layer resources list.

10. The method according to claim 7, wherein in case it is determined that there is an existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated, and that an existing chunk version data element can be overwritten, writing write data of the write command in storage resources that were allocated to a last chunk version data element in the chunk version data structure.

11. The method according to claim 10, wherein in response to writing the write data of the write command in the storage resources that were allocated to the last chunk version data element in the chunk version data structure updating the timestamp of the last chunk version data element with a current timestamp.

12. The method according to claim 7, wherein determining whether a new chunk version data element needs to be generated or whether an existing chunk version data element can be overwritten, comprises:

reading a timestamp from a last chunk-version data element in the existing chunk-version data structure; and

in a case where there is no snapshot operation whose source is the LU volume or the snapshot volume of the snapshot layer chunk with which the write command is associated, or in a case where all snapshot operations whose source is the LU volume or the snapshot volume of the snapshot layer chunk with which the write command is associated have a timestamp that is earlier than or equal to the timestamp in the last chunk-version data element, determining that the last chunk-version data element in the existing chunk-version data structure can be overwritten.

13. The method of claim 1, further comprising:

(a) in response to receiving a read command at the storage system determining with which volume and with which snapshot layer chunk the read command is associated, initializing a read pointer with respective volume ID and logical chunk address, and initializing a time-marker according to a timestamp at receipt of the read command;

(b) determining whether there is a chunk-version data structure that is associated with a current read pointer;

(c1) if the condition in operation (b) is not met, determining whether there is a snapshot operation where the volume that is referenced in the write pointer is a target volume and whether the snapshot operation is associated with a timestamp that is not greater than the current time-marker; and

(d1) if the conditions in operation (c) are met updating the read pointer with a volume ID of a source volume of the snapshot operation, updating the time-marker with the timestamp for the snapshot operation—

1, and returning to operation (b).

14. The method according to claim 13, further comprising:

(c2) if the condition in operation (b) is met, determining whether in the chunk version data structure there is a chunk version data element whose timestamp is not greater than a current time-marker; and

(e1) if the condition in operation (c2) is met reading data from the storage resource referenced in a last chunk version element of the chunk version data structure.

15. The method according to claim 14, wherein in response to implementing operation (e1):

(f) determining whether a search was conducted for all logical blocks referenced in the read command;

(g1) and if the condition in operation (f) is met responding to the read command with data obtain in operation (e1) and including invalid data indication(s) for data blocks referenced in the read command for which valid data could not be obtained.

16. The method according to claim 15, wherein in case the condition in operation (f) is not met, returning to operation (c1).

17. The method according to claim 14, wherein in case the condition in operation (c2) is not met, returning to operation (c1).

18. A storage system, comprising:

a storage layer providing storage resources;

a snapshot layer comprising;

a volume-version data structure including LU volume entries for an LU volume and for snapshot volumes associated with the LU volume, wherein for each volume a respective volume ID is kept, and for each snapshot a timestamp for the snapshot operation and an indication of a connection between a respective target volume and a source volume are kept;

a chunk-version data structure that is uniquely associated with a volume ID and a logical chunk address combination;

an Input/Output (TO) handler that is configured to include in the chunk-version data structure one or more chunk-version data elements, each chunk version data element including a timestamp at a corresponding write to the respective logical chunk address in the respective volume and a pointer to storage resources associated with the chunk-version data element.

19. The storage system according to claim 18, wherein responsive to an instruction to create a new snapshot volume where a source of the snapshot is the LU volume or a snapshot volume that is associated with the LU volume, the IO handler is configured to update the volume-version data structure with:

a volume ID reference for the new snapshot-volume, an indication of a connection between the new snapshot-volume and the source, and a timestamp for the snapshot operation.

20. The storage system according to claim 18, further comprising responsive to receiving a write command in the storage system:

the IO handler is configured to determine with which snapshot layer chunk the write command is associated; and

the IO handler is configured to determine whether there is an existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated.

21. The storage system according to claim 20, wherein in case there is no existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated, the IO handler is configured to generate a new chunk version data structure that is uniquely associated with the volume ID and with a logical chunk address of the snapshot layer chunk with which the write command is associated, and to generate in the chunk-version data structure a chunk-version data element including a current timestamp and a pointer to storage resources that were allocated for this chunk-version data element.

22. The storage system according to claim 20, wherein in case there is an existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated, the IO handler is configured to determine whether a new chunk version data element needs to be generated or whether an existing chunk version data element can be overwritten.

23. The storage system according to claim 22, wherein the IO handler is configured to determine whether a new chunk version data element needs to be generated or whether an existing chunk version data element can be overwritten, by:

reading a timestamp from a last chunk-version data element in the existing chunk-version data structure; and

in a case where there is no snapshot operation whose source is the LU volume or the snapshot volume of the snapshot layer chunk with which the write command is associated, or in a case where all snapshot operations whose source is the LU volume or the snapshot volume of the snapshot layer chunk with which the write command is associated have a timestamp that is earlier than or equal to the timestamp in the last chunk-version data element, the IO handler is configured to determine that the last chunk-version data element in the existing chunk-version data structure can be overwritten.

24. The storage system of claim 18, wherein responsive to receiving a read command, the IO handler is further configured for:

(a) determining with which volume and with which snapshot layer chunk the read command is associated, initializing a read pointer with respective volume ID and logical chunk address, and initializing a time-marker according to a timestamp of the read command;

(b) determining whether there is a chunk-version data structure that is associated with a current read pointer;

(c1) if the condition in operation (b) is not met, determining whether there is a snapshot operation where the volume that is referenced in the write pointer is a target volume and whether the snapshot operation is associated with a timestamp that is not greater than the current time-marker; and

(d1) if the conditions in operation (c1) are met the IO handler is configured for;

updating the read pointer with a volume ID of a source volume of the snapshot operation, updating the time-marker with the timestamp for the snapshot operation—

1, and returning to operation (b).

25. The storage system according to claim 24, wherein in case the condition in operation (b) is met the IO handler is configured for:

(c2) determining whether in the chunk version data structure there is a chunk version data element whose timestamp is not greater than a current time-marker; and

(e1) if the condition in operation (c2) is met the IO handler is configured for reading data from the storage resource referenced in a last chunk version element of the chunk version data structure.

26. A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform a method of managing data in a storage system, comprising:

maintaining a volume-version data structure including LU volume entries for an LU volume and for snapshot volumes associated with the LU volume, wherein for each volume a respective volume ID is kept, and for each snapshot a timestamp for the snapshot operation and an indication of a connection between a respective target volume and a source volume are kept;

maintaining a chunk-version data structure that is uniquely associated with a volume ID and a logical chunk address combination; and

including in the chunk-version data structure one or more chunk-version data elements, each chunk version data element including a timestamp at a corresponding write to the respective logical chunk address in the respective volume and a pointer to storage resources associated with the chunk-version data element.

27. The program storage device of claim 26, wherein the program of instructions further comprising:

in response to receiving a write command determining with which snapshot layer chunk the write command is associated, and whether there is an existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated;

in case the write command is associated with an existing chunk-version data structure, reading a timestamp from a last chunk-version data element in the existing chunk-version data structure, and in a case where there is a snapshot operation whose source is a LU volume or a snapshot volume of the snapshot layer chunk with which the write command is associated and this snapshot operation is associated with a timestamp that is later than a timestamp of the last chunk-version data element, maintaining the last chunk-version data element and adding to the existing chunk-version data structure a new chunk version data element for the write command.

28. The program storage device of claim 26, wherein, wherein the program of instructions further comprising:

(a) in response to receiving a read command at the storage system determining with which volume and with which snapshot layer chunk the read command is associated, initializing a read pointer with respective volume ID and logical chunk address, and initializing a time-marker according to a timestamp of the read command;

(b) determining whether there is a chunk-version data structure that is associated with a current read pointer;

(c1) if the condition in operation (b) is not met, determining whether there is a snapshot operation where the volume that is referenced in the write pointer is a target volume and whether the snapshot operation is associated with a timestamp that is not greater than the current time-marker; and

(d1) if the conditions in operation (c) are met updating the read pointer with a volume ID of a source volume of the snapshot operation, updating the time-marker with the timestamp for the snapshot operation—

1, and returning to operation (b).

29. A computer program product comprising a non-transitory computer useable medium having computer readable program code embodied therein for managing data in a storage system, the computer program product comprising:

computer readable program code for causing the computer to maintain a volume-version data structure including LU volume entries for an LU volume and for snapshot volumes associated with the LU volume, wherein for each volume a respective volume ID is kept, and for each snapshot a timestamp for the snapshot operation and an indication of a connection between a respective target volume and a source volume are kept;

computer readable program code for causing the computer to maintain a chunk-version data structure that is uniquely associated with a volume ID and a logical chunk address combination; and

computer readable program code for causing the computer to include in the chunk-version data structure one or more chunk-version data elements, each chunk version data element including a timestamp at a corresponding write to the respective logical chunk address in the respective volume and a pointer to storage resources associated with the chunk-version data element.

30. The computer program product of claim 29, the computer program product further comprising:

computer readable program code that is responsive to receiving a write command in the storage system for causing the computer to determine with which snapshot layer chunk the write command is associated, and to determine whether there is an existing chunk version data structure which is associated with the snapshot layer chunk with which the write command is associated;

computer readable program code for causing the computer to determine whether the write command is associated with an existing chunk-version data structure, and in case the write command is associated with an existing chunk-version data structure, the computer readable program code is configured to cause a timestamp from a last chunk-version data element in the existing chunk-version data structure to be read, and in a case where there is a snapshot operation whose source is a LU volume or a snapshot volume of the snapshot layer chunk with which the write command is associated and this snapshot operation is associated with a timestamp that is later than a timestamp of the last chunk-version data element, the computer readable program code is configured to cause the last chunk-version data element to be maintained and a new chunk version data element for the write command to be added to the existing chunk-version data structure.