Operational Defect Database

BugZero found this defect 3122 days ago.

Veeam | kb2071

Collection of historical performance data fails after upgrading to vSphere 5.5 Update 3

Last update date:

8/13/2020

Affected products:

Veeam ONE

Affected releases:

ALL

Fixed releases:

No fixed releases provided.

Description:

Challenge

After update to vCenter 5.5 U3 historical performance collection fails with error "Unable to collect performance. A specified parameter was not correct. querySpec.size".

Cause

With vCenter 5.5 Update 3 VMware has limited the size of query in order to protect the vCenter database (more information can be found in this VMware KB article).

Solution

At the moment two workarounds are available.1. Disable the collection of historical information as described in the following KB article. This will effectively turn off the collection of historical data for all vCenter servers added to your installation of Veeam ONE.or, alternatively,2. Download and apply build 8.0.0.1731. With build 8.0.0.1731 the collection of historical information will be disabled for vCenter servers 5.5 Update 3 and later. vCenter versions prior to 5.5 U3 will not be affected. To apply build 8.0.0.1731, run the executable file on the machines containing Veeam ONE services, as well as on all machines, where Veeam ONE Monitor Client is installed.

More Information

If you have any questions, please contact Veeam Support.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

Learn More

Search:

...