Autonomic rollback

• US 7,080,279 B2
• Filed: 12/03/2003
• Issued: 07/18/2006
• Est. Priority Date: 12/03/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jemiolo, Daniel Everett, Asare, Kwasi Addo, Barta, Attila, Huddleston, Richard D.
• Primary Examiner(s): Nguyen, Hiep T.
• Application Number:
  US10/727,011
• Publication Number:
  US 20050138468A1
• Time in Patent Office: 958 Days
• Field of Search: 711/156, 711/161, 711/162, 713/100, 713/187, 714/13, 714/15, 717/170, 717/177
• US Class Current: 714/13
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 8/62 Uninstallation

Abstract

An autonomic rollback system. An autonomic rollback system can include a registry configured to store meta-data specifying a contemporary state of a system of components. The system also can include a backup location configured to store a backup copy of the meta-data in the registry specifying a past state of the system of components prior to installing a new component. A monitor can be programmed to compare the operation of the system of components with a policy defining a nominal state of operation for the system of components. Finally, a rollback processor can be coupled to the registry and the backup location. Responsive to the monitor, the rollback processor can restore the registry to the past state when the monitor determines that the operation of the system of components falls outside the nominal state defined within the policy. Importantly, the system of components can reside within an application server.

Claims

1. An autonomic rollback system comprising:

a registry configured to store meta-data specifying a contemporary state of a system of components;

a backup location configured to store a backup copy of the meta-data in said registry specifying a past state of said system of components prior to installing a new component;

a monitor programmed to compare the operation of said system of components with a policy defining a nominal state of operation for said system of components; and

,

a rollback processor coupled to said registry and said backup location and responsive to said monitor, said rollback processor having programming for restoring said registry to said past state when said monitor determines that the operation of said system of components falls outside said nominal state defined within said policy.

2. The autonomic rollback system of claim 1, wherein said system of components resides within an application server.

3. A method for autonomically rolling back a system of components in response to detecting a failure condition in the system, the method comprising the steps of:

prior to installing a new component in the system, recording a backup copy of a registry storing contemporary system state information;

installing said new component in the system and recording a new state of the system in said registry;

monitoring the operation of the system and comparing said operation to a policy defining a nominal state of operation for the system; and

,

when the operation of the system exceeds said defined nominal state of operation in said policy, removing said installed new component and restoring said registry with said backup copy in order to rollback said new state to a state which had existed prior to said installation of said new component.

4. The method of claim 3, wherein said step of recording a backup copy of a registry comprises the steps of:

recording a listing of all installed components in the system;

defining dependencies between said installed components;

specifying resources within the system which are required by at least one of said installed components; and

,

identifying environmental parameter values established to support said installed components.

5. The method of claim 4, wherein said step of recording a new state in said registry comprises the steps of:

recording a listing of all installed components in the system including said new component;

defining dependencies between said installed components;

specifying resources within the system which are required by at least one of said installed components; and

,

identifying environmental parameter values established to support said installed components.

6. The method of claim 5, further comprising the steps of:

releasing resources no longer required by any of said installed components; and

,

resetting said environmental parameters to values specified within said restored registry.

7. The method of claim 3, further comprising the step of notifying a network administrator when the operation of the system exceeds said defined nominal state of operation in said policy.

8. A machine readable storage having stored thereon a computer program for autonomically rolling back a system of components in response to detecting a failure condition in the system, the computer program comprising a routine set of instructions for causing the machine to perform the steps of:

prior to installing a new component in the system, recording a backup copy of a registry storing contemporary system state information;

installing said new component in the system and recording a new state of the system in said registry;

monitoring the operation of the system and comparing said operation to a policy defining a nominal state of operation for the system; and

,

when the operation of the system exceeds said defined nominal state of operation in said policy, removing said installed new component and restoring said registry with said backup copy in order to rollback said new state to a state which had existed prior to said installation of said new component.

9. The machine readable storage of claim 8, wherein said step of recording a backup copy of a registry comprises the steps of:

recording a listing of all installed components in the system;

defining dependencies between said installed components;

specifying resources within the system which are required by at least one of said installed components; and

,

identifying environmental parameter values established to support said installed components.

10. The machine readable storage of claim 9, wherein said step of recording a new state in said registry comprises the steps of:

recording a listing of all installed components in the system including said new component;

defining dependencies between said installed components;

specifying resources within the system which are required by at least one of said installed components; and

,

identifying environmental parameter values established to support said installed components.

11. The machine readable storage of claim 10, further comprising the steps of:

releasing resources no longer required by any of said installed components; and

,

resetting said environmental parameters to values specified within said restored registry.

12. The machine readable storage of claim 8, further comprising the step of notifying a network administrator when the operation of the system exceeds said defined nominal state of operation in said policy.

13. An e-Registry configured to store meta-data specifying a contemporary state of a system of components and coupled to a backup location for storing a backup copy of said meta-data specifying a past state of said system of components prior to installing a new component, said e-Registry further comprising a communicative coupling to a monitor programmed to compare the operation of said system of components with a policy defining a nominal state of operation for said system of components, said e-Registry yet further comprising a communicative coupling to a rollback processor having programming for restoring said e-Registry to said past state when said monitor determines that the operation of said system of components falls outside said nominal state defined within said policy.

14. The e-Registry of claim 13, wherein said e-Registry is disposed within an application server.

15. The e-Registry of claim 13, wherein said e-Registry is disposed externally to a cluster of application servers, and wherein said system of components comprises a set of components deployed about a cluster of application servers.