SearchDisasterRecovery_IT_DisasterRecoveryTemplate.doc

8/14/2019 SearchDisasterRecovery_IT_DisasterRecoveryTemplate.doc

1/34

IT Disaster Recovery PlanTemplate

By Paul Kirvan, CISA, CISSP, FBCI,CBCP


2/34

Revision History

REVISION DATE NAME DESCRIPTION

Original 1.0

2


3/34

Table of Contents

By Paul Kirvan, CISA, CISSP, FBCI, CBCP......................................................................1

Information Technology Statement of Intent.......................................................................5Policy Statement.................................................................................................................. 5

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

Key Personnel Contact Info................................................................................................. 6

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

External Contacts................................................................................................................. 8

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

1 Plan Overview.................................................................................................................11

1.1 Plan Updating...........................................................................................................11

1.2 Plan Documentation Storage....................................................................................11

1.3 Backup Strategy....................................................................................................... 111.4 Risk Management.................................................................................................... 11

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

2.1 Alert, escalation and plan invocation.......................................................................12

2.1.1 Plan Triggering Events..................................................................................... 12

2.1.2 Assembly Points...............................................................................................12

2.1.3 Activation of Emergency Response Team........................................................12

2.2 Disaster Recovery Team.......................................................................................... 13

2.3 Emergency Alert, Escalation and DRP Activation.................................................. 13

2.3.1 Emergency Alert............................................................................................... 13

2.3.2 DR Procedures for Management.......................................................................142.3.3 Contact with Employees................................................................................... 14

2.3.4 Backup Staff......................................................................................................14

2.3.5 Recorded Messages / Updates.......................................................................... 14

2.3.7 Alternate Recovery Facilities / Hot Site........................................................... 14

2.3.8 Personnel and Family Notification................................................................... 14

3 Media.............................................................................................................................. 15

3.1 Media Contact......................................................................................................... 15

3.2 Media Strategies......................................................................................................15

3.3 Media Team............................................................................................................. 15

3.4 Rules for Dealing with Media..................................................................................15

4 Insurance ........................................................................................................................ 15

5 Financial and Legal Issues.............................................................................................. 16

5.1 Financial Assessment...............................................................................................16

5.2 Financial Requirements........................................................................................... 16

5.3 Legal Actions........................................................................................................... 16

6 DRP Exercising...............................................................................................................16

Appendix A Technology Disaster Recovery Plan Templates ........................................17

3


4/34

Disaster Recovery Plan for ................................................................... 17

Disaster Recovery Plan for ...................................................................19

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

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

Disaster Recovery Plan for Remote Connectivity......................................................... 25

Disaster Recovery Plan for Voice Communications..................................................... 27Appendix B Suggested Forms........................................................................................ 29

Damage Assessment Form.............................................................................................29

Management of DR Activities Form..............................................................................29

Disaster Recovery Event Recording Form.................................................................... 30

Disaster Recovery Activity Report Form...................................................................... 30

Mobilizing the Disaster Recovery Team Form .............................................................31

Mobilizing the Business Recovery Team Form ............................................................31

Monitoring Business Recovery Task Progress Form ....................................................32

Preparing the Business Recovery Report Form ............................................................ 32

Communications Form ..................................................................................................33

Returning Recovered Business Operations to Business Unit Leadership..................... 33

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

4


5/34

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

infrastructure. This document summarizes our recommended procedures. In the event of anactual emergency situation, modifications to this document may be made to ensure physical

safety of our people, our systems, and our data.

ur mission is to ensure information system uptime, data integrity and availability, and business

continuity.

Policy Statement

!orporate management has approved the following policy statement"

The company shall develop a comprehensive IT disaster recovery plan.

# formal ris$ assessment shall be underta$en to determine the re%uirements for the

disaster recovery plan.

The disaster recovery plan should cover all essential and critical infrastructure

elements, systems and networ$s, in accordance with $ey business activities.

The disaster recovery plan should be periodically tested in a simulated environment to

ensure that it can be implemented in emergency situations and that the managementand staff understand how it is to be e&ecuted.

#ll staff must be made aware of the disaster recovery plan and their own respective

roles.

The disaster recovery plan is to be $ept up to date to ta$e into account changingcircumstances.

Objectives

The principal ob'ective of the disaster recovery program is to develop, test and documenta well-structured and easily understood plan which will help the company recover as

