The process cannot access the file because it is being used by another process

A job or task fails with the error:

The process cannot access the file because it is being used by another process.

Indicating that a file is locked by another process/task. The console may indicate specifically what file is locked. Identification of the process that is locking the file(s) must take place.

Example:

Linux File Lock Investigation

To determine file locks on a Linux repository, you can use various utilities. This section will focus on using lslocks, but keep in mind that there may be other distribution-specific tools and methods available. It's important to distinguish between locked and opened files, as a file can be locked without being actively opened. The lsof command, for example, only lists actively opened files.

• lslocks — Displays a list of active file locks. (Requires util-linux package)
• lsof — Displays a list of actively open files. Specifying a particular file will show active processes for that file.
  

  lsof “/path/to/file”
  

Alternatively /proc/locks can be manually investigated using the following command:

sudo find -L /proc/*/fd -maxdepth 1 -print -exec readlink {} \;

Regardless of the method used, you must verify that the file is not actively being modified. File locks can come from various sources. For example, if a job is unexpectedly terminated due to a network drop, it is possible 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 you have 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. However, be cautious, as killing a process that is modifying a file may result in a corrupted file.