Home > Storage > PowerStore > Databases and Data Analytics > Dell PowerStore Metro Node with Oracle > Claim PowerStore volumes in metro node
After metro node scans the underlying PowerStore arrays for exposed storage volumes, metro node must make a claim against the PowerStore volumes before it can use them. In a Metro config, there must be a paired or like-purposed volumes existing between the PowerStore arrays, and these paired/like-purposed volumes must be claimed.
To claim the paired or like-purposed PowerStore volumes, set the metro node provisioning context to cluster-1 and perform the steps in this section. Then, set the metro node provisioning context to cluster-2 and repeat the steps in this section. (See Setting metro node Metro provisioning context).
Note: This section is repeated for both provisioning contexts cluster-1 and cluster-2. For brevity, only metro cluster-1 is shown.
Note: PowerStore arrays are identified in metro node by the PowerStore service tag. See PowerStore service tags for more information.
Note the message displayed by the wizard: “There are ‘n’ unclaimed storage volumes on PowerStore that do not require a Name Mapping file.”. In Metro node v7.0, the option Use a Name Mapping file to customize claimed storage volumes names is not supported for PowerStore arrays because this feature is intended for third-party arrays. Leave this box cleared.
Note: Use ctrl-click to select multiple storage volumes, or shift-click, to select a range of storage volumes. If the WWNs of the volumes to claim are unknown, refer to the section Provision PowerStore volumes for metro node and Oracle ASM to help identify the storage volumes. The Logical Unit Number will be needed when the metro node virtual volumes are exposed to the Oracle database server.
DellEMC-PowerStore-<PowerStore-service-tag>_LUN_<LUNID>
Although it is not necessary, it is recommended to change the default target volume name to make volume identification and management easier.
To change the name of the proposed metro node storage volume, click the name of the volume under the column To Be Named and change the name. In our lab, the naming convention included the PowerStore array name, PowerStore service tag, ORA tag and SID, ASM disk name, ASM disk number, and LUN ID.
Repeat this process on the other metro node cluster. After storage from both PowerStore arrays has been claimed, extents can be added to the metro node storage volumes in both metro clusters. Extents are the first layer of logical abstraction of the metro node storage volumes.