I'm testing in a 100% Windows Server 2012 R2 environment.It''s a 2 node Hyper-V cluster, the cluster also hosts the Backup & Replication VM. It also host an SMB3 file share that is clusterd and leverages transparent failover. This file share is used for a backup repository. I run a backup job and while data is being copied I failover the file share. If VEAAM leverages SMB 3.0 for the backup target repository it could survice such a failover. However it fails. So the question is does VEEAM leverage SMB3 to the repository or not? If yes, I'm not doing something right, if not, consider it a feature request . If this would be impossible, could you explain why?
Thank you. But I think that's for virtual machines living on the SMB 3.0 share, a backup source. I'm talking about adding a file share as backup repository but instead of an "ordinary" file share an SMB transparent failover one. That means it's clusterd share and client running SMB 3.0X can survive a failover. If VEEAM leverages SMB 3.0 for that I was thinking we could leverage that, so I was experimenting in backing up to that SMB transparent failover share to see what happens.
If you have your backup infrastructure running on SMB3 capable Windows OS, then Veeam "should be using" SMB3. I have quoted that because our data movers are running on top of Windows OS and use standard file I/O API, and I believe Windows selects SMB3 protocol automatically if both OS and share supports it. Just as if you would initiate transfer from Windows Explorer (you never get to pick SMB protocol version there either, it just works).
. If this would be impossible, could you explain why?