Scenario 1:
Problem description
VMs are not being discovered on the Hyper-V side in the Druva Console.
Cause
The refresh job for the Hyper-V host has not yet run. By default, it runs every 24 hours, which may delay the discovery.
Resolution
A manual refresh needs to be triggered in the console to initiate the discovery job for VMs. This will ensure that VM’s are discovered in the Druva Console.
Follow the steps below to manually trigger a refresh:
Log in to the Management Console.
Select your organization from the top menu bar (if organizations are enabled). If not, proceed to the next step.
Navigate to Protect > Hyper-V in the menu.
In the left panel, click on the All Virtual Machines tab.
Click the Refresh icon (recycle symbol) next to the VM's name to trigger the refresh.
After the refresh is complete, the vms will be discovered in the console.
Scenario 2:
Problem description
Some virtual machines are missing from the “All Virtual Machines” tab in the Phoenix console.
Cause
The issue occurs when the same UUID is assigned to multiple virtual machines.
Resolution
Change the UUID of your virtual machine. Druva recommends consulting your Hyperv Admin for expert assistance.
Restart the Phoenix service on the host once the UUID is changed.
To restart the Phoenix service on your host please follow this article:
Logging, configuration files, and services for Hyper-V