Upgrading Call Manager 3.1.4b to CM 3.3.2

[Wavesg]

I'm trying to upgrade our CM version from 3.1.4b to CM version 3.3.2. I was told by cisco that I should backup the current 3.1.4b using sitback 3.5.44. I saved that backup on the different drive so I can restore it in a newly built server with Call Manager 3.3.2.

It just doesn't work. When restore the 3.3.2 server with the 3.1.4b backup, after the reboot none of the service will start including Call Manager, cisco layer database monitor and RIS.

Can anyone help? Has anyone been able to upgrade from 3.1.4b to 3.3.2?

Stay cool; it’s not over yet!

 

[AdmanOK]

You have restore the STI backup as part of the install routine. There is an option that says "same server restore" that sets a flag during installation to prompt for a STI to pull in. It also performs some transformations on the data it is importing to convert it from 3.1 format to 3.3 format (and SQL 7.0 to SQL 2000). I also found that it is a good idea to disable CDR and purge your database before performing the backup on the old system. When I didn't do this the restore failed.

 

[Wavesg]

Thanks for the information. Now the installation CD I have installs stibackup 3.5.6. Do I need to skip the installation from the cd and install 3.5.44, which is supported in the matrix?

Stay cool; it’s not over yet!

 

[AdmanOK]

Having 3.5.6 installed on the 3.3 machine won't cause any problems... you just have to have AT LEAST 3.5.44 installed on your old CallManagers for the backup file to be compatible with the new version.

 

[Wavesg]

When I do installation of the new version 3.3.2, it installs sitbackup 3.5.6. Should I upgrade that to 3.5.44 prior to doing the restore from 3.1.4b? I have done a backup of the old system (3.1.4b) using the sitbackup 3.5.44

Stay cool; it’s not over yet!

 

[AdmanOK]

I just realized that there is no 3.5.6 - it went from 3.5.53 to the 4.0 version... I have CCM 3.3(3) disks and they install the 3.5.44 version of BART.