VM chargeback report bug with multiple datastores

[ic_mcourtney]

I've come across what seems to be a bug with the Veeam ONE VM Chargeback reporting.

When a VM has vDisks spread across multiple datastores, Veeam ONE seems to incorrectly report the vCPU and vRAM count.

In the screenshot shown below the VM is configured with 2x vCPUs and 12GB of vRAM, it also has 6x vDisks each of which are stored on different datastores.
I would expect Veeam ONE to report the VM having 2x vCPUs and 12GB of vRAM, but instead it reports 12x vCPUs and 72GB of vRAM.



I've raised support case 02452007 with Veeam Support, but I'm curious to know if anyone else has observed the same behaviour in their environment?

[Mike Resseler]

Hi Matty,
I haven't come across it but in my environment I have no such setup. Thanks for posting the case. If it is indeed a bug we will try to fix it as soon as possible. Please keep us informed about your case ID and the outcome with the support engineers

Thanks
Mike

[Shestakov]

Hi Matty,
That looks like a bug, I've not heard of before.
Indeed there should be only one row with 2 vCPUs, 12 GB of RAM and summed Datastore price.
Thanks for pointing it out.

[ic_mcourtney]

Hi Shestakov,

What are the chances of a hotfix? It’s quite an issue for us, and waiting until U4 for a fix would be a challenge.

Regards,

Matty

[Shestakov]

Chances are pretty good, I believe we will not make yoo wait for the next release.
Once the bug is confirmed, R&D make fix and provide it through the support team, so please keep working with them.
Thanks!

[Vitaliy S.]

The easiest way to get a fix is ask for it (via existing support ticket)

[ic_mcourtney]

I’m still waiting for support to confirm the bug

[Shestakov]

There are public holidays in some countries where Veeam ONE support is present, so it may take a bit longer than usual.
Thanks for understanding.