liveBook · Manning

Disaster recovery

As explained in Fundamentals of Cybersecurity

Disaster recovery is the process of restoring critical information-technology systems, applications, data, and services after a disruptive event.

Disaster recovery (DR) restores critical IT systems, applications, data, and services after a disruption. Equipment failure, a security incident, or a natural disaster can interrupt the technology an organization needs to operate. DR focuses on getting that technology working again; business continuity focuses on keeping essential business functions going. section 7.0 section 7.5

Recovery follows a pre-approved Disaster Recovery Plan (DRP), not a set of decisions invented during the emergency. The plan assigns responsibilities and gives procedures for restoring operations to a last-known reliable state: one confirmed free of errors or corruption. Depending on the disruption, those procedures might activate redundant systems, restore backups, or move operations to an alternate site. section 7.0 section 7.1

A usable DRP brings several decisions together:

  • Set recovery objectives. Recovery Time Objective (RTO) and Recovery Point Objective (RPO) define acceptable downtime and data loss. section 7.6
  • Give people instructions suited to their roles. Executive summaries, department plans, technical guides, and checklists serve different needs during recovery. section 7.1
  • Protect recoverable data. Full, differential, and incremental backups, along with snapshots, are data-recovery options. section 7.6
  • Choose recovery infrastructure to fit the required speed and budget. Options include cold, warm, hot, and mirrored sites; a backup site far from the primary site reduces the chance that one event affects both. section 7.6 section 7.3

A disrupted workplace

Suppose a flood affects an organization's primary site. Its recovery team follows assigned DRP roles, restores data from backups, and, if needed, shifts operations to a prepared alternate site. The goal is to bring critical technology back to a reliable state so business operations can continue. section 7.0 section 7.1

A written plan still needs testing and maintenance. In a tabletop exercise, team members discuss what they would do without actually recovering systems. Simulations test selected procedures hands-on, while parallel tests run backup systems alongside production. Regular exercises expose gaps, outdated information, and incorrect assumptions before a real disruption; the plan and its instructions should then be updated. section 7.4 section 7.8

How Fundamentals of Cybersecurity covers it

How deep it goes
Explains documented roles, recovery choices, and testing methods, but does not provide a complete system-specific recovery procedure.
Examples
Uses floods, alternate sites, backup restoration, and tabletop exercises to make recovery decisions concrete.
What it assumes
Defines disaster recovery and its plan directly without naming required technical background.
What you can do after
Evaluate/understand recovery plans, site and backup options, and tests for restoring critical technology after disruption.
How it connects
Connects disaster recovery to business continuity, backups, recovery sites, and recovery time and point objectives.

Also explained in

Compare how 8 books explain disaster recovery →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fundamentals of Cybersecurity. The section links point to the parts of the book it draws on.