Direct NFS Question

[isaako]

Hi,

I'm planning Direct NFS deployment and I've a question regarding NFS ip's.
How the VM proxy knows the needed ip address to mount the NFS datastore?
The VM proxy needs an ip address in the same network as ESXi to access NFS?

Thanks.

[widmerkarl]

Hi Isaac,

I recently did this at a customer.

There we have some ESXi hosts and a shared NetApp storage. The Veeam backup server is a physical server with his own local repository.

The server has four NIC ports. At the moment i connected one NIC port to the NFS network and gave it a manual IP in this network (because there is NO DHCP). That worked fine.

I have to investigate and troubleshoot the NIC teaming and / or LACP trunking on the NFS switch, because the LACP trunk does not work. Without trunk the connection worked, but only with 1GBit (instead of 2GBit).

[isaako]

I mean that the NFS network must be same that ESXI NFS network.
My idea is to create a separately network for Veeam NFS access but I don't know how the native veeam NFS client retrieves de NFS server address.

[ferrus]

I did something very similar a couple of months ago.
Our Veeam servers are on a different subnet to the ESXi mgmt traffic, so I created a new network using unused NICs on the Veeam servers, and NFS vmkernel ports on each ESXi server.
At first all the traffic tried to go through the standard Veeam server LAN connection, until I read this thread:

vmware-vsphere-f24/how-to-use-veeam-vpo ... 42-15.html

The Veeam repositories have to be setup as static NFS datastores on the ESXi servers, then the traffic will go through the correct NICs.
I had to add the registry entry mentioned later in the thread manually to each Veeam server.

NFS performance is still an issue for us, but that may be related to other factors.

[ferrus]

Better presented in this KB article (+ registry key, from above)

https://www.veeam.com/kb1284