Template

IT Dis as ter
Recovery P la nning:
A Te mpla te
When disaster strikes, business s uffers . A goal of business planning is to mitigate
disruption of product and s ervices delivery to the greatest degree possible whe n
disruption due to disaster occurs. Business continuity is the overarching concern.

An IT disaster recovery plan is the lynchpin of an overall business continuity s trate gy.
And the purpos e of business continuity is to maintain a minimum level of s ervice while
restoring the organization to business as usual. If a business fails to put a disaster
recovery plan in place then, whe n disaster strikes, the company ris ks losing cus tome
rs
to competitors, losing funding and having the need for its products or services re-
evaluated and deemed unnecessary.
Mic ro Focus encourages every organization to proactively execute an IT Disaster
Recovery plan. To assist, we provide you with a template as a springboard for your
organization’s customized plan. Please contact a Mic ro Focus re pres e ntative whe n you
are ready!

XYZ Organization IT Disaster Recovery Plan Revision His

tory
REVISION DATE NA ME DESCRIPTION
 Table of Contents
XYZ Organization IT Disaster Recovery Plan Revision History......................................................................................................2

Information Technology StatementofIntent...................................................................................................................................5

Policy Statement.............................................................................................................................................................................5

Objectives.......................................................................................................................................................................................5

Key PersonnelContactInfo............................................................................................................................................................6

Notification Calling Tree..................................................................................................................................................................7

ExternalContacts............................................................................................................................................................................8

External Contacts Calling Tree .....................................................................................................................................................10

1 PlanOverview.......................................................................................................................................11

1.1 PlanUpdating........................................................................................................................................11

1.2 Plan DocumentationStorage.................................................................................................................11

1.3 BackupStrategy....................................................................................................................................11

1.4 RiskManagement..................................................................................................................................12

2 Emergency............................................................................................................................................12

2.1 Alert, escalationandplaninvocation.....................................................................................................12

2.1.1 Plan TriggeringEvents..........................................................................................................................12

2.2.2 AssemblyPoints....................................................................................................................................14

2.2.3 Activation of Emergency ResponseTeam.............................................................................................14

2.3 DisasterRecoveryTeam.......................................................................................................................14

2.4 Emergency Alert, Escalation and DRPActivation..................................................................................14

2.4.1 EmergencyAlert....................................................................................................................................15

2.4.2 DR Procedures forManagement...........................................................................................................15

2.4.3 ContactwithEmployees........................................................................................................................15

2.4.4 BackupStaff..........................................................................................................................................15

2.4.5 Recorded Messages / Updates .............................................................................................................16

2.3.7 Alternate Recovery Facilities / HotSite..................................................................................................16

2.3.8 PersonnelandFamilyNotification.........................................................................................................16

3 Me dia ....................................................................................................................................................16

3.1 Me dia Contact.......................................................................................................................................16

 3.2 Me dia Strategies....................................................................................................................................16

3.3 Me dia Team..........................................................................................................................................16

3.4 Rules for Dealing withMedia.................................................................................................................16

4 Insurance ..............................................................................................................................................17

5 Financial and LegalIssues....................................................................................................................17

5.1 FinancialAssessment............................................................................................................................17

5.2 FinancialRequirements.........................................................................................................................17

5.3 LegalActions.........................................................................................................................................17

6 DRP Exercising.....................................................................................................................................18

Appendix A – Technology Disaster Recovery Plan.......................................................................................................................19

Templates Disaster Recovery Plan for<SystemOne>.................................................................................................................19

Disaster Recovery Planfor<SystemTwo>...................................................................................................................................21

Disaster Recovery Plan for Local Area Network(LAN).................................................................................................................23

Disaster Recovery Plan for Wide Area Network(WAN)................................................................................................................25

Disaster Recovery Plan for Remote Connectivity.........................................................................................................................27

Disaster Recovery Plan for Voice Communications......................................................................................................................29

Appendix B – Suggested Forms ...................................................................................................................................................31

Damage AssessmentForm...........................................................................................................................................................31

