How to Migrate Veeam Service Provider Console to a New Server

KB ID: 2451
Product: Veeam Service Provider Console | 4.0 | 5.0 | 6.0
Published: 2018-02-27
Last Modified: 2022-08-19
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article documents different scenarios and methods of migrating the Veeam Service Provider Console software, its database, or both.

Solution

Scenario 1 - Migrate Only the Database

  1. Stop “VeeamManagementPortalSvc” service on the VSPC server.
  2. Copy the VSPC database to the new SQL server instance.
    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.

Scenario 2 - Migrate Only the Software

Starting with Veeam Service Provider Console v6, when moving the software, you must manually export the active “Veeam Service Provider Console Security Certificate” and import it on the new server. If this is not performed, agents will connect to the new VSPC server in the “Unverified” state and have to be verified manually.

Expand for Certificate Export/Import Guide

Retrieve Certificate Thumbprint

Run the following SQL query against the existing VSPC database to retrieve the thumbprint of the certificate used for communication with managed agents.

SELECT RootCertThumbprint FROM [VeeamBR].[ServerSettings]

Export Certificate

Use the following PowerShell commands to export the active Veeam Service Provider Console Security Certificate.

Note:

  • Run these commands in an Administrative PowerShell window or PowerShell ISE run as Administrator.
  • Replace {thumbprint} with the thumbprint value output by the SQL Query above.
  • Adjust the -FilePath setting to a valid location.
$mypwd = Get-Credential
Get-ChildItem -Path cert:\localMachine\my\{thumbprint} | Export-PfxCertificate -FilePath C:\temp\VSPCcert.pfx -Password $mypwd.Password

Import Certificate

Use the following PowerShell commands on the new VSPC server to import the Veeam Service Provider Console Security Certificate.

Note:

  • Run these commands in an Administrative PowerShell window or PowerShell ISE run as Administrator.
  • Check the -FilePath setting to ensure the correct pfx file is specified.
$mypwd = Get-Credential
Import-PfxCertificate -FilePath C:\temp\VSPCcert.pfx -CertStoreLocation Cert:\LocalMachine\My -Password $mypwd.Password
  1. Install Veeam Service Provider Console on a new server using a temporary new SQL database. The upgrade to the same patch level the old Veeam Service Provider Console installation was running.
  2. Stop the “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. The various credentials are encrypted on the VSPC server with a machine key. As such, after migration, you must manually update:
    • Connection and Service accounts for Veeam Cloud Connect
    • SMTP credentials here and here
    • Access accounts in Discovery rules here, here, and here. 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
    • The account used in the VSPC to search for 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 the “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 the “VeeamConnectWiseManagePlugin” service
    • Renew ConnectWise Manage keys here and here
  6. If the Veeam Service Provider Console installation was migrated to a new server with a different hostname than the one known to management agents installed on Veeam Cloud Connect servers, you will need to migrate these records in the Veeam Service Provider Console.
    1. Disconnect the Veeam Cloud Connect servers.
      In the Veeam Service Provider Console > Configuration > Cloud Connect > Select servers and click Remove and select Migrate from the drop-down menu.
    2. Re-add the Veeam Cloud Connect servers.

Scenario 3 - Migrate Both the Database and the Software

Starting with Veeam Service Provider Console v6, when moving the software, you must manually export the active “Veeam Service Provider Console Security Certificate” and import it on the new server. If this is not performed, agents will connect to the new VSPC server in the “Unverified” state and have to be verified manually.

Expand for Certificate Export/Import Guide

Retrieve Certificate Thumbprint

Run the following SQL query against the existing VSPC database to retrieve the thumbprint of the certificate used for communication with managed agents.

SELECT RootCertThumbprint FROM [VeeamBR].[ServerSettings]

Export Certificate

Use the following PowerShell commands to export the active Veeam Service Provider Console Security Certificate.

Note:

  • Run these commands in an Administrative PowerShell window or PowerShell ISE run as Administrator.
  • Replace {thumbprint} with the thumbprint value output by the SQL Query above.
  • Adjust the -FilePath setting to a valid location.
$mypwd = Get-Credential
Get-ChildItem -Path cert:\localMachine\my\{thumbprint} | Export-PfxCertificate -FilePath C:\temp\VSPCcert.pfx -Password $mypwd.Password

Import Certificate

Use the following PowerShell commands on the new VSPC server to import the Veeam Service Provider Console Security Certificate.

Note:

  • Run these commands in an Administrative PowerShell window or PowerShell ISE run as Administrator.
  • Check the -FilePath setting to ensure the correct pfx file is specified.
$mypwd = Get-Credential
Import-PfxCertificate -FilePath C:\temp\VSPCcert.pfx -CertStoreLocation Cert:\LocalMachine\My -Password $mypwd.Password
  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. The various credentials are encrypted on the VSPC server with a machine key. As such, after migration, you must manually update:
    • Connection and Service accounts for Veeam Cloud Connect
    • SMTP credentials here and here
    • Access accounts in Discovery rules herehere, and here. 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
    • The account used in the VSPC to search for users in Active Directory under Configuration->Roles and Users->User or group->Advanced
  6. 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 the “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 the “VeeamConnectWiseManagePlugin” service
    • Renew ConnectWise Manage keys here and here
  7. If the Veeam Service Provider Console installation was migrated to a server with a different hostname than the one known to management agents installed on Veeam Cloud Connect servers, you will need to migrate these records in the Veeam Service Provider Console.
    1. Disconnect the Veeam Cloud Connect servers.
      In the Veeam Service Provider Console > Configuration > Cloud Connect > Select servers and click Remove and select Migrate from the drop-down menu.
    2. Re-add the Veeam Cloud Connect servers.

More information

The account used to connect to the Microsoft SQL Server hosting Veeam Service Provider Console database must have the following permissions:
  • 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
Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.