HP Storage Provisioning Manager (SPM) version 2.1 User Guide

The goal is to resynchronize the state of the SPM catalog with the state of the storage services and
volumes being managed.
When SPM has populated the “Signature State” field of each volume, SPM switches to Manual
Recovery mode. The user should take appropriate action based on the Signature State of each
volume, which is found in SPM's volume list. The possible “Signature State” values of volumes
imported into SPM after internal recovery is complete, and actions the user may choose to take
are listed below.
Possible ActionInterpretationSignature State
These volumes are safe to remove from
quarantine.
This indicates volumes in the recovered
catalog that are unchanged from the time
the backup was performed.
Valid
The user should remove the volume from the
catalog or rewrite the management signature
This indicates that the management signature
on a volume was written by a newer version
of SPM.
Unsupported Version
to assert ownership by the current instance of
SPM.
The user should begin troubleshooting
procedures to determine the reason for the
This indicates that the management signature
on a volume is corrupted.
Corrupt
corruption before removing the volume from
quarantine.
These volumes may be used if desired, but
SPM cannot assert that these volumes are not
No management signature is being stored
for this volume. This could be because the
Not present
imported by some instance of a version ofvolume is hosted on an array that does not
SPM that did not write management
signatures.
support or is not enabled to write
management signatures, or the volume was
not imported into any SPM catalog.
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 (e.g. in the
case of a catastrophic loss of data).
This indicates volumes mentioned in SPM's
restored state that were last imported into
another instance of SPM.
Owning catalog mismatch
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
18 Getting started with SPM