Veeam Availability Console 3.0 upgrade considerations

KB ID: 2933
Product: Veeam Service Provider Console
Version: 3.0
Published: 2019-04-09
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

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

Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.