Disaster Recovery

Overview

Disaster Recovery Planning is the act of formulating a program that would be followed in the event a catostrophic event should occur that would severely disrupt a business. A Disaster Recovery Plan (or DRP) is assembled with step-by-step instructions on the actions that should be taken to ensure continuity of business systems in the event of a disaster. The DRP is a document which is meant to suppliment an organizations broader Business Continuity Plan (BCP).

Why Should You Plan for Disaster?

Disaster can strike any organization, and it can hit in a variety of different forms. Whether it be a ransomware attack that encrypts all of your organizations critical data, or a natural disaster causes power loss to the location your servers are hosted in, critical disasters can hit organizations of all shapes and sizes.

The Disaster Recovery Planning process provides a litany of benefits to organizations. It allows upper management to see the process in which systems would be restored in the event of a disaster, and clarity as to how long that process would take. For IT professionals it provides a clear directive as to how to proceed in the event a disaster should occur and exactly which systems should be given priority to restore.

How does the Process Work?

The assembly a Disaster Recovery Plan is an involved process that often involves many business units within an organization. Our team will meet with various parties within the organization and carry out the following tasks:

  • Determine which systems are within scope for the Disaster Recovery Plan, and which are not.
  • Discuss how much data loss is acceptable in the event of a disaster, and how much down-time is acceptable. These metrics are known as Recovery Point Objectives (RPOs) and Recovery Time Objectives (RTOs) respectively.
  • Assess the current backup and recovery plans within the organization and determine whether or not they can provide RPO's and RTO's that align with the business' objectives.
  • Assemble a list of all hardware that would need to be replaced in the event of a failure, and determine the quickest method to replace it.
  • Put together a call tree that would be followed in a critical event, as well as other important external contacts that may need to be contacted.
  • Assemble a detailed report detailing the steps that should be taken in a disaster, and how to restore systems back to a fully operational state.