1) don't see the point, i assume it will deploy on private raid groups based on the tier you specify and it will stay there. Might as well create distinct pool for each tier. 2) it will be spread over as many private groups as possible in 1g slice increments 3) if you are on flare 32, whenever you add disk to an existing pool it will rebalance automatically the LUNs onto the new drives. After that it will stay pat if you don't have FAST license. 4) it's a scheduled process, it collect stats all day and during the specified time window it start moving slices around. 5) yes (i have ), for performance consideration EMC recommends to use dedicated pools for File.
Hi,  I am a big admirer of VNX and i would like to ask a couple of questions about the functionality of pools:  1- If i dont have FAST VP enabled, is there a point in having 2 disk types in the same pool? If yes, how will the system decide how to spread the LUN on the private raid groups?  2- If i have a LUN residing in a pool of 1 disk type, is this LUN spread over ALL the disks in the pool? or over certain "private raid groups" ?  3- If i have a LUN residing in a pool of 1 disk type and i add more disks to the pool, will i get performance enhancements assuming that i had performance bottlenecks from lack of spindles? i.e: will the LUN be redistributed over the new disks that i add to the pool? Is there a manual operation required after adding new disks?  4- If FAST VP is enabled on a pool, when does relocation happen? If the scheduler says all days, all hours. When does the relocation happen and under what conditions?   5- Can i create a LUN that will be used by data movers (for file access) from a pool which i am using for block access?  Thanks JS
VNX Functionality - Pools