Management of DR Activities Form..............................................................................................................................................31

Disaster Recovery EventRecordingForm....................................................................................................................................32

Disaster Recovery Activity ReportForm.......................................................................................................................................32

Mobilizing the Disaster Recovery TeamForm..............................................................................................................................33

Mobilizing the Business Recovery TeamForm.............................................................................................................................33

Monitoring Business Recovery Task Progress Form....................................................................................................................34

Preparing the Business Recovery ReportForm............................................................................................................................34

Communications Form..................................................................................................................................................................35

Returning Recovered Business Operations to Business UnitLeadership.....................................................................................35

Business Process/Function Recovery Completion Form..............................................................................................................36

Information Technology Statement of Intent

This document delineates our policies and procedures for technology disaster recovery,
as well as our process-level plans for recovering critical technology platforms and the
telecommunications infra s tructure . This document summarizes our recommended
procedures . In the event of an actual emergency situation, modifications to this
document may be made to ens ure physical safety of our people, our systems, and our
data.

Our mission is to ens ure information system uptime, data integrity and availability, and
business continuity.

Policy Statement

Corpora te management has approved the following policy s tate ment:

• The company shall develop a comprehensive IT disaster recovery plan.

• A formal risk assessment shall be undertaken to determine the requirements
for the disaster recovery plan.
• The disaster recovery plan should cover all essential and critical
infrastructure elements, s ys tems and networks, in accordance with key
business activities.
• The disaster recovery plan should be periodically tes ted ina simulated
environment to ens ure that it can be implemented in emergency situations
and
that the management and staff understand how it is to be executed.
• All staff must be made aware of the disaster recovery plan and their own
res pective roles .
• The disaster recovery plan is to be kept up to date to take into account
changing circumstances.
Objectives

The principal objective of the disaster recovery program is to develop, test and
document a we ll- s tructure d and easily understood plan which will help the company
recover as quickly and effectively as possible from an unforeseen disaster or
emergency which interrupts information s ys tems and business operations . Additional
objectives include the following:

• The need to ens ure that all employees fully understand their duties in
implementing such a plan
• The need to ens ure that operational policies are adhered to within all
planned activities
• The need to ens ure that proposed contingency a rra nge me nts are cost-
effective
• The need to consider implications on other company sites
• Disaster recovery capabilities as applicable to key cus tomers , vendors and others
Key Personnel Contact Info

Name, Title Contact Option Contact Number

Work
Alte rna te
Mo bile
Ho me
Email Address
Alte rna te Email

Work
Alte rna te
Mo bile
Ho me
Email Address
Alte rna te Email

Work
Alte rna te
Mo bile
Ho me
Email Address
Alte rna te Email

Work
Alte rna te
Mo bile
Ho me
Email Address
Alte rna te Email

Work
Alte rna te
Mo bile
Ho me
Email Address
Alte rna te Email

Work
Alte rna te
Mo bile
Ho me
Email Address
Alte rna te Email
No tificatio n Calling Tree

Person
Identifying
Incident
External Contacts

Name, Title Contact Option Contact Number

Landlord / Property
Manager
Account Number None
Work
Mo bile
Ho me
Email Address

Power Company
Account Number Work
Mo bile
Ho me
Email Address

Telecom Carrier 1
Account Number Work
Mo bile
Fax
Ho me
Email Address

Telecom Carrier 2
Account Number Work
Mo bile
Ho me
Email Address

Hardware Supplier 1
Account Number Work
Mo bile
Emergency
Reporting
Email Address

Server Supplier 1
Account Number. Work
Mo bile
Fax
Email Address

Wo rks tatio n Supplier

1 Work
Account Number Mo bile
Ho me
Email Address
 Name, Title Contact Option Contact Number
Office Supplies 1
Account Number Work
C3095783
Mo bile
Home
Email Address
Ins urance – Name
Account Number Work
Mo bile
Home
Email Address

Site Security –
Account Number Work
Mo bile
Home
Email Address

Off-Site Storage 1
Account Number Work
Mo bile
Home
Email Address

