A .vmdk file to which the guest operating system can write. The delta disk represents the difference between the current state of the virtual disk and the state that existed at the time that the previous snapshot was taken. When you take a snapshot, the state of the virtual disk is preserved, which prevents the guest operating system from writing to it, and a delta or child disk is created.
A delta disk has two files, including a descriptor file that is small and contains information about the virtual disk, such as geometry and child-parent relationship information, and a corresponding file that contains the raw data.
How did you create the snapshot (manually, script, backup application, ...)?
I saw this behavior with backup applications where a first snapshot was created for the VM itself (as expected), and a second snapshot was created due to the backup application's way (independent-nonpersistent) to mount the VM's virtual disk for the backup.
I created quiesce snapshot manually on VM . There is no backup software involved here as I am doing it on a lab
I am unable to understand why two delta files
Please create a snapshot and delete that with Delete All option .
Uninstall and install the vmware tool to latest .
Try again and let me know if you face same issue .
Also please check there is hdd .vmdk file avaialbel on the folder of the VM by browsing or from CLI which is not in use . This HDd may be you have remove from VM but not selected delete option
VCA -DCV/WM/Cloud,VCP 5 - DCV/DT/CLOUD, ,VCP6-DCV, EMCISA,EMCSA,MCTS,MCPS,BCFA
Mark my post as "helpful" or "correct" if I've helped resolve or answered your query!
Have a look at the vmware.log that describes the process.
I would expect to see that the guest gets stunned twice and in between the VSS actions are executed.
The two delta files are typically created only for quisced snapshots ( for windows 2k8 and above for windows and latest Linux kernels also support this).
One of the delta file contains the normal delta information and the other file ( which is small in size) contains the application consistent information . The combination of both these delta files ensures that the snapshot taken is not just filesystem consistent but application consistent.
For windows GOS this is typically achieved by the VSS service
Is this a new change? earlier it used to be different. Whether quisced or not it had created only a single delta vmdk file.
Could you please point to VMware article describing the change? Tried to find the KB article or release notes with information mentioned but could not.