"Failed to lock file" NFS Repository with Datadomain Storage

A task for attempting to send backups to a Datadomain NFS share that is either added directly as an NFS Repository or mounted to a Linux intermediary server as a Linux repository fails with the error:

Processing <VM_name> Error: Input/output error
Failed to lock file [/mnt/path/to/backup.vbk].
Failed to open storage for read/write access. Storage: [/mnt/path/to/backup.vbk].
--tr:Failed to upgrade/fix the storage

NFS Repository using Linux Gateway

For NFS Repositories using a Linux gateway server, create the following registry value to configure the default NFS mount parameters that will be used with the specified NFS share.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: NfsLinuxMountOptions
Value Type: Multi-String Value (REG_MULTI_SZ)
Value Data(Default): rw,soft,timeo=600,retrans=5,intr

Notes:

• The default parameters are: rw,soft,timeo=600,retrans=5,intr
• This registry setting is a full override of the default NFS mount parameters, be mindful of the parameters you specificy (hint: include the defaults if you aren't sure).
• Each row in the multi string value is a seperate share with its own mount parameters.
  Example:
  

  10.0.0.120:/backups;rw,soft,timeo=600,retrans=5,intr,nolock
  10.0.0.121:/backups;rw,soft,timeo=600,retrans=5,intr,nolock
  10.0.0.122:/backups;rw,soft,timeo=600,retrans=5,intr,nolock
  

Linux Repository with NFS Share Mounted

For Linux repositories where the datadomain NFS share has been directly mounted, update the mount parameters in the /etc/fstab to include nolock.