For information about AUTOMATED disaster recovery planning, deployment, and implementation, or assistance with your disaster recovery planning, deployment, or Implementation projects, please contact: or Mt Xia Inc.

Our primary focus is Business Continuity, Disaster Recovery, High Availability, Virtualization, and Datacenter Automation in large worldwide environments.

The Template Disaster Recovery Plan follows:

Company

Logo

Disaster Recovery Plan

<Company Name>

<Company Site Addr1

Site Addr2

Site Addr3

Site Addr4

Postcode>

<Company Name> Confidential

Instructions for Using This Template

This template Disaster Recovery Plan is a typical example of the contents of a plan document, which will help you save time when writing your own. However, ALL of this plan is designed to be CUSTOMIZED for the solution designed specifically for your company. In particular, the teams, timescales and responsibilities are for example ONLY and are not necessarily recommendations. Note also that some of the teams referred to may be only one person.

The layout has been designed to be easy to navigate, but, again, you may wish to modify it, particularly the cover page, to suit a house style.

The document contains some hints for writing your own plan; these are in bold italic text. Remember to delete these paragraphs, together with these instructions, when you finalize your plan.

When you have written your plan, remember to:

• Customize the footer in the first two sections (Header and Footer on the View menu).

• Search for < to ensure that you have entered appropriate text in all placeholders.

• Regenerate the table of contents and the cross references (Select All with Ctrl A and press F9).

Version 1.2 May 2001

Table of Contents

Plan Revision History

It is important that this Disaster recovery Plan accurately reflects the current situation and business requirements at <Company Name>. Updates must be provided to <Plan Owner>

The following table describes the history of this document.

Version	Date Issued	Reason for Update

1.About This Disaster Recovery Plan

Hint: Clearly define the scope of the plan. For example, the plan may cover the company’s computer processing only, or it may be broader and extend to environmental and safety issues.

1.1.Purpose and Scope of This Plan

This plan has been designed and written to be used in the event of a disaster affecting <Company name> at <Company Site Address>.

This plan is structured around teams, with each team having a set of specific responsibilities.

The decision to initiate disaster recovery procedures will be taken by the Disaster Management Team Leader or his deputy after assessing the situation following a disaster or crisis.

If the Disaster Management Team Leader decides to initiate disaster recovery procedures, then all members of the recovery teams will follow the procedures contained in this plan until recovery is complete.

This plan contains all the information necessary to restore an operational service in the event of a serious disruption of computer services at <Company Site>.

1.2.Updating This Plan

This plan must be kept up to date.

It is the responsibility of <Plan Owner> to ensure that procedures are in place to keep this plan up to date. If, whilst using the plan, you find any information which is incorrect, missing or if you have a problem in understanding any part of this plan please inform <Plan Owner> so that it may be corrected. It is important that everyone understands their role as described in this plan.

Updated versions of the plan are distributed to the authorised recipients, listed in Section 1.3, Distribution List.

1.3.Distribution List

<Plan Owner> is responsible for distributing this plan. Each plan holder, listed in the table below, receives two copies of this plan. One copy is to be kept at the place of work and the other copy at home or other safe offsite location. These copies have an official copy number.

Each team leader must ensure that each team member has two copies of the plan.

Name	Copy Number
<Disaster Management Team Leader>
<Operations Team Leader>
<Network Team Leader>
<Facilities Team Leader>
Offsite Copy 1
Offsite Copy 2

2.Plan Objectives

A disaster is defined as an incident which results in the loss of computer processing at the <Company Name> site at <Location>, to the extent that relocation to a Standby Facility must be considered. A disaster can result from a number of accidental, malicious or environmental events such as fire, flood, terrorist attack, human error, software or hardware failures.

The primary objective of this Disaster recovery Plan is to ensure the continued operation of identified business critical systems in the event of a disaster.

Specific goals of the plan are :

• To be operational at the standby facility within <X> working days of a standby invocation

• To operate at the standby facility for up to <DEFINED PERIOD OF TIME>

• To reinstate <Company Name> facilities in the <Company Name> premises within the maximum working standby period

• To minimize the disruption to <Company Name>’ s business

6.2.Disaster Management Team Tasks

6.2.1.Immediate

1. Receive an initial assessment of the nature and extent of the problem.

2. Decide whether to activate the Plan.

3. Alert all Recovery team leaders.

4. Alert and mobilize all other team members.

5. Make a preliminary (verbal) report to senior management.

6. Call an initial meeting of the recovery team leaders with the following objectives:

• To define the problem, the extent of the disruption, its consequences and the probable implications for the foreseeable future.

• To set up a specified location as a Control Centre.

• To agree each team's objectives for the next three hours.

• To set up a second meeting for three hours later.

