If you need to move/migrate the DS-Client deployment to a new server you can use the following process to ensure you maintain your original job configuration, logs and backup data.


Solution


MIGRATE DS-CLIENT TO NEW SERVER

On the original/current DS-Client Server

  • Go to Setup | System Activities, click the ‘Run Now’ button for daily admin to ensure latest DB is backed up to the cloud.
  • Once the daily admin process has successfully completed go to Services and Stop & Disable the DS-Client service.


On the new DS-Client Server

  • Download the latest DS-Client setup from the NOC portal.
  • Download the associated customer CRI file from the NOC portal.
    Note. You will need the customers encryption keys to re-install the DS-Client, if you do not have these please contact support and we can confirm if you have forwarded a secure copy to the cloud platform and supply you with a special CRI file containing the keys.
  • Run DS-Client setup, when deploying a new SQL instance for the new client please ensure you use the same Instance name as the previous installation.
  • Once the installation has completed and the DS-Client and DS-User have started you will be prompted for your Customer Registration Information, use the downloaded CRI and ensure that the same encryption settings and keys are used, at the end of the installation ensure that the DS-Client service and DS-User GUI start as expected.
  • Go to Setup | Configuration | Connections and click the 'Test Connection' button, this will force the DS-Client to connect to the Cloud and check if any updates are available (if an update is available you will see a failure message stating the test failed due to an auto update process).
  • Wait for the auto update process to complete, this can take up to 10 minutes.The DS-User will report it has lost connectivity once the upgrade is complete.
  • Re-start the DS-User you may be prompted update the DS-User (if this fails most likely down to UAC and permissions. Copy the file app_dsu_xx.x_x_x_inst.win32.exe  from the C:\Program Files\CloudBackup\DS-Client\app_upgrade_cache to C:\Temp and rename with a .exe extension. Run the file with the following syntax app_dsu_xx.x_x_x_inst.win32.exe "C:\Program Files\CloudBackup\DS-Client" this will update the DS-User and start it). You should now see a new (blank) DS-User environment and have the backup wizard pop-up, cancel the backup wizard.
  • Go to Setup | System Activities, click on the Repair DS-Client Databases button and select DS-Client & delta databases, this will download the databases and then state that you will be required to manually restart the service to complete the restore.
  • Close the DS-User and from services stop the DS-Client service.
  • ***IMPORTANT*** For the restore process to work the SQL Database and Log paths MUST match the previously installed DS-Client/SQL Instance, later versions of the DS-Client now use Microsoft SQL Express 2012 (not 2008 as previous versions did) so the path will have changed!
    • Create a directory junction using the MKLINK command
      mklink /J "C:\Program Files(x86)\Microsoft SQL Server\xxOLDPATHxx" "C:\Program Files(x86)\Microsoft SQL Server\xxNEWPATHxx"
    • Using SQL Management Studio detach each Asigra DB (dsclient, dsdelta, dslanfiles) and reattach using the directory junction you created, confirm the database and log file paths now match the original SQL setup.
  • Start the DS-Client service. Wait for up to 5 minutes to allow SQL to restore the databases. You can also use the Event Viewer and watch the Application log to confirm the successful auto recovery of the databases
  • Start the DS-User and you should now see all of your backup sets, schedules, retention rules and logs exactly as they were from the old DS-Client server.


On the original/current DS-Client Server

  • After testing that the new DS-Client is performing as expected uninstall the DS-Client from the original server, you should also uninstall the DS-Client SQL instance where applicable.


If you experience issues this can be caused by the automated SQL restore process failing. Check the windows 'Application' event logs to confirm if a restore failure occurred. If this is the case please raise a ticket for support.