Using

• 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/Rocky Linux/AlmaLinux 8.x or later
• Monitoring a Failover Manager cluster
  • Reviewing the cluster status report
    • Exit codes
  • 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