I've been going down the road to change from virtual proxies to a physical proxy with Direct SAN, because I'm trying to reduce/eliminate the stun issue with large active VMs when a backup finishes, such as our SQL servers that can cause a failover
In the Best Practice guide I saw this line that made me look closer at this method:https://bp.veeam.expert/resource_planni ... t_san.html
Direct Storage Access for NFS datastores will mitigate the "VM stun" issues that may be caused by Virtual Appliance Mode (hot-add).
I thought this meant it had a way to backup without a snapshot, as it is always when the snapshot is being removed that the stun occurs for us. I just ran my first test today and vCenter still placed a snapshot and removed it at the end, but there were new entries I had not seen before "Map disk region" and "Release disk lease".
What is the VM Stun issue with hot-add that was mentioned and how is it different than just a standard snapshot delete?