Veeam MP for Hyper-V Discovery

The Veeam MP for Hyper-V uses cascaded discovery methods to populate OpsMgr with Hyper-V objects. These discoveries use scripts and custom time-based datasources.

How Hyper-V Objects are Discovered

The discovery process is performed as follows:

  1. After you import Veeam MP for Hyper-Vs, the Veeam Base Discovery management pack is deployed on all OpsMgr agents. This pack discovers servers with the Hyper-V role.

Note that this initial discovery consists of hidden objects, not visible in default OpsMgr views.

  1. Hyper-V Hosts and Clusters discovered as above will first appear under the Discovered Hyper-V Servers tree on the Hyper-V Servers tab in the Veeam UI. All hosts will be checked (monitoring enabled) by default, if sufficient Veeam licenses are available.

The Veeam Extensions Service will scan OpsMgr through the SDK to add newly discovered hosts once per hour.

  1. When the host has appeared in the Veeam UI and is checked, then additional topology discovery scripts running on the host will populate Veeam MP views with clusters, hosts, virtual machines, virtual network switches, storage disks and volumes, and so on.

The additional discovery stage can take between 1 – 3 hours.

If you experience a delay in discovery of hosts, VMs or other components, a restart of the OpsMgr service on Hyper-V hosts will force initial discovery:

  • In OpsMgr 2016 and later, restart Microsoft Monitoring Agent Service

For details, see section Troubleshooting on Hyper-V hosts not discovered in OpsMgr.

After discovery is completed, monitors and rules will be loaded and dashboards and reports will begin to populate. Note that some views will require additional time to initialize, for details see section Troubleshooting on Veeam MP views or dashboards are empty.

Using the Veeam UI, you can enable and disable monitoring for specific hosts, check and update license, and discover new Hyper-V hosts. For details, see Veeam UI.

All Hyper-V object discoveries are enabled by default. You can use overrides to disable or change discovery settings. For the list of discovery rules and their default configuration, see Appendix B.