Network And Fabric Zoning Requirements; Volume Requirements; Remote Copy Requirements - HP 3PAR StoreServ 7200 2-node Manual

WARNING!
mpclaim CLI command or attempt to display the MPIO information via the Disk Management GUI
during the Peer Motion migration admitvv stage. Doing so will result in the host becoming
unresponsive.

Network and Fabric Zoning Requirements

The software runs as a client process on the host. Therefore, the host must remain connected
to the destination system during the data migration process.
Windows clusters are supported in minimally disruptive migration mode, and VMware ESX
clusters are supported in online migration mode.
There must be two unique paths between the source and destination systems. This means there
must be two separate nodes on the source connected to two separate nodes on the destination.
The nodes on the destination system must be an adjacent node pair: 0/1, 2/3, 4/5, or 6/7.
The nodes on the source system do not need to be an adjacent node pair.
A Fibre Channel switch is required. Only fabric connections on peer ports are supported.
The hosts and source system must use the same IP protocol version. Version IPv6 is not
supported.
The ports should be zoned 1:1 across the fabric. If nodes 0 + 1 are used on the source system
and nodes 0 + 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 connection is not important, but you should connect or zone the source and
destination systems together and make sure they are visible to each other before connecting
hosts to the destination system.
Do not disconnect the source and destination systems from each other until the data migration
is complete.
For more information, see the appropriate Implementation Guide at the following website:
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?
lang=en=us=101=SupportManual=64180=5044394=18964

Volume Requirements

The only limit to volumes that are migrated 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.

Remote Copy Requirements

Remote Copy is a data replication technology. It is intended to keep a consistent copy of a particular
volume or set of volumes on another array for recovery purposes, coping with catastrophic failures
of the primary array, or—if the arrays are in different sites—issues with the physical infrastructure
around the primary array.
The volumes that are being migrated 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 will
need to be manually reconfigured to use the new array after migration.
NOTE: See
60) for instructions on migrating secondary periodic Remote Copy volumes.
On Windows Server 2012, Windows Server 2008 R2 and non-R2, do not use the
"Migrating Secondary Asynchronous Periodic Remote Copy Volume Groups" (page
Network and Fabric Zoning Requirements 9