Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x - Replacing Cisco Unity Connection 7.x Servers [Cisco Unity Connection]

Table Of Contents

Replacing Cisco Unity Connection 7.x Servers

Replacing a Single 7.x Server Without a Connection Cluster

Replacing a 7.x Publisher Server in a Connection Cluster

Replacing a 7.x Subscriber Server in a Connection Cluster

Replacing the 7.x Publisher and Subscriber Servers in a Connection Cluster

When Both Original Servers Are Available and Functioning

When Neither the Publisher Nor the Subscriber Server Is Functioning

Replacing Cisco Unity Connection 7.x Servers

This chapter contains the following sections:

•Replacing a Single 7.x Server Without a Connection Cluster

•Replacing a 7.x Publisher Server in a Connection Cluster

•Replacing a 7.x Subscriber Server in a Connection Cluster

•Replacing the 7.x Publisher and Subscriber Servers in a Connection Cluster

Replacing a Single 7.x Server Without a Connection Cluster

Use the high-level task list in this section to replace a single Connection 7.x server correctly.

Note Do the same tasks if Digital Networking is configured. After data is restored on the replacement server, Digital Networking automatically starts working again.

1. Use the Disaster Recovery System to back up the Connection server. See the Disaster Recovery System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/drs_administration/guide/7xcucdrsag.html.

2. Install the new server. See "Part 1: Installing and Configuring the Cisco Unity Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

3. Use the Disaster Recovery System to restore data on the new Connection server. See the Disaster Recovery System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/drs_administration/guide/7xcucdrsag.html.

4. Disconnect the old server from the network.

Replacing a 7.x Publisher Server in a Connection Cluster

Revised August 26, 2009

You can replace the publisher server in a Connection cluster without replacing the subscriber server. During the time that the publisher server is not functioning, the subscriber server will handle all functions for the Connection cluster to avoid loss of service to the system. After removing the publisher server, a replacement publisher server is installed because the subscriber server cannot be converted into the publisher server. On the replacement publisher server, a new Connection cluster is configured. When the subscriber server is connected to the new Connection cluster, the subscriber server will replicate its data to the replacement publisher server without loss of service to the system. When the replacement publisher server has Primary or Secondary status, it will handle calls.

Note that you must order a replacement Connection license that includes the MAC address of the replacement publisher server. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

Do the six procedures in this section in the order listed.

Caution If you are using Digital Networking, you must disable it before doing the procedures in this section. For instructions, see the "Using Digital Networking" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

To Manually Change the Subscriber Server to Primary Status

Step 1 Log on to Cisco Unity Connection Serviceability.

Step 2 On the Tools menu, click Cluster Management.

Step 3 On the Cluster Management page, under Server Manager, locate the subscriber server.

Step 4 If the subscriber server has Primary status, skip the remaining steps in this procedure and skip to the next procedure.

If the subscriber server has Secondary status, skip to Step 5.

If the subscriber has Deactivated status, change the status to Secondary:

a. In the Change Server Status column for the subscriber server, click Activate.

b. When prompted to confirm changing the server status, click OK.

c. Confirm that the Server Status column indicates that the subscriber server now has Secondary status.

Step 5 In the Change Server Status column for the subscriber server, click Make Primary.

Step 6 When prompted to confirm changing the server status, click OK.

The Server Status column displays the changed status when the change is complete.

Note The publisher server will automatically change to Secondary status.

To Manually Change the Publisher Server from Secondary Status to Deactivated Status

Step 1 Log on to the Real-Time Monitoring Tool (RTMT).

Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane.

Step 3 In the Node field, click the publisher server.

Step 4 In the right pane, click Start Polling.

Step 5 Note whether any voice messaging ports are currently handling calls for the server.

Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability.

Step 7 If no voice messaging ports are currently handling calls for the publisher server, skip to Step 8.

If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the publisher server, then wait until RTMT shows that all ports for the publisher server are idle.

Step 8 Under Server Manager, in the Change Server Status column for the publisher server, click Deactivate.

Step 9 When prompted to confirm changing the server status, click OK.

The Server Status column displays the changed server status when the change is complete.

To Remove the Publisher Server from the Environment

Step 1 Shut down the publisher server.

On the Cluster Management page, the Server Status column shows the publisher server has Not Functioning status.

Step 2 Disconnect the network cable from the publisher server.

The publisher server can be removed from the environment.

To Install the Replacement Publisher Server

Follow the instructions in "Part 1: Installing and Configuring the Cisco Unity Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly.

The replacement publisher server must have the same host name as the publisher server that you removed. Otherwise, the Connection cluster will not be able to function.

You must install a replacement license that includes the MAC address of the replacement publisher server. Otherwise, the server will not function.

To Configure the Cluster on the Replacement Publisher Server

Step 1 Log on to Cisco Unity Connection Administration on the publisher server.

Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster.

Step 3 On the Find and List Servers page, click Add New.

Step 4 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the subscriber server.

Step 5 In the Description field, enter Server 2 or another description for the server.

Step 6 Click Save.

