HP Storage Provisioning Manager (SPM) version 2.3 User Guide

Deleting CPGs
In the event a CPG was deleted, all volumes in the CPG end up being deleted, which is catastrophic
as it results in data loss and inability for the application to access their volumes. Fixing this is
beyond the scope of SPM, however, the storage administrator should:
1. Re-synchronize the corresponding pool in SPM
2. Re-synchronize all volumes in the pool. As deleting a CPG results in the deletion of all volumes
in that CPG, the Re-synchronize operation should result in putting all the volumes offline.
Backup and restore handling on HP 3PAR StoreServ Storage System
volumes
SPM supports backup and restore of HP 3PAR volumes by writing a management signature string
to every HP 3PAR volume managed by SPM. This string will be stored in the volume's Comment
field in the array. This field should not be modified manually using the HP 3PAR Management
Console or by other means. For more information, see “Backup and restore” (page 21).
Working with other HP 3PAR StoreServ Storage System features
The following provides important information on the operation of SPM with HP 3PAR StoreServ
Storage System features.
Peer Motion
SPM has limited support for Peer Motion. If Peer Motion is used on an HP 3PAR StoreServ Storage
System which is imported into an SPM catalog, a number of manual steps must be performed in
order to guarantee that SPM and Matrix can properly use the storage affected by Peer Motion.
For details on these steps, see the SPM 3PAR Peer Motion Technical White Paper at http://
www.hp.com/go/matrixoe/docs.
Peer Persistence
SPM does not support Peer Persistence. Other documentation may indicate that Peer Persistence
is supported by SPM with manual intervention, but those documents are incorrect. SPM cannot
import volumes that are part of a remote copy group, and cannot import two volumes that share
the same WWN. For this reason, SPM cannot be used to manage volumes in a Peer Persistence
configuration.
Persistent Ports
SPM supports the Persistent Ports feature available in HP 3PAR OS 3.1.2. If the persistent ports
feature is activated on an HP 3PAR StoreServ Storage System which is imported into an SPM
catalog, the activity of the persistent ports feature generally will not affect SPM.
Adaptive Optimization
SPM service requests must not mandate a specific RAID level when 3PAR Adaptive Optimization
and SPM are used concurrently. If a RAID level is specified, services may be nonconformant when
Adaptive Optimization operates on the volume associated with that service.
• Provision services whose requirements either do not specify a RAID level or specify a RAID
level as Recommended.
• The storage administrator should set the RAID Level as None in storage pool entries and as
Any in Matrix IO templates.
88 Working with HP 3PAR StoreServ Storage Systems