Periodic validation and health reports of disaster recovery plan

Patent metadata

Field	Value
Publication number	US-9396052-B2
Application number	US-201414265616-A
Country	US
Kind code	B2
Filing date	Apr 30, 2014
Priority date	Apr 30, 2014
Publication date	Jul 19, 2016
Grant date	Jul 19, 2016

Abstract

Techniques are described for validating a disaster recovery plan. In an embodiment, a request is received to perform a validation of a disaster recovery operation plan that includes a set of instructions for performing a disaster recovery operation with respect to a first site and a second site. In response to receiving the request to perform the validation of the disaster recovery operation plan, a set of one or more validation operations is performed with respect to the disaster recovery operation plan. Based on the set of one or more validation operations, a report is generated that identifies one or more issues that may prevent the disaster recovery operation plan from executing properly.

First claim

What is claimed is:

1. A method for validating a disaster recovery operation plan, the method comprising:
receiving a request to perform a validation of the disaster recovery operation plan that includes a set of instructions for performing a disaster recovery operation with respect to a first site and a second site;
in response to receiving the request to perform the validation of the disaster recovery operation plan:
identifying a set of topology metadata that was received from the first site and the second site;
performing a set of one or more validation operations with respect to the disaster recovery operation plan;
wherein the set of one or more validation operations uses the set of topology metadata that was received from the first site and the second site to determine one or more issues that may cause errors during execution of the disaster recovery operation plan;
generating, based on the set of one or more validation operations, a report that identifies the one or more issues that may cause errors during execution of the disaster recovery operation plan; and

wherein the method is performed by one or more computing devices.

2. The method of claim 1 , wherein performing the set of one or more validation operations with respect to the disaster recovery operation plan comprises:
determining, from the set of topology metadata received from the first site and the second site, whether a first topology associated with the first site or a second topology associated with a second site has changed since creation of the disaster recovery operation plan;
in response to determining that the first topology associated with the first site or the second topology associated with the second site has changed since creation of the disaster recovery operation plan, generating notification data that indicates a topology change; and
wherein the notification data is included in the report that identifies one or more issues that may cause errors during execution of the disaster recovery operation plan.

3. The method of claim 1 , wherein performing the set of one or more validation operations with respect to the disaster recovery operation plan comprises:
determining, from the set of topology metadata, a set of one or more credentials for accessing a set of one or more respective targets on the first site or the second site;
determining whether the set one or more of credentials for accessing the set of one or more respective targets on the first site or the second site are valid; and
wherein the one or more issues identified in the report are based, at least in part, on determining that at least one credential of the set of one or more credentials is not valid.

4. The method of claim 1 , wherein performing the set of one or more validation operations with respect to the disaster recovery operation plan comprises:
determining a problem associated with data replication between the first site and the second site; and
wherein the one or more issues identified in the report are based, at least in part, on the problem associated with data replication between the first site and the second site.

5. The method of claim 4 , wherein performing the set of one or more validation operations with respect to the disaster recovery operation plan comprises:
determining a lag time for data replication between the first site and the second site;
and

determining that the lag time for data replication between the first site and the second site does not satisfy a threshold.

6. The method of claim 1 , wherein performing the set of one or more validation operations with respect to the disaster recovery operation plan comprises:
performing a first validation check with respect to data replication between a first storage appliance on the first site and a second storage appliance on the second site; and
performing a second validation check with respect to data replication between a first database on the first site and a second database on the second site.

7. The method of claim 1 , wherein said performing the set of one or more validation operations includes periodically performing the set of one or more validation operations with respect to the disaster recovery operation plan to generate periodic reports that identify a health associated with the disaster recovery operation.

8. The method of claim 7 , wherein generating periodic reports includes sending the periodic reports to a set of one or more email addresses that are associated with the disaster recovery operation plan.

9. The method of claim 7 ,
wherein the disaster recovery operation plan is a first disaster recovery operation plan of a plurality of disaster recovery operation plans for performing disaster recovery operations with respect to the first site and the second site;
wherein generating periodic reports includes generating the periodic reports for the first disaster recovery operation plan of the plurality of disaster recovery operation plans but not for a second disaster recovery operation plan of the plurality of disaster recovery operation plans.

10. The method of claim 1 , wherein performing a set of one or more validation operations includes performing the set of one or more validation operations for a plurality of tiers on the first site and the second site.

11. One or more non-transitory computer-readable media storing code for validating a disaster recovery operation plan, the code, when executed by one or more processors, causes:
receiving a request to perform a validation of the disaster recovery operation plan that includes a set of instructions for performing a disaster recovery operation with respect to a first site and a second site;
in response to receiving the request to perform the validation of the disaster recovery operation plan:
identifying a set of topology metadata that was received from the first site and the second site;
performing a set of one or more validation operations with respect to the disaster recovery operation plan;
wherein the set of one or more validation operations uses the set of topology metadata that was received from the first site and the second site to determine one or more issues that may cause errors during execution of the disaster recovery operation plan; and
generating, based on the set of one or more validation operations, a report that identifies the one or more issues that may cause errors during execution of the disaster recovery operation plan.

12. The one or more non-transitory computer-readable media of claim 11 , wherein performing the set of one or more validation operations with respect to the disaster recovery operation plan includes:
determining, from the set of topology metadata received from the first site and the second site, whether a first topology associated with the first site or a second topology associated with a second site has changed since creation of the disaster recovery operation plan;
in response to determining that the first topology associated with the first site or the second topology associated with the second site has changed since creation of the disaster recovery operation plan, generating notification data that indicates a topology change;
wherein the notification data is included in the report that identifies one or more issues that may cause errors during execution of the disaster recovery operation plan.

13. The one or more non-transitory computer-readable media of claim 11 , wherein performing the set of one or more validation operations with respect to the disaster recovery operation plan comprises:
determining, from the set of topology metadata, a set of one or more credentials for accessing a set of o

Assignees

• Oracle Int Corp

Inventors

• Sampath Praveen
• Vijjapurapu Rama
• Desai Mahesh
• Borde Shekhar

Classifications

• G06F11/008 Primary

  Reliability or availability analysis · CPC title

• H04L41/0873 Primary

  Checking configuration conflicts between network elements · CPC title

• H04L41/0654

  using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) · CPC title

• G06F11/2023

  Failover techniques · CPC title

• H04L41/12

  Discovery or management of network topologies · CPC title