HP EVA-to-3PAR Online Import Migration Guide

Deleting virtual disks from the source EVA
Once the source virtual disks have been migrated to the destination 3PAR, they can be deleted
from the EVA. Use HP P6000 Command View to unlock and delete the migrated virtual disks.
What to do if the migration fails
• If a migration fails after data transfer to the HP 3PAR storage system is started, the migration
can be restarted without having to change the zoning (the host will retain access). For example,
a migration may fail due to excess load on the EVA source. If other parts of the migration
have succeeded, the load on the EVA may be reduced, allowing the failed migration to be
restarted successfully.
• If the customer has not started data migration and the host is still zoned to the EVA, the host
can just be disconnected from the 3PAR without disruption.
After a failed migration, to return the source EVA and destination 3PAR storage systems to their
original configuration, perform the following tasks:
Source EVA tasks
1. Unlock all the source virtual disks.
2. Re-present the source virtual disks to their original host(s).
3. Rezone the EVA to the original host(s).
Destination 3PAR tasks
1. Unzone the 3PAR from the host.
2. Delete the respective virtual volumes and virtual LUNs.
3. Delete the host if it did not exist before the migration.
Deleting virtual disks from the source EVA 33