Scroll down to view The Template Disaster Recovery Plan:

FREE DEMO: Automated Unix / Linux Deployment As A Service


We will participate in your Disaster Recovery Implementation or Test Exercises as emergency AIX Administrators

If you have a disaster and require additional AIX administrators, call us, we can be on-site in a matter of hours, or work remotely within minutes. If your Disaster Recovery Test Exercise requires using AIX administrators who are not familiar with your specific environment, call us. We can provide multiple Advanced AIX Experts for your DR test exercises.

Dana French, President, Mt Xia Inc., (email) (+1 615 556 0456)

Mr French's primary focus is business continuity, disaster recovery, high availability (HACMP, PowerHA), virtualization (VIO,APV,PowerVM), data center migration, and data center automation (vLPAR) in large IBM AIX data center environments. He consults with many of the worlds largest organizations regarding data center automation, data center and server consolidation, business function consolidation and outsourcing, and a variety of other cost saving techniques.

We Perform Short Term Project Work

If you only need some Advanced AIX Administration assistance for a short term project, please give me a call. We perform project work for companies world wide at very inexpensive rates.

We fill-in for vacationing or vacant AIX Administration roles

If you need an AIX administrator for a vacationing employee, or for a vacant AIX position you are attempting to fill, please call us. We will provide an Advanced AIX Administrator to fill-in for this role.

The Template Disaster Recovery Plan follows:


Company

Logo












Disaster Recovery Plan

<Company Name>


<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:





























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 :



3.Recovery Teams and Responsibilities

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.



3.1.Disaster Management Team

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.

3.1.1.Disaster Management Team Charter

The Disaster Management Team is responsible for the following:

3.1.2.Responsibilities



3.2.Operations Team

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.

3.2.1.Operations Team Charter

The Operations Team is responsible for the following:

3.2.2.Responsibilities



3.3.Networks Team

The networks team is responsible for all computer networking and communications.

3.3.1.Networks Team Charter

The Networks Team is responsible for the following:

3.3.2.Responsibilities



3.4.Facilities Team

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.

3.4.1.Facilities Team Charter

3.4.2.Responsibilities



3.5.Communications Team

3.5.1.Communications Team Charter

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).

3.5.2.Responsibilities



3.6.<Other Recovery Teams>

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:





3.6.1.<Other Recovery Team> Charter



3.6.2.Responsibilities





3.7.Standby Facilities 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.



3.7.1.Standby Facilities Team Charter



3.7.2.Responsibilities





4.What To Do in the Event of a Disaster

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.



4.1.Standard Emergency Procedures

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:



4.2.The First Steps for the Recovery Teams



4.3.The Next Steps

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.



5.Recovery Scenarios

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.



5.1.Scenario One: Minor Damage

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.

5.1.1.Action Plan

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



5.2.Scenario Two: Major Damage

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.



6.Recovery Activities

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.

6.1.Overview of the Tasks for Each Team

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
(Standby Facility)

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


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:

  1. 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

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

6.2.3.Within Twenty Four Hours

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

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

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

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

  5. Report progress to senior management.

6.2.4.Ongoing

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

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

  1. 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

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

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

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

  4. Inform all staff of any temporary instructions.

  5. 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.

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

6.3.3.Within Twenty Four Hours

  1. Contact suppliers of:

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

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

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

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

6.3.4.Ongoing

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

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

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

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

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

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

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

  2. Transfer security copies to off site storage location.

  3. Start processing in accordance with prepared production schedules.

  4. 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

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

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

  3. Inform networks staff of any temporary instructions.

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

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

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

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

  8. 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.

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

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

6.4.3.Within Twenty Four Hours

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

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

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

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

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

6.4.4.Ongoing

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

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

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

  4. 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

  1. Conduct an asset inventory.

  2. Make a full evaluation of the damage.

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

  4. Carry out safety inspections.

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

  6. Estimate the time required to recover.

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

6.5.3.Within Twenty Four Hours

  1. Provide the required facilities at the Command Centre.

  2. Arrange hotel or other temporary accommodation for staff.

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

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

  5. Transfer staff to temporary locations.

  6. Remove vital documents from disaster site.

  7. Remove re usable equipment from disaster site.

6.5.4.Ongoing

  1. Set up administrative support services:

  1. Remove salvaged items from the disaster area.

  2. Set up security procedures at the standby facility.

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

  4. Supervise delivery and installations at the standby facility.

  5. Monitor the installation of:

if these need to be provided at the standby facility.

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

  2. 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:

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

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

6.6.3.Within Twenty Four Hours

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

6.6.4.Ongoing

  1. 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



7.The Command Centre

This section describes the Command Centre, from where the Disaster Management Team will direct disaster recovery operations.



7.1.Primary Command Centre

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>.



7.2.Alternative Command Centre

If an alternative command centre is necessary, the command centre will be located at:

<Location of alternative command centre>.



7.3.Command Centre Requirements

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



8.The Standby Facility

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:



8.1.Location of the Standby Facility

The address of the Standby Facility is:



Instructions on how to get to the Standby Facility are as follows:







8.2.Standby Alert Confirmation Sheet

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
Agreement Number:


Designated Site:


Nature of Disaster:


Estimated Duration of Usage of the Standby Facility:


Date Usage to Start:


Name:


Signature:



Date:


9.The Data Storage Location(s)

This section describes the location(s) of the vault facilities where secure copies of data backups and other vital information are stored.

9.1.Storage Location 1



Location and address:


Contact person:


Contact phone number:


Number of vault/safe:


Type of vault/safe:


Maximum capacity:


Content:




9.2.Storage Location 2



Location and address:


Contact person:


Contact phone number:


Number of vault/safe:


Type of vault/safe:


Maximum capacity:


Content:


10.Critical Business Lessons

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.



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



Device

Model, Description, Number

Quantity





















13.3.Software Inventory



Supplier

Name, Version, etc.

Qty

License no.























13.4.Operating Systems



Manufacturer

Name of Operating System, Version

No of licences







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:

The reference documentation includes: