Why an Untested Backup Isn't Really a Backup

Ask most companies whether their business applications are backed up and you’ll hear “yes.” Ask when they last restored from a backup and the room gets quiet.

An untested backup is a guess. It might work. It might be incomplete, corrupted, missing a database, encrypted with a key nobody has, or stored in an account tied to someone who left two years ago. You won’t know until the day you need it, which is the worst possible day to find out.

Common ways backups fail

What a good backup routine looks like

Define what “recovered” means

For each critical system, decide two things:

Back up everything needed to rebuild

Not just the database: uploaded files, configuration, environment settings, and the information needed to redeploy the application itself.

Keep copies separate

At least one backup copy should live outside the system’s primary account or location, so one compromised account or failed provider doesn’t take everything.

Monitor the backups

Backup jobs should report success and failure to a person. Silence shouldn’t be interpreted as success.

Test restores on a schedule

At least once or twice a year for each critical system, restore a backup into a separate environment and confirm:

Write it down

A short runbook covering where backups live, how to access them, and the step-by-step restore process. Store it somewhere you can reach during an outage.

The question to ask this week

“When did we last restore our most important system from backup, and how long did it take?”

If nobody knows, that’s your next project. Verified backups and tested restores are part of every managed software services engagement we run, and a tested restore is one of four critical items in the free Software Estate Risk Scorecard.


Tell us what you're running.

Two quick steps. I'll read it personally and reply with an honest read on your situation and whether our team can help, usually within one business day.

  • I lead every engagement personally
  • No sales sequences, and your details are only used to reply

Prefer email? [email protected]

Step 1 of 2

Which sounds most like you?
What's prompting this? Pick any that apply
How many business-critical custom systems?
Timeline
Where should I reply?