Migration of Kaseya Server and the Database


I would like to migrate my current Kaseya application server and my database to a new server. What are the steps I need to take?


Although we have a detailed guide on how this can be achieved in our help file here, this article has been written to provide summarized points that you need to take for the migration.

  • This article assumes that you have migrated all of the KAV/KAM Classic installations to the new module prior to migrating.

NoteThe KAV/KAM Classic Module will not be installed in new installations of VSA 9.3 or higher.

  • This article assumes that you will use the same IP for the new server as the one being used by the old server or that you will point the current DNS address agents are using under "Agent > Check-in Control" to this new server's IP.
  • This article also assumes that the Kaseya application along with the database is on the same server.

If you are looking to migrate from the same server to two different servers (i.e different front end and different SQL server) then please follow instruction from this article in order to migrate the database - also the steps related to transfer of ManagedFiles and UserProfiles can be found in the list below.

If you are looking to migrate from the existing split set up to a new split set up servers, please follow our help file in detail.

On your OLD Server

1. Important, please make a note of collation of the ksubscribers database per the notes from this article.
2. Next, backup the ksubscribers database via 'System > Server Management > Configure > Backup Now button' and copy this completed backup to a backup folder. (Example: 'D:\KaseyaServerBackup').
3. Please stop all the Kaseya services on the OLD server

4. Copy 'C:\Kaseya\WebPages\ManagedFiles' and all sub-directories (Important: Excluding 'VSAHiddenFiles') to the same backup directory. (Example: 'D:\KaseyaServerBackup\ManagedFiles').

5. Copy 'C:\Kaseya\UserProfiles' and all sub-directories to the same backup directory. (Example: 'D:\KaseyaServerBackup\UserProfiles').

6. Copy 'C:\Kaseya\EndpointDownloads' and all sub-directories to the same backup directory. (Example: 'D:\KaseyaServerBackup\EndpointDownloads').

7. Copy 'C:\Kaseya\EndpointUploads' and all sub-directories to the same backup directory. (Example: 'D:\KaseyaServerBackup\EndpointUploads').

NoteAfter securing the important files, please proceed with the below steps.

On your NEW Server

1. Install SQL using the same collation as the ksubscribers database had on your OLD server.

2. Download the Kaseya installer - http://download.kaseya.com/KInstall.exe

3. Run through the installer to install Kaseya without any data. (Important: The same VSA version that your OLD server has should be installed on the NEW server).

4. Stop all the Kaseya services except for the 'Kaseya.ApplicationFirewall' or 'Kaseya Edge Services' and the 'Kaseya Web Exec'.
5. Copy 'UserProfiles' and all sub-directories from your backup directory. (Example: 'D:\KaseyaServerBackup\UserProfiles' to 'C:\Kaseya\UserProfiles').

6. Copy 'ManagedFiles' and all sub-directories (excluding 'VSAHiddenFiles') from your backup folder. (Example: 'D:\KaseyaServerBackup' to 'C:\Kaseya\WebPages\ManagedFiles').

7. Copy 'EndpointDownloads' and all sub-directories from your backup folder. (Example: 'D:\KaseyaServerBackup\EndpointDownloads' to 'C:\Kaseya\EndpointDownloads').

8. Copy 'EndpointUploads' and all sub-directories from your backup folder. (Example: 'D:\KaseyaServerBackup\EndpointUploads' to 'C:\Kaseya\EndpointUploads').

9. In SQL Management Studio, restore the database that you previously copied to the backup folder. Please make sure you choose to overwrite the existing database from options tab in restore window
10. In SQL Management Studio, locate a user with the name starting "KaseyaVSA" and map it to newly restored ksubscribers database:

11. Once complete, click the "Start menu > Programs > Kaseya > Reinstall Database Schema". 

12. Verify that schema runs and completes without any errors and check if you can log in. If you receive any schema errors or have any issues logging in please contact Kaseya Support immediately and select Service(s) Down for the "Issue Severity" after selecting the "Kaseya Support" form.
13. If you are able to log in, the next thing to do would be to check your agents' check-in address. Since your agents should be checking in with the other IP you had for the OLD server then this would need to be reviewed/updated if needed. Simply navigate to Agent > Configure Agents > Check-in Control and verify the Primary Secondary KServer for your agents here.
NoteSince this NEW server should now have the same IP address, agents should be online and checking in, if they are not, note that the DNS should be pointed to this NEW server IP address.
14. Lastly, please verify the correct permissions are set under directory path 'C:\Kaseya\WebPages' for the user IUSR:
Applies to: All VSA Versions.
Was this article helpful?
7 out of 7 found this helpful
Have more questions? Contact us