During a Delete Snapshot operation, the content of two virtual disks are merged, the redo log contents are consolidated into its parent.
It is necessary to store both the writes from the Guest OS and the writes from the consolidation operation for a running virtual machine. Further, the source of the consolidate must be read-only during the consolidation. This is referred to as an Online Consolidate.
ESX uses an iterative process to accommodate these requirements:
- The size of the source redolog files are reviewed.
- If the contents can be copied into the parent within a few seconds:
- The virtual machine is momentaraliy paused.
- Data is copied from the source redolog (eg, 00001) to its parent.
- The virtual machine resumes running from the parent.
- If the contents cannot be copied into the parent within a few seconds:
- If this is not the first iteration, it is logged similar to:
vmx| SnapshotVMXConsolidateOnlineCB: Another iteration is needed.
- A new snapshot is created and named "Consolidate Helper".
- An associated redolog (eg, 00002) is created and opened read-write.
- Data is copied from the source redolog (eg, 00001) to its parent.
- During the copy operation, the Guest OS continues to write new data to the read-write consolidate helper (eg, 00002).
- Data copy is completed, and the source redolog files (eg, 00001) are deleted.
- The size of the new redolog files (eg, 00002) are reviewed.
- The process repeats from step 1.
The general trend is that the amount of data in the additional redolog will decrease over time. As the amount of data being written by the Guest OS increases, the duration of a snapshot delete and redolog consolidation will also increase.
Note: There is no option to cancel the snapshot delete or redolog consolidation operations. To allow the snapshot delete to complete, reduce the amount of write disk I/O generated by the virtual machine's Guest OS and applications.