How to migrate Veeam Backup & Replication or Veeam Backup Enterprise Manager

1. Export all Keysets from the old Veeam Backup Enterprise Manager web console. Take note of which keyset was Active
2. Stop the following services on the old Veeam Backup Enterprise Manager server.
   • Veeam Backup Enterprise Manager
   • Veeam Guest Catalog Service
   • Veeam RESTful API Service
     ^{Note: On combined VBEM and VBR deployments, there are two Veeam services with RESTful API in their name. Stop the one named Veeam RESTful API Service, not the one named Veeam Backup Server RESTful API Service.}
3. Back up the old Veeam Backup Enterprise Manager configuration database.
   Refer to KB1471: How to Manually Back up Veeam Configuration Databases
   
4. Uninstall Veeam Backup Enterprise Manager from the old server.
5. If Veeam Backup Enterprise Manager was installed on the same server as Veeam Backup & Replication, at this point, all Veeam services on the old server may be started.
6. Install Backup Enterprise Manager on the new server.
   
   Critical Note: If the old Veeam Backup Enterprise Manager server was hosting the configuration database on Microsoft SQL Server, and you are installing Veeam Backup Enterprise Manager v12 or newer, you must select the "Customize settings" option during installation and specify an existing Microsoft SQL Server Instance. If there is no existing Microsoft SQL Server Instance on the machine where you are migrating Veeam Backup Enterprise Manager, you must install Microsoft SQL Server Express yourself.
7. Stop the following services on the new Veeam Backup Enterprise Manager server.
   • Veeam Backup Enterprise Manager
   • Veeam Guest Catalog Service
   • Veeam RESTful API Service
     
8. Restore the backup of the old VeeamBackupReporting database over the new database created during the installation of Veeam Backup Enterprise Manager
   • If the configuration database was hosted on Microsoft SQL Server, use SSMS to restore the backup.
     Note: Enable "Overwrite the existing database" in the Restore Database > Options menu of SSMS
   • If the configuration database was hosted on PostgreSQL, we recommend using pgAdmin to restore the backup.
     Note: Enable "Clean before restore" in the Query Options tab of the Restore Dialog.
9. Using the dbconfig tool on the new server, reconfigure Backup Enterprise Manager to use the restored database. The tool will prompt stating that the database is in use by the old Backup Enterprise Manager server. Select Yes to update the database ownership to the new server.
   
10. At this point in the migration, there will be keysets visible in the Veeam Backup Enterprise Manager web console, but they are invalid. You must do the following to replace each keyset:
    1. Import Keyset(s) from the old Backup Enterprise Manager server.
    2. Set whichever keyset was Active in the old Backup Enterprise Manager console to be Active.
    3. Delete the corresponding invalid keyset that was replaced by the import process.
11. Update passwords for each connected Veeam Backup & Replication server.
    Reference Veeam KB1900 for information about password locations to update in Backup Enterprise Manager.

12. (Optional) Compare the following registry keys on the old and new Veeam Backup Enterprise Manager servers to identify if any custom registry values need to be brought to the new Veeam Backup Enterprise Manager server.

    • HKLM\SOFTWARE\Veeam\Veeam Backup Catalog
    • HKLM\SOFTWARE\Veeam\Veeam Backup Reporting
13. (Veeam Backup Enterprise Manager 12.0 & 12.2) If the mail server settings were configured prior to migration, you must contact Veeam Support for assistance with clearing the email client settings in the configuration database (reference Issue ID# 614693).

Before you begin, please note that this type of migration requires sufficient experience in ensuring that the existing SQL Instance is configured to allow the new Veeam Backup Enterprise Manager deployment to connect remotely.

1. Export all Keysets from the old Veeam Backup Enterprise Manager web console. Take note of which keyset was Active
2. Uninstall Veeam Backup Enterprise Manager from the old server.
3. Install Backup Enterprise Manager on the new server.
   
   The installer will deploy a local PostgreSQL instance, which will be used for the new deployment, but in the later steps, you will reconfigure Veeam Backup Enterprise Manager to utilize the existing database that remains on the old SQL Instance.
   
   Critical Note: If the old Veeam Backup Enterprise Manager server was hosting the configuration database on Microsoft SQL Server, and you are installing Veeam Backup Enterprise Manager v12 or newer, you must select the "Customize settings" option during installation and specify an existing Microsoft SQL Server Instance. If there is no existing Microsoft SQL Server Instance on the machine where you are migrating Veeam Backup Enterprise Manager, you must install Microsoft SQL Server Express yourself.
4. Stop the following services on the new Veeam Backup Enterprise Manager server.
   • Veeam Backup Enterprise Manager
   • Veeam Guest Catalog Service
   • Veeam RESTful API Service
5. Using the dbconfig tool on the new server, reconfigure Backup Enterprise Manager to use the existing database. The tool will prompt stating that the database is in use by the old Backup Enterprise Manager server. Select Yes to update the database ownership to the new server.

6. At this point in the migration, keysets will be visible in the Veeam Backup Enterprise Manager web console; however, they will be invalid. You must do the following to replace each keyset:
   1. Import Keyset(s) from the old Backup Enterprise Manager server.
   2. Set whichever keyset was Active in the old Backup Enterprise Manager console to be Active.
   3. Delete the corresponding invalid keyset that was replaced by the import process.
7. Update passwords for each connected Veeam Backup & Replication server.
   Refer to Veeam KB1900 for information on password locations to update in Backup Enterprise Manager.

8. (Optional) Compare the following registry keys on the old and new Veeam Backup Enterprise Manager servers to identify if any custom registry values need to be brought to the new Veeam Backup Enterprise Manager server.

   • HKLM\SOFTWARE\Veeam\Veeam Backup Catalog
   • HKLM\SOFTWARE\Veeam\Veeam Backup Reporting
9. (Veeam Backup Enterprise Manager 12.0 & 12.2) If the mail server settings were configured before migration, you must contact Veeam Support for assistance with clearing the email client settings in the configuration database (reference Issue ID# 614693).

1. Stop the following services on the  Backup Enterprise Manager server.
   • Veeam Backup Enterprise Manager
   • Veeam Guest Catalog Service
   • Veeam RESTful API Service
2. Back up the old Backup Enterprise Manager configuration database (VeeamBackupReporting).
   
3. Restore the backup of the old VeeamBackupReporting database to the new MSSQL\PGSQL server.
   1. For Microsoft SQL Server, use SSMS to restore the backup.
      
   2. For PostgreSQL, we recommend using pgAdmin to restore the backup.
      _{If you want to use an existing PostgreSQL instance, ensure that the instance can use sufficient resources. For more information, see Configuring PostgreSQL Instance.}
4. This step can be skipped if native Microsoft SQL\PostgreSQL authentication will be used for the remote connection.
   
   If the database was restored to a Microsoft SQL Server instance that uses Windows Authentication or a PostgreSQL server that utilizes SSPI Authentication, the services associated with Enterprise Manager must be configured to 'Log on as' using an account that has the appropriate permissions to connect to the Microsoft SQL Server or PostgreSQL server. Below are the services that must be modified before continuing to the next step:
   • Veeam Backup Enterprise Manager
   • Veeam Guest Catalog Service
   • Veeam RESTful API Service
5. Using the dbconfig tool reconfigure Backup Enterprise Manager to use the restored database.
   
6. Start all Veeam services on the Backup Enterprise Manager server.