First I will try to share a design of a Veeam Backup Infrastructure without Direct NFS Access backup.
Direct NFS Access backup transport mechanism is only available in Veeam v9
In above I try to design the Veeam Backup flow between iSCSI vs NFS.
In this case we did not had the proper configuration so that Direct NFS Access backup transport mechanism could work.
In this case we have a Veeam Backup Server and a Veeam Backup proxy.
Actual Veeam Backup Infrastructure:
192.100.27.x is iSCSI subnet - vLAN 56
192.128.23.x is the NFS Subnet vLAN 55
192.168.6.x(vLAN 25) is Management subnet. Used by Veeam Backup Server, vCenter and most of our ESXi hosts. But we still have some ESXi hosts that use our old management subnet 192.168.68.x
This is why we build a new Proxy with this subnet 192.68.68.x(vLAN 29)
Veeam Server I have(physical server):
1 interface(is 2 with NIC Teaming) for 192.168.6.x for Management Network.
1 Interface(also 2 with NIC Teaming) for 192.168.27.x using iSCSI initiator for the iSCSI connections.
Veeam Proxy(Virtual Machine):
1 interface with 192.168.68.x (vLAN 29) for Management Network.
This was the initial configuration and where Veeam Backup Server and Proxy never use the Direct NFS Access backup transport mechanism. All backups were running always with the option [nbd] for network block device (or network) mode, [hotadd] for virtual appliance mode.
Future Veeam Backup Infrastructure: