- Veeam Support Knowledge Base
- Unable to access file [unspecified filename] since it is locked
Unable to access file [unspecified filename] since it is locked
| KB ID: | 1213 |
| Product: | Veeam Backup & Replication |
| Published: | 2011-09-13 |
| Last Modified: | 2021-07-06 |
Get weekly article updates
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
VMware holds a lock on the snapshot file while it is being consolidated. If there is an issue during this process, it is possible for further snapshots to be unable to consolidate, causing removal failures. You receive warnings that the snapshot removal process failed because '<unspecified filename>' is locked.
RemoveSnapshot failed, snapshotRef "snapshot-xxx", timeout "3600000"
Unable to access file <unspecified filename> since it is lockedCause
There are two common causes are:
- The request to have disks released from a Veeam Backup Proxy at the job run was not processed by the vSphere environment, resulting in a condition called "Stuck hotadded disks."
- The ESXi host is holding a lock on the specified snapshot.
More Information
If ESXi host file locks occurs frequently, it is advisable to check the network connection between Veeam and the source host, as well as the overall load on the source host at the time the backup typically finishes.
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.
