Challenge
If the Veeam Backup Enterprise Manager software is moved, or needs to be reinstalled and it was previously patched it errors out with the following error:Cause
The SQL database that is being reused contains table entries that mark it as having been used with a newer version the version of BEM that is being installed.Solution
If you wish to start with a clean installation:•Remove the existing VeeamBackupReporting DB to allow a fresh DB to be created.
──────────
If you wish to preserve existing historical information within BEM:
• Modify the existing VeeamBackupReporting DB to be seen as an earlier version, using SQL queries below.
Note: We recommend backing up your database prior to making any changes. To change the version number:
1. From SQL Management Studio, connect to the instance containing the Veeam configuration database (default name is VeeamBackupReporting)
2. Expand “Databases”
3. Right-click “VeeamBackupReporting” > New query.
4. Paste the appropriate query (below) and press “execute” or F5.
# Veeam Backup & Replication v7
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 568
UPDATE [Version] SET Fill_version = 341
# Veeam Backup & Replication v8
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 670
UPDATE [Version] SET Fill_version = 568
# Veeam Backup & Replication v9
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 849
UPDATE [Version] SET Fill_version = 713
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 568
UPDATE [Version] SET Fill_version = 341
# Veeam Backup & Replication v8
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 670
UPDATE [Version] SET Fill_version = 568
# Veeam Backup & Replication v9
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 849
UPDATE [Version] SET Fill_version = 713
After install completes be sure to run the most recent patch. This can be found at: http://www.veeam.com/patches.html.