Thanks gearoid, Yes im planning to use Virtual Provision,and Yes they are all the same speed.

What am planning to is to have too pools one with 16 Drives for Raid 1 and the other with 25 for Raid5.

Hi

Firstly I would recommend you would possible repost this in the VNX forum

https://community.emc.com/community/support/family/vnx

Are you going to be using any Virtual Provision applications? (I saw you said that you will not be using FAST VP) but what about compression? Are these drives all the same speed or different?

Pools give you the opportunity to expand beyond the traditional raid groups limits

Pools also give you the opportunity to mix thin and thick (full provisioned luns)

If you are on, or do goto Rel 32, and if you ever need to expand the pool, you would be able to rebalance your pool on Rel 32

Hope that helps

Gearoid

why two pools, are you separating specific workloads ?

As far as i know ,i can have diffrent raid type in the same pool running flare 32,but each type of disks can be configured to diffrent raid type. I need two raid types so can i have them on the same pool with the same drive type ?

Please share your recommendations this why im posting.

Thnx

you are correct, you can mix different raid types in the same pool. Maybe i misunderstood your question ? I am looking at your alias , maybe you are thinking in terms of VMAX where you have different pools for different tiers yet they participate in the same FAST policy ?

Ya , then do you recommend using only one pool ? as per the latest unified best practices for performance released on august, EMC recommends to create multiple pools.

Hello dynamox,

Would you please also advice what could be the impact on performance while the number of the pool changed?

Thanks & Happy Sunday

Henry

definitely use multiple pools if you have a unified platform where you want to create one dedicated pool for File (datamovers). Aside from that it's up to you to decide if you need to have multiple pools. For example in my shop i created two pools, one was generic pool where i pretty much put all applications, the second pool was created specifically for my backup application. This application was not FAST Cache friendly so i wanted to isolate it from other workloads and disable FAST Cache (can only be done at pool level, not individual LUNs). If i had a medical records application where i just had to have predictable performance i would put it in its own pool so it would not be impacted by some other database runaway query or something of that nature.

Hello Henry,

probably the biggest is the number of spindles that you dedicate to pools, on VMAX you create data devices and add them to a pool, on VNX you add physical spindles. I wanted to consolidate as many spindles as possible in as few pools as required to give me the best possible number of iops.

I would recommend that since your are not using FAST as of now, you won't have control over which data is placed on which RAID type disks. Hence you may end up with a mismatch in terms of performance requirements of the data and the underlying spindle type it is on. E.g. small block random IO might be serviced from RAID 5 disks and may be detrimental to your performance expectations. Till the time you  don't have FAST, create seperate pools for seperate performance requirements, but keep maximum number of disks in the pool. Moreover, as @dynamox said, definitely use a seperate pool for file services/datamovers.