CUCM 10.5 to 15 Migration with Data Import

[mumbles202]

Trying to migrate an existing 10.5 installation w/ a Pub/Sub to a new 15 cluster.  I had planned to use PCD, but I need to re-use the existing ip addresses but also keep the outage window as small as possible.  I don't recall how long the outage window would be with PCD if I did a migration re-using the same ip addresses (I know there is a pause and I can resume when time to cutover, but don't recall if the new cluster actually gets bulk ahead of that or after).  

I was thinking Fresh Install w/ Data Import would allow me to stand-up  the new cluster with a set of temp ips, then the day of the cutover just disconnect the nics on the 10.5 servers and re-ip the 15.x cluster?  If I go this route, I need to install the following cop files on both the pub and sub in the 10.5 cluster right:

ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn

ciscocm.DataExport_v4.0.cop.sha512

[mumbles202]

Based off of reading this:

BRKCOL-2076 (ciscolive.com)

PCD with Data Import seems to be the recommendation.  I'd have to run the pre-readiness check, install the cop files on each node in the cluster, and then do an export on each node?  Then use the export from each node to build out the new cluster members (so pub would import old pub export, sub old sub export)?  

Unity Connection I'm using Cobras so think I'm covered there.

[Nithin Eluvathingal]

PCD and a fresh install with data import are two different processes. I have never heard of PCD with data import. PCD automates migrations with minimal intervention. With a fresh install and data export, you need to install the COP, export the data to an SFTP, perform a fresh install, and import the data manually. ( you can automate the last two process by using AFG )

According to a discussion with the PM of PCD, it is in survival mode, and Cisco recommends using the native option, which is the fresh install with data export.

I have done migrations with PCD, and it’s very easy.

Since you are using the same IP address, the outage is minimal when using PCD. With only a Publisher (Pub) and Subscriber (Sub), PCD will first shut down the old Publisher and install the new one with the same IP address. By the time the installation is complete, all configuration data will be available on the Publisher. Then it will shut down the Subscriber and do the same for the Sub. During this process, the phones will switch over to Pub/Sub based on how redundancy is configured.

Once the installation is completed, the user-facing feature configuration will be imported. You can expect minimal outage. However, the least outage would be achieved by installing fresh from the data exported in an isolated setup and during maintenance, just swapping the network cables to the new setup.

Both methods seem fine to me, but PCD is my preference.

If your Unity Connection is on version 11.5, you can perform a fresh install with data export, similar to CUCM, without needing to use Cobra. You might consider upgrading Unity to 11.5 first, then using data export. This is the method I use with Unity Connection.

[mumbles202]

Thanks for the response.  Yes, I meant to either use PCD migration or do a fresh install with data import as 2 separate approaches.  I've used PCD in the past to do the migrations and it's gone pretty smoothly, just wasn't remembering the process in terms of when the new Publisher gets built (if it gets built during the first part of the migration task but just offline until the resume is performed).  I'll have a few hours in terms of an outage window, but I was thinking about possibly getting the machines built out ahead of time to minimize the maintenance window if possible. I'll see if there is a way for me to get a fresh install going into an isolated environment and still get everything to work as expected during the installation network checks.

Unity is 10.5.  I already took a Cobras export, did the manual configuration required on the 15.x box and imported the configuration into Unity.  I figure during the cutover window I'll use the Shuttle to move messages and populate user inboxes.