Plugin all of a sudden consuming license - though VM is part of socket license

Thanks, @JMeixner. No, still 12.0.

We found the root cause for the issue. 😅

Actually it even relates to something @vNote42 has already shared earlier: [Quicktip] Licensing error during backup | Veeam Community Resource Hub - but now for plugin jobs.

What happened in our case was:

• Service account PW used by Veeam to access vCenter was changed three (!) days earlier and was updated within VBR, but seemingly with a typo in the PW. A domain account is being used here.
• For two more days the kerberos ticket that Veeam used to access vCenter stayed valid - even with the now wrong PW inside VBRs database. So the timb bomb is ticking.
• On Friday around 10:30 the kerberos ticket on VBR had to be renewed, which failed because of the wrong PW.
• From now on VBR was no longer able to proof that the HANA plugins are living on already license wise covered VMs and started to require a license. So they failed, as there are no VULs available for them.

Of course all VM backups would also have failed in their next run.

But funnily enough the first jobs to fail are the ones that have no obvious correlation with the account using the wrong PW. This made troubleshooting kind of a challenge.

My take-away is: always check your vCenter creds once you face the above error.

Very interesting.

We had the “problem” with the expired password once, too. But the plugins didn't failt with this licensing error.

Good to know 😎👍🏼