Problem Description
Administrators observe duplicate entries for the same Virtual Machine (VM) in the "Storage consumption by backupset" report. While the VM names are identical (e.g., Cisco-vISE), each entry displays a different value for the "Current Source size".
Cause
This issue is caused by the same Virtual Machine being registered and configured for backup from multiple sources within the VMware environment. The report generates a separate entry for each unique discovery source (e.g., vCenter, standalone ESXi host) from which the VM is managed.
For example, a single VM may be configured for backup independently from:
A vCenter server (e.g.,vcenter.abc.org)
A standalone ESXi host (e.g., 10.0.0.101)
Another standalone ESXi host (e.g., 10.0.0.103)
Because the VM is "seen" by Druva from three different management sources, the report lists it three times. Each entry reflects the VM's properties as reported by that specific source, which can result in different "Current Source size" values.
Resolution
There are two approaches to address this: consolidating the configuration (Best Practice) or using Administrative Groups to differentiate the entries (Workaround).
Primary Resolution (Best Practice)
The recommended solution is to consolidate the VM's backup configuration under a single management source.
Identify all sources (vCenters and standalone ESXi hosts) from which the duplicate VM is being configured.
Decommission the VM backup configuration from the standalone ESXi hosts (e.g., 10.0.0.101 and 10.0.0.103).
Ensure the VM remains configured for backup only once through the primary vCenter server (e.g., vcenter.abc.org).
This aligns the reporting with the intended single-management-source structure and will prevent future duplicate entries.
Workaround (Differentiation)
If you must maintain separate configurations for business reasons, you can use Administrative Groups to distinguish the entries in the report.
In the Druva console, locate the different instances of the VM (one from vCenter, others from ESXi hosts).
Assign each VM instance to a unique Administrative Group (e.g., "vCenter VMs" vs. "ESXi-101 VMs").
The "Storage consumption by backupset" report includes the Administrative Group name, which can then be used to clearly identify which entry corresponds to which source.
Verification
After applying the Primary Resolution (consolidating the configuration), allow time for at least one new backup cycle and for the reporting data to refresh.
Generate a new "Storage consumption by backupset" report.
Verify that the Virtual Machine (e.g., Cisco-vISE-600-3.3.0.430-r) now appears only once in the report.
If you used the Administrative Group workaround, verify that the report now correctly displays the different group names next to each duplicate entry, allowing for clear identification.