Drp disaster recovery plan

Solo disponible en BuenasTareas
  • Páginas : 25 (6160 palabras )
  • Descarga(s) : 0
  • Publicado : 19 de octubre de 2010
Leer documento completo
Vista previa del texto
White Paper

Disaster Recovery: Best Practices
1 2 2.1 2.2 Executive Summary Disaster Recovery Planning Identification and Analysis of Disaster Risks/Threats Classification of Risks Based on Relative Weights

2.2.1 External Risks 2.2.2 Facility Risks 2.2.3 Data Systems Risks 2.2.4 Departmental Risks 2.2.5 Desk-Level Risks 2.3 2.4 Building the Risk Assessment Determining theEffects of Disasters

2.4.1 List of Disaster Affected Entities 2.4.2 Downtime Tolerance Limits 2.4.3 Cost of Downtime 2.4.4 Interdependencies 2.5 2.6 3 3.1 Evaluation of Disaster Recovery Mechanisms Disaster Recovery Committee Disaster Recovery Phases Activation Phase

3.1.1 Notification Procedures 3.1.2 Damage Assessment 3.1.3 Activation Planning 3.2 Execution Phase

3.2.1 Sequence of RecoveryActivities 3.2.2 Recovery Procedures 3.3 4 Reconstitution Phase The Disaster Recovery Plan Document

© 2008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 1 of 18

White Paper

4.1 4.2 5

Document Contents Document Maintenance Reference

© 2008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 18 White Paper


Executive Summary

Disasters are inevitable but mostly unpredictable, and they vary in type and magnitude. The best strategy is to have some kind of disaster recovery plan in place, to return to normal after the disaster has struck. For an enterprise, a disaster means abrupt disruption of all or part of its business operations, which may directly result in revenue loss.To minimize disaster losses, it is very important to have a good disaster recovery plan for every business subsystem and operation within an enterprise. This paper discusses an approach for creating a good disaster recovery plan for a business enterprise. The guidelines are generic in nature, hence they can be applied to any business subsystem within the enterprise. In the IT subsystem, disasterrecovery is not the same as high availability. Though both concepts are related to business continuity, high availability is about providing undisrupted continuity of operations whereas disaster recovery involves some amount of downtime, typically measured in days. This paper focuses only on disaster recovery. Every business disaster has one or more causes and effects. The causes can be naturalor human or mechanical in origin, ranging from events such as a tiny hardware or software component’s malfunctioning to universally recognized events such as earthquakes, fire, and flood. Effects of disasters range from small interruptions to total business shutdown for days or months, even fatal damage to the business. The process of preparing a disaster recovery plan begins by identifying thesecauses and effects, analyzing their likelihood and severity, and ranking them in terms of their business priority. The ultimate results are a formal assessment of risk, a disaster recovery plan that includes all available recovery mechanisms, and a formalized Disaster Recovery Committee that has responsibility for rehearsing, carrying out, and improving the disaster recovery plan. When adisaster strikes, the normal operations of the enterprise are suspended and replaced with operations spelled out in the disaster recovery plan. Figure 1 depicts the cycle of stages that lead through a disaster back to a state of normalcy.
Figure 1. Enterprise Operations Cycle of Disaster Recovery

© 2008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of18

White Paper

It takes the enterprise some time to assess the exact effects of the disaster. Only when these are assessed and the affected systems are identified can a recovery process begin. The disaster recovery system cannot replace the normal working system forever, but only supports it for a short period of time. At the earliest possible time, the disaster recovery process must be...
tracking img