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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMDcxIiwiaGFzaCI6IjJkNDk2ODVhLTg5YWItNDZkMy1hYjg3LTIwNjQ2MDIzZGU3MSJ9
1-800-691-1991 | 9am - 8pm ET
EN

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

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.
KB ID:
2071
Product:
Veeam ONE
Version:
8.x
Published:
2015-11-02
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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later