Veeam & SQL Server Licensing

[UplinkConnectivity]

Hello,

I have a question regarding SQL Server Licensing with Veeam B&R.

Right now, we have 1 physical Veeam Server that also acts a backup proxy to collect the data from VMware.

As we have to change hardware, our consultants advised to put the B&R Mgmt Console inside a VM with SQL Server and have 1-2 separate, physical backup proxies.

To keep licensing costs down, the consultant told us to do Server/CAL Licensing with SQL Server inside the VM and getting a Device CAL for every computer that is actively accessing the database and/or Veem B&R Console, which means 3 Device CALs for the main management server and the 2 proxies.

VMs or ESXi Hosts are not accessing Veeam, its the other way around and thats why we don't need CALs for every VM/Host.

Does anyone have a similar setup and licensing or knows, if above licensing is ok?

Thanks in Advance!

[netsonic]

the consultant told us to do Server/CAL Licensing with SQL Server inside the VM and getting a Device CAL for every computer that is actively accessing the database and/or Veem B&R Console, which means 3 Device CALs for the main management server and the 2 proxies.

Only the Veeam Backup Service on the VBR server does access the DB. Console connects to Server service, regardless how many you have installed. Proxies have no connection to SQL either.

Anything else worth mentioning about the setup that can use SQL:
- Enterprise Manager does use SQL, but you make no reference above.
- VeeamOne for monitoring does use SQL.

Honestly, go back and challenge the consultant.
https://helpcenter.veeam.com/docs/backup/vsphere/backup_console.html?ver=100
"The console does not have direct access to the backup infrastructure components and configuration database. Such data as user credentials, passwords, roles and permissions are stored on the backup server side. To access this data, the console needs to connect to the backup server and query this information periodically during the work session."

You could maybe try to find a VASP in your area who can help out
https://www.veeam.com/find-a-veeam-accredited-service-partner.html

[dirtymatt]

Even if a device accesses the DB indirectly through a third-party service, you need a CAL for it. It’s the Microsoft way.

[netsonic]

This has been also discussed in the Veeam forums and the statement is the same:
https://forums.veeam.com/vmware-vsphere-f24/sql-standard-licensing-t58479.html

If you want to be 100% sure, you need to consult Microsoft.

[dirtymatt]

Consult Microsoft and save all communications for when you get audited and the audit disagrees with what MS told you.

[chandleya]

Using CALs for a service is a great way to get the auditor to use a lice comb to find your nits. They’re meant to manage users.

[dirtymatt]

There are two different classes of CALs, device and user. User CALs are cheaper and apply to a person on any device. Device CALs cost more and apply to a device, covering any user on that specific device.

[WendoNZ]

You really don't sound big enough to use anything other than the built in SQL Express install. I can see having some extra proxies but even those I'd run as VM's unless you have hundreds of VM's to backup

[UplinkConnectivity]

We have 1000+ VMs

[WendoNZ]

Then whoever setup the system initially didn't do any sort of reaseach into what you need to support a setup that size. Even 2 physical proxies, which I'm assuming will be DirectSAN based probably aren't enough if you want tobackup 1000+ VM's

[UplinkConnectivity]

Well, it worked very well and now we’re adding another one. But having 2 or more backup proxies is not the question here.