take a look at this paper if you have not already  [URL]
Admins,  For some reason am not able to post content in the VNX support forum - so am posting this question on Symmetrix forum.  We are migrating from HP 3PAR and MSA to VNX soon. And we have a proposed VNX pool layout as below.   Main Site:  ===========  VPOOL1 for APP:   • 75 TB • Thin Provisioning • 20 * 200GB SSL +40 * 600GB + 40 * 2TB.  • 3.9% SSD  22.9% SAS  73.2% NL • Almost 39,000 IOPS  VPOOL2 for Non Prod Apps: • 11 TB Usable • Thin Provisioning • 8 * 2TB • 100% NL • Almost 260 IOPS  VPOOL3 for File Share: • 11 TB Usable • Thin Provisioning • 8 * 2TB ` • 100% NL • Almost 260 IOPS  VPOOL4 for RP Journaling: • 12.8 TB Usable • Thin Provisioning • 30 * 600GB • 100% SAS • Almost 2600 IOPS  We will have extra 5 * 600GB HDD to be utilized when needed in Journaling or any other place.   DR Site: ========  VPOOL1 for APP:   • 52.6 TB • Thin Provisioning • 15 * 200GB SSL +15 * 600GB + 32 * 2TB.  • 4.2% SSD  12.2% SAS  83.6% NL • Almost 27,400 IOPS  VPOOL2 for RP Journaling: • 8.5 TB Usable • Thin Provisioning • 20 * 600GB • 100% SAS • Almost 1700 IOPS  We will have extra 5 * 600GB HDD to be utilized when needed in Journaling or App Pool Also we have 8 * 2 TB HDD to be utilized when needed in App Pool or File Share.  ***** Before we proceed to our new infrastructure  - are there any best practises we can follow with regards to the creating the types of LUNs (Boot Vs RDM LUNs) with each pool. We are going to have both Microsoft Hyper V and ESXi on the hosts side.**********  Thanks in advance.  ~Taz
VNX pool considerations when migrating from other storages