Data set version counting in a mixed local storage and remote storage environment

• US 20070106709A1
• Filed: 11/10/2005
• Published: 05/10/2007
• Est. Priority Date: 11/10/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Augenstein, Oliver, Zaremba, Christopher, Garimella, Neeta, Smith, James
• Granted Patent: US 7,617,260 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 2003/0697 device management, e.g. handlers, drivers, I/O schedulers
• CPC Class Codes: G06F 3/0601 Interfaces specially adapted for storage systems
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• 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/0653 Monitoring storage devices or systems
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Provided are a techniques for storing local versions of a data set. A first number that indicates how many local versions of the data set are to be stored in local storage given an amount of available local storage is received. It is determined whether a second number that indicates a total number of local versions of the data set that the local storage is capable of storing exceeds the first number. In response to determining that the second number exceeds the first number, the amount of local storage that is capable of storing the first number of local versions of the data set is used.

Claims

1. A method for storing versions of a data set, comprising:

receiving a first number that indicates how many local versions of the data set are to be stored in local storage given an amount of available local storage;

determining whether a second number that indicates a total number of local versions of the data set that the local storage is capable of storing exceeds the first number; and

in response to determining that the second number exceeds the first number, using the amount of local storage that is capable of storing the first number of local versions of the data set.

2. The method of claim 1, wherein a new policy construct is provided that defines how many local versions of the data set are to be stored in the local storage given the amount of available local storage.

3. The method of claim 1, further comprising:

overloading an existing policy construct that defines how many local versions of the data set are to be stored in the local storage given the amount of available local storage.

4. The method of claim 1, wherein the local storage is partitioned into one or more local storage containers.

5. The method of claim 4, wherein each local version of the data set is stored in one of the one or more local storage containers in the local storage.

6. The method of claim 4, wherein the amount of storage used is a third number of local storage containers and wherein the first number and third number are equivalent, further comprising:

using a backup policy to determine how to re-use the third number of storage containers when more than the first number of local versions are backed up with local backup operations.

7. The method of claim 6, wherein a local backup operation is an instant virtual copy operation, and wherein the backup policy indicates that a local storage container representing an oldest full copy is to be re-used as long as there are no other virtual instant copy operations on other local storage containers.

8. The method of claim 6, wherein a local backup operation is an incremental virtual copy operation and wherein a local storage container representing a backup copy that was established with an incremental relationship is re-used as long as there are no background copy processes or incremental refreshes still in effect on volumes in that local storage container.

9. The method of claim 1, further comprising:

in response to determining that the first number exceeds the second number, failing a backup operation for any local version of the data set exceeding the second number.

10. An article of manufacture for storing local versions of a data set, wherein the article of manufacture is capable of causing operations to be performed, and wherein the operations comprise:

receiving a first number that indicates how many local versions of the data set are to be stored in local storage given an amount of available local storage;

determining whether a second number that indicates a total number of local versions of the data set that the local storage is capable of storing exceeds the first number; and

in response to determining that the second number exceeds the first number, using the amount of local storage that is capable of storing the first number of local versions of the data set.

11. The article of manufacture of claim 10, wherein a new policy construct is provided that defines how many local versions of the data set are to be stored in the local storage given the amount of available local storage.

12. The article of manufacture of claim 10, wherein the operations further comprise:

overloading an existing policy construct that defines how many local versions of the data set are to be stored in the local storage given the amount of available local storage.

13. The article of manufacture of claim 10, wherein the local storage is partitioned into one or more local storage containers.

14. The article of manufacture of claim 13, wherein each local version of the data set is stored in one of the one or more local storage containers in the local storage.

15. The article of manufacture of claim 13, wherein the amount of storage used is a third number of local storage containers and wherein the first number and third number are equivalent, wherein the operations further comprise:

using a backup policy to determine how to re-use the third number of storage containers when more than the first number of local versions are backed up with local backup operations.

16. The article of manufacture of claim 15, wherein a local backup operation is an instant virtual copy operation, and wherein the backup policy indicates that a local storage container representing an oldest full copy is to be re-used as long as there are no other virtual instant copy operations on other local storage containers.

17. The article of manufacture of claim 15, wherein a local backup operation is an incremental virtual copy operation and wherein a local storage container representing a backup copy that was established with an incremental relationship is re-used as long as there are no background copy processes or incremental refreshes still in effect on volumes in that local storage container.

18. The article of manufacture of claim 10, wherein the operations further comprise:

in response to determining that the first number exceeds the second number, failing a backup operation for any local version of the data set exceeding the second number.

19. A system for storing local versions of a data set, comprising:

local storage; and

logic capable of performing operations, the operations comprising;

receiving a first number that indicates how many local versions of the data set are to be stored in local storage given an amount of available local storage;

determining whether a second number that indicates a total number of local versions of the data set that the local storage is capable of storing exceeds the first number; and

in response to determining that the second number exceeds the first number, using the amount of local storage that is capable of storing the first number of local versions of the data set.

20. The system of claim 19, wherein a new policy construct is provided that defines how many local versions of the data set are to be stored in the local storage given the amount of available local storage.

21. The system of claim 19, the operations further comprising:

overloading an existing policy construct that defines how many local versions of the data set are to be stored in the local storage given the amount of available local storage.

22. The system of claim 19, wherein the local storage is partitioned into one or more local storage containers.

23. The system of claim 22, wherein each local version of the data set is stored in one of the one or more local storage containers in the local storage.

24. The system of claim 22, wherein the amount of storage used is a third number of local storage containers and wherein the first number and third number are equivalent, the operations further comprising:

using a backup policy to determine how to re-use the third number of storage containers when more than the first number of local versions are backed up with local backup operations.

25. The system of claim 24, wherein a local backup operation is an instant virtual copy operation, and wherein the backup policy indicates that a local storage container representing an oldest full copy is to be re-used as long as there are no other virtual instant copy operations on other local storage containers.

26. The system of claim 24, wherein a local backup operation is an incremental virtual copy operation and wherein a local storage container representing a backup copy that was established with an incremental relationship is re-used as long as there are no background copy processes or incremental refreshes still in effect on volumes in that local storage container.

27. The system of claim 19, the operations further comprising:

in response to determining that the first number exceeds the second number, failing a backup operation for any local version of the data set exceeding the second number.