Hi,
The idea with the 3PAR is that you can over-subscribe your storage and make better us of the actual physical disk space, albeit paying attention so you don't end up way oversubscribed and filling up the actual 3PAR disks... As an example, we're up to 137% presented out to hosts, but only using 70% of the actual physical disk capacity.
Your easiest option, i think, would be to create and export another vvolume, add it as an additional VM datastore, and let the 3PAR deal with the "thin" side of things. If you start doing thin on thin, you then run the risk of filling up both the vmfs store and the exported vlun without warning; if a lot of data is added and the vmdk's need to expand beyond what vmfs sees as datastore size, I assume the VM;s will just freeze/shutdown? We're using thin on the 3par, and datastore clusters in vsphere, that way, vsphere might be using 80-85% of what it sees, but the 3par vvolumes are sitting down at 50-60%.
Hope that helps.
Cheers,
Will
|