Oracle ASM and VMAX Storage Pools

My company is looking at the VMAX for consolidating multiple older Symms. We are told by EMC Pre-Sales that we need to move all data into pools on the VMAX (not neccessarily thin pools) to be able to take advantage of the new functionality like TP, FAST etc. We run a 20 TB Oracle RAC 10g-R3 database accross 146x 133 GB Metavolumes with 8x 16.5 GB members that are replicated to our DR site via SRDF/DM (yeah, yucks).

My questions are as follows:

- How would you design this on the VMAX with storage pools?

- So you know, we do want to go to larger LUN sizes e.g. 266 GB but would you recommend 266 GB Meta-volumes with 16 members? Or more or less members? Get rid of Metas altogether?

- How do you avoid/manage wrapping on the physicals? ASM is striping, Metas are striping, the storage pool is striping too. How do you avoid hitting the same physicals multiple times with a single extend write in ASM with this "striping over striping over striping"? Wrapping can probably not be avoided when you do the math but how do you know that each physical in the storage pool wraps in a "fair" way?

- Single storage pool, multiple storage pools ...

- What would you do with the R1-BCVs? You wouldn't want to put them in a storage pool too, would you?

- Can you do storage pools on the R1 side and continue with the traditional appoach on a DMX-4 on the R2 side?

Thanks in advance.