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

Intermittent vCenter disconnections in Veeam ONE Monitor

Challenge

vCenter periodically disconnects from Veeam ONE Moniotor. This causes intermittent alerts that get resolved automatically in several minutes when a connection is restored.

Cause

This behavior is caused by vCenter Update Manager. When checking for updates Update Manager might freeze vCenter database for a few moments resulting in vCenter being unable to give its performance data to Veeam ONE.

Solution

In vCenter, go to File - Export - Export Events. Match the time of the alerts and find them in vCenter event log. You might find that every time an alert is triggered, Update Manager is running its tasks.

This issue is documented in the following VMware KB article.

To resolve this issue, contact VMware Support.

More information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support
KB ID:
1716
Product:
Veeam ONE
Version:
6.5
Published:
2013-01-17
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