Step 7 Log off Cisco Unity Connection Administration.

To Connect the Subscriber Server to the New Connection Cluster

Step 1 Log on to the command-line interface (CLI) for the subscriber server.

Step 2 Run the CLI command utils cuc cluster renegotiate.

Note When the CLI command completes, the publisher server automatically restarts.

Step 3 Run the CLI command show cuc cluster status on the subscriber server to confirm that the new Connection cluster has been configured correctly.

Replacing a 7.x Subscriber Server in a Connection Cluster

Revised May 2009

You can replace the subscriber server in a Connection cluster without replacing the publisher server. During the time that the subscriber server is not functioning, the publisher server will handle all functions for the Connection cluster to avoid loss of service to the system. On the publisher server, the subscriber server is removed from the Connection cluster and the replacement secondary server is added. The replacement subscriber server is installed. The publisher server will replicate its data to the replacement subscriber server without loss of service to the system. When the replacement subscriber server has Primary or Secondary status, it will handle calls.

Note that you must order a replacement Connection license that includes the MAC address of the replacement subscriber server. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

Do the six procedures in this section in the order listed.

Caution If you are using Digital Networking, you must disable it before doing the procedures in this section. For instructions, see the "Using Digital Networking" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

To Manually Change the Publisher Server to Primary Status

Step 1 Log on to Cisco Unity Connection Serviceability.

Step 2 On the Tools menu, click Cluster Management.

Step 3 On the Cluster Management page, under Server Manager, locate the publisher server.

Step 4 If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next procedure.

If the publisher server has Secondary status, skip to Step 5.

If the publisher has Deactivated status, change the status to Secondary:

a. In the Change Server Status column for the publisher server, click Activate.

b. When prompted to confirm changing the server status, click OK.

c. Confirm that the Server Status column indicates that the publisher server now has Secondary status.

Step 5 In the Change Server Status column for the publisher server, click Make Primary.

Step 6 When prompted to confirm changing the server status, click OK.

The Server Status column displays the changed status when the change is complete.

Note The subscriber server automatically changes to Secondary status.

To Manually Change the Subscriber Server from Secondary Status to Deactivated Status

Step 1 Log on to the Real-Time Monitoring Tool (RTMT).

Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane.

Step 3 In the Node field, click the subscriber server.

Step 4 In the right pane, click Start Polling.

Step 5 Note whether any voice messaging ports are currently handling calls for the server.

Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability.

Step 7 If no voice messaging ports are currently handling calls for the server, skip to Step 8.

If there are voice messaging ports that are currently handling calls for the subscriber server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the subscriber server, then wait until RTMT shows that all ports for the server are idle.

Step 8 Under Server Manager, in the Change Server Status column for the subscriber server, click Deactivate.

Step 9 When prompted to confirm changing server status, click OK.

The Server Status column displays the changed server status when the change is complete.

To Remove the Subscriber Server from the Environment

Step 1 Shut down the subscriber server.

On the Cluster Management page, the Server Status column shows the subscriber server has Not Functioning status.

Step 2 Disconnect the network cable from the subscriber server.

The subscriber server can be removed from the environment.

To Remove the Subscriber Server and Add the Replacement Subscriber Server to the Connection Cluster

Step 1 If the replacement subscriber server will have the same host name or IP address as the subscriber server that you removed, skip the remaining steps in this procedure and skip to the next procedure.

If the replacement subscriber server will have a different host name or IP address, log on to Cisco Unity Connection Administration on the publisher server.

Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster.

Step 3 On the Find and List Servers page, click Find to display all servers in the cluster.

Step 4 Check the check box in front of the subscriber server and click Delete Selected.

Step 5 When prompted to confirm deleting the server, click OK.

Step 6 Click Add New.

Step 7 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the replacement server.

Step 8 In the Description field, enter Server 2 or another description for the server.

Step 9 Click Save.

Step 10 Log off Cisco Unity Connection Administration.

To Install the Replacement Subscriber Server

Follow the instructions in "Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x system with a Connection Cluster Configured" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly.

You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function.

To Confirm That the Connection Cluster Is Configured

Step 1 Log on to the command-line interface (CLI) for the subscriber server.

Step 2 Run the CLI command show cuc cluster status.

Replacing the 7.x Publisher and Subscriber Servers in a Connection Cluster

See the applicable section:

•When Both Original Servers Are Available and Functioning

•When Neither the Publisher Nor the Subscriber Server Is Functioning

When Both Original Servers Are Available and Functioning

Revised August 26, 2009

When both the publisher and subscriber servers in the Connection cluster are available and functioning, you can replace both servers by completing the process in stages. While you are replacing the subscriber server, the publisher server will handle all functions for the Connection cluster to avoid loss of service to the system. On the publisher server, the subscriber server is removed from the Connection cluster and the replacement secondary server is added. The replacement subscriber server is installed. The publisher server will replicate its data to the replacement subscriber server without loss of service to the system. When the replacement subscriber server has Primary or Secondary status, it will handle calls. While you are replacing the publisher server, the replacement subscriber server will handle all functions for the Connection cluster to avoid loss of service to the system. After removing the publisher server, a replacement publisher server is installed because the subscriber server cannot be converted into the publisher server. On the replacement publisher server, a new Connection cluster is configured. When the subscriber server is connected to the new Connection cluster, the subscriber server will replicate its data to the replacement publisher server without loss of service to the system. When the replacement publisher server has Primary or Secondary status, it will handle calls.

