Veeam ONE Alert - Performance data collection failure

[sirhideo]

Hi,

I have just updated our vCenter 5.5 to build 3000241 yesterday (released on 15 Sep 2015 from VMware) and after that I've got the captioned alarm. Detail is as follows:

Alarm:Performance data collection failure
Time:9/23/2015 4:08:47 PM
Details:Fired by event: VeeamPerfCollectionFailedEvent
Event description: Failed to collect performance data for object 192.168.8.225. A specified parameter was not correct. querySpec.size
Initiated by: Veeam ONE Monitor (VeeamONEServer)

I have tried stop/start veeam one monitor and report service on Veeam ONE server, run the data collection manually from reporter url (success) but no joy. Would like to seek for solution here. Thanks!

[cmaier]

We have the same issue and I already discuss this with the support. (Case # 01061524)
They say that the development guys are working on it.

[sirhideo]

Thank you for your information

[cmaier]

By the way - it looks like the problem is caused by VMware not Veeam.

[sirhideo]

Could be, but I think we need more information from Veeam before calling VMware support.

[Vitaliy S.]

Yes, we are investigating this currently, so if you want to be notified about possible workaround/fix please open a support case with our team first.

[tomson]

I'm not sure if my problem is the same; instead of opening up a new thread

- I have Veeam free monitor version 8.0.1615

- I have two vcenters environments. One of them i have upgraded to Vsphere 6 - the other is still Vsphere 5.5

- Veeam is unable to collect the performance data from the Vsphere 6 environment. The Performance Data from the Vsphere 5.5 environment can still be read out.

- In the Dashobard there is simply a message "Performance data collection failure - Veeam one Monitor server failed to collect performance data from the objects specified"

Is this a known problem with vsphere 6?

Regards

[Vitaliy S.]

That's a bit different. Did you just add this vCenter Server 6 to Veeam ONE or it was already present in Veeam ONE collection job, when you did the upgrade?

[itfnb]

FWIW, I also have two v. 5.5u3 vCenter servers. One is the Windows version and one is the virtual appliance version. Both of them have just been updated to the latest build, but it appears that only the Windows-based version of vCenter Server is having the performance data collection failure. YMMV, but I thought I'd go ahead and pass that info along.

UPDATE: After realizing I didn't have Veeam One 8u2 applied, I went ahead and updated Veeam One and now it appears that the vCenter Server VA version is now also not receiving performance data.

[Vitaliy S.]

itfnb, it is always recommended to be running on the latest update

As for the performance data collection issue - if it is observed during initial job run, then enable this registry key. There are known issues for vSphere 6 and vSphere 5.5 U3, that prevents monitoring tools to collect historical data from the vCenter Server.

[itfnb]

That registry edit did the trick!

[cmaier]

Ok, worked for me, too. What disadvantages do I have now with these registry keys set to zero?

[Vitaliy S.]

The only drawback of this registry key is that Veeam ONE will not import historical performance data (for the past 3 months) from the vCenter Server. In other words, you will be able to generate performance trends and capacity planning reports only after you have enough data collected from the vCenter Server. The more data you have, the more accurate these reports will be.

[soylent]

Any word on a hotfix?

[Vitaliy S.]

Yes, please use the registry key I've mentioned above. Thanks!

[cmaier]

I received a hotfix from support but it seems that it does the same without setting those registry keys.

[Vitaliy S.]

Yes, the hotfix includes this registry key as well as other minor fixes for issues reported by other users.

[soylent]

So this disables historical data collection and makes it real-time only? What happens to modeling or capacity planning?

[Vitaliy S.]

Hi Max,

Not exactly. This registry key disables initial data collection of historical data that is already stored in the vCenter Server. For capacity planning and modelling you will have all the data in place, cause the data you collect with Veeam ONE will be placed into our database and then you will be able to leverage that in the reports.

By referring to historical data I mean data that is stored only in vCenter Server.

Thanks!

[ylws]

Hi Guys,
My veeam one 8 is just stucked in retrieving infrustructure data, it display "importing past performance data", but in past 3 days, the progress never go ahead.I also have add an registry DWORD "HistQueryTimeoutSec" and set it to 3600, but it doesn't work.
Any one can help? Thanks in advance.

[Vitaliy S.]

Please check out the solution mentioned on the first page of this topic, should help!

[fhoffmann]

Hi everybody.
We had the same issue, status info working, performance data not available.

Setting the registry values to 0 will make loose any historical data, also those from vCenters 5.5 update 2 and earlier.
This is explicitly described here: https://www.veeam.com/kb1609

The better way:
Fix it for vCenter 5.5 update 3 and above, and leave other vCenters with historical data UNTOUCHED.
Therefore install Veeam-Fix, which is available here: https://www.veeam.com/kb2071

I've installed that fix and it works fine, leave older data untouched as promised, left the registry keys mentioned under bk1609 untouched, too.

Hope this works for others, too.
Regards.

[Vitaliy S.]

Yes, KB1609 is a bit outdated and doesn't fully resolve the issue, the preferred way for keeping historical data is to apply VMware's reconfiguration of the vCenter Server. Good to hear this solution is working for you!

[carlos.luna]

Hi Vitality, what do you mean when say "the preferred way for keeping historical data is to apply VMware's reconfiguration of the vCenter Server" ?
Regards, Carlos Luna

[Vitaliy S.]

I refer to this KB article referenced in the Veeam KB above. Thanks!

[DeLiriOusNoMaD]

Regedit did the trick, many thanks

[jbarrow.viracoribt]

Yes, please use the registry key I've mentioned above. Thanks!

Once we set this, and reboot or restart services, should we set it back?

If so, what are the default settings for these two keys?

[Vitaliy S.]

The defaults in v8 are to import past performance data, if you're on v9 no re-configuration is required. If you applied these keys, restarted all services, the error should go away.

[jbarrow.viracoribt]

We're still on v8.

I changed these settings to get past constant errors collecting data from our server but I now want to change them back. I didn't record what the defaults were for these two keys before setting them to 0 though. Do you know what those are out of the box?

[Vitaliy S.]

Oh... I see. To enable it back switch these keys to 1 or just delete them. Thanks!