Systems and methods for disaster recovery of multi-tier applications

• US 8,984,325 B2
• Filed: 05/30/2012
• Issued: 03/17/2015
• Est. Priority Date: 05/30/2012
• Status: Active Grant

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Garai, Debasish, Gawali, Ashish
• Primary Examiner(s): Leibovich, Yair
• Application Number:
  US13/483,380
• Publication Number:
  US 20130326265A1
• Time in Patent Office: 1,021 Days
• Field of Search: 714/1, 714/6.3
• US Class Current: 714/1
• CPC Class Codes: G06F 11/203 using migration
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component

Abstract

A computer-implemented method for disaster recovery of multi-tier applications may include 1) identifying a multi-tier application that is provisioned with a plurality of production clusters at a production site, 2) identifying a disaster recovery site including a plurality of recovery clusters, 3) identifying, at the disaster recovery site, a failure of the multi-tier application at the production site, and 4) initiating, from the disaster recovery site, a migration of the multi-tier application from the production site to the disaster recovery site. Various other methods, systems, and computer-readable media are also disclosed.

Claims

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

identifying a multi-tier application that is provisioned with a plurality of production clusters at a production site;

identifying a disaster recovery site comprising a plurality of recovery clusters;

identifying, at the disaster recovery site, a failure of the multi-tier application at the production site;

initiating, from the disaster recovery site, a migration of the multi-tier application from the production site to the disaster recovery site, wherein the migration comprises;

identifying a dependency map of the multi-tier application;

migrating each tier of the multi-tier application when, according to the dependency map, no additional tier dependent on the tier remains to be migrated.

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

the multi-tier application comprises a database tier configured for replication from a database cluster within the plurality of production clusters at the production site to a corresponding database cluster within the plurality of recovery clusters at the disaster recovery site;

identifying the failure of the multi-tier application comprises identifying a fault in the replication of the database tier of the multi-tier application.

3. The computer-implemented method of claim 1, wherein identifying the failure at the disaster recovery site comprises identifying the failure from an agent executing within a cluster within the plurality of recovery clusters.

4. The computer-implemented method of claim 1, wherein identifying the failure comprises identifying a user-initiated failover of the multi-tier application.

5. The computer-implemented method of claim 4, wherein initiating the migration of the multi-tier application from the production site to the disaster recovery site comprises:

identifying a status of each tier of the multi-tier application at the production site;

identifying, based on the status, at least one tier within the multi-tier application that is online;

bringing the tier offline at the production site.

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

identifying a status of each tier of the multi-tier application at the production site;

identifying, based on the status, at least one concurrency violation during the migration of the multi-tier application.

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

identifying a secondary application executing on at least one of the plurality of recovery clusters;

determining that the secondary application has a priority lower than the multi-tier application;

bringing the secondary application offline before initiating the migration in response to the priority.

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

identifying a status of each tier of the multi-tier application at the production site;

displaying the status of each tier of the multi-tier application in an interface for initiating the migration of the multi-tier application.

9. A system for disaster recovery of multi-tier applications, the system comprising:

a detection module programmed to identify a multi-tier application that is provisioned with a plurality of production clusters at a production site;

an identification module programmed to identify a disaster recovery site comprising a plurality of recovery clusters;

a failure module programmed to identify, at the disaster recovery site, a failure of the multi-tier application at the production site;

a migration module programmed to initiate, from the disaster recovery site, a migration of the multi-tier application from the production site to the disaster recovery site, wherein the migration comprises;

identifying a dependency map of the multi-tier application;

migrating each tier of the multi-tier application when, according to the dependency map, no additional tier dependent on the tier remains to be migrated;

at least one hardware processor configured to execute the detection module, the identification module, the failure module, and the migration module.

10. The system of claim 9, wherein:

the multi-tier application comprises a database tier configured for replication from a database cluster within the plurality of production clusters at the production site to a corresponding database cluster within the plurality of recovery clusters at the disaster recovery site;

the failure module is programmed to identify the failure of the multi-tier application by identifying a fault in the replication of the database tier of the multi-tier application.

11. The system of claim 9, wherein the failure module is programmed to identify the failure at the disaster recovery site by identifying the failure from an agent executing within a cluster within the plurality of recovery clusters.

12. The system of claim 9, wherein the failure module is programmed to identify the failure by identifying a user-initiated failover of the multi-tier application.

13. The system of claim 12, wherein the migration module is programmed to initiate the migration of the multi-tier application from the production site to the disaster recovery site by:

identifying a status of each tier of the multi-tier application at the production site;

identifying, based on the status, at least one tier within the multi-tier application that is online;

bringing the tier offline at the production site.

14. The system of claim 9, wherein the migration module is further programmed to:

identify a status of each tier of the multi-tier application at the production site;

identify, based on the status, at least one concurrency violation during the migration of the multi-tier application.

15. The system of claim 9, wherein the migration module is further programmed to:

identify a secondary application executing on at least one of the plurality of recovery clusters;

determine that the secondary application has a priority lower than the multi-tier application;

bring the secondary application offline before initiating the migration in response to the priority.

16. The system of claim 9, wherein the migration module is further programmed to:

identify a status of each tier of the multi-tier application at the production site;

display the status of each tier of the multi-tier application in an interface for initiating the migration of the multi-tier application.

17. A non-transitory computer-readable-storage 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:

identify a multi-tier application that is provisioned with a plurality of production clusters at a production site;

identify a disaster recovery site comprising a plurality of recovery clusters;

identify, at the disaster recovery site, a failure of the multi-tier application at the production site;

initiate, from the disaster recovery site, a migration of the multi-tier application from the production site to the disaster recovery site, wherein the migration comprises;

identifying a dependency map of the multi-tier application;

migrating each tier of the multi-tier application when, according to the dependency map, no additional tier dependent on the tier remains to be migrated.

18. The computer-readable-storage medium of claim 17, wherein:

the multi-tier application comprises a database tier configured for replication from a database cluster within the plurality of production clusters at the production site to a corresponding database cluster within the plurality of recovery clusters at the disaster recovery site;

the one or more computer-executable instructions cause the computing device to identify the failure of the multi-tier application by causing the computing device to identify a fault in the replication of the database tier of the multi-tier application.

19. The computer-readable-storage medium of claim 17, wherein:

the multi-tier application comprises a database tier configured for replication from a database cluster within the plurality of production clusters at the production site to a corresponding database cluster within the plurality of recovery clusters at the disaster recovery site;

the one or more computer-executable instructions cause the computing device to identify the failure of the multi-tier application by causing the computing device to identify a fault in the replication of the database tier of the multi-tier application.

20. The computer-readable-storage medium of claim 17, wherein the one or more computer-executable instructions cause the computing device to identify the failure at the disaster recovery site by causing the computing device to identify the failure from an agent executing within a cluster within the plurality of recovery clusters.