Note that you must order replacement Connection licenses that includes the MAC addresses of the replacement servers. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

Do the 12 procedures in this section in the order listed.

Caution If you are using Digital Networking, you must disable it before doing the procedures in this section. For instructions, see the "Using Digital Networking" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

To Manually Change the Publisher Server to Primary Status

Step 1 Log on to Cisco Unity Connection Serviceability.

Step 2 On the Tools menu, click Cluster Management.

Step 3 On the Cluster Management page, under Server Manager, locate the publisher server.

Step 4 If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next procedure.

If the publisher server has Secondary status, skip to Step 5.

If the publisher has Deactivated status, change the status to Secondary:

a. In the Change Server Status column for the publisher server, click Activate.

b. When prompted to confirm changing the server status, click OK.

c. Confirm that the Server Status column indicates that the publisher server now has Secondary status.

Step 5 In the Change Server Status column for the publisher server, click Make Primary.

Step 6 When prompted to confirm changing the server status, click OK.

The Server Status column displays the changed status when the change is complete.

Note The subscriber server automatically changes to Secondary status.

To Manually Change a Subscriber Server from Secondary Status to Deactivated Status

Step 1 Log on to the Real-Time Monitoring Tool (RTMT).

Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane.

Step 3 In the Node field, click the subscriber server.

Step 4 In the right pane, click Start Polling.

Step 5 Note whether any voice messaging ports are currently handling calls for the server.

Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability.

Step 7 If no voice messaging ports are currently handling calls for the server, continue to Step 8.

If there are voice messaging ports that are currently handling calls for the subscriber server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the subscriber server, then wait until RTMT shows that all ports for the server are idle.

Step 8 Under Server Manager, in the Change Server Status column for the subscriber server, click Deactivate.

Step 9 When prompted to confirm changing server status, click OK.

The Server Status column displays the changed server status when the change is complete.

To Remove the Subscriber Server from the Environment

Step 1 Shut down the subscriber server.

On the Cluster Management page, the Server Status column shows the subscriber server has Not Functioning status.

Step 2 Disconnect the network cable from the subscriber server.

The subscriber server can be removed from the environment.

To Remove the Subscriber Server and Add the Replacement Subscriber Server to the Connection Cluster

Step 1 If the replacement subscriber server will have the same host name or IP address as the subscriber server that you removed, skip the remaining steps in this procedure and skip to the next procedure.

If the replacement subscriber server will have a different host name or IP address, log on to Cisco Unity Connection Administration on the publisher server.

Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster.

Step 3 On the Find and List Servers page, click Find to display all servers in the cluster.

Step 4 Check the check box in front of the subscriber server and click Delete Selected.

Step 5 When prompted to confirm deleting the server, click OK.

Step 6 Click Add New.

Step 7 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the replacement server.

Step 8 In the Description field, enter Server 2 or another description for the server.

Step 9 Click Save.

Step 10 Log off Cisco Unity Connection Administration.

To Install the Replacement Subscriber Server

Follow the instructions in "Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x system with a Connection Cluster Configured" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly.

You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function.

To Confirm That the Connection Cluster Is Configured with the Replacement Subscriber Server

Step 1 Log on to the command-line interface (CLI) for the subscriber server.

Step 2 Run the CLI command show cuc cluster status.

To Manually Change the Subscriber Server to Primary Status

Step 1 Log on to Cisco Unity Connection Serviceability.

Step 2 On the Tools menu, click Cluster Management.

Step 3 On the Cluster Management page, under Server Manager, locate the subscriber server.

Step 4 If the subscriber server has Primary status, skip the remaining steps in this procedure and continue to the next procedure. If the subscriber server has Secondary status, in the Change Server Status column for the subscriber server, click Make Primary.

Step 5 When prompted to confirm changing the server status, click OK.

The Server Status column displays the changed status when the change is complete.

Note The publisher server will automatically change to Secondary status.

To Manually Change the Publisher Server from Secondary Status to Deactivated Status

Step 1 Log on to the Real-Time Monitoring Tool (RTMT).

Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane.

Step 3 In the Node field, click the publisher server.

Step 4 In the right pane, click Start Polling.

Step 5 Note whether any voice messaging ports are currently handling calls for the server.

Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability.

Step 7 If no voice messaging ports are currently handling calls for the publisher server, skip to Step 8.

If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the publisher server, then wait until RTMT shows that all ports for the publisher server are idle.

Step 8 Under Server Manager, in the Change Server Status column for the publisher server, click Deactivate.

Step 9 When prompted to confirm changing the server status, click OK.

The Server Status column displays the changed server status when the change is complete.

To Remove the Publisher Server from the Environment

