HP EVA-to-3PAR Online Import Migration Guide (T5494-96606)

• Migration preparation failed
◦ Cause: The preparation process failed to admit volumes on the destination storage system.
Solution: Verify the following:
– The destination CPGs have enough capacity. If they do not, free up enough capacity
in the CPGs or add more capacity to the CPGs on the destination storage system.
– No duplicate volumes exist. This may occur if either a virtual volume with same name
or with the same WWN exists on the destination storage system.
– The required LUN number is available on the host object on the destination storage
system.
– The source volumes are visible to the destination storage system through both paths.
• Migration preparation failed
◦ Cause: The preparation process failed to create a host object on the destination storage
system.
Solution: Verify the following:
– The destination storage system is accessible.
– There is no other host on the destination storage system with a subset of HBA ports
of the host being created.
– There is no host on the destination storage system with a duplicate name but a
different HBA port.
– There is no host on the destination storage system with a duplicate name and a subset
of a HBA port with a different operating system. If a host pre-exists on the destination
storage system, verify that the operating system field contains the correct value.
Possible values are linux, windows2008, mswindows, hpux, ibmaix.
• An error message “Improper EVA to 3PAR StoreServ Online Import configuration, no source
storage system visible to the destination storage system. Please make sure zoning is proper
and retry the operation." is displayed on the confirm migration destination page
◦ Cause: The following are the possible causes:
– Incorrect peer port zoning is made with EVA storage system and 3PAR storage system
– EVA to 3PAR StoreServ Online Import does not realize zoning changes
◦ Solution : Verify the following:
– There is 1:1 mapping between EVA and 3PAR peer port connection. Also, no two
configured EVAs should be connected to one 3PAR storage system, and vice-versa.
– Since the EVA to 3PAR StoreServ Online Import server takes some time to realize
recent zoning changes, wait for minimum three minutes and retry.
• VMware: An error message "The lock protecting /vmfs/volumes/.... has been lost" is displayed
in the Tasks and Events section in a vSphere client session
◦ Cause: This is likely due to high latencies experienced by the ESX host(s) during the
migration process.
◦ Solution : Refer to the “Load restrictions on EVA Nearline drives” (page 28) section for
load limitations in Nearline environments. Also, see VMware's KB article number:
1022119 for more information.
36 Troubleshooting