Failover Manager provides a utility to assist you when upgrading a Failover Manager cluster. To upgrade an existing cluster, you must:
2. After installing Failover Manager, invoke the efm upgrade-conf utility to create the .properties and .nodes files for Failover Manager 3.5. The Failover Manager installer adds the upgrade utility (efm upgrade-conf) to the /usr/edb/efm-3.5/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 pre-existing 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 /etc/edb/efm-3.5 directory.
3. Modify the .properties and .nodes files for EFM 3.5, specifying any new preferences. Version 3.5 of Failover Manager adds the following configuration properties:Use your choice of editor to modify any additional properties in the properties file (located in the /etc/edb/efm-3.5 directory) before starting the service for that node. For detailed information about property settings, see Section 3.5.
5. The following example demonstrates invoking the upgrade utility to create the .properties and .nodes files for a Failover Manager installation:[root@ONE efm-3.5]}> /usr/edb/efm-3.5/bin/efm upgrade-conf example
Checking directory /etc/edb/efm-3.5
Processing example.properties file
jvm.options property value updated to "-Xmx128m".
The following properties were added in addition to those in previous installed version:
Checking directory /etc/edb/efm-3.4
Processing example.nodes file
Upgrade of files is finished. The owner and group for properties and nodes files have been set as 'efm'.If you are 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 you are using a Failover Manager configuration without sudo, include the -source flag and specify the name of the directory in which the configuration files reside. If the directory is not the configuration default directory, the upgraded files will be created in the directory from which the upgrade-conf command was invoked. For more information, see Section 3.4.1.