The Backup You Never Opened
For almost a week, one of my backups ran every night and left a file behind every morning.
That was the whole problem. It looked fine. A job kicks off at three in the morning, copies the folder that holds a big chunk of my business work, zips it up, and drops the zip on a separate drive. Every morning there was a new zip, dated correctly, sitting next to the others. Around eight gigabytes each. Nothing looked off.
Then a check I had running in the background did something I had never bothered to do by hand. It opened one.
Eight gigabytes of almost
The zip was cut off partway through. So was the one before it. And the one before that. The job had been tripping over one folder full of build files from a little hardware project, quitting halfway, and leaving behind a file that was big, recent, and useless.
The real thing, when I finally got a clean copy, came out to twenty-two gigabytes. The nightly file had been carrying about a third of what it promised. For days, the honest answer to “do I have a backup?” was no, and every signal I normally glance at said yes.
I wrote a while back about the assumption nobody checked. This was that, wearing a different shirt. The assumption was that a file existing means a file working.
A backup is a promise about the future
Here is the shift that stuck with me. A backup is not a file. It is a promise that on your worst day, you can get your stuff back. The file is just the evidence, and evidence can lie.
You do not find out whether the promise holds on a normal Tuesday. You find out the day a drive dies or a folder gets wiped, which is exactly the day you have no time to discover that the last six copies are broken.
So the only test that counts is the one that looks like that bad day. Open it. Pull a file out. Make sure the thing you would actually need is in there.
What I changed
Three small things, none of them clever.
First, I made a clean copy by hand that same morning, so there was at least one real restore point while the nightly job got fixed. Fix the gap before you fix the cause.
Second, every backup now gets opened after it is made. Not glanced at. Opened. The check reads the end of the file, counts what is inside, and pulls out a handful of specific files I know should be there. If any of that fails, the backup did not happen, no matter what the job says.
Third, I stopped trusting size. Eight gigabytes looked like a lot. It looked like a backup. Size tells you something got written. It does not tell you what.
The green light problem
Most of the systems I run, the AI ones included, have some version of a green light. Job finished. Task complete. All good. I have learned the hard way, more than once, that a green light usually means “the thing ran,” and almost never means “the thing worked.”
Those are different questions. The first one is cheap to answer. The second one costs you a minute of actually looking. That minute is the whole job. It is the same lesson I got from forty-one messages nobody read: output is not the same as outcome.
If you run anything for your business, a website, a client folder, a photo archive, a spreadsheet you would cry about losing, try this today. Find your most recent backup. Open it. Get one file out. If you cannot, you just learned something for free that most people learn for a lot of money.
The backup you never opened is not a backup. It is a hope with a timestamp on it.
