The Community Event for Data Recovery Experts

Watch for FREE to expand your cloud and security skills

On-demand event

Watch now

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

KB ID: 1889
Product: Veeam Backup & Replication | 9.5 | 10 | 11 | 12
Published: 2014-05-29
Last Modified: 2022-05-11
mailbox
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.

Veeam Backup & Replication Migration

Details regarding Veeam Backup & Replication migration are now fully documented in the product user guide.

Please review the following documentation:


Other Migration Types:

 

Veeam Backup Enterprise Manager Migration

The credentials and keysets stored in the Backup Enterprise Manager database are encrypted in such a manner that moving where the Backup Enterprise Manager software is installed will cause them to become invalid. Before moving where Backup Enterprise Manager is installed, you must export keysets and be prepared to re-enter all credentials for connections to Veeam Backup & Replication servers managed by Backup Enterprise Manager. When only relocating the Backup Enterprise Manager configuration database, the credentials and keysets will remain valid.

 

Expand the section below that best matches the type of Migration needed:

Migrate Backup Enterprise Manager software and its configuration database to a new server

Use case example:

  • Veeam Backup & Replication and Backup Enterprise Manager were installed on the same machine, and you want to move Backup Enterprise Manager off to its own server.
  • You want to move Backup Enterprise Manager and its configuration database to a new server.
  1. Export all Keysets from the old Backup Enterprise Manager web console. Take note of which keyset was Active

  2. Stop the following services on the old Backup Enterprise Manager server.
    • Veeam Backup Enterprise Manager
    • Veeam Guest Catalog Service
    • Veeam RESTful API Service
       
  3. Using SQL Service Management Studio, backup the old Backup Enterprise Manager configuration database (VeeamBackupReporting).

  4. Uninstall Backup Enterprise Manager from the old server.

  5. If 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

  7. Stop the following services on the new Backup Enterprise Manager server.
    • Veeam Backup Enterprise Manager
    • Veeam Guest Catalog Service
    • Veeam RESTful API Service

  8. Using SSMS, restore the backup of the old VeeamBackupReporting database over the new database created during the installation of Backup Enterprise Manager.

    Note: Enable "Overwrite the existing database" in the Restore Database > Options menu of SSMS

  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. Launch the Backup Enterprise Manager web console and update passwords for each connected Veeam Backup & Replication server. Reference https://www.veeam.com/kb1900 for information about password locations to update in Backup Enterprise Manager.

  11. At this point in the migration, there will be keysets visible in the 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. Delete the corresponding invalid keyset that was replaced by the import process.
    3. Set whichever keyset was Active in the old Backup Enterprise Manager console to be Active

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

    • HKLM\SOFTWARE\Veeam\Veeam Backup Catalog
    • HKLM\SOFTWARE\Veeam\Veeam Backup Reporting
Migrate the Veeam Backup Enterprise Manager configuration database to an existing SQL Instance but keep the software in place.

Use case example:

  • You want to keep Backup Enterprise Manager installed where it is, but shift from using the default local SQL instance to a dedicated SQL server's instance. (SQL Requirements | Permissions Requirements)
  1. Stop the following services on the  Backup Enterprise Manager server.
    • Veeam Backup Enterprise Manager
    • Veeam Guest Catalog Service
    • Veeam RESTful API Service
       
  2. Using SQL Server Management Studio, backup the old Backup Enterprise Manager configuration database (VeeamBackupReporting).

  3. Using SSMS restore the backup of the VeeamBackupReporting database to the new SQL Instance

  4. On the server where Backup Enterprise Manager is installed, edit the following services and set their "Log on as" value to an account that has the appropriate permissions to the SQL Instance where the VeeamBackupReporting database is being relocated to.
    • 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 service on the Backup Enterprise Manager server.

 

Migrate the Backup Enterprise Manager software, but keep the configuration database in place.

Use case example:

  • You want to keep the Backup Enterprise Manager configuration database on the SQL Instance where it is, but you want to move where the Backup Enterprise Manager software is run.
  1. Export all Keysets from the old Backup Enterprise Manager web console. Take note of which keyset was Active

  2. Uninstall Backup Enterprise Manager from the old server.

  3. Install Backup Enterprise Manager on the new server. During the installation of Backup Enterprise Manager, do the following:

    1. If presented with the Default Configuration step of the installer, check the box labeled "Let me specify different settings"

    2. For the Service Account Credentials step, provide an account with the appropriate permissions to the SQL Instance where the VeeamBackupReporting database is located.

    3. On the SQL Server Instance step, choose the option to "Use existing instance of SQL Server" and specify the SQL Server and Instance where the existing VeeamBackupReporting database is located. Change the name of the database to be created to "VeeamBackupReportingTemp".

      This is done to prevent conflicts during the installation process. Later steps will reconfigure Backup Enterprise Manager to target the old database.
       
  4. Using the dbconfig tool on the new server, reconfigure Backup Enterprise Manager to use the old VeeamBackupReporting 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.

  5. Launch the Backup Enterprise Manager web console and update passwords for each connected Veeam Backup & Replication server. Reference https://www.veeam.com/kb1900 for information about password locations to update in Backup Enterprise Manager.

  6. At this point in the migration, there will be keysets visible in the Backup Enterprise Manager web console, but they are invalid. You must do the following to replace each keyset(s):
    1. Import Keyset from old Backup Enterprise Manager server.
    2. Delete the corresponding invalid keyset that was replaced by the import process.
    3. Set whichever keyset was Active in the old Backup Enterprise Manager console to be Active 
       

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

    • HKLM\SOFTWARE\Veeam\Veeam Backup Catalog
    • HKLM\SOFTWARE\Veeam\Veeam Backup Reporting
If you have any issue during the migration of Backup Enterprise Manager, create a support case and include logs from %programdata%\Veeam\Setup\Temp
To submit feedback regarding this article, please click this link: 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.

You have selected too large block!

Please try select less.

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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.