OPERATIONAL DEFECT DATABASE
...
...
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.
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.
Review the Following articles: Veeam - Removing Stuck VMDK’s from the Veeam Proxy VMware - Failed to lock the file or One or more disks are busy deleting vm snapshots (2017072) VMware - Investigating virtual machine file locks on ESXi hosts (10051)
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.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
