K: The Typical Contents Of A Recovery Plan
The typical contents of an ITSCM recovery plan are as follows.
GENERIC RECOVERY PLAN
1. DOCUMENT CONTROL
This document must be maintained to ensure that the systems, Infrastructure and far Titles included, approprately support business recovery requirements.
1.1 Document distribution
| Copy | Issued to | Date | Position
|
| 1. | | |
|
| 2. | | |
|
| 3. | | |
|
| 4. | | |
|
1.2 Document revision
This document will be reviewed every X months. Current Revision: date
Next Revision: date
| Revision Date | Version No | Summary of Changes
|
| | |
|
| | |
|
| | |
|
| | |
|
1.3 Document approval
This document must be approved by the following personnel:
2 SUPPORTING INFORMATION
2.1 Introduction
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.
2.2 Recovery strategy
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, services or facility was last tested on: ______________
2.3 Invocation
The following personnel are authorized to invoke this plan:
1.
2.
2.4 Interfaces and dependencies on other plans
Details of the inter-relationships and references with all other continuity and recovery plans and how the interfaces are activated.
2.5 General guidance
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:
- Be calm and avoid lengthy conversation
- Advise them of the need to refer information requests to escalation point
- Advise them of expectations and actions (avoid giving them details of the Incident unless absolutely necessary
- If the call is answered by somebody else:
- Ask if the contact is available elsewhere
- If they cannot be contacted, leave a message to contact you on a given number
- Do not provide details of the incident
- Always document call time details, responses and actions.
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.
2.6 Dependencies
System, Infrastructure, service, facility or interface dependencies should he 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 coordinated with these other plans.
| System | Document Reference | Contact
|
| | |
|
| | |
|
| | |
|
| | |
|
2.7 Contact lists
Lists of all contact names, organizations and contact details and mechanisms:
| Name | Organization/Role | Title | Contact Details
|
| 1. | | |
|
| 2. | | |
|
| 3. | | |
|
| 4. | | |
|
2.8 Recovery team
The following staff/functions are responsible for actioning them procedure or ensure the procedures are actioned and recording any issues or problems encountered. Contact will be made via the normal escalation procedures.
2.9 Recovery team checklist
to facilitate the execution of key activities in a timely manner, a checklist similar to the following should he used.
| Task | Target completion | Actual completion
|
| Confirm Invocation | |
|
| Initiate call tree and
escalation procedures | |
|
| Instigate and interface with any
ether recovery plans necessary
e.g. BCP, Crisis Management,
Emergency Response Plan) | |
|
| Arrange for backup media and
documentation to be shipped
to recovery site(s) | |
|
| Establish recovery teams | |
|
| Initiate recovery actions | |
|
| Confirm progress reporting | |
|
| Inform recovery team of
reporting requirements | |
|
| Confirm liaison requirements
with all recovery teams | |
|
| Advise customers and management of estimated recovery completion | |
|
3 RECOVERY PROCEDURE
Enter recovery instructions/procedures or references to all recovery 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.
![[To top of Page]](../../../images/up.gif)
