In summary, both servers should be ready for failover, but left in standby status. If the primary server is in failover active status, then enter '''failoverUtil setServer standby''' to bring it to standby status.

* If you switch on replication with sync via the mp_replication switchON command and replication fails, it is possible that a table is locking due to the processes on an active server. To resolve this issue, run the mp_replication switchON with sync command again.

* During this process, you may see several error messages. These error messages are expected behavior and informational only. The final message of the command explicitly says if the command ran successfully or not.

* During this process, you may see several error messages. These error messages are expected behavior and informational only. The final message of the command explicitly says if the command ran successfully or not.

Line 253:

Line 256:

# Go to '''http://''<application-server>''/admin/'''.

# Go to '''http://''<application-server>''/admin/'''.

#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.

#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.

+

#: The "copyConfigFiles" commands will include recorded name files as well.

## Verify that "Failover deployment. Standby server." appears at the top of the page.

## Verify that "Failover deployment. Standby server." appears at the top of the page.

-

## Configure the server-specific parameters on the standby server.

+

## Configure the server-specific parameters on the standby server.

+

+

===== What to Do Next =====

+

+

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

+

# Log in to the CLI of the active server.

+

#:If you are logging in remotely, use the eth0 IP address or hostname.

+

# Enter the following command to compress and transfer the files from the active server to the standby server:

+

#:'''failoverUtil copyConfigFiles'''

+

#:This will compress and copy over configuration files and user prompts to the remote server.

+

# Log in to the CLI of the standby server.

+

#:If you are logging in remotely, use eth0:0 IP address or hostname.

+

# Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:

+

#:'''failoverUtil restoreConfigFiles'''

+

#:This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.

Setting Up Failover for Two Newly Installed Application Servers

Before You Begin

In summary, both servers should be ready for failover, but left in standby status. If the primary server is in failover active status, then enter failoverUtil setServer standby to bring it to standby status.

Procedure

Install the first Application Server (Node 1).

During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.

Install any licenses on the first Application Server (Node 1). See About Licenses for information about licenses.

Enter the following command to change Node 1 from standby mode to active mode:

failoverUtil setServer active

Note: Node must be active to add licenses (step 7)

Verifying

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

To verify that the replication was successful, log in to both nodes (eth0:0 interface) as root user and enter the mp_replication status command. The following should display in your output:

Local Server

Remote Server

Replication Type: Local

Site: 1

Node: 1

State: Active

Status: Local

Replication Type: Intra-site

Site: 1

Node: 2

State: Active

Status: Connected

Troubleshooting Tips

If the Administration Center in both nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in Step 12. To resolve this issue, see the failoverUtil setServer command description.

If you switch on replication with sync via the mp_replication switchON command and replication fails, it is possible that a table is locking due to the processes on an active server. To resolve this issue, run the mp_replication switchON with sync command again.

During this process, you may see several error messages. These error messages are expected behavior and informational only. The final message of the command explicitly says if the command ran successfully or not.

Procedure

Install the second Application Server (Node 2), ensuring the following:

To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.

This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.

Node 1 and Node 2 server times must be synchronized with each other.

Log in to the CLI of Node 1.

If you are logging in remotely, use the Node 1 eth0 IP address or hostname.

Enter the following command to change Node 1 from standby mode to active mode:

failoverUtil setServer active

Verifying

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

To verify that the replication was successful, log in to both nodes (eth0:0 interface) as root user and enter the mp_replication status command. The following should display in your output:

Local Server

Remote Server

Replication Type: Local

Site: 1

Node: 1

State: Active

Status: Local

Replication Type: Intra-site

Site: 1

Node: 2

State: Active

Status: Connected

Troubleshooting Tips

If the Administration Center in both nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in Step 14. To resolve this issue, see the failoverUtil setServer command description.

If you switch on replication with sync via the mp_replication switchON command and replication fails, it is possible that a table is locking due to the processes on an active server. To resolve this issue, run the mp_replication switchON with sync command again.

During this process, you may see several error messages. These error messages are expected behavior and informational only. The final message of the command explicitly says if the command ran successfully or not.

Take note of any changes you make on pages or fields that are labeled as:

Copied

Server-specific

Partially replicated

If you made changes to any copied pages or parameters, perform the following steps:

Log in to the CLI of the active server.

If you are logging in remotely, use the eth0 IP address or hostname.

Enter the following command to compress and transfer the files from the active server to the standby server:

failoverUtil copyConfigFiles

Log in to the CLI of the standby server.

If you are logging in remotely, use eth0:0 IP address or hostname.

Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:

failoverUtil restoreConfigFiles

If you made changes to any server-specific pages or parameters, perform the following steps.

Tip: If your workstation screen is large enough to accommodate two full web browser windows without overlapping, you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.

Go to http://standby-eth0:0/admin/.

Use either the hostname or IP address of the virtual eth0:0 interface of the standby Application Server.

Verify that "Failover deployment. Standby server." appears at the top of the page.

Configure the server-specific parameters on the standby server.

What to Do Next

Perform the following from both Application Servers to replicate custom prompts and some configurations from the Primary application server to the Standby application server during a maintenance window or off-peak hours.

Log in to the CLI of the active server.

If you are logging in remotely, use the eth0 IP address or hostname.

Enter the following command to compress and transfer the files from the active server to the standby server:

failoverUtil copyConfigFiles

This will compress and copy over configuration files and user prompts to the remote server.

Log in to the CLI of the standby server.

If you are logging in remotely, use eth0:0 IP address or hostname.

Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:

failoverUtil restoreConfigFiles

This action copies over custom prompts including customized system prompts and user name recordings. Without this action .wav files are not replicated to the standby server.