Almost every business has backups. Far fewer have backups they've tested. The gap between those two facts is where data losses actually happen — discovered, always, at the worst possible moment.
An untested backup is a hope, not a safeguard
Backups fail quietly. The job that's been "running" for months but silently erroring. The snapshot that captures the files but not the database. The restore that technically works but takes four days you don't have. None of this is visible until you try to recover — and the middle of a ransomware incident is a terrible time to learn your safeguard was theater.
Restore is the real test, not backup
Backing up is easy; restoring is the part that counts, and the part almost no one rehearses. The only way to know your backups work is to actually bring something back from them — on a schedule, deliberately, while nothing is on fire. A restore you've performed is a capability. A backup you've never restored is a guess wearing the costume of one.
A backup you can trust answers:
- When did we last restore from this, successfully, end to end?
- How long would a full recovery actually take — and can the business survive that long?
- Is at least one copy off-site and offline, beyond the reach of ransomware that encrypts everything it can touch?
- Does it include the things that are hard to rebuild — configurations, not just files?
A backup is a promise about the future. A tested restore is the only proof that the promise will be kept.
The 3-2-1 habit, and the rehearsal
The old rule still holds — three copies, two kinds of media, one off-site — because it survives the failures that take out single backups. But the rule that matters more is the one most teams skip: rehearse the restore. Twice a year, recover something real and time it. The exercise will surface a broken assumption every single time, which is the entire point of doing it before you need it.
The question isn't whether you have backups. Everyone has backups. The question is whether you've ever watched one bring your business back — because if you haven't, you don't have a safeguard. You have a story you've been telling yourself.