HP 3PAR Peer Motion Guide

◦ The Fibre Channel fabric between the source and destination arrays is capable of and
enabled for N_Port ID Virtualization (NPIV).
◦ If the destination array is running a release prior to HP 3PAR OS 3.1.3, is a T-Class or
F-Class system, or the cluster size is larger than four hosts, or the Fiber Channel fabric is
not capable of NPIV, then the MDM procedure must be followed.
• For single volume migration:
Both the source and destination arrays must be running at least HP 3PAR OS 3.1.3.◦
◦ The host(s) to which the volumes are exported to must be defined using an ALUA persona
on both source and destination arrays.
◦ The host(s) must be configured to use ALUA. Refer to host specific documentation for
enabling ALUA.
• When migrating volumes exported to Windows 2008 Server or Windows 2012 Server hosts,
ensure that the "Path Verify Enabled" setting is enabled on all the hosts.
◦ On Windows 2008, the setting can be found at Server Manager > Disk Management.
Right-click any of the 3PAR disks, then select MPIO tab > MS DSM Details. Select the
Path Verify Enabled checkbox.
◦ On Windows 2012, the setting can be found at Device Manager > Disk Drives. Right-click
any of the 3PAR disks, then select MPIO tab > MS DSM Details. Select the Path Verify
Enabled checkbox.
Restrictions
• For offline data migration, the volumes that are to be migrated from the source system must
not be exported to any host.
• Do not import a volume to the destination system that is also a member of a secondary Remote
Copy group on the destination system. A high probability exists that the virtual volume blocking
operation will fail and cause a volume import task failure.
• Wild cards are not supported.
• Virtual volume sets and patterns are not supported.
CAUTION: On Windows Server 2012 R2, Windows Server 2008 R2 and non-R2 you should
ensure that Microsoft hotfix KB2821052 is installed. If it is not, do not use the mpclaim CLI
command or attempt to display the MPIO information via the Disk Management GUI during the
Peer Motion migration admitvv stage, since these actions would result in the host becoming
unresponsive.
Fabric Zoning Requirements
• The HP 3PAR Management Console software runs as a client process on the management
host. Therefore, the host must remain connected to the destination system during the data
migration process. This also applies for HP 3PAR Peer Motion Utility.
• You must have two unique Fibre Channel paths between the source and destination systems.
In other words, 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.
Fabric Zoning Requirements 15