In short
- Definition: The ability to restore a system and its data after a major incident such as a data center loss, cyberattack or natural disaster.
- Goal: Limit downtime and data loss to levels the business can tolerate.
- Example S.M.A.R.T. requirement: RTO of 4 hours and RPO of 15 minutes, verified by a full failover exercise twice a year.
1. Definition
As a non-functional requirement, disaster recovery describes the ability to restore a system and its data after a major incident: loss of a data center or cloud region, a ransomware attack, a fire or a natural disaster [1], [2].
An untested recovery plan is a document, not a capability.Key takeaway
It is expressed with two key targets. The Recovery Time Objective (RTO) is the maximum time to restore the service. The Recovery Point Objective (RPO) is the maximum amount of data, measured in time, that may be lost [3].
Disaster recovery is part of broader contingency and business continuity planning, as described by guidance such as NIST SP 800-34 [4].
2. Goal
The goal is to limit downtime and data loss after a major incident to levels the business can tolerate.
Without a tested plan, recovery depends on improvisation under pressure, and a disaster can turn into weeks of outage or permanent data loss.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Recovery Time Objective (RTO) | Hours | e.g., 4 h | Timed failover or recovery exercise |
| Recovery Point Objective (RPO) | Minutes of data | e.g., 15 min | Replication lag and backup frequency |
| Recovery tests | Per year | ≥ 2 full exercises | Exercise reports |
| Plan currency | Months since last update | < 12 | Document review |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Core system: “The order system shall have an RTO of 4 hours and an RPO of 15 minutes, verified by a full failover exercise to the secondary region twice a year.”
- Ransomware: “The organization shall be able to restore critical systems from immutable backups within 24 hours, as demonstrated by an annual exercise.”
- Plan: “The disaster recovery plan shall be reviewed after every major architecture change and at least once a year.”
5. Questions to Ask Stakeholders
- Which disasters must the plan cover?
- How long can the business survive without this system?
- How much data can be lost without serious harm?
- Where is the secondary site or region?
- Who decides to trigger the recovery, and who does what?
- How and how often will the plan be tested?
6. Common Pitfalls
- Never running a full exercise. Only real failover tests reveal missing steps and wrong assumptions.
- Same region for primary and backup. A regional outage takes both down. Separate them geographically.
- Ignoring dependencies. Recovery fails if identity, DNS or a key supplier is not covered by the plan.
7. Related NFRs
- Backup — backups are the base of most recovery plans.
- Availability — disaster recovery protects availability against rare, severe events.
- Resilience — resilient design reduces how often recovery is needed.
- Fault Tolerance — handles smaller failures without invoking the plan.
- Data Integrity — restored data must be correct and consistent.
8. FAQ
RTO is how long the service may be down; RPO is how much recent data may be lost.
No. Disaster recovery restores IT systems; business continuity covers the whole organization, including people and processes.
For critical systems, at least once or twice a year, and after major changes.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| NIST | National Institute of Standards and Technology | United States government agency that publishes widely used standards and guides, notably in cybersecurity. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| DNS | Domain Name System | The internet’s directory: it translates names such as example.com into network addresses. | [7] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [8] |
| IT | Information technology | Use of computers, software and networks to store, process and exchange information; also the department that runs them. | [9] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
| RPO | Recovery point objective | Maximum acceptable amount of data loss after a disruption, expressed as a period of time. | [3] |
| RTO | Recovery time objective | Maximum acceptable time to restore a service after a disruption. | [10] |
| SP | Special Publication | Numbered series of NIST guidance documents, such as SP 800-34. | [5] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Cloud | Computing resources (servers, storage, services) rented over the internet from a provider. | [11] |
| Data center | Building that houses servers, storage and network equipment. | [12] |
| Failover | Automatic switch to a standby component when the main one fails. | [13] |
| Incident | Unplanned interruption or degradation of a service. | [14] |
| Replication | Keeping synchronized copies of data or services on several machines. | [15] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [16] |
10. Sources and Further Reading
- [1] “Disaster recovery.” Wikipedia. https://en.wikipedia.org/wiki/Disaster_recovery (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “Recovery point objective.” Wikipedia. https://en.wikipedia.org/wiki/Recovery_point_objective (accessed Nov. 18, 2026).
- [4] “Contingency Planning Guide for Federal Information Systems, SP 800-34 Rev. 1.” NIST. https://www.nist.gov/publications/contingency-planning-guide-federal-information-systems-including-updates-through (accessed Nov. 18, 2026).
- [5] “National Institute of Standards and Technology.” Wikipedia. https://en.wikipedia.org/wiki/National_Institute_of_Standards_and_Technology (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “Domain Name System.” Wikipedia. https://en.wikipedia.org/wiki/Domain_Name_System (accessed Nov. 19, 2026).
- [8] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [9] “Information technology.” Wikipedia. https://en.wikipedia.org/wiki/Information_technology (accessed Nov. 19, 2026).
- [10] “IT disaster recovery.” Wikipedia. https://en.wikipedia.org/wiki/IT_disaster_recovery (accessed Nov. 19, 2026).
- [11] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [12] “Data center.” Wikipedia. https://en.wikipedia.org/wiki/Data_center (accessed Nov. 19, 2026).
- [13] “Failover.” Wikipedia. https://en.wikipedia.org/wiki/Failover (accessed Nov. 19, 2026).
- [14] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [15] “Replication (computing).” Wikipedia. https://en.wikipedia.org/wiki/Replication_(computing) (accessed Nov. 19, 2026).
- [16] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @designbytholen; inline photo by @solusfire, both on Unsplash.




