Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
Separating Cisco Unity 5.x and Exchange
Downloads: This chapterpdf (PDF - 119.0KB) The complete bookPDF (PDF - 6.98MB) | Feedback

Separating Cisco Unity 5.x and Exchange

Table Of Contents

Separating Cisco Unity 5.x and Exchange

Moving Cisco Unity 5.x onto a Separate Server

Converting from Two-Server to Three-Server Failover


Separating Cisco Unity 5.x and Exchange


This chapter contains the following sections:

Moving Cisco Unity 5.x onto a Separate Server

Converting from Two-Server to Three-Server Failover

Moving Cisco Unity 5.x onto a Separate Server

For a Cisco Unity 5.x system that has Exchange on the Cisco Unity server, this section explains how to get Cisco Unity and Exchange onto separate servers by removing Cisco Unity from the current server and installing it on a separate server.

Some customers have successfully removed Exchange from the current server instead of removing Cisco Unity. However, removing Cisco Unity from the server has, on average, been more successful.

For information on adding Cisco Unity failover after you have separated Cisco Unity and Exchange, see the "Adding Failover to the Cisco Unity System When Exchange Is Already on a Separate Server" section on page 2-51.

To Move Cisco Unity 5.x onto a Separate Server


Step 1 Confirm that you have discs for the currently installed version of Cisco Unity.


Caution This procedure requires that you back up Cisco Unity data, uninstall and reinstall Cisco Unity, and restore Cisco Unity data. You must restore data to the exact version of Cisco Unity that you backed up.

Step 2 Download and install the latest versions of the following three applications from http://ciscounitytools.com:

Cisco Unity Directory Walker (DbWalker) utility. DbWalker is used to check the consistency of and correct errors in the Cisco Unity database.

Cisco Unity Disaster Recovery tools (DiRT). DiRT is used to back up and restore Cisco Unity data.

Uninstall Cisco Unity utility.

Step 3 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)

Step 4 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)


Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.

Step 5 Uninstall Cisco Unity by using the Uninstall utility. This is necessary to remove Cisco Unity data from Active Directory. Refer to Uninstall Cisco Unity Help for detailed instructions.

Step 6 Set up a new Cisco Unity server and install all software by following the instructions in the applicable Cisco Unity installation guide for your configuration at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.


Caution Reinstall the exact version of Cisco Unity that was installed when you backed up Cisco Unity data earlier in the procedure. DiRT can restore data only to the exact version of Cisco Unity that you backed up.

Step 7 Restore Cisco Unity data by using the Disaster Recovery Restore tool and the backup that you made earlier. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryRestore.exe.)


Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully.

Step 8 Reapply any non-Cisco Unity custom registry settings. (DiRT backs up and restores Cisco Unity registry settings.)


Converting from Two-Server to Three-Server Failover

Revised May 1, 2008

For a Cisco Unity 5.x failover system that has Exchange on the Cisco Unity secondary server, this section explains how to get Cisco Unity and Exchange onto separate servers by removing Cisco Unity from the current server and installing it on a separate server.

Some customers have successfully removed Exchange from the current server instead of removing Cisco Unity. However, removing Cisco Unity from the server has, on average, been more successful.

For information on reconfiguring Cisco Unity failover after you have separated Cisco Unity and Exchange, see the "Adding Failover to the Cisco Unity System When Exchange Is Already on a Separate Server" section on page 2-51.

The following items are required to remove Cisco Unity from the secondary server and install it on a separate server:

The latest version of the following applications from the CiscoUnityTools.com website, http://ciscounitytools.com/App_DirectoryWalker4.htm:

Cisco Unity Directory Walker (DbWalker) utility.

Cisco Unity Disaster Recovery tools (DiRT). DiRT is used to back up and restore Cisco Unity data.

Uninstall Cisco Unity utility.

Software for reinstalling all software on the new secondary server.


Caution You must install on the new secondary server the same version of Cisco Unity that is installed on the primary server.

The applicable Cisco Unity installation guide for your configuration, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

To Remove Any SQL Errors and Stop SQL Replication on the Primary Server


Step 1 On the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager.

Step 2 In the left pane of the Console Root window, browse to the Replication node for the primary server. Typically, the node is three levels under the Microsoft SQL Servers node.

