HP Storage Provisioning Manager (SPM) Version 2.0 User Guide

in situations where archiving processes are in place and have saved all necessary data before
deleting the service.
• Recycle — On service deactivation, if the storage volume’s presentation was changed, then
the volume is unpresented. If the storage volume was created, then the storage volume will
be deleted – destroying the data it contains – and the capacity is returned to its containing
pool for future service provisioning requests. Any SAN zoning that was performed will be
removed as well. This policy is only to be used in situations where archiving processes are in
place and have saved all necessary data before deleting the service.
Storage Capability requirement
The Storage Capability requirement specifies the capabilities which a matching service must
be able to perform after it is provisioned (subject to available capacity). If a capability is not
specified as required, then it is optional whether a provisioned service will be able to perform the
operation after it is provisioned. For example, a Storage Capability requirement with a value
of “Thin Provisioning” matches only arrays that are capable of creating thinly-provisioned volumes.
Storage Pool Available Capacity requirement
The Storage Pool Available Capacity and Storage Pool Available Capacity
(percentage) requirements specify the amount of free capacity (non-committed available
capacity) which must exist in a pool after the provisioning request is completed. The amount of
free capacity can be expressed as a data size or as a percentage of the pool size.
This requirement enables the storage architect to control the amount of remaining free space that
must exist for provisioning to be performed from a pool.
This requirement is only enforced when a volume is created or grown, and evaluates as a Match
when the remaining free space in a storage template will be left after the provisioning is complete.
After provisioning, the requirement always evaluates as a Match (for example, the requirement
will not cause an existing volume service to become nonconformant because the required pool
free space was no longer satisfied).
Storage Pool Subscription Ratio requirement
The Storage Pool Subscription Ratio requirement specifies the ratio of subscribed
capacity of a pool to its physical capacity which must exist in order to create or grow a volume
within the pool. Because it is expressed as a ratio of the pool subscribed capacity, a value of “1”
means no oversubscription will be performed. A value of “2” means that new volumes will be
created in the pool up to twice the physical capacity of the pool. A value of “3” means triple, etc.
This requirement controls thinly provisioned volume creation and growth.
Storage Pool Volume Count requirement
The Storage Pool Volume Count requirement specifies the number of volumes in a pool.
This requirement can be used to control volume creation within a pool to keep a pool from becoming
overallocated.
Tag requirement
The Tag requirement specifies a tag which must exist on at least one resource (array, storage pool,
volume or network) within the matching service.
Use Resource requirement
The Use Resource requirement specifies a resource which must be included (or excluded) from
a service. Types of objects referenced can be: Volumes, Storage Pools, Arrays, or SANs. Storage
architects or administrators may use this requirement to ensure a given template only fulfills service
requests using a specific set of storage arrays.
26 Storage service policy