HP EVA-to-3PAR Online Import Migration Guide

Review the Linux Multipathing Configuration File
Use an online migration process to migrate a Linux host. Ensure that the host’s /etc/
multipath.conf file has entries for both the EVA and the 3PAR arrays and that the file is in
compliance with the latest version of the following documents:
HP Native Linux Device-Mapper Multipath for HP Storage Disk Arrays reference guide
HP 3PAR Red Hat Enterprise Linux and Oracle Linux Implementation Guide
HP 3PAR SUSE Linux Enterprise Implementation Guide
Pay particular attention to the defaults and the devices sections of the /etc/multipath.conf
file to ensure that all values are set according to the variant and version of Linux involved. This is
important if there have been multiple upgrades to the Linux server spanning across major versions,
that is, RHEL 4.x to RHEL 5.6 or newer.
Network and fabric zoning requirements
Data migration requires the necessary zoning to create paths between the source and destination
storage systems and any hosts involved in the migration. The data paths used are shown in Figure 1
(page 11).
Two unique paths must be zoned between the source and destination storage systems. To
create two paths, the two controller ports on the source EVA must be connected to two peer
ports on the destination 3PAR storage system. See “Zoning the source EVA to the destination
3PAR storage system (page 11).
Paths must be zoned between the host and destination 3PAR storage system. The time at which
these paths are created is determined by the type of host—Windows/AIX or others. For more
information, see “Zoning a host to the destination 3PAR storage system (page 12).
Paths must exist between the host and source EVA. These paths will be unzoned during the
migration.
Figure 1 Data migration zoning
Zoning the source EVA to the destination 3PAR storage system
The correct zoning must be created between the source EVA storage system and destination 3PAR
storage system at every stage of the migration operation. The following zoning rules apply:
There must be two unique paths between the source and destination storage systems. To create
two paths, the two controller host ports on the source EVA must be zoned to two peer ports
Review the Linux Multipathing Configuration File 11