i'm also noticing that when i run a test snapshot, i lose connectivity to the vm until the snapshot is complete? Is this normal?
Bad news... You can try "service mgmt-vmware start" at the service console, but it usually does not help. Try shutting down the VM and deleting the snapshot. If that does not work, the only thing I have seen to work is doing a cold clone to a new VM and deleting the old VM. SUX!
yep, a cold clone to a new vmdk file was the only way i got rid of it. Thanks
Are you referring to doing a cold clone using Converter (or another product)?
A "cold Clone" is the process of shutting down the VM, right click and select clone. It makes a copy of the VM.
Yes, but you can't clone a VM if it contains snapshots. That's why I was thinking that it is a cold clone using "Converter"
I've read that you can use Converter to hot clone a VM to a new name and get rid of all the snapshots. Will a cold clone using Converter do the same?
I have not had that issue. I would think using converter will produce the same result.
Thanks for your response.
Are you certain that you are able to clone a VM that has active snapshots?
I get a "Migration of virtual machines with snapshots is not supported between the source and destination".
What version of VC and ESX are you running?
Just to make things clear, i ran the:
vmkfstools -i tool to fix the issue and create the new vmdk files.
I had the same error, I attempted to remove the snapshot which failed, I then received the "consolidate helper" snap inplace of the removed
snapshot.(also failed when attempted to delete)
I had three drives 20GB,100GB and 250 GB (SQL Server...)and yes migration worked for me. I migrated the server from HPBlade1 to HPBlade2
kept 20gb and 250gb in same datastore but moved the 100gb to a new datastore. took 30min to complete and started 100%.
Thanx for the postings it all helps
I am experiencing similar prolems but the suggested workaround is pretty drastic and I think not practical in a production environment.
Does anyone know whether a bug has been opened against this issue?
I just tried your solution on the "primary vmdk files" but all the other .vmdk files that resist in this directory are NOT applied to the primary vmdk file after cloning it. Did you have this same problem?
I am now cloning thru the GUI and hopefully all changes are commited to the primary vmdk.
With kind regards,
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
I've had the consolidate helper problem many times, All you have to do is create a new snapshot. after that completes, go back into snapshot manager and select delete all snapshots and it will get rid of the consolidate helper and the new snapshot.
If your snapshot is rather large, the removing of the snap shot will error out at 95% (this is normal as there is a predifined time out to get a finished response) even though it errors out it is still merging the files in the background.
Hope this helps
this was the simpliest and best solution to solve this problem, worked for me in two minutes..
Thank you !!