Not enough licenses after adding a new ESX

[KOPFteam]

Hi forum,

we have a "Standard 2 CPU sockets" license of Veeam B&R. We have 5 VMs that were running on the hosts ESX1 and ESX2 and a (nonvirtualized) vCenter on an additional Windows server. Veeam was working for many months without problem.

Now I added a new host: ESX3. I migrated all VMs from ESX1 to the new ESX3. I deleted the now empty ESX1 from the vCenter (to get the paid VMware license back) and shut it down. I removed the VMs that were on ESX1 from the Veeam jobs and readded them immediatelly (now from ESX3).

Now I get the "Task failed Error: Not enough licenses" whenever I try to run these updated jobs. "Licensed hosts" only shows ESX2 and ESX3, so Veeam knows about ESX3 and has "forgotten" about ESX1.

What can I do?

Thanks,
Florian

[veremin]

How many sockets do the two hosts together have? Thanks.

[KOPFteam]

One socket (CPU) each.
ESX2 has 1 CPU/4 Cores, ESX3 has 1 CPU/8 Cores
"Licensed hosts" shows all this correctly.

[foggy]

I recommend contacting support with this. There could be some "remnants" of the old host somewhere in the database or something...

[KOPFteam]

OK, will do. Thanks!

[KOPFteam]

Denis from Veeam support helped me to solve the problem:

Months ago I created a replica on ESX1. I deleted the job for this replica long ago, but the replica itself was still known to Veeam. And because of this the host ESX1.

After we deleted this replica Veeam "forgot" about ESX1 at all places but one: Backup Infrastructure - Managed Servers. To remove it from there, Denis had to use SQL Management Studio and delete 1 row from 3 tables in the Veeam database.

Thanks for the great support!

[foggy]

Thanks for finding time to update the thread, Florian, much appreciated.