7. Make a second, more detailed, report to senior management on the content of the meeting and the actions being taken.

6.2.2.Within Three Hours

8. Call a second meeting of the recovery team leaders with the following objectives:

• To receive initial reports from the recovery team leaders.

• To take the decision to implement disaster recovery procedures.

• To agree each team's objectives for the next twenty four hours.

• To set up a third meeting for twenty four hours later.

6.2.3.Within Twenty Four Hours

9. Contact the supplier of the standby facilities to invoke the installation as per contract.

10. Agree installation schedule with the supplier of the standby facility.

11. Prepare plans for the transition to the standby facility.

12. Make official declarations (for example, place of work change to any regulatory authorities).

13. Report progress to senior management.

6.2.4.Ongoing

14. Act as the main point of contact with the emergency services (Police, Fire, Ambulance).

15. Monitor on a regular basis all activities to exercise and maintain control over delivery and installation dates.

15. Document progress against agreed schedules.

6.3.Operations Team Tasks

6.3.1.Immediate

1. Attend the initial meeting called for recovery team leaders.

2. Alert and mobilize all other team members.

6.3.2.Within Three Hours

3. Contact all operations, data preparation, data control and microfiche staff.

4. Inform all staff of the problem and the actions being taken

5. Ensure all staff remain calm and understand their roles.

6. Inform all staff of any temporary instructions.

7. Inform all user contacts of the nature and extent of the problem. telling them that they will be kept informed of the plans to recover.

8. Report back at the second meeting of recovery team leaders.

6.3.3.Within Twenty Four Hours

9. Contact suppliers of:

• hardware

• communications equipment

• ancillary equipment.

9. Inform them of the arrangements for moving to the standby facilities.

10. Order new equipment and arrange to have it installed in the standby facility.

11. Initiate 'interim' back up procedures for priority systems (this may involve manual procedures)

12. Brief all operations staff required to travel to the interim site(s).

6.3.4.Ongoing

14. Call all user contacts on a regular basis, advising them of the disruption and the actions being taken.

15. In conjunction with the Facilities Team, monitor the delivery and installation of new/replacement hardware, communications and ancillary equipment.

16. In the light of the disruption, review all production schedules in terms of jobs to be run, timings, priorities and dependencies.

17. Prepare production schedules in readiness for start up at the standby site.

18. Accept hand over of standby site from the Facilities Team.

19. In conjunction with the Networks Team, initialise and test the systems:

• hardware

• operating systems

• communications network

14. Before undertaking any processing, take security copies of all files and programs.

15. Transfer security copies to off site storage location.

16. Start processing in accordance with prepared production schedules.

17. Discontinue work at any interim site(s).

6.4.Networks Team Tasks

6.4.1.Immediate

1. Alert and mobilize all other team members.

2. Attend the initial meeting called for recovery team leaders.

6.4.2.Within Three Hours

3. Contact relevant staff with a networks responsibility, inform them of the problem and the actions being taken.

4. Ensure that all staff remain calm and understand their roles.

5. Inform networks staff of any temporary instructions.

6. Help to compile an inventory of surviving communications equipment (voice/data) and that to be acquired.

7. Ensure that all relevant documentation is at hand or retrieved from the off site storage facility, for the reinstatement of the network.

8. Liaise with the Operations Team as to the status of communications equipment and assist with acquiring replacement equipment if required.

9. Provide further information to enable the Communications Team to keep users informed of current position if required.

10. Ensure that all documentation/ information is available for the Operations and Facilities teams in order to connect the voice, local and wide area network to the standby facility.

11. Liaise with the Standby Facility and telecom service providers to monitor progress of communications reinstatement.

12. Report back at the second meeting of recovery team leaders.

6.4.3.Within Twenty Four Hours

13. Define the priorities for restoring the network on a gradual basis in order to provide a minimum initial communications requirement for normal operations.

14. Liaise with suppliers of communications equipment to ensure prompt delivery, if required.

15. In conjunction with the Operations Team, ensure that the reinstated communications network is operable and tested.

16. Provide ongoing support for the communications network and carry out any re configuration of the reinstated network that may be necessary.

17. Attend the third meeting of the disaster recovery team leaders and report the restoration status.

6.4.4.Ongoing

18. In conjunction with the Operations Team, monitor the network's performance.

19. Monitor and deal with users' requests in the light of the restricted network.

20. Prepare an inventory of all communications equipment requiring replacement in order for the original computer processing environment to be re utilised.

21. Order replacement equipment as required (in conjunction with the Disaster Management Team for. expenditure approval).

6.5.Facilities Team Tasks

6.5.1.Immediate

1. Provide an initial damage report to the Disaster Management Team Leader.

2. Alert and mobilize all other team members.

3. Attend the initial meeting called for recovery team leaders.

