HP Storage Provisioning Manager (SPM) Version 2.0 User Guide
Table Of Contents
- HP Storage Provisioning Manager (SPM) Version 2.0 User Guide
- Contents
- 1 Introduction
- 2 Getting started with SPM
- 3 Importing storage into the storage catalog
- 4 Storage service policy
- Managing templates
- Service types
- Requirement types
- All Of requirement
- Any Of requirement
- Connected To Fibre Channel Endpoint requirement
- Connected To Network requirement
- Fibre Channel Initiator Endpoint requirement
- Fibre Channel Target Endpoint requirement
- Fibre Channel Host requirement
- Network Capability requirement
- RAID Level requirement
- Resource Existence requirement
- Service Deactivation Policy requirement
- Storage Capability requirement
- Storage Pool Available Capacity requirement
- Storage Pool Subscription Ratio requirement
- Storage Pool Volume Count requirement
- Tag requirement
- Use Resource requirement
- Volume Capacity requirement
- Volume Committed Capacity requirement
- Volume Creation Security Group requirement
- 5 Storage service provisioning
- 6 Managing storage catalog entities
- Managing arrays
- Viewing and modifying array properties (Overview tab)
- Viewing array storage pools (Storage Pools tab)
- Viewing array volumes (Volumes tab)
- Viewing array ports (Ports tab)
- Viewing array host entries (Hosts tab)
- Viewing and modifying array capabilities settings (Capabilities tab)
- Viewing and modifying array security settings (Security tab)
- Removing an array
- Managing storage pools
- Managing volumes
- Managing networks
- Managing security
- Resynchronizing resources
- Quarantining resources
- Managing arrays
- 7 Monitoring the storage catalog
- 8 Support and other resources
- A Troubleshooting
- Viewing operational logs
- Addressing common issues
- Storage Provisioning Manager issues
- SPM will not launch in browser
- The user is unable to login through the SPM user interface
- Issues with multiple SPM instances pointed to the same storage resources
- Cannot import 3PAR Storage Systems
- 3PAR SMI-S connection problems
- Service activation fails to present volumes on 3PAR arrays
- EVA arrays and/or XP arrays are marked as Offline when they appear to be functioning correctly outside of SPM
- HP Matrix OE storage pool issues
- Storage Provisioning Manager issues
- Backup and recovery
- Managed SAN
- Unmanaged SAN
- B Working with Brocade Fibre Channel networks
- C Working with EVA storage systems
- D Working with 3PAR storage systems
- Overview
- Understanding how to import 3PAR arrays into SPM
- Understanding 3PAR capacity reporting
- Understanding 3PAR Storage System volume creation/growth
- Understanding 3PAR Storage System virtual domains
- Exposing volume presentations in 3PAR Storage Systems
- Working with 3PAR Storage System host modes
- Presenting volumes on 3PAR Storage Systems
- Creating hosts on a 3PAR Storage System
- Working with 3PAR Storage System active VLUNs and VLUN templates
- Working with autonomic groups
- Volume migration (Tiering)
- Importing a large number of volumes
- Unique identification of common provisioning groups (CPG)
- E Working with HP P9000/XP Disk Array
- F Working with unmanaged networks
- G Working with unmanaged arrays
- H Units of measurement
- Glossary
- Index
legacy volumes can be assigned any supported RAID level. As explained later, this means SPM
must report raw capacity for concrete pools.
Common Provisioning Groups (CPG) are thin pools that are created within the scope of a concrete
pool. Intitially, a CPG’s capacity is always 0. CPGs are RAID-locked, meaning that volumes
provisioned in a CPG are always assigned the CPG’s RAID-level. But this doesn’t mean all volumes
in a CPG have the same RAID level because the RAID level of a CPG can be changed after which
point all newly provisioned volumes will be assigned the new RAID level.
CPGs support both thick provisioning and pure thin provisioning for volumes. CPGs draw capacity
from their concrete pool. The capacity allocated to a CPG grows when:
• A fully provisioned volume is created, in which case necessary disk space is allocated to the
CPG to account for the full size of the volume, RAID overhead and administrative overhead
• A thin volume is allocated, a small amount of disk space is allocated to cover administrative
overhead requirements
• When a host writes to a thinly provisioned volume, increasing its required space
When creating a CPG, a space limit can be specified. This limit indicates the maximum amount
of logical capacity that the system will let the CPG grow to. If the limit is not specified, then the
CPG is allowed to grow unbounded. The CPG space limit isn’t tied to the actual capacity of the
underlying concrete pool and may represent an unreachable value if there isn’t enough physical
disk space available as data stored on the array grows.
Calculating capacity for concrete pools is relatively straightforward:
3PAR calculation (concrete pools)SPM capacity value
Raw capacity of the disks associated with the pool.Physical capacity
The raw capacity actually used by legacy volumes and/or
thick and thin volumes allocated on CPGs defined on this
concrete pool.
Committed capacity
Calculated as the sum of all derived CPGs’ subscribed
capacities + all legacy volumes’ size + the space used for
Subscribed capacity
snapshots. Because SPM volumes capacity is always
reported as logical capacity, subscribed capacity is a
logical capacity.
The raw available capacity equals the physical capacity
minus the committed capacity of the pool. SPM reports the
Available capacity
logical available capacity which depends on the RAID level
chosen for the volume that will be created.
Capacity values for CPG based pools are calculated differently:
3PAR calculation (CPG based pools)SPM capacity value
Reported as logical capacity, it is the min of:
• Committed capacity plus the logical capacity of the
largest thick volume that could possibly be allocated on
the CPG given its RAID level
OR
• Space limit of the CPG
Physical capacity is variable because multiple CPGs can
draw capacity from the same concrete pool (for example,
Physical capacity
when a volume gets provisioned in a pool, that much
capacity becomes unavailable for other pools).
The logical capacity used by the CPG. This includes
volumes as well as snapshot and admin space (for
example, RAID overhead and cruft).
Committed capacity
64 Working with 3PAR storage systems