IP Library Granted Patent US 9,122,711
Granted Patent B1
US 9,122,711 · App. 13/479,936 · Granted Sep 1, 2015

Simplified system backup protection and recovery

Inventors: Mark J. Nicolini (Orlando, FL); Rick A. Wildes (Oviedo, FL); John E. Slawsky (Heathrow, FL); Check A. Sabjan (Sanford, FL); John W. Alexander (Redmond, WA); Kirk Freiheit (Lake Mary, FL); Eric W. Shaffer (Lake Mary, FL); Ynn-Pyng Tsaur (Oviedo, FL); Gregory R. Dowers, II (Lake Mary, FL)
Assignee: Symantec Corporation
G06F17/30289G06F17/30067G06F11/1451G06F11/1479
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,122,711
App. No.
13/479,936
Granted
Sep 1, 2015
Kind
B1
Abstract

A system, method, and medium for automatically identifying, protecting, and recovering the critical services and components of a server. A backup application detects a request to perform a backup operation. In response, the backup application performs a discovery process to identify the critical services and components of a server. The backup application includes a user interface to display the critical services and components to an administrator. The critical services and components are then backed up to a backup storage device. The collection of critical services and components can then be recovered to a target server when a recovery operation is needed.

Claims (77)

1. A method comprising:

executing a software application to perform a discovery process of a computing system;

identifying which components of a plurality of components of an operating system of the computing system are critical components, wherein critical components are components which are required for restoring the operating system to an operational state;

generating a user interface and displaying the critical components in a first section of the user interface and displaying non-critical components in a second section of the user interface;

comparing discovered critical components to an administrator's backup selections;

generating a message within the user interface if any critical components have been left out of the administrator's backup selections;

generating metadata to identify the critical components, wherein the metadata is considered a critical component; and

storing the metadata with the backup.

2. The method as recited in claim 1 , wherein the discovery process and backup are performed in response to receiving a request from a backup application to perform a backup of the critical components of the operating system of the computing system, and wherein the discovery process comprises:

accessing data which identifies a type of operating system being utilized by the computing system;

loading a configuration file with information on what types of components are critical for the operating system being utilized by the computing system;

querying a system volume, boot volume, and service control manager of the computing system to determine the critical components;

determining auto-start services for the operating system from the service control manager; and

determining a location of required executables from the service control manager.

3. The method as recited in claim 2 , the method further comprising:

determining a first component is a critical component during discovery of critical components;

detecting the first component is excluded from a backup request; and

overriding the exclusion and backing up the first component when performing a backup of the critical components.

4. The method as recited in claim 3 , the method further comprising showing that simplified disaster recovery is enabled in the user interface, wherein simplified disaster recovery signifies that critical components of the operating system of the computing system are being protected during any backup jobs that are performed.

5. The method as recited in claim 3 , wherein the critical components comprise one or more of system files, event logs, registry, windows internet name service, windows management instrumentation, component object model (COM+) class registration database, basic input output system (BIOS), extensible firmware interface (EFI), unified EFI, utility partition volumes, boot device, system services devices, and system state devices.

6. The method as recited in claim 5 , wherein the system state devices comprise one or more of an active directory, background intelligent transfer service, certificate services, cluster quorum, COM+ class registration database, dynamic host configuration protocol, event logs, file server resource manager, internet information services, microsoft (MS) search service, network policy server, performance counter, registry, remote storage, removable storage manager, shadow copy optimization, system files, system volume, task scheduler, terminal server licensing, terminal services gateway, volume shadow copy service (VSS) express writer, windows deployment services, windows internet name service, and windows management instrumentation.

7. The method as recited in claim 1 , the method further comprising:

receiving a request to perform an incremental backup of the computing system;

comparing critical component information from a current discovery process to critical component information from a previous discovery process; and

responsive to detecting a new critical component during the current discovery process, converting the incremental backup to a full backup for the new critical component.

8. A non-transitory computer readable storage medium comprising program instructions, wherein when executed the program instructions are operable to:

execute a software application to perform a discovery process of a computing system;

identify which components of a plurality of components of an operating system of the computing system are critical components, wherein critical components are components which are required for restoring the operating system to an operational state;

generate a user interface and display the critical components in a first section of the user interface and display non-critical components in a second section of the user interface;

compare discovered critical components to an administrator's backup selections;

generate a message within the user interface if any critical components have been left out of the administrator's backup selections;

generate metadata to identify the critical components, wherein the metadata is considered a critical component; and

store the metadata with the backup.

9. The non-transitory computer readable storage medium as recited in claim 8 , wherein the discovery process and backup are performed in response to receiving a request from a backup application to perform a backup of the critical components of the operating system of the computing system, and wherein the discovery process comprises:

accessing data which identifies a type of operating system being utilized by the computing system;

loading a configuration file with information on what types of components are critical for the operating system being utilized by the computing system;

querying a system volume, boot volume, and service control manager of the computing system to determine the critical components;

determining auto-start services for the operating system from the service control manager; and

determining a location of required executables from the service control manager.

10. The non-transitory computer readable storage medium as recited in claim 9 , wherein the program instructions are further operable to:

determine a first component is a critical component during discovery of critical components;

detect the first component is excluded from a backup request; and

override the exclusion and backing up the first component when performing a backup of the critical components.

