This is a short blog post to give you some alert troubleshooting details.
The alert VMware connection data processing errors from the Veeam VMware management pack (8.x) needs a collector server and a Run As Account with permissions in VCenter. Permissions are described in this article.
“The Veeam VMware Collector service was not able to process data it received from the VMware target. Some data could be missing in the VMware API response or it could be a parsing error. Some performance data may not be published. The exact error received from Collector: VP050 Error encountered while retrieving performance metrics for a cluster on system name. The VMware API error returned was: ‘One or more errors occurred.’.”
The alert details talk about performance metrics, which confused me.
The Veeam logs (you get them through the Veeam Enterprise Console) show these details:
[VP120] retrieveDatastores failed, A: No ‘datastore’ objects returned for VC,
Collector cannot access a datastore at the vCenter.
Then, [VP038] buildInventory failed [system name]
Cannot build topology always for system name
And after that you seeing [VP050] performanceDaemon One or more errors occurred.
Possible root causes:
1. system does not have a datastore at all
2. no permissions => re check permissions (see link above)
The permissions need to be set on the top level of the cluster not below!
To check, if the system has a datastore, you can browse the following webpage: http://system name/mob or https://system name/mob. Login with the Run As Account.
Then click the content link.
Click the link beside the rootFolder entry.
Click the link beside the childEntitiy entry.
If you see one or more datastores in the list, then the permissions are correct.
You can also click on one of the datastore links to verify.
When both topics are resolved (permissions and datastore access) then the alert should resolve itself.