I did have a few jobs that fails every other day with the ": Error: The process cannot access the file because it is being used by another process."-message.
Veeam Support solved the issue, but I still would like a better message in the first place. The message is of little use next day when the job has failed.
VBR knows the filname, so why not use this info to find and list the filelocking process while the lock is still active? Either by internal code or maybe calling SysInternals handle.exe wih the filename to search for?