In short
- Definition: The capability to create and keep copies of data and configuration so they can be restored after loss or corruption.
- Goal: Protect data against accidental deletion, corruption, attacks and hardware failure.
- Example S.M.A.R.T. requirement: Daily backups kept 30 days, with a monthly restore test succeeding 100% of the time.
1. Definition
As a non-functional requirement, backup describes the capability to make and keep copies of data and configuration so they can be restored after loss, corruption, deletion or attack [1], [2], [3].
A backup that has never been restored is only a hope. The real requirement is the restore.Key takeaway
A backup requirement covers what is copied, how often, where the copies are stored, how long they are kept, and how quickly and completely they can be restored. The widely cited 3-2-1 rule recommends three copies of the data, on two different media, with one copy off-site.
Backup is not the same as replication. Replication copies changes almost instantly, including mistakes and ransomware encryption; a backup keeps earlier versions you can go back to.
2. Goal
The goal is to protect data against human error, software bugs, hardware failure and attacks, so the organization can recover what it needs.
Without tested backups, a single deletion or ransomware attack can destroy years of work, stop operations and breach legal obligations to keep records.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Backup frequency | Hours between backups | ≤ 24 h (or as set by the RPO) | Backup tool job history |
| Backup success rate | % of jobs | 100%, failures alerted within 1 h | Backup monitoring and alerts |
| Restore test success | % of tests | 100% monthly | Scheduled restore tests to an isolated environment |
| Restore time | Hours | Within the agreed RTO (e.g., < 4 h) | Timed restore tests |
| Retention | Days or years | e.g., 30 daily, 12 monthly | Backup policy and catalog |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Business database: “The customer database shall be backed up every 24 hours, with copies kept for 30 days, one copy stored off-site and immutable, and a full restore tested every month.”
- File server: “Any file deleted by mistake shall be restorable by the service desk within 4 business hours, for up to 90 days after deletion.”
- SaaS data: “Data held in third-party SaaS tools (e-mail, CRM) shall be exported or backed up daily to storage controlled by the organization.”
5. Questions to Ask Stakeholders
- Which data can you not afford to lose, and how much of it (in hours)?
- How long must backups be kept, for business or legal reasons?
- How fast must data be restored after loss?
- Must backups be protected against ransomware (immutable or offline copies)?
- Who is allowed to restore data, and who must approve it?
- Are data in SaaS tools covered by the vendor, or do we need our own copies?
6. Common Pitfalls
- Never testing restores. Backups fail silently. Schedule restore tests and measure their time.
- Keeping backups on the same network. Ransomware can encrypt them too. Keep an immutable or offline copy.
- Ignoring SaaS and configuration. Data in cloud tools and system configuration are often missing from backup plans.
7. Related NFRs
- Disaster Recovery — backups are a key input to recovery after a major incident.
- Data Retention — sets how long backup copies may or must be kept.
- Data Integrity — backups must be consistent and uncorrupted to be useful.
- Durability — durable storage reduces but does not remove the need for backups.
8. FAQ
Keep three copies of your data, on two different types of storage, with one copy off-site. Many teams now add an immutable or offline copy.
No. Replication also copies deletions and corruption. You still need point-in-time backups.
At least for every critical system on a regular schedule, such as monthly, 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. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [4] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| CRM | Customer relationship management | Software for managing customer contacts, sales and interactions. | [5] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| 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. | [3] |
| RPO | Recovery point objective | Maximum acceptable amount of data loss after a disruption, expressed as a period of time. | [7] |
| RTO | Recovery time objective | Maximum acceptable time to restore a service after a disruption. | [7] |
| SaaS | Software as a service | Software rented and used over the internet rather than installed locally. | [8] |
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. | [9] |
| Database | Organized store of data that software can query and update. | [10] |
| Encryption | Scrambling data so only authorized parties with the key can read it. | [11] |
| Incident | Unplanned interruption or degradation of a service. | [12] |
| Replication | Keeping synchronized copies of data or services on several machines. | [13] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [14] |
10. Sources and Further Reading
- [1] “Backup.” Wikipedia. https://en.wikipedia.org/wiki/Backup (accessed Nov. 18, 2026).
- [2] “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).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [5] “Customer relationship management.” Wikipedia. https://en.wikipedia.org/wiki/Customer_relationship_management (accessed Nov. 19, 2026).
- [6] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “IT disaster recovery.” Wikipedia. https://en.wikipedia.org/wiki/IT_disaster_recovery (accessed Nov. 19, 2026).
- [8] “Software as a service.” Wikipedia. https://en.wikipedia.org/wiki/Software_as_a_service (accessed Nov. 19, 2026).
- [9] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [10] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [11] “Encryption.” Wikipedia. https://en.wikipedia.org/wiki/Encryption (accessed Nov. 19, 2026).
- [12] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [13] “Replication (computing).” Wikipedia. https://en.wikipedia.org/wiki/Replication_(computing) (accessed Nov. 19, 2026).
- [14] “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 @nkend; inline photo by @redaquamedia, both on Unsplash.




