Hyper-V Failover Clustering and Nic Teaming - Target Storage is SMB3

All,

I'm Using a 8024F pair in Stack mode with 2 hyper-v Hosts that connect to a SMB3 Storage for hosts:

Switch config is the following on each Server:

Hyper-v1: Dual 10GB card (Nic Team LACP/Hyperv Port)
Hyper-v2: Dual 10GB card (Nic Team LACP/Hyperv Port)
Storage Node: Dual 10GB card (Nic Team LACP/Address Hash)

Channel-group for each is Mode Active (Hashing-Mode 3, which seems to be default when active is enabled)

The hashing-mode options are:

<1-7> Enter LAG hashing mode.
1 - Src MAC, VLAN, EtherType, Src module and portId.
2 - Dest MAC, VLAN, EtherType, Src module and portId.
3 - Src IP and Src TCP/UDP port.
4 - Dest IP and dest TCP/UDP port.
5 - Src/Dest MAC, VLAN, EtherType, Src MODID/port.
6 - Src/Dest IP and Src/Dest TCP/UDP port.
7 - Enhanced hashing mode.

From all the research I've done it isn't clear which mode is best used for this , however, allot of what i read does point to "6 - Src/Dest IP and Src/Dest TCP/UDP port." option. to be used.

So If anyone has experience with this I'd love to hear from you, and or suggestions.

So my current issue is thi:

When my Veeam runs all machines on that host lose connection to SMB during the VSS attempt and they immediately shutdown. As you can see this is a critical issue occurring and its affecting multiple fronts.