IP Library Granted Patent US 8,832,492
Granted Patent B1
US 8,832,492 · App. 13/751,005 · Granted Sep 9, 2014

Systems and methods for managing applications

Inventors: Joshua Kruck (St. Paul, MN); Aaron Christensen (Roseville, MN); Guido Westenberg (Columbia Heights, MN); Girish Jorapurkar (Woodbury, MN)
Assignee: Symantec Corporation
H04L47/70
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 8,832,492
App. No.
13/751,005
Filed
Jan 25, 2013
Granted
Sep 9, 2014
Kind
B1
Examiner
TRUONG, LOAN
Art Unit
2114
USPC
714/4
Abstract

A method for maintaining applications may include: (1) receiving a request to recover a first application, (2) identifying a first production topology of the first application that identifies a set of resources upon which the application depends, (3) maintaining a template for transforming the first production topology of the first application into a first recovery topology for the first application, the template comprising information for mapping the first production topology to the first recovery topology, (4) applying the template to the first production topology at a first point in time to create the first recovery topology, and (5) recovering the first application to a first computing system using the first recovery topology. Various other methods, systems, and computer-readable media are also disclosed herein.

Claims (69)

1. A computer-implemented method for managing applications, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

discovering a set of resources upon which an application depends;

generating an application topology that identifies the set of resources;

for each resource in the set of resources:

identifying a computer-executable command programmed to change a state of the resource;

including the computer-executable command in the application topology in a manner that associates the computer-executable command with the resource.

2. The computer-implemented method of claim 1 , further comprising:

receiving a request to change a state of the application;

changing the state of the application by:

traversing the application topology to identify a resource whose state needs to be changed;

reading, from the application topology, the computer-executable command programmed to change the state of the resource;

changing the state of the resource by executing the computer-executable command.

3. The computer-implemented method of claim 2 , wherein:

the request to change the state of the application comprises a request to recover the application;

changing the state of the resource comprises onlining the resource.

4. The computer-implemented method of claim 2 , wherein:

the request to change the state of the application comprises a request to shut down the application;

changing the state of the resource comprises offlining the resource.

5. The computer-implemented method of claim 2 , wherein traversing the application topology to identify the resource whose state needs to be changed comprises:

determining that the resource is not in a predetermined state.

6. The computer-implemented method of claim 1 , wherein at least one resource in the set of resources comprises a file system.

7. The computer-implemented method of claim 1 , wherein at least one resource in the set of resources comprises a database.

8. The computer-implemented method of claim 1 , wherein identifying the computer-executable command and including the computer-executable command in the application topology is performed while the application topology is being generated.

9. A system comprising:

a discovery module programmed to:

discover a set of resources upon which an application depends;

generate a first production topology that identifies the set of resources;

a command-identification module programmed to, for each resource in the set of resources:

identify a computer-executable command programmed to change a state of the resource;

include the computer-executable command in the first production topology in a manner that associates the computer-executable command with the resource;

a template-retention module programmed to maintain a template for transforming the first production topology of the application into a recovery topology for the application, the template comprising information for mapping the first production topology to the recovery topology;

a recovery module programmed to:

receive a request to recover the application;

identify the first production topology;

apply the template to the first production topology at a point in time to create the recovery topology;

recover the application to a computing system using the recovery topology;

at least one processor programmed to execute the discovery module, the command-identification module, the template-retention module, and the recovery module.

10. The system of claim 9 , wherein the template-retention module is programmed to maintain the template by:

storing a set of changes that map the first production topology to the recovery topology.

11. The system of claim 9 , wherein the template-retention module is programmed to:

retrieve the template;

present at least a portion of information stored in the template to a user via a graphical user interface;

receive, via the graphical user interface, input that modifies at least one value stored in the template.

12. The system of claim 9 , wherein:

the first production topology and the recovery topology comprise markup-language documents;

the template comprises a markup-language transformation document.

13. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

discover a set of resources upon which an application depends;

generate an application topology that identifies the set of resources;

for each resource in the set of resources:

identify a computer-executable command programmed to change a state of the resource;

include the computer-executable command in the application topology in a manner that associates the computer-executable command with the resource.

14. The non-transitory computer-readable medium of claim 13 , wherein the one or more computer-executable instructions are further programmed to cause the computing device to:

receive a request to change a state of the application;

change the state of the application by:

traversing the application topology to identify a resource whose state needs to be changed;

reading, from the application topology, the computer-executable command programmed to change the state of the resource;

changing the state of the resource by executing the computer-executable command.

15. The non-transitory computer-readable medium of claim 14 , wherein:

the request to change the state of the application comprises a request to recover the application;

the one or more computer-executable instructions are further programmed to change the state of the resource by onlining the resource.

16. The non-transitory computer-readable medium of claim 14 , wherein:

the request to change the state of the application comprises a request to shut down the application;

the one or more computer-executable instructions are further programmed to change the state of the resource by offlining the resource.

17. The non-transitory computer-readable medium of claim 14 , wherein the one or more computer-executable instructions are programmed to traverse the application topology to identify the resource whose state needs to be changed by:

determining that the resource is not in a predetermined state.

18. The non-transitory computer-readable medium of claim 13 , wherein at least one resource in the set of resources comprises a file system.

19. The non-transitory computer-readable medium of claim 13 , wherein at least one resource in the set of resources comprises a database.

20. The non-transitory computer-readable medium of claim 13 , wherein the one or more computer-executable instructions are programmed to identify the computer-executable command and include the computer-executable command in the application topology after the application topology is generated.

Assignments (13)
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 Jan 25, 2013
From: KRUCK, JOSHUA; CHRISTENSEN, AARON; WESTENBERG, GUIDO; JORAPURKAR, GIRISH
To: SYMANTEC CORPORATION
Reel/Frame 029699/0398 →
Continuity (1)
Continuation 12780056 · May 14, 2010