Step 1 Shut down the publisher server.

On the Cluster Management page, the Server Status column shows the publisher server has Not Functioning status.

Step 2 Disconnect the network cable from the publisher server.

The publisher server can be removed from the environment.

To Install the Replacement Publisher Server

Follow the instructions in "Part 1: Installing and Configuring the Cisco Unity Connection Server" of the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly.

The replacement publisher server must have the same host name as the publisher server that you removed. Otherwise, the Connection cluster will not be able to function.

You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function.

To Configure the Cluster on the Replacement Publisher Server

Step 1 Log on to Cisco Unity Connection Administration on the publisher server.

Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster.

Step 3 On the Find and List Servers page, click Add New.

Step 4 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the subscriber server.

Step 5 In the Description field, enter Server 2 or another description for the server.

Step 6 Click Save.

Step 7 Log off Cisco Unity Connection Administration.

To Connect the Subscriber Server to the New Connection Cluster

Step 1 Log on to the command-line interface (CLI) for the subscriber server.

Step 2 Run the CLI command utils cuc cluster renegotiate.

Note When the CLI command completes, the publisher server automatically restarts.

Step 3 Run the CLI command show cuc cluster status to confirm that the new Connection cluster has been configured correctly.

When Neither the Publisher Nor the Subscriber Server Is Functioning

Added May 2009

When neither the publisher nor the subscriber server in the Connection cluster is functioning, and you have a Disaster Recovery System backup from which you can restore the Connection data, you can replace both servers at the same time. During this process, the Connection cluster is not able to answer calls.

You install the replacement publisher server and restore the backed-up Connection data by using Disaster Recovery System. Then you install the replacement subscriber server and force Connection to copy the data from the publisher server to the subscriber server. When the copying is complete, replication will resume between the two servers. When the replacement servers have Primary or Secondary status, they will handle calls.

Note that you must order replacement Connection licenses that includes the MAC addresses of the replacement servers. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

Do the five procedures in this section in the order listed.

To Install the Replacement Publisher Server

Follow the instructions in "Part 1: Installing and Configuring the Cisco Unity Connection Server" of the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly.

The publisher server must have the same IP address and host name as the server from which Disaster Recovery System backed up the data. Otherwise, Disaster Recovery System Disaster Recovery System will not restore the data.

You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function.

To Restore the Backed-up Data to the Replacement Publisher Server

Step 1 Log on to Disaster Recovery System.

Step 2 On the Restore menu, click Restore Wizard.

Step 3 On the Step 1 Restore—Choose Backup Device page, in the Device Name field, click the name of the backup device from which you want to restore and click Next.

Step 4 On the Step 2 Restore—Choose the Backup Tar File page, in Select Backup File field, click the backup file that you want to restore and click Next.

Note The backup filename indicates the date and time that the system created the backup file.

Step 5 In the Step 3 Restore—Select the Type of Restore page, under Special Features, check the check boxes for the features that you want to restore and click Next.

Note Only the features that were backed up to the file that you chose will appear on the page.

Step 6 In the Step 4 Restore—Final Warning for Restore page, in the Select the Server field, click the publisher server and click Restore.

Caution The publisher server must have the same IP address and host name as the server from which Disaster Recovery System backed up the data. Otherwise, Disaster Recovery System Disaster Recovery System will not restore the data.

Note During the restore process, do not perform any tasks with Connection Administration.

Step 7 When the restore status indicates 100 percent, restart the publisher server.

To Install the Replacement Subscriber Server

Follow the instructions in "Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x system with a Connection Cluster Configured" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly.

You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function.

To Copy the Data from the Publisher Server to the Subscriber Server

Step 1 Log on to the command-line interface (CLI) for the subscriber server.

Step 2 Run the CLI command utils cuc cluster overwritedb to force Connection to copy data from the publisher server to the subscriber server:

Step 3 Run the CLI command show cuc cluster status to confirm that the new Connection cluster has been configured correctly on the subscriber server.

Step 4 Log on to the CLI for the publisher server.

Step 5 Run the CLI command show cuc cluster status to confirm that the new Connection cluster has been configured correctly on the publisher server.

To Synchronize MWIs for Each Phone System

Step 1 During off-peak hours, log on to either server in the Connection cluster.

Step 2 In Connection Administration, expand Telephony Integrations, then click Phone System.

Step 3 On the Search Phone Systems page, click the name of the first phone system.

Step 4 On the Phone System Basics page, under Messaging Waiting Indicators, click Run.

Step 5 Click Next.

