Home > Storage > PowerStore > Databases and Data Analytics > Dell PowerStore Metro Node with Oracle > Provision PowerStore volumes for metro node and Oracle ASM
For highly available storage in a metro node Local or Metro configuration, identical storage must be provisioned in both PowerStore arrays that are used by metro node. Metro node will create a mirrored device from the matching pair of PowerStore volumes existing on both PowerStore arrays. From this mirrored device, a virtualized volume will be created in metro node. The virtualized volume in metro node will then be exposed to the database server for standalone Oracle, or to multiple database servers in an Oracle RAC Standalone Cluster environment. The provisioning process for the metro node virtualized volume for Oracle ASM in a standalone database or Oracle RAC Standalone Custer is the same as for PowerStore storage volumes.
For an Oracle standalone database in a metro node Local configuration, the PowerStore volumes targeted for Oracle and residing on both PowerStore arrays, must be provisioned to the metro node Local cluster residing at that same site. See Figure 3 and Figure 7.
For an Oracle RAC Standalone Cluster in a Metro configuration, the PowerStore volumes targeted for Oracle and residing on the PowerStore array at site A must be provisioned to the metro node Metro cluster residing at site A. The PowerStore volumes targeted for Oracle and residing on the PowerStore array at site B must be provisioned to the metro node Metro cluster residing at site B. See Figure 4 and Figure 8.
The initial configuration of the PowerStore host object that corresponds to the Metronode cluster is out of scope for this document as it was configured during the initial deployment of Metronode. For additional information, see References.
Use a consistent naming standard for storage volumes and supporting components in metro node. The naming convention used in our lab for PowerStore volumes included the following and may not be appropriate for all environments:
Note: Having the same LUN ID on the matching pair of PowerStore volumes is not necessary but it is highly recommended because it will help with administration and ensure LUN ID consistency in the environment.
Use a standard for assigning LUN IDs throughout the environment. See Table 1 for the LUN ID assignments used in our lab environment.
LUN ID | ASM disk group intention |
Grid CRS/OCR | |
21, 22, … | DATA |
31, 32, … | hammerDB |
41, 42, … | FRA |
51, 52, … | REDO |
61, 62, … | ARCH |
After the PowerStore storage volumes are presented to metro node, make note of the WWN and LUN ID of the PowerStore volumes on both arrays. In PowerStore Manager, perform the following steps on the PowerStore array members of the metro node cluster: