Upgrading Failover Manager v4
Failover Manager provides a utility to assist you when upgrading a cluster managed by Failover Manager. To upgrade an existing cluster, you must:
Install Failover Manager 4.8 on each node of the cluster. For detailed information about installing Failover Manager, see Installing Failover Manager.
After installing Failover Manager, invoke the efm upgrade-conf utility to create the
.nodesfiles for Failover Manager 4.8. The Failover Manager installer installs the upgrade utility (efm upgrade-conf) to the
/usr/edb/efm-4.8/bindirectory. To invoke the utility, assume root privileges, and invoke the command:
upgrade-confutility locates the
.nodesfiles of preexisting clusters and copies the parameter values to a new configuration file for use by Failover Manager. The utility saves the updated copy of the configuration files in the
.nodesfiles for Failover Manager 4.8, specifying any new preferences. Use your choice of editor to modify any additional properties in the properties file (located in the
/etc/edb/efm-4.8directory) before starting the service for that node. For detailed information about property settings, see The cluster properties file.
If you're using Eager Failover, you must disable it before stopping the Failover Manager cluster. For more information, see Disabling Eager Failover.
Use a version-specific command to stop the old Failover Manager cluster. For example, you can use the following command to stop a version 4.7 cluster:
The primary agent will not drop the virtual IP address (if used) when it is stopped; the database will remain up and accessible on the VIP during the EFM upgrade. See also: Using Failover Manager with virtual IP addresses
Start the new Failover Manager service (
edb-efm-4.8) on each node of the cluster.
The following example shows invoking the upgrade utility to create the
.nodes files for a Failover Manager installation:
If you're using a Failover Manager configuration without sudo, include the
-source flag and specify the name of the directory in which the configuration files reside when invoking
upgrade-conf. If the directory isn't the configuration default directory, the upgraded files are created in the directory from which the
upgrade-conf command was invoked.
If you are using custom scripts, check to see if they are calling any Failover Manager scripts. For example, a script that runs after promotion to perform various tasks and then calls Failover Manager's
efm_address script to acquire a virtual IP address. If you have any custom scripts calling Failover Manager scripts, update the custom scripts to use the newly installed version of the Failover Manager script before uninstalling the older version of the Failover Manager script.
After upgrading to Failover Manager 4.8, you can use your native package manager to remove previous installations of Failover Manager. For example, use the following command to remove Failover Manager 4.7 and any unneeded dependencies:
- On RHEL or CentOS 7.x:
- On RHEL or Rocky Linux or AlmaLinux 8.x:
- On Debian or Ubuntu:
- On SLES:
You can perform maintenance activities such as an OS patch or a minor database version upgrade. You can upgrade from one minor version to another (for example, from 10.1.5 to version 10.2.7) or apply a patch release for a version.
First, update the database server on each standby node of the Failover Manager cluster. Then, perform a switchover, promoting a standby node to the role of primary in the Failover Manager cluster. Then, perform a database update on the old primary node.
On each node of the cluster, perform the following steps to update the database server:
- Stop the Failover Manager agent.
- Stop the database server.
- Update the database server.
- Start the database service.
- Start the Failover Manager agent.
For detailed information about controlling the EDB Postgres Advanced Server service or upgrading your version of EDB Postres Advanced Server, see the EDB Postgres Advanced Server Guide
When your updates are complete, you can use the efm set-priority command to add the old primary to the front of the standby list (if needed), and then switchover to return the cluster to its original state.