Backup locked by another application

[slugman]

Hi,

One of our backups failed with the following error:

Cannot process the VM because the target VM state is "Restore"

I understand this can be caused by a restore not completing correctly - this makes sense, as I think exactly this happened here the other day.

I found another couple of postings here which suggested running the File Level Restore Wizard for that VM and making sure it's closed properly to reset the state. Unfortunately when I go to select the VM with the problem, I receive an error saying:

Unable to access the backup file because it is locked by another application.

I don't receive the error on any of the other VMs.

Any ideas?

Thanks!

Ben

[Gostev]

Ben, rebooting the Veeam Backup server should help to remove the backup file lock. After this, you should be able to open/close FLR wizard for this VM and reset the VM state. If it does not help for some reason, please contact our support for assistance. Thank you.

[slugman]

Thanks Gostev,

Unfortunately rebooting the Backup server didn't remove the lock - I'll submit a call to support and update the forum with the outcome.

Ben

[slugman]

FYI the support team provided us with a SQL script to reset the job status - this worked perfectly and seems to have successfully removed the lock.

Many thanks for your help,

Ben

[Luckas]

Hi Ben,

i have the same problem with one vm.
Can you please send me the sql script for fixing this?

best+
Helmut

me again,

problem is fixed with an answer of antother posting: Open and close restore window works fine for me.

Thanks

Helmut

[Vitaliy S.]

Helmut,

Good to hear that you've troubleshooted the issue with yourself, however do not hesitate in future writing to support@veeam.com if you have any issues more. (for ex. if you need that SQL script)

[kmccubbin]

Hi. I know this is an old issue and the "Open and Close" solution does work to clear it up, but has anyone found a way to prevent the problem in the first place? With File-Level Restores it seems to happen more often than not and I come in in the morning to find failed backups because of it.
It's not a huge deal, really, since redoing the backups are so quick, but I was wondering if anyone had any tips on how to avoid it to start with?

[Gostev]

Hi Kelly, what Veeam Backup version are you using?

[kmccubbin]

Hi Gostev,
4.1.1

[Gostev]

I think it would be best for you to open a case with our support to let us investigate particular occasions and find the reason for this behavior... this is definitely not an issue you are expected to encounter with v4, in fact, this is the first time I see this issue reported on forums in a very long time. It was pretty common issue with previous releases, but it was (supposedly) addressed in 4.0 (and I thought it is).