Hello Enrique,
Here is the 3PAR implementation guide for exchange:
Attachment:
I would not filter CPGs by drive cage but instead filter it by magazine position. This way your CPGS will stripe across cages for better performance and symmetry. If you choose to filter your CPGs to adhere to Microsoft Best Practices, I would filter half your magazine positions to one CPG, and the other half to another CPG. Then flip flop data/logs to each:
For example:
CPG1: = filtered to drives in magazine positions 0-4
-LUN1- EXCH DB1 DATA
-LUN3- EXCH DB2 LOG
...and so on
CPG2: = filtered to drives in magazine positions 5-9
-LUN2- EXCH DB1 LOG
-LUN4- EXCH DB2 DATA
...and so on
CPG3: = not filtered, so it uses all drives, positions 0-9
-LUNx- Imaging Data
-LUNx- Imaging Data
..and so on
Talk to your 3PAR SE about his/her recommendations for CPG creation. The advice I got from mine was unconventional by Microsoft standards, but has worked very well for us. We don't filter any of our CPGs, we let the wide striping do its job across all available spindles, and performance is excellent. We have multiple windows systems that bottle neck at the host HBA.... but we also have a great wall of spindles, 960 spindles total. What works for us, may not apply to you, so leverage your SE for help.