Screwed up with VAW license after test P2V

[Shunx239]

We were testing P2V conversion of VAW protected Windows 2012R2 server.

We have used the Instant recovery and finalised it on extra ESXi host not licensed for VBR backup.

It was a test recovery that we intended to run again after performing additional incremental backup in production.

Suddenly we are not able to perform that additional backup because the host is considered VM now and reguires a socket license for Agent backup:

[AM] Failed to start agent licensing. Licensed agent Id: 593bb5b2-9818-4975-92c8-236062718e45. Platform: 11d0870b-566f-46ce-a190-e65a4ae39f09. Mode: Server
Unable to process the VM: your socket license has been exceeded. Install an extended license, or migrate protected VMs to the licensed hosts. (Veeam.Backup.Common.CLicenseCommonException)

[Dima P.]

Hello Nikolay,

If license was accidentally consumed while you were testing some functionality you can revoke the license from such host via license tab in B&R UI. Thank you!

[Shunx239]

Hello Dima thank you but it is different.

B&R thinks the VAW workload to be VM and asks for a socket license that is not available.

[Shunx239]

Luckily we had another (licensed) host to run instant recovery again.
This time I noticed the advanced option to keep BIOS UUID, supposed to be irrilevant for P2V, but not from the Veaam viewpoint!

This way we persuaded B&R to allow for further backup on this workload.

All this stuff because of oltrageous decision of Veeam to pretend socket license for VAW backup on VM, even if instance license is available.
Frankly speaking i was unaware of this before this incident

[Dima P.]

Hello Nikolay,

This behavior is unexpected. Please raise a support case and share the case ID as we need debug logs to understand the root cause of such issue. Thank you!

[Mildur]

Hi all

It‘s expected behavior that all Workloads have to be licensed by a socket license when there is a socket license present on the backup server.

@Shunx239
Remove the hypervisor from the inventory menu, and your agent backup will consume licenses like a physical machine (instances).
As long as the hypervisor is added to the inventory pane, a socket license will be requested for any type of backup job (vm, agent, plugin) on this hypervisor machine.

Source: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Under the merged license, the following workloads will consume a Socket license:

- VMware vSphere and Microsoft Hyper-V VMs

- Application servers protected by Veeam Plug-ins (only for application servers running in VMs of a virtual infrastructure registered with Veeam Backup & Replication)

- VMs protected by Veeam Agents (only for VMs of a virtual infrastructure registered with Veeam Backup & Replication)

Best,
Fabian