HP EVA-to-3PAR Online Import Migration Guide

NOTE: For additional steps that might be required post migration, see “Post-migration tasks”
(page 32). These tasks must be considered during the planning process.
Considerations when migrating data
Before migrating data using HP EVA to 3PAR StoreServ Online Import, be aware of the following:
General
• HP recommends that a single host be migrated at a time, unless a cluster is being migrated,
in which all the hosts have to move at once.
• If available, a CPG of the same RAID level as the virtual disk being migrated is automatically
selected on the destination. Otherwise, the first CPG discovered will be presented as the
destination CPG. Only non-domain CPGs are used for migration.
• Only virtual disks presented to Fibre Channel hosts can be migrated. Virtual disks presented
to iSCSI or FCoE hosts must be migrated through the offline procedure in which all presentations
are removed prior to the migration . For more information, see “Migrating unpresented virtual
disks” (page 28)
• LUNs identified for migration should not be part of any other current application jobs. For
example, make sure the LUN is not part of a Replication Solutions Manager Job or a Data
Protector backup job.
• The limit for active offline migrations is 25. The limit for online migrations is 255.
• When a virtual disk on the source EVA is migrated, a management lock is installed to prevent
any unwanted management changes to the virtual disk during the migration. The Management
Lock remains on the virtual disk after the migration.
• Only one EVA storage system at a time can be attached as a source to the 3PAR destination
storage system.
• When migrating multiple EVAs to a single 3PAR array, compatible LUN numbering is required
and must be considered for each host that is migrated. If LUN numbers are overlapping, you
must renumber the LUNs on the source EVA prior to migration. For example, consider the
following:
◦ A host being migrated to a single 3PAR has LUN numbers 1-3 presented from the first
EVA
◦ A second EVA also has the same LUN numbers 1-3
The LUNs on the second EVA must be renumbered to a compatible numbering, such as 4-6
before migrating to 3PAR.
Considerations when migrating data 9