Nobody wants backups. Everybody wants restores.
/Technical/1 min read
This is a sample post so you can see how articles look. Replace it with your own writing, then delete this file.
Every backup system looks fine on the dashboard. Green ticks, tidy job histories, a retention policy someone signed off three years ago. None of that tells you whether you can get a file back on a bad Monday morning.
The only test that counts
A backup is a promise about the future. The way to check a promise is to call it in.
- Pick something real, not a test file you made five minutes ago.
- Restore it somewhere that is not where it came from.
- Time it, and write down how long it took.
# Example only: restore one directory to a scratch location and compare
restore --snapshot latest --target /srv/restore-test /home/projects
diff -rq /home/projects /srv/restore-test/home/projects
What changes when you do this regularly
You stop arguing about backup tooling and start talking about recovery time, which is the conversation people actually care about.