This morning I realized that the Veeam backup did not run last night. And when i tried to run it again I got an error saying that the backup .vbk file was locked by a running session. (Having just rebooted the server, there should be no running job locking the .vbk file)
So I found a page describing the issue:
A few nights ago, one of our Veeam Backup jobs was hung. I tried the “Stop Job” option but seemed to have no effect. I then rebooted the backup server but found the drives for the server being backed up were still mounted to the backup server. I issued a “Retry Job” but the job came back failed with an error: “vbk is locked running session”To resolve this issue and to get the job runnable again:
- Launch the vSphere client, go to Edit Settings on the Veeam VM
Remove any hard drives that shouldn’t be there(VMDKs mounted for the job).
- Remove any orphaned snapshots on servers being backed up.
Create a manual snapshot, go into Snapshot Manager - > Delete All.
vbk is locked running session.