- Veeam Support Knowledge Base
- "Failed to lock file" NFS Repository with Datadomain Storage
"Failed to lock file" NFS Repository with Datadomain Storage
| KB ID: | 1741 |
| Product: | Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 |
| Published: | 2013-03-20 |
| Last Modified: | 2025-04-23 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
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
Cause
flock() file locking with their NFS implementation and must be mounted using nolock parameter.
Solution
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.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.