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. If the server does not respond, the agent will start in an IDLE state.
1.
Unless auto.allow.hosts is set to true, use the efm allow-node command, to add the IP address of the new node to the Failover Manager allowed node host list. When invoking the command, specify the cluster name and the IP address of the new node:
efm allow-node cluster_name ip_address
For more information about using the efm allow-node command or controlling a Failover Manager service, see Section 5.
If your Failover Manager cluster includes more than one Standby server, you can use the efm set-priority command to influence the promotion priority of a Standby node. 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. Include the –switchover option to reconfigure the original Master as a Standby.
efm promote cluster_name [-switchover]
Please note that if you include the –switchover keyword, the cluster must include a master node and at least one standby, and the nodes must be in sync. During switchover:
A recovery.conf file is copied from an existing standby to the master node.
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.
efm set-priority cluster_name ip_address priority
efm promote cluster_name switchover
Until you invoke the efm disallow -node command (removing the node's address of the node from the Allowed node host list), you can use the service efm-2.1 start command to restart the node at a later date without first running the efm allow-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.
Please Note: when you invoke the efm stop-cluster command, all authorized node information is lost from the Allowed node host list. For detailed information about restarting a Failover Manager cluster, please see Section 4.1.7.
2.
Unless the auto.allow.hosts parameter is set to true, use the efm allow-node command to add the IP address of each node of the cluster to the Failover Manager Allowed node host list. When invoking the command, specify the cluster name and the IP address of the node:
efm allow-node cluster_name ip_address
If a node's address is not in the allowed node host list before you start the Failover Manager agent on a member node, Failover Manager will write the following error to the startup-efm.log file:
There was an error starting service: authentication failed
If other nodes are already running in the cluster, please verify that the address for this node is on the allowed node host list.
The efm disallow -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 disallow -node command, specifying the cluster name and the IP address of the node:
efm disallow -node cluster_name ip_address
The efm disallow -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 disallow -node command, you must use the efm allow-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