I85PREP
⌘ K
Dell PowerMax Operate (DCA Operate) study materials
Dell PowerMax Operate (DCA Operate) study resources

Dell PowerMax Operate (DCA Operate): Provisioning and Storage Group Management

Dell PowerMax Operate (DCA Operate) · Work through your exam, one topic at a time.

All guide sections

Provisioning and Storage Group Management

Provisioning questions test the full path from "this application needs 8 volumes" to a host seeing the right LUNs, and the lifecycle rules that govern storage groups once they exist.

The provisioning path

  1. Check the pool first: SRP free, used and subscribed capacity, and the service level you intend to associate with the workload.
  2. Create thin devices in that SRP, for example symdev -sid 123 create -tdev -cap 500 -captype GB -noport.
  3. Add them to a storage group: symsg -sid 123 add -sg APP_PROD_SG dev <range>.
  4. Present them by creating a masking view that binds the storage group to an initiator group and a port group.
  5. Verify with symsg -sid 123 show APP_PROD_SG and confirm the SRP subscription delta matches the devices you created.

Storage group rules

  • A device can be in only one storage group; to move it, remove it from the current group before adding it to the other.
  • Storage groups can be nested (child groups added to a parent) so a single masking view can present many groups; the parent is what the masking view references.
  • Composite storage groups tie a local group to its remote counterpart and RDF group number, which is how SRDF operations act on both sides consistently.
  • A device cannot be deleted while it is still a member of a storage group, or while it is presented by a masking view.

Device attributes that matter

  • Emulation: FBA for open systems, CKD (3390/3380) for mainframe, with capacity expressed in GB/TB, cylinders or tracks.
  • Configure thin devices as non-presented (-noport) so nothing is exposed until the masking view is deliberate.

Worked example

An application needs 8 x 500 GB volumes on the Gold service level. You create eight 500 GB TDevs in the Gold SRP, add them to APP_PROD_SG, then bind that group into a masking view with the host's initiator group and the correct port group. SRP subscription increases by 4 TB while used capacity stays flat. If the request had specified Platinum, the fix is not a device attribute: you would have to create the devices in the Platinum SRP (or migrate them) because the service level comes from the pool.

Traps

  • Provisioning into the wrong SRP, which you cannot correct by editing the device.
  • Expecting volumes on the host before the masking view exists.
  • Deleting a device that is still in a storage group.
  • Forgetting that nested groups change which group the masking view must reference.