Are there any "official" Veeam documentations or recommandations about how to licence correctly SQLServer STANDARD for VBR installation.
I mean, information above are interesting, but there are many, many, many subtles points in Microsoft licences model. If you have ever known an audit driven by Microsoft, you will know what I'm talking about...
According to the above MS documentation, it's rather clear that using "SERVER+CAL" model will impose :
=> a SQLServer licence for each OS hosting a SQLserver componant (I would say, at least one for the Veeam BR server itself if it hosts the SQLserver instance)
=> a user CAL (or a device CAL) for each administrator accessing the console.
=> For a "veeam Agent for windows", installed on a workstation or physical server : SQLServer CAL required ? (I'd say yes, because the agent goes to SQL indirectly, and he's iniating the connection to the Veeam Server).
=> For a vSphere environnement, backed up by Veeam, composed a several physical hosts and VMs : SQLServer CAL required ? (I'd say no, because vSphere and all hosts are passively accessed by Veeam, without any agent). But is it true from a Microsoft point of view ?
=> For the Veeam Enterprise Manager client component installed on the same server as the one used for SQLserver and VBR Server Components : SQLServer CAL required (i'd say no, because the server itself is already covered by a SQLServer Server licence).
So, could Veeam be able to formalize it (if it's not already done... of course...) ?
and Happy New Year !