VM snapshot consolidation attempts have failed

[btmaus]

I got an alert this morning that one of my VM backups have failed, due to "hostname.domainname needs snapshot consolidation, but all automatic snapshot consolidation attempts have failed. Most likely reason is a virtual disk being locked by some external process."

I can see the VM's disks still attached to the Veeam proxy.

So firstly, how do I resolve this, do I just remove the disks from the Veeam proxy, and then run a consolidate on the VM itself?

Secondly, why would this happen?

P.S. Support case raised as well - #01674475.

[Shestakov]

Hello btmaus,
As support engineer suggested, you need to Removing Stuck VMDK’s from the Veeam Proxy.
The possible reason is an orphaned snapshot which caused the new VM snapshot consolidation stuck. Snapshot Hunter usually resolves it but something might go wrong. Keep working with the support team to find out the real issue.
Thanks!

[btmaus]

Thanks, I did the above and it seems fine now.

[Shestakov]

Great! Have you found out the reason?
Thanks!

[btmaus]

No, might have to open a support ticket with VMware.

[Shestakov]

It`s up to you.
I was just curious what caused the problem. But since it works now you may not want to contact VMware.
Anyway thanks for updating the thread!

[roit]

I had a similar problem and i solved with a VMware VM Parameter: snapshot.asyncConsolidate.forceSync = TRUE

Cause:
This message is reported if the virtual machine is powered on and the asynchronous consolidation fails after 10 iterations. An additional iteration is performed if the estimated stun time is over 12 seconds. This occurs when the virtual machine generates data faster than the consolidated rate.

More information:
http://wiki.webperfect.ch/index.php?tit ... or_scsix:x
http://kb.vmware.com/selfservice/micros ... Id=2082886