Promoting a Failover Manager Node

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> [-switchover] [-sourcenode <address>] [-quiet] [-noscripts]

Where:

<cluster_name> is the name of the Failover Manager cluster.

Include the –switchover option to reconfigure the original Master as a Standby. 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.

Include the –sourcenode keyword to specify the node from which the recovery.conf file will be copied to the master.

Include the -quiet keyword to suppress notifications during switchover.

Include the -noscripts keyword to prevent instruct Failover Manager to not invoke fencing and post-promotion scripts.

During switchover:

  • A recovery.conf file is copied from an existing standby to the master node.

  • The master database is stopped.

  • If you are using a VIP, the address is released from the master node.

  • A standby is promoted to replace the master node, and acquires the VIP.

  • The address of the new master node is added to the recovery.conf file.

  • If the recovery.conf file contains an application name, and the application.name property is set for this node, the application name will be replaced with the property value.

  • The old master is restarted; the agent will resume monitoring it as a standby.

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 property. The Master agent remains running, and assumes a status of Idle.

The Standby agent confirms that the virtual IP address is no longer in use before pinging a well-known address to ensure that the agent is not isolated from the network. The Standby agent runs the fencing script and promotes the Standby database to Master. The Standby agent then assigns the virtual IP address to the Standby node, and runs the post-promotion script (if applicable).

Please note that this command instructs the service to ignore the value specified in the auto.failover parameter in the cluster properties file.

To return a node to the role of master, place the node first in the promotion list:

efm set-priority <cluster_name> <ip_address> <priority>

Then, perform a manual promotion:

efm promote <cluster_name> ‑switchover

For more information about the efm utility, see Using the EFM Utility.