NFS repository protocol?

[danswartz]

Apparently a linux proxy connecting to an NFS repository only uses V4? I was trying to avoid V4 because my vsphere hosts connect to the same Linux host using V3. This broke the next daily backup run though. Is this using V4 mandated? If so, why?

[Gostev]

Veeam supports NFS versions 3.0 and 4.1 (just like vSphere). Thanks!

[danswartz]

Umm, okay. I didn't remember seeing the option when I created the 2 NFS repositories. Let me check again...

[danswartz]

Okay, I just edited that NFS repository. I stepped through everything up to "Finish". I don't see anywhere to specify the NFS version. ???

[Gostev]

Veeam will automatically use the highest NFS protocal version supported by the NFS share.

[danswartz]

A couple of comments:

1. IMO it is wrong to forcibly pick the highest version. What if I don't *want* that?
2. You would seem to have a bug then. When I disabled V4 on the CentOS7 repository, the entire job failed. It was something to the effect of a write error. Sorry I didn't capture a log for it. If you need, I can repro this and provide logs?

[Gostev]

While designing this functionality, we weren't sure why would anyone NOT want to use the highest version. Nevertheless, I bet there's a registry key to force v3, just because there's a registry key for almost everything

Yes, please open a support case and share the debug logs. You don't need to reproduce again, as we archive all debug logs. Just pick the time range when this happened when exporting the support log package.

Thanks!

[danswartz]

I wasn't using V4 awhile ago (vsphere 6.5?) and V4 NFS seemed flaky, so I stuck with V3. I'm paranoid about mixing them, due to incompatible locking protocols. I understand that the repository won't be the same location as the vsphere datastore, but I didn't want to take a chance. I will open a case...

[Gostev]

I agree about NFS v4 specifically, we actually wasted a few month trying to support it... but in the end scrapped all the work, because we started to sink in all of its issues. On the other hand, v4.1 was not as problematic - big difference for a minor update!

[danswartz]

Case 04051915 opened. I reduced to a trivial backup job with 1 VM.

[danswartz]

Nothing from support so far (going on 24 hours.) Good thing I'm not down...

[danswartz]

So, per service dude: I needed to refresh the properties of the NFS-based repository. Just step through the wizard and save at the end. This really should be documented. Heck, I would argue that if it is starting at 4 and working down, an error should not be fatal (or at least indicate something to that effect...)

[Dima P.]

Dan,

Sounds right - the protocol version is detected and saved during repository creation in Veeam B&R console, so if you enable/disable the version at the NFS side, you must walk thru the wizard again to let backup server recognize this change. We will work with support and technical writers to update the manuals. Thank you for your feedback!

[DennisT]

I've been working with support on intermittent job failures and currently we're moving from using SMB to NFS. Support wants me to use NFS 3. The NAS doesn't allow me to define available NFS versions by share. The NAS allows v3 through 4.1. Veeam uses the highest available as mentioned above. So the only way to get Veaam to use v3 is to break all my active NFS connections (and deal with all the havoc that will cause) to limit it to v3, rerun the repository wizard, and then hope my systems will recover when I reenable 4.1? Since Veaam supports v3 and v4 why not just give the option when creating the repository like you can when adding a datastore in Vmware?

Sorry for the zombie revival, but this thread is appropriate for my issue.

[foggy]

There's a registry key to control NFS version for a particular repository: NfsShareVersions

https://imgur.com/zillrkL

[jeri]

Hello,

where is the RegKey? I don´t find them.

thanks

[Mildur]

Not all keys are preinstalled. You need to create it by yourself in

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

Best,
Fabian

[jeri]

what is wrong? i try also with only "4".

https://ibb.co/jyxD3s3

[Mildur]

For NFS v4.1, please use 4.1.

Code: Select all

192.168.10.37:/volume1/veeam_backup;4.1

Best,
Fabian

[jeri]

thank you. unfortunately, in veeam about the path still shows me nfs3. Or is the display not meaningful?

[Mildur]

If your NFS server supports NFS v4.1, then the backup server should already use v4.1 without the key.
Please check the supported protocols on the NFS server.

You may have to go through the repository wizard (next > next > next > finish) for the backup server to detect and connect to the new protocol version.

Best,
Fabian