HP StorageWorks P9000 Command View Advanced Edition Suite Software 7.1 Administrator Guide (web) (TB581-96050, May 2011)

SolutionProblem and causeNo.
Perform the following procedure to restore the consistency between the
database information and the storage system status:
1. After restarting the P9000 Command View AE Suite product services,
refresh all storage systems by using Device Manager.
2. If a migration task was being created or canceled during an abnormal
termination of the Tiered Storage Manager server, perform the cre-
ation or cancellation again. If an error occurred while a migration
was being canceled, refresh the storage system.
If a migration task that is being executed has failed, refresh the stor-
age system again. After that, take action as described below accord-
ing to the task status.
If data was not deleted:
The migration is complete, and the LDEV numbers of the migration source
and destination have been reversed. Check the status of the source volume
that has the destination volume LDEV number. If data was not deleted, the
original data remains on the source volume that has the destination volume
LDEV number.
The following action is required:
If the volume that has the destination LDEV number is blocked:
Use Remote Web Console.
If the volume that has the destination LDEV number is not blocked:
The data on the volume might not have been deleted. If the data must be
deleted, either format the volume or use the procedure below to delete
the data. Note that the following procedure assumes that LDEV 10:01
has been migrated to LDEV 20:01. (Also note that the LDEV numbers of
the volumes have been reversed.)
1. Set a path to LDEV 20:01, and allocate it to a host.
2. From the host, write 0 for the size of the volume to delete any data
remaining on LDEV 20:01.
3. Remove the path to LDEV 20:01.
If a migration failed:
Depending on the cause of the error, even if migration processing has
been completed in the storage system, Tiered Storage Manager or Device
Manager might treat the processing as having failed. As such, do the
following:
1. Use Device Manager to refresh all storage systems, and update the
management information in Tiered Storage Manager and Device
Manager. If reserved volumes remain, their reservation is canceled
during refresh processing.
2. Display the volume information for the migration task that is in the
failed status, and check whether the volumes have already been mi-
grated. Also, check the parity group names and storage system names
of all LDEVs in the migration group.
3. If there are LDEVs that have not been migrated yet, remove the cause
of the error, and then re-create and execute the migration task.
PROBLEM: An
inconsistency exists
between the database
information and the
storage system status.
CAUSE: Possible causes
are as follows:
• The Tiered Storage
Manager server ter-
minated abnormally
due to a forced termin-
ation or an unexpec-
ted error.
• A failover occurred in
a cluster environment.
3
Administrator Guide (Web Version) 247