King_Julien wrote:
As far as I know I have to move a VM to a LUN on the FAST VP pool, then FAST VP will what?
Then nothing...the FAST will take care of the rest.
Will take a "slice" (a block if get it right) of the VM having more workload and will put it into a SSD drive to gain better performance for that VM? And then what?
Exactly - hot blocks wil move up to faster disk, and cold will move down to slower disk automatically (how long this takes depends on array model and configuration).
Also, I did a little investigation about this, but I got more confused, is it necessary to measure the IOPS of the VMs that are intended to be moved to FAST VP luns, right?
It helps so that you can properly understand how many VMs / how much workload the pool can support, but its not required, per se.
Since I'm barely new to this whole VMware stuff and since I'm still trying to understand lots of concepts from VM documentation and EMC documentation... here's another of my newbie question... What's the difference between FAST VP and to set "shares" on VM options?
FAST VP moves blocks around on the storage array. Shares on the VMware level tries to deal with contention by making some VMs more important. Its OK to use both at the same time.
Or even, what's the difference with Storage DRS.... Beat me if you want but I´m learning this from zero and it's very confusing!
Storage DRS should be set to 'Initial placement mode' only when using FAST VP. SDRS can move VMs between datastores to get better performance, but it can only move entire VMs, whereas FAST can do it with much better granularity (1GB slices).
Any tip will be highly appreciated.
Assuming you are using VNX (and not VMAX), all these best practices are in in thechbook here:
http://www.emc.com/collateral/hardware/technical-documentation/h8229-vnx-vmware-tb.pdf
Also, talk to your reseller and have them bring in your local EMC vSpecialist/SDspecialist to go into gory detail on this.
↧
Re: Fast VP + Vmware
↧