Off-Site Storage 2
Account Number User ID
Password
Home
Email Address

HVAC –
Account Number Work
Mo bile
Home
Email Address

Power Generator –
Account Number Work
Mo bile
Home
Email Address

Other –
Account Number Work
Mo bile
Home
Email Address
External Contacts Calling Tree
1 Plan Overview

1.1 Plan Updating

It is necessary for the DRP updating process to be properly s tructure d and controlled.
Whenever changes are made to the plan they are to be fully tested and appropriate
amendments should be made to the training materials. This will involve the use of
formalized change control procedures under the control of the IT Dire cto r.

1.2 Plan Documentation Storage

Copies of this Plan, CD, and hard copies will be s tored in s ecure locations to be
defined
by the company. Each member of senior management will be issued a CD and ha rd
the
copyBusiness Recovery
of this plan Teamatwill
to be filed be issued
home. a CD and
Each member ofhard copy of this
the Disaster RecoveryATeam
master
and
plan. protected copy will be stored on specific res ources established for this purpose.

1.3 Backup Strategy

Key business processes and the agreed backup s trategy for each are lis ted below.
The s trategy chosen is for a fully mirro re d recovery s ite at the company’s offices in
.
This s trategy entails the maintenance of a fully mirro re d duplicate s ite which will
enable instantaneous switching between the live s ite (headquarters ) and the backup
s ite.

KEY B US INES S BACKUP STRATEGY

PROCESS Fully mirro re d recovery s ite
Tech Support - Ha rdwa re
IT Operations Fully mirro re d recovery s ite
Tech Support - S oftwa re Fully mirro re d recovery s ite
Facilities Management Fully mirro re d recovery s ite
Email Fully mirro re d recovery s ite
P urchas ing Fully mirro re d recovery s ite
Disaster Recovery Fully mirro re d recovery s ite
Finance Fully mirro re d recovery s ite
Contracts Admin Fully mirro re d recovery s ite
Warehouse & Inventory Fully mirro re d recovery s ite
Product Sales Fully mirro re d recovery s ite
Ma inte na nce Sales Fully mirro re d recovery s ite
Human Resources Off- s ite data s torage facility
Testing Fully Mirro re d Recovery s ite -Fully mirro re d recovery s ite
Works hop Fully Mirro re d Recovery s ite - Fully mirro re d recovery s
ite Fully mirro re d recovery s ite
Call Center Fully mirro re d recovery s ite
Web Site
 1.4 Ris k Management

The re are many potential disruptive thre a ts which can occur at any time and affect
the
normal business proces s . We have considered a wide range of potential threats and
the re s ults of our deliberations are included in this section. Each potential
environmental disaster or emergency situation has been examined. The focus he re is
on the level of business disruption which could aris e from each type of dis aster.
Potential disasters have been assessed as follows:
Probability Brief Description Of
Potential Dis as ter Impact Potential
Rating
Rating Consequences
& Remedial
Actions
Flood 3 4 All critical equipment is
located on 1st Floor
Fire 3 4 FM200 suppression system
installed in main computer
centers. Fire and smoke
detectors on
all floors.
Tornado 5
Electrical storms 5
Act of terrorism 5
Act of sabotage 5
Electrical 3 4 Redundant UPS array
power together with auto standby
Failure generator that is tes ted
weekly & remotely
monitored 24/7. UPSs also
remotely monitored.
Loss of 4 4 Two diversely routed T1
communications trunks into building. WAN
network services redundancy, voice
network resilience

Probability: 1=Very High, 5=Very Low Impact: 1=Total destruction, 5=Minor annoyance

2 Emergency

2.1.1 Alert, escalation and plan invocation

2.1.2 Plan Triggering Events
2.2 Key trigger issues at headquarters that would lead to activation of the DRP
are:
• Total loss of all
power
communications
• Flooding of the premises
• Loss of the building
2.2.2 As s embly Points
Where the premis es need to be evacuated, the DRP invocation plan identifies two
evacuation assembly points:
• P rima ry – Far end of main parking lot;
• Alte rna te – Parking lot of company acros s the
street

