HP Online Import Software manual Restarted Migration Showed Incorrect Failed Status

Restarted Migration Showed Incorrect FAILED Status

Problem: If a migration failed and it has been restarted using the HP 3PAR Online Import Utility startmigration command again, the status will immediately change to IMPORTING. However, due to timing issues, the status may change back to FAILED for a short time before returning to

IMPORTING.

Solution: On a restarted migration, if an HP 3PAR Online Import Utility showmigration command shows FAILED status unexpectedly, wait 1–2 minutes and issue the HP 3PAR Online Import Utility showmigration command again. You should see the proper IMPORTING status. If the status continues to remain at FAILED, the migration has failed.

Migration Includes Unexpected LUNs and Hosts

Problem: When the SMI-S provider manages multiple EMC VMAX Storage systems, LUNs with same devid or a host with the same name can result in the createmigration command migrating unexpected LUNs and hosts.

Workaround: SMI-S provider used during migration should only manage VMAX that is being migrated.

Masking View Required for Offline Migration of LUN with No Host

Problem: If you are migrating a LUN without a host, it still needs to be in a masking view in order to be successfully migrated.

Workaround: The LUN must be added to a storage group and the storage group must be part of a masking view on the EMC VMAX Storage system.

HP 3PAR Online Import Utility for EMC Storage does not distinguish between source arrays when managing same host

Problem: The SMI-S provider is managing more than 1 array which have the same host in different storage groups on each array.

This problem occurs when OIU asks SMI-S provider to retrieve host information and if there is the same host on 2 arrays, you will get LUNs on both source arrays.

Workaround: The SMI-S provider should not manage multiple arrays where the same host is provisioned in different storage groups. In the case where SMI-S provider is installed only for migration, only the array being migrated should be added. In the case where SMI-S provider is already installed and being used by some other application, a separate SMI-S provider should be installed for the migration.

Troubleshooting Issues 101