Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A disaster recovery plan is the documented, tested procedure for restoring IT systems and data after a major disruption, built around agreed recovery time and recovery point objectives.

What Is a Disaster Recovery Plan?
A disaster recovery plan is the set of documented procedures an organisation follows to restore its IT systems, applications, and data after a serious disruption. It is narrower than business continuity, which covers how the organisation keeps operating overall, and it is the part that fails most visibly when it has not been tested.
The distinction between the two is worth getting right. Business continuity asks how the finance team keeps paying suppliers when the ERP system is down. Disaster recovery asks how the ERP system comes back, in what order, from what copy, and by when.
Every recovery plan rests on two agreed figures per service, drawn from a business impact analysis. The recovery time objective is how long restoration may take. The recovery point objective is how much data may be lost, measured as the interval back to the last usable copy.
These figures determine architecture and therefore cost. The relationship is unforgiving:
| Strategy | Typical RTO | Relative cost |
|---|---|---|
| Backup and restore to new infrastructure | Days | Low |
| Cold standby site, built on demand | 1–3 days | Low to moderate |
| Warm standby, infrastructure running, data replicated | Hours | Moderate |
| Hot standby or active-active | Minutes | High |
A plan that promises a four-hour RTO on a backup-and-restore architecture is not a plan; it is a statement of intent that will be disproved on the worst possible day.
Keep an offline copy. A plan stored only in SharePoint is unavailable in exactly the scenario it was written for.
Traditional disaster recovery assumed the primary site failed and the secondary was clean. Ransomware breaks that assumption: replication faithfully copies encrypted data, and attackers target backup infrastructure deliberately, often deleting snapshots and backup catalogues before triggering encryption.
Modern plans account for this with immutable or air-gapped copies that cannot be deleted within a retention window, separate credentials for backup systems that are not part of the main directory, and a clean recovery environment where restored systems are verified before being reconnected. The British Library’s October 2023 attack is the instructive UK case: the library’s own review described infrastructure destroyed so thoroughly that services were rebuilt over many months rather than restored, and the absence of a comprehensive, current recovery position for legacy systems was a central finding.
Plan for the possibility that recovery means rebuilding rather than restoring, and know which systems would need that.
Four levels of test, in increasing order of value and disruption: a walkthrough of the document, a tabletop exercise against a scenario, a partial failover of selected services, and a full failover with production traffic.
Test at least annually and after material change. Record the actual recovery time achieved against the target, and treat a gap as a finding with an owner, not as an observation. The most common discoveries are unglamorous: backups that completed but could not be restored, licences bound to the failed hardware, documentation naming staff who left, and dependencies on a service that was out of scope.
UK GDPR Article 32(1)(c) requires the ability to restore availability and access to personal data in a timely manner after a physical or technical incident, and 32(1)(d) requires regular testing of that ability. ISO 22301 provides the management system structure, and ISO 27001 Annex A control 5.30 covers ICT readiness for business continuity. Financial firms work to PRA and FCA operational resilience rules and, for EU-authorised entities, DORA.
If you want the plan validated rather than reviewed, our emergency action plan services cover exercising it against realistic scenarios and measuring what actually happens.
Business continuity covers how the organisation keeps delivering its services during a disruption, including manual workarounds, alternative premises, and staffing. Disaster recovery is the IT component: restoring systems, applications, and data. Disaster recovery sits inside business continuity, and a recovery plan without the wider continuity context tends to restore systems in an order the business would not have chosen.
At least annually for a full exercise, with lighter tests more frequently, and always after a material change such as a migration, a new critical application, or a supplier change. Record the recovery time actually achieved against the target. Many organisations test backup completion but never a full restore, which is the step that fails in real events.
No. Cloud providers guarantee infrastructure availability, not your data or configuration. Accidental deletion, ransomware, a misconfigured deployment, or an account compromise are your responsibility under the shared responsibility model, and most SaaS platforms retain deleted data for a limited period only. You still need defined recovery objectives, independent backups, and tested restoration procedures.
Keep at least one copy immutable or offline so it cannot be deleted or encrypted within its retention window. Use separate credentials for backup systems, outside the main directory, so a domain compromise does not grant backup access. Monitor for mass deletion of snapshots, and verify restored systems in an isolated clean environment before reconnecting them.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.