beautypg.com

16 using the peer motion manager – HP 3PAR Operating System Software User Manual

Page 244

background image

16 Using the Peer Motion Manager

The HP 3PAR Peer Motion Manager enables users to perform the following Peer Motion operations:

Display the source and destination configurations.

Display volumes that are to be migrated, admitted, and imported.

Display hosts, users, and domains that are to be migrated.

Display the LDAP configuration if it is available.

Create a Peer Motion configuration.

Copy storage settings and configurations from the source system to the destination system.

Migrate Data.

Import Volumes.

Remove Peer Volumes.

Remove a Peer Motion configuration.

Provide all the functionality of the Peer Motion Manager 1.2 CLI script.

The following are the limitations of the Peer Motion Manager:

It is not an end-to-end wizard; some operations are needed to perform Peer Motion.

There are no automatic steps for zoning and unzoning the source and destination systems.

Peer Motion Manager does not display source system data if the source system is not an HP
3PAR Storage System.

You must connect to both systems to perform most of the Peer Motion Manager operations.

EVA-to-3PAR data migration is not supported.

All commands and wizards require that you have the Super user role on the source and destination
systems, a Peer Motion License, and other applicable licenses. For more information, see the
following sections:

“Creating a Peer Motion Configuration” (page 245)

“Copying Storage Settings and Configurations” (page 249)

“Migrating Data ” (page 251)

“Importing Volumes” (page 254)

“Removing Peer Volumes ” (page 256)

“Post Migration Cleanup ” (page 257)

“Removing a Peer Motion Configuration ” (page 258)

“Viewing a Peer Motion Configuration” (page 260)

“Viewing Port Information” (page 264)

“Viewing Storage Settings and Configurations” (page 267)

“Viewing Migration Data Information” (page 271)

“Viewing Source and Destination Systems” (page 279)

“Viewing Available Storage Systems” (page 283)

244 Using the Peer Motion Manager