Cisco Collaboration CMS CUCM CUC Expressway Migration

Migrate Cisco Meeting Server

• Check the database status on all servers using the database cluster status command.
• Take a backup on all servers using the backup snapshot <backup_filename> command.
• Disconnect the slaves CMS2 and CMS3 and the callbridge node CMS4 from the old primary using the database cluster remove command.
• Disconnect the Primary database server CMS1 using the database cluster remove command.
• Check again the database status to confirm (On the old primary).
• Shutdown CMS1, CMS2, CMS3 and CMS4.
• Remove all CMS on Cisco Meeting Management.
• Deploy a new VM with the same network settings as the primary CMS1. Copy the backup file using SFTP.  Restore the backup using the backup rollback <backup_filename> command. The server reboot automatically.
• Deploy a new VM with the same network settings as the slave CMS2, CMS3 and CMS4. Copy the backup file using SFTP.  Restore the backup using the backup rollback <backup_filename>.
• Reboot CMS1, CMS2, CMS3 and CMS4. After reboot.
• Cluster the database, run the database cluster initialize command on the Primary server CMS1.
• Join all slaves CMS2 and CMS3 to the primary CMS1 using the database cluster join <Database_primary_IP address> command.
• Connect CallBridge node CMS4 to the primary using the database cluster connect <Database_primary_IPaddress> command.
• Verify the database status on all node using the database cluster status command.
• Add all CMS to Cisco Meeting Management.

Migrate Cisco Unified Communication Manager

• Check the database replication on the old publisher using the Run the utils dbreplication runtimestate.
• Backup the DRS on the old publisher, including the subscribers CUCM and IMP, shutdown the three nodes.
• Install a new publisher with the same network settings and security password.
• Add the new subscriber and IMP to the new publisher Under System > Server. For IMP (uncheck the High Availability box).
• Install the new Subscriber CUCM and IMP with same network settings.
• From the new Publisher node, restore the DRS Backup of the publisher and subscribers including IMP Nodes.
• Reboot the new publisher first and then subscribers.
• Check the database replication on the new publisher using the utils dbreplication runtimestate.

Migrate Cisco Expressway

• Go to Maintenance > Backup and restore (Web GUI) on old Expressway and create the system backup file.
• Install new Expressway with (same version as the old Expressway).
• Install required release key and option key(s) on new Expressway installed in step 2.
• Go to Maintenance > Backup and restore (Web GUI) on new Expressway and upload system backup file that you generated in step 1.

Replace Cisco Unity Connection Publisher

• On old publisher go to Cisco Unity Connection Serviceability. Under the Cluster Management. Locate the subscriber server and change the server status to Primary.
• Shutdown the old publisher using the utils system shutdown command. On the Cluster Management page of the subscriber server, the publisher should display the Not Functioning status.
• Install a new publisher with the same network settings and security password.
• On new publisher, navigate to Cisco Unity Connection Administration. Under System Settings, select Cluster. Add the IP address of the current subscriber server.
• Restore the publisher using the subscriber data. On the current subscriber run the utils cuc cluster renegotiate command. The publisher automatically restarts.
• Check the database replication on the new publisher using the Run the utils dbreplication runtimestate.