HP 3PAR InForm Software Licenses - Manual (Page 11)

•
Note the World Wide Names (WWNs) of hosts connected to the source and destination
systems.
•
Note the InForm CLI Super user name and password for the source and destination systems.
•
Note the Names of volumes to be migrated from the source to the destination system.
•
Enabling the Peer Motion on the destination system requires a Peer Motion license.
•
For offline data migration, there can be no active LUNs on the host attached to the source
system.
•
Do not import a volume to the destination system that is also a member of a secondary Remote
Copy group on the destination system. There is a high probability 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.
Network and connection requirements and restrictions:
•
The script runs as a CLI client process on the host so the host must remain connected to the
destination system during the data migration process.
•
Only VMWare clusters are supported. There is no support for other clustered environments.
Host clusters that are not VMWare clusters cannot be migrated with the Peer Motion Manager
Software script.
•
There must be 2 unique paths between the source and destination systems. This means there
must be 2 separate nodes on the source connected to 2 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.
•
An FC 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 1:1 zoned 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.
nl
•
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.
The Peer Motion Manager Software Script
SCRIPT NAME
pmm
DESCRIPTION
Manages the migration of data from a source system to a destination system.
SYNTAX
pmm [options]
The Peer Motion Manager Software Script 11