I85PREP
⌘ K
Dell PowerStore Operate 2023 study materials
Dell PowerStore Operate 2023 study resources

Dell PowerStore Operate 2023: Storage Provisioning: Volumes, Volume Groups, and Hosts

Dell PowerStore Operate 2023 · Work through your exam, one topic at a time.

All guide sections

Storage Provisioning: Volumes, Volume Groups, and Hosts

This domain follows the provisioning chain end to end: initiator, host, host group, volume, volume group, protection policy, and mapping. Most exam items here are about which object owns which behaviour.

Objects and rules

  • Volumes are thin-provisioned block devices owned by one node of one appliance, reachable through both nodes of that appliance using ALUA-aware multipathing. A volume cannot be shrunk after creation.
  • Hosts represent initiator sets: FC WWPNs, iSCSI IQNs, or NVMe NQNs. A host may hold several initiators, but a single initiator cannot belong to two hosts.
  • Host groups bundle hosts that need identical access, typically cluster nodes. Map to the host group and every member inherits the mapping.
  • Volume groups bundle volumes for atomic snapshots and replication. All members must be on the same appliance, and a volume belongs to at most one group.
  • Mapping assigns a volume to a host or host group with a LUN ID. The same volume can carry different LUN IDs on different hosts, so standardise them for the application's sake.

Order of operations

  1. Confirm initiators are logged in (zoning complete, CHAP configured).
  2. Create the host and verify connectivity in PowerStore Manager.
  3. Create volumes, then the volume group.
  4. Attach a protection policy for snapshots and replication.
  5. Map to the host or host group, then rescan the host.

Worked example

A two-node database cluster needs five volumes, consistent snapshots, and identical LUN IDs on both servers. Reasoning: create the five volumes on one appliance, place them in a single volume group so snapshots are consistent across all five, create one host per server from its HBA WWPNs, place both hosts in one host group, and map the volume group once. Assigning LUN IDs once at the group level avoids the classic mismatch where the same volume lands on a different LUN per node.

Traps

  • Mapping to individual hosts instead of the host group, so a newly added cluster member sees nothing.
  • Trying to combine volumes from two different appliances in one volume group; the UI rejects it.
  • Reusing a LUN ID already consumed on that host.
  • Setting snapshot rules per volume while also applying a group policy, producing an unpredictable schedule.
  • Expecting to shrink a volume or to flip thick/thin after creation.