Point in time rollback and un-installation of software

• US 8,719,809 B2
• Filed: 12/22/2006
• Issued: 05/06/2014
• Est. Priority Date: 12/22/2006
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Gokhale, Parag
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): GOORAY, MARK A
• Application Number:
  US11/615,378
• Publication Number:
  US 20080155526A1
• Time in Patent Office: 2,692 Days
• Field of Search: None
• US Class Current: 717/170
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 8/62 Uninstallation

Abstract

Systems and methods for providing point in time rollback and un-installation of software within computer networks are disclosed. The system comprises a plurality of elements which perform data migration operations and a rollback and un-installation manager which monitors the elements and software installations. Upon detection of a software installation, the rollback and un-installation manager identifies the installation, obtains records of the computer network files modified by the installation, and causes copies of the modified files to be generated. At future dates, the records and copies are utilized to return the computer network to a state prior to the installation. In this manner the risks associated with removal single or multiple updates are greatly reduced.

Claims

1. A method of updating a data storage system such that the updated data storage system can be rolled back to a pre-update state, the method comprising:

automatically detecting one or more software upgrades,

sequentially intercepting update commands associated with each software upgrade and identifying at least some components and files in primary storage of a data storage system that are to be updated;

delaying execution of the update commands associated with identified components and files;

automatically copying with one or more computer processors at least one or more of the identified components in the data storage system as well as at least one or more of the identified files in the data storage system existing at a pre-update state to create copied components and files prior to execution of the update commands that update the identified components and files in the data storage system such that at least some of the updated components and files can be rolled back to the pre-update state;

storing information in a rollback data structure about the copied components and files existing at the pre-update state, the rollback data structure comprising at least storage locations and copy times associated with the copied components and files existing at the pre-update state, the rollback data structure stored in the primary storage of the data storage system;

allowing execution of each update command after automatically copying the identified components and files existing at the pre-update state;

maintaining data migration parameters regarding copies of the components and files existing at the pre-update state, wherein the data migration parameters define a time period for retaining the copies of the components and files existing at the pre-update state in primary storage before migrating to secondary storage;

when migrating the copied files and components to secondary memory, updating the storage locations in the rollback data structure to identify secondary storage locations in secondary memory;

receiving a point-in-time request due to problems encountered in association with an upgrade, to roll back the one or more software updates to a point in time, to the pre-update state existing at a prior time and date;

automatically identifying which of the one or more software upgrades occurred after the point in time based at least in part on the copy times in the rollback data structure;

automatically rolling back the one or more software upgrades to the prior time and date that wherein automatically rolling back the one or more software upgrades restores the identified components and files existing at the pre-update state associated with the point-in-time request,

wherein the data migration parameters further define automatic deletion of migrated copies of the components and files existing at the pre-update state after a designated number of upgrades are known to be good.

2. The method of claim 1, wherein the components comprise at least one of executable files, application files, data files, graphics files, configuration files, binary files, device drivers, backup files, archive files, text files, media files, archive files, temporary files, and dynamic link library files.

3. The method of claim 1, further comprising copying at least some components prior to performing a second update such that the components can be rolled back to a state that predates either the second update or the first update.

4. The method of claim 1, wherein the components that are to be updated are identified by examining the received update prior to performing the update.

5. The method of claim 4, wherein the components to be updated are contained within a data structure provided by the received update.

6. A system for point in time rollback and un-installation of updates within a data storage system, comprising:

a plurality of elements which perform at least data storage operations; and

a rollback and un-installation manager comprising computer hardware, the rollback and un-installation manager configured to;

automatically detect one or more software upgrades;

sequentially intercept update commands associated with each software upgrade and identify components and files in primary storage of a data storage system that are to be updated;

delay execution of the update commands associated with identified components and files;

automatically copy at least one or more of the identified components and files existing at a pre-update state to create copied components and files prior to execution of the update commands such that at least some of the updated components and files can be rolled back to the pre-update state;

