Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
There are a few utilities that can show File Locks. Pre-installed is Resource Monitor.
In this example, there is a PID for the VeeamAgent process, meaning Veeam has a lock on this file. The agent responsible for this lock can be confirmed in logging, or with the assistance of support. The PID of a given agent exists at the beginning of any source or target agent log. In the case of file locks, the target agent log should be examined.
< 23740> Windows agent.
< 23740> Path to the executable module: C:\Program Files (x86)\Veeam\Backup Transport\x64\VeeamAgent.exe
< 23740> Agent version: 9.5.0.1536
< 23740> Installed memory, MB: 8191
< 23740> PID: 18232
There are utilities that can be used to determine File Locks on a Linux repository, and this section will cover the usage of lslocks. However, there may be other distribution-specific utilities and methods. It is critical to differentiate between Locked and Opened files. It is possible for a file to be in a locked state but not be actively opened. A command like lsof will only list actively opened files.
lsof “\path\to\file”
Manually investigating /proc/locks can also be done like so:
sudo find -L /proc/*/fd -maxdepth 1 -print -exec readlink {} \;
In either scenario, one must verify that the file is not actively modified. File Locks can come from a variety of sources. If a job is unexpectedly terminated due to a network drop, it is plausible that the Veeam Agent finished but never received a terminate command. If the repository uses deduplication, the storage may have too aggressive of a profile active and is locking the file(s) as soon as Veeam releases a lock on them.
Once verified that the locked file is no longer being modified, it is safe to manually kill any process still maintaining a lock on the file.
Killing a process that is modifying a file may result in a corrupted file.
Your feedback has been received and will be reviewed.
Please try again later.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.