This Document Usage
This document is to be used as a template for creating the Disaster Recovery Checklist for a service or application. Replace <any text that looks like this> for example <SERVICE or APP name> with the actual values needed for the service or application. This is used to signify a placeholder value that requires to be updated for the specific technology. Delete this entire section for the finalized checklist.
Any areas that looks like below are providing guidance for that section in the template and should be delete when the checklist is finalized.
EXAMPLE OF GUIDANCE SECTION
Business Function
GUIDANCE FOR BUSINESS FUNCTION SECTION. DELETE THIS PORTION ONCE INPUTTED
This section should provide a short description of the business function of the application or service being supported. In addition, the customer(s) of the application or service should be identified. It is enough to identify departments and teams. The goal is provide a layperson context of the application or service.
Key Information
GUIDANCE FOR KEY INFORMATION SECTION. DELETE THIS PORTION ONCE INPUTTED
Include references to any information required to successfully execute this DRP, such as:
- Configuration files
- Inventory files
- Links to consoles, tools, web sites or wiki pages (consider if they are expected to be available in the considered disaster scenarios!)
- LastPass links for required credentials
- Vendor upport contacts
IMPORTANT: DO NOT INCLUDE ANY SENSITIVE INFORMATION HERE, SUCH AS PERSONAL PHONE NUMBERS OR ADDRESSES, FINANCIAL DATA, CONFIDENTIAL AGREEMENTS, PASSWORD, API KEYS OR ANY OTHER TYPE OF SECRET.
Recovery Checklist & Dependencies
GUIDANCE FOR RECOVERY CHECKLIST SECTION. DELETE THIS PORTION ONCE INPUTTED
Below is the recovery table. The first column (Status) adds a checkbox to track completion of the task in that row. The second column (Task Summary) should include a short summary of the task. This should only contain a few words. The last column (Task Details) should include all the details need to complete the specific task. Someone who is not an expert on the system should have enough context to execute the task. See below for a simple example.
| Status | Task Summary | Task Details |
|---|---|---|
| ☐ | Log into AWS | Log into the AWS Console using this link |
| ☐ | Restore RDS from Snapshot | Select the latest snapshot for the ETL Prod Job under RDS. Use the steps in this guide from AWS to restore the snapshot |
The following tables provide the step-by-step recovery checklist that the ACE Infra team can use to guide them through the recovery steps for <SERVICE or APP name>. Tasks to verify the functionality of the recovered service are included
| Status | Task Summary | Task Details |
|---|---|---|
| ☐ | <Provide a short summary of task 1> | <Details of task 1> |
| ☐ | <Provide a short summary of task 2> | <Details of task 2> |
| ☐ | <Provide a short summary of task 3 | <Details of task 3> |