Disaster Recovery Report

When we do the DR drills requested by the company or external parties (regulator, compliance, risk, etc.), the team is confused about what contents need to be there and commonly the company doesn’t have a standard template to record that.

Therefore, today, I will discuss what content must be in the report and why.

[1] Referential documents

Before going to the actual document, there should be a document supporting the DR drills. The represented documents are below

• Service Level Objective of the service: This is an important figure as it will decide the pass/fail of the DR. You may describe the expectation from the business like the essential (critical) user journey to be available during the DR (It is not necessary to cover all services during the incident/disaster). Plus, you should have requirements like RTO, and RPO collectively considered by multiple respected departments. (Product, security, legal, etc.)
• Playbook: The playbook must be included as you won’t randomly troubleshoot on the production where the decision comes out as a disaster so you will need to run your DR site instead of recovering the production site. The step-by-step instructions and the permission required for the actions and Eta. expected time period to perform each step.

[2] Executive Summary and Introduction

This section provides a high-level overview of the entire document. It includes the purpose of…