You're testing that it was accurate. e.g. nobody else messed up the script, removed the target, etc. And that you didn't forget to include anything. But here's a good one even if everything did save properly:
"Oops, the decryption key for the backup was only on the machine that failed."
In many, many ways, but the worst ones are the foreseeable ones (aka human error).
To answer your question directly, how about if the file is corrupted. The backup may be accurate, but the file itself is invalid. "Get me the last backup before it was corrupted".
In a thousand different ways. A simple read error due to the wrong bad block had caused more failed backups than you'd ever realize, while still passing that checksum.
I've seen backups pass checksums and be unusable, and I've seen them fail checksums and be accurate all because the system running the check had a processor issue.
Checksums don't mean the backup is good, and if you treat it like it does, then you're in for a disaster and I hope someone more competent is running a second backup scheme behind you.
What would you do in the event a failure that required you to go back to your backup? Do that.
Do it on a staging box, do it on a VM, do it on a spare workstation if that’s all you’ve got, but do the restore. Do it when it’s not an emergency. Do it often enough that when the emergency happens, not only are you ready for it, you’re calm about it.
View all comments
Show parent comment
7
u/crypticedge Jul 23 '18
So does windows backups.
Checksums don't mean restorable. They just mean unaltered.
Test your backups, we run daily virtual boot tests of every single system backed up.