Backups you can trust
When Claude and I started on my network, I had to admit something embarrassing for someone who has been in this business as long as I have: I had no real backups. One disk failure, a fire, or a ransomware infection could have taken years of work with it.
Fixing that went to the top of the list.
The setup
- Every machine, every night. Each of the four machines in the house backs itself up automatically in the early morning hours, a few minutes for most of them.
- Offsite. The backups go to Backblaze B2, a cloud storage service, so a problem at the house can't take the backups with it.
- Encrypted before it leaves. We use restic, an open-source backup tool that encrypts everything on my machines before upload. The storage company only ever sees scrambled data.
- Only what changed. restic stores each piece of data once, so a nightly run only uploads what's new. My Windows virtual machine is a 160 GB disk file, and a typical night uploads well under a tenth of that.
- Protected from deletion. The storage is set so nothing uploaded can be permanently erased for 30 days, even by someone who has my passwords. That's the ransomware defense: an attacker who gets in can't quietly destroy the backups too.
- A sensible history. We keep a backup for each of the last 7 days, the last 4 weeks and the last 12 months, and old ones are cleaned up automatically. Anything we want to keep longer, like the last copy of Windows 10 before I upgraded, gets a tag so it's kept indefinitely.
- Email if anything fails. A failed backup sends me a message. I know that works, because it has already happened twice, once when we hit a storage limit on a brand-new account and once after an internet outage in the middle of the night.
All of it costs a few dollars a month.
The part most people skip
Here's the thing about backups: the only one you can trust is one you have restored. Every backup system reports "success." The question is whether you get your data back when you need it.
So we tested restores. Not once, and not just a few files.
- The first week: we restored files, system configuration and a database export from each machine, and the whole 128 GB Windows disk. The disk came back in about twenty minutes, and the disk-checking tool found no errors.
- The real test, before deleting something: I had a local copy of my old Windows 10 disk that I'd kept "just in case." Before I deleted it, we restored the cloud copy of the same disk and compared the two, byte by byte, all 138 billion bytes. They were identical. Only then did I delete the local copy.
A backup you haven't restored is only a hope.
Small things that mattered
- Keep the passwords somewhere else. An encrypted backup is useless if the only copy of its password was on the machine that died. Each machine's backup password is saved off that machine.
- Watch the numbers. When one night's Windows backup was more than twice the usual size, Claude flagged it so we'd notice if it kept happening. It went back to normal the next night.
- Little problems hide nearby. While checking on the backups, Claude noticed one machine's system log had quietly grown to 18 GB because the job that trims old logs had been turned off. It would have filled the disk eventually. Five minutes to fix.
What I'd tell a friend
If you do one thing, set up automatic offsite backups. If you do two things, restore from them and check what comes back. An AI assistant made both easy enough that I ran out of excuses.