HP EVA to 3PAR StoreServ Online Import Migration Guide (T5494-96604, July 2013)

◦ Host set creation failed because data from destination storage system could not be fully
loaded
◦ Data from destination storage system could not be fully loaded
◦ Possible cause:
The destination storage system is busy and did not provide the required data within
the expected time.
–
– Network latency between server component and the destination storage system.
◦ Solution
IMPORTANT: It may be necessary to restart the HP EVA to 3PAR StoreServ Online Import
service to solve this problem. Contact HP Customer Support for assistance before attempting
to restart the HP EVA to 3PAR StoreServ Online Import service.
1. Verify that the destination storage system is not overloaded.
2. Identify and correct any network latency issues.
3. Retry the operation.
4. If the problem persists, restart the HP EVA to 3PAR StoreServ Online Import service.
• Migration failed due to insufficient capacity even though Capacity Check indicates OK
◦ Possible cause: The Capacity Check may not be able to determine accurately the capacity
available on the destination 3PAR storage system.
Solution: Check the migration history. The migration may have succeeded even though
insufficient capacity was indicated. If the migration failed, it will be necessary to ensure
adequate capacity is available on the destination 3PAR storage system before attempting
the migration again.
• A migration has stopped due to the failure of data transfer of one or more virtual disks
Possible cause: I/O latency on the source EVA due to heavy load or SAN switch is
overloaded.
Solution: Restart the migration when the load is less on the EVA or the corresponding
SAN.
◦
◦ Possible cause: The CPG on the destination 3PAR does not have enough space.
Solution: Free up enough capacity in the CPG or add more capacity to the CPG on the
destination 3PAR.
◦ Possible cause: The LUN number of the Virtual disk is already in use on the destination
3PAR for the corresponding host.
Solution: Make the required LUN numbers available on the host or reconfigure the host
to use new LUN numbers for the virtual disks that are being migrated.
◦ Possible cause: Fibre Channel connectivity between the source EVA and the destination
3PAR has either degraded (one path lost) or gone down.
Solution: Check cabling and ensure that the source virtual disks are visible to the 3PAR
through two distinct paths.
NOTE: When the problem has been solved, click Restart to continue the migration. This
does not restart ongoing or completed migration tasks, only the failed tasks.
35