h3. Question
How do I migrate my entire CDP Server installation and keep all of the data and configurations?
h3. Answer
This step by step guide will address this question.
----
h5. Step 1
Install CDP Server on your new hardware.
{note:title=Be Careful}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 is migrated to 32-bit, and 64-bit to 64-bit.{note}
----
h5. Step 2
Confirm that the newly installed CDP Server maintains the same paths for all of your volumes and 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.
{info:title=Additional Info}As an alternative to maintaining the same paths, you can import existing volumes and Disk Safes into your new CDP Server installation. Please, keep in mind that this alternative requires some additional configuration. See "Importing Data" below.
{info}
----
h5. Step 3
Stop all Disk Safes on the production instance and then copy them (or volumes) to your new installation in their entirety.
{note:title=Be Careful}Please, note that failure to copy all files and folders for each disk safe will result in a non-functioning disk safe.{note}
{info:title=Additional Info}rsync and Robocopy are useful for copying Disk Safes and Volumes.{info}
----
h5. Step 4
Shut down the CDP Server {{daemon/service}} on both the original and new server. Then copy and overwrite either {{/usr/sbin/r1soft}} or {{C:\Program Files\R1soft CDP Server Enterprise\}} (Windows Installations) from the original server to the new server in the same location. As long as your disk safes are in the original paths upon starting the new CDP server daemon/service, all your settings and data will have been migrated.
h6. Importing Data
If you were unable to maintain the paths for your volumes on the new server (Step 2), you will need to make a change to the {{./conf/server.properties}} file.
Using your favorite text editor, open the configuration file.
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}
{panel}* After you have made the change to the {{server.properties}} file, you can start the CDP Server {{daemon/service}}. This will allow you to start the CDP server and import your existing volumes and disk safes. Without this 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.{panel}
{note:title=Be Careful}Please, do not forget to revert the change made to the configuration file, or the next time the {{daemon/service}} is restarted the disk safes will be closed on startup.{note}
See also:
* [CDP:Migrating Enterprise Edition]
{kb-related-articles}
How do I migrate my entire CDP Server installation and keep all of the data and configurations?
h3. Answer
This step by step guide will address this question.
----
h5. Step 1
Install CDP Server on your new hardware.
{note:title=Be Careful}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 is migrated to 32-bit, and 64-bit to 64-bit.{note}
----
h5. Step 2
Confirm that the newly installed CDP Server maintains the same paths for all of your volumes and 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.
{info:title=Additional Info}As an alternative to maintaining the same paths, you can import existing volumes and Disk Safes into your new CDP Server installation. Please, keep in mind that this alternative requires some additional configuration. See "Importing Data" below.
{info}
----
h5. Step 3
Stop all Disk Safes on the production instance and then copy them (or volumes) to your new installation in their entirety.
{note:title=Be Careful}Please, note that failure to copy all files and folders for each disk safe will result in a non-functioning disk safe.{note}
{info:title=Additional Info}rsync and Robocopy are useful for copying Disk Safes and Volumes.{info}
----
h5. Step 4
Shut down the CDP Server {{daemon/service}} on both the original and new server. Then copy and overwrite either {{/usr/sbin/r1soft}} or {{C:\Program Files\R1soft CDP Server Enterprise\}} (Windows Installations) from the original server to the new server in the same location. As long as your disk safes are in the original paths upon starting the new CDP server daemon/service, all your settings and data will have been migrated.
h6. Importing Data
If you were unable to maintain the paths for your volumes on the new server (Step 2), you will need to make a change to the {{./conf/server.properties}} file.
Using your favorite text editor, open the configuration file.
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}
{panel}* After you have made the change to the {{server.properties}} file, you can start the CDP Server {{daemon/service}}. This will allow you to start the CDP server and import your existing volumes and disk safes. Without this 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.{panel}
{note:title=Be Careful}Please, do not forget to revert the change made to the configuration file, or the next time the {{daemon/service}} is restarted the disk safes will be closed on startup.{note}
See also:
* [CDP:Migrating Enterprise Edition]
{kb-related-articles}