|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (27)
View Page History{page-title}
h3. How do I migrate my entire CDP Server installation and keep all of the data and configurations?
{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.
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.
This step by step guide will address this question.
{kb-resolution}
The first step to this 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.
{panel}h5. +Step 1+
The second step after the fresh installation is to ensure that you maintain the 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. 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.
Install CDP Server on your new hardware.{panel}
The third step is to stop all of the disk safes on the production instance and copy the disk safes or volumes to your new installation in their entirety. You can use any method that you are comfortable with, however we find that rsync and robocopy work very well in this situation. Please note that failure to copy all files and folders for each disk safe will result in a non-functioning disk safe.
The last step is to 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\" 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.
If you find yourself in a situation where you could not maintain the paths for your volumes on the new server you will need to make a change to the "./conf/server.properties" file.
(!) Be Careful
bq. 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.
bq. 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.
{panel}h5. +Step 2+
Using your favorite text editor you will need to open the configuration file.
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.{panel}
(i) Additional Info
bq. 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.
bq. 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.
{panel}h5. +Step 3+
Stop all Disk Safes on the production instance and then copy them (or volumes) to your new installation in their entirety.{panel}
(!) Be Careful
bq. Please note that failure to copy all files and folders for each disk safe will result in a non-functioning disk safe.
(i) Additional Info
bq. rsync and Robocopy are useful for copying Disk Safes and Volumes.
{panel}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.{panel}
(/) Importing Data
bq. 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.
Stop all Disk Safes on the production instance and then copy them (or volumes) to your new installation in their entirety.{panel}
(!) Be Careful
bq. Please note that failure to copy all files and folders for each disk safe will result in a non-functioning disk safe.
(i) Additional Info
bq. rsync and Robocopy are useful for copying Disk Safes and Volumes.
{panel}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.{panel}
(/) Importing Data
bq. 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}
[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"
C:\Users\Administrator>notepad.exe "C:\Program Files\R1Soft CDP Server Enterprise\conf\server.properties"
...
{code} {code}
Then change it to the following.
{code}
close-all-disk-safes-on-start-up=true
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.
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.
* After you have imported your data, you can resume your replication schedule with no changes to your agents.{panel}
(!) Be Careful
bq. 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.
bq. 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.
{kb-related-articles}