

If you look at the contents of the *.vmsd file in the virtual machine’s working directory, you should see the following if consolidation is required: /vmfs/volumes/4f27b82e-3fc1540e-bf6b-000c295da2d9/XP3 # cat XP3.vmsd You should immediately get the ‘needs consolidation’ message in the vSphere client. This will remove the snapshot, without committing the delta files. If you want to test the process, create a snapshot on your virtual machine, then run the following in PowerCLI:

When you see this, you can run a Consolidation on the virtual machine to commit the delta files to the base disk: Now, when a VM has had issues consolidating its snapshots you will see a message on the Summary tab for the virtual machine:

This could lead to problems where a VM that didn’t look as though it had any active snapshots, was still actually writing to the delta files. This was done to address an issue where, when doing a snapshot removal, the delta files would not be merged with the base disk but would be removed from visibility in the vSphere client. Further to that, I thought I’d cover a bit on Snapshot Consolidation With vSphere 5, a new feature was added to allow you to consolidate snapshots. I’ve written a post recently around creating snapshots using the ESXi CLI.
