Disaster Recovery Plan Template

This assignment provides a framework for creating a comprehensive Disaster Recovery Plan. It requires you to identify potential risks such as physical security breaches, system failures, power outages, and virus attacks. For each identified risk, you must describe the disaster response steps, resources needed, and a timeline for action. The template also includes sections for declaring a disaster, cut-over criteria, and sign-off by responsible parties.

Disaster Recovery Plan
for <BNS>
Version: <n.n> Date: <dd-mm-yyyy>
Copy: Uncontrolled
<Project Title>
Disaster Recovery Plan
Version: <n.n>, Date: <dd-mm-yyyy>
Page ii of ix

Document Acceptance and Release Notice
This document is Version <n.n> <dd-mm-yyyy> of the Disaster Recovery Plan for <Project
Title>.
The Disaster Recovery Plan is a managed document. For identification of amendments
each page contains a release number and a page number. Changes will only be issued as
complete replacement. Recipients should remove superseded versions from circulation.
This document is authorised for release once all signatures have been obtained.
PREPARED: Date: - -
(for acceptance) <Project Manager Name and Title>
<Project Name>
ACCEPTED: Date: - -
(for release) <Project Sponsor Name and Title>
<Project Name> Project Sponsor
<Project Title>
Disaster Recovery Plan
Version: <n.n>, Date: <dd-mm-yyyy>
Page 3 of 9

Risk Analysis
Table of Contents
1 Business Analysis........................................................................................................................
1.1 Project Title.........................................................................................................................
1.2 Disaster Recovery Plan Objective......................................................................................
1.3 Business Critical Functions.................................................................................................
1.4 Critical Data and Software..................................................................................................
1.5 Statutory/Commercial Requirements and Constraints.......................................................
2 Risk Analysis.................................................................................................................................
2.1 Risk Analysis Table............................................................................................................
2.2 Risk Prevention Table.........................................................................................................
2.3 Risk/Disaster Recovery Table............................................................................................
2.4 Disaster Recovery Plan Sign-off.......................................................................................
<Project Title>
Disaster Recovery Plan
Version: <n.n>, Date: <dd-mm-yyyy>
Page 4 of 9

1 Business Analysis
1.1 Project Title
<Project Title>
1.2 Disaster Recovery Plan Objective
<Summarise any relevant background information, why the disaster recovery plan exists
and how to use the plan.>
1.3 Business Critical Functions
<List the business critical functions performed by the business (those relevant to this
project).>
Business Critical Functions
1.
2.
3…
<Provide a summary of how you determined the business critical functions (Eg: What
documentation did you analyse? Did you have team discussions? Did you have Client
discussions? Etc…)>
1.4 Critical Data and Software
<List the Critical Data and Software relevant to this project and disaster prevention and
recovery.>
Critical Data and Software
1.
2.
3…
Provide a summary of how you determined the Critical Data and Software (Eg: What
documentation did you analyse? Did you have team discussions? Did you have Client
discussions? Etc…)
1.5 Statutory/Commercial Requirements and Constraints
Provide a summary of the statutory and commercial requirements that you have identified
and taken into account when developing this plan.
(See - National Privacy Principles. Describe how you must follow these principles when
backing-up and storing personal data gathered by your system)
Provide a summary of your cost constraints and other documents which must be read in
conjunction – ie. Your project plan etc…)
2 Risk Analysis
Key to Risk Rating Symbols used:

Risk Analysis
Rating for Likelihood and Seriousness for each risk
L Rated as Low E Rated as Extreme (Used for Seriousness
only)
M Rated as Medium NA Not Assessed
H Rated as High
Grade: Combined effect of Likelihood/Seriousness
Seriousness
Likelihood
low medium high EXTREME
low N D C A
medium D C B A
high C B A A
Recommended actions for grades of risk
Grade Risk mitigation actions
A Mitigation actions to reduce the likelihood and seriousness to be identified and
implemented as soon as the project commences.
B Mitigation actions to reduce the likelihood and seriousness to be identified and appropriate
actions implemented during project execution.
C Mitigation actions to reduce the likelihood and seriousness to be identified and costed for
possible action if funds permit.
D To be noted - no action is needed unless grading increases over time.
N To be noted - no action is needed unless grading increases over time.
Change to Grade since last assessment
NEW New risk  Grading decreased
— No change to Grade  Grading increased
<Project Title>: Project Business Plan – Version 0.A Page 6

