Thick vs Thin Provisioning for the vCenter Server VM?

[munkyman]

What type of provisioning should be used for the vCenter Server VM?  I will be using the High Availability functionality between 2 hosts eventually, but right now I am just building the vCenter Server VM.

Thick Provision Lazy Zeroed	Create a virtual disk in a default thick format. Space required for the virtual disk is allocated during creation. Any data remaining on the physical device is not erased during creation, but is zeroed out on demand at a later time on first write from the virtual machine.
Thick Provision Eager Zeroed	Create a thick disk that supports clustering features such as Fault Tolerance. Space required for the virtual disk is allocated at creation time. In contrast to the flat format, the data remaining on the physical device is zeroed out during creation. It might take much longer to create disks in this format than to create other types of disks.
Thin Provision	Use the thin provisioned format. At first, a thin provisioned disk uses only as much datastore space as the disk initially needs. If the thin disk needs more space later, it can grow to the maximum capacity allocated to it.

[a_p_]

You may use any of these options. There might be slight performance benefits in using the Eager Zeroed Thick format , but with vCenter Server running on the VM you may not even notice them. Whether to chose thin or thick is another question. If you keep monitoring the disk space usage, and you will be able to increase the disk space if required then you may select thin provisioning. If you do have sufficient disk space - that's at least my opinion - use thick.

André

[admin]

If you are going to use only two hosts for this VC for HA then it is advised from me to use thin disk as it will be using less disk space from your datastore and since you are using only two hosts for VC, There will be no performance issues for you.

Thanks,

DJ