11. The non-transitory computer readable storage medium as recited in claim 10 , wherein the program instructions are further operable to show that simplified disaster recovery is enabled in the user interface, wherein simplified disaster recovery signifies that critical components of the operating system of the computing system are being protected during any backup jobs that are performed.

12. The non-transitory computer readable storage medium as recited in claim 10 , wherein the critical components comprise one or more of system files, event logs, registry, windows internet name service, windows management instrumentation, component object model (COM+) class registration database, basic input output system (BIOS), extensible firmware interface (EFI), unified EFI, utility partition volumes, boot device, system services devices, and system state devices.

13. The non-transitory computer readable storage medium as recited in claim 12 , wherein the system state devices comprise one or more of an active directory, background intelligent transfer service, certificate services, cluster quorum, COM+ class registration database, dynamic host configuration protocol, event logs, file server resource manager, internet information services, microsoft (MS) search service, network policy server, performance counter, registry, remote storage, removable storage manager, shadow copy optimization, system files, system volume, task scheduler, terminal server licensing, terminal services gateway, volume shadow copy service (VSS) express writer, windows deployment services, windows internet name service, and windows management instrumentation.

14. The non-transitory computer readable storage medium as recited in claim 8 , the program instructions are further operable to:

receive a request to perform an incremental backup of the computing system;

compare critical component information from a current discovery process to critical component information from a previous discovery process; and

responsive to detecting a new critical component during the current discovery process, convert the incremental backup to a full backup for the new critical component.

15. A system comprising:

a computing system, wherein the computing system is configured to execute an operating system; and

a server, wherein the server is coupled to the computing system and configured to execute a backup application;

wherein the backup application is configured to:

execute a process to perform a discovery process of a computing system;

identify which components of a plurality of components of an operating system of the computing system are critical components, wherein critical components are components which are required for restoring the operating system to an operational state;

generate a user interface and display the critical components in a first section of the user interface and display non-critical components in a second section of the user interface;

compare discovered critical components to an administrator's backup selections;

generate a message within the user interface if any critical components have been left out of the administrator's backup selections;

generate metadata to identify the critical components, wherein the metadata is considered a critical component; and

store the metadata with the backup.

16. The system as recited in claim 15 , wherein the discovery process and backup are performed in response to receiving a request to perform a backup of the critical components of the operating system of the computing system, and wherein the discovery process comprises:

accessing data which identifies a type of operating system being utilized by the computing system;

loading a configuration file with information on what types of components are critical for the operating system being utilized by the computing system;

querying a system volume, boot volume, and service control manager of the computing system to determine the critical components;

determining auto-start services for the operating system from the service control manager; and

determining a location of required executables from the service control manager.

17. The system as recited in claim 16 , wherein the backup application is further operable to:

determine a first component is a critical component during discovery of critical components;

detect the first component is excluded from a backup request; and

override the exclusion and backing up the first component when performing a backup of the critical components.

18. The system as recited in claim 17 , wherein the backup application is further operable to show that simplified disaster recovery is enabled in the user interface, wherein simplified disaster recovery signifies that critical components of the operating system of the computing system are being protected during any backup jobs that are performed.

19. The system as recited in claim 17 , wherein the critical components comprise one or more of system files, event logs, registry, windows internet name service, windows management instrumentation, component object model (COM+) class registration database, basic input output system (BIOS), extensible firmware interface (EFI), unified EFI, utility partition volumes, boot device, system services devices, and system state devices.

20. The system as recited in claim 15 , wherein the backup application is further operable to:

receive a request to perform an incremental backup of the computing system;

compare critical component information from a current discovery process to critical component information from a previous discovery process; and

responsive to detecting a new critical component during the current discovery process, convert the incremental backup to a full backup for the new critical component.

Assignments (14)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 7, 2026
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 075763/0001 →
AMENDMENT NO. 1 TO PATENT SECURITY AGREEMENT Recorded Apr 8, 2025
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 070779/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2025
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 070335/0013 →
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2024
From: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC (F/K/A VERITAS US IP HOLDINGS LLC)
Reel/Frame 069712/0090 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069634/0584 →
SECURITY INTEREST Recorded Dec 9, 2024
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK. N.A.
Reel/Frame 069890/0001 →
ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Nov 25, 2024
From: BANK OF AMERICA, N.A., AS ASSIGNOR
To: ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE
Reel/Frame 069440/0084 →
TERMINATION AND RELEASE OF SECURITY IN PATENTS AT R/F 037891/0726 Recorded Nov 30, 2020
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: VERITAS US IP HOLDINGS, LLC
Reel/Frame 054535/0814 →
SECURITY INTEREST Recorded Aug 20, 2020
From: VERITAS TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 054370/0134 →
MERGER AND CHANGE OF NAME Recorded Apr 18, 2016
From: VERITAS US IP HOLDINGS LLC; VERITAS TECHNOLOGIES LLC
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 038455/0752 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 037891/0726 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037891/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2016
From: SYMANTEC CORPORATION
To: VERITAS US IP HOLDINGS LLC
Reel/Frame 037697/0412 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2012
From: NICOLINI, MARK J.; WILDES, RICK A.; SLAWSKY, JOHN E.; SABJAN, CHECK A.; ALEXANDER, JOHN W.; FREIHEIT, KIRK; SHAFFER, ERIC W.; TSAUR, YNN-PYNG ANKER; DOWERS, GREGORY R., II
To: SYMANTEC CORPORATION
Reel/Frame 028266/0577 →