Schmoog wrote:
In my environments, I generally create cpgs for system groups. So for instance I have a vmware pcg, exchange cpg, etc.
The reason I did that was so that I can run performance reports on the cpg and view the performance of a particular group of hosts/services in system reporter
We did something similar, I had 3 AO configs each with 3 CPGs, one for vmware, one for AIX and one for databases. We abandoned that because as our array got tight on space it was a nightmare to juggle growth warnings to make sure we had enough space in each tier of disk. We instead went to a single AO config and 3 CPGs on each array. It helps that our databases got peeled off onto their own 7400. I do have front end ports dedicated for each environment so if I want to see how much IO or latency a given environment is seeing I run SR against the front end reports.
I also find that unless you have a lot of active data AO regardless of mode (Performance, Balanced, cost) AO tend to move data down and you never want to run out of your lowest tier of disk since if a higher tier fills the array will always write to the lowest tier. Keeping that in mind if you run your array tight then having multiple AO configs and CPG sets is a nightmare to manage.