Skip to main content

NFS Repository Performance Revisited: Hidden NFS Mount Tuning in Veeam

  • September 24, 2026
  • 3 comments
  • 68 views

Marcel.K
Forum|alt.badge.img+13

When I published my previous article about NFS repository performance, one of the key observations was that NFS mounts could become a bottleneck due to a limited number of network connections being used between the backup infrastructure and the storage system.

At the time, a common recommendation was to manually tune Linux NFS mount options, especially the nconnect parameter, to improve throughput.

Recently, I discovered an interesting configuration option within Veeam Backup & Replication that deserves attention.

 

A Hidden Registry Setting

Veeam appears to support custom NFS mount parameters through the following registry value:

 

Key:

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

Value Name:

NfsLinuxMountOptions

Type:

REG_MULTI_SZ

 

Example: nconnect=300

 

When configured, the resulting mount may look similar to:

172.0.0.30:/data /mnt/repository nfs rw,soft,vers=4.1,nconnect=300

 

 

Now all Linux Gateway Servers will use this option ….

 

3 comments

MatzeB
Forum|alt.badge.img+7
  • Veeam Vanguard
  • September 24, 2026

Interessting - i know nconnect from connecting VMware NFS Datastores to NetApp NFS3 for example. But we go with nconnect 4-16 typically…..is 300 really a good idea?

Matze


Marcel.K
Forum|alt.badge.img+13
  • Author
  • Veeam Legend
  • September 24, 2026

Hi ​@MatzeB 

this is like limit for gateway as nfs client

if you use same gateway for several nfs repositories, then value 300 is like top limit and is keeping gateway to use so many connections as storage allows.

Storage will allow 16 connections, then only 16 connection could be used by gateway.


MatzeB
Forum|alt.badge.img+7
  • Veeam Vanguard
  • September 24, 2026

thx! makes sense - need to try this :)