Thanks for the quick reply.
I have taken a look at the notes you suggested. Seems fairly straight forward.
I am a little puzzled by the statement
"If your VM is on shared storage and you specify local storage as a location you will not be able to use Vmotion/HA/DRS."
Shared Storage? Aren't all data stores shared storage? I have allocated two data stores for Snapshots, both 200GB and both will be accessed by all VMs on the Cluster (for their Snapshots). I suppose I could have defined a data store on some JBOD, physically attached to the VM hosting server.
Local Storage? Is this suggesting that I ought not to put the Snapshot on a locally attached hard disk (as opposed to one on the SAN)? If so, not being able to use Vmotion and HA seems reasonable (although I am not sure about DRS -- it seems harsh not to be able to use DRS to manage Memory and Processor if the data disks are locally attached).
Would the strategy of housing snapshots away from the base VMDK files cause us problems in the future, should we want to Vmotion/Migrate to an alternative Cluster? Or, would the Vmotion/Migrate wizards ask us to supply a location for the Snapshot (and potentially, the Swap file)?
The more I read Eric's statement the more I believe my assumptions are correct. We do use Shared Storage for all aspects of our VMs (EMC SAN).
Before I blunder in and start changing things, I'd just like to be crystal, so sorry for the rambling self-answering nature of this post!
BTW, Snapshot Moderate?
