HP 3PAR Peer Motion Guide

D Troubleshooting
The following describes troubleshooting for HP 3PAR Peer Motion data migration and the Peer
Motion Utility.
Troubleshooting Peer Motion Data Migration
If issues arise, you can access the event log through the HP 3PAR Management Console Event
Manager. Additionally, the HP 3PAR Management Console has a log file directory on the client
system. This directory is located at C:\Users\<userID>\InFormMC\log.
Very often, errors in data migration are caused by zoning issues. Verify the zoning status in the
HP 3PAR Management Console on the Summary tab, as shown in the following figure:
Migration Phase Issues
Troubleshooting a volume admit or import failure:
• Verify the destination system has no active paths from the host screen or using the CLI command,
showhost.
• Monitor the migration task from the task screen or using the CLI command, showtask, then
determine where the operation failed.
• If a failure occurs before the volume import stage, but after volumes have been admitted on
the destination system, it is possible to manually return the system to the pre-admit state. This
process is non-disruptive to the hosts provided the appropriate zoning and host multi-pathing
is performed. The host must have access to the volume through the source system.
NOTE: Unzoning operations are not required for Single Volume migration.
To return the system to its state before a volume admit failure:
1. On the fabric and host - If the host has already been unzoned from the source system
then rezone it back to that system and confirm that I/O is occurring on the source system.
2. On the fabric and host - Unzone the host from the destination system and verify that all
access to the volumes is now only through the source system.
3. On the destination system - Remove the VLUNs on the destination system for the volumes
admitted to the hosts.
4. On the destination system - Remove the admitted volumes from the destination system.
5. On the destination system - Remove the host from the destination system.
104 Troubleshooting