Step 3 Right-click the Replication node, and click Configure Publishing, Subscribers, and Distribution. The Configure Publishing and Distribution wizard appears.

Step 4 On the Welcome page, click Next.

Step 5 On the Select Distributor page, click Next.

Step 6 On the Specify Snapshot Folder page, click Next.

Step 7 In the SQL Server Enterprise Manager dialog box, click Yes.

Step 8 On the Customize the Configuration page, click Next.

Step 9 On the Completing page, click Finish.

Step 10 In the SQL Server Enterprise Manager dialog box, click OK.

Step 11 In the SQL Server Enterprise Manager dialog box, click Close.

Step 12 In the left pane of the Console Root window, right-click the Replication node, and click Disable Publishing. The Disable Publishing and Distribution wizard appears.

Step 13 On the Welcome page, click Next.

Step 14 On the Disable Publishing page, click Yes, then click Next.

Step 15 On the Confirm Dropping of Publications page, click Next.

Step 16 On the Completing page, click Finish.

Step 17 When the process is completed, click OK.

Step 18 Close the Console Root window.

Step 19 Exit Enterprise Manager.


To Check the Consistency of the Cisco Unity Database and Back Up Data on the Secondary Server


Step 1 On the secondary server, install the latest version of DbWalker and DiRT, if they are not already installed.

Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)

Step 3 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)


Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.

Caution Do not back up the primary server unless the secondary server is unavailable. If you restore from a backup of the primary server, you must also perform an additional procedure for Cisco Unity failover to function correctly. For more information, see "Working With Systems Configured For Failover" in DiRT Help.

To Uninstall Cisco Unity on the Secondary Server


Step 1 On the secondary server, log on to Windows as a Cisco Unity administrator.

Step 2 Right-click the Cisco Unity icon in the status area of the taskbar.

(If the Cisco Unity icon is not in the taskbar, browse to the CommServer directory and double-click AvCsTrayStatus.exe.)

Step 3 Click Stop Cisco Unity.

Step 4 Click OK to confirm that you want to stop the Cisco Unity software. Cisco Unity stops running when all calls are finished, and an "X" appears in the Cisco Unity icon.

Step 5 Right-click the SQL Server icon in the status area of the taskbar.

Step 6 Click MSSQLServer - Stop.

Step 7 On the secondary server, install the latest version of the Uninstall Cisco Unity utility, if it is not already installed.

Step 8 Uninstall Cisco Unity on the secondary server by using the Uninstall utility. Refer to Uninstall Cisco Unity Help for detailed instructions.


Caution Do not choose the option to remove Cisco Unity data from Active Directory.


To Install Cisco Unity 5.x on the New Secondary Server


Step 1 Follow the instructions in the applicable Cisco Unity installation guide for your configuration to install the new secondary server. Refer to Part 2 in the "Overview of Mandatory Tasks for Installing Cisco Unity" chapter.


Caution Install the same version of Cisco Unity that is installed on the primary server, or failover may not function properly.

Step 2 Reapply any non-Cisco Unity custom registry settings.


To Configure Failover on the Primary Server


Step 1 In Windows Explorer, browse to the CommServer directory.

Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.

Step 3 On the Welcome page, click Next.

Step 4 On the Specify Server Role page, click Primary Server, and click Next.

Step 5 On the Enter the Name of Your Server page, click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.

Step 6 Click Next.

Step 7 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.

The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.


Caution You must specify the same account on both the primary and secondary servers.

Step 8 In the Password field, enter the password for the account that the failover service will log on as, and click Next.

Step 9 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the primary server.

If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.

Step 10 On the Completing page, click Finish.


To Configure Failover on the Secondary Server


Step 1 On the Windows taskbar, double-click the system clock. The Date/Time Properties dialog box appears.

Step 2 Set the time to the same hour and minute as shown on the primary server, and click OK.

Step 3 In Windows Explorer, browse to the CommServer directory.

Step 4 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.

Step 5 On the Welcome page, click Next.

Step 6 On the Specify Server Role page, click Secondary Server, and click Next.

Step 7 On the Enter the Name of Your Server page, click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.

Step 8 Click Next.

Step 9 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.

The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.


Caution You must specify the same account on both the primary and secondary servers.

Step 10 In the Password field, enter the password for the account that the failover service will log on as, and click Next.

Step 11 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the secondary server.

If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.

Step 12 On the Completing page, click Finish.