%uic$ly and effectively as possible from an unforeseen disaster or emergency which

interrupts information systems and business operations. #dditional ob'ectives include the

following"

The need to ensure that all employees fully understand their duties in implementingsuch a plan

The need to ensure that operational policies are adhered to within all plannedactivities

The need to ensure that proposed contingency arrangements are cost-effective The need to consider implications on other company sites (isaster recovery capabilities as applicable to $ey customers, vendors and others

)


6/34

Key Personnel Contact Info

Name, Title Contact Option Contact Number

*or$

#lternate

+obile

ome

mail #ddress

#lternate mail

*or$

#lternate

+obile

ome

mail #ddress

#lternate mail

*or$#lternate

+obile

ome

mail #ddress

#lternate mail

*or$

#lternate

+obile

ome

mail #ddress

#lternate mail

*or$

#lternate

+obile

ome

mail #ddress

#lternate mail

*or$

#lternate

+obile

ome

mail #ddress

#lternate mail


7/34

Notification Calling Tree

/

Person

Identifying

Incident


8/34

External Contacts


Landlord / Property Manager

#ccount 0umber 0one

*or$+obile

ome

mail #ddress

Power Company

#ccount 0umber *or$

+obile

ome

mail #ddress

Telecom Carrier 1

#ccount 0umber *or$

+obile1a&

ome

mail #ddress

Telecom Carrier 2

#ccount 0umber *or$

+obile

ome

mail #ddress

Hardware Supplier 1

#ccount 0umber *or$

+obile

mergency eporting

mail #ddress

Serer Supplier 1

#ccount 0umber. *or$

+obile

1a&

mail #ddress

!or"#tation Supplier 1

#ccount 0umber *or$

+obileome

mail #ddress

O$$ice Supplie# 1

#ccount 0umber !3)/53 *or$

+obile

ome

mail #ddress

5


9/34


%n#urance & Name

#ccount 0umber *or$

+obile

ome

mail #ddress

Site Security &

#ccount 0umber *or$

+obile

ome

mail #ddress

O$$'Site Storage 1

#ccount 0umber *or$

+obile

ome

mail #ddress

O$$'Site Storage 2#ccount 0umber 6ser I(

7assword

ome

mail #ddress

H()C &

#ccount 0umber *or$

+obile

ome

mail #ddress

Power *enerator &

#ccount 0umber *or$

+obile

ome

mail #ddress

Ot+er &

#ccount 0umber *or$

+obile

ome

mail #ddress


10/34

External Contacts Calling Tree

8


11/34

1 Plan Overview

11 Plan !"#ating

