Re: "Snapshot hierarchy is too deep" after vSphere Replication crashed

Hi,

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 :

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004545

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 :

https://my.vmware.com/web/vmware/info/slug/infrastructure_operations_management/vmware_vcenter_converter_standalone/5_0

Links of the KB article’s below which would help you to increase the performance of the converter and speed up the process.

http://kb.vmware.com/kb/1004588

http://kb.vmware.com/kb/2020517

Hope this was helpful.

Thanks,

Avinash