Browse Prior Art Database

A method and system for Extracting Disaster Recovery Best Practices

IP.com Disclosure Number: IPCOM000202333D
Publication Date: 2010-Dec-14
Document File: 4 page(s) / 76K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for extracting disaster recovery best practices is disclosed. The method involves automatically learning best practices and disaster recovery templates from a plan repository of already deployed plans. A logical layout of copy relationships are extracted in a plan repository and these relationships are used as standard templates for disaster recovery planning.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 35% of the total text.

Page 01 of 4

A method and system for Extracting Disaster Recovery Best Practices

Disclosed is a method and system for extracting disaster recovery best practices. To accomplish this, best practices and disaster recovery templates of already deployed plans are automatically learned from a plan repository. Thereafter, a logical layout of copy relationships are extracted in the plan repository and these relationships are used as standard templates for disaster recovery planning. Further, Service Level Agreement (SLA) parameters of each plan present in the plan repository may be learned and used to identify best practices that can be employed while designing new plans.

A best practice extraction tool is used for extracting disaster recovery best practices. An input to this tool is a plan repository. The plan repository consists of a set of disaster recovery plans that are deployed in live enterprises. Each plan may include an IT infrastructure deployed (server, storage, network) and disaster recovery elements (replication relationships, server clusters and resource groups, consistency groups etc.). Additionally, each plan may optionally specify the disaster recovery SLAs that are met by the plan. Further, the output of the tool may include a set of best practices/policy of type:

If

Then

.

These policies are derived from the plan repository. The two most common policies may have the following format:

If

Then

, wherein Template1 is a set of replicas and copy relationships. (e.g., Replicas = {Primary, Cop1, Copy2, Copy3}, Relationshops = {(Primary, Copy1, Metro Mirror), (Copy1, Copy2, Global Mirror), (Copy2, Copy3, Flashcopy)}.

If

Then

, wehrein the SLA X'||Y' implies that the source of the replication solution that meets X' may also act as source for Y'. Similarly, X' and Y' implies that the target of the replication solution that meets X may also act as a source for the solution that meets Y'. This best practice specifies how a composite SLA may be broken down into simpler individual SLAs.

In an instance, a DR Knowledge Center illustrated in Fig. 1, is a hosted web service that may accumulate all the disaster recovery/business resilience solutions that are offered and validated. All the different disaster recovery solution deployments are captured from field engagements. These solutions are extracted or discovered, and then transformed to a standard format and stored at this knowledge center. Metadata associated with these deployments are extracted semi-automatically or automatically discovered and then manually supplied by field experts. [Appears repetition.] Any new DR plan may get validated through the best practices of this knowledge center. This validates the new plans against lessons learnt from previous deployments i.e., best practices are used as guidance policies for future planning processes. Best practice

1


Page 02 of 4

aging or upgrade happens due to this iterative procedure. The DR knowledge center may be used as a search and validati...