2.2.3 Activation of Emergency Response Team

When an incident occurs the Emergency Response Team (ERT) must be activated.
The ERT will then decide the extent to which the DRP must be invoked. All
employees must be issued a Quick Reference card containing ERT contact details to
be used in the event of a disaster.
Responsibilities of the ERT are to:

• Respond immediately to a potential disaster and call emergency services;

• Assess the extent of the disaster and its impact on the business, data center,
etc.;
• Decide which elements of the DR Plan should be activated;
• Establish and manage disaster recovery team to maintain vital services and
re turn
• Ens uretoemployees
normal operation;
are notified and allocate responsibilities and activities as
re quire d

2.3 Dis as ter Recovery Team

The team will be contacted and assembled by the ERT. The team's responsibilities
include:
• Establish facilities for an emergency level of s ervice within 2.0 business
hours;
• Res tore key s ervices within 4.0 business hours of the incident;
• Recover to business as usual within 8.0 to 24.0 hours after the incident;
• Coordinate activities with disaster recovery team, first responders, etc.
• Report to the emergency response team

2.4 Emergency Alert, Escalation and DRP Activation

This policy and procedure has been established to ens ure that in the event of a
disaster or crisis, personnel will have a clear understanding of who should be
contacted. P rocedures have been addressed to ens ure that communications can be
quickly established while activating disaster recovery.

The DR plan will rely principally on key me mbe rs of management and staff who will
provide the technical and management skills necessary to achieve a smooth
technology and business re cove ry. Suppliers of critical goods and s ervices will
continue to support recovery of business operations as the company returns to no rma l
operating mode.
2.4.1 Emergency Alert

The person discovering the incident calls a member of the Emergency Response
Team in the order listed:

Emergency Response Team

•
•
If not available try:
•
•

The Emergency Response Team (ERT) is responsible for activating the DRP for
dis as ters identified in this plan, as well as in the event of any other occurrence
that affects the company’s capability to perform normally.

One of the tas ks during the early stages of the emergency is to notify the Disaster
Recovery Team (DRT) that an emergency has occurred. The notification will request
DRT me mbe rs to assemble at the s ite of the problem and will involve sufficient
information to have this request effectively communicated. The Business Recovery
Team (BRT) will consist of senior representatives from the main business de pa rtments .
The BRT Leader will be a senior member of the company's management team, and will
be res pons ible for taking overall charge of the proces s and ensuring that the company
returns to normal working operations as early as possible.

2.4.2 DR Procedures for Management

Me mbe rs of the management team will keep a hard copy of the names and
contact
numbers of each employee in their departments. In addition, management team
members will have a ha rd copy of the company’s disaster recovery and business
continuity plans on file in their homes in the event that the he a dqua rte rs building
is
2.4.3 Contact
inaccessible, with Employees
unusable, or destroyed.
Managers will serve as the focal points for their departments, while designated
employees will call other employees to discuss the crisis/disaster and the company’s
immediate plans. Employees who cannot reach staff on their call list are advised to call
the staff member’s emergency contact to re lay information on the dis as ter.

2.4.4 Backup Staff

Ifa manager or staff member designated to contact other staff members is
unavailable or incapacitated, the designated backup staff member will perform
notification duties.
 2.4.5 Recorded Mes s ages /
Updates
For the lates t information on the disaster and the organization’s res pons e, s
taff
members can call a toll- fre e hotline lis ted in the DRP wallet card. Included in
messages
will be data on the nature of the dis as ter, assembly sites, and updates on wo
rk
2.3.7 Alternate Recovery Facilities / Hot Site
resumption.
If necessary, the hot site at SunGard will be activated and notification will be given via
recorded messages or through communications with managers . Hot site staffing will
consist of members of the disaster recovery team only for the first 24 hours , with
other
staff members joining at the hot site as necessary.

2.3.8 Personnel and Family No tificatio

n
If the incident has re s ulte d ina situation which would cause concern to an
employee’s immediate family such as hospitalization of injured pers ons , it will be
necessary to notify their immediate family members quickly.

