Migrating a CDP Server Installation to a Larger Server

{page-title}

{kb-cause}
Many Customers as time goes on may outgrow their CDP servers and need to upgrade to bigger and better servers. A common question we get is: "How do we migrate our entire CDP server installation and keep all of our data and configurations?" This step by step guide will address this question.


{kb-resolution}

The first step to his guide is to go ahead and make a fresh install of CDP Server on your new hardware. This install must be the same exact version as your previous install so if you are on version 4.0.0 on your production server you will need to either upgrade to the latest version prior to the migration or you will need to install version 4.0.0 on your new hardware. You will also need to use the same architecture as your previous installation, 32 bit to 32 bit, and 64bit to 64 bit.

The second step after the fresh installation is to ensure that you maintain the paths for all of your volumes or disk safes. For example if you previously installed all of your volumes on /backup it is best to mount your storage to the same location on the new server. This is not completely necessary because you can always import existing volumes and disk safes, but it will ease the transition, and save some additional configuration.

Using your favorite editor you will need to open the configuration.

For Linux:

{code}
[root@cdp ~]# vi /usr/sbin/r1soft/conf/server.properties

{code}
For Windows:


{code}
C:\Users\Administrator>notepad.exe "C:\Program Files\R1Soft CDP Server Enterprise\conf\server.properties"
{code}

Then find the following line.

{code}
close-all-disk-safes-on-start-up=false

{code}

Then change it to the following.

{code}
close-all-disk-safes-on-start-up=true

{code}

Afer you have made the change to the server.properties file you can go a head and start the CDP Server daemon/service. This will allow you to start the CDP server and import your existing volumes and disk safes with out the change to the configuration the CDP server may fail to start properly. After you have imported your data, you can resume your replication schedule with no changes to your agents.
Please do not forget to revert the change, or the next time your restart the daemon/service the disk safes will be closed upon startup.

{kb-related-articles}