2 ms·
The fascinating thing to me about the ops 101 rule you describe: 1) it's so obviously correct, but 2) for some reason, almost nobody has a good backup plan that
by unoti 14y ago
The fascinating thing to me about the ops 101 rule you describe: 1) it's so obviously correct, but 2) for some reason, almost nobody has a good backup plan that they actually follow, where they actually have a process to periodically validate the restore procedure works. So few people actually do this, that I've come to think of this as a basic rule to understand, but an apparently advanced one to actually follow.
You hit the nail on the head regarding overabundant cleverness. A lot of developers are too clever by half, too.
- GFischer 14y agoI worked for a company that actually did periodical restores of backups, and had a smaller scale version of the "Chaos Monkey" (per company procedures, someone would periodically delete on purpose a file at random - it could be part of an important product, documentation, accounts, an SQL database - and we were asked to get it back from backup). After I got to the "real world", I'm shocked that some extremely large companies (financial institutions that should know better) don't have anything like it in place, and have far worse and untested but expensive disaster recovery plans.