- Veeam Support Knowledge Base
- File is locked by running session
File is locked by running session
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
"File is locked by running session (Name of Current Job)"Cause
When tasks are running in Veeam Backup & Replication, the files being 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 other tasks are currently accessing the files that 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 was improperly shutdown or lost power. If you suspect that this has happened, you are advised to create a case with Veeam Support.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.