File is locked by running session

Challenge

A job or task within Veeam Backup & Replication displays the following message:

"File is locked by running session (Name of Current Job)"

Copy

Cause

When tasks run in Veeam Backup & Replication, the files accessed by those tasks are tracked within the configuration database to prevent collision. As tasks are completed, their locked file tracking entries in the configuration database are removed.

Solution

This message is expected behavior if other tasks are currently accessing the files the task is attempting to access.

For example, an offload session will display this message if the Backup Job is running, as the backup job is given priority over the offload session.

However, there are situations in which the procedures to remove tracked action entries from the configuration database may not have been processed correctly, causing files to be marked as in use by a task that is no longer running. Often, this occurs when the Veeam Server is improperly shut down or loses power. If you suspect this has happened, you should create a case with Veeam Support.

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.