Migrating a Physical Server to a Virtual Machine
Follow the given tasks to migrate from physical server to a virtual machine:
-
Backup the software component on the physical server. For more information, see the Backing Up and Restoring Cisco Unity Connection Components chapter.
-
Download and deploy the OVA template to create a new virtual machine. For more information, see the Creating a Virtual Machine section.
-
Migrating the Unity Connection server on the virtual machine.
-
To replace the publisher server, see the Replacing a Publisher Server section.
-
To replace the subscriber server, see the Replacing a Subscriber Server section.
-
-
If Unity Connection is installed as a standalone server, restore the software component from the physical server to the virtual machine for which you have taken the back up. For more information, see the Restoring the Software Components on Unity Connection section.
-
(Optional) Install new languages on the replaced server if required or remove the existing languages already installed on the server. For more information, see the Adding or Removing Unity Connection Languages section.
Note |
If you are deploying Unity Connection networking (Intersite, Intrasite, or HTTPS), see the Networking Guide for Cisco Unity Connection Release 11.x, before replacing the Unity Connection server, available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/networking/guide/b_11xcucnetx.html . |
Replacing a Publisher Server
While you are upgrading the publisher server in a Unity Connection cluster, the subscriber server continues to provide services to the users and callers.
Note |
In case of a standalone server, replace the server during off-peak hours to avoid call-processing interruptions and impact to services. |
Procedure
Step 1 |
Manually change the status of subscriber server to Primary: |
||
Step 2 |
Manually change the status of publisher server to Deactivated: |
||
Step 3 |
Install the replacement publisher server, see Installing the Publisher Server section. |
||
Step 4 |
Configure the cluster on the replaced publisher server:
|
||
Step 5 |
If Unity Connection is installed as a cluster, you can restore the publisher using the subscriber data.
|
Replacing a Subscriber Server
While you are upgrading the subscriber server in a Unity Connection cluster, the publisher server continues to provide services to users and callers.
Procedure
Step 1 |
Manually change the status of publisher server to Primary: |
||
Step 2 |
Manually change the status of subscriber server to Deactivated: |
||
Step 3 |
Make sure that the hostname or IP address of the subscriber server is configured correctly on the publisher server as mentioned in 4 of replacing a publisher server. |
||
Step 4 |
Install the replaced subscriber server, see Installing the Publisher Server section.
|
||
Step 5 |
Check the cluster status by running the show cuc cluster status CLI command on the subscriber server.
|