Table of Contents Previous Next


4 Using Failover Manager : 4.1 Managing a Failover Manager Cluster

By default, some of the commands listed below must be invoked by efm or by an OS superuser; an administrator can selectively permit users to invoke these commands by adding the user to the efm group. The commands are:
If the cluster properties file for the node specifies that is.witness is true, the node will start as a Witness node.
If the node is not a dedicated Witness node, Failover Manager will connect to the local database and invoke the pg_is_in_recovery() function. If the server responds false, the agent assumes the node is a Master node, and assigns a virtual IP address to the node (if applicable). If the server responds true, the Failover Manager agent assumes that the node is a Standby server.
1.
Assume the identity of efm or the OS superuser on any existing node (that is currently part of the running cluster), and invoke the efm add-node command, adding the IP address of the new node to the Failover Manager Allowed node host list.
efm add-node cluster_name ip_address [priority]
For more information about using the efm add-node command or controlling a Failover Manager service, see Section 5.
4.
Assume superuser privileges on the new node, and use the service efm-2.0 start command to start the Failover Manager agent:
If your Failover Manager cluster includes more than one Standby server, you can use the efm add-node command to influence the promotion priority of the Standby nodes. Invoke the command on any existing member of the Failover Manager cluster, and specify a priority value after the IP address of the member.
For example, the following command instructs Failover Manager that the acctg cluster member that is monitoring 10.0.1.9:7800 is the primary Standby (1):
You can invoke efm promote on any node of a Failover Manager cluster to start a manual promotion of a Standby database to Master database. Manual promotion should only be performed during a maintenance window for your database cluster. If you do not have an up-to-date Standby database available, you will be prompted before continuing. To start a manual promotion, assume the identity of efm or the OS superuser, and invoke the command:
efm promote cluster_name
During a manual promotion, the Master agent releases the virtual IP address before creating a recovery.conf file in the directory specified by the db.recovery.conf.dir parameter. The Master agent remains running, and assumes a status of Idle.
Until you invoke the efm remove-node command (removing the node's address of the node from the Allowed node host list), you can use the service efm-2.0 start command to restart the node at a later date without first running the efm add-node command again.
efm stop-cluster cluster_name
The command will cause all Failover Manager agents to exit. Terminating the Failover Manager agents completely disables all failover functionality.
The efm remove-node command removes the IP address of a node from the Failover Manager Allowed node host list. Assume the identity of efm or the OS superuser on any existing node (that is currently part of the running cluster), and invoke the efm remove-node command, specifying the cluster name and the IP address of the node:
efm remove-node cluster_name ip_address
The efm remove-node command will not stop a running agent; the service will continue to run on the node until you stop the agent (for information about controlling the agent, see Section 5). If the agent or cluster is subsequently stopped, the node will not be allowed to rejoin the cluster, and will be removed from the failover priority list (and will be ineligible for promotion).
After invoking the efm remove-node command, you must use the efm add-node command to add the node to the cluster again. For more information about using the efm utility, see Section 5.3.

4 Using Failover Manager : 4.1 Managing a Failover Manager Cluster

Table of Contents Previous Next