Failover Manager

Failover Manager (EFM) is a tool for managing Postgres database clusters, enabling high availability of primary-standby deployment architectures using streaming replication. Failover Manager provides a Postgres primary database node automatic failover to a standby database node in the event of a software or hardware failure. You can use Failover Manager with PostgreSQL or EDB Postgres Advanced Server.

• Introduction
  • Release notes
    • Version 5.2
    • Version 5.1
    • Version 5.0
    • Version 4.10
    • Version 4.9
    • Version 4.8
    • Failover Manager 4.7 release notes
    • Failover Manager 4.6 release notes
    • Failover Manager 4.5 release notes
    • Failover Manager 4.4 release notes
    • Failover Manager 4.3 release notes
    • Failover Manager 4.2 release notes
    • Failover Manager 4.1 release notes
    • Failover Manager 4.0 release notes
  • Supported platforms
• Planning
  • Architecture
  • Choosing a deployment architecture
    • Failover Manager with virtual IP
    • Failover Manager with client connect failover
    • Failover Manager with EDB PgBouncer
    • Failover Manager with EDB Pgpool-II
• Installing and Upgrading
  • Installing Failover Manager on Linux
    • Linux x86-64 (amd64)
    • Linux Installing Failover Manager on Linux IBM Power (ppc64le)
    • Linux Installing Failover Manager on Linux AArch64 (ARM64)
  • Upgrading Failover Manager
    • The optional -source flag
• Configuring
  • Configuring streaming replication
    • Limited support for cascading replication
  • Configuring Failover Manager
    • The cluster properties file
    • Encrypting your database password
    • The cluster members file
    • Extending Failover Manager permissions
    • Using Failover Manager with virtual IP addresses
    • Configuring for Eager Failover
  • Configuring SSL authentication on a Failover Manager cluster
• Using
  • Using Failover Manager
    • Managing a Failover Manager cluster
    • Running multiple agents on a single node
  • Monitoring a Failover Manager cluster
    • Reviewing the cluster status report
    • Viewing failed nodes in the cluster
    • Monitoring streaming replication with Postgres Enterprise Manager
  • Using the efm utility
    • efm allow-node
    • efm disallow-node
    • efm cluster-status
    • efm cluster-status-json
    • efm create-standby
    • efm encrypt
    • efm promote
    • efm reset-members
    • efm resume
    • efm set-priority
    • efm stop-cluster
    • efm upgrade-conf
    • efm node-status-json
    • efm –help
  • Controlling the Failover Manager service
    • Using the systemctl utility on RHEL/Rocky Linux/AlmaLinux 8.x or later
  • Controlling logging
    • Enabling syslog log file entries
  • Notifications
  • Supported failover and failure scenarios
    • Primary database is down
    • Return the node to the cluster
    • Return the node to the role of primary
    • Primary agent exits or node fails
    • Standby agent exits or node fails
    • Dedicated witness agent exits/node fails
    • Nodes become isolated from the cluster
  • Troubleshooting
    • The Failover Manager agent fails to start
    • Authorization file not found. Is the local agent running?
    • Not authorized to run this command. User ‘<os user>’ is not a member of the `efm` group.
    • Notification; Unexpected error message
    • Confirming the OpenJDK version
    • Unexpected connection attempts from outside the cluster
• Tutorial
  • Creating a Failover Manager cluster
    • Perform a switchover
    • Access online help