Veeam on Nutanix and proxy affinity

[vNik]

Hi,
I have a general question about the proxy affinity, especially with using Nutanix as HCI.

Nutanix writes all changes locally, so the best and easy way to backup the data is to place a virtual proxy on each node and read the data where the VM is running.
Even after vMotion the new and relevant data for Veeam will be written on the node where the VM is running.

I read about the RegKey “EnableSameHostHotaddMode” to force Veeam to use the local proxy.
Exactly what I was looking for and working very well when I use the hot add virtual appliance mode.

But with Nutanix I am able to let the proxy connect to the NFS share and still read everything locally because the local node is hosting the NFS share.

When I change the settings to use DirectNFS the RegKey is ignored and the proxies are again random assigned.

Is there a way to combine local proxy affinity and the DirectNFS feature?
With Nutanix this would be an amazing feature and reduce the network traffic between the nodes a lot!

Thanks for every idea.

[vNik]

Found the answer on my own in the best practice guide.

In hyperconverged infrastructures (HCI), it is preferred to keep the datamover close the the backed up VM to avoid stressing the storage replication network with backup traffic. If the HCI is providing storage via the NFS protocol (such as Nutanix or Cisco HyperFlex), it is possible to force a Direct NFS data mover on the same host using the following registry key:

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Key: EnableSameHostDirectNFSMode
Type: REG_DWORD
Default value: 0 (disabled)
Value = 1 - when a proxy is available on the same host, Veeam Backup & Replication will leverage it. If the proxy is busy, Veeam Backup & Replication will wait for its availability; if it becomes unavailable, Veeam Backup & Replication will switch to NBD mode.

[Gostev]

Self-service at its best thanks for updating your post!

[vNik]

I implemented this feature on a customer site who is using a Nutanix infrastructure.
After a few hours of struggle to get this to work, I decided to open a support case.
After uploading a few job logs I got this answer.

I just received a confirmation from QA team that EnableSameHostDirectNFSMode option hasn't been implemented yet. It is planned for one of the future releases.
I apologize for the incorrect information in Best Practices book. I've requested to remove this option from the document until the feature will be implemented.
Unfortunately currently there is no possibility to reach the desired behavior automatically.

Looks like there is at the moment no easy option to receive the data locally with DirectNFS and VMware DRS enabled.

[jpiscaer]

That's unfortunate! I had the regkey set as well, but I clearly see multiple proxies (on different hosts) backing up a single VM.
Any timeframe when the feature will be included?

[foggy]

It is currently planned for update 3, but no specific ETA at the moment.

[lapstar]

Is there an update on this regkey or when it will be released?

[Andreas Neufert]

As foggy said, it is planned for Update 3 (ETA soon).

[blithespirit]

It was added to BP guide very recently after a request for inclusion for update 3, I will comment this out straight away until release of the update not to confuse anyone

[signal]

I have a customer on 9.5 update 3, with a Nutanix environment. I've set the registry key, but VBR doesn't seem to use the local proxy on the host, just one it has picked (at random?).

Has this been implemented in u3?

[Andreas Neufert]

Hi signal,

yes it was implemented. It should be set to 2. Please check again if it the correct type of Registry entry and start the "Veeam Backup Service" again after it.
Support can help you as well.

We are at the moment in discussion with Nutanix to support this from their side. In the meantime the Nutanix + Veeam Guide was updated recently.

[signal]

It looks like it's working now.

I had copied the setting from the Nutanix+Veeam guide, and Type was latched onto the end of Mode. This should be fixed in the guide, page 17.

[georgewkenny]

Thanks for the info @signal!

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and ReplicationKey:
EnableSameHostDirectNFSModeType: REG_DWORDValue = 1

Regards

[Luca82]

Hi everyone.... sorry for bump up this old post... but I don't understand where to put that parameter: the veeam VBR can't communicate with proxy (the veeam VBR must be added to the proxy just acting as repository repository)... but it is possible only to start the backup job from the proxy web interface....therefore there is only one proxy per cluster and I don't understand who and how chooses the closest proxy from the vm to backup.
thank you

[Gostev]

Luca, this value is for Nutanix on vSphere, not AHV. There's no similar functionality for AHV. Thanks!

[Luca82]

Luca, this value is for Nutanix on vSphere, not AHV. There's no similar functionality for AHV. Thanks!

Now everything is clear...thanks