Re:Approaches to PostgreSQL Replication and Backup
by colanderman on Friday February 23, 2018 @11:02PM
(#16451590)
Nor does Postgres replication manage failover. Either way you need a 3rd party tool.
Yep, botched failovers are bad. Of course, a botched failover between replicated DBs is no walk in the park either. In many such cases you'll still want to pull backups anyway, if there's no clear way in your domain to merge two "authoritative" databases.
Re:Approaches to PostgreSQL Replication and Backup
by rosser on Friday February 23, 2018 @11:57PM
(#16451766)
> In many such cases you'll still want to pull backups anyway...
In all cases where you care about your data, you must take backups. There is no substitute for that step.
Additionally, you want to periodically restore your backups and test them for validity — ideally automatically. There's a saying in the ops world, borne of bitter experience:
"Your backups are only as good as their last successful restore."
Re:Approaches to PostgreSQL Replication and Backup
by colanderman on Saturday February 24, 2018 @10:15AM
(#16453545)
What grantwu said. You misinterpreted me. Seems to be a theme today. I guess I should spell things out more clearly in the future.
Re:Approaches to PostgreSQL Replication and Backup
by rosser on Saturday February 24, 2018 @05:19PM
(#16455775)
Ok, my apologies. I've never heard that phrasing before, but now that you clarify, I understand it.
Ambiguity in online discourse is an ongoing problem. Thanks for helping resolve this occurrence without acrimony.
If you mis-manage failover, you will destroy your data. This makes proper backup even more important.