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

4 Post-migration tasks
System post-migration tasks
• If the boot LUN for a host server was migrated, the boot setting on the server/adapter must
be changed to point to the new 3PAR destination data paths.
Exporting migration job histories
You can export migration job histories in csv format to an external file to track data migrations.
1. In Command View, select the Settings point of view.
2. In the left navigation pane, select the HP EVA to 3PAR StoreServ Online Import instance.
The HP EVA to 3PAR StoreServ Online Import screen is displayed.
3. Under Migrations in Progress or Completed Migrations, click Export and follow the on-screen
instructions.
Network and fabric topology post-migration tasks
• Unzone the EVA source and the 3PAR destination storage systems.
Marking migrated hosts and volumes
For virtual disks and hosts, HP P6000 Command View provides a Comments field that is used in
HP EVA to 3PAR StoreServ Online Import to mark these objects after they have been migrated. If
a comment already exists, and the size of comment plus the Online Import-related comment exceeds
128 characters, the comment will not be updated. Otherwise, the Online Import-related comment
will be appended to the existing comment.
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 started the actual migration of data to the 3PAR storage system the migration
host will need to be shutdown during this process and then reconnected to the EVA. 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).
System post-migration tasks 29