Security

Backups That Actually Restore

Most backup failures aren't technical they're process. Here's a simple restore drill you can run quarterly.

A restore test is the only real backup report

Dashboards can look green while restores fail because of missing access, incomplete scope, or unclear ownership. This post gives you a repeatable drill that proves you can recover before you need to.


.
Marc Vaccaro
May 08 · 8 min read
Myth
"We're backed up because the job succeeded."

A successful backup job doesn't guarantee your data is complete, uncorrupted, decryptable, or restorable under pressure.

Reality
A backup is only proven after a restore.

A simple restore drill validates access, scope, time-to-recover, and that the output is usable by the business.

The quarterly restore drill

Pick one or two restore targets each quarter. Keep it consistent. Treat it like a fire drill: short, calm, repeatable.

1
Define what "good" means

Decide your target: restore a file share folder, a VM, a database, or a Microsoft 365 mailbox. Write down: acceptable data loss (RPO) and acceptable downtime (RTO).

2
Confirm access before you start

Verify you have admin credentials, MFA recovery methods, and access to the backup console and storage destination. This is where many "we're fine" plans fail.

3
Restore into a safe location

Use an isolated folder, alternate VM network, or a test environment. The goal is validation without risking production data.

4
Prove the restored data is usable

Open files, launch the app, connect to the database whatever "usable" means in your environment. Document the exact steps.

Questions you should ask yourself
  • If our primary server was encrypted today, what would we restore first?
  • Do we know who has the keys (credentials + MFA recovery) to perform the restore?
  • Have we tested a restore within the last 90 days?
  • Do we know how long it actually takes (not how long we hope)?

A simple way to rate backup readiness

This helps leadership understand where you are without jargon.

High risk
We have backups… somewhere

No recent restore test, unclear scope, unclear access, unknown recovery time.

Medium risk
Backups run reliably

Jobs are monitored and scope is known, but restores are tested inconsistently.

Low risk
Restore drills are routine

Quarterly test restores, documented steps, known RTO/RPO, verified access.

.

Want a one-page restore drill template?

We can send a simple worksheet that captures scope, access owners, steps, and results so each quarterly test gets easier.


Tip: the best first test is restoring a small but business-critical dataset (like a shared folder your team uses daily).