Challenge
You need to move Veeam Backup & Replication or Enterprise manager software and/or database to a new server.
Solution
Veeam Backup & Replication migration
Note: This section will refer to the server where Veeam Backup & Replication is installed prior to the move as the “old server”, and the location after the move as the “new server”.
There are two methods to perform Veeam Backup & Replication migration task:
Migrate using Configuration Backup
Perform the following steps on the old server:
- Stop and disable all jobs.
- Manually perform a configuration backup.
- Close Veeam GUI and stop all Veeam Services.
Perform the following steps on the new server:
- Install Veeam Backup & Replication with a brand new DB.
- Apply the latest patch to Veeam Backup & Replication: http://www.veeam.com/patches.html
- Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
- Perform configuration backup restore:
Note: It will be necessary to re-enter the password for every account during restore of non-encrypted configuration backups. - Run a test job to make sure everything moved correctly.
Migrate using SQL Backup
IMPORTANT: Use this option only if Configuration Backup is not available. If encryption was used on the previous installation, a newly installed backup server will not be able to decrypt such information if attached to the existing database, so any encrypted information will have to be supplied manually – existing encrypted backups have to be re-imported to provide the password.
Perform the following steps on the old server:
- Stop and disable all jobs.
- Close Veeam GUI and stop all Veeam Services.
- Create backup of the SQL database. (http://vee.am/kb1471)
To find out where the VeeamBackup database is located, open regedit on the old server and navigate to: [HKLM\SOFTWARE\Veeam\Veeam Backup and Replication]
There you will find 3 dword values:- SqlServerName
- SqlInstanceName
- SqlDatabaseName
Perform the following steps on the new server:
- Install Veeam Backup & Replication with a brand new DB.
- Apply the latest patch to Veeam. http://www.veeam.com/patches.html
- Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
- Restore the Veeam database to the instance on the new server or on a SQL server which will host Veeam DB.
Click (here) for information regarding restoring databases. - To associate Veeam with the restored database, please use the DBConfig Utility to change the Database that Veeam is connecting to.
- Restart Veeam Services to apply the changes.
- Open the Veeam console and using the “Manage Credentials” button from the main menu and check the passwords for every account to confirm they are up to date.
- Run a test job to make sure everything moved correctly.
Enterprise manager migration
Note: This section describes how to move the Enterprise Manager (EM) database to a different SQL if the EM is installed separately from the Backup & Replication.
- Relocate VeeamBackupReporting DB to the new SQL server. See http://vee.am/kb1250
- On the Veeam Backup & Replication server, open the following directory:
C:\Program Files\Veeam\Backup and Replication\Backup - On the EM server, open the following directory:
C:\Program Files\Veeam\Backup and Replication\Enterprise Manager - Сopy the following files from the VBR folder to the EM one:
- Veeam.Backup.Configuration.Tool.exe
- Veeam.Backup.DBConfig.exe
- Veeam.Backup.Tool.Core.dll
- Veeam.Backup.Backup.UI.dll
- Run the copied ‘Veeam.Backup.DBConfig.exe’ as Administrator
- Follow the steps described here to connect the EM to the new DB location: https://helpcenter.veeam.com/docs/backup/hyperv/using_dbconfig_utility.html?ver=95
More Information
In situations where physical local storage is used please see the following KB that details how to relocate Veeam Backup and Replication backup file locations: https://www.veeam.com/kb1729
For steps on migrating the Veeam database to another SQL Instance or Server, please refer to KB1250.