Disaster Recovery
Disaster recovery prepares an organization to restore critical technology services and data after a severe, prolonged disruption.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/disaster-recovery/
01What it means
Disaster recovery, or DR, is the set of plans, architectures, responsibilities, and tested procedures used to restore technology after events that normal high-availability mechanisms cannot absorb. It addresses priorities, dependencies, alternate environments, backups, communications, and two central targets: recovery time and acceptable data loss.[1][2]
- 01PrioritizeCritical services, data, dependencies
- 02Set objectivesDowntime and acceptable data loss
- 03Protect recovery assetsBackups, credentials, alternate resources
- 04Restore in orderDeclare, communicate, recover, validate
- 05Exercise + improveMeasure actual performance and gaps
Recovery time addresses restoration speed; acceptable data loss addresses the recovery point. Both must be tested, not assumed.
02Why it matters
Major regional outages, destructive changes, cyber incidents, and facility loss can exceed routine incident procedures. Recovery decisions made for the first time under pressure are slow and error-prone. DR planning makes business priorities explicit and tests whether backups, access, capacity, dependencies, and people can support restoration.
03When to use it
Maintain DR capability for services whose prolonged loss or data corruption would create unacceptable business, safety, regulatory, or customer consequences. The strategy should follow a business impact analysis. Not every workload needs active-active infrastructure; the recovery approach should match its required recovery time objective and recovery point objective.
04How it works
- Identify critical services, data, dependencies, owners, and acceptable downtime and data loss.
- Choose recovery patterns and alternate resources that can meet those objectives.
- Protect backups and recovery credentials from the same failures as production.
- Document declaration, communication, restoration order, validation, and return-to-normal procedures.
- Exercise the plan regularly, record actual recovery performance, and correct gaps.
05A practical example
A payroll platform targets restoration within four hours with no more than fifteen minutes of transaction loss. It maintains encrypted cross-region backups and infrastructure definitions, rehearses recovery in an isolated account, validates balances before reopening access, and records that a manual identity dependency threatens the target.
06Where it breaks
A written plan is not demonstrated recoverability. Backups may be corrupt, dependencies unavailable, or restored data inconsistent. Lower recovery times and data-loss targets generally cost more and add complexity. Exercises can also disrupt teams, so scope and cadence should reflect risk without becoming a checkbox ritual.
Common mistakes
- Assuming high availability or backups alone constitute disaster recovery.
- Setting recovery objectives without business impact or dependency analysis.
- Testing restoration components separately but never exercising the end-to-end service.
07Sources
- Contingency Planning Guide for Federal Information SystemsNational Institute of Standards and Technology · Government guidanceContingency Planning Guide for Federal Information Systems
- Disaster Recovery of Workloads on AWSAmazon Web Services · Cloud architecture whitepaperDisaster Recovery of Workloads on AWS