Upgrade Guide for Cisco Unity Connection Release 9.x
Migrating from a Cisco Unity Connection Standalone Physical Server to a Connection 9.x Virtual Machine
Downloads: This chapterpdf (PDF - 102.0KB) The complete bookPDF (PDF - 1.5MB) | Feedback

Table of Contents

Migrating from a Cisco Unity Connection Physical Servers to a Unity Connection 9.x Virtual Machine

Task List for Migrating from a Unity Connection Standalone Physical Server to a Unity Connection 9.x Virtual Machine

Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster, page 10-8

Changing the Boot Order of the Unity Connection 9.x Virtual Machine

Task List for Migrating from a Unity Connection Standalone Physical Server to a Unity Connection 9.x Virtual Machine

Revised June 26, 2013

1. Review the section “Requirements for Installing Cisco Unity Connection 9.x on a Virtual Machine” in System Requirements for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html .

2. In the Cisco Unity Connection 9.x Supported Platforms List , in the table of virtualization specifications, determine which VMware configuration you want to deploy on the Unity Connection server, based on the maximum number of ports and the maximum number of users. Then make note of the VMware OVA template that corresponds with that configuration. The document is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html .

3. Optional: Download the VMware OVA template that you identified in Task 2. See the “Installing Cisco Unity Connection for the First Time on a Virtual Machine” section in the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

You can also manually configure a virtual machine; if you prefer that option, you do not need the OVA template.


Note Information on downloading a VMware OVA template appears in the Release Notes for Cisco Unity Connection for versions 9.x and later.


4. If the Unity Connection physical server is running version 7.1(3), or version 8.0(2) or later: Skip to Task 5.

If the Unity Connection physical server is running version 8.0(1): Upgrade to Unity Connection 9.x: See the “Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version” chapter of this guide.

If the Unity Connection physical server is running version 7.1(2) or earlier: Upgrade to Unity Connection 7.1(3). See the applicable chapter in the Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html . (You upgrade to version 9.x in a later task.)


Caution Running Unity Connection 7.1(3) in a virtual environment for any longer than is required for the migration is not supported.

5. Provision the physical host where the Unity Connection virtual machine will run, according to the “Requirements for Installing a Cisco Unity Connection 9.x Virtual Machine” section in System Requirements for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html .

6. If you downloaded the VMware OVA template in Task 3.: Deploy the template, which creates a virtual machine and configures it.

If you did not download the VMware OVA template in Task 3.: Create a virtual machine for the Unity Connection server, and configure the virtual machine hardware properties to match the settings in the “Requirements for Installing a Cisco Unity Connection 9.x Virtual Machine” section in System Requirements for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html .

7. If the physical server has more total available disk space than the virtual machine: Change the VMware virtual machine hardware configuration so the Unity Connection virtual machine has as much as or more total available disk space than the physical server.

Total available disk space is the amount of disk space usable by Unity Connection after accounting for the RAID configuration. (For example, two 146-GB hard disks configured as RAID 1 provide only 146 GB of total available disk space.)

8. In the VMware vSphere Client, configure the virtual disks that are assigned to the Unity Connection virtual machine in independent-persistent mode. This provides the best storage performance.

9. On the virtual machine, change the BIOS setting so the virtual machine boots first from the DVD virtual device, then from the virtual hard disk. See the “Changing the Boot Order of the Unity Connection 9.x Virtual Machine” section.

10. Back up the Unity Connection physical server by using the Disaster Recovery System. For more information, see the applicable Disaster Recovery System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

11. Shut down the Unity Connection physical server by using the CLI command utils system shutdown . For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

12. On the virtual machine, install the exact version of Unity Connection that is installed on the physical server, including engineering specials, if any. See the Installation Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html .

The following two installation settings must be the same on the Unity Connection virtual machine as on the Unity Connection physical server, or using the Disaster Recovery System to transfer data from the physical server to the virtual machine will fail:

  • Hostname of the server
  • IP address of the server

We recommend that you enter settings that are unlikely to change for the foreseeable future:

  • Time zone
  • NTP server
  • NIC speed and duplex settings
  • DHCP settings
  • Primary DNS settings
  • SMTP hostname
  • X.509 Certificate information (Organization, Unit, Location, State, and Country)

You must give the Unity Connection virtual machine the same hostname as the Unity Connection physical server so you can restore data. After you have restored data, you may change the hostname and/or IP address of the Unity Connection virtual machine.

13. Restore data on the Unity Connection virtual machine by using the backup that you made in Task 10.

14. Optional: Change the hostname of the Unity Connection virtual machine. See the “Renaming Cisco Unity Connection 9.x Servers” chapter of this guide.

15. If you installed Unity Connection 7.1(3) on the virtual machine: Upgrade to version 9.x or later. See the “Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version” chapter of this guide.

16. Post installation, if you have installed Unity Connection on a virtual machine with 1v CPU and upto 4 GB RAM, make sure to install the ciscocm.cuc_license_patch.sgn COP file. For more information on the specific Unity Connection version for which you need to install the COP file, see the Readme file available at the Download Software page. To download the cop file, sign in to a computer with a high-speed Internet connection, and go to the Voice and Unified Communications Downloads page at http://www.cisco.com/cisco/software/navigator.html?mdfid=280082558 .


Note To access the software download page, you must be signed in to Cisco.com as a registered user.


Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster, page 10-8

To replace the Publisher and Subscriber servers or the Hard Disk in both the servers in a cluster, see the following section Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster

Changing the Boot Order of the Unity Connection 9.x Virtual Machine

Do the procedure in this section to change the BIOS setting so the virtual machine boots first from the DVD virtual device, then from the virtual hard disk.

To Change the Boot Order of the Unity Connection 9.x Virtual Machine


Step 1 In VMware vSphere Client, power off the virtual machine on which you deployed the OVA template.

Step 2 In the left pane of vSphere Client, right-click the name of the virtual machine, and select Edit Settings .

Step 3 In the Virtual Machine Properties dialog box, select the Options tab.

Step 4 In the Settings column, under Advanced, select Boot Options .

Step 5 Under Force BIOS Setup, check the The Next Time the Virtual Machine Boots, Force Entry into the BIOS Setup Screen check box.

Step 6 Select OK to close the Virtual Machine Properties dialog box.

Step 7 Power on the virtual machine. The virtual machine boots into the BIOS menu.

Step 8 Navigate to the Boot menu, and change the boot device order so the CD-ROM device is listed first and the Hard Drive device is listed second.

Step 9 Save the change, and exit BIOS setup.