No, this is not the usual "Can I run free ESXi with Veeam?" question. This is a statement, and I'm wondering if anyone else has come across this.
I discovered yesterday, during a quick investigation for a colleague regarding a backup error for a particular VM on the host in question, that Veeam was managing to back up the VM (we only have one currently in the backup job) 100% completely on an ESXi host that, unbeknownst to us working with the Veeam install, was licensed with only the vSphere 5 Hypervisor license. The backup error we were looking into ended up being resolved by a specific Windows maintenance (it was an RPC error).
We are now extremely confused, as I know in v5 that this didn't work due to the lack of write access the free version has to the vStorage APIs, and yet here in v6 on this particular host in our particular environment (which is a different environment to what I had experience with v5) I am looking at a host with a free license installed and backups of a VM ON THAT HOST are completing successfully, triggered by our offsite Veeam Backup Manager installation. Veeam's support stance still states it's unsupported, but supporting it and it working are very different things.
Gostev, or anyone else who may have come across this, any ideas what the heck is going on? The only thing I can offer as a possible explanation is that the backup job was created whilst the host was in evaluation mode, then due to the amount of time it took to get the right license file the guys who were onlining that host put a free ESXi license on it temporarily (and then possibly forgot about it) which leads us to the situation I have here. I have requested if those with the rights to do so attempt a restoration of the VM to ensure the whole process worked as expected and we're not just getting false completion notifications.