HP 3PAR Peer Motion Guide

• The ports should be zoned 1:1 across the fabric. If nodes 0 and 1 are used on the source
system and nodes 0 and 1 are used on the destination system, the ports on source-0 and
destination-0 should be zoned together. The ports source-1 and destination-1 should be zoned
together in a separate zone.
• The order of zoning is not important, but you should zone the source and destination systems
together and make sure they are visible to each other before connecting hosts to the destination
system.
• The peer ports on the destination array have different node/port WWNs than host ports, so
zoning on the Fibre Channel fabric between the source and destination systems should only
be done after the ports are correctly configured.
◦ For all NPIV ports created, the NPIV port WWNs must be included in the zones created
between the source and the destination systems. The zones must also include the physical
peer port WWNs. NPIV port configuration and zoning applies only to Online Windows
Cluster migration.
• Do not disconnect the source and destination systems from each other until the data migration
is complete.
• For more information, find the appropriate Implementation Guide at:
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?
lang=en=us=101=SupportManual=64180=5044394=18964
Volume Requirements
The only limit to volumes you can migrate is that snapshots are not moved in a space-efficient
manner. They come across as new base volumes rather than as snapshots of their parents on the
destination system.
ALUA and Path State Change Detection Requirements
If the source and the destination arrays are both running at least HP 3PAR OS 3.1.3 it becomes
unnecessary to unzone the host from the source array before the migration begins. The arrays
communicate with each other and the paths from the source to the host are automatically reported
as standby to the host once data migration begins. As the host does not lose access to the source
array during the data migration process, it is possible to move only a subset of the volumes the
host sees from the source array to the destination array.
This requires that the host is configured to use an ALUA capable host persona on both the source
and destination arrays. If the source array is running an HP 3PAR OS release earlier than 3.1.3,
or if the host is not capable of using the ALUA information, or is configured on a non-ALUA persona,
then it will still be necessary to unzone the host from the source before beginning the data migration.
This will require migrating all the volumes that the host sees from the source to the destination.
Remote Copy Requirements
The volumes you are migrating cannot be in a Remote Copy relationship with the destination
system. The volumes can be involved in a Remote Copy relationship with another array, but they
need to be manually reconfigured to use the new array after migration.
NOTE: See “Peer Motion in a Remote Copy Environment” (page 85) for instructions on migrating
sync and async periodic Remote Copy volumes.
Pre-Migration Constraints
The source system in a Peer Motion operation should be running HP 3PAR OS 2.3.1 or later. The
destination system must run HP 3PAR OS 3.1.2 or later. The HP 3PAR E-Class and S-Class Storage
systems running HP 3PAR OS 2.3.1 are supported as source arrays only.
16 Data Migration Requirements