3 Media

3.1 Media Contact

Assigned staff will coordinate with the media, working according to guidelines that have
been previously approved and issued for dealing with post- disaster communications.

3.2 Media Strategies

1. Avoiding adverse publicity
2. Take advantage of opportunities for useful publicity
3. Ha ve ans wers to the following basic questions:
• What happened?
• How did it happen?
• What are you going to do about
it?

3.3 Media Team

•
•
•

3.4 Rules for Dealing with Media

Only the media team is permitted direct contact with the media; anyone else
contacted should refer callers or in-person media repres entatives to the media
team.
4 Ins urance

As part of the company’s disaster recovery and business continuity s trategies a number
of insurance policies have been put in place. These include e rro rs and omissions,
dire cto rs & officers liability, general liability, and business interruption insurance.

If insurance-related assistance is required following an e me rge ncy out of normal

business hours , please contact:

Person
Next
Policy Name Coverage Coverage Amount Of Responsible
Renewal
Type Period Coverage For
Date
Coverage

5 Financial and Legal Is s

ues
5.1 Financial Assessment

The emergency res pons e team shall prepare an initial assessment of the impact
of the incident on the financial affairs of the company. The assessment should
include:
• Loss of financial documents
• Loss of revenue
• Theft of check books, credit cards,
etc.
• Loss of cash

5.2 Financial Requirements

The immediate financial needs of the company must be addressed. These can include:
• Cash flow position
• Tempora ry borrowing capability
• Upcoming payments for taxes, payroll taxes, Social Security, etc.
• Availability of company credit cards to pay for supplies and services re quire
d
post- disaster

5.3 Legal Actions

The company legal department and ERT will jointly review the afte rma th of the incident
and decide whether there may be legal actions resulting from the event; in particular,
the possibility of claims by or against the company for regulatory violations, etc.
6 DRP Exercising

Disaster recovery plan exercis es are an essential part of the plan development process.
In a DRP exercis e no one passes or fails; everyone who participates le a rns from
exercis es – what needs to be improved, and how the improvements can be
implemented. Plan exercising ensures that emergency teams are familiar with their
assignments and, mo re importantly, are confident in their capabilities.

Successful DR plans launch into action smoothly and effectively when they are
needed. This will only happen if everyone with a ro le to play in the plan has rehears
ed
the ro le one or more times . The plan should also be validated by simulating the
circumstances within which it has to work and seeing what happens
Appendix A – Technology Disaster Recovery Plan

Templates Dis as ter Recovery Plan for <Sys tem

One>

SYSTEM
OVERVIEW
PRODUCTION SERVER Location:
Server Model:
Operating System:
CPUs:
Me mo ry:
Total Disk:
System Handle:
System Serial #:
DNS Entry:
IP Addres s :
O the r:
HOT SITE SERVER
AP P LICATIONS
(Us e bold for Hot
Site)
ASSOCIATED SERVERS
KEY CONTACTS
Ha rdwa re Vendor
System Owners
Database Owner
Application O wne rs
S oftware Vendors
Offsite S torage

BACKUP STRATEGY
FOR SYSTEM ONE
Daily
Mo nthly
Q ua rte rly
SYSTEM ONE
DISASTER
RECOVERY
PROCEDURE
S cenario 1

Total Loss of Data

S cenario 2

Total Loss of HW
A DDENDUM
CONTACTS

File Sys tems

File System as of File s ys tem Kbytes Us ed Avail %us ed
Mo unted on
Minimal file
s ys tems to
be created
and res tored
from
backup:

Other critical files

to modify
Necessary
dire cto rie s
to
cre ate
Critical files to
res tore
Secondary files to
res tore
Other files to
res tore
Disaster Recovery Plan for <Sys tem Two>

SYSTEM

OVERVIEW
PRODUCTION SERVER Location:
Server Model:
Operating System:
CPUs:
Me mory:
Total Disk:
System Handle:
System Serial #:
DNS Entry:
IP Address:
Other:
HOT SITE SERVER
AP P LICATIONS
(Us e bold for Hot Site)
ASSOCIATED SERVERS

