Problem description
In some environments, certain virtual machines (VMs) may not appear under the “All Virtual Machines” list in the Druva Phoenix Console, even though other VMs from the same vCenter are successfully discovered.
Cause
This issue typically occurs when the affected VM’s configuration file (VMX file) does not contain a valid vc.uuid entry.
The vc.uuid is a unique identifier required by Phoenix to discover and list VMs correctly. If this field is missing, the VM will not be recognized during inventory scans.
Traceback
You can confirm this issue by analyzing the Phoenix logs, specifically:
main_service.log – for Phoenix Agent version 7.0.X and below
controlservice.log – for Phoenix Agent version 7.0.X and above
Log File Locations:
Phoenix Agent version 7.0.X and below:
/var/log/PhoenixPhoenix Agent version 7.0.X and above:
/var/log/Druva/EnterpriseWorkloads/controlservice
Example Entry for Affected VM:
{"instance_uuid": "", "datacenter": "xx-datacenter", "name": "XXXX", "power_state": ...}
Note: The instance_uuid field is empty for the affected VM, indicating missing UUID metadata.
Example Entry for a Working VM:
{"instance_uuid": "52e3ba7f-900b-04e5-af16-b0b9d84e93eb", "datacenter": "xx-datacenter", "name": "YYYY", ...}
This entry confirms that a working VM has a valid UUID assigned and is discovered properly.
Resolution
Follow the steps below to resolve the issue by assigning a valid vc.uuid to the affected VM:
1. Power Off the Affected VM
Shut down the VM from the vSphere Client or vCenter console.
2. Download the VMX Files
Access the VM’s datastore via vSphere Client or ESXi host.
Download the .vmx file for:
The affected VM (not detected).
A working VM (detected successfully) for comparison.
3. Compare VMX Files
Open both .vmx files in a text editor.
In the affected VM's .vmx file, you will observe that the vc.uuid parameter is missing.
Example Missing Entry:
vc.uuid = ""
The working VM’s .vmx file will have an entry like:
vc.uuid = "52 e3 ba 7f-90 0b-04 e5-af 16-b0 b9 d8 4e 93 eb"
4. Add the vc.uuid Entry
Generate or copy a unique vc.uuid.
You can either let VMware regenerate it automatically on next power-on, or manually assign a UUID.
Add the following line to the affected VM's .vmx file:
vc.uuid = "<generated-uuid>"
5. Upload the Updated VMX File
Upload the modified .vmx file back to the original VM folder in the datastore, replacing the old file.
6. Power On the VM
Start the VM again from the vSphere Client.
7. Refresh Inventory in Druva Phoenix Console
Go to Phoenix Management Console > Protect > VMware.
Click "Refresh" or "Discover Virtual Machines" from the actions menu.
8. Verify VM Detection
The VM should now appear in the "All Virtual Machines" list in the Phoenix Console.
9. Configure Backup for the VM
Proceed to configure and assign backup policies to the newly detected VM as required.
See Also