9 Upgrading an Existing Cluster

Table of Contents Previous Next


9 Upgrading an Existing Cluster

When configuring the cluster for Failover Manager 2.0, please note that within the cluster properties file (now named efm.properties by default) the following properties have changed (since version 1.1.2):
The cluster.name property is no longer used. The cluster name is now the prefix of the cluster properties file (by default, efm.properties) and cluster members file (by default, efm.nodes). If a node is a member of more than one cluster, you must specify a unique name for the cluster properties and cluster members files of each cluster.
The db.reuse.connection property (a boolean value) has been replace by the db.reuse.connection.count property (a numeric value). Specifying a value of 0 for the db.reuse.connection.count property provides the same functionality as specifying false for db.reuse.connection.
The agents and witness properties have been replaced with the bind.address and is.witness properties.
Use the efm encrypt command to generate a new encrypted password for the cluster in Failover Manager 2.0. Provide the new encrypted password in the db.password.encrypted= parameter in the cluster properties file.
service ppfm-1.1 stop-cluster

9 Upgrading an Existing Cluster

Table of Contents Previous Next