KEY CONTACTS
Ha rdwa re Vendor
System Owners
Database Owner
Application O wne rs
S oftware Vendors
Offsite S torage

BACKUP STRATEGY for

SYSTEM TWO
Daily
Mo nthly
Q ua rte rly

SYSTEM TWO
DISASTER
RECOVERY
PROCEDURE

S cenario 1

Total Loss of Data

S cenario 2

Total Loss of HW
A DDENDUM
CONTACTS

File Sys tems

File System as of File s ys tem Kbytes Us ed Avail %us ed
Mo unted on
Minimal file
s ys tems to
be created
and res tored
from
backup:

Other critical files

to modify
Necessary
dire cto rie s
to
cre ate
Critical files to
res tore
Secondary files to
res tore
Other files to
res tore
Disaster Recovery Plan for Local Area Netwo rk
(LAN)
SYSTEM

OVERVIEW
SERVER Location:
Server Model:
Operating System:
CPUs:
Me mory:
Total Disk:
System Handle:
System Serial #:
DNS Entry:
IP Address:
Other:
HOT SITE SERVER
AP P LICATIONS
(Us e bold for Hot Site)
ASSOCIATED SERVERS

KEY CONTACTS
Ha rdwa re Vendor
System Owners
Database Owner
Application O wne rs
S oftware Vendors
Offsite S torage

BACKUP STRATEGY for

SYSTEM TWO
Daily
Mo nthly
Q ua rte rly

SYSTEM TWO
DISASTER
RECOVERY
PROCEDURE

S cenario 1

Total Loss of Data

S cenario 2

Total Loss of HW
A DDENDUM
CONTACTS

File Sys tems

File System as of File s ys tem Kbytes Us ed Avail %us ed
Mo unted on
Minimal file
s ys tems to
be created
and res tored
from
backup:

Other critical files

to modify
Necessary
dire cto rie s
to cre ate
Critical files to
res tore
Secondary files to
res tore
Other files to
res tore
Disaster Recovery Plan for Wide Area Netwo rk (WA
N)
SYSTEM

OVERVIEW
EQUIP MENT Location:
Device Type:
Model No.:
Technical Specifications:
Network Interfaces:
Power Requirements;
System Serial #:
DNS Entry:
IP Address:
Other:
HOT SITE EQUIP MENT
SPECIAL
AP P LICATIONS
ASSOCIATED DEVICES

KEY CONTACTS
Ha rdwa re Vendor
System Owners
Database Owner
Application O wne rs
S oftware Vendors
Offsite S torage
Network Services

BACKUP STRATEGY for

SYSTEM TWO
Daily
Mo nthly
Q ua rte rly

SYSTEM TWO
DISASTER
RECOVERY
PROCEDURE

S cenario 1

Total Loss of Network

S cenario 2

Total Loss of HW
A DDENDUM
CONTACTS

Support Sys tems

Support system

Critical network
assets
Critical interfaces
Critical files to
res tore
Critical network
s ervices to res tore
Other services
Disaster Recovery Plan for Remote Connectivity

SYSTEM

OVERVIEW
EQUIP MENT Location:
Device Type:
Model No.:
Technical Specifications:
Network Interfaces:
Power Requirements;
System Serial #:
DNS Entry:
IP Address:
Other:
HOT SITE EQUIP MENT
SPECIAL
AP P LICATIONS
ASSOCIATED DEVICES

KEY CONTACTS
Ha rdwa re Vendor
System Owners
Database Owner
Application O wne rs
S oftware Vendors
Offsite S torage
Network Services

BACKUP STRATEGY for

SYSTEM TWO
Daily
Mo nthly
Q ua rte rly

SYSTEM TWO
DISASTER
RECOVERY
PROCEDURE

S cenario 1

Total Loss of Network

S cenario 2

Total Loss of HW
A DDENDUM
CONTACTS

Support Sys tems

Support system

