Vmware snapshots not consolidating
Hi a delete of the latest snap I understand commits the Delta and deletes the snapshot (keeping the server at its current state) A commit I understand commits the changes but does not delete the snapshot. Here is some more information: Consolidating snapshots in v Sphere 5.x (2003638) Understanding virtual machine snapshots in VMware ESXi and ESX (1015180) DELETE SNAPSHOT: The snapshot files are consolidated and written to the parent snapshot disk and merge with the virtual machine base disk.So what is the reason for doing this - I'm guessing then after the commit the snap is still in place and will continue to grow (delta) - until you commit or delete? Deleting a snapshot leaves the current state of the virtual machine or any other snapshot untouched.Unfortunately, this failure to consolidate was not apparent via the UI, and usually only became noticeable to the end user when the delta files grew very large, possibly resulting in a full VMFS or NFS volume if they were attached to very large VMs.Support engineers from GSS (VMware's Global Support Services) would then have you use their many tricks of the trade to consolidate the snapshot deltas into the VM base disk.Deleting a snapshot consolidates the changes between snapshots and previous disk states and writes to the parent disk all data from the delta disk that contains the information about the deleted snapshot.
With v Sphere 5, a new option called consolidate was introduced.
The steps to test are quite simple: A ' Configuration Issue' warning should now be surfaced in v Center, same as that shown above.
If you login to the ESXi shell, and examine the home folder of the VM, you will notice that the snapshot delta file still exists.
With the consolidation option, when you initiate a snapshot deletion, if the snapshot fails to delete, the VM will then generate a warning letting you know that a consolidation is required.
You would then run the snapshot consolidation option and the snapshot would get committed.
There is a way to test this via the Power CLI if you so wish.