Delta disk files | 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. If you are looking at a datastore with the Datastore Browser in the vSphere Client, you see only one entry to represent both files. The files that make up the delta disk are referred to as child disks or redo logs. A child disk is a sparse disk. Sparse disks use the copy-on-write mechanism, in which the virtual disk contains no data in places, until copied there by a write operation. This optimization saves storage space. A grain is the unit of measure in which the sparse disk uses the copy-on-write mechanism. Each grain is a block of sectors that contain virtual disk data. The default size is 128 sectors or 64KB. |
Flat file | A -flat.vmdk file that is one of two files that comprises the base disk. The flat disk contains the raw data for the base disk.This file does not appear as a separate file in the Datastore Browser. |
Database file | A .vmsd file that contains the virtual machine's snapshot information and is the primary source of information for the Snapshot Manager. This file contains line entries, which define the relationships between snapshots and between child disks for each snapshot. |
Memory file | A .vmsn file that includes the active state of the virtual machine. Capturing the memory state of the virtual machine lets you revert to a turned on virtual machine state. With nonmemory snapshots, you can only revert to a turned off virtual machine state. Memory snapshots take longer to create than nonmemory snapshots. The time the ESX host takes to write the memory onto the disk is relative to the amount of memory the virtual machine is configured to use. |
Description |
---|
Snapshot file that represents the difference between the current state of the virtual disk and the state that existed at the time the previous snapshot was taken. Free violin ringtone. The filename uses the following syntax, S1vm-000001.vmdk where S1vm is the name of the virtual machine and the six-digit number, 000001, is based on the files that already exist in the directory. The number does not consider the number of disks that are attached to the virtual machine. |
Database of the virtual machine's snapshot information and the primary source of information for the Snapshot Manager. |
Memory state of the virtual machine at the time you take the snapshot. The file name uses the following syntax, S1vm.snapshot1.vmsn, where S1vm is the virtual machine name, and snapshot1 is the first snapshot. A .vmsn file is created each time you take a snapshot, regardless of the memory selection. A .vmsn file without memory is much smaller than one with memory. |