How to migrate Veeam Service Provider Console to a new server

Scenario 1 - migrate only the database

1. Stop “VeeamManagementPortalSvc” service on the VSPC server.
2. Move the database to a new SQL server instance using one of the ways outlined here. Make sure the collation of the database matches the collation of the SQL server.
3. Start “VeeamManagementPortalSvc” service on the VSPC server.
4. Access Veeam Service Provider Console Web UI, navigate to Configuration > Settings > SQL Server Connection, specify the new SQL server and database name and click Save.

1. Install a new instance of Veeam Service Provider Console on a new server using a temporary new SQL database and upgrade it to the same patch level the old installation had.
2. Stop “VeeamManagementPortalSvc” service on the old server.
3. Access Veeam Service Provider Console Web UI on the new server, navigate to Configuration > Settings > SQL Server Connection, specify the SQL server and database name used in the previous installation and click Save.
4. Since various credentials are encrypted on the VSPC server with a machine key, after migration you need to update:
   • Connection and Service accounts for Veeam Cloud Connect
   • SMTP credentials 1, 2
   • Access accounts in Discovery rules 1, 2, 3. The same applies to rules configured under Reseller.
   • Credentials to access VBR repositories or Shared folders in Backup Policies under all users who configured them – SP, Resellers, Company Owners
   • Credentials for Application-Aware Processing in Backup Policies under all users who configured them – SP, Resellers, Company Owners
   • Account used in the VSPC to search of users in Active Directory under Configuration->Roles and Users->User or group->Advanced
5. If you had ConnectWise Manage integration configured, it is advised to migrate the CWM database along with the VSPC server application. Otherwise you will need to reconfigure the plugin:
   • On the old VSPC server stop “VeeamConnectWiseManagePlugin” service
   • Copy VeeamConnectorDb.edb located in “C:\ProgramData\Veeam\Veeam Availability Console\Plugins\ConnectWiseManage\Database” to the new server
   • On the new VSPC server stop “VeeamConnectWiseManagePlugin” service and replace the VeeamConnectorDb.edb file
   • On the new VSPC server start “VeeamConnectWiseManagePlugin” service
   • Renew ConnectWise Manage keys 1, 2

Scenario 3 - migrate both the database and the server

1. Stop “VeeamManagementPortalSvc” service on the old VSPC server.
2. Move the database to a new SQL server instance using one of the ways outlined here. Make sure the collation of the database matches the collation of the SQL server.
3. Install a new instance of Veeam Service Provider Console on the new server server using a temporary new SQL database and upgrade it to the same patch level the old installation had.
4. Access Veeam Service Provider Console Web UI on the new server, navigate to Configuration > Settings > SQL Server Connection, specify the new SQL server and database name and click Save.
5. Update credentials and migrate CWM database as specified in Scenario 2

• public role (default permissions)
• dbcreator role (needed to create the Veeam Availability Console database during the Veeam Availability Console installation procedure)
• db_owner and public roles on the Veeam Availability Console database
• public permissions on the master database
• public permissions on the msdb database
• [For Always-On Availability Groups] VIEW SERVER STATE, VIEW ANY DEFINITION permissions