We just got some shiny new SAN hardware that has NFSv4 enabled, which the backup proxies are attempting to use and are generating noise like so:
kernel: VFS: Lookup of 'tintri' in nfs4 0:46 would have caused loop
Rather than get into the weeds of NFSv4 I'd rather just force the proxy to v3. How can this be done?
-
- Expert
- Posts: 232
- Liked: 71 times
- Joined: Nov 07, 2016 7:39 pm
- Full Name: Mike Ely
- Contact:
Any way to force NFSv3 on Direct NFS Access?
'If you truly love Veeam, then you should not let us do this
' --Gostev, in a particularly Blazing Saddles moment

-
- Product Manager
- Posts: 15003
- Liked: 3181 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Any way to force NFSv3 on Direct NFS Access?
Hello,
I suggest to fix the root cause. There is a registry key to define per share which NFS version to use, but it's marked with "special use only" and "can crash VBR server". The key can be obtained via support, but I would not use it in production.
Best regards,
Hannes
I suggest to fix the root cause. There is a registry key to define per share which NFS version to use, but it's marked with "special use only" and "can crash VBR server". The key can be obtained via support, but I would not use it in production.
Best regards,
Hannes
-
- VP, Product Management
- Posts: 7167
- Liked: 1537 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Any way to force NFSv3 on Direct NFS Access?
I would say, let´s find out the real issue and then fix this on Veeam or storage side?
Who is online
Users browsing this forum: No registered users and 24 guests