While migration from Windows Server 2012 R2 to Windows Server 2016 we have find a bug where VM with Virtual SAN on Windows Server 2012 R2 backup correctly, but after migration to Windows Server 2016 and upgrading config to 8.0 backup has been stopped with error.
We have a support request 02269654 where we tied:
1. Change snapshot type to production and try to take snapshot.
That do not worked before on Windows Server 2012 R2 because of Virtual SAN adapters, and that do not worked in Windows Server 2016 too.
2. Try to backup VM with Windows Backup.
Backup with Windows Backup worked in Windows Server 2012 R2 and worked in Windows Server 2016 too.
3.Try to turn off Guest Processing and enable Hyper-V Quiescence.
We do not use Guest Processing at all, and we can not use Hyper-V Quiescence because of our feature request not completed: microsoft-hyper-v-f25/feature-request-i ... 38197.html
After all of this support tied to say that our scenario is not supported because of:
But we do not use pass-through or in-guest iSCSI initiator. We use this: https://technet.microsoft.com/en-us/lib ... s.11).aspx.[For Microsoft Hyper-V 2016 Server VMs] Processing of VMs with pass-through virtual disks and disks connected via in-guest iSCSI initiator is not supported. Veeam Backup & Replication cannot create checkpoints for such VMs.
https://helpcenter.veeam.com/docs/backu ... tml?ver=95
Please help to understand you have stopped support of backing up VMs with vSAN or support make a wrong decision? If you stopped this support where you have write about this?