EDB Failover Manager™

EDB Failover Manager™

EDB Postgres Failover Manager (EFM) is a high-availability module from EnterpriseDB that enables a Postgres primary node to automatically failover to a Standby node in the event of a software or hardware failure on the primary.

This guide provides information about installing, configuring and using Failover Manager 4.0. For information about the platforms and versions supported by Failover Manager 4.0, visit the EnterpriseDB website at:

https://www.enterprisedb.com/services-support/edb-supported-products-and-platforms#efm

This document uses Postgres to mean either the PostgreSQL or EDB Postgres Advanced Server database.

• What’s New
• Failover Manager Overview
  • Prerequisites
• Installing Failover Manager
  • Performing post-installation tasks
  • Installation Locations
• Configuring Failover Manager
  • The Cluster Properties File
    • Specifying Cluster Properties
  • Encrypting Your Database Password
  • The Cluster Members File
  • Extending Failover Manager Permissions
    • Running Failover Manager without sudo
  • Using Failover Manager with Virtual IP Addresses
• Using Failover Manager
  • Managing a Failover Manager Cluster
    • Starting the Failover Manager Cluster
    • Adding Nodes to a Cluster
    • Changing the Priority of a Standby
    • Promoting a Failover Manager Node
    • Stopping a Failover Manager Agent
    • Stopping a Failover Manager Cluster
    • Removing a Node from a Cluster
  • Running Multiple Agents on a Single Node
    • RHEL 6.x or CentOS 6.x
    • RHEL/CentOS 7.x or RHEL/CentOS 8.x
• Monitoring a Failover Manager Cluster
  • Reviewing the Cluster Status Report
  • Monitoring Streaming Replication with Postgres Enterprise Manager
• Using the efm Utility
• Controlling the Failover Manager Service
  • Using the service Utility on RHEL 6.x and CentOS 6.x
  • Using the systemctl Utility on RHEL/CentOS 7.x and RHEL/CentOS 8.x
• Controlling Logging
  • Enabling syslog Log File Entries
• Notifications
• Supported Failover and Failure Scenarios
  • Primary Database is Down
  • Standby Database is Down
  • Primary Agent Exits or Node Fails
  • Standby Agent Exits or Node Fails
  • Dedicated Witness Agent Exits / Node Fails
  • Nodes Become Isolated from the Cluster
• Upgrading an Existing Cluster
  • Un-installing Failover Manager
  • Performing a Database Update (Minor Version)
• Troubleshooting
• Configuring Streaming Replication
  • Limited Support for Cascading Replication
• Configuring SSL Authentication on a Failover Manager Cluster
• Conclusion