OPERATIONAL DEFECT DATABASE
...
...
The following alerts about handle counts on the collector server are raised: Health Service (Monitoring Host) Handle Count has exceeded the threshold Health Service Handle Count has exceeded the threshold
The monitors raising the mentioned alerts ensure that the "Process\Handle Count" counter for the "MonitoringHost.exe" and "HealthService.exe" processes does not exceed a specific threshold over a series of consecutive samples. If the conditions are met, this monitor will change to a critical state, which will then roll up to the "Health Service State" monitor. In the Veeam MP case, the values that trigger the monitor may result from Collector server overload. If too many VMware hosts and VMs are monitored, then the Health Service may be overwhelmed when processing the data.
Please check configuration of SCOM Agent co-located with Veeam collector, see KB1026. Make sure you don't have either of the following alerts, reference KB1765: Veeam Collector: Health Service dropped data or Veeam Collector: Health Service workflows failed If no additional alerts indicating performance issues with SCOM Agent occur, you can try increasing thresholds for 2 monitors based on current number of handles: For MonitoringHosts.exe adjust "Veeam Collector: Health Service (Monitoring Host) Handle Count threshold" For HealthService.exe adjust "Veeam Collector: Health Service Handle Count threshold" Otherwise you may consider moving VMware monitoring jobs to other Veeam Collectors or co-locating Veeam Collector with a SCOM Management Server.
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
