POINT IN TIME ROLLBACK AND UN-INSTALLATION OF SOFTWARE

• US 20080155526A1
• Filed: 12/22/2006
• Published: 06/26/2008
• Est. Priority Date: 12/22/2006
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Gokhale, Parag
• Granted Patent: US 8,719,809 B2
• Time in Patent Office: Days
• US Class Current: 717/169
• 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:

identifying at least some components in a data storage system that are to be updated;

copying at least some of the components of the data storage system prior to updating such that at least some of the updated components can be rolled back to a pre-update state;

updating the components of the data storage system;

receiving a rollback request to roll the data storage system back to a pre-update state; and

automatically rolling back the updated components of the storage system to the pre-update state by using copies of the components.

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. The method of claim 4, wherein the commands issued by the received update are examined and then executed sequentially in order to identify the components that are to be updated.

7. The method of claim 4, wherein the commands issued by the received update are examined in batch prior to their execution in order to identify the components that are to be updated.

8. A method of rolling back a software application to a previous state comprising:

identifying at least some components in a software application that are to be updated;

copying at least some of the components of the software application prior to updating such that at least some of the updated components can be rolled back to a pre-update state;

updating the components of the software application; and

rolling back the updated components of the software application to a pre-update state by automatically reinstalling copies of the components in response to a rollback request.

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

10. The method of claim 8, 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.

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

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

13. The method of claim 11, wherein the commands issued by the received update are examined and then executed sequentially in order to identify the components that are to be updated.

14. The method of claim 11, wherein the commands issued by the received update are examined in batch prior to their execution in order to identify the components that are to be updated.

15. 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 that monitors an update received by the data storage system;

wherein the rollback and un-installation manager identifies the components to be modified by the update, and wherein at least a portion of the components to be modified by the update are stored for future restoration by the rollback and un-installation manager.

16. The system of claim 15, wherein the elements comprise at least one of a storage manager, media agent, client computer, and storage media.

17. The system of claim 15, 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.

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

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

20. The system of claim 18, wherein the commands issued by the received update are examined and then executed sequentially in order to identify the components that are to be updated.

21. The system of claim 18, wherein the commands issued by the received update are examined in batch prior to their execution in order to identify the components that are to be updated.

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

24. The system of claim 21, 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.

22. A rollback and un-installation system comprising:

means for identifying at least some components in a software application that are to be updated;

means for copying at least some of the components of the software application prior to updating such that at least some of the updated components can be rolled back to a pre-update state;

means for updating the components of the software application; and

means for rolling back the updated components of the software application to a pre-update state by automatically reinstalling copies of the components in response to a rollback request.