A. There are several ways for virtual hard disks to be stored with ESX:
- Zeroed thick: VMDK files have all space allocated at time of creation, but the blocks that make up the VMKD aren't erased until the VM tries to access the block.
- Thick: Same as zeroed thick, but blocks aren't erased when accessed for the first time. This means that if a thick VMDK is created over the same location as a previous VMDK and the application just tries to read certain blocks of data, the old data will be read, posing a security risk.
- Eager zeroed thick: Same as zeroed thick, except all the blocks that make up the VMKD are cleared when you create the VMDK.
- Thin: Data blocks are only wiped and allocated as the VMDK uses them.
If you perform a storage vMotion with vCenter 2.5, the target disk will be a thick disk, even if the source was a thin disk. While there are ways to keep the disks thin, they're very complex procedures. The ideal solution is to upgrade vCenter to version 4, which supports keeping VMDKs in their original format. The hosts can still be ESX 3.5 and be managed by vCenter 4.
- Q. Is it possible to manage ESX 3.5 hosts from vCenter 4?
- Q. I've upgraded my ESX installation to ESX 4.0. How do I upgrade the virtual machine (VM) hardware to version 7?
- Q. What is VMware Fault Tolerance (FT)?
- Q. I have an Iomega NAS with NFS support. I get errors connecting VMware ESX to the NFS on the NAS. What's wrong?
Check out hundreds more useful Q&As like this in John Savill's FAQ for Windows. Also, watch instructional videos made by John at ITTV.net.