NFSv3 vmkPortBinding in v8u1 and Veeam Instant Recovery

[Desiderat]

Hi,

I have a question. We're in the middle of a migration to vSphere v8. In vSphere 8 Update 1 (as mentioned in this VMware resource https://core.vmware.com/resource/whats- ... 26105-sub3), the NFSv3 vmkPortBinding was updated. From what I understand, VMware removed the default ability to bind NFS to a specific vmk port, making it an option when mounting the NFS datastore.

In our environment, we use 1G NICs for management and 25G NICs for data, storage, vMotion, and NFS. Based on this update, it seems that NFS traffic will, by default, use the 1G NICs unless we configure the binding during datastore mounting.

So, my question is: Am I correct in assuming that this change could slow down all Instant Recovery jobs, given that Veeam’s GUI doesn't provide the option to select the vmk port for binding? Or am I missing something?

[Mildur]

Hello Oleh

We are aware of this change of vSphere 8 U1 and that we probably have to make some updates to our mapping process.

The datastore stays mapped after the instant recovery session has finished. Have you tried to change the "Vmknic binding option" for the Veeam datastore before starting another Instant Recovery session? Or is the option greyed out?

Best,
Fabian

[Desiderat]

Hello Fabian,
It looks like I don't have any option to change the binding. The vCenter shows that datastore vmknic binding is None and there are no possibilities to change that.