Calix CMS - Server Migration

CMS Migration

(This document is from Calix in response to a ticket in 2015)

There are two options for moving CMS from server to server. Option 1 is to install CMS on the new server and then do an export of the CMS objects on the old server and import these into the application on the new server. The drawback to this method is that the Subscriber Services page will not be synchronized on the new server. Also, any old log files, performance data, etc will not be present on the new server. The other option is to move the entire application and directory. The steps for doing this are outlined below.

Note: These steps are Linux specific but could be adapted for Solaris. They are also specific to the Postgres DB. If you are running Oracle as the DB, do not use this KB, instead, contact your Oracle admin for steps on migration.

Before beginning, shutdown the CMS application on the old server. the C7 networks should only attempt to connect to one CMS server at a time.

Locate the CMS install directory. The easiest way to do this is do a process list and look for the cms entry ps ax | grep cms | awk '{print $1,$2,$3,$4,$5}'
1. output -- "3923 ? Sl 0:00 /opt/cms11.0.129/java/bin/java"
2. From this output, we see the path to CMS is /opt/cms11.0.129
Make an archive (tar) of the CMS folder. This will backup the application and the database.
1. tar cvf cms.tar /opt/cms11.0.129
2. This could take a while depending on the amount of data in the database.
Check the userid/groupid of the cms user cat /etc/passwd | grep cmsuser output -- "cmsuser:501:501:CMS User:/opt/cms11.0.129:/bin/bash"
1. From this, we see the CMS user has a user id of 501 and a group id of 501. The same id's need to be used on the new server to ensure correct ownership of the cms application files.
On the new server, make a folder identical to the folder on the older server mkdir /opt/cms11.0.129
Create the cmsuser and cms group
1. groupadd -g 501 cmsuser
2. useradd -c "CMS User" -u 501 -g 501 -d /opt/cms11.0.129
Copy the archive file to the new server. We will use scp for this so we need the root username/password of the new server.
1. scp cms.tar root@10.1.1.50:/opt/cms11.0.129 In this example, the new server has an IP address of 10.1.1.50, rep
Also copy the CMS init script
1. scp /etc/init.d/cms root@10.1.1.50:/etc/init.d/cms
Now, extract the archive file
1. tar xvf /opt/cms11.0.129/cms.tar
Start CMS
1. cd /opt/cms11.0.129/bin
2. ./startup.sh (This might take 10-15 minutes, dont close the shell session until it completes)
Set CMS to start on boot (optional) chkconfig cms on

That's it. You should now be able to connect to the CMS application using the CMS GUI and all networks, subscriber data, pm logs, etc should be visible. Should anything be amiss, the old server still has the complete database and you can revert to this application if necessary