1 Document Control
1.1 Document distribution
1.2 Document revision
1.3 Document approval
2 Supporting Information
2.1 Introduction
2.2 Recovery strategy
2.3 Invocation
2.4 General guidance
2.5 Dependencies
2.6 Recovery team
2.7 Recovery team checklist
3 Recovery Procedure
This document must be maintained to ensure that the systems, Infrastructure and facilities included, appropriately support business recovery requirements.
Copy |
Issued to |
Date |
Position |
1 |
|||
2 |
|||
3 |
|||
4 |
|||
This document will be reviewed every X months.
Current Revision: date
Next Revision: date
Revision |
Version No |
Summary of Changes |
This document must be approved by the following personnel.
Name |
Title |
Signature |
This document details the instructions and procedures that are required to be followed to recover or continue the operation of systems, Infrastructure, Services or facilities to maintain Service Continuity to the level defined or agreed with the business.
The systems, Infrastructure, Services or facilities will be recovered to alternative systems, Infrastructure, services or facilities.
It will take approximately X hours to recover the systems, Infrastructure, services or facilities. The System will be recovered to the last known point of stability/data integrity, which is point in day/timing.
The required recovery time for this system, Infrastructure, Service or facility is:
The recovery time and procedures for this system, Infrastructure, service or facility was last tested on:
The following personnel are authorised to invoke this plan
1.
All requests for information from the media or other sources should be referred to the Company procedure.
When notifying personnel of a potential or actual disaster follow the defined operational escalation procedures, and in particular:
All activities and contact/escalation should be clearly and accurately recorded. To facilitate this, actions should be in a checklist format and there should be space to record the date and time the activity was started and completed, and who carried out the activity.
System, Infrastructure, Service, facility or Interface dependencies should be documented (in Priority order) so that related recovery plans or procedures that will need to be invoked in conjunction with this recovery plan can be identified and actioned. The person responsible for Invocation should ensure recovery activities are co-ordinated with these other plans.
System |
Document Reference |
Contact |
The following staff/functions are responsible for actioning these procedures or ensuring the procedures are actioned and recording any issues or problems encountered. Contact will be made via the normal escalation procedures.
Name |
Title |
Contact Details |
To facilitate the execution of key activities in a timely manner, a checklist similar to the following should be used.
Task |
Target |
Actual |
Confirm Invocation has taken place |
||
Initiate call tree and establish recovery team |
||
Identify issues and advise Crisis management Team |
||
Arrange for backup media, vital records to be shipped from off-site store to recovery site |
||
Establish recovery team rota |
||
Confirm progress reporting requirements |
||
Inform recovery team of reporting requirements |
||
Confirm liaison requirements with other recovery teams |
||
Initiate recovery actions |
||
Advise the estimate for System recovery and commencement of testing |
||
Advise estimate for when systems will be ready for User processing. |
||
Enter recovery instructions/procedures here.
Content/format should be in-line with company standards for procedures. If there are none, guidance should be issued by the Manager or Team Leader for the area responsible for the System, Infrastructure, Services or facility. The only guideline is that the instructions should be capable of being executed by an experienced professional without undue reliance on local knowledge.
Where necessary, references should be made to supporting documentation (and its location), diagrams and other information sources. This should include the document reference number (if it exists). It is the responsibility of the plan author to ensure that this information is maintained with this plan. If there is only a limited amount of supporting information, it may be easier for this to be included within the plan, providing this plan remains easy to read/follow and does not become too cumbersome.