4 ms·
This once again reinforces the point that a backup is worthless if you haven't tested restore.
by perlgeek 7y ago
This once again reinforces the point that a backup is worthless if you haven't tested restore.
- cptskippy 7y agoThat's one of those idioms that rings hollow until it rings very true.
- SlowRobotAhead 7y ago“If you haven’t tested your backups, you don’t have backups.” LOTS of people don’t have backups.
- nemothekid 7y agoFrom the thread: >It's Oracle cloud - you can't really test them without restoring a snapshot (overwriting your current data) Jesus, if thats true, what a shit product. AWS RDS doesn't even let you restore a backup to an already running database, it always creates a new one.
- fauigerzigerk 7y agoRestore would have been successful while the key was still in memory. You could say if that happens it's a badly designed test, and I agree. But it goes to show that testing entire infrastructures partly run by service providers is not easy.
- CodeWriter23 7y agoRestore to the same system isn’t actually a restore test.
- deleted 7y ago[deleted]
- rwbhn 7y agoI think about it this way: you don't need a backup system - you need a restore system.
- MarkMc 7y agoIt also reinforces the point that there is a trade-off between reliability and security. When you encrypt something you are slightly increasing the chance that you will lose access to that data. Our accounting software offers end-to-end encryption, but it's not enabled by default. When the user tries to enable it they see a bold message saying, "Warning: In this mode we cannot reset your password. If you forget your password you will lose access to your data. Are you sure you want to continue?"