Controlling computer storage systems

• US 8,185,779 B2
• Filed: 05/30/2008
• Issued: 05/22/2012
• Est. Priority Date: 06/27/2006
• Status: Active Grant

• Current Assignee: GlobalFoundries, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Devarakonda, Murthy V., Magoutis, Konstantinos, Vogl, Norbert George, Voruganti, Kaladhar
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): TRUONG, LOAN
• Application Number:
  US12/130,216
• Publication Number:
  US 20080228687A1
• Time in Patent Office: 1,453 Days
• Field of Search: 714/13, 714/6.2, 714/6.22
• US Class Current: 714/13
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 2211/1004 Adaptive RAID, i.e. RAID system adapts to changing circumstances, e.g. RAID1 becomes RAID5 as disks fill up

Abstract

Goal-based availability and change management are handled over groups of heterogeneous storage controllers. Probabilistic and deterministic methods are employed to determine the allocation and placement of storage volumes to storage controllers, as well as the degree of data redundancy necessary to achieve data availability goals The probabilistic methods can take into account past observations of controller availability, and operator beliefs, as well as the state of storage controller configuration, in coming up with a probabilistic estimate of future availability.

Claims

1. A method for controlling a computer storage system, comprising the steps of:

obtaining deterministic component availability information pertaining to said system;

obtaining probabilistic component availability information pertaining to said system;

checking for violation of availability goals based on both said deterministic component availability information and said probabilistic component availability information;

determining replication parameters, responsive to said checking indicating a violation of said availability goals; and

placing a set of storage volumes on a set of storage controllers, wherein said placement satisfies said availability goals, said placing comprising;

determining an initial placement of said storage volumes on said storage controllers based on capacity and performance goals; and

replicating said storage volumes, responsive to said availability goals.

2. The method of claim 1, further comprising the additional step of maintaining a current status, responsive to said checking indicating no violation of said availability goals.

3. The method of claim 1, wherein said replication parameters comprise at least how to replicate and where to replicate.

4. The method of claim 1, wherein said obtaining deterministic component availability information pertaining to said system comprises obtaining a request for change, further comprising the additional step of obtaining an estimated replication time.

5. The method of claim 4, further comprising the additional step of taking said estimated replication time into account in evaluating said request for change.

6. The method of claim 5, wherein said taking into account comprises:

determining whether sufficient time is available to replicate to accommodate said request for change; and

responsive to said determining step indicating that sufficient time is not available, rejecting said request for change.

7. The method of claim 5, wherein said taking into account comprises:

determining whether sufficient time is available to replicate to accommodate said request for change; and

responsive to said determining step indicating that sufficient time is not available, searching for an alternative plan to accommodate said request for change.

8. The method of claim 5, wherein said taking into account comprises:

determining whether sufficient time is available to replicate to accommodate said request for change; and

responsive to said determining step indicating that sufficient time is available, developing a change plan.

9. The method of claim 8, wherein said change plan comprises:

preparation information indicative of replica locations, relationships, and timing.

10. The method of claim 9, wherein said change plan further comprises:

execution information indicative of replication performance; and

failover detection information indicative of how to execute necessary failover actions no later than a time of an action associated with said request for change.

11. The method of claim 10, wherein said change plan further comprises:

completion information indicative of replication relationship maintenance and discard, and

information indicative of how to execute necessary failback actions no earlier than a time of another action associated with said request for change.

12. A method for controlling a computer storage system, comprising the steps of:

obtaining a request for change due to a violation of availability goals based on both said deterministic component availability information and said probabilistic component availability information;

obtaining an estimated replication time associated with a replication to accommodate said change;

determining whether sufficient time is available to replicate to accommodate said request for change; and

taking said estimated replication time into account in evaluating said request for change.

13. The method of claim 12, wherein said taking into account comprises

responsive to said determining step indicating that sufficient time is not available, rejecting said request for change.

14. The method of claim 12, wherein said taking into account comprises

responsive to said determining step indicating that sufficient time is not available, searching for an alternative plan to accommodate said request for change.

15. The method of claim 12, wherein said taking into account comprises

responsive to said determining step indicating that sufficient time is available, developing a change plan.

16. A computer program product comprising a tangible computer readable recordable storage medium having computer useable program code for controlling a computer storage system, said computer program product including:

computer useable program code for obtaining deterministic component availability information pertaining to said system;

computer useable program code for obtaining probabilistic component availability information pertaining to said system;

computer useable program code for checking for violation of availability goals based on both said deterministic component availability information and said probabilistic component availability information;

computer useable program code for determining replication parameters, responsive to said checking indicating a violation of said availability goals; and

computer useable program code for placing a set of storage volumes on a set of storage controllers, wherein said placement satisfies said availability goals, said placing comprising;

determining an initial placement of said storage volumes on said storage controllers based on capacity and performance goals; and

replicating said storage volumes, responsive to said availability goals.

17. The computer program product of claim 16, wherein said computer useable program code for obtaining deterministic component availability information pertaining to said system comprises computer useable program code for obtaining a request for change, further comprising:

computer useable program code for obtaining an estimated replication time; and

computer useable program code for taking said estimated replication time into account in evaluating said request for change.

18. A computer program product comprising a tangible computer readable recordable storage medium having computer useable program code for controlling a computer storage system, said computer program product including:

computer useable program code for obtaining a request for change due to a violation of availability goals based on both said deterministic component availability information and said probabilistic component availability information;

computer useable program code for obtaining an estimated replication time associated with a replication to accommodate said change;

computer useable program code for determining whether sufficient time is available to replicate to accommodate said request for change; and

computer useable program code for taking said estimated replication time into account in evaluating said request for change.

19. The computer program product of claim 18, wherein said computer useable program code for taking said estimated replication time into account comprises:

computer useable program code for determining whether sufficient time is available to replicate to accommodate said request for change; and

computer useable program code for rejecting said request for change, responsive to said computer useable program code for determining indicating that sufficient time is not available.

20. A method for controlling a computer storage system, comprising the steps of:

obtaining deterministic component availability information pertaining to said system, said obtaining said deterministic component availability information pertaining to said system comprising obtaining a request for change;

obtaining probabilistic component availability information pertaining to said system;

checking for violation of availability goals based on both said deterministic component availability information and said probabilistic component availability information;

determining replication parameters, responsive to said checking indicating a violation of said availability goals;

obtaining an estimated replication time;

taking said estimated replication time into account in evaluating said request for change, said taking into account comprising;

determining whether sufficient time is available to replicate to accommodate said request for change; and

responsive to said determining step indicating that sufficient time is available, developing a change plan, said change plan comprising;

preparation information indicative of replica locations, relationships, and timing;

execution information indicative of replication performance;

failover detection information indicative of how to execute necessary failover actions no later than a time of an action associated with said request for change;

completion information indicative of replication relationship maintenance and discard, and

information indicative of how to execute necessary failback actions no earlier than a time of another action associated with said request for change; and

placing a set of storage volumes on a set of storage controllers, responsive to said availability goals, said placing comprising;

determining an initial placement of said storage volumes on said storage controllers based on capacity and performance goals; and

replicating said storage volumes, responsive to said availability goals.