HP EVA-to-3PAR Online Import Migration Guide

on the destination 3PAR. The peer ports on the destination 3PAR system must be on adjacent
nodes: 0/1, 2/3, 4/5, or 6/7.
• Zone the source and destination systems together and make sure they are visible to each other
before zoning hosts to the destination system.
• Do not unzone the source and destination systems from each other until the data migration is
complete.
To create the zoning:
1. On the destination 3PAR storage system, configure two free ports as peer ports using adjacent
node pairs: 0/1, 2/3, 4/5, or 6/7.
a. Set the Port connection type to point.
b. Set the Port connection mode to peer.
2. Create two zones between the source EVA storage system and destination 3PAR storage
system, ensuring that one EVA host port is in the same zone with one 3PAR peer port.
Each zone should contain only two ports: one from each storage system. Adjacent 3PAR peer
nodes should be zoned to separate EVA controllers in a one-to-one mapping. For example:
Zone 1: Peer port on node 0 of the 3PAR storage system, and host port 1 on controller A of
the EVA
Zone 2: Peer port on node 1 of the 3PAR storage system, and host port 1 on controller B of
the EVA
3. Verify that the EVA can detect both ports on the 3PAR.
Ensure that the peer port WWNs appear in the discovered port list. Alternately, verify that
the EVA is shown as a connected device on both peer ports of the destination 3PAR storage
system.
Zoning a host to the destination 3PAR storage system
The migration process requires each host involved in the migration to be zoned to the destination
3PAR storage system. Paths must be created from the host to the destination 3PAR storage system.
For a host using the Online migration procedure (Linux/VMware/HPUX), zoning from a host to
the destination 3PAR storage system is performed as a pre-migration step. For hosts utilizing the
Minimally Disruptive migration procedure (Windows/AIX), this zoning is performed during the
migration process. For details on migrating from a Windows host, see “Reconfiguring the Windows
host DSM” (page 10)
Identifying source and destination storage systems
NOTE: An EVA should be selected as a source only if it is being managed by Command View
10.3.2. If a Command View 10.2 instance is included in the same management group with
Command View 10.3.2, the Add a Source Storage System screen displays EVAs for both Command
View 10.3.2 and Command View 10.2. To determine the version of a Command View instance
before selecting a source array, perform the following steps
1. In the settings point of view, determine if there are multiple instances of Command View.
2. If there are multiple instances, select each instance and check the Version/Build on the
Command View Management Properties page.
3. If the Version/Build is 10.1 or prior, note the IP address.
4. On the HP EVA to 3PAR StoreServ Online Import GUI pages check the IP addresses of the
Management Server for each array.
The source and destination storage systems that will be made available for HP EVA to 3PAR
StoreServ Online Import data migration must be identified before a migration can be performed.
This involves the following steps:
12 Preparing for data migration