Critical network
assets
Critical interfaces
Critical files to
res tore
Critical network
s ervices to res tore
Other services
Disaster Recovery Plan for Voice Communications

SYSTEM

OVERVIEW
EQUIP MENT Location:
Device Type:
Model No.:
Technical Specifications:
Network Interfaces:
Power Requirements;
System Serial #:
DNS Entry:
IP Address:
Other:
HOT SITE EQUIP MENT
SPECIAL
AP P LICATIONS
ASSOCIATED DEVICES

KEY CONTACTS
Ha rdwa re Vendor
System Owners
Database Owner
Application O wne rs
S oftware Vendors
Offsite S torage
Network Services

BACKUP STRATEGY for

SYSTEM TWO
Daily
Mo nthly
Q ua rte rly

SYSTEM TWO
DISASTER
RECOVERY
PROCEDURE

S cenario 1

Total Loss of Switch

S cenario 2

Total Loss of Network

A DDENDUM
CONTACTS

Support Sys tems

Support system

Critical network
assets
Critical interfaces
Critical files to
res tore
Critical network
s ervices to res tore
Other services
Appendix B – Suggested Fo rms

Damage As s es s ment Fo rm
Key Business
Process Description Of Extent Of Damage
Affected Problem

Management of DR Activities Fo rm

• During the disaster recovery proces s all activities will be determined using
a
s tandard s tructure ;
• Where practical, this plan will need to be updated on a regular basis
• All actions thatdisaster
throughoutthe occur during thisperiod;
recovery phase will need to be
recorded
Activity Name:
Reference Number:
Brief Description:

Commencement Completion
Date/Time Date/Time Resources In Charge
Involved
Disaster Recovery Event Recording Fo rm

• All key events that occur during the disaster recovery phase must be
recorded.
• An event log shall be maintained by the disaster recovery team leader.
• This event log should be started at the commencement of the emergency and
a
copy of the log passed on to the business recovery team once the initial
dangers have been controlled.
• The following event log should be completed by the disaster recovery team
leader to re cord all key events during disaster recovery, until such time as
responsibility
Description of Dis asis handed
ter: over to the business recovery team.
Commencement Date:
Date/Time DR Team Mo bilized:

Activities Undertaken Date Follow-On

by and Outcome Action
DR Team Time Required

Disaster Recovery Team's Wo rk Completed: <Date>

Event Log Passed to Business Recovery Team: <Date>

Disaster Recovery Activity Report Fo rm

• On completion of the initial disaster recovery res ponse the DRT leader should
pre pa re a report on the activities undertaken.
• The report should contain information on the emergency, who was notified and
when, action taken by members of the DRT together with outcomes arising
from
those actions.
• The report will also contain an assessment of the impact to no rma l
business operations.
• The report should be given to business recovery team leader, with a copy to
senior management, as a ppropria te .
• A disaster recovery report will be pre pared by the DRT leader on completion
of the initial disaster recovery response.
• In addition to the business recovery team leader, the report will be
dis tributed to senior management
 The report will include:
• A description of the emergency or incident
• Those people notified of the emergency (includingdates)
• Action taken by members of the DRT
• Outcomes arising from actions taken
• An assessment of the impact to normal business operations
• Assessment of the effectiveness of the BCP and lessons
learned
• Lessons learned

Mo bilizing the Disaster Recovery Team Fo

rm
• Following an emergency requiring recovery of technology infrastructure
assets, the disaster recovery team should be notified of the situation and
placed onstandby.
• The format shown below can be used for recording the activation of the DR
team
once the work of the damage assessment and emergency res ponse teams
has
Description of Emergency:
been completed
Date Occurred:
Date Work of Disaster Recovery Team Completed:

Name of Contacted
Contact Start Date
Team On (Time / By Whom Response
Member Details Date) Required

Relevant Comments (e.g., Specific Instructions Issued)

Mo bilizing the Business Recovery Team Fo