store information in a rollback data structure about the copied components and files existing at the pre-update state, the rollback data structure comprising at least storage locations and copy times associated with the copied components and files existing at the pre-update state, the rollback data structure stored in the primary storage of the data storage system;

allow execution of each update command after automatically copying the identified components and files existing at the pre-update state;

a data migration system comprising computer hardware, the data migration system configured to;

maintain data migration parameters regarding copies of the components and files existing at a pre-update state, wherein the data migration parameters define a time period for retaining the copies of the components and files existing at the pre-update state in primary storage before migrating to secondary storage;

when migrating the copied files and components to secondary memory, update the storage locations in the rollback data structure to identify secondary storage locations in secondary memory;

wherein in response to a point-in-time request due to problems encountered in association with an upgrade, to roll back the one or more software updates to a point in time, to the pre-update state existing at a prior time and date, the rollback and un-installation manager is further configured to;

automatically identify which of the one or more software upgrades occurred after the point in time based at least in part on the copy times in the rollback data structure;

automatic roll back of the one or more software upgrades to the prior time and date wherein the automatic roll back of the one or more software upgrades restores the identified components and files existing at the pre-update state associated with the point-in-time request,

wherein the data migration parameters further define automatic deletion of migrated copies of the components and files existing at the pre-update state after a designated number of upgrades are known to be good.

7. The system of claim 6, further comprising at least one of a storage manager, media agent, client computer, and storage media.

8. The system of claim 6, wherein the components comprise at least one of executable files, application files, data files, graphics files, configuration files, binary files, device drivers, backup files, archive files, text files, media files, archive files, temporary files, and dynamic link library files.

9. The system of claim 6, wherein the components that are to be updated are identified by examining the received update prior to performing the update.

10. The system of claim 9, wherein the components to be updated are contained within a data structure provided by the received update.

11. The system of claim 9, wherein the components comprise at least one of a storage manager, media agent, client computer, and storage media.

12. The system of claim 9, wherein the components comprise at least one of executable files, application files, data files, graphics files, configuration files, binary files, device drivers, backup files, archive files, text files, media files, archive files, temporary files, and dynamic link library files.

13. A rollback and un-installation system comprising:

means for automatically detecting one or more software upgrades;

means for sequentially intercepting update commands associated with each software upgrade and identifying at least some components and files in a data storage system that are to be updated;

means for delaying execution of the update commands associated with identified components and files;

means for automatically copying with one or more computer processors at least some of the identified components and files of the software application and copying at least some of the identified components and files existing at the pre-update state to create copied components and files prior to execution of the update commands that update the identified components and files in the data storage system such that at least some of the updated components and files can be rolled back to the pre-update state;

means for storing information in a rollback data structure about the copied components and files existing at the pre-update state, the rollback data structure comprising at least storage locations and copy times associated with the copied components and files existing at the pre-update state, the rollback data structure stored in the primary storage of the data storage system;

means for allowing execution of each update command after automatically copying the identified components and files existing at the pre-update state;

means for maintaining data migration parameters regarding copies of the components and files existing at the pre-update state, wherein the data migration parameters define a time period for retaining the copies of the components and files existing at the pre-update state in primary storage before migrating to secondary storage; and

when migrating the copied files and components to secondary memory, means for updating the storage locations in the rollback data structure to identify secondary storage locations in secondary memory;

means for receiving a point-in-time request due to problems encountered in association with an upgrade, to roll back the one or more software updates to a point in time, to the pre-update state existing at a prior time and date;

means for automatically identifying which of the one or more software upgrades occurred after the point in time based at least in part on the copy times in the rollback data structure;

means for automatically rolling back the one or more software upgrades to the prior time and date wherein automatically rolling back the one or more software upgrades restores the identified components and files existing at the pre-update state associated with the point-in-time request,

wherein the data migration parameters further define automatic deletion of migrated copies of the components and files existing at the pre-update state after a designated number of upgrades are known to be good.