Postgres as a Service
Deploy a Managed Postgres Cluster in Minutes! Enterprise-ready and Oracle compatible.
Failover Manager 2.1 offers support for monitoring and failover of clusters with one or more Standby servers. You can add or remove nodes from the cluster as your demand for resources grows or shrinks.For failover protection, the initial cluster should have a master and one or more standby nodes. If the cluster contains more than one Standby node, a dedicated Witness node is not required. If there is only one Standby node, the cluster should include a dedicated Witness node.Before configuring and starting Failover Manager, configure PostgreSQL Streaming Replication between the Master node and one or more Standby nodes on an Advanced Server or PostgreSQL installation. For more information about implementing streaming replication, see the PostgreSQL core documentation atBefore starting a Failover Manager agent, you must install Failover Manager (see ), and specify your configuration preferences in the cluster properties file (see ) and the cluster members file (see ) on the server on which the agent will be running.Please Note: If a Master node reboots, Failover Manager may detect the database is down on the Master node and promote a Standby node to the role of Master. If this happens, the Failover Manager agent on the (rebooted) Master node will not get a chance to write the recovery.conf file; the rebooted Master node will return to the cluster as a second Master node. To prevent this, start the Failover Manager agent before starting the database server. The agent will start in IDLE mode, and check to see if there is already a master in the cluster. If there is a master node, the agent will verify that a recovery.conf file exists, and the database will not start as a second master.