Hyper-V VM backup locked by another task or snapshot group?

[enoch]

Hi all,

On a few VM's on Hyper-V I get the problem that I cannot backup these. Get the information from Veeam: One or more VMs in the snapshot group has been locked by another task or a snapshot group and VM is locked by another task or a snapshot group

This information/error haven't I seen before on Hyper-V and cannot find anything on how to fix this.

Any help for anyone?

[schmiesus]

Are the snapshots getting stuck at 9%?

[enoch]

Hi,

Can't see any % in the progress of snapshot in Veeam.

It only shows Pending on all 5 VM's and then on 4 VM's stuck at "One or more VMs in the snapshot group has been locked by another task or a snapshot group". The last VM show: "VM is locked by another task or a snapshot group"

This is with Hyper-V 2012r2. Other VM's works fine!

[enoch]

The wierd thing is I can't find anything nowhere on the message..

Am I the only one and how to fix

[Mike Resseler]

Hi Peter,

It has been a while since I heard this and at that time simply restarting the services of the backup server (or proxy if you are using a proxy that is not located on the B&R server) did the trick. But as said, this is quite a while ago (which is probably the reason why you can't find too much information on the message )

Another reason I am aware of is that the host is locking it with a snapshot. Can you open Hyper-V Manager and check for these VMs if they are running on a snapshot?

Lastly: If the above does not solve anything please log a support case (and report the case ID and the outcome afterwards here) so that our engineers can look through the logs to figure out what is stuck

Thanks
Mike

[nefes]

And one more reason could be another backup server (Veeam or third party) backing up same VM at the same time

[enoch]

Hi all,

Will restart the server now (in 15 min.) and then check again after reboot.

I've checked all Hyper-V hosts and there is no active or starting checkpoints running.

Job runs in On-Host Proxy mode.

Will be back soon with status

[enoch]

Hi all,

It works after reboot of Veeam BR server

Would be nice with a little better error handling..

[Mike Resseler]

Hi Peter,

Good to know that it is solved. So there was probably somewhere a task locked (for a specific VM). I understand your question for better error handling, but as you read here, we were also "gambling" what it could be (thanks to Nikita also actually, forgot that option ) so better error handling is difficult as we don't know the root cause.

Anyway, glad it is solved. And thanks for coming back to us with the solution

cheers
Mike

[nmdange]

Just wanted to chime in I also ran into this same issue recently and restarting the Veeam server fixed the problem.

[Mike Resseler]

Peter, nmdange,

Next time you hit this, I would appreciate it if you could create a support case so the logs can be investigated. If this happens too much, we might want to figure out if it is not something that can be solved better

Thanks
Mike

[nmdange]

Sorry should have put it in my poste, we had opened case # 02134160. One thing to note, we had not restarted the Veeam server for about 4 months. Due to various reasons, we had not restarted to apply Microsoft monthly patches so the server had been running a lot longer that it would normally.