HP Storage Provisioning Manager (SPM) version 2.2 User Guide

Possible ActionInterpretationSignature State
Management signatures are supported on
HP 3PAR StoreServ Storage Systems and HP
P6000/EVA arrays.
These volumes may be used if desired, but
SPM cannot assert that these volumes are not
This indicates volumes mentioned in SPM's
restored state that are not known to be
Not present with changes
since recovery
imported by some instance of a version ofmanaged by any instance of SPM since they
SPM that did not write management
signatures.
do not have a management signature, and
which had different properties recorded in
the restored state than they have at recovery
time.
The user generally should not import these,
but can force an import if desired (for
This indicates volumes mentioned in SPM's
restored state that were last imported into
another instance of SPM.
Owning catalog mismatch
example, in the case of a catastrophic loss of
data).
The user should resolve the discrepancy
before using such volumes, perhaps by
deactivating the bound service.
This means that SPM's restored state
indicates that a volume is bound to a service
while the management signature on that
Unexpected service
binding
volume indicates it is not bound to a service.
This may mean that the service was
deactivated since the most recent backup.
The user should use Matrix lsmanalyser, and
if that does not repair the issue, manually
This indicates that the management signature
on a volume states that a service was
Service Activation Level
Mismatch
update service requirements and rewrite theactivated in a different way than is recorded
in the restored SPM catalog. management signature before taking the
volume out of quarantine.
The user should resolve this difference before
removing the volume from quarantine,
This indicates that the management signature
on a volume states it is in use by a different
Service Mismatch
perhaps by deactivating the current serviceservice than is recorded in the restored SPM
catalog. in the catalog and activating a new service
on that volume.
Only volumes that exist on the arrays are given a state from the list above. Volumes that exist in
the recovered catalog but which do not exist on an array are marked offline. The user may need
to recreate services that were lost between the backup and restore times, and manually assign
Volumes to those services. For information on this process, see Manually assigning a volume to a
storage service.
When restoring from backup, SPM puts all volumes into quarantine, and the user must manually
take them out of quarantine as appropriate. If the management signature is not present, is corrupt,
or has changed since recovery, the user should manually inspect the volume to ensure it is safe to
bring out of the quarantine state. When the user has completed all desired manual actions in
response to the status of recovered volumes and is ready to begin normal operations, the user
should take SPM out of recovery mode by clicking on the item saying “Exit Manual Recovery”
displayed when SPM is in Manual Recovery mode.
Volumes that were imported into SPM after the most recent backup will not be in the SPM catalog
after the backup has been restored, and will not be handled by the procedures above. To recover
those volumes, the user must re-import them into SPM. The SPM import wizard indicates those
volumes that were previously owned by the current instance of SPM. These volumes are safe to
import. Volumes that are owned by other instances of SPM may or may not be safe to import,
depending on the current state of those instances of SPM.
20 Getting started with SPM