Backup is not recovery: how to know your data will come back
By the SIM team · 29 Oct 2026 · 3 min read
Having a backup and being able to recover are different things. Backups fail silently: a job stops running, a disk fills up, a new server is never added to the schedule. The only proof is a restore.
Set two numbers
Decide how much data you can afford to lose (for example, one day) and how long you can afford to be down (for example, four hours). These two numbers, not the product brochure, determine what you need.
Nobody has ever needed a backup. What they needed was a restore.
Follow the 3-2-1 idea
Keep three copies of important data, on two different kinds of storage, with one copy away from the main site. A copy that ransomware can reach from the network is not a safe copy.
Test a restore every quarter
Pick a real file, a real database and one whole server. Restore them somewhere safe, time it, and write down what went wrong. Most problems are small and easy to fix once found.
Write the steps down
A one-page recovery procedure, kept somewhere other than the server it describes, saves hours when people are under pressure.
Review when things change
New application, new branch, new staff: each is a reason to check that the backup still covers everything that matters.
Common reasons restores fail
- The backup job stopped weeks ago and nobody was alerted.
- A new server or folder was never added to the schedule.
- The backup is encrypted and the password is lost.
- The only copy sat on the same network as the infected machines.
- Restoring takes three days and nobody knew.
A simple quarterly routine
- ChooseOne file, one database and one whole server.
- RestoreTo a safe location, never over live data.
- Time itCompare against the downtime you can afford.
- RecordNote what failed and fix it before next quarter.
An hour each quarter is a small price. Organisations that do this find their problems on a quiet afternoon instead of during a crisis.
Want this looked at for your organisation? Start with a conversation, or book an India-First Technology Assessment.


