Migrating Veeam Service Provider Console

In case you need to move Veeam Service Provider Console Server to another location, and want to preserve configuration and client data, you can install Veeam Service Provider Console Server on a new machine and connect it to an existing database. Alternatively, you can migrate only the configuration database used by Veeam Service Provider Console or both Veeam Service Provider Console Server and the configuration database.

Before You Begin

Before you start the migration process, complete the following prerequisites:

Check and save the version of the Veeam Service Provider Console server which you want to migrate to a new machine.

Make sure that the machine on which you plan to migrate Veeam Service Provider Console meets software and hardware requirements.

For details, see System Requirements

Make sure that an account used to connect to Veeam Service Provider Console database has necessary permissions.

For details, see Connecting to Microsoft SQL Server.

Migrating Veeam Service Provider Console Configuration Database

To migrate only the Microsoft SQL Server configuration database used by Veeam Service Provider Console server and connect Veeam Service Provider Console to the migrated database:

Move the Veeam Service Provider Console database to an existing Microsoft SQL Server instance that you want to use. For details on database migration, see Microsoft Docs.
Update SQL Server connection settings in Veeam Service Provider Console. For details, see section Configuring SQL Server Connection Settings of the Guide for Service Providers.

Migrating Veeam Service Provider Console Server

To migrate only Veeam Service Provider Console Server component:

Transfer security certificates used in the old Veeam Service Provider Console configuration to the machine where you plan to install Veeam Service Provider Console:

To retrieve the certificate thumbprint, use the following SQL query:

SELECT RootCertThumbprint FROM [VeeamBR].[ServerSettings]

To export the active certificates, run the following PowerShell commands as an administrator:

$mypwd = Get-Credential

Get-ChildItem -Path cert:\localMachine\my\<thumbprint> | Export-PfxCertificate -FilePath <path> -Password $mypwd.Password

where:

<thumbprint> — certificate thumbprint obtained at step a.
<path> — path to the certificate file.

To import the certificates to the target machine, run the following PowerShell commands as an administrator:

$mypwd = Get-Credential

Import-PfxCertificate -FilePath <path> -CertStoreLocation Cert:\LocalMachine\My -Password $mypwd.Password

Import-PfxCertificate -FilePath <path> -CertStoreLocation Cert:\LocalMachine\Root -Password $mypwd.Password

where <path> is the path to the certificate file.

Important!

You cannot export self-signed certificates. If you use self-signed certificates, skip step 1 and generate new self-signed certificates in the Veeam Service Provider Console installation wizard.

Install a new Veeam Service Provider Console Server on a target machine as described in section Install Veeam Service Provider Console.
At the Security Certificates step of the wizard, select certificates imported at step 1.

If you used self-signed certificates, generate new certificates.

At the SQL Server Instance step of the installation wizard, select the Use existing instance of SQL Server option and point to the database used in the previous Veeam Service Provider Console installation.

If you had any updates installed on top of the Veeam Service Provider Console major release version, you cannot specify an existing database during installation. To workaround version mismatch between the new Veeam Service Provider Console server and existing database, at the SQL Server Instance step of the installation wizard, select the Install new instance of SQL Server option. When installation completes, update Veeam Service Provider Console to the version of the previous installation. Then, connect to a required database. For details, see section Configuring SQL Server Connection Settings of the Guide for Service Providers.

Follow through the other steps of the wizard to complete the installation.
If you have migrated Veeam Service Provider Console to a server with hostname different from the old server, you must reconnect Veeam Cloud Connect servers to Veeam Service Provider Console:

Disconnect Veeam Cloud Connect servers as described in section Disconnecting Veeam Cloud Connect Servers of the Guide for Service Providers. Note that you must use the Migrate option.
Reconnect Veeam Cloud Connect servers as described in section Connecting Veeam Cloud Connect Servers of the Guide for Service Providers.

Manually update the following components:

Service accounts and connection accounts used to connect Veeam Cloud Connect servers. For details, see section Managing Veeam Cloud Connect Servers of the Guide for Service Providers.
SMTP server authentication credentials. For details, see section Configuring Notification Settings of the Guide for Service Providers.
Access accounts credentials specified in the configured discovery rules. For details on the discovery rules, see section Deploying Management Agents with Discovery Rules of the Guide for Service Providers.
Veeam Backup & Replication servers and shared folders access credentials and applications credentials specified in the configured backup policies. For details on changing backup policies settings, see section Modifying Backup Policies of the Guide for Service Providers.
Veeam Backup for Public Clouds integration:

