VUL Migration to much VM into the logfile

[prubner]

Hello everyone,
I have a question regarding license migration to VUL.
The VM.log file is used to determine the required licenses.
However, for various customers, the log file now contains significantly more resources than the customer actually uses.
For example, in the log file, 154 VMs are listed, but only 13 are used, or 342 VMs are listed, but only 190 are used.
Where do these differences come from? So, the customer is then offered 350 VULs, although they only need 190.
Peter

[d.artzen]

Without knowing the infrastructure, could it be that the costumer has that many templates? If I recall correctly, Templates are also seen as a workload, so would consume a VUL.

[petesteven]

This sounds familiar, and I recently had the same issue with one of my customers.
Due to changes in the data center (new hosts, new vCenter), the customer has registered their VMs with new IDs on the new vCenter. After that, their VULs were of course fully utilized at first.
So they used the “Revoke” function. After that, everything worked again and you can only see the newly used VULs in the console, but the VME.log below doesn't match.
Could this be something similar?

[prubner]

I think that's the same behavior. But how can we get the VBR server to update the database? The VM.log is created from the DB information. Is this a Veeam bug?

[Gostev]

This log is 10+ years old functionality so it's extremely unlikely to have bugs. Do you have a support case number or something?

So, the customer is then offered 350 VULs, although they only need 190

Why would they not take a 350VM license though if offered, what exactly is the drawback? The more VULs you can get the better, no? What if they need to protect these other VMs later?