HP XP7 Command View Advanced Edition Administrator Guide (Web Version) (TK981-96004, May 2014)

3. If a migration task that is being executed has failed, refresh the storage system again. After that,

take action as described below according to the task status.

If the task status is DATA ERASURE FAILURE:

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,

and then take the appropriate action depending on the status. If data was not deleted, the original

data remains on the source volume that has the destination volume LDEV number.

• If the volume that has the destination LDEV number is blocked, use Remote Web Console to

format the volume.

• If the volume that has the destination LDEV number is not blocked, the data on the volume

might not have been deleted.

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 LUN path to LDEV 20:01, and allocate it to a host.

2. From the host, enter 0 for the size of the volume to delete any data remaining on LDEV

20:01.

3. Remove the LUN path to LDEV 20:01.

If the task status is MIGRATION FAILURE:

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 the storage systems, and update the management

information in Tiered Storage Manager and Device Manager.

If reserved volumes remain, their reservation is canceled during the refresh processing.

2. For the migration task that is in the failed status, display the volume information and check

whether the volumes have already been migrated.

Also, check the parity group names and storage system names for all LDEVs at the migration

source.

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.