Update accounts used to connect appliances. For details, see section Modifying Accounts of the Guide for Service Providers.
Update guest OS account specified in the appliance settings. For details, see section Modifying Appliances of the Guide for Service Providers.
Reassign client companies to the appliances. For details, see section Assigning Company to Appliance of the Guide for Service Providers.

Migrating Veeam Service Provider Console Server and Configuration Database

Transfer security certificates used in the old Veeam Service Provider Console configuration to the machine where you plan to install Veeam Service Provider Console:

To retrieve the certificate thumbprint, use the following SQL query:

SELECT RootCertThumbprint FROM [VeeamBR].[ServerSettings]

To export the active certificates, run the following PowerShell commands as an administrator:

$mypwd = Get-Credential

Get-ChildItem -Path cert:\localMachine\my\<thumbprint> | Export-PfxCertificate -FilePath <path> -Password $mypwd.Password

where:

<thumbprint> — certificate thumbprint obtained at step a.
<path> — path to the certificate file.

To import the certificates to the target machine, run the following PowerShell commands as an administrator:

$mypwd = Get-Credential

Import-PfxCertificate -FilePath <path> -CertStoreLocation Cert:\LocalMachine\My -Password $mypwd.Password

Import-PfxCertificate -FilePath <path> -CertStoreLocation Cert:\LocalMachine\Root -Password $mypwd.Password

where <path> is the path to the certificate file.

Important!

You cannot export self-signed certificates. If you use self-signed certificates, skip step 1 and generate new self-signed certificates in the Veeam Service Provider Console installation wizard.

Move the Veeam Service Provider Console database to an existing Microsoft SQL Server instance that you want to use. For details on database migration, see Microsoft Docs.
Install a new Veeam Service Provider Console Server on a target machine as described in section Install Veeam Service Provider Console.
At the Security Certificates step of the wizard, select certificates imported at step 1.

If you used self-signed certificates, generate new certificates.

At the SQL Server Instance step of the installation wizard, select the Use existing instance of SQL Server option and point to the database migrated at step 2.

If you had any updates installed on top of the Veeam Service Provider Console major release version, you cannot specify a migrated database during installation. To workaround version mismatch between the new Veeam Service Provider Console server and existing database, at the SQL Server Instance step of the installation wizard, select the Install new instance of SQL Server option. When installation completes, update Veeam Service Provider Console to the version of the previous installation. Then, connect to a migrated database. For details, see section Configuring SQL Server Connection Settings of the Guide for Service Providers.

Follow through the other steps of the wizard to complete the installation.
If you have migrated Veeam Service Provider Console to a server with hostname different from the old server, you must reconnect Veeam Cloud Connect servers to Veeam Service Provider Console:

Disconnect Veeam Cloud Connect servers as described in section Disconnecting Veeam Cloud Connect Servers of the Guide for Service Providers. Note that you must use the Migrate option.
Reconnect Veeam Cloud Connect servers as described in section Connecting Veeam Cloud Connect Servers of the Guide for Service Providers.

Manually update the following components:

Service accounts and connection accounts used to connect Veeam Cloud Connect servers. For details, see section Managing Veeam Cloud Connect Servers of the Guide for Service Providers.
SMTP server authentication credentials. For details, see section Configuring Notification Settings of the Guide for Service Providers.
Access accounts credentials specified in the configured discovery rules. For details on the discovery rules, see section Deploying Management Agents with Discovery Rules of the Guide for Service Providers.
Veeam Backup & Replication servers and shared folders access credentials and applications credentials specified in the configured backup policies. For details on changing backup policies settings, see section Modifying Backup Policies of the Guide for Service Providers.
Veeam Backup for Public Clouds integration:

Update accounts used to connect appliances. For details, see section Modifying Accounts of the Guide for Service Providers.
Update guest OS account specified in the appliance settings. For details, see section Modifying Appliances of the Guide for Service Providers.
Reassign client companies to the appliances. For details, see section Assigning Company to Appliance of the Guide for Service Providers.

Important!

Consider the following:

If you did not transfer Veeam Service Provider Console security certificates to the target machine, you will have to verify Veeam Service Provider Console management agents manually. For details, see section Setting Company to Management Agents of the Guide for Service Providers.
If your new Veeam Service Provider Console server is connected to the same domain as the previous installation, portal user roles will be restored from the database.

In case you installed Veeam Service Provider Console in a different domain, or you had any portal user roles assigned to local users of the previous Veeam Service Provider Console Server, you may need to reassign portal user roles manually. For details, see section Managing Administrator Portal Users of the Guide for Service Providers.