Postgres as a Service
Deploy a Managed Postgres Cluster in Minutes! Enterprise-ready and Oracle compatible.
Failover Manager 2.1 provides a utility to assist you when upgrading a Failover Manager 2.0 cluster to Failover Manager 2.1. To upgrade an existing cluster, you must:
1. Invoke the efm upgrade-conf utility to create the .properties and .nodes files for Failover Manager 2.1. The Failover Manager installer adds the upgrade utility (efm upgrade-conf) to the /usr/efm-2.1/bin directory. To invoke the utility, assume root privileges, and invoke the command:efm upgrade-conf cluster_nameThe efm upgrade-conf utility locates the .properties and .nodes files of a 2.0 cluster (stored in /etc/efm-2.0) and copies the parameter values to a configuration file for use by Failover Manager 2.1. The utility saves the updated copy of the configuration files in the /etc/efm-2.1 directory for use by Failover Manager 2.1.
2. Modify the .properties and .nodes files for EFM 2.1, specifying any new preferences. Version 2.1 of Failover Manager adds the following configuration parameters:Use your choice of editor to modify any additional properties in the properties file (located in the /etc/efm-2.1 directory) before starting the service for that node.Please note: If you use an operating system service script (via the service or systemctl command) when starting and stopping the database on a non-witness node, you must provide the service name in the db.service.name parameter.The jgroups.max.tries and jgroups.timeout properties are replaced by the node.timeout property.
4. The following example demonstrates invoking the upgrade utility to create the .properties and .nodes files for an EFM 2.1 installation:[root@localhost bin]# ./efm upgrade-conf efm
Processing efm.properties file.
Setting new property node.timeout to 40 (sec) based on existing timeout 5000 (ms) and max tries 8.
Processing efm.nodes file.
Upgrade of files is finished. Please ensure that the new file permissions match those of the template files before starting EFM.
The db.service.name property should be set before starting a non-witness agent.