The concept
Backup is a recovery capability, not just another copy somewhere. Determine which files matter, how much recent work can be lost, and how quickly access must return. Keep backups protected from the same incident that could destroy or encrypt the working files. Test restoration rather than relying only on a successful-copy notification.
Worked example
A fictional local newspaper saves its archive to a drive permanently attached to the main computer. A destructive incident affects both locations. Staff redesign the process with an additional protected backup, a defined schedule, and a monthly restoration exercise. In the first test they discover that image captions were stored in a separate folder that had never been included. The test finds a problem before an emergency exposes it.
Limits and judgment
Synchronization is useful but may faithfully copy unwanted deletion or corruption. A cloud service may offer version history or recovery, but availability and retention vary. Understand the actual arrangement, protect access credentials, and document the restoration steps. Recovery should also account for someone being absent: a backup only one unavailable volunteer knows how to use is operationally fragile.
FROM UNDERSTANDING TO ACTION
Put it to work.
Choose three irreplaceable file types and write a restoration test with a clear success condition.
RETRIEVE. REASON. REMEMBER.
Knowledge check.
Choose one answer for each question, then check your reasoning.
Sources & further reading.
Links support the core concepts or identify the book. Examples, exercises, and critical analysis are original Institute material. Source checks are not an independent expert review of every claim.
- NCSC: Mitigating malware and ransomware ↗
Security or privacy principle; the fictional scenarios and operational analysis are original. Source reviewed 2026-10-19.