Counts all CPU sockets on a physical Hypervisor host based on the last successful backup (full or synthetic full) of a virtual machine residing in the host.

https://documentation.commvault.com/commvault/v11_sp20/article?p=40124.htm

Explains why we see old and new IPs, since not every VM has had a Full Backup after the IP change.

Hence my question if it is possible to clean up the old entries? Because waiting for all VMs would mean 5 additional days with the current license error.

Regards
Mario

Not that I`m aware. My understanding is that VM sockets on a physical hypervisor is based on the last successful full or synthetic full. If you do not run that, your report will still show the old hosts as "valids".

Hey @Mario Weise .  I’m not aware of any way to force things (some Licensing is impacted when Data Aging is run, but I don’t think sockets are impacted).

Are you seeing any operations impacted or is it just an error?

I’ll look into this to see if we have any forcing mechanism just in case.

Thanks!

Backups are running, with the end customer resetting the usage warning in the license dialog of the console.Hopefully this helps until next wednesday, when all fulls finished.

Ok, so you are having to hit the rest button.  That’s definitely a concern (at the least an inconvenience, but more than that).

I’ll let you know if I discover any method to speed that up.

Not sure about the situation but inc + synthetic full could be a faster way?

That’s some clever thinking!

@Mario Weise , this could be a simpler method that won’t inhibit the clients at all.

Thanks for the feedback. Will discuss this with the end customer.

Great!  I also confirmed that we can’t force the check...the Full is the check.  The license checked the last full backup to see what esx hosts are in use and applies accordingly.