Hi,  dont worry about a Celerra pool being too big in terms of performance it cant be too big - only too small :-)  reason being that a pool isnt a "physical object" like a raidgroup or an aggregate a (system) pool is merely a list of volumes with the similar protection and performance characteristics  from that pool the Celerra selects a couple of dvols (nr. depends on the pool - max for for Clariion), stripes them together for performance and slices/concats them for capacity  if the pool is large enough then AVM has a decent chance to find some balanced dvols to stripe together  I would use more pools (user defined pools) only when I need to seggregate performance or capacity between different applications or departments If you go that route you need to make sure the user defined pool also uses striping (by default it doesnt)  in terms of LUN size I would go with whatever the Storage Provisioning Wizard creates  there is no max pool size - it would be good if a pool had at least four independent dvols (not on the same raidgroup)  raid type and size is really up to your preferences and how many disks you have all the supported configs are fine - I tend to go with 4+1R5 or 8+1R5 or 6+2R6  Rainer
Guys, We are upgrading our Celerra NS480 with 56Tb raw capacity using 2Tb SATA disks. We are currently using AVM. If we let AVM create the pools, then this huge amount of capacity will go into the clarata_archive pool automatically. I have a few questions: a ) Will there be a performance issue if we have a single pool of this size? b ) Is it recomended to create two or more ATA pools manually instead of a single huge one?. If yes, what would be the recommended size and what are the benefits if any of having multiple ATA pools?.  c) Is there a recommended maximum size of a pool? d) What raid type is recommended to create out of this raw storage at the Clariion backend?  Thanks a bunch. 
Celerra pool management