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
<Company Site Addr1
Site Addr2
Site Addr3
Site Addr4
Postcode>
|
Issued by: |
<Plan Owner> |
|
Version: |
|
|
Date: |
|
|
Copy Number: |
|
<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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
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>.
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.
<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 |
|
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
Hint: The recovery teams defined for a company vary according to the specific needs of that company. Adapt this section to describe the recovery teams applicable for your situation.
This section defines the functional responsibilities of each recovery team.
The names of all the team members are to listed in Section 12.2, Recovery Team Members.
The Disaster Management Team is responsible for providing overall direction of the data centre recovery operations. It ascertains the extent of the damage, activates the recovery organisation and notifies the team leaders. Its prime role is to monitor and direct the recovery effort. It has a dual structure in that its members include Team Leaders of other teams.
The Disaster Management Team Leader is responsible for deciding whether or not the situation warrants the introduction of disaster recovery procedures. If he decides that it does, then the organisation defined in this section comes into force and, for the duration of the disaster, supersedes any current management structures.
The Disaster Management Team operates from the Command Centre.
The Disaster Management Team is responsible for the following:
Making decisions about restoring the computer processing environment in order to provide the identified level of operational service to users.
Managing all the recovery teams and liaising with <Company Name>‘s management, company headquarters and users, as appropriate.
Maintaining audit and security control during the recovery from disaster.
Controlling and recording emergency costs and expenditure.
Evaluating the extent of the problem and potential consequences.
Notifying senior management of the disaster, recovery progress and problems.
Initiating disaster recovery procedures.
Co ordinating recovery operations
Monitoring recovery operations and ensuring that the schedule is met.
Documenting recovery operations.
Liaising with user management.
Expediting authorisation of expenditures by other teams.
Recording emergency extraordinary costs and expenditure
Making a detailed accounting of the damage to aid in insurance claims.
Ensuring that the conversion to the standby facilities and the final resumption of operations at the data centre are under sufficient audit control to provide reliability and consistency to the accounting records.
Monitoring computer security standards.
Ensuring that appropriate arrangements are made to restore the site and return to the status quo within the time limits allowed for emergency mode processing.
Approving the results of audit tests on the applications which are processed at the standby facility shortly after they have been produced.
Performing a detailed audit review of the critical accounting files after the first back up cycle has been completed.
Declaring that the Disaster recovery Plan is no longer in effect when computer processing is restored at the primary site.
The Operations Team is responsible for the computer environment (computer room and other vital computer locations) and for performing tasks within those environments.
This team is responsible for restoring computer processing and for performing computer room activities.
The Operations Team is responsible for the following:
Ensuring that the standby equipment meets the recovery schedules.
Installing the computer hardware and setting up the latest version of the operating system at the standby facility. (This may be done together with the Standby Vendor team.)
Obtaining all appropriate historical/current data from the vault location and restoring an up to date application systems environment.
Providing the appropriate management and staffing of the standby computer processing centre, data control, help desk and media control/tape library in order to meet the defined level of user requirements.
Support operable versions of all critical applications needed to satisfy the minimum operating requirements.
Performing backup activities at the standby site.
Providing on going technical support at the standby facility.
Working with the Networks Team to restore local and wide area data communications services to meet the minimum processing requirements.
Obtaining all necessary back ups from off site storage.
Initiating operations at the standby facility.
Re establishing software libraries and databases to the last backup.
Co-ordinating the user groups to aid the recovery of any non recoverable (i.e. not available on the latest MT dump) data
Providing sufficient personnel to support operations at the standby facility
Re establishing the Help Desk, Data Control and Media Control/Tape Library functions at the standby facilities.
Managing the standby facilities to meet users' requirements
Establishing processing schedule and inform user contacts
Arranging for acquisition and/or availability of necessary computer supplies
Ensuring that all documentation for standards, operations, vital records maintenance, application programs etc. are stored in a secure/safe environment and reassembled at the standby facilities, as appropriate.
The networks team is responsible for all computer networking and communications.
The Networks Team is responsible for the following:
Arranging new local and wide area data communications facilities and a communications network, which links the standby facility to the critical users
Installing a minimum voice network to enable identified critical telephone users to link to the public network.
Evaluate the extent of damage to the voice and data network and discuss alternate communications arrangements with telecoms service providers.
Establish the network at the standby facilities in order to bring up the required operations.
Define the priorities for restoring the network in the user areas.
Order the voice/data communications and equipment as required.
Supervise the line and equipment installation for the new network.
Providing necessary network documentation.
Providing ongoing support of the networks at the standby facility.
Re establish the networks at the primary site when the post disaster restoration is complete.
The Facilities Team is responsible for the general environment including buildings, services and all environmental issues outside of the computer rooms.
This team has responsibility for security, health and safety and for replacement building facilities.
Administering the reconstruction of the original site for recovery and operation
Arranging all transport to the standby facility.
Controlling security at the standby facility and the damaged site. (Note: physical security may need to be increased.)
In conjunction with the Disaster Management Team, evaluating the damage and identifying equipment which can be salvaged.
Working with the Networking Team to have lines ready for rapid activation.
As soon as the standby site is occupied, cleaning up the disaster site and securing that site to prevent further damage.
Supplying information for initiating insurance claims.
Ensuring that insurance arrangements are appropriate for the prevailing circumstances (i.e. any replacement equipment is immediately covered etc.)
Preparing the original data centre for re occupation.
Maintaining current configuration schematics of the Data Centre (stored off site) This should include:
air conditioning
power distribution
electrical supplies and connections
specifications and floor layouts
Controlling security within the disaster area.
Arranging for all necessary office support services.
Dealing with staff safety and welfare.
The Communications Team is responsible for obtaining communications directives from the Disaster Management Team, and communicating information during the disaster and restoration phases to employees, suppliers, customers and the media (Press, TV, radio).
Liaising with the Disaster Management Team to obtain directives on the messages to communicate.
Making statements to local, national and international media, as appropriate.
Informing suppliers and customers of any potential delays.
Informing employees of the recovery progress of the schedules.
Ensuring that there is no mis-communications that could damage the image of the company.
Any other public relations.
Hint: Include a section on any other teams that are defined in the company’s disaster recovery plans. Ensure that you describe each team’s responsibilities and activities.
Other recovery teams may include the following:
Personnel and Purchasing Team
Business Team
Damage Assessment Team
Hint: Include the responsibilities of the Standby Facilities team. This team may be composed, wholly or in part, of personnel from a vendor providing the standby facility.
Hint: you may wish to include your Company standard Fire/Evacuation/Safety procedures in an Appendix or as the main text for 4.1 below.
The most critical and complex part of the management of resources is in the planning and organisation of the required personnel during the invocation of the plan.
Personnel must be well-rehearsed, familiar with the Disaster recovery Plan and be sure of their assignments.
The first priority in a disaster situation is to ensure safe evacuation of all personnel.
In the event of a major physical disruption, standard emergency procedures must be followed. This means immediately:
Activating the standard alarm procedures for that section of the building to ensure that Medical, Security and Safety departments and emergency authorities are correctly alerted.
If necessary, evacuating the premises following the laid down evacuation procedures and assemble outside at the designated location, if it is safe to do so.
The Facilities Team assesses the nature and extent of the problem.
If it is safe to do so, the Operations Team switches off all equipment in the computer room, including air conditioners.
Building Security alerts the Disaster Management Team Leader.
The Facilities Team give an initial assessment to the Disaster Management Team Leader, who needs to know the extent of the damage to the buildings and equipment and the staff status. Also report what actions have been taken.
The Disaster Management Team Leader decides whether to activate the Disaster recovery Plan, and which recovery scenario will be followed.
The recovery teams then follow the defined recovery activities and act within the responsibilities of each team, as defined in this Disaster recovery Plan.
Hint: this section optionally provides the opportunity to specify actions which may be taken if the 'disaster' is less than total. Such a situation may prevail on a large site with multiple buildings - perhaps even with multiple computer rooms in different locations. Clearly, this will be inappropriate in some cases. Remember, the action plans are by way of example only and are not intended to suggest or recommend what you should do.
This section describes the various recovery scenarios that can be implemented, depending on the nature of the disaster and the extent of the damage. The Disaster Management Team Leader decides which recovery scenario to implement when he or she activates the Disaster recovery Plan.
In this scenario, only a part of the computer processing environment is out of action, but the communication lines and network are still up and running. The goal of the recovery process in this case is to move the applications from the systems which are unavailable to the Standby Facility.
In this scenario the building is still available and the users can use normal office space to wait for the restart of computer processing.
|
Task |
Team |
|
Evaluate the damage |
Disaster Management Facilities and Operations |
|
Identify the concerned applications |
Disaster Management and Operations |
|
Request the appropriate resources at the Standby Facility |
Disaster Management |
|
Obtain the appropriate backups |
Operations |
|
Restart the appropriate applications at the Standby Facility |
Operations |
|
Inform users of the new procedures |
Communications |
|
Order replacement equipment to replace the damaged computers. |
Operations |
|
Install replacement equipment and restart the applications |
Operations |
|
Inform users of normal operations |
Communications |
In this scenario, the entire computer processing environment (or most of it) is out of action. Communication lines and the network are out of action.
The goal of the recovery process in this scenario is to move all identified applications to the Standby Facility.
This scenario requires a full recovery procedure, as documented in this Disaster recovery Plan.
This section contains a list of tasks for each of the recovery teams. Sensible judgement must be exercised to determine what activities are appropriate based on the nature and extent of the disruption.
Hint: the timescales used here are for example only and should be modified to suit your Organisation. For example, some production process may require a significant action to be taken every two hours, or there may be something which repeats on a twelve-hour cycle. Modify the timescales and actions to reflect these requirements.
The following table provides an overview of the main responsibilities of each recovery team during the lifecycle of the disaster recovery process. The detailed tasks for each team are listed in the following sections.
|
Phase Team |
|
Site in normal working conditions |
|
Decision to Activate the Plan |
Plan is in Operation |
Return to the Primary Site |
|
|
|
|
|
|
|
|
|
|
|
Disaster |
|
Test the Plan |
D |
Evaluate damage |
Make decisions |
|
|
|
Management |
|
Update the Plan |
I |
Ensure safety |
Co-ordinate activities |
|
|
|
team |
|
|
S |
Call team meeting |
Inform senior management |
|
|
|
|
|
|
A |
|
|
|
|
|
|
|
Test the Plan |
S |
Assess damage |
Salvage operations |
|
|
|
Facilities |
|
|
T |
Attend team meeting |
Security |
|
|
|
team |
|
|
E |
|
Administration services |
|
|
|
|
|
|
R |
Prepare/move to S'by Facility |
Supervise repairs and prepare for |
Supervise re-occupation of Primary |
|
|
|
|
|
|
|
return to Primary Site |
Site or move to new permanent site |
|
|
|
|
|
O |
|
|
|
|
|
Operations |
|
Test the Plan |
C |
Attend team meeting |
Move to Standby Facility |
Reinstate computer processing |
|
|
team |
|
|
C |
Prepare move to Standby Facility |
Operate the Standby Facility |
|
|
|
|
|
|
U |
|
|
|
|
|
Networks |
|
Test the Plan |
R |
Attend team meeting |
Move to Standby Facility |
Reinstate network communications |
|
|
team |
|
|
S |
Prepare/move to S'by Facility |
Operate the Standby Facility |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Test the Plan |
|
Attend team meeting |
Operate 'Crisis Desk' to: Inform suppliers |
|
|
|
Communications |
|
|
|
Set up 'Crisis Desk' |
Inform customers |
|
|
|
team |
|
|
|
|
Inform employees |
|
|
|
|
|
|
|
|
Inform the Press |
|
|
|
|
|
|
|
|
Be the public relations contact generally |
|
|
Receive an initial assessment of the nature and extent of the problem.
Decide whether to activate the Plan.
Alert all Recovery team leaders.
Alert and mobilize all other team members.
Make a preliminary (verbal) report to senior management.
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.
Make a second, more detailed, report to senior management on the content of the meeting and the actions being taken.
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.
Contact the supplier of the standby facilities to invoke the installation as per contract.
Agree installation schedule with the supplier of the standby facility.
Prepare plans for the transition to the standby facility.
Make official declarations (for example, place of work change to any regulatory authorities).
Report progress to senior management.
Act as the main point of contact with the emergency services (Police, Fire, Ambulance).
Monitor on a regular basis all activities to exercise and maintain control over delivery and installation dates.
Document progress against agreed schedules.
Attend the initial meeting called for recovery team leaders.
Alert and mobilize all other team members.
Contact all operations, data preparation, data control and microfiche staff.
Inform all staff of the problem and the actions being taken
Ensure all staff remain calm and understand their roles.
Inform all staff of any temporary instructions.
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.
Report back at the second meeting of recovery team leaders.
Contact suppliers of:
hardware
communications equipment
ancillary equipment.
Inform them of the arrangements for moving to the standby facilities.
Order new equipment and arrange to have it installed in the standby facility.
Initiate 'interim' back up procedures for priority systems (this may involve manual procedures)
Brief all operations staff required to travel to the interim site(s).
Call all user contacts on a regular basis, advising them of the disruption and the actions being taken.
In conjunction with the Facilities Team, monitor the delivery and installation of new/replacement hardware, communications and ancillary equipment.
In the light of the disruption, review all production schedules in terms of jobs to be run, timings, priorities and dependencies.
Prepare production schedules in readiness for start up at the standby site.
Accept hand over of standby site from the Facilities Team.
In conjunction with the Networks Team, initialise and test the systems:
hardware
operating systems
communications network
Before undertaking any processing, take security copies of all files and programs.
Transfer security copies to off site storage location.
Start processing in accordance with prepared production schedules.
Discontinue work at any interim site(s).
Alert and mobilize all other team members.
Attend the initial meeting called for recovery team leaders.
Contact relevant staff with a networks responsibility, inform them of the problem and the actions being taken.
Ensure that all staff remain calm and understand their roles.
Inform networks staff of any temporary instructions.
Help to compile an inventory of surviving communications equipment (voice/data) and that to be acquired.
Ensure that all relevant documentation is at hand or retrieved from the off site storage facility, for the reinstatement of the network.
Liaise with the Operations Team as to the status of communications equipment and assist with acquiring replacement equipment if required.
Provide further information to enable the Communications Team to keep users informed of current position if required.
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.
Liaise with the Standby Facility and telecom service providers to monitor progress of communications reinstatement.
Report back at the second meeting of recovery team leaders.
Define the priorities for restoring the network on a gradual basis in order to provide a minimum initial communications requirement for normal operations.
Liaise with suppliers of communications equipment to ensure prompt delivery, if required.
In conjunction with the Operations Team, ensure that the reinstated communications network is operable and tested.
Provide ongoing support for the communications network and carry out any re configuration of the reinstated network that may be necessary.
Attend the third meeting of the disaster recovery team leaders and report the restoration status.
In conjunction with the Operations Team, monitor the network's performance.
Monitor and deal with users' requests in the light of the restricted network.
Prepare an inventory of all communications equipment requiring replacement in order for the original computer processing environment to be re utilised.
Order replacement equipment as required (in conjunction with the Disaster Management Team for. expenditure approval).
Provide an initial damage report to the Disaster Management Team Leader.
Alert and mobilize all other team members.
Attend the initial meeting called for recovery team leaders.
Conduct an asset inventory.
Make a full evaluation of the damage.
In conjunction with the Operations Team identify all potentially salvageable equipment.
Carry out safety inspections.
Make the site secure, to prevent unauthorised access by staff or the public.
Estimate the time required to recover.
Report back at the second meeting of recovery team leaders.
Provide the required facilities at the Command Centre.
Arrange hotel or other temporary accommodation for staff.
Set up transport arrangements to/from all temporary locations.
Set up an Administration Support Desk to handle all queries.
Transfer staff to temporary locations.
Remove vital documents from disaster site.
Remove re usable equipment from disaster site.
Set up administrative support services:
secretarial typing/word processing
telephones
telex/fax
mail internal/external
office equipment
stationery
Remove salvaged items from the disaster area.
Set up security procedures at the standby facility.
Contact suppliers of essential services (electricity, gas, water) and make any arrangements required as a result of the disruption.
Supervise delivery and installations at the standby facility.
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.
Provide office furniture for the standby facility if required.
In conjunction with the Operations Team, transfer tapes, discs, documentation, stationery from off site store to standby facility.
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.
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.
Liaise with the Management Disaster team to agree on the information to be communicated.
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)
If applicable, make calls to customers and inform them of any potential delays.
If applicable, issue a statement to local, national and international Press, as appropriate.
Advise all user departments of the transition plans and the arrangements during the period prior to the actual transition.
Handle all public relations.
Hint: Repeat this section for all the other recovery teams which are part of your solution.
This section describes the Command Centre, from where the Disaster Management Team will direct disaster recovery operations.
If the <Company Name> premises at <Company Address> are intact following the disaster, the command centre will be located at:
<Location of primary command centre>.
If an alternative command centre is necessary, the command centre will be located at:
<Location of alternative command centre>.
The following command centre resources are required, and will be supplied by the team indicated.
Hint: This is not intended to be a definitive list, but may contain a few suggestions which you find helpful.
|
Item: |
To be supplied by team: |
|
Disaster recovery Plan |
|
|
Whiteboard / flip chart & stand |
|
|
Petty Cash |
|
|
Computer Users Year Book |
|
|
Telecom telephone directory |
|
|
Desks, chairs |
Facilities |
|
< > telephone lines |
Networks |
|
< > dedicated lines |
|
|
Mobile phones |
Networks |
|
Fax machine |
Facilities |
|
Photocopier |
Facilities |
|
Shredder |
Facilities |
|
Tool kit (cables and plugs) |
Facilities |
|
Office supplies |
Facilities |
|
Refreshments (coffee, tea and so on) |
Facilities |
|
Camp beds |
Facilities |
|
Shower facility |
Facilities |
|
Car parking |
Facilities |
|
First aid kit |
Facilities |
|
Refrigerator |
Facilities |
|
Microwave oven |
Facilities |
Hint: state if the Standby Facility is for computer processing only, or whether it also provides some office space. If you use an external Company to provide this facility, you may find standard information supplied to enable you to use the service will fit well into this section.
This section provides a general introduction to the standby facility which the <Company Name> can utilise for computer processing <and office space> following a disaster.
It provides detailed information on preparing the facility.
This information includes the following:
Network (data and voice communications)
Hardware configurations
Security
The address of the Standby Facility is:
Instructions on how to get to the Standby Facility are as follows:
Hint: Where standby facilities are provided by a vendor on a commercial basis, the vendor may require written confirmation of the invocation of the service. Therefore be prepared to provide typically the following details.
The following form is used to confirm the invocation of the Standby Facilities. It must be completed by the Disaster Management Team Leader and communicated to the Standby Facility Vendor at <Vendor address, fax number, phone number>.
|
Company Name: |
|
|
Address:
|
|
|
Telephone Number: |
|
|
Disaster Alert
|
|
|
Designated Site: |
|
|
Nature of Disaster: |
|
|
Estimated Duration of Usage of the Standby Facility: |
|
|
Date Usage to Start: |
|
|
Name: |
|
|
Signature:
|
|
|
Date: |
|
This section describes the location(s) of the vault facilities where secure copies of data backups and other vital information are stored.
|
Location and address: |
|
|
Contact person: |
|
|
Contact phone number: |
|
|
Number of vault/safe: |
|
|
Type of vault/safe: |
|
|
Maximum capacity: |
|
|
Content: |
|
|
Location and address: |
|
|
Contact person: |
|
|
Contact phone number: |
|
|
Number of vault/safe: |
|
|
Type of vault/safe: |
|
|
Maximum capacity: |
|
|
Content: |
|
Hint: The Class 1 applications correspond to the ‘must have’ and the Class 2 to the ‘want’ applications as defined in the Business Impact Assessment.
This section describes the system requirements for <Company Name>’s critical business applications in the Standby Facility.
It is divided into two sections: Class 1 systems (“must-have”) and Class 2 systems (important), with the timescales for these systems to support the business.
Refer to Section 12.4, User Groups and Application Support, for the names of the application owner.
|
Timescale |
Application |
System Requirements |
Number of Users |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Timescale |
Application |
System
Requirements |
Number of Users |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
Supplies required are as follows:
|
Item |
Location/Vendor |
Comments |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|
|
Other equipment required is as follows:
|
Item |
Location/Vendor |
Comments |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
Service |
Phone |
Address |
|
Police |
|
|
|
Fire |
|
|
|
Hospitals |
|
|
|
Gas |
|
|
|
Gas Escapes |
|
|
|
Electricity |
|
|
|
Electricity Supply Enquiries (24 hours) |
|
|
|
Water |
|
|
|
Burst Pipes/ |
|
|
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.
|
Name |
Work Phone |
Home Phone |
Pager/other contact info |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Name |
Work Phone |
Home Phone |
Pager/other contact info |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Name |
Work Phone |
Home Phone |
Pager/other contact info |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Name |
Work Phone |
Home Phone |
Pager/other contact info |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Name |
Work Phone |
Home Phone |
Pager/other contact info |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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>.
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 |
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|
|
|
|
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.
|
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 |
|
|
|
|
|
|
|
|
|
Device |
Model, Description, Number |
Quantity |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Supplier |
Name, Version, etc. |
Qty |
License no. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Manufacturer |
Name of Operating System, Version |
No of licences |
|
|
|
|
|
|
|
|
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
The reference documentation includes:
Data backup procedures
Type(s) of backups
Means of identification
Length of time that backups are kept
Frequency of backups
Times when backups are performed
Method of rotating sets of backups
Emergency procedures
Fire
Bomb
Flood
Power Failure
Evacuation
First Aid