Thanks for clarifying that confusing.
Now per https://helpcenter.veeam.com/backup/vsphere/storage_setup.html
1) Can I use the default Backup Proxy which is the Veeam server itself?
2) Done, I connected my vCenter server to Veeam from day one.
3) Only applicable to HP Storage server (Clicking on the link to step 4 confirms the support of the VNXe)
4) Step 4 adding storage server, now it checks for existing snapshots, from what I've checked it appears my VNXe already has a scheduled snapshot defined.
So now I'm assuming the following.
1) is a yes, so keep going.
4) Configure my current Veeam AD account that already has admin rights to vCenter, provide that account admin permissions to the VNXe (Since I configured AD auth on the VNXe already) I can then use the already stored Veeam account thats on Veeam in the Add Storage Wizard for step 4 (add admin creds for the storage unit).
Let Veeam scan the existing setup (Will it detect just my NFS datastores or my iSCSI(VMFS) datastores as well?) including existing snapshots.
At this point I'd assume I could just edit the default proxy and choose Direct NFS as its transport mode, at this point since the Veeam server is a VM in the cluster with a leg in the SAN network it would use this leg to read the storage snapshot, then write to the iSCSI based volume thats on my other SAN. I'm hoping since the two end connections would be two different IPS I'd hope that the bonded NICs would actually both be used, in the case full 1 gbps read from the VNXe (nic 1 lets say) and a full 1 gbps up (to the iSCSI based other SAN this VM has for a direct volume.)
Am I correct in this assumption?