Get-VBRBackup cmdlet returns incorrect VmCount

[ic_mcourtney]

When using Get-VBRBackup to query backup jobs, the cmdlet seems to report an incorrect VmCount for any vCloud backup jobs (VMware backup jobs are reported correctly).
For vCloud jobs, the cmdlet returns a value in the VmCount property that includes the number of VMs and the number of vApps in the job.
This does not seem to align to the way VBR tracks license usage -- VMs are the metric counted, and vApps are ignored.

This may be the root cause of a problem we've observed with Veeam ONE Reporter's 'Backup Billing' report, which seems to return the same values as the Get-VBRBackup cmdlet (see this post for more details about that issue). This is problematic for us as we need an accurate count of VMs per backup job for chargeback purposes.

[ic_mcourtney]

Veeam Support have confirmed this as a bug that will be resolved in the next B&R update.