6.5.2.Within Three Hours

4. Conduct an asset inventory.

5. Make a full evaluation of the damage.

6. In conjunction with the Operations Team identify all potentially salvageable equipment.

7. Carry out safety inspections.

8. Make the site secure, to prevent unauthorised access by staff or the public.

9. Estimate the time required to recover.

10. Report back at the second meeting of recovery team leaders.

6.5.3.Within Twenty Four Hours

11. Provide the required facilities at the Command Centre.

12. Arrange hotel or other temporary accommodation for staff.

13. Set up transport arrangements to/from all temporary locations.

14. Set up an Administration Support Desk to handle all queries.

15. Transfer staff to temporary locations.

16. Remove vital documents from disaster site.

17. Remove re usable equipment from disaster site.

6.5.4.Ongoing

18. Set up administrative support services:

• secretarial   typing/word processing

• telephones

• telex/fax

• mail   internal/external

• office equipment

• stationery

18. Remove salvaged items from the disaster area.

19. Set up security procedures at the standby facility.

20. Contact suppliers of essential services (electricity, gas, water) and make any arrangements required as a result of the disruption.

21. Supervise delivery and installations at the standby facility.

22. Monitor the installation of:

• electricity

• heating/lighting

• air conditioning

• fire detection systems

• access control systems

• telephones.

if these need to be provided at the standby facility.

19. Provide office furniture for the standby facility if required.

20. In conjunction with the Operations Team, transfer tapes, discs, documentation, stationery from off site store to standby facility.

6.6.Communications Team Tasks

Hint: be sure that the Communications Team has a clear understanding of its own role and that of the other teams, to ensure no duplication of effort and/or issuing of conflicting information.

6.6.1.Immediate

Alert and mobilize all other team members.

Attend the initial meeting called for the recovery team leaders.

Set up the Crisis Desk to handle all communications.

6.6.2.Within Three Hours

1. Liaise with the Management Disaster team to agree on the information to be communicated.

2. If applicable, make initial calls to suppliers of the following and inform them of the disruption and the likely demands to be made on their time and services:

• standby facility

• hardware

• software

• communications equipment

• other equipment

• utilities (electricity, gas, water)

3. If applicable, make calls to customers and inform them of any potential delays.

4. If applicable, issue a statement to local, national and international Press, as appropriate.

6.6.3.Within Twenty Four Hours

5. Advise all user departments of the transition plans and the arrangements during the period prior to the actual transition.

6.6.4.Ongoing

6. Handle all public relations.

6.7.<Other Recovery Teams> Tasks

Hint: Repeat this section for all the other recovery teams which are part of your solution.

6.7.1.Immediate

6.7.2.Within Three Hours

6.7.3.Within Twenty-Four Hours

6.7.4.Ongoing

10.1.Class 1 Systems

Timescale	Application	System Requirements (Hardware, Software, Communications, Data, Documentation)	Number of Users

10.2.Class 2 Systems

Timescale	Application	System Requirements (Hardware, Software, Communications, Data, Documentation)	Number of Users

11.Supplies for the Standby Facility

This section contains checklists of all supplies, documentation and equipment you need to obtain for the Standby Facility for business survival (such as billing stationery). It lists what you need and where to obtain it.

Hint: again, you are reminded that these are not recommendations and you should decide and note here what is appropriate to your needs.

11.1.Supplies

Supplies required are as follows:

Item	Location/Vendor	Comments (e.g. duration of stock, supplier response time)

11.2.Documentation

The Systems documentation required is as follows:

Item	Location/Vendor	Comments
System Specifications
Program Specifications
File Specifications
Record Specifications
Support Manuals

The Operations documentation required is as follows:

Item	Location/Vendor	Comments
Operations Standards And Procedures
Operations Manuals
Run Instructions
Job Control Sheets
Sample Input Documents
Networks Documentation

11.3.Other Equipment

Other equipment required is as follows:

Item	Location/Vendor	Comments

12.Directories

Hint: The information in this section may often be stored and maintained in a database tool. If so, this section will include printed reports obtained from the software.

This section of the plan contains a series of directories.

These directories contain the type of information which is most likely to change   such as names, addresses, telephone numbers etc.

It is important to keep these directories up to date.

12.1.Emergency Services

Service	Phone	Address
Police
Fire
Hospitals
Gas
Gas Escapes (24 hours)
Electricity
Electricity Supply Enquiries (24 hours)
Water
Burst Pipes/ Emergencies (24 hour)

12.2.Recovery Team Members

There are <> recovery teams.

The staffing of these Recovery Teams is listed in this section. The team leader is the first name in the list, in the shaded box.

12.2.1.Disaster Management Team: Members and Contacts

Name	Work Phone	Home Phone	Pager/other contact info

