Q: How the product is licensed?
A: Per physical CPU socket of "source" hypervisor host (where protected virtual machines reside). Destination hosts for replication and migration jobs do not need to be licensed. Hosts running virtual machines which are not being processed by Veeam do not need to be licensed, even if they are a part of the same cluster.
Yeah Right. You might want to update that. If not - why am I licensed per VM?.
Friday: veeam automagically updated the license on our backup server. Sweet, one less thing for me to worry about.
Saturday: Alerted by 2 backup failures from two different backup sets. Hmm, strange. Oh well it's Saturday and its my f*king day off. no big deal.
Sunday: Alerted by backup failures on the same two VM's. F*ck. My day off but that is unacceptable. This needs to be resolved now.
So fire up a management VM at home, remote in via VPN to have a look.. Open up Veeam license information and behold: "Managed VMs (vSphere) 104 (106 used)
Thats strange. When looking at the portal it says I pay for 107 VMs yet when I click "Update now" in the license information box it says I'm up to date. Woooonderful. So now i need to bother my boss because that's who the key is emailed to.