1. The case for a disaster recovery strategy for component XYZ
Proposal by:
Feodor Georgiev,
Role ...,
Team ...

2. Content Background information on component XYZ
Current disaster recovery strategy and risk to business
Proposed disaster recovery strategy and benefits to business
Estimated required resources for proposed changes (cost)

3. Background on component XYZ
Name and sub-components or hosted applications:
Location (if relevant) and team reponsible:
Purpose/ Importance to business:
Highlight what data is stored on the server and what it is worth to the business (i.e. vital for external financial reports, client billing etc)
Highlight business groups using it and if this is their only source for this data
Highlight the business’ key metrics or expectations (if known) regarding Recovery Point Objectives (RPO*) and Recovery Time Objective (RTO**) should a disaster occur
* the maximum tolerable period in which data might be lost from an IT service due to a major incident
** the time duration and a service level within which a business process must be restored after a disaster or disruption in order to avoid unacceptable consequences *

4. Current disaster recovery strategy/plan and risk to business
Highlight current DR strategy (if any)
Highlight what the impact would be to the business should the component break down partially or completely (i.e. Could the business get the data elsewhere and with what delay and manpower? What would be the negative impact of the business – inability to do billing? Delayed reaction to market changes? Bad experience for end customers? etc)

5. Proposed disaster recovery strategy/plan and benefits to business
Highlight proposed DR changes
IT disaster recovery control measures can be classified into the following three types:
Preventive measures - Controls aimed at preventing an event from occurring.
Detective measures - Controls aimed at detecting or discovering unwanted events.
Corrective measures - Controls aimed at correcting or restoring the system after a disaster or an event.
Highlight what the benefits would be to the business with the new changes to the DR strategy should the server break down partially or completely

6. Estimated required resources for proposed changes (cost)
Hardware:
Software:
Estimated duration:
IT staff required:
Impact on business (if any downtime etc):
Impact on IT staff workload (if any, which team):
etc