Preparing For Data Migration; System Requirements - HP 3PAR StoreServ 7200 2-node Manual

Hp 3par-to-3par storage peer motion guide (os 3.1.2 mu2) (ql226-97008, june 2013)
Hide thumbs Also See for 3PAR StoreServ 7200 2-node:
Table of Contents

Advertisement

2 Preparing for Data Migration

System Requirements

Installation Requirements
The following requirements must be satisfied to install Peer Motion:
There must be access to the HP Software Depot at http://www.software.hp.com.
The host computer must have access to the destination system.
The HP 3PAR user account must have Super user rights.
The source and destination systems must not already be in a Peer Motion configuration.
The following operating systems are supported:
Red Hat Enterprise Linux 6 Server
Red Hat Enterprise Linux 5 Server
Windows 7 Professional
Windows 7 Professional (Japanese)
Windows Server 2008 x64 Edition SP2
Windows Server 2008 x64 Edition SP1
Windows Server 2008 x64 Edition
Windows Server 2008 x64 Edition (Japanese)
Using Peer Motion has requirements and restrictions.
General Requirements and Restrictions
All of the installation requirements must be satisfied.
The source system must be running HP 3PAR OS version 2.3.1, 3.1.1, or 3.1.2, and the
destination system must be running HP 3PAR OS version 3.1.1 or 3.1.2. The source system
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.
Note the name and IP address of the source and destination systems.
Note the World Wide Names (WWNs) of hosts 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 to be migrated from the source to the destination system.
Enabling Peer Motion on the destination system requires a Peer Motion license.
For offline data migration, the volumes that are to be migrated from the source system must
not be exported to any host.
Importing to a thin volume requires a Thin Conversion license.
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 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.
For HP-UX and AIX, the destination system must be running HP 3PAR OS 3.1.2 MU2 or later.
8
Preparing for Data Migration

Advertisement

Table of Contents
loading

Table of Contents