OPERATIONAL DEFECT DATABASE
...
...
After upgrading Veeam Backup & Replication servers to version 9.5 Update 4, Veeam Cloud Connect monitoring and reporting in Veeam ONE 9.5 Update 3 will stop working.
This issue is caused by incompatibility of Veeam Backup & Replication 9.5 Update 4 and Veeam ONE 9.5 Update 3. To resolve this issue, confirm you are running Veeam ONE version 9.5.0.3801 prior to installing this compatibility patch. NOTE: For those who are not using Cloud Connect, there is no need to apply the compatibility patch as there are no issues monitoring Veeam Backup & Replication 9.5 Update 4 with Veeam ONE 9.5 Update 3.
There are several ways of applying the hotfix:Using SQL Server Management Studio Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and the database name. Alternatively, check the same via Veeam ONE Settings Utility (C:\Program Files\Common Files\Veeam\Veeam ONE Settings). Open Microsoft SQL Server Management Studio with the Administrator permissions. Connect to the ServerName\Instance of the server that has the Veeam ONE database. Expand the Databases tree and select "VeeamOne" database (default name). Right-click on the database > New Query. Copy the following query and run it against the database: IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL ALTER TABLE monitor.BpCloudTenantVersionInfo DROP CONSTRAINT [ENUM_CTVI_PV]; If the query was performed correctly, you will get the following status in the SQL Server Management Studio: Commands completed successfully. Using SQL command line In case you do not have the Management Studio installed, run the hotfix against the Veeam ONE database using the SQLCMD utility: Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and the database name. Alternatively, check the same via Veeam ONE Settings Utility (C:\Program Files\Common Files\Veeam\Veeam ONE Settings). Open Windows command line or PowerShell prompt using the Veeam ONE Service account and run the hotfix against the Veeam ONE database: for default instances (change the database name in the query if it differs from yours): sqlcmd -S SqlServerName -q "USE VeeamOne IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL ALTER TABLE monitor.BpCloudTenantVersionInfo DROP CONSTRAINT [ENUM_CTVI_PV];" for named instances (change the database name in the query if it differs from yours): sqlcmd -S SqlServerName\SqlInstanceName -q "USE VeeamOne IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL ALTER TABLE monitor.BpCloudTenantVersionInfo DROP CONSTRAINT [ENUM_CTVI_PV];" In case you have SQL server authentication enabled you may define username and password (change the database name in the query if it differs from yours): sqlcmd -S SqlServerName\SqlInstanceName -U username -P password -q "USE VeeamOne IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL ALTER TABLE monitor.BpCloudTenantVersionInfo DROP CONSTRAINT [ENUM_CTVI_PV];"
Should have any questions, contact Veeam Support.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
