In reviewing the Veeam v6.5 Release notes, I noted that in the "Known Issues" section, under "Hyper-V" the following items appears:
Changed block tracking is not supported for virtual disks residing on SMB3 High Availability shares. Microsoft recommends using Scale Out shares for hosting virtual machines
I am not sure what this means for my planned usage:
We have a Windows 2012 Hyper-V cluster which has 2 nodes, which uses SMB 3 based storage on another Windows 2012 File Storage cluster, via Chelsio 10Gbe RDMA NICs.
We are planning to use v6.5 to perform backup/replicas of the VMs.
The way I read this, the CBT functionality will not work. Have I read this correctly?
If so, I don't quite understand why CBT isn't supported, MS claims that VSS is supported by SMB 3 shares.
In order to use the CBT for VMs residing on SMB3 shares you have to manually add this SMB3 server/cluster to the VB&R console. Otherwise, it won’t work.
In the way I see it, after having added your Windows 2012 File Storage to the VB&R console there shouldn’t be any issues related to CBT, unless you’re using Cluster Disks.
For more information please see corresponding User Guide.