4 ms·
"work related mistake"? If anything, the CTO should be blamed here... it's not hard to do a sql dump on the hour for backups.
by veemjeem 14y ago
"work related mistake"? If anything, the CTO should be blamed here... it's not hard to do a sql dump on the hour for backups.
- mgkimsal 14y agowe don't know the size of the db involved. multi-gig dbs dumping every hour may be production-limiting.
- gaius 14y agoWell, I've worked on a 50T DB doing 800G of changes per hour, which was recoverable to any point in time. That's not even particularly big by today's standards.
- mgkimsal 14y agoand you dumped the entire 50terabytes every hour? The point above was that they should have been doing a db dump. that's not always the best way (or even possible) to deal with large data sets.
- gaius 14y agoNo, but why would you do that? It makes no sense when there are better backup strategies available (archived redo logs, hot standby, filesystem snapshots, etc etc).