Method and system for restoring software

• US 9,606,787 B1
• Filed: 08/22/2014
• Issued: 03/28/2017
• Est. Priority Date: 12/30/2005
• Status: Active Grant

• Current Assignee: United Services Automobile Association
• Original Assignee: United Services Automobile Association
• Inventors: Weathersby, Richard Douglas, Black, Darren John
• Primary Examiner(s): Aponte, Francisco
• Application Number:
  US14/466,472
• Time in Patent Office: 949 Days
• Field of Search: 717168-178
• US Class Current: 1/1
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/64 Retargetable
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Method and system are disclosed for restoring multiple instances of a software application to a predetermined baseline state. The method/system of the invention creates a baseline template from a single correct or “golden” installation of the software application. The baseline template may then be deployed to restore previously used instances of the software application to a baseline state.

Claims

1. A computer-implemented method, comprising:

installing a software application on a host computing system, wherein said installation produces a file having a host computing system specific directory reference;

creating a baseline template of said software application, said baseline template comprising;

a first baseline file that includes a baseline version of a file of said software application, and

a second baseline file having a generic directory reference in place of a host computing system specific directory reference; and

uploading said baseline template to a user computing system containing an instance of said software application,

wherein a first instance file in said instance is replaced with said first baseline file, and wherein a second instance file in said instance is replaced with said second baseline file.

2. The method according to claim 1, further comprising transferring said baseline template to multiple computing systems and replacing said second baseline file having a generic directory reference with a file having a reference specific to each one of said multiple computing systems.

3. The method according to claim 1, wherein said software application comprises at least one of a patch, fix, modification, and customization needed for said software application.

4. The method according to claim 1, wherein said first baseline file is likely to be modified during a usages of said software application.

5. The method according to claim 1, wherein said replace is performed by executing one or more scripting routines.

6. The method according to claim 1, wherein said creating of said baseline template is performed by compressing said first baseline file and said second baseline file into at least one compressed file.

7. The method according to claim 1, wherein said creating of said baseline template is performed by backing up said first baseline file and said second baseline file into at least one backup file.

8. A system for restoring a software application to a baseline state on multiple computing systems, said system comprising:

a processor; and

memory coupled to the processor, said memory storing instructions that cause said processor executing the instructions to effectuate operations comprising;

installing a software application on a host computing system, wherein said installation produces a file having a host computing system specific directory reference;

creating a baseline template of said software application, said baseline template comprising;

a first baseline file that includes a baseline version of a file of said software application, and

a second baseline file having a generic directory reference in place of a host computing system specific directory reference; and

uploading said baseline template to a user computing system already containing an instance of said software application,

wherein a first instance file in said instance is replaced with said first baseline file, and wherein a second instance file in said instance is replaced with said second baseline file.

9. The system according to claim 8, said operations further comprising transferring said baseline template to multiple computing systems and replacing said second baseline file having a generic directory reference with a file having a reference specific to each one of said multiple computing systems.

10. The system according to claim 8, wherein said software application comprises at least one of a patch, fix, modification, and customization needed for said software application.

11. The system according to claim 8, wherein said first baseline file is likely to be modified during a usages of said software application.

12. The system according to claim 8, wherein creating said baseline template of said software application comprises compressing said first baseline file and said second baseline file into at least one compressed file.

13. The system according to claim 8, wherein creating said baseline template of said software application comprises backing up said first baseline file and said second baseline file for said software application into at least one backup file.

14. A non-transitory computer-readable medium comprising computer-readable instructions for restoring a software application to a baseline state on multiple computing systems, said computer-readable instructions comprising instructions for:

installing a software application on a host computing system, wherein said installation produces a file having a host computing system specific directory reference;

creating a baseline template of said software application, said baseline template comprising;

a first baseline file that includes a baseline version of a file of said software application, and

a second baseline file having a generic directory reference in place of a host computing system specific directory reference; and

uploading said baseline template to a user computing system containing an instance of said software application,

wherein a first instance file in said instance is replaced with said first baseline file, and wherein a second instance file in said instance is replaced with said second baseline file.

15. The non-transitory computer-readable medium according to claim 14, wherein said computer readable instructions further comprise instructions for transferring said baseline template to multiple computing systems and replacing said second baseline file having a generic directory reference with a file having a reference specific to each one of said multiple computing systems.

16. The non-transitory computer-readable medium according to claim 14, wherein said software application comprises at least one of a patch, fix, modification, and customization needed for said software application.

17. The non-transitory computer-readable medium according to claim 14, wherein said first baseline file is likely to be modified during a usages of said software application.

18. The non-transitory computer-readable medium according to claim 14, wherein said replace is performed by executing one or more scripting routines.

19. The non-transitory computer-readable medium according to claim 14, wherein said creating of said baseline template is performed by compressing said first baseline file and said second baseline file for said software application into at least one compressed file.