Connecting devices for data migration, Requirements and restrictions – HP 3PAR Operating System Software User Manual
Page 10
2.
Verify the host can see the new paths and VLUNs from the destination system.
3.
Select the import parameters. You can change the import parameters for each volume by
enabling the user interface option to make setting changes.
4.
Verify that the import can proceed. If the import proceeds while both source and destination
systems are serving data, data corruption may occur. The status of the selected host ports on
the source system is checked. If any of the host ports on the source system are online, a warning
is issued but the migration can proceed.
5.
The migration manager monitors and displays the status of the migrating volumes. You must
refresh the screens.
WARNING!
Data corruption may occur if both the source and destination systems are serving
data.
Peer Motion Manager offline data migration user interface tasks:
1.
Select a volume on the source system. This volume cannot be exported to any host.
2.
Select the import parameters, Thinly-Provisioned Virtual Volume (TPVV) or fully-provisioned
virtual volume. You can change the import parameters for each volume by enabling the user
interface option to make setting changes.
3.
The Peer Motion Manager monitors and displays the status of the migrating volumes. You
must refresh the screens.
Connecting Devices for Data Migration
The Peer Motion Manager software runs on a Windows host connected to the destination system.
Both the source and destination systems must be connected to any hosts to be exported from the
source to the destination system. The destination system is connected by one or more FC connections
to the source system and appears as a host to the source system. This configuration allows volumes
to be exported to the destination system as if it were any host.
Requirements and Restrictions
Using the Peer Motion Manager Software script has requirements and restrictions.
General requirements and restrictions:
•
All of the
“Installation Requirements” (page 7)
must be satisfied.
•
The destination system must be running InForm OS version 3.1.1 or greater.
•
The source system must be running InForm OS version 2.2.4 or greater.
•
Note the Name and IP address of the source and destination systems.
10
Using the Peer Motion Manager Software