5 ms·
This is why you should be extremely wary of anything that is only run once in a a blue moon. And very wary of such things that when run, are being run to save y
by dboreham 9y ago
This is why you should be extremely wary of anything that is only run once in a a blue moon. And very wary of such things that when run, are being run to save your bacon.
- quicklyfrozen 9y agoAnd wary of using options that might be outside typical usage (such as -INF for the backup VIP).
- king_phil 9y agoI don't see how using infinity in a pacemaker config would be outside typical usage
- Klathmon 9y agoI always advocate for monthly "pull the plug on the box" tests. If you don't need "high availability", then it will test your backups and restore process, and if you do need "high availability", it will ensure your failover processes are running smoothly. Not to mention it trains everyone involved what to do in an emergency since it should be second nature by the time it really happens. If you can't go "Full netflix" and unleash a chaos monkey on your servers, at least setup a maintenance period where downtime is somewhat expected, and do it then.
- rosser 9y ago"Your backups are only as good as their last successful restore."
- CodeWriter23 9y agohttps://feedbin.com/blog/2017/05/05/testing-huge-postgresql-backups-for-37-cents-a-day/ https://feedbin.com/blog/2017/05/05/testing-huge-postgresql-...
- seanwilson 9y ago> This is why you should be extremely wary of anything that is only run once in a a blue moon. I find this similar to when you launch a project that hasn't been used in production yet. Bugs should be expected because it hasn't been battle tested.