Use this template as a guide for documenting your disaster recovery test efforts. Disaster recovery tests should be regularly conducted, reviewed, and plans subsequently updated. This template outlines the critical components of your disaster recovery and business continuity practices. Using the runbook template provided here by Evolve IP can make the difference for an organization between two extremes: being prepared for an unexpected event and efficiently recovering, or never recovering at all. If documented properly, it can take the confusion and uncertainty out the recovery environment which, during an actual disaster, is often in a state of panic. However, a runbook is only useful if it is up-to-date. Runbooks, or updates to runbooks, are the outputs of every DR test. It provides an instruction set for personnel in the event of a disaster, including both infrastructure and process information. To ensure that DR testing, planning, and recovery is organized and effective, many organizations use a disaster recovery “runbook.”Ī DR runbook is a working document, unique to every organization, which outlines the necessary steps to recover from a disaster or service interruption. Also, the recovery of systems in the right sequence is important. Examples include change management such as the needed reconfiguration of applications or systems. Each application tier should have an established recovery time objective (RTO) and recovery point objective (RPO) based on business risk.ĭR testing is essential to adequate recovery of systems and data, but also to uncover events or conditions met during real disasters scenarios that were not previously accounted for. Natural tiers or stages of DR begin at phase 1 – infrastructure (networking, AD, DHCP, etc.) – then extend to recovery by application tiers. From an IT perspective, planning starts with a business impact analysis (BIA) by application/workload. By Laura DuBois, Program Vice President, Storage, IDC:ĭR planning is complex and spans three key areas: technology, people, and process.
0 kommentar(er)
