1 person found this helpful
This problem is a tricky one to handle since VMware supports only 32 level of snapshots. but we have our options,
this is what I do when the snapshots is out of control
Option 1 :
Step 1 : Take an SSH to any of the Host with access to the data store containing the snapshots and cd to the location.
Step 2 : Run vmkfstools -qv3 <last snapshot >
eg : vmkfstools -qv3 test-00256.vmdk --- This will let us know if the snapshot chain is complete.
Then commit the disks using vmksfstools -i last < snapshot.vmdk > VMname. vmdk name
eg : vmkfstools -i test-00256.vmdk VMName.vmdk
The below Kb should be helpful :
Note : If have to repeat the same for all the hard disk. ie vmdks.and requires downtime.
Option 2 :
use the VMware converter and do V2V of the machine on the fly - No downtime required.
I would prefer to use the second option.
Download link for converter :
Links of the KB article’s below which would help you to increase the performance of the converter and speed up the process.
Hope this was helpful.
You will need a downtime some time when the vmsd is invalid.
To keep the downtime as short as possible you can use vmkfstools -i to consolidate all but the very last snapshot.
Then you still need about 3 minutes of downtime to prepare the final step that gets rid of the last snapshot.
Merging the last snapshot into the new basedisk that you created with vmkfstools -i then again can be done while the VM is running.
I can give you detailed instructions when you post details (file-listing, vmware.logs ...)
Many thanks. I'll convert VM for sure first and try commit the disks then. The snapshot chain looks to be complete.
"Cannot convert a powered-on machine" message. I must omit this step
Actually convert "Powered on machine" can be used in this case.
I see, back to the first wizard page and choose "Powered on machine" source.
In this case you need admin credentials for the machine, also result will not have any snapshots (they are invisible for the guest os).
Thanks for your tip. But I'm not able to contact the specified VM. It's probably out of scope this discussion but I can ping this VM, I can log to it via remote desktop but using the same credentials Converter can't contact it from the same PC
It's probably because the host this VM running on is in disconnected state. Can't reconnect host to vCSA: Host name does not match the subject name(s) in certificate. I've put support request but it's not resolved yet.
It depends on network/firewall/etc. settings.
Via remote desktop you can install converter and choose "This local machine" radio button.
Thanks again. It works. I can't see the most simple solution sometimes
I converted VM for backup purposes and now I try to consolidate snapshots. There are two disks in different storages with the same amount of snapshots.
the download link does not work - please simply attach the files here
Thanks, logs attached. I used simple editor before and I couldn't find Attach Files icon I'm sorry.
Some more info:
There are two disks in different storages with the same amount of snapshots in this VM. I've did for both of them yet:
1. cd <disk directory>
2. mkdir ../restore
3. vmkfstools -i <disk name>-000255.vmdk ../restore/<dik name>.vmdk
I can't copy the last snapshots to restore directory now 'cause <disk name>-000256-delta.vmdk files are busy. Shall I turn off VM first, copy files, turn on VM and proceed with consolidation then? But what about new changes? Or is better to have VM turned off for all next steps? Anyway I must wait for maintanace hours before turn this VM off.
I'm not sure with "9. Remove the existing snapshot vmdk ..." in VMware KB: Committing snapshots in vSphere when more than 32 levels of snapshots are present fails with the error: T… Shall I do "rm <disk name>-000*.vmdk"?