HP 3PAR Peer Motion Guide

2 Data Migration Requirements
IMPORTANT: Before beginning migration, consult SPOCK (at http://www.hp.com/storage/
spock) to verify that the HP 3PAR OS versions on the hosts to be migrated are supported. Ensure
each host configuration that is to be migrated is supported with both the Source and Destination
arrays.
NOTE: If you are performing HP-UX migration, refer to “Additional Steps to Migrate HP-UX Hosts”
(page 89).
The following are requirements for data migration:
Peer Motion General Requirements and Restrictions
Requirements
• A management host running the HP 3PAR Management Console or Peer Motion Utility must
be available.
• The management host must have network access to the source and destination systems.
• The source and destination systems must not already be in a Peer Motion configuration.
• SPOCK should be consulted to ensure that the HP 3PAR OS versions on the hosts to be migrated
are supported. See http://www.hp.com/storage/spock.
• The source system must be running HP 3PAR OS version 2.3.1 or later. The source system HP
3PAR OS version must be the same or lower than that of the destination system. For example,
migration of a 3.1.2 array to a 3.1.1 destination is not supported.
• The destination system must be running HP 3PAR OS 3.1.2 or later. If the destination system
is running HP 3PAR OS 3.1.1, refer to the HP 3PAR Peer Motion Manager 1.1.0 Software
User's Guide.
• For HP-UX and AIX, the destination system must be running HP 3PAR OS 3.1.2 MU2 or later.
• Note the name and IP address of the source and destination systems.
• Note the Host HBA port World Wide Names (WWNs) that are connected to the source and
destination systems.
• Note the HP 3PAR Super user name and password for the source and destination systems.
• Note the names of volumes you want to migrate from the source to the destination system.
• Enabling Peer Motion on the destination system requires a Peer Motion license. The source
system does not require any special license.
• If the imported volume is intended to be a thinly provisioned volume on the destination system,
a Thin Provisioning license is required.
• If the migrated hosts or volumes are intended to be part of a domain on the destination system,
a Virtual Domain license is required.
• For Online Windows Cluster migration:
The destination system must be a HP 3PAR StoreServ 7000 or HP 3PAR StoreServ 10000,
and must be running HP 3PAR OS 3.1.3 or later.
◦
◦ Cluster sizes of up to four hosts are supported and the peer ports on the destination system
must be configured with twice as many NPIV ports as cluster hosts (for example, a two
node cluster requires that each peer port be configured with four NPIV ports).
14 Data Migration Requirements