BugZero found this defect 3554 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
8/13/2020
Veeam Backup & Replication
ALL
No fixed releases provided.
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:
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.
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 v7Use VeeamBackupReportingUPDATE [Version] SET current_version = 568UPDATE [Version] SET Fill_version = 341 # Veeam Backup & Replication v8Use VeeamBackupReportingUPDATE [Version] SET current_version = 670UPDATE [Version] SET Fill_version = 568# Veeam Backup & Replication v9Use VeeamBackupReportingUPDATE [Version] SET current_version = 849UPDATE [Version] SET Fill_version = 713# Veeam Backup & Replication v9.5Use VeeamBackupReportingUPDATE [Version] SET current_version = 1130UPDATE [Version] SET Fill_version = 1151 After install completes be sure to run the most recent patch. This can be found at: http://www.veeam.com/patches.html.