vmware - disk provision
Can some one explain the difference between the following specially
thick provision eagar zeroed
thick provision lazy zeroed
thin
also what is use of vmware tools?
is it really needed for vm? what is the function of this tool?
thick provision eagar zeroed
thick provision lazy zeroed
thin
also what is use of vmware tools?
is it really needed for vm? what is the function of this tool?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you use thin it will save you space but the performance will be lesser than thick as the disks are zeroed and then data is filled every time you write.
If space is no issue, Go with disk.
If performance is not important go with thin
If space is no issue, Go with disk.
If performance is not important go with thin
thick eager zeroed - always!
@alexgreen312 You can migrate VMs using vMotion without VMware Tools!
ASKER
my SAN admin told me that HP recommend to use Thick eager provision for all VMs.
It does not make sense to me. You guys have any idea.
It does not make sense to me. You guys have any idea.
ASKER
People arguing that VMware tools is must for vMotion. not make sense to me.
This is what the HP Documentation says
Block Zeroing uses the standard SCSI command WRITE_SAME to offload large, block-level write
operations of zeros from the host to the storage array. Block zeroing improves host performance and
efficiency when allocating or extending Eager Zeroed Thick (EZT) virtual disks, or on initial access to
a block on a non-EZT virtual disk. When combined with built-in zero-detection and EZT virtual disks,
storage array bandwidth, disk I/O bandwidth, and disk consumption is minimized. Initialization of
EZT virtual disks in seconds rather than minutes eliminates the tradeoff between fast VM creation and
fast run-time performance.
So yes it makes sense to have Eager zero disks.
And yes it does not make sense that VM-tool is required for vmotion. That's a wrong statement.
Block Zeroing uses the standard SCSI command WRITE_SAME to offload large, block-level write
operations of zeros from the host to the storage array. Block zeroing improves host performance and
efficiency when allocating or extending Eager Zeroed Thick (EZT) virtual disks, or on initial access to
a block on a non-EZT virtual disk. When combined with built-in zero-detection and EZT virtual disks,
storage array bandwidth, disk I/O bandwidth, and disk consumption is minimized. Initialization of
EZT virtual disks in seconds rather than minutes eliminates the tradeoff between fast VM creation and
fast run-time performance.
So yes it makes sense to have Eager zero disks.
And yes it does not make sense that VM-tool is required for vmotion. That's a wrong statement.
ASKER
Can you please point the HP document?
ASKER
Can you point out some scenarios where it would be more appropriate to use these three technologies.
thick provision eagar zeroed
thick provision lazy zeroed
thin
thick provision eagar zeroed
thick provision lazy zeroed
thin
thick provision eagar zeroed - performance critical VMs, VMs using for Fault Tolerence or Clustering.
thick provision lazy zeroed - Virtual Machines, where performance is no so critical, but to be honest, why not use thick provision eagar zeroed, and get 15% better performance.
thin - when you are short of disk space, Lab and Test environments. But be careful, ALL your VMs, do not dynamic allocate, and use ALL the disk space, because then you will over subscribe your storage space.
Most NFS datastores, would use Thin disks. Be careful Thin disks are not supported by some vendors for Applications e.g. Microsoft Exchange
thick provision lazy zeroed - Virtual Machines, where performance is no so critical, but to be honest, why not use thick provision eagar zeroed, and get 15% better performance.
thin - when you are short of disk space, Lab and Test environments. But be careful, ALL your VMs, do not dynamic allocate, and use ALL the disk space, because then you will over subscribe your storage space.
Most NFS datastores, would use Thin disks. Be careful Thin disks are not supported by some vendors for Applications e.g. Microsoft Exchange
ASKER