The Backup You Never Tested Is Just Another Monthly Bill
Ask a room full of small business owners whether they have backups and every hand goes up. Ask when they last pulled a file back out of one and the hands drop fast. That gap is where the real risk lives — not in whether you bought the software, but in whether anyone has ever proven it works.
Backups are one of the few purchases that feel finished the moment the invoice clears. The dashboard turns green at 2 a.m., the confirmation email arrives every morning, and nothing gives you a reason to look closer. Then a laptop takes a tumble down a staircase, or a folder gets dragged somewhere it shouldn't, or someone clicks a link in an invoice that wasn't an invoice. The green dashboard has no opinion about any of that.
What follows is a drill you can run in half an hour, once a month, without hiring anyone. It won't catch every possible failure, but it will catch the ones that actually happen.
What a Real Test Looks Like
Restoring a single photo and calling it verified is not a test — it's a formality. A genuine test answers three questions:
- Is the data actually there?
- Is it current, or is it from three weeks before anyone noticed the problem?
- Can a normal person get it back without the person who set the system up standing over their shoulder?
That third question is the one most businesses flunk. It's also the one that matters on the worst day, when the person who configured everything is on vacation or no longer works for you.
The Drill, Step by Step
Pick a boring target. Not the one folder everyone protects. Choose something mid-weight — a client proposals folder, last quarter's invoices, the shared design assets. If you only ever test the crown jewels, you're rehearsing a scenario that probably won't happen.
Restore to a separate location. Never restore over the live folder. Drop it on a desktop or a scratch folder so a mistake can't make things worse.
Open three files at random. One from the beginning of the folder's history, one from the middle, one from last week. Open them in the actual program — the PDF viewer, the spreadsheet app, whatever it was made in. A file that exists but won't open is not a backup; it's a souvenir.
Check the date. Look at the timestamp on the newest file in the restored set. If your nightly backup runs at 2 a.m., the newest item should be from yesterday, not last Tuesday. A backup that quietly stopped advancing is the most common failure I see, and it's invisible unless you look at dates.
Time the restore. Start a clock before you click go and note how long it takes. Thirty minutes to pull back a small folder is a warning sign for what a full restore would look like.
Delete the test copy when you're done. Cleanup matters. A desktop littered with restored folders becomes its own mess.
Failure Points That Show Up Over and Over
The cloud apps aren't covered. Your backup might protect a file server while Microsoft 365, Google Workspace, and your accounting software sit unbacked. Deleted email and cloud files typically vanish for good once the trash window closes — usually thirty days or fewer. Ask your provider directly whether those apps are in scope, and get the answer in writing.
Retention is too short. A thirty-day window sounds generous until ransomware sits quietly for six weeks before it detonates.
Nobody has the encryption key. An encrypted backup with a lost password is a very secure brick.
The job skipped files and still reported success. Logs love to say "completed" while listing a handful of skipped items. Skim the log, not just the status line.
The backup lives in the same building as the original. A drive on a shelf in the same office doesn't survive a fire, a flood, or a break-in. One copy offsite, one copy local, one copy somewhere immutable — that's the old rule and it still holds.
The scope drifted. You added a shared drive in March and never added it to the backup job. New folders don't add themselves.
Write It Down in Plain English
This is the part people skip, and it's the part that pays off. One dated paragraph per drill, saved somewhere the whole team can find it:
November 10, 2026 — Restored the Client Proposals folder from the November 9 backup. 1,140 files. Opened six, all fine. Took 34 minutes. Done by the office manager using the vendor's web portal. Portal login is in the password manager under "Backup Portal."
That's it. No scores, no charts. Six months of those paragraphs will tell you more about your IT health than any dashboard, and they're readable by anyone — including whoever buys the business someday.
Put It on the Calendar
Second Tuesday of the month. Thirty minutes. Recurring calendar invite with the drill steps pasted into the description so nobody has to remember them. Pair it with a coffee and it stops feeling like IT work.
And if the drill takes you two hours, or you can't find the portal login, or you discover the last successful backup was in August — that's not a failure of the drill. That's the drill doing its job early, while it's still cheap to fix.