https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyOTMzIiwiaGFzaCI6IjVjYWVhNGE2LTA1M2UtNGVjZi04NGQwLWE0ZjBiM2Y0Zjc3NiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Veeam Availability Console 3.0 upgrade considerations

Challenge

Under certain circumstances upgrade to Veeam Availability Console v3 may fail leaving configuration database in a non-consistent state

Cause

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. Using Microsoft SQL Management Studio or sqlcmd connect to the SQL Server running the Configuration Database. You can get the Database connection parameters from the corresponding section in the Server Settings.
    • Using Management Studio: Connect to the "ServerName\Instance" obtained from Server Settings
    • Using sqlcmd: Open an Administrative Command Prompt and execute the following command:
      SQLCMD -S ServerName\Instance
      Note: In case you have SQL server authentication enabled you may define username using '-U' parameter
  3. Back up Availability Console database: 
    • Using Management Studio: Expand the Databases tab, right click the VAC DB --> Tasks --> Back Up. Set "Backup Type" to "Full"
    • Using sqlcmd:
      BACKUP DATABASE VACDatabaseName TO DISK = 'C:\VAC_DB.bak'
      GO
  4. Execute the script against the Availability Console database.
    • Using Management Studio: Right click on your VAC database and choose the “New query” option, insert the text from the file, and click Execute.
    • Using sqlcmd:
      SQLCMD -S ServerName\Instance -d VACDatabaseName -i PATHTOSCRIPT\Pre-upgradeCheck.sql -o c:\result.txt -I
      Note: In case you have SQL server authentication enabled you may define username using '-U' parameter

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'

More information

KB ID:
2933
Product:
Veeam Service Provider Console
Version:
3.0
Published:
2019-04-09
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.