Step 6 Repeat Step 4 and Step 5 for the remaining phone systems.

	Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x
	Replacing Cisco Unity Connection 7.x Servers
Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x Index Preface Upgrading Cisco Unity Connection 7.x to the Shipping 7.x Version Upgrading Cisco Unity Connection 2.x to the Shipping 7.x Version Reverting Servers to the Cisco Unity Connection Version on the Inactive Partition Migrating from Cisco Unity Connection 1.x to Version 7.x Migrating from Cisco Unity 4.x or Later to Cisco Unity Connection 7.x Adding Languages to the Cisco Unity Connection 7.x System Replacing Cisco Unity Connection 7.x Servers Creating or Changing a Cisco Unity Connection 7.x Cluster Changing the IP Addresses of Cisco Unity Connection 7.x Servers Renaming Cisco Unity Connection 7.x Servers	Download this chapter Replacing Cisco Unity Connection 7.x Servers Download the complete book PDF Version of the Entire Guide (PDF - 2 MB) Table Of Contents Replacing Cisco Unity Connection 7.x Servers Replacing a Single 7.x Server Without a Connection Cluster Replacing a 7.x Publisher Server in a Connection Cluster Replacing a 7.x Subscriber Server in a Connection Cluster Replacing the 7.x Publisher and Subscriber Servers in a Connection Cluster When Both Original Servers Are Available and Functioning When Neither the Publisher Nor the Subscriber Server Is Functioning Replacing Cisco Unity Connection 7.x Servers This chapter contains the following sections: •Replacing a Single 7.x Server Without a Connection Cluster •Replacing a 7.x Publisher Server in a Connection Cluster •Replacing a 7.x Subscriber Server in a Connection Cluster •Replacing the 7.x Publisher and Subscriber Servers in a Connection Cluster Replacing a Single 7.x Server Without a Connection Cluster Use the high-level task list in this section to replace a single Connection 7.x server correctly. Note Do the same tasks if Digital Networking is configured. After data is restored on the replacement server, Digital Networking automatically starts working again. 1. Use the Disaster Recovery System to back up the Connection server. See the Disaster Recovery System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/drs_administration/guide/7xcucdrsag.html. 2. Install the new server. See "Part 1: Installing and Configuring the Cisco Unity Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html. 3. Use the Disaster Recovery System to restore data on the new Connection server. See the Disaster Recovery System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/drs_administration/guide/7xcucdrsag.html. 4. Disconnect the old server from the network. Replacing a 7.x Publisher Server in a Connection Cluster Revised August 26, 2009 You can replace the publisher server in a Connection cluster without replacing the subscriber server. During the time that the publisher server is not functioning, the subscriber server will handle all functions for the Connection cluster to avoid loss of service to the system. After removing the publisher server, a replacement publisher server is installed because the subscriber server cannot be converted into the publisher server. On the replacement publisher server, a new Connection cluster is configured. When the subscriber server is connected to the new Connection cluster, the subscriber server will replicate its data to the replacement publisher server without loss of service to the system. When the replacement publisher server has Primary or Secondary status, it will handle calls. Note that you must order a replacement Connection license that includes the MAC address of the replacement publisher server. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html. Do the six procedures in this section in the order listed. Caution If you are using Digital Networking, you must disable it before doing the procedures in this section. For instructions, see the "Using Digital Networking" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html. To Manually Change the Subscriber Server to Primary Status Step 1 Log on to Cisco Unity Connection Serviceability. Step 2 On the Tools menu, click Cluster Management. Step 3 On the Cluster Management page, under Server Manager, locate the subscriber server. Step 4 If the subscriber server has Primary status, skip the remaining steps in this procedure and skip to the next procedure. If the subscriber server has Secondary status, skip to Step 5. If the subscriber has Deactivated status, change the status to Secondary: a. In the Change Server Status column for the subscriber server, click Activate. b. When prompted to confirm changing the server status, click OK. c. Confirm that the Server Status column indicates that the subscriber server now has Secondary status. Step 5 In the Change Server Status column for the subscriber server, click Make Primary. Step 6 When prompted to confirm changing the server status, click OK. The Server Status column displays the changed status when the change is complete. Note The publisher server will automatically change to Secondary status. To Manually Change the Publisher Server from Secondary Status to Deactivated Status Step 1 Log on to the Real-Time Monitoring Tool (RTMT). Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane. Step 3 In the Node field, click the publisher server. Step 4 In the right pane, click Start Polling. Step 5 Note whether any voice messaging ports are currently handling calls for the server. Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability. Step 7 If no voice messaging ports are currently handling calls for the publisher server, skip to Step 8. If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the publisher server, then wait until RTMT shows that all ports for the publisher server are idle. Step 8 Under Server Manager, in the Change Server Status column for the publisher server, click Deactivate. Step 9 When prompted to confirm changing the server status, click OK. The Server Status column displays the changed server status when the change is complete. To Remove the Publisher Server from the Environment Step 1 Shut down the publisher server. On the Cluster Management page, the Server Status column shows the publisher server has Not Functioning status. Step 2 Disconnect the network cable from the publisher server. The publisher server can be removed from the environment. To Install the Replacement Publisher Server Follow the instructions in "Part 1: Installing and Configuring the Cisco Unity Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html. Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly. The replacement publisher server must have the same host name as the publisher server that you removed. Otherwise, the Connection cluster will not be able to function. You must install a replacement license that includes the MAC address of the replacement publisher server. Otherwise, the server will not function. To Configure the Cluster on the Replacement Publisher Server Step 1 Log on to Cisco Unity Connection Administration on the publisher server. Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster. Step 3 On the Find and List Servers page, click Add New. Step 4 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the subscriber server. Step 5 In the Description field, enter Server 2 or another description for the server. Step 6 Click Save. Step 7 Log off Cisco Unity Connection Administration. To Connect the Subscriber Server to the New Connection Cluster Step 1 Log on to the command-line interface (CLI) for the subscriber server. Step 2 Run the CLI command utils cuc cluster renegotiate. Note When the CLI command completes, the publisher server automatically restarts. Step 3 Run the CLI command show cuc cluster status on the subscriber server to confirm that the new Connection cluster has been configured correctly. Replacing a 7.x Subscriber Server in a Connection Cluster Revised May 2009 You can replace the subscriber server in a Connection cluster without replacing the publisher server. During the time that the subscriber server is not functioning, the publisher server will handle all functions for the Connection cluster to avoid loss of service to the system. On the publisher server, the subscriber server is removed from the Connection cluster and the replacement secondary server is added. The replacement subscriber server is installed. The publisher server will replicate its data to the replacement subscriber server without loss of service to the system. When the replacement subscriber server has Primary or Secondary status, it will handle calls. Note that you must order a replacement Connection license that includes the MAC address of the replacement subscriber server. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html. Do the six procedures in this section in the order listed. Caution If you are using Digital Networking, you must disable it before doing the procedures in this section. For instructions, see the "Using Digital Networking" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html. To Manually Change the Publisher Server to Primary Status Step 1 Log on to Cisco Unity Connection Serviceability. Step 2 On the Tools menu, click Cluster Management. Step 3 On the Cluster Management page, under Server Manager, locate the publisher server. Step 4 If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next procedure. If the publisher server has Secondary status, skip to Step 5. If the publisher has Deactivated status, change the status to Secondary: a. In the Change Server Status column for the publisher server, click Activate. b. When prompted to confirm changing the server status, click OK. c. Confirm that the Server Status column indicates that the publisher server now has Secondary status. Step 5 In the Change Server Status column for the publisher server, click Make Primary. Step 6 When prompted to confirm changing the server status, click OK. The Server Status column displays the changed status when the change is complete. Note The subscriber server automatically changes to Secondary status. To Manually Change the Subscriber Server from Secondary Status to Deactivated Status Step 1 Log on to the Real-Time Monitoring Tool (RTMT). Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane. Step 3 In the Node field, click the subscriber server. Step 4 In the right pane, click Start Polling. Step 5 Note whether any voice messaging ports are currently handling calls for the server. Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability. Step 7 If no voice messaging ports are currently handling calls for the server, skip to Step 8. If there are voice messaging ports that are currently handling calls for the subscriber server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the subscriber server, then wait until RTMT shows that all ports for the server are idle. Step 8 Under Server Manager, in the Change Server Status column for the subscriber server, click Deactivate. Step 9 When prompted to confirm changing server status, click OK. The Server Status column displays the changed server status when the change is complete. To Remove the Subscriber Server from the Environment Step 1 Shut down the subscriber server. On the Cluster Management page, the Server Status column shows the subscriber server has Not Functioning status. Step 2 Disconnect the network cable from the subscriber server. The subscriber server can be removed from the environment. To Remove the Subscriber Server and Add the Replacement Subscriber Server to the Connection Cluster Step 1 If the replacement subscriber server will have the same host name or IP address as the subscriber server that you removed, skip the remaining steps in this procedure and skip to the next procedure. If the replacement subscriber server will have a different host name or IP address, log on to Cisco Unity Connection Administration on the publisher server. Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster. Step 3 On the Find and List Servers page, click Find to display all servers in the cluster. Step 4 Check the check box in front of the subscriber server and click Delete Selected. Step 5 When prompted to confirm deleting the server, click OK. Step 6 Click Add New. Step 7 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the replacement server. Step 8 In the Description field, enter Server 2 or another description for the server. Step 9 Click Save. Step 10 Log off Cisco Unity Connection Administration. To Install the Replacement Subscriber Server Follow the instructions in "Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x system with a Connection Cluster Configured" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html. Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly. You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function. To Confirm That the Connection Cluster Is Configured Step 1 Log on to the command-line interface (CLI) for the subscriber server. Step 2 Run the CLI command show cuc cluster status. Replacing the 7.x Publisher and Subscriber Servers in a Connection Cluster See the applicable section: •When Both Original Servers Are Available and Functioning •When Neither the Publisher Nor the Subscriber Server Is Functioning When Both Original Servers Are Available and Functioning Revised August 26, 2009 When both the publisher and subscriber servers in the Connection cluster are available and functioning, you can replace both servers by completing the process in stages. While you are replacing the subscriber server, the publisher server will handle all functions for the Connection cluster to avoid loss of service to the system. On the publisher server, the subscriber server is removed from the Connection cluster and the replacement secondary server is added. The replacement subscriber server is installed. The publisher server will replicate its data to the replacement subscriber server without loss of service to the system. When the replacement subscriber server has Primary or Secondary status, it will handle calls. While you are replacing the publisher server, the replacement subscriber server will handle all functions for the Connection cluster to avoid loss of service to the system. After removing the publisher server, a replacement publisher server is installed because the subscriber server cannot be converted into the publisher server. On the replacement publisher server, a new Connection cluster is configured. When the subscriber server is connected to the new Connection cluster, the subscriber server will replicate its data to the replacement publisher server without loss of service to the system. When the replacement publisher server has Primary or Secondary status, it will handle calls. Note that you must order replacement Connection licenses that includes the MAC addresses of the replacement servers. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html. Do the 12 procedures in this section in the order listed. Caution If you are using Digital Networking, you must disable it before doing the procedures in this section. For instructions, see the "Using Digital Networking" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html. To Manually Change the Publisher Server to Primary Status Step 1 Log on to Cisco Unity Connection Serviceability. Step 2 On the Tools menu, click Cluster Management. Step 3 On the Cluster Management page, under Server Manager, locate the publisher server. Step 4 If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next procedure. If the publisher server has Secondary status, skip to Step 5. If the publisher has Deactivated status, change the status to Secondary: a. In the Change Server Status column for the publisher server, click Activate. b. When prompted to confirm changing the server status, click OK. c. Confirm that the Server Status column indicates that the publisher server now has Secondary status. Step 5 In the Change Server Status column for the publisher server, click Make Primary. Step 6 When prompted to confirm changing the server status, click OK. The Server Status column displays the changed status when the change is complete. Note The subscriber server automatically changes to Secondary status. To Manually Change a Subscriber Server from Secondary Status to Deactivated Status Step 1 Log on to the Real-Time Monitoring Tool (RTMT). Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane. Step 3 In the Node field, click the subscriber server. Step 4 In the right pane, click Start Polling. Step 5 Note whether any voice messaging ports are currently handling calls for the server. Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability. Step 7 If no voice messaging ports are currently handling calls for the server, continue to Step 8. If there are voice messaging ports that are currently handling calls for the subscriber server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the subscriber server, then wait until RTMT shows that all ports for the server are idle. Step 8 Under Server Manager, in the Change Server Status column for the subscriber server, click Deactivate. Step 9 When prompted to confirm changing server status, click OK. The Server Status column displays the changed server status when the change is complete. To Remove the Subscriber Server from the Environment Step 1 Shut down the subscriber server. On the Cluster Management page, the Server Status column shows the subscriber server has Not Functioning status. Step 2 Disconnect the network cable from the subscriber server. The subscriber server can be removed from the environment. To Remove the Subscriber Server and Add the Replacement Subscriber Server to the Connection Cluster Step 1 If the replacement subscriber server will have the same host name or IP address as the subscriber server that you removed, skip the remaining steps in this procedure and skip to the next procedure. If the replacement subscriber server will have a different host name or IP address, log on to Cisco Unity Connection Administration on the publisher server. Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster. Step 3 On the Find and List Servers page, click Find to display all servers in the cluster. Step 4 Check the check box in front of the subscriber server and click Delete Selected. Step 5 When prompted to confirm deleting the server, click OK. Step 6 Click Add New. Step 7 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the replacement server. Step 8 In the Description field, enter Server 2 or another description for the server. Step 9 Click Save. Step 10 Log off Cisco Unity Connection Administration. To Install the Replacement Subscriber Server Follow the instructions in "Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x system with a Connection Cluster Configured" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html. Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly. You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function. To Confirm That the Connection Cluster Is Configured with the Replacement Subscriber Server Step 1 Log on to the command-line interface (CLI) for the subscriber server. Step 2 Run the CLI command show cuc cluster status. To Manually Change the Subscriber Server to Primary Status Step 1 Log on to Cisco Unity Connection Serviceability. Step 2 On the Tools menu, click Cluster Management. Step 3 On the Cluster Management page, under Server Manager, locate the subscriber server. Step 4 If the subscriber server has Primary status, skip the remaining steps in this procedure and continue to the next procedure. If the subscriber server has Secondary status, in the Change Server Status column for the subscriber server, click Make Primary. Step 5 When prompted to confirm changing the server status, click OK. The Server Status column displays the changed status when the change is complete. Note The publisher server will automatically change to Secondary status. To Manually Change the Publisher Server from Secondary Status to Deactivated Status Step 1 Log on to the Real-Time Monitoring Tool (RTMT). Step 2 On the Cisco Unity Connection menu, click Port Monitor. The Port Monitor tool appears in the right pane. Step 3 In the Node field, click the publisher server. Step 4 In the right pane, click Start Polling. Step 5 Note whether any voice messaging ports are currently handling calls for the server. Step 6 Return to the Cluster Management page of Cisco Unity Connection Serviceability. Step 7 If no voice messaging ports are currently handling calls for the publisher server, skip to Step 8. If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster Management page, under Change Port Status, click Stop Taking Calls for the publisher server, then wait until RTMT shows that all ports for the publisher server are idle. Step 8 Under Server Manager, in the Change Server Status column for the publisher server, click Deactivate. Step 9 When prompted to confirm changing the server status, click OK. The Server Status column displays the changed server status when the change is complete. To Remove the Publisher Server from the Environment Step 1 Shut down the publisher server. On the Cluster Management page, the Server Status column shows the publisher server has Not Functioning status. Step 2 Disconnect the network cable from the publisher server. The publisher server can be removed from the environment. To Install the Replacement Publisher Server Follow the instructions in "Part 1: Installing and Configuring the Cisco Unity Connection Server" of the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html. Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly. The replacement publisher server must have the same host name as the publisher server that you removed. Otherwise, the Connection cluster will not be able to function. You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function. To Configure the Cluster on the Replacement Publisher Server Step 1 Log on to Cisco Unity Connection Administration on the publisher server. Step 2 In Cisco Unity Connection Administration, expand System Settings, then click Cluster. Step 3 On the Find and List Servers page, click Add New. Step 4 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the subscriber server. Step 5 In the Description field, enter Server 2 or another description for the server. Step 6 Click Save. Step 7 Log off Cisco Unity Connection Administration. To Connect the Subscriber Server to the New Connection Cluster Step 1 Log on to the command-line interface (CLI) for the subscriber server. Step 2 Run the CLI command utils cuc cluster renegotiate. Note When the CLI command completes, the publisher server automatically restarts. Step 3 Run the CLI command show cuc cluster status to confirm that the new Connection cluster has been configured correctly. When Neither the Publisher Nor the Subscriber Server Is Functioning Added May 2009 When neither the publisher nor the subscriber server in the Connection cluster is functioning, and you have a Disaster Recovery System backup from which you can restore the Connection data, you can replace both servers at the same time. During this process, the Connection cluster is not able to answer calls. You install the replacement publisher server and restore the backed-up Connection data by using Disaster Recovery System. Then you install the replacement subscriber server and force Connection to copy the data from the publisher server to the subscriber server. When the copying is complete, replication will resume between the two servers. When the replacement servers have Primary or Secondary status, they will handle calls. Note that you must order replacement Connection licenses that includes the MAC addresses of the replacement servers. For details, see the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html. Do the five procedures in this section in the order listed. To Install the Replacement Publisher Server Follow the instructions in "Part 1: Installing and Configuring the Cisco Unity Connection Server" of the "Task List for Installing a Cisco Unity Connection 7.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html. Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly. The publisher server must have the same IP address and host name as the server from which Disaster Recovery System backed up the data. Otherwise, Disaster Recovery System Disaster Recovery System will not restore the data. You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function. To Restore the Backed-up Data to the Replacement Publisher Server Step 1 Log on to Disaster Recovery System. Step 2 On the Restore menu, click Restore Wizard. Step 3 On the Step 1 Restore—Choose Backup Device page, in the Device Name field, click the name of the backup device from which you want to restore and click Next. Step 4 On the Step 2 Restore—Choose the Backup Tar File page, in Select Backup File field, click the backup file that you want to restore and click Next. Note The backup filename indicates the date and time that the system created the backup file. Step 5 In the Step 3 Restore—Select the Type of Restore page, under Special Features, check the check boxes for the features that you want to restore and click Next. Note Only the features that were backed up to the file that you chose will appear on the page. Step 6 In the Step 4 Restore—Final Warning for Restore page, in the Select the Server field, click the publisher server and click Restore. Caution The publisher server must have the same IP address and host name as the server from which Disaster Recovery System backed up the data. Otherwise, Disaster Recovery System Disaster Recovery System will not restore the data. Note During the restore process, do not perform any tasks with Connection Administration. Step 7 When the restore status indicates 100 percent, restart the publisher server. To Install the Replacement Subscriber Server Follow the instructions in "Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber Connection Server" in the "Task List for Installing a Cisco Unity Connection 7.x system with a Connection Cluster Configured" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html. Caution Both Connection servers must have the same software and ES versions installed. Otherwise, the Connection cluster may not function correctly. You must install a replacement license that includes the MAC address of the replacement subscriber server. Otherwise, the server will not function. To Copy the Data from the Publisher Server to the Subscriber Server Step 1 Log on to the command-line interface (CLI) for the subscriber server. Step 2 Run the CLI command utils cuc cluster overwritedb to force Connection to copy data from the publisher server to the subscriber server: Step 3 Run the CLI command show cuc cluster status to confirm that the new Connection cluster has been configured correctly on the subscriber server. Step 4 Log on to the CLI for the publisher server. Step 5 Run the CLI command show cuc cluster status to confirm that the new Connection cluster has been configured correctly on the publisher server. To Synchronize MWIs for Each Phone System Step 1 During off-peak hours, log on to either server in the Connection cluster. Step 2 In Connection Administration, expand Telephony Integrations, then click Phone System. Step 3 On the Search Phone Systems page, click the name of the first phone system. Step 4 On the Phone System Basics page, under Messaging Waiting Indicators, click Run. Step 5 Click Next. Step 6 Repeat Step 4 and Step 5 for the remaining phone systems.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.