Loading...
Loading...
The Hyper-V topology is discovered correctly, however, the Display Names of Virtual Machines are listed as their VM IDs. Example:
The issue is caused by "ghost" roles for the affected VMs on the Failover Cluster Manager server or the VMM server. When the Veeam Management Pack for Microsoft System Center script discovers the VM names, it checks the VM list in the registry of the Cluster Manager or the VMM server at HKEY_LOCAL_MACHINE\Cluster\Resources The behavior may manifest itself if a VM has been manually removed from inventory. By design, Hyper-V should be updating the registry appropriately, however, if this does not happen, the "ghost" VM has no VmID under "Parameters". Here are two examples of invalid configuration: Invalid Example #1 [HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4] "Name"="Name of VM Configuration" "Type"="Virtual Machine Configuration" "SeparateMonitor"=dword:00000000 [HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4\Parameters] "DependsOnSharedVolumes"=hex(7):61,00,62,00,63,00,33,00,36,00,33,00,32,00,63,\ 00,2d,00,37,00,36,00,36,00,66,00,2d,00,34,00,38,00,61,00,62,00,2d,00,39,00,\ 36,00,61,00,36,00,2d,00,37,00,35,00,62,00,61,00,63,00,65,00,63,00,65,00,34,\ 00,63,00,32,00,38,00,00,00,00,00 Invalid Example #2 [HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f] "Name"="{vmname}" "Type"="Virtual Machine" "SeparateMonitor"=dword:00000000 [HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f\Parameters]
The workaround is to remove the Virtual Machines with missing VmID from the registry of the Failover Cluster Manager or the VMM server. Note: This workaround may cause failover to no longer work for the VMs removed from the registry.
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.