RID Description of
Risk
Impact on
System
Assessment of
Likelihood
Assessment of
Seriousness
Grade
(combined
Likelihood and
Change Date of
Review
Risk Prevention
references
Disaster Response
reference
Responsibility for
mitigation action(s)
Cost Timeline
for
mitigation
action(s)
<R> <A description of
the risk. Also
identify relevant
triggers that may
cause the risk to
be realised.>
<Describe the
nature of the risk
and the impact
on the project if
the risk is not
mitigated or
managed>
<Change in
Grade
since last
review>
<Date of
last
review>
<Risk prevention will
be detailed in the Risk
Prevention Table.
Enter the
prevention IDs that
are used to prevent
this risk>
<Disaster Response will
be detailed in the Disaster
Response Table.
Enter the response IDs
that are used when
responding to this risk
when it becomes
reality>
<Specify who is
responsible for
undertaking each
action(s)>
<Specify
timeframe
for
mitigation
action(s) to
be
completed
by>
R1 Physical Security.
There may be a
risk to
hardware/softwar
e/data if un-
authorised
personnel gained
access to the
physical server
running the virtual
machines.
Expand upon
this…
M M B New 15/02/2013 P5 (See: Risk
Prevention Table)
P1 (See: Risk/Disaster
Recovery Table)
Manager TBC TBC
R2 System
failure/Data
Corruption.
Expand upon this…
R3 Power failure.
Expand upon this…
R4 Virus attack
Expand upon this…
2.1 Risk Analysis Table
<Complete this table for each risk identified below, for the system you are developing. Include any other risks you believe are important to identify>

Risk Analysis
2.2 Risk Prevention Table
<Complete this table for each prevention measure identified below. Include any other prevention measures you believe are important>
<Project Title>: Project Business Plan – Version 0.A Page 8
PID Description of prevention method Resources
Needed
Timeline for
action(s)
<P
>
<Fully describe the how the prevention measure will be undertaken and why>
P1 Backup strategy (What needs to be backed, how often and when) List of items
to be backed
up… etc
P2 Backup procedures
P3 Backup schedules
P4 Password Policy
P5 Physical Protection
P6 Virus/attack Protection
P7 Power Protection

Risk Analysis
2.3 Risk/Disaster Recovery Table
<Complete the table for each risk identified below for the system you are developing. Include any other risks you believe are important to identify.>
<Project Title>: Project Business Plan – Version 0.A Page 9
RID Risk/
Disaster
item
Declaring the disaster Description of disaster response steps Resources
Needed
Date of
Review
Timeline for
action(s)
<P
>
<Specify who’s
responsibility it is to
declare a disaster>
<Identify the cut-over
criteria for initiating a
disaster. Ie when will you
initiate the disaster
reponse? >
R1 Physical
Security.
R2 System
failure/Dat
a
Corruption
.
R3 Power
failure.
Any staff can initiate this
disaster response.
When there is evidence of
a power outage, initiate
the response.
Power outage evidence:
Currently no power,
Server/s have restarted,
Corrupt data,etc…
1. Check local power.
Check if circuit breakers can be flipped back.
On success, turn on/ restart downed servers
Check for data corruption
Fix data corruption as given in “System failure/Data Corruption –
R2” above
2. Check external power ….
3. …
4. …
Expand upon this…
01/04/13 As soon as
disaster is
initiated.
R4 Virus
attack

2.4 Disaster Recovery Plan Sign-off
This plan was reviewed on ___________ by ____________
Signed ___________________________________________
The next review date for this document is on ___________