Challenge
Under certain circumstances upgrade to Veeam Availability Console v3 may fail leaving configuration database in a non-consistent stateCause
The issue occurs when one or more tenants from the underlying Cloud Connect server have duplicated backup quotas on the repository.Solution
Before upgrading an existing Veeam Availability Console installation to version 3, please run the pre-upgrade check script. This script removes duplicated values from the VAC database that can affect the upgrade procedure.To apply the script:
1. Ensure that you are running Availability Console 2.0 (any update and patch level). The script will not work on an earlier version of the database.
2. Use Microsoft SQL Management Studio or sqlcmd as described in the KB1471, connect to the Configuration Database. You can get the Database connection parameters from the corresponding section in the Server Settings.
3. Back up Availability Console database.
4. Execute the script against the Availability console database. Please refer to KB1443 for detailed instructions.
Interpreting the results:
If the script outputs one of the following messages, you can proceed with the upgrade to version 3.0:
(x row(s) affected)
All duplicates entries (x) have been removed. Ready to upgrade.
or
(0 row(s) affected)
No duplicates have been found. Ready to upgrade.
In case of the following message, make sure that the product's version is at least 2.0 or 2.0U1, and you are connected to a proper database. If these conditions are met, contact Technical Support for assistance:
Msg 208, Level 16, State 1, Line 5
Invalid object name 'VeeamBR.CompanyResources'