Working with a customer that has a 4x SQL servers running as VMs on a single 2016 host. They have set up symlinks on the SQL VMs to point to storage on the physical host. So the D: drive on the SQL1 VM has a folder called data that points to \\host\sqldata\sql1\data, and d:\logs on the host points to \\host\sqldata\sql1\logs\. Same thing on SQL2, SQL3, and SQL4. There is another host with another 3 or 4 SQL VMs doing the exact same thing. Veeam only backs up the data actually in the VHDX, and not referenced through the symlink - as expected.
Want to unravel this mess and get these VMs properly backing up with Veeam like the rest of the VMs on the hosts. Was looking at a shared VHD, but see that Veeam doesn't support that, but rather to use VHD Sets. There is no clustering and probably won't be. Can I set up clustered storage even though it obviously won't be clustered with a single host? When I try and add a VHD Set to a VM, I get the error
The storage where the virtual hard disk is located does not support virtual hard disk sharing.
I assume that is because the VHD is not in c:\clusterstorage\
Putting a VHD for each VM with the data, logs, and backups doesn't appear to be an option. Customer is concerned they won't carve up the space correctly, give too much space to one machine, not enough to another, run out of space on one, etc. Shared storage or complicating the topology with a virtual SAN is more than likely out of the picture.
Open to other suggestions or even someone telling me I'm wasting my time.
