Event pre-filtering causes high vCenter Database load

Veeam Management Pack for Microsoft System Center;Veeam Smart Plug-in (SPI) for VMware
Last Modified:


The vCenter Database utilizes most of the available CPU, impacting vCenter Server performance. Stopping nworks Collectors brings the CPU usage back to normal. The nworks vmspi log shows the following errors: 

VCEVT+** [VC250] retrieveEvents: createFilter failed, System.Net.WebException: The operation has timed out


nworks can use a vCenter-side event filter to reduce the traffic back to the Collector. The filtering, however, turns out to impact vCenter Database performance.


In nworks 5.6 and later, creation of the event filter is disabled by default. However, if the issue described above occurs, you will need to turn off the setting manually:
  1. In nworks Web UI, go to the Enterprise Manager tab, select the Collector in the hierarchy on the left and click Advanced settings

  2. Find the EnableVcVerboseFilter setting and set it to False

  3. You will be prompted to restart the Collector. To do that, select the Collector and click the Restart button.

Applied changes will not influence monitoring accuracy.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
5 out of 5 based on 1 ratings

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: