> All disaster recovery cannot be automated. See also: https://github.com/blog/1261-github-availability-this-week https://github.com/blog/1261-github-availabil

> All disaster recovery cannot be automated. See also: https://github.com/blog/1261-github-availability-this-week https://github.com/blog/1261-github-availability-this-week > The automated failover of our main production database could be described as the root cause of both of these downtime events. In each situation in which that occurred, if any member of our operations team had been asked if the failover should have been performed, the answer would have been a resounding no. There are many situations in which automated failover is an excellent strategy for ensuring the availability of a service. After careful consideration, we've determined that ensuring the availability of our primary production database is not one of these situations. To this end, we've made changes to our Pacemaker configuration to ensure failover of the 'active' database role will only occur when initiated by a member of our operations team.