rm
• Following an emergency requiring activation of the disaster recovery team,
the business recovery team should be notified of the situation and placed
on
standby.
• The format shown below will be used for recording the activation of the
business recovery team once the work of the disaster recovery team has
been completed.
Description of Emergency:
Date Occurred:
Date Work of Business Recovery Team Completed:
 Name Contact Contacted Start Date
of Team On (Time / By Whom Response
Details Required
Member Date)

Relevant Comments (e.g., Specific Instructions Issued)

Mo nito ring Business Recovery Tas k Progres s Fo

rm
• The progres s of technology and business recovery tas ks must be closely
monitored during this pe riod of time
• Since difficulties experienced by one group could significantly affect other
dependent tasks it is important to ens ure that each task is adequately res
ourced
and that the efforts re quire d to res tore normal business operations have not
been underes timated
Note : A priority sequence must be identified although, whe re possible, activities will
be carried out simultaneously.

Recovery Tasks P erson(s) Completion Date Miles tone Other

(Order of Responsibl Estimated Actual s Relevant
P rio rity) e Identified Information
1.
2.
3.
4.
5.
6.
7.

Preparing the Business Recovery Report Fo rm

• On completion of business recovery activities the BRT leader should prepare a

report on the activities undertaken and completed
• The report should contain information on the disruptive event, who was notified
and when, action taken by members of the BRT together with outcomes aris ing
from those actions
• The report will also contain an assessment of the impact to normal
operations
business
• The report should be distributed to senior management, as appropriate

The contents of the report shall include:

• A description of the incident
• People notified of the emergency (including dates )
 • Action taken by the business recovery team
• Outcomes arising from actions taken
• An assessment of the impact to normal business operations
• P roblems identified
• Suggestions for enhancing the disaster recovery and/or business continuityplan
• Lessons learned

Communications Fo rm

• It is ve ry important during the disaster recovery and business recovery activities

thatall affected persons and organizations are kept properly informed
• The information given to all parties must be accurate and timely
• In particular, any e s timate of the timing to re turn to normal working operations
should be announced with care
• It is also ve ry important that only authorized personnel deal with media
queries

Groups of Pers ons Selected To Coordinate

Pers ons or Communications
Organizations to Affected Pers ons / Organizations
Affected by Name Position Contact Details
Disruption
Cus tomers
Management &
Staff
Suppliers
Me dia
Stakeholders
O the rs

Returning Recovered Business Operations to Business Unit Leadership

• Once normal business operations have been restored it will be necessary to

re turn the responsibility for specific operations to the appropriate business unit
leader
• This proces s should be formalized in order to ens ure that all parties
unders tand the change in overall responsibility, and the transition to business-
as-usual
• It is likely that during the recovery process, overall responsibility may have been
assigned to the business recovery proces s lead
• It is assumed that business unit management will be fully involved throughout
the
re cove ry, but in order for the recovery proces s to be fully effective, overall
responsibility during the recovery pe riod should probably be with a business
recovery process team
Business Proces s /Function Recovery Completion Fo
rm The following transition form should be completed and signed by the business
recovery team leader and the responsible business unit leader, for each proces s
recovered.

A s eparate form should be used for each recovered business proces s

.
Name Of Business Proces s
Completion Date of Wo rk Provided by
Business Recovery Team
Date of Transition Back to Business
Unit Management
(If different than completion date)

I confirm that the work of the business recovery team has been completed in
accordance with the disaster recovery plan for the above process, and that
normal business operations have been effectively res tored.

Business Recovery Team Leader Name:

Signature:

Date:

(Any relevant comments by the BRT leader in connection with the return of
this business proces s should be made here.)

I confirm that above business proces s is now acceptable for normal working

conditions. Name:

Title:

Signature:

Date:

Courtesy of Micro Focus, Inc.

This document is intended to be a starting point for a potential disaster recovery plan and is a not, in any way, a complete disaster
recovery plan. Micro Focus does not take responsibility for any disaster recovery plans that are based off of this document, nor any
failure due to implementation orexecution of this template.

Acknowledgement to Paul Kirvan of searchdisasterrecovery.com for the inspiration of this template.

135-000078-001