It is necessary for the (7 updating process to be properly structured and controlled.*henever 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 (irector.

1$ Plan %oc&mentation Storage

!opies of this 7lan, !(, and hard copies will be stored in secure locations to be defined

by the company. ach member of senior management will be issued a !( and hard copyof this plan to be filed at home. ach member of the (isaster ecovery Team and the

9usiness ecovery Team will be issued a !( and hard copy of this plan. # master

protected copy will be stored on specific resources established for this purpose.

1' (ac)&" Strategy

:ey business processes and the agreed bac$up strategy for each are listed below. The

strategy chosen is for a fully mirrored recovery site at the company;s offices in


12/34

results of our deliberations are included in this section. ach potential environmental

disaster or emergency situation has been e&amined. The focus here is on the level of

business disruption which could arise from each type of disaster.

7otential disasters have been assessed as follows"

Potential %isaster Probability +ating Im"act +ating(rief %escri"tion Of PotentialConse0&ences +eme#ial

,ctions

Flood ( ) #ll critical e*uipment is locatedon +st Floor

Fire ( ) FM, suppression systeminstalled in main computercenters. Fire and smo&edetectors on all floors.

Tornado /

Electrical storms /

#ct of terrorism /

#ct of sa'otage /

Electrical powerfailure

( ) !edundant 0PS array togetherwith auto stand'y generator

that is tested wee&ly % remotelymonitored ,)12. 0PSs alsoremotely monitored.

3oss of communications networ&services

) ) Two diversely routed T+ trun&sinto 'uilding. $#4 redundancy5voice networ& resilience

Pro'a'ility6 +78ery High5 /78ery 3ow Impact6 +7Total destruction5 /7Minor annoyance

$ Emergency +es"onse

$1 ,lert2 escalation an# "lan invocation

2.1.1 Plan TriggeringEvents

:ey trigger issues at head%uarters that would lead to activation of the (7 are" Total loss of all communications Total loss of power 1looding of the premises ?oss of the building

2.1.2 AssemblyPoints

*here the premises need to be evacuated, the (7 invocation plan identifies twoevacuation assembly points"

7rimary @ 1ar end of main par$ing lotA #lternate @ 7ar$ing lot of company across the street

2.1.3 Activationof EmergencyResponseTeam

*hen an incident occurs the mergency esponse Team =T> must be activated. The

T will then decide the e&tent to which the (7 must be invo$ed. #ll employees must

82


13/34

be issued a Buic$ eference card containing T contact details to be used in the event

of a disaster. esponsibilities of the T are to"

espond immediately to a potential disaster and call emergency servicesA #ssess the e&tent of the disaster and its impact on the business, data center, etc.A

(ecide which elements of the ( 7lan should be activatedA stablish and manage disaster recovery team to maintain vital services and return tonormal operationA

nsure employees are notified and allocate responsibilities and activities as re%uired.

$$ %isaster +ecovery Team

The team will be contacted and assembled by the T. The teamCs responsibilities

include" stablish facilities for an emergency level of service within 2. business hoursA estore $ey services within 4. business hours of the incidentA

ecover to business as usual within 5. to 24. hours after the incidentA !oordinate activities with disaster recovery team, first responders, etc. eport to the emergency response team.

$' Emergency ,lert2 Escalation an# %+P ,ctivation

This policy and procedure has been established to ensure that in the event of a disaster or

crisis, personnel will have a clear understanding of who should be contacted. 7rocedures

have been addressed to ensure that communications can be %uic$ly established whileactivating disaster recovery.

The ( plan will rely principally on $ey members of management and staff who willprovide the technical and management s$ills necessary to achieve a smooth technology

and business recovery. Duppliers of critical goods and services will continue to support

recovery of business operations as the company returns to normal operating mode.

2.3.1 EmergencyAlert

The person discovering the incident calls a member of the mergency esponse Team in

the order listed"

mergency esponse Team

E


14/34

The mergency esponse Team =T> is responsible for activating the (7 for disasters

identified in this plan, as well as in the event of any other occurrence that affects the

company;s capability to perform normally.

ne of the tas$s during the early stages of the emergency is to notify the (isaster

ecovery Team =(T> that an emergency has occurred. The notification will re%uest(T members to assemble at the site of the problem and will involve sufficient

information to have this re%uest effectively communicated. The 9usiness ecovery Team

=9T> will consist of senior representatives from the main business departments. The9T ?eader will be a senior member of the companyCs management team, and will be

responsible for ta$ing overall charge of the process and ensuring that the company

returns to normal wor$ing operations as early as possible.

2.3.2 DR Proceduresfor Management

+embers of the management team will $eep a hard copy of the names and contact

numbers of each employee in their departments. In addition, management team members

will have a hard copy of the company;s disaster recovery and business continuity planson file in their homes in the event that the head%uarters building is inaccessible, unusable,

or destroyed.

2.3.3 Contact with Employees

+anagers will serve as the focal points for their departments, while designated

employees will call other employees to discuss the crisisFdisaster and the company;s

immediate plans. mployees who cannot reach staff on their call list are advised to call

the staff member;s emergency contact to relay information on the disaster.

2.3.4 BackupStaff

If a manager or staff member designated to contact other staff members is unavailable or

incapacitated, the designated bac$up staff member will perform notification duties.

2.3.5 RecordedMessages/ Updates

1or the latest information on the disaster and the organization;s response, staff members

can call a toll-free hotline listed in the (7 wallet card. Included in messages will be

data on the nature of the disaster, assembly sites, and updates on wor$ resumption.

2.3.7 AlternateRecoveryFacilities / Hot Site

If necessary, the hot site at DunGard will be activated and notification will be given via

recorded messages or through communications with managers. ot site staffing willconsist of members of the disaster recovery team only for the first 24 hours, with other

staff members 'oining at the hot site as necessary.

2.3.8 Personneland Family Notification

If the incident has resulted in a situation which would cause concern to an employee;s

immediate family such as hospitalization of in'ured persons, it will be necessary to notify

their immediate family members %uic$ly.

84


15/34

' /e#ia

'1 /e#ia Contact#ssigned staff will coordinate with the media, wor$ing according to guidelines that have

been previously approved and issued for dealing with post-disaster communications.

'$ /e#ia Strategies8. #voiding adverse publicity2. Ta$e advantage of opportunities for useful publicity

3. ave answers to the following basic %uestions"

*hat happenedH

ow did it happenH

*hat are you going to do about itH

'' /e#ia Team


16/34

4 3inancial an# 5egal Iss&es

41 3inancial ,ssessment

The emergency response team shall prepare an initial assessment of the impact of the

incident on the financial affairs of the company. The assessment should include"

?oss of financial documents

?oss of revenue

Theft of chec$ boo$s, credit cards, etc.

?oss of cash

4$ 3inancial +e0&irements

The immediate financial needs of the company must be addressed. These can include"

!ash flow position

Temporary borrowing capability

6pcoming payments for ta&es, payroll ta&es, Docial Decurity, etc.

#vailability of company credit cards to pay for supplies and services re%uired post-

disaster

4' 5egal ,ctions

The company legal department and T will 'ointly review the aftermath of the incidentand decide whether there may be legal actions resulting from the eventA in particular, the

possibility of claims by or against the company for regulatory violations, etc.

6 %+P Exercising

(isaster recovery plan e&ercises are an essential part of the plan development process. Ina (7 e&ercise no one passes or failsA everyone who participates learns from e&ercises @

what needs to be improved, and how the improvements can be implemented. 7lan

e&ercising ensures that emergency teams are familiar with their assignments and, more

importantly, are confident in their capabilities.

Duccessful ( plans launch into action smoothly and effectively when they are needed.This will only happen if everyone with a role to play in the plan has rehearsed the roleone or more times. The plan should also be validated by simulating the circumstances

within which it has to wor$ and seeing what happens.

8


17/34

,""en#ix , 7 Technology %isaster +ecovery Plan Tem"lates

%isaster +ecovery Plan for 8System One9SST-M

O(-.(%-!

P.O0CT%

ON S-.(-.

?ocation"

Derver +odel"

perating Dystem"

!76s"

+emory"

Total (is$"

Dystem andle"Dystem Derial J"

(0D ntry"

I7 #ddress"

ther"

HOT S%T- S-.(-. 7rovide details)PPL%C)T%ONS

=6se bold for ot Dite>

)SSOC%)T- S-.(-.S

- CONT)CTS

ardware Kendor 7rovide details

Dystem wners 7rovide details

(atabase wner 7rovide details

#pplication wners 7rovide details

Doftware Kendors 7rovide details

ffsite Dtorage 7rovide details

)C0P ST.)T-* 3O.

SST-M ON-

(aily 7rovide details

+onthly 7rovide details

Buarterly 7rovide details

SST-M ON-

%S)ST-. .-CO(-.

P.OC-0.-

Dcenario 8

Total ?oss of (ata

7rovide details

Dcenario 2

Total ?oss of *

7rovide details

8/


18/34

,%%EN%!/

CONT)CTS

3ile Systems 8#ate9

3ile Sy#tem a# o$

4date5

+inimal file systems to

be created and restored

from bac$up"

L?istM

3ile#y#tem "byte# 0#ed )ail 6u#ed Mounted on

L7rovide detailsM

ther critical files to

modify

L7rovide detailsM

0ecessary directories to

create

L7rovide detailsM

!ritical files to restore L7rovide detailsM

Decondary files to

restore

L7rovide detailsM

ther files to restore L7rovide detailsM

85


19/34

%isaster +ecovery Plan for 8System Two9SST-M

O(-.(%-!

P.O0CT%ON S-.(-.

?ocation"

Derver +odel"perating Dystem"

!76s"

+emory"Total (is$"

Dystem andle"

Dystem Derial J"

(0D ntry"

I7 #ddress"

ther"

HOT S%T- S-.(-. 7rovide details

)PPL%C)T%ONS

=6se bold for ot Dite>

)SSOC%)T- S-.(-.S

- CONT)CTS







)C0P ST.)T-* $or

SST-M

T!O

(aily 7rovide details+onthly 7rovide details


SST-M T!O

%S)ST-. .-CO(-.

P.OC-0.-

Dcenario 8

Total ?oss of (ata

7rovide details

Dcenario 2

Total ?oss of *

7rovide details

8


20/34

,%%EN%!/

CONT)CTS

3ile Systems 8#ate9

1ile Dystem as of

LdateM



from bac$up"

L?istM


L7rovide detailsM


modify

L7rovide detailsM


create

L7rovide detailsM


Decondary files to

restore

L7rovide detailsM


2


21/34

%isaster +ecovery Plan for 5ocal ,rea Networ) :5,N;

SST-M

O(-.(%-!

S-.(-. ?ocation"Derver +odel"

perating Dystem"

!76s"

+emory"

Total (is$"

Dystem andle"Dystem Derial J"

(0D ntry"

I7 #ddress"

ther"

HOT S%T- S-.(-. 7rovide details

)PPL%C)T%ONS

=6se bold for ot Dite>)SSOC%)T- S-.(-.S

- CONT)CTS







)C0P ST.)T-* $or

SST-M

T!O




SST-M T!O

%S)ST-. .-CO(-.

P.OC-0.-

Dcenario 8

Total ?oss of (ata

7rovide details

Dcenario 2

Total ?oss of *

7rovide details

28


22/34

,%%EN%!/

CONT)CTS

3ile Systems 8#ate9

1ile Dystem as of

LdateM



from bac$up"

L?istM


L7rovide detailsM


modify

L7rovide detailsM


create

L7rovide detailsM


Decondary files to

restore

L7rovide detailsM


22


23/34

%isaster +ecovery Plan for


24/34

,%%EN%!/

CONT)CTS

S&""ort Systems 8#ate9

Dupport system L7rovide detailsM

!ritical networ$ assets L7rovide detailsM

!ritical interfaces L7rovide detailsM


!ritical networ$

services to restore

L7rovide detailsM

ther services L7rovide detailsM

24


25/34

%isaster +ecovery Plan for +emote Connectivity

SST-M

O(-.(%-!

-70%PM-NT ?ocation"(evice Type"

+odel 0o."

Technical Dpecifications"

0etwor$ Interfaces"

7ower e%uirementsA

Dystem Derial J"(0D ntry"

I7 #ddress"

ther"

HOT S%T- -70%PM-NT 7rovide details

SP-C%)L )PPL%C)T%ONS

)SSOC%)T- -(%C-S

- CONT)CTS







0etwor$ Dervices 7rovide details

)C0P ST.)T-* $or

SST-M

T!O




SST-M T!O

%S)ST-. .-CO(-.

P.OC-0.-

Dcenario 8

Total ?oss of 0etwor$

7rovide details

Dcenario 2

Total ?oss of *

7rovide details

2)


26/34

,%%EN%!/

CONT)CTS






!ritical networ$

services to restore

L7rovide detailsM


2


27/34

%isaster +ecovery Plan for =oice Comm&nications

SST-M

O(-.(%-!

-70%PM-NT ?ocation"

(evice Type"+odel 0o."

Technical Dpecifications"

0etwor$ Interfaces"

7ower e%uirementsA

Dystem Derial J"

(0D ntry"I7 #ddress"

ther"

HOT S%T- -70%PM-NT 7rovide details

SP-C%)L )PPL%C)T%ONS

)SSOC%)T- -(%C-S

- CONT)CTSardware Kendor 7rovide details






0etwor$ Dervices 7rovide details

)C0P ST.)T-* $or

SST-M

T!O




SST-M T!O

%S)ST-. .-CO(-.

P.OC-0.-

Dcenario 8

Total ?oss of Dwitch

7rovide details

Dcenario 2

Total ?oss of 0etwor$

7rovide details

2/


28/34

,%%EN%!/

CONT)CTS






!ritical networ$

services to restore

L7rovide detailsM


25


29/34

,""en#ix ( 7 S&ggeste# 3orms

%amage ,ssessment 3orm

Key (&sinessProcess ,ffecte#

%escri"tion Of Problem Extent Of %amage

>>>>>>>>>>>>>

/anagement of %+ ,ctivities 3orm

(uring the disaster recovery process all activities will be determined using a standardstructureA

*here practical, this plan will need to be updated on a regular basis throughout thedisaster recovery periodA

#ll actions that occur during this phase will need to be recorded.

,ctivity Name?

+eference N&mber?

(rief %escri"tion?

Commencement%ate@Time

Com"letion%ate@Time

+eso&rces Involve# In Charge

999999999999999999

2


30/34

%isaster +ecovery Event +ecor#ing 3orm

#ll $ey events that occur during the disaster recovery phase must be recorded. #n 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 copyof 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

record all $ey events during disaster recovery, until such time as responsibility ishanded over to the business recovery team.

%escri"tion of %isaster?

Commencement %ate?

%ate@Time %+ Team /obiliAe#?

,ctivities !n#erta)en by %+Team

%ate an#Time

O&tcome3ollowBOn ,ction

+e0&ire#

%isaster +ecovery Teams


31/34

The report will include" # description of the emergency or incident Those people notified of the emergency =including dates> #ction ta$en by members of the (T

utcomes arising from actions ta$en #n assessment of the impact to normal business operations #ssessment of the effectiveness of the 9!7 and lessons learned ?essons learned

>>>>>>>>>>

/obiliAing the %isaster +ecovery Team 3orm

1ollowing an emergency re%uiring recovery of technology infrastructure assets, thedisaster recovery team should be notified of the situation and placed on standby.

The format shown below can be used for recording the activation of the ( team

once the wor$ of the damage assessment and emergency response teams has beencompleted.

%escri"tion of Emergency?

ate Occurred6

ate $or& of isaster !ecovery Team "ompleted6

Name of Team/ember

Contact%etails

Contacte# On:Time @ %ate;

(y >>>>>>>>>

/obiliAing the (&siness +ecovery Team 3orm

1ollowing an emergency re%uiring 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 wor$ of the disaster recovery team has been completed.

%escri"tion of Emergency?

ate Occurred6

ate $or& of >usiness !ecovery Team "ompleted6

Name of Team/ember

Contact%etails

Contacte# On:Time @ %ate;

(y


32/34

!elevant "omments >>>>>>>>>>>

/onitoring (&siness +ecovery Tas) Progress 3orm

The progress of technology and business recovery tas$s must be closely monitoredduring this period of time.

Dince difficulties e&perienced by one group could significantly affect other dependenttas$s it is important to ensure that each tas$ is ade%uately resourced and that the

efforts re%uired to restore normal business operations have not been underestimated.

Note: A priority sequence must be identified although, where possible, activities will be carried out

simultaneously.

!ecovery Tas&s


33/34

#n assessment of the impact to normal business operations

7roblems identified

Duggestions for enhancing the disaster recovery andFor business continuity plan

?essons learned

Comm&nications 3orm

It is very important during the disaster recovery and business recovery activities that

all affected persons and organizations are $ept properly informed.

The information given to all parties must be accurate and timely.

In particular, any estimate of the timing to return to normal wor$ing operations

should be announced with care.

It is also very important that only authorized personnel deal with media %ueries.

?roups of Persons orOrgani@ations #ffected

'y isruption

Persons Selected To "oordinate "ommunicationsto #ffected Persons 1 Organi@ations

4ame Position "ontact etails

"ustomers

Management % Staff

Suppliers

Media

Sta&eholders

Others

>>>>>>>>>>>>

+et&rning +ecovere# (&siness O"erations to (&siness !nit5ea#ershi"

nce normal business operations have been restored it will be necessary to return the

responsibility for specific operations to the appropriate business unit leader.

This process should be formalized in order to ensure that all parties understand the

change in overall responsibility, and the transition to business-as-usual.

It is li$ely that during the recovery process, overall responsibility may have been

assigned to the business recovery process lead.

It is assumed that business unit management will be fully involved throughout the

recovery, but in order for the recovery process to be fully effective, overall

responsibility during the recovery period should probably be with a business recovery

process team.

>>>>>>>>>>>>

33


34/34

(&siness Process@3&nction +ecovery Com"letion 3orm

The following transition form should be completed and signed by the business recoveryteam leader and the responsible business unit leader, for each process recovered.

# separate form should be used for each recovered business process.

Name Of (&siness Process

Com"letion %ate of

Date post:	04-Jun-2018
Category:	Documents
Upload:	arturo-de-lira-delgado
View:	220 times
Download:	0 times

SearchDisasterRecovery_IT_DisasterRecoveryTemplate.doc

Documents