12.2.2.Operations Team: Members and Contacts

Name	Work Phone	Home Phone	Pager/other contact info

12.2.3.Networks Team: Members and Contacts

Name	Work Phone	Home Phone	Pager/other contact info

12.2.4.Facilities Team: Members and Contacts

Name	Work Phone	Home Phone	Pager/other contact info

12.2.5.Communications Team: Members and Contacts

Name	Work Phone	Home Phone	Pager/other contact info

12.3.First Aiders

For First Aid during office hours, contact <Name> at <Contact Number>.

If a first aider is not immediately available, contact the Emergency ambulance service by dialling <emergency service telephone number>.

12.4.User Groups and Application Support

Hint: This table lists the users who can provide support for each application. Ensure that there is a user contact listed for each critical business application that is defined in Section 10, Critical Business Applications.

System/Application	Contact	Phone

12.5.Vendor and Supplier Contacts

This section lists all the key vendors and suppliers who need to be contacted following a disaster.

Hint: Adapt this list as necessary.

Requirement	Contact/ Company	Phone /Fax (working hours)	Phone outside working hours	Contract no. if any
Field Service
Hardware
Data communications
Voice communications
Wide Area Network Equipment
Software
Magnetic Media
Office Equipment
Furniture
Banking
Air Conditioning
Fire Protection/ Detection
Computer Room Cleaning
Disc Pack Cleaning/ Checking
Decollator/ Guillotine Service
Fire Safe Maintenance
Salvage Contracting Services
Transport (Car/Truck hire)
Courier Services
Portable office buildings
Stationery

13.Inventories

Hint: The information in this section may be stored and maintained in a database or other type of software tool. If so, this section may include printed reports obtained from the software. Many Organisations will have this information recorded as an Asset Register. You may wish to include the Asset Number assigned to any item. Keeping this information accurate will help with administration of any Insurance claims.

This section contains inventories of all computer hardware, software and other equipment.

13.1.Computer Hardware

Manufacturer	Model, Description, Number	Qty
	Mainframes/Processors/Servers
	Workstations
	PCs
	Disk drives
	Tape drives
	Printers
	Network equipment

Hint: The tables below are in an alternative, more complete format for listing the hardware inventory.
Duplicate the table as necessary.

MAINFRAMES/SERVERS	Identifier such as Scary	Sporty	Ginger etc.
Manufacturer
Model, Description, Number, Code
Capital Value as Asset
Rental Cost
Capital Value for Insurance
Maintenance Contract Number
Contract Expiry Date
Rental Contract No.
Location, Department
Supply Date
WORKSTATIONS	Identifier	Identifier	Identifier
Manufacturer
Model, Description, Number, Code
Capital Value as Asset
Rental Cost
Capital Value for Insurance
Maintenance Contract Number
Contract Expiry Date
Rental Contract No.
Location, Department
Supply Date

PCs	Family Type 1	Family Type 2	Family Type 3
Manufacturer
Model, Description, Number, Code
Capital Value as Asset
Rental Cost
Capital Value for Insurance
Maintenance Contract Number
Contract Expiry Date
Rental Contract No.
Location, Department
Supply Date
Quantity

DISK DRIVES	Family Type 1	Family Type 2	Family Type 3
Manufacturer
Model, Description, Number, Code
Capital Value as Asset
Rental Cost
Capital Value for Insurance
Maintenance Contract Number
Contract Expiry Date
Rental Contract No.
Location, Department
Supply Date
Quantity

TAPE DRIVES	Family Type 1	Family Type 2	Family Type 3
Manufacturer
Model, Description, Number, Code
Capital Value as Asset
Rental Cost
Capital Value for Insurance
Maintenance Contract Number
Contract Expiry Date
Rental Contract No.
Location, Department
Supply Date
Quantity

PRINTERS	Family Type 1	Family Type 2	Family Type 3
Manufacturer
Model, Description, Number, Code
Capital Value as Asset
Rental Cost
Capital Value for Insurance
Maintenance Contract Number
Contract Expiry Date
Rental Contract No.
Location, Department
Supply Date
Quantity

NETWORK EQUIPMENT	Item 1	Item 2	Item 3
Manufacturer
Model, Description, Number, Code
Capital Value as Asset
Rental Cost
Capital Value for Insurance
Maintenance Contract Number
Contract Expiry Date
Rental Contract No.
Location, Department
Supply Date

13.2.Non-computer Equipment

13.3.Software Inventory

13.4.Operating Systems

14.Related Documentation

This section contains references to other key documentation which must be copied and kept in the vault location, together with < > copies of this Disaster recovery Plan.

Hint: for example:

• Production Schedules

• Insurance Policies

• Planning Permission Documents

• Site Plans

• Network Diagrams