HP 3PAR Peer Motion Data Migration Guideh20628. · "ERROR: OIUERRDST0010 Unable to validate certificate for HP 3PAR Storage >

HP 3PAR Peer Motion Data Migration Guide

AbstractThis guide provides information on using HP 3PAR Peer Motion to migrate data from one HP 3PAR StoreServ Storage systemto another HP 3PAR StoreServ Storage system.

HP Part Number: QL226-98157bPublished: October 2015Edition: 2

© Copyright 2015 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP productsand services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed asconstituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Contents1 Overview of HP 3PAR Peer Motion................................................................6

Migration Types........................................................................................................................6How HP 3PAR Peer Motion Works..........................................................................................7

2 Data Migration Requirements.....................................................................11HP 3PAR Peer Motion General Requirements and Restrictions........................................................11Fabric Zoning Requirements.....................................................................................................13Volume Requirements..............................................................................................................14ALUA and Path State Change Detection Requirements..................................................................14Storage Foundation Requirements.............................................................................................14Remote Copy Requirements......................................................................................................15Pre-Migration Constraints.........................................................................................................15

3 Using Peer Motion in HP 3PAR Management Console Manager.....................17Creating an HP 3PAR Peer Motion Configuration........................................................................18

Select Systems...................................................................................................................18Set Up Connections............................................................................................................19

Show Port WWNs........................................................................................................21Port Configuration and Zoning........................................................................................22

Copying storage settings and configurations..............................................................................25Migrating Data......................................................................................................................26

Creating Peer Volumes........................................................................................................28Importing Volumes.............................................................................................................29

Online Data Migration Confirmation................................................................................30Minimally Disruptive Data Migration Confirmation.............................................................31

Importing Volumes wizard........................................................................................................31Selecting Peer Volumes.......................................................................................................32Removing Peer Volumes .....................................................................................................32

Post Migration Cleanup ..........................................................................................................33Removing a Peer Motion Configuration......................................................................................35Viewing a Peer Motion Configuration........................................................................................37

Summary Tab....................................................................................................................37Tasks Tab..........................................................................................................................38Alerts Tab.........................................................................................................................39

Viewing Port Information..........................................................................................................40The Summary Screen Detail Pane.........................................................................................40The Hosts Screen Detail Pane...............................................................................................42

Viewing Storage Settings and Configurations.............................................................................42Hosts Node.......................................................................................................................42

Storage Settings and Configuration Hosts Tab...................................................................43Storage Settings and Configuration Host Sets Tab..............................................................43

Security and Domains Node...............................................................................................44Security and Domains Node—Summary Tab....................................................................44Security and Domains Node—Users Tab..........................................................................45Security and Domains Node—Domains Tab.....................................................................46Security and Domains Node—Domain Sets Tab................................................................46Security and Domains Node—LDAP Tab..........................................................................46

Viewing Migration Data Information..........................................................................................47Available/Imported Hosts Tab.............................................................................................47Available/Imported Host Sets Screen....................................................................................49Available/Imported Linked Hosts Screen...............................................................................49Admitted/Importing Hosts Screen.........................................................................................49

Contents 3

Admitted/Importing Linked Hosts Screen...............................................................................50Available/Imported Volumes Screen.....................................................................................51Admitted/Imported Volumes Screen.....................................................................................51

Summary Tab...............................................................................................................52Settings Tab.................................................................................................................53Active VLUNs Tab..........................................................................................................54Hosts Tab.....................................................................................................................54

Viewing Source and Destination Storage Systems........................................................................54Summary Tab....................................................................................................................55Alerts Tab.........................................................................................................................56Ports Screen......................................................................................................................57

Viewing Available Storage Systems...........................................................................................59Migration Phase Issues............................................................................................................60

4 Using the HP 3PAR Peer Motion Utility.........................................................61Pre-Migration Tasks.................................................................................................................61Installing the HP 3PAR Peer Motion Utility..................................................................................62

System Requirements..........................................................................................................62Installation on a Windows System........................................................................................62Adding a CA signed certificate...........................................................................................68Upgrading on a Windows System........................................................................................68Installation on Linux Systems................................................................................................69Adding Users to Groups.....................................................................................................69Confirming Services...........................................................................................................70

Launching the HP 3PAR Peer Motion Utility.................................................................................70Using the HP 3PAR Peer Motion Utility Commands......................................................................70

HP 3PAR Peer Motion Utility Workflow..................................................................................71Online Migration ..............................................................................................................72

Online Windows Cluster Migration..................................................................................72Single VV Migration......................................................................................................73

Minimally Disruptive Migration ...........................................................................................74Offline Migration...............................................................................................................75Virtual Volume Set..............................................................................................................76

Consistency Group.................................................................................................................78Best Practices....................................................................................................................78Volume Based Migration.....................................................................................................79Host Based Migration.........................................................................................................79

LUN conflict autoresolve..........................................................................................................79HP 3PAR Peer Motion Utility Commands Quick Reference............................................................80Uninstalling the HP 3PAR Peer Motion Utility..............................................................................83

5 Post-Migration Tasks..................................................................................85System Post-Migration Tasks......................................................................................................85Fabric Topology Post-Migration Tasks.........................................................................................85Volume Post-Migration Tasks.....................................................................................................85Remote Copy Post-Migration Tasks............................................................................................85

6 Support and Other Resources.....................................................................86Contacting HP........................................................................................................................86HP 3PAR documentation..........................................................................................................86Typographic conventions.........................................................................................................87Documentation feedback.........................................................................................................87

7 Documentation feedback...........................................................................88A Peer Motion in a Remote Copy Environment.................................................89

Migration of a Primary System..................................................................................................89

4 Contents

Migration of a Secondary System.............................................................................................91B Additional Steps to Migrate HP-UX Hosts.....................................................93

Rescanning for New LUN Paths................................................................................................93HP-UX 11i V3.........................................................................................................................93HP-UX 11i V2.........................................................................................................................93Single-node Online Reconfiguration..........................................................................................93

C Data Migration for VMware vSphere ESXi hosts...........................................96D HP 3PAR Peer Motion Utility Commands......................................................97

help......................................................................................................................................97addsource.............................................................................................................................97showsource............................................................................................................................98adddestination.......................................................................................................................99showdestination....................................................................................................................101showconnection...................................................................................................................101createmigration....................................................................................................................103showmigration.....................................................................................................................105showmigrationdetails............................................................................................................107startmigration.......................................................................................................................107removemigration...................................................................................................................108removesource.......................................................................................................................108removedestination.................................................................................................................109installcertificate....................................................................................................................109showpersona.......................................................................................................................110

E Troubleshooting......................................................................................113Troubleshooting Peer Motion Data Migration............................................................................113

Migration Phase Issues.....................................................................................................113Troubleshooting HP 3PAR Peer Motion Utility............................................................................114

Index.......................................................................................................126

Contents 5

1 Overview of HP 3PAR Peer MotionHP 3PAR Peer Motion provides non-disruptive migration of a host and its data from a source storagesystem to a destination storage system. Throughout the migration process, I/O requests from allattached hosts continue to be serviced. Virtual volumes and system configuration information canbe copied to a new system with no changes to host configurations, no loss of access by a host toits data in an online migration, and a minimal downtime during a minimally disruptive migration.The peer motion process can be orchestrated using the HP 3PAR Management Console, whichruns on Windows or Linux management host. The management host must have managementnetwork connectivity to both the source and destination storage systems, but does not need anyaccess to the data being migrated. HP 3PAR Peer Motion with the HP 3PAR Management Consoleis supported when the destination storage system is running HP 3PAR OS 3.1.2 or later. For moreinformation, see “Using Peer Motion in HP 3PAR Management Console Manager” (page 17).Alternatively, the peer motion process can be orchestrated using the HP 3PAR Peer Motion Utility,which uses scripting commands to coordinate the migration. HP 3PAR Peer Motion with the HP3PAR Peer Motion Utility is supported when the destination storage system is running HP 3PAR OS3.1.1 or later. For more information, see “Using the HP 3PAR Peer Motion Utility” (page 61).

Migration TypesThere are three types of data migration:

• Online—With online migration, there is no disruption to the hosts and the data accessed bythe hosts remains available throughout the migration process. The destination storage systemnon-disruptively moves the volumes from the source storage system and completes the migrationwhile servicing I/O requests from the hosts.

◦ Host Level Migration—If the source storage system is running HP 3PAR OS 3.1.2 or earlierand the destination storage system is running HP 3PAR OS 3.1.3 or later, then all thevolumes exported to the host from the source storage system must be migrated to thedestination storage system together, and the host must be unzoned from the source storagesystem before the migration begins.

◦ Single Volume Migration—If both the source and destination storage systems are runningHP 3PAR OS 3.1.3 or later, then a subset (one or more) of the volumes exported to thehost can be migrated to the destination storage system. The host does not need to beunzoned from the source storage system during the migration process; it can concurrentlyaccess the volumes that have not been migrated from the source storage system and thevolumes that are in the process of, or have migrated to the destination storage system.

• Minimally Disruptive Migration—With Minimally Disruptive Migration (MDM), there is atemporary short duration disruption, as the host is removed from the source storage system,then reconfigured to use the destination storage system. However, the host is able to accessthe data through the destination storage system while data migration from the source todestination is occurring.

• Offline—With offline migration, volumes are not actively exported, and there is no access tothe data throughout the migration process. The volumes can be exported any time after themigration ends using the HP 3PAR OS export commands.

6 Overview of HP 3PAR Peer Motion

For a list of host OS that support single volume migration, see the HP SPOCK website:HP SPOCK

How HP 3PAR Peer Motion WorksPeer motion takes place in four stages:

• Interlinking source and destination storage systems

• Admitting volumes

• Importing volumes

• Completing post-migrationFigure 1 (page 7) shows a host that owns volumes on the source HP 3PAR StoreServ Storagesystem. The host is connected to the source storage system through FC and a SAN. The host hastwo HBAs connected to two adjacent controller nodes on the source storage system.The (potentially new) destination storage system is also online and visible over the network to aninstance of the HP 3PAR Management Console.

NOTE: Single fabric/single HBA configuration are also supported, but not recommended dueto the single point of failure that are inherent in those configurations.

Figure 1 Host is connected to the source array

To interlink the storage systems (see Figure 2 (page 8)), two FC ports are configured as peerports on the destination storage system and hooked up via the SAN to host ports on the sourcestorage system. The peer ports must be created on horizontally adjacent nodes on the destinationstorage system. On the source storage system, the host ports do not need to be on horizontallyadjacent nodes, but should be on different nodes. You can create peer ports in HP 3PARManagement Console or use the CLI command controlport.The ports for the array interlinks (blue lines) on the source storage system are standard host ports.They can even be host ports that are already in use by a host.Direct FC connect between destination storage system is not supported.

NOTE: HP 3PAR Peer Motion Utility is supported, if a host has only one HBA in the box.

Migration Types 7

http://www.hp.com/storage/spock

Figure 2 Interlinking source and destination storage systems

In the admit stage (see Figure 3 (page 8)), the volumes to be migrated are admitted to thedestination storage system. These admitted volumes appear as volumes in the HP 3PAR ManagementConsole for the destination storage system with 'peer' for their provisioning type. In this stage, thevolumes are defined and prepared on the destination storage system for export to the host. Nolocal storage is allocated for these volumes on the destination storage system at this point in time.The multipathing software on the host sees four paths to the same volume. Appropriate SCSIrescan/multipathing configuration must be performed on the host to pick up the additional pathsfrom the destination storage system.

Figure 3 Admit stage


In the import stage (see Figure 4 (page 9)), migration can start. During this stage, the host accessesthe volumes on the source storage system via the destination storage system. The host-issuedread/write I/O may see increased latency.For host-level migration, the hosts are prevented from directly accessing the volumes on the sourcestorage system by manually removing the zones for those paths.For single-volume migration, the hosts are prevented from directly accessing the volumes on thesource storage system by an automatic peer motion re-configuration of those paths from the activestate to the standby state.

Figure 4 Import stage

When all LUNs on the source storage system are migrated (see Figure 5 (page 10)), the sourcestorage system can be decommissioned or re-initialized.After migration has completed, all the data that was in the source volumes has been copied tonew destination volumes. At this point, all host-issued read/write I/O is serviced directly on thenew destination volumes.

Migration Types 9

Figure 5 Migration complete


2 Data Migration Requirements

IMPORTANT: Before beginning migration, consult HP SPOCK to verify that the HP 3PAR OSversions on the hosts to be migrated are supported:http://www.hp.com/storage/spock

NOTE: If you are performing HP-UX migration, see “Additional Steps to Migrate HP-UX Hosts”(page 93).

HP 3PAR Peer Motion General Requirements and Restrictions

Requirements• A management host running the HP 3PAR Management Console or HP 3PAR Peer Motion

Utility must be available.• The management host must have network access to the source and destination storage systems.

• The source and destination storage systems must not already be in a peer motion configuration.

• Consult HP SPOCK to ensure that the host OS versions to be migrated are supported:http://www.hp.com/storage/spock

• The source storage system in a peer motion operation should be running HP 3PAR OS 2.3.1or later. The source storage system HP 3PAR OS version must be the same or lower than thatof the destination storage system. For example, migration of an HP 3PAR OS 3.1.2 sourcestorage system to an HP 3PAR OS 3.1.1 destination storage system is not supported. In somecases, HP 3PAR Peer Motion Utility can be used when the source storage system is HP 3PAR3.2.1 MU2 and destination storage system is HP 3PAR 3.2.1 MU1. However, it isrecommended to migrate to the same MU or newer.

• The destination storage system must be running HP 3PAR OS 3.1.2 or later. When using theHP 3PAR Management Console, the minimum OS level for destination storage system mustbe 3.1.2 or later. When using HP 3PAR Peer Motion Utility, the minimum OS level for thedestination storage system is 3.1.1.

• The destination storage system must run HP 3PAR OS 3.1.2 or later. The HP 3PAR E-Classand S-Class storage systems running HP 3PAR OS 2.3.1 are supported as source storagesystems only.

• For HP-UX and AIX, the destination storage system must be running HP 3PAR OS 3.1.2 MU2or later.

• Remote copy groups and their synchronization tasks that exist on the source storage systemare not created by peer motion on the destination storage system; this has to be done manually.

• Only point connections (also known as fabric connections) between the destination and thesource storage systems are supported. Direct FC connections are not supported. iSCSI is alsonot supported to interconnect the systems. The speeds of the FC ports do not need to be thesame.

• Make a note of the name and IP address of the source and destination storage systems.

• Make a note of the host HBA port World Wide Names (WWNs) that are connected to thesource and destination storage systems.

• Make a note of the HP 3PAR Super user name and password for the source and destinationstorage systems.

HP 3PAR Peer Motion General Requirements and Restrictions 11



• Make a note of the names of volumes you want to migrate from the source to the destinationstorage system.

• Enabling HP 3PAR Peer Motion on the destination storage system requires HP 3PAR PeerMotion Software license. The source storage system does not require any special license.

• If the imported volume is intended to be a thinly provisioned volume on the destination storagesystem, an HP 3PAR Thin Provisioning Software license is required.

• If the migrated hosts or volumes are intended to be part of a domain on the destination storagesystem, an HP 3PAR Virtual Domain Software license is required.

• If the host persona being used on the source HP 3PAR storage system for the hosts to bemigrated is not supported on the HP 3PAR OS running on the destination storage system, thepersona being used on the source storage system must be changed to a common personasupported by the HP 3PAR OS versions on both the source and destination storage systems,prior to initiating the migration process.

• Migrating data from a VMware vSphere, ESXi host(s) on a source array running HP 3PAR OS3.1.1 to an HP 3PAR storage array running HP 3PAR OS 3.2.1 requires that the host personaon the destination storage system to be changed to persona 11. For more information aboutadditional steps, see “Data Migration for VMware vSphere ESXi hosts” (page 96).

• Thin Reclamation may not work while the migration is in progress. Thin Reclamation functionalityis restored according to the provisioning type chosen after the migration completes.

• If the imported volume is intended to be a thinly deduped volume, use SSD CPG on thedestination storage system.

• For online windows cluster migration:

The destination storage system must be an HP 3PAR StoreServ 7000 Storage or HP 3PARStoreServ 10000 Storage, 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 destinationstorage system must be configured with twice as many NPIV ports as cluster hosts (forexample, a two node cluster requires that each peer port be configured with four NPIVports).

◦ The FC fabric between the source and destination storage systems is capable of andenabled for N_Port ID Virtualization (NPIV).

◦ If the destination storage system is running a release prior to HP 3PAR OS 3.1.3, is aT-Class or F-Class system, if the cluster size is larger than four hosts, or the Fiber Channel


fabric is not capable of NPIV, then the Minimally Disruptive Migration procedure mustbe followed.

• For single volume migration:

Both the source and destination storage systems must be running HP 3PAR OS 3.1.3 orlater.

◦

◦ The hosts to which the volumes are exported to must be defined using an AsymmetricLogical Unit Access (ALUA) persona on both source and destination storage systems.

◦ The hosts must be configured to use ALUA. See host-specific documentation for enablingALUA.

• When migrating volumes exported to Windows 2008 Server or Windows 2012 Server hosts,ensure that the Path Verify Enabled setting is enabled on all the hosts.

◦ On Windows Server 2008, the setting can be found at Server Manager→DiskManagement. Right-click any of the HP 3PAR disks, then select MPIO→MS DSM Details.Select the Path Verify Enabled check box.

◦ On Windows Server 2012, the setting can be found at Device Manager→Disk Drives.Right-click any of the 3PAR disks, then select the MPIO→MS DSM Details. Select the PathVerify Enabled check box.

Restrictions• For offline data migration, the volumes that are to be migrated from the source storage system

must not be exported to any host.• Do not import a volume to the destination storage system that is also a member of a secondary

remote copy group on the destination storage system. There is a high probability that thevirtual volume blocking operation might fail and cause a volume import task failure.

• Wild cards are not supported.

• Virtual volume sets and patterns are not supported.

CAUTION: On Windows Server 2012 R2, Windows Server 2008 R2, and Windows Server2008 (non-R2), you should ensure that Microsoft hotfix KB2821052 is installed. If it is not, do notuse the mpclaim CLI command or attempt to display the MPIO information via the Disk ManagementGUI during the peer motion migration admitvv stage, since these actions would result in the hostbecoming unresponsive.

Fabric Zoning Requirements• The HP 3PAR Management Console software runs as a client process on the management

host. Therefore, the host must remain connected to the destination storage system during thedata migration process. This also applies for HP 3PAR Peer Motion Utility.

• You must have two unique FC paths between the source and destination storage systems. Inother words, there must be two separate nodes on the source connected to two separate nodeson the destination. The nodes on the destination storage system must be an adjacent nodepair: 0/1, 2/3, 4/5, or 6/7. The nodes on the source storage system do not need to be anadjacent node pair. The best practice for the source storage system is to select and enableHP 3PAR Peer Persistence on adjacent nodes and partner ports.

• An FC switch is required.

• Only fabric connections on peer ports are supported.• The ports should be zoned 1:1 across the fabric. If nodes 0 and 1 are used on the source

storage system and nodes 0 and 1 are used on the destination storage system, the ports on

Fabric Zoning Requirements 13

source-0 and destination-0 should be zoned together. The ports source-1 and destination-1should be zoned together in a separate zone.

• The peer ports on the destination storage system have different node/port WWNs than hostports, so zoning on the FC fabric between the source and destination storage systems shouldonly be done after the ports are correctly configured.

◦ For all NPIV ports created, the NPIV port WWNs must be included in the zones createdbetween the source and the destination storage systems. The zones must also include thephysical peer port WWNs. NPIV port configuration and zoning applies only to onlinewindows cluster migration.

• Do not disconnect the source and destination storage systems from each other until the datamigration is complete.

• For more information, find the appropriate Implementation Guide for the OS of your host at:http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en=us=101=SupportManual=64180=5044394=18964

Volume RequirementsThe only limit to volumes you can migrate is that snapshots are not moved in a space-efficientmanner. Therefore, the destination storage system snapshots expand into base volumes losing theirparent relationship.

ALUA and Path State Change Detection RequirementsIf the source and the destination storage systems are both running at least HP 3PAR OS 3.1.3 itbecomes unnecessary to unzone the host from the source storage system before the migrationbegins. The storage systems communicate with each other and the paths from the source to thehost are automatically reported as standby once data migration begins. As the host does not loseaccess to the source storage system during the data migration process, it is possible to move onlya subset of the volumes the host sees from the source storage system to the destination storagesystem.This requires that the host is configured to use an ALUA capable host persona on both the sourceand destination storage systems. If the source storage system is running an HP 3PAR OS releaseearlier than 3.1.3, or if the host is not capable of using the ALUA information, or is configured ona non-ALUA persona, then it will still be necessary to unzone the host from the source beforebeginning the data migration. This will require migrating all the volumes that the host sees fromthe source to the destination, at the same time.

Storage Foundation RequirementsAs of HP 3PAR OS 3.2.1 MU2 release, some Symantec Storage Foundation configurations aresupported for migration through HP 3PAR Peer Motion.For information about supported configurations or migration paths, refer HP SPOCK.


http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&contentType=SupportManual&docIndexId=64180&prodSeriesId=5044394&prodTypeId=18964

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&contentType=SupportManual&docIndexId=64180&prodSeriesId=5044394&prodTypeId=18964


IMPORTANT:• For online data migration with Symantec Storage Foundation, virtual peer ports must be created

while setting up the peer connections between the source and destination storage systems.For information about setting up connections for a peer motion configuration, refer “Set UpConnections” (page 19). Twice the number of virtual peer ports must be created as there arenodes in the cluster per peer port.For example, if migrating a two-node cluster, four NPIV ports must be created on each peerport. Enter 4 in the NPIV Port Count field of the Create PM Configuration screen, Figure 7 (page19). A maximum of a four-node cluster is supported.

In addition, the Single Volume Migration feature is not supported in Symantec Storage Foundationenvironments. This means that all Virtual Volumes exported to the host(s)/Cluster being migratedmust be selected for migration and that the paths to the source array must be removed beforestarting the data migration.After the migration is complete, HP recommends that the Storage Foundation UDID on the VirtualVolumes be updated to reflect the new array serial number of the destination storage system, duringthe next available maintenance window. Enter the following command to update the UDID writtenin the private region of the virtual volumes:vxdisk updateudid <device>

NOTE: Updating the UDID is an offline process and requires that the diskgroups be deportedbefore executing this command.

Remote Copy RequirementsThe volumes you are migrating cannot be in a remote copy relationship with the destination storagesystem. The volumes can be involved in a remote copy relationship with another storage system,but they need to be manually reconfigured to use the new storage system after migration.

NOTE: For instructions on migrating sync and async periodic remote copy volumes, see “PeerMotion in a Remote Copy Environment” (page 89) .

Pre-Migration ConstraintsThe following table indicates the HP 3PAR OS version that a particular platform must support tofunction as a source or destination storage system:

Table 1 Storage systems and HP 3PAR OS versions

HP 3PAR OS versionsSource and Destination Storage systems

3.1.3HP 3PAR T-Class Storage SystemHP 3PAR F-Class Storage SystemHP 3PAR StoreServ 10000 Storage SystemHP 3PAR StoreServ 7000 Storage SystemHP 3PAR StoreServ 7450 Storage System

3.2.1 or laterHP 3PAR StoreServ 7200c Storage SystemHP 3PAR StoreServ 7400c Storage SystemHP 3PAR StoreServ 7440c Storage SystemHP 3PAR StoreServ 7450c Storage System

3.2.1 with the supported storage systemHP 3PAR StoreServ 10000 Storage SystemHP 3PAR StoreServ 7000 Storage SystemHP 3PAR StoreServ 7450 Storage System

Remote Copy Requirements 15

Table 1 Storage systems and HP 3PAR OS versions (continued)

HP 3PAR OS versionsSource and Destination Storage systems

3.1.2 MU2HP 3PAR T-Class Storage SystemHP 3PAR F-Class Storage SystemHP 3PAR StoreServ 10000 Storage SystemHP 3PAR StoreServ 7000 Storage SystemHP 3PAR StoreServ 7450 Storage System

3.1.2HP 3PAR T-Class Storage SystemHP 3PAR F-Class Storage SystemHP 3PAR StoreServ 10000 Storage SystemHP 3PAR StoreServ 7000 Storage System

3.1.1HP 3PAR T-Class Storage SystemHP 3PAR F-Class Storage SystemHP 3PAR StoreServ 10000 Storage System


3 Using Peer Motion in HP 3PAR Management ConsoleManager

The HP 3PAR Peer Motion Manager within the HP 3PAR Management Console enables you toperform the following peer motion operations:

• Display the source and destination configurations.

• Display volumes that are to be migrated.

• 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 storage system to the destinationstorage system.

• Migrate data.

• Import volumes.

• Remove peer volumes.

• Remove a peer motion configuration.The following are the limitations of the Peer Motion Manager:

• The Peer Motion Manager is not an end-to-end wizard; some additional operations are requiredto perform peer motion. There are no automatic steps for zoning and unzoning the sourceand destination storage systems.

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

• Data migration from a non-HP 3PAR system to an HP 3PAR StoreServ storage system is notsupported using Peer Motion Manager.

All commands and wizards require that you log on to the source and destination storage systemwith a user account that has Super credentials, an HP 3PAR Peer Motion Software license on thedestination storage system, and other applicable licenses. For more information, see the followingsections:“Creating an HP 3PAR Peer Motion Configuration” (page 18)“Copying storage settings and configurations” (page 25)“Migrating Data” (page 26)“Importing Volumes wizard” (page 31)“Removing Peer Volumes ” (page 32)“Post Migration Cleanup ” (page 33)“Removing a Peer Motion Configuration” (page 35)“Viewing a Peer Motion Configuration” (page 37)“Viewing Port Information” (page 40)“Viewing Storage Settings and Configurations” (page 42)“Viewing Migration Data Information” (page 47)“Viewing Source and Destination Storage Systems” (page 54)“Viewing Available Storage Systems” (page 59)“Migration Phase Issues” (page 60)

17

Creating an HP 3PAR Peer Motion ConfigurationTo use the Create PM Configuration wizard, the following conditions are required:

• At least one available source storage system and destination storage system that are notalready in a peer motion configuration.

• Storage systems must meet all the requirements as listed in “HP 3PAR Peer Motion GeneralRequirements and Restrictions” (page 11).

• You must log on to the source and destination storage system with a user account that hasSuper credentials.

Perform the following tasks before using the wizard:

• Choose two host ports on the source storage system. (You will need this information to zonethe source and destination storage systems.)

• Configure the two host ports on the source storage system, if not already configured.The Create PM Configuration wizard guides you through the configuration of two peer ports onthe destination storage system.To create a peer motion configuration:1. Select Peer Motion in the Manager Pane.2. Select Available Storage Systems in the Management Tree.3. Click Create PM Configuration to open the Create PM Configuration wizard.

Select Systems

1. Click the source icon ( ) and select a source storage system.2. Click the <Destination> icon and select a destination storage system (Figure 6 (page 18)).

Figure 6 Selecting the source and destination storage systems

If you attempt to create a peer motion configuration between an encrypted source storagesystem and a non-encrypted destination storage system, a warning dialog box displays,indicating data migrated to the non-encrypted system will no longer be protected by encryption.

18 Using Peer Motion in HP 3PAR Management Console Manager

Click Yes to create the configuration, or click No to return to the Select Systems screen withthe destination storage system reset.

3. Click Next to open the Set Up Connections page.

Set Up Connections1. In the Set Up Connections pane, right-click to select a port on the destination storage system

that will become a peer port(Figure 7 (page 19)).

Figure 7 Selecting a port

2. Select Pick a pair for <destination port>, then select the port you want to be paired with thedestination port.

Creating an HP 3PAR Peer Motion Configuration 19

NOTE:• If the peer ports are not already configured, the NPIV Port Count will be blank. For online

cluster migration (Windows or Symantec), each physical peer port must have twoassociated NPIV ports for every host in the cluster. For example, to support a cluster withtwo hosts, enter an NPIV Port Count of four. The NPIV Port count must be a multiple oftwo and must be the same for both peer ports. The maximum number of NPIV portssupported as of 3.1.3 is eight per peer port and the maximum number of hosts supportedfor online cluster migration is four.

• If the peer ports are already configured, the NPIV port count reflects the number of NPIVports already created on the peer ports. You can increase the NPIV port count in orderto support a cluster with more hosts during online migration.

• At any time, you can view host and peer port WWNs by clicking on Show Port WWNsfrom the Set Up Connections screen (Figure 8 (page 20)).

• For more information about port WWNs, see “Show Port WWNs” (page 21).

Figure 8 Viewing host and peer port WWNs

3. Select Apply. This button is enabled when the port parameters are modified. If the paired portis online, the Confirmation dialog box displays (Figure 9 (page 20)), indicating that the portmust be set to offline. Click Yes to continue.

Figure 9 Confirmation dialog box


The Port Configuration and Zoning windows displays.

Show Port WWNsThe Show Port WWNs window displays the host port WWNs of the source storage system andthe peer port WWNs of the destination storage system. Use this information to zone the peer portsto the host ports.An expandable panel is associated with ports having NPIV ports created on them. Click the (+)icon next to NPIV Ports to view a list of NPIV ports and WWN details.

Figure 10 Show Port WWNs dialog with NPIV ports:


Figure 11 Show Port WWNs dialog without NPIV ports:

Port Configuration and ZoningThe Port Configuration and Zoning dialog box displays the port configuration results and thecorresponding port WWNs. An expandable panel is associated with ports having NPIV portscreated on them. Click the (+) icon next to NPIV Ports to view a list of NPIV ports and WWNdetails.


Figure 12 Port Configuration and Zoning dialog with NPIV ports


Figure 13 Port Configuration and Zoning dialog without NPIV ports

After zoning is complete, click OK, and click Verify Configuration when you return to the Set UpConnections screen.

NOTE: If NPIV peer ports were created, the NPIV port WWNs associated with each peer portmust be included in the same zone as the peer port WWN.

If the peer port configuration is successful, the Verify Configuration dialog box (Figure 14 (page24)) appears. Click OK to continue. If the peer port configuration is unsuccessful, resolve theproblem and restart the creation of peer ports.

Figure 14 Verify Configuration


Copying storage settings and configurationsTo use the Copy Storage Settings and Configurations wizard, the following conditions are required:

• Super user role

• Any valid peer motion configuration that has source and destination storage systemsThe wizard link is not enabled if the source system storage settings and configurations are alreadyconfigured or copied on destination system. This wizard allows you to copy the following storagesettings and configurations from the source storage system to the destination storage system:

• Domain sets

• Domains

• Host sets

• Hosts

• Users

• LDAP Configuration

• NTP Server configuration

• DNS Server Configuration

• Syslog Parameters

• SNMP ConfigurationWhen there is no domain license on the destination storage system and the source storage systemhas domains, a warning message displays, indicating that host sets, hosts, and users will be copiedto the <none> domain, and domain sets and domains will not appear.

NOTE:• Syslog parameters are copied from the source storage system to the destination storage system,

but the HP 3PAR Management Console has no syslog parameters management functionality.• The SNMP configuration is copied from the source storage system to the destination storage

system, but the HP 3PAR Management Console has no SNMP management functionality.Additionally, the user settings are not copied.

• The wizard link is disabled, if the source system storage settings and configurations are alreadyconfigured or copied on destination storage system.

To copy storage settings and configurations:1. Select Peer Motion in the Manager Pane.2. Select Peer Motion Configuration in the Management Tree.3. In the Common Actions panel, select Copy Storage Settings and Configurations. The Copy

Storage Settings and Configurations wizard appears (Figure 15 (page 26)).

Copying storage settings and configurations 25

Figure 15 Copy Storage Settings and Configurations

To copy storage settings and configurations from the source storage system to the destinationstorage system:1. Select the Copy all listed storage settings check box.2. Select each storage configuration you want to copy, if enabled.3. Click Next to go to the summary page. The settings and configurations you selected to copy,

and those previously copied appear.4. Verify your copy selections.5. Click Finish to complete the wizard.If the simple copy operation does not meet your needs, you can modify settings and configurationson the destination storage system, outside of the Peer Motion wizard. You can use the followingexisting HP 3PAR Management Console commands:

• Create/Edit domain

• Create/Edit domain set

• Create/Edit host

• Create/Edit host set

• Create/Edit user

• Create/Edit LDAP configuration

Migrating DataTo use the Migrate Data wizard, the following conditions are required:

• Super user role

• HP 3PAR Peer Motion Software license on the destination storage system

• Any peer motion configuration that includes a source and destination storage system whosestatus is Normal and that has no admitted or importing volumes.

Perform the following tasks before using the wizard:

• Configure the data migration process by using the Create PM Configuration wizard.

• Copy the desired settings from the source storage system to the destination storage systemusing the Copy Storage Settings and Configurations wizard.


• Determine the best time to do the data migration. (A period of low usage is best, as migrationincurs I/O latency.)

• If migrating a VMware vSphere ESXi host(s) from 3.1.1 to 3.2.1 or higher, review Appendix“Data Migration for VMware vSphere ESXi hosts” (page 96) for additional requirements andsteps.

The Migrate Data wizard (see Figure 16 (page 27)) guides you in migrating volumes from thesource storage system to the destination storage system.

Figure 16 Migrate Data—Welcome

The types of migration are as follows:

• Online Migration (Default)—Used to migrate virtual volumes that are exported to one or morehosts. Online migration supports the migration of all volumes, a subset of volumes, or a singlevirtual volume. Migrating either a single virtual volume or a subset of volumes is consideredas single virtual volume migration. With single virtual volume migration, the host and sourcestorage systems remain zoned.The following conditions are required to use online single virtual volume migration:

◦ Both source and destination storage systems should be running HP 3PAR OS 3.1.3, orlater.

◦ The host(s) to which the volumes are exported to must be defined using an ALUA personaon both source and destination storage systems.

If any of these requirements are not met, the migration type will require the migration of allvolumes exported to the host(s).

• Minimally Disruptive Migration—Used to migrate virtual volumes that are exported to one ormore hosts when the OS or multipath solution does not meet the requirements for onlinemigration. This migration type requires shutting down the host system(s) for a short period oftime. The destination storage systems must be running HP 3PAR OS version 3.1.2 or later.Minimally disruptive migration is applicable to Windows 2003, Windows 2008, or Windows2012 clusters when the requirements for Windows online cluster migration are not met. Forthe supported releases for online migration of Windows clusters, see the support matrix onHP SPOCK:http://www.hp.com/storage/spockWhen migrating Windows Server 2012 clusters, set maintenance mode on the cluster disksto clear SCSI reservations on these disks. Because the quorum disk cannot be set in maintenance

Migrating Data 27


mode, it should be set offline to clear the SCSI reservations. Then, you should shut down allof the cluster nodes.When migrating Windows clusters other than Windows Server 2012 clusters, shut down thecluster nodes. Doing this releases SCSI reservations on the cluster disks, including quorumdisks. For Windows 2003 clusters, this must be done before the "Create Peer Volumes" stepto ensure that the volumes can be correctly seen by the destination storage system.

• Offline Migration—Used to migrate virtual volumes that are not exported to a host. Exportedvolumes that you want to migrate must first be unexported to use offline migration. No unzoningor system shutdown is required.

NOTE: A warning message displays if either of the following licenses is missing:• Thin provisioning (needed to create a thin volume)

• Domain (needed to add the volumes to a domain that is not the <none> domain)

HP 3PAR Management Console does not support multi-array migration. HP 3PAR ManagementConsole version 4.7 supports migration with 1-Source to 1-Destination at single point in time.Further, a source storage system with a lower version than HP 3PAR OS version 3.2.2 can be peermotion configured to work with same destination storage systems having HP 3PAR OS version3.2.2 and storage systems in federation configuration. If this condition is not met, it will be treatedas 1-1 legacy. Autolun feature was introduced in HP 3PAR OS version 4.6. For more information,refer “Creating Peer Volumes” (page 28).To migrate data:1. Select Peer Motion in the Manager Pane.2. In the Common Actions panel, click Migrate Data. The wizard appears.If the peer host already exists on the source storage system, a warning message appears indicatingit must be cleaned it up before proceeding.

Creating Peer VolumesFigure 17 (page 28) shows the Migrate Data—Create Peer Volumes screen.1. Depending on your system, the system selects Online Migration, Minimally Disruptive Migration,

or Offline Migration.2. If the system is using online migration or minimally disruptive migration, select the Host, Host

Set, or Linked Hosts for which you want to migrate virtual volumes to the destination storagesystem.

Figure 17 Migrate Data—Create Peer Volumes screen


NOTE:• All virtual volumes exported to overlapping hosts (linked hosts) must be exported. For

example: VV1 is exported to Host1, VV2 is exported to Host2 and Host3, and VV3 isexported to Host1 and Host3. To migrate VV1, you must also migrate VV2 and VV3.

• The admitted online volumes are explicitly exported to the destination host with the sameLUN number used on the source. If a LUN with the same ID already exists on thedestination, the LUN Conflict Found dialog box appears. To export the VLUN to thedestination HP 3PAR StoreServ Storage system with the next available LUN ID, select theAuto LUN check box.

3. If the system is using offline migration, select the virtual volumes to migrate to the destinationstorage system and click Add.

4. Click Next to go to the Import Volumes page (recommended), or click Finish if you want tocheck the configuration and run the Import Volumes wizard later. If you click Finish, the peervolumes are created but do not contain any data until the Import Volumes step or wizard hasbeen completed. (To run the Import Volumes wizard, see “Importing Volumes wizard”(page 31).)

Importing VolumesTo import volumes:1. Select one or more virtual volumes to be configured during import to the <destination system>.2. Select allocation settings. You can assign Same As Source, Thinly Deduped, Thin, or Full

provisioning to the virtual volumes being imported. The default is Thin.• Same As Source—Each source volume will retain its current provisioning type when

imported. If you are importing virtual copies, this option assigns the parent volume'sprovisioning type to each copy. If your list of volumes contains a mix of Thin and fullyprovisioned volumes, that mix is retained upon import.

• Full—All source volumes will be migrated to fully provisioned volumes on the destinationstorage system.

• Thin—All source volumes will be migrated to thinly provisioned volumes on the destinationsystem.

• Thinly Deduped—All source volumes will be migrated to thinly deduped volumes on thedestination storage system.

NOTE: If you select a Thinly Deduped volume on the source storage system, and thedestination storage system does not support TDVV, a message to that effect is displayed andThinly Provisioned Virtual Volumes are created on the destination storage system.If you select a Thinly Provisioned volume on the source storage system, and the destinationstorage system does not support TPVV, a message to that effect is displayed and FullyProvisioned Virtual Volumes are created on the destination storage system.

3. Select a User CPG (required) and Copy CPG (optional).

NOTE: If there is no CPG available for the specified domain, you must exit the wizard andcreate the CPG first.

4. If you selected Copy CPG, you have the option of selecting the Create virtual copies afterimporting volumes check box.a. Select Suffix or Full Name.b. Enter a suffix or name in the text box.

Migrating Data 29

5. If not already selected, select the virtual volumes to be configured during import to the<destination system>, then click Add. (You can also add the virtual volumes one at a time.)

6. If you are using offline migration, click Finish to create the peer volumes and begin themigration.If you are using online migration or minimally disruptive migration, click Finish to create thepeer volumes.

To start the importing tasks for online migration, refer to “Online Data Migration Confirmation”(page 30).To start the importing tasks for minimally disruptive migration, refer to “Minimally Disruptive DataMigration Confirmation” (page 31).

NOTE: The admitted online volumes are explicitly exported to the destination host with the sameLUN number used on the source. If a LUN with the same ID already exists on the destination, apopup displays with an auto LUN check box. Select the auto LUN check box to export the VLUNwith the next available LUN ID on the destination host.

Online Data Migration Confirmation1. Configure the switch to zone the destination storage system to the host paths listed.2. Re-run a scan on the host systems to discover the new volume(s).3. Verify that the host paths to the destination storage system are active.

• Use OS/multipath centric commands to confirm that the correct number of paths are beingseen and that they are in an active and healthy state.

• Alternatively, the use the statvlun command on the destination storage system toconfirm that I/O is being directed to the destination paths for the volumes being migrated.

4. Use online migration to migrate virtual volumes that are exported to a host. The source storagesystem must be unzoned from the host systems to complete online migration.

NOTE: You must remove the stale device paths manually if the device paths are notautomatically removed by the operating system. You must also ensure that an active path isnot removed. For more information on removing stale devices, see the OS/multipathdocumentation.

Unzoning is not required in the following cases:

• Both the source and destination storage systems are running OS 3.1.3, or later.

• The volumes being migrated are assigned to an ALUA capable host(s) using an ALUAenabled host persona.

• The volumes are not involved in a Remote Copy relationship.5. Click Verify.

If the system zoning is correct, a confirmation message displays. If the zoning is incorrect, amessage displays describing the problem.

NOTE:Zoning changes might not immediately reflect in the HP 3PAR Management Console. If theVerify operation indicates a problem even after confirming that the zoning is correct, navigateto the host being migrated on the source array and verify that the host is not listed on anyports.To verify zoning changes for a port that is listed next to the WWNs associated with the host,navigate to the port, right click and select Name Server Sync.


6. Click OK to exit the Verify dialog box.7. Click Continue.

If the systems are zoned correctly, the importing tasks start.

Minimally Disruptive Data Migration Confirmation1. Shut down the host system. (You must use the shut-down, not the restart option).2. Click Verify.3. Click OK to exit the Verify dialog box.4. Click Continue.5. After the import task starts, the Migrate Data Confirmation dialog box displays (Figure 18 (page

31)). Click OK.

Figure 18 Migrate Data Confirmation dialog box

Importing Volumes wizardThe following conditions are required to use the Import Volumes wizard:

• Super user role.

• HP 3PAR Peer Motion Software license on the destination storage system.

• Any peer motion configuration that includes a source and destination storage system whosestatus is Normal.

• There are admitted (peer) volumes to be imported and no importing volumes.This wizard guides you in importing peer volumes to the destination storage system. The wizardautomatically selects a migration type based on your system setup and the data migration selectionsyou made for the peer motion configuration.

Importing Volumes wizard 31

NOTE: A warning message displays if either of the following licenses is missing:• Thin provisioning (needed to create a thin volume)

• Domain (needed to add the volumes to a domain that is not the <none> domain)If the peer host already exists on the source storage system, a warning message appears indicatingit must be cleaned it up before proceeding.

To import a volume:1. Select Peer Motion in the Manager Pane.2. In the Common Actions panel, click Import Volume. The Import Volume wizard appears.

Selecting Peer VolumesThe type of migration is preselected based on the system set up and the settings you configuredin the Create PM Configuration wizard.1. For online or minimally disruptive migration, select the Host or Host Set or Linked Hosts for

which you want to migrate virtual volumes to the destination storage system.For Offline migration, select the Virtual Volumes to migrate to the destination storage system.If one volume is a member of a domain, all selected volumes must belong to the same domain.

NOTE:• Only one group of source volumes can be imported to peer volumes on the destination

storage system at the same time.• You must finish the import process completely or remove admitted (peer) volumes before

you can migrate additional volumes.

2. Click Verify peer volumes to verify the peer volumes to be used.3. Click Next to view the Import Volumes screen.

Removing Peer VolumesThe following conditions are required to use Remove Peer Volumes:

• Super user role

• A peer motion configuration that has a source and destination storage system

• Admitted (peer) volumesYou can use Remove Peer Volumes to remove peer volumes that are not yet in the Importing state.You cannot remove exported volumes. You must first unexport the volumes, before you can removethem.

NOTE: Do not remove peer volumes unless the migration process is not successful. If you removepeer volumes which have not yet been imported to the destination storage system, these volumeswill not be migrated to the destination server. To import these volumes, you must begin the migrationprocess again. Additionally, if the host cannot access the source volumes because you haveunzoned the source system, you can lose data.

To remove peer volumes:1. Select Peer Motion in the Manager Pane.2. In the Common Actions panel, click Remove Peer Volumes to open the Remove Peer Volumes

dialog box (Figure 19 (page 33)).


Figure 19 Remove Peer Volumes dialog box

3. Select the Select to also delete check box if you want to delete any listed volumes currentlyexported to a host and listed volumes that are part of a volume set. If this check box is selected,a warning dialog box displays (Figure 20 (page 33)). Click Delete to remove the volumes.

Figure 20 Warning dialog box

4. Click OK.

Post Migration CleanupThe post migration cleanup feature does the following:

• Removes the exports for the migrated volumes so that they are no longer visible to thedestination storage system.

• Removes the VLUNs associated with the volumes being unexported.

• Removes the destination host from the source storage system.

Post Migration Cleanup 33

NOTE:• The peer host is an interim host created by the peer motion process that represents the

destination storage system. Therefore, migration cleanup is not complete until the peer host isremoved from the source storage system.

• When migrating volumes using single volume migration, the post-migration cleanup will notbe removing source VLUN exports as certain hosts such as Linux may not react well, unlessadditional configuration is in place. On the other hand, with hosts such as Windows, thesource VLUN exports can be safely removed after the post-migration cleanup.

To use the Post Migration Cleanup command, the following conditions are required:

• Super user role.

• A peer motion configuration that has a source and destination storage system.

• No admitted (peer) volumes or importing volumes on the destination storage system.

• A peer host exists.You must complete post-migration cleanup after each migration (import task) finishes.After the system completes the post-migration cleanup, you can start a new migration using theexisting peer motion configuration and the current peer ports. To delete the existing peer motionconfiguration and reconfigure the peer ports as host ports, use the Remove PM Configuration dialogbox.To remove the peer host after the data migration process is complete:1. Select Peer Motion in the Manager Pane.2. In the Common Actions panel, click Post Migration Cleanup and the Post Migration Cleanup

dialog box displays (Figure 21 (page 35)).


Figure 21 Post Migration Cleanup dialog box

3. Click OK to remove the peer host on the source storage system.

Removing a Peer Motion ConfigurationThis feature enables you to remove the peer motion configuration. It also removes the peer host,if one exists on the source storage system. You can keep peer ports for later use or change themto host ports.The following conditions are required to use the Remove PM Configuration command:

• Super user role


• No admitted (peer) volumes or importing volumes on the destination storage systemTo remove a peer motion configuration:1. Select Peer Motion in the Manager Pane.2. In the Common Actions panel, click Remove PM Configuration and the Remove PM

Configuration dialog box appears.3. Select the Unconfigure the Peer Ports check box.4. Click OK.

When the peer host exists on the source storage system, click OK to remove the peer host (TheRemove PM Configuration dialog box that appears depends on whether the peer host existson the source storage system).

Figure 22 (page 36) shows the Remove PM Configuration dialog box if the peer host exists on thesource storage system:

Removing a Peer Motion Configuration 35

Figure 22 Remove PM Configuration dialog box with peer host

Figure 23 (page 36) shows the Remove PM Configuration dialog box if the peer host does notexist on the source storage system:

Figure 23 Remove PM Configuration dialog box without peer host

NOTE: Reconfiguring the peer ports to host ports, removes the associated NPIV ports if any werepresent.


Viewing a Peer Motion ConfigurationTo view the current peer motion configuration:1. Select a storage system in the Management Tree.2. Select Peer Motion in the Manager Pane. The Peer Motion Configuration tree node displays

(Figure 24 (page 37)).The Peer Motion Configuration screen includes a Summary tab, a Tasks tab, and an Alertstab.

Figure 24 Peer Motion Configuration tree node

Summary TabThe Summary tab is divided into a left pane and a right pane. The left pane displays the PeerMotion topology in one of the following views:

• Overview—Displays the source and destination storage systems, the direction of data migration,the number of ports and their status, and the View Physical Connectivity check box.

• Physical Connectivity View—Displays the source and destination storage systems, the host andpeer ports, and port connectivity.

The right pane provides a summary of the current migration information.

DescriptionFieldGroup

HostsGeneral

The number and lists of hosts. (Select to go to the Peer MotionHost: Available panel.)

Available

The number of hosts in an admitted state. (Select to go to the PeerMotion Host: Admitted panel.)

Admitted

The number of hosts in an importing state. (Select to go to the PeerMotion Host: Importing panel.)

Importing

The number of imported hosts. (Select to go to the Peer MotionHost: Imported panel.)

Imported

Virtual Volumes

The number of available volumes. (Select to go to the Peer MotionVirtual Volumes: Available panel.)

Available

Viewing a Peer Motion Configuration 37


The number of volumes in an admitted (peer) state. (Select to goto the Peer Motion Virtual Volumes: Admitted panel.)

Admitted

The number of volumes in an importing state. (Select to go to thePeer Motion Virtual Volumes: Importing panel.)

Importing

The number of imported volumes. (Select to go to the Peer MotionVirtual Volumes: Imported panel.)

Imported

(Select to go to the Peer Motion Tasks screen.)Tasks

The number of currently running Peer Motion tasks. (Select to goto the Peer Motion Tasks screen.)

Running Tasks

The number of failed peer motion tasks. (Select to go to the PeerMotion Tasks screen.)

Failed Tasks

The names of the source and destination storage systems.SystemHealth

Indicates the state of each system: Normal, Degraded, or Failed.System State

The peer motion ports associated with each system.Port

The peer motion connection status, which can be one of thefollowing:

Port State

• Normal

• Incorrect number of Peer Motion paths

• Peer Motion ports are not on adjacent nodes

• Peer Motion port modes are not point-to-point

• Source host ports are on the same node

• Source host port is not a host port

• Source port is not ready

• Incompatible source system version

• Incompatible destination system version

• Unsupported version of source or destination system

• Unknown

Displays the number of new alerts and their severity for both source and destinationstorage systems. The severity state can be one of the following:

New Alerts

• Fatal

• Critical

• Major

• Minor

• Degraded

• Info

• None

Select the alert severity to go to the Peer Motion Alerts screen.

Shows RW throughput statistics of the source and destination ports.Performance and Reports

Tasks TabThe Tasks tab is divided into a list pane and a detail pane. The list pane displays complete, running,and failed tasks that are associated with the current peer motion configuration. The detail panedisplays the details related to a selected task.


The list pane displays the following information:

DescriptionColumn

The name of the system on which the task is running.System

The task IDID

The type of task (for example, Scheduled Task).Type

The name of the task.Name

The status of the task (for example, Completed).Status

The user running the task.User

The task progress, if currently running.Progress

The time the task started.Start Time

The time the task finished.Finish Time

The amount of time it took to complete the task.Duration

The detail pane displays the following information:


The name of the system on which the task was started.System NameGeneral

Serial number of the system.System SN

The task ID.ID

The task type.Type

Indicates whether a task is Running, Cancelled, Failed, orCompleted.

Status

The task progress, if currently running.Progress

The time the task started.Start Time

The time the task finished.Finish Time

The amount of time it took to complete the task.Duration

Provides detailed information for the task by time increments.Detailed Status

Alerts TabThe Alerts tab is divided into a list pane and a detail pane. The list pane displays alert informationassociated with the current peer motion configuration. The detail pane displays details for theselected alert.The list pane displays the following information:

DescriptionColumn

The name of the system for which the alert was generated.System

The severity of the problem.Severity

The task ID.ID

The task state (for example, New).State

The last time the task was run.Last Time

Viewing a Peer Motion Configuration 39

DescriptionColumn

Text message describing the reason for the alert.Message

The number of times the task has been run.Repeat Count

The first time the task was run.First Time

Viewing Port InformationTo view the Ports screen:1. Select Peer Motion in the Manager Pane.2. Select Ports under Peer Motion Configuration in the Peer Motion tree.The Peer Motion Configuration: Ports screen (Figure 25 (page 40)) shows the topology betweenthe source and destination storage system ports, a list pane, and a detail pane. The port topologyarea displays the source and destination storage systems, the host and peer ports, and the portsconnectivity.

Figure 25 Peer Motion Configuration: Ports

The list pane provides the following information:

DescriptionColumn

The port location in Node:Slot:Port format.Position

Indicates whether the port is a peer port.Label

The WWN or MAC address of the connected device.WWN/MAC

The state of the port.State

Indicates the port type. For peer links, the port type is always FC.Type

Indicates whether the connection mode is Host or Peer.Connection Mode

Indicates whether the connection device type is Host or Peer.Connected Device Type

Name of device(s) that the port is connected to.Connected Device

Port mode indicator. Can be Initiator, Target or Suspended.Mode

The partner port.Partner

The WWN of the partner port.Partner WWN

Indicates if the system is in a failover state.Failover State

The detail pane contains a Summary tab. If the connected device type is Host, there a Hosts tabis included.

The Summary Screen Detail PaneThe detail pane of the Summary screen displays the following:


The port location in Node:Slot:Port format.PositionGeneral

Port World Wide Name.Port WWN

Node World Wide Name.Node WWN



Indicates the port type. For peer links, the port type is always FC.Type

Rate that data can be transferred over the port (1 Gbps, 2 Gbps, 4 Gbps, or 8Gbps). When there is no specified value, no connection exists.

Rate

Type of device that the port is connected to: Host or Peer.Connected DeviceType

The name of the system associated with the selected port.Connected Device

Port firmware mode setting. Ports in Initiator mode are connected to drive cagesor peer ports. Ports in Target mode are used for host connectivity. Suspended

Mode

mode is for target ports that have not yet been initialized by the system (this israre). Peer mode is for Ethernet ports.

Current state of the port.State

The throughput in KB/s.Total DataThroughput

Resources

The type of port connection: Host or Peer.Connection ModeSettings(displayed for

Connection type or port connection setting: Loop or Point.Connection TypeFC and RCFCports)

Data transfer rate setting (for example, 1 Gbps). Auto indicates that the systemautomatically selects the rate.

Configured Rate

Maximum rate of connection from the port.Max Rate

Indicates whether FC service Class 2 is Disabled, Ack 1 or Ack 0.Class 2

For fabric attached ports, indicates the VLUN change notification setting. Whenset to Enabled, notices are generated and sent to the fabric controller. When setto Disabled, no notification is sent.

VCN

Indicates whether the node's WWN is Enabled or Disabled.Unique NodeWWN

If disabled, each I/O generates a separate interrupt to the HBA port driver ratherthan generating one interrupt for multiple I/O completion.

Interrupt Coalesce

For RCIP ports. The MAC address of the Ethernet interface.MACIP Settings

For iSCSI ports. Indicates if the DHCP protocol is enabled.DHCP

IP address of the iSCSI or RCIP port.IP Address

The address of a local IP router on the same network as the system, used to forwardtraffic to destinations beyond the local network.

Gateway

The netmask address for the iSCSI or RCIP interface.Subnet Mask

The greatest amount of data or "packet" size that can be transferred at one timeover a particular network connection without overburdening the connection. The

MTU

default MTU setting for an iSCSI port is 1500. When supported by the network,an MTU value of 9000 should be used.

For RCIP ports. The configured data transfer rate. A value of 0 indicates that nodata is being transferred.

Configured Rate

For iSCSI ports. Data transfer rate. A value of 0 indicates that no data is beingtransferred.

Rate

The TCP port number used by the iSCSI card.TCP Port

(For RCIP) The duplex speed, Half or Full.Duplex

For RCIP ports. Model of the adapter that contains the port (for example, IntelPRO/1000MT).

Adapter Type

Type of connection (for example, Fabric Attached).TopologyFC Settings

Viewing Port Information 41


(displayed forFC and RCFCports)

Identifies which FC classes of service are enabled (2, 3, or 2/3). 2/3 indicatesthat both Class 2 and Class 3 are enabled.

Class

Model of the FC adapter that contains the port (for example, QLOGIC 2302).Adaptor Type

The node WWN. Displayed if the port is an RCFC port.Remote NodeWWN

The port WWN. Displayed if the port is an RCFC port.Remote Port WWN

Indicates whether port mode change from initiator to target or vice versa is Allowedor Prohibited. This setting is configured using the CLI controlport command.

Mode Change

The number of hosts connected to the port. This is only displayed if the port isconnected to hosts.

Hosts

The number of physical disks connected to the port. This is only displayed if theport is connected to drive cages.

Physical Disks

The current state of the link. Displayed if the port is an RCFC port.Link State

Primary Internet Storage Name Service server IP address. iSNS protocol allowsfor automated discovery, management, and configuration of iSCSI.

Primary IP AddressiSNS Settings(displayed foriSCSI ports -not shown) The port on the iSNS server with which to communicate.TCP Port

The number of NPIV ports.NPIV PortsNPIV Ports(displayed forFC Peer ports) The WWN of each NPIV port.Port WWN

Click the highlighted value for Connected Device in the General area to display the Host Summaryscreen or the System screen, depending on the connected device type.

The Hosts Screen Detail PaneThe detail pane of the Hosts screen displays the following:

DescriptionColumn

The ID of the host associated with the selected port.Host ID

The name of the host system.Host Name

The domain the host is associated with (if any).Domain

The WWN of the port.WWN

The port location in Node:Slot:Port format.Port

Depending on the connected device type, click the highlighted value under Host Name to displaythe Host Summary screen or the System screen.

Viewing Storage Settings and ConfigurationsThe Storage Settings and Configurations section of the Peer Motion tree node contains nodes forHosts and Security and Domains.

Hosts NodeWhen you select the Hosts node in the Peer Motion tree, the Hosts and a Host Sets tabs displayin the Management Window.


Storage Settings and Configuration Hosts TabThe Hosts tab (Figure 26 (page 43)) displays source hosts and destination hosts side by side. Thesource system must be connected for the source hosts screen to display source hosts.

Figure 26 Hosts tab

The following information displays for both source and destination storage system:

DescriptionColumn

The host name.Name

The domain (if any) the host is associated with.Domain

The host set (if any) the host is associated with.Set

The number of storage system ports associated with the host.Storage System Ports

The number of exported volumes on the host.Volumes Exported

The total size (in GiB) of the exported volumes.Total Exported Size

Storage Settings and Configuration Host Sets TabThe Hosts Sets tab (Figure 27 (page 43)) displays source host sets and destination host sets sideby side. The source system must be connected for the source Hosts screen to display source hostsets.

Figure 27 Host Sets tab

Viewing Storage Settings and Configurations 43

The following information appears:

DescriptionColumn

The host set name. Each name listed is a link to the Host Sets details screen.Name

The domain in which the host set resides.Domain

The number of hosts belonging to the host set.Hosts

The total reserved size of the volume, (in GiB).Total Reserved Size

The total exported size of the host set, in GiB.Total Exported Size

User-created comments about the host sets.Comments

Security and Domains NodeThe Security and Domains screen displays the security settings of the source and destination storagesystem. It includes the following tabs:

• Summary

• Users

• Domains

• Domain Sets

• LDAP

Security and Domains Node—Summary Tab

Figure 28 Security and Domains—Summary tab


The Summary tab (Figure 28 (page 44)) displays the following information:


The number of users on the system.UsersGeneral

Whether the system is configured for LDAP authentication.LDAP configuration

The number of domains on the system.Domains

The number of domain sets on the system.Domain Sets

Global/DomainUser Roles

The number of users with Browse permission.Browse

The number of users with Create permission.Create

The number of users with Edit permission.Edit

The number of users with Super permission.Super

The number of users with Service permission.Service

The capacity associated with domains.Inside Domain SizeCapacity

The capacity outside of domains.Outside Domain Size

The total capacity.Total Size

The name of each domain. (Select the Top 10 check box ifyou only want to display the top 10 domains.)

Domain

The size (in GiB) of each listed domain.Size

Security and Domains Node—Users Tab

Figure 29 Users tab

The Users tab (Figure 29 (page 45)) displays user information for the source and destination storagesystem:

DescriptionColumn

User name on the specified system.User Name

The name of the system to which the user has access.System

Domains on the specified system.Domain

Role give to the specified user.Role

Indicates whether there is a default domain associated with the user.Default Domain

Viewing Storage Settings and Configurations 45

Security and Domains Node—Domains Tab

Figure 30 Domains tab

NOTE: The Domains tab (Figure 30 (page 46)) is hidden if the source and destination storagesystem do not have a domain license or do not support the object set feature.

The Domains tab displays the following for both, source and destination storage system:

DescriptionColumn

The domains on each system.Domain

The name of domain set with which the domain is associated, if any.Set

The date and time the specified domain was created.Creation Time

User-created comments.Comments

Security and Domains Node—Domain Sets TabThe Domain Sets tab displays the following for both source and destination storage system:

DescriptionColumn

The name of a domain set on the specified system.Name

The number of domains in the specified domain set.Domains

The number of hosts in the specified domain set.Hosts


Security and Domains Node—LDAP TabThe Security & Domains→LDAP tab (Figure 31 (page 46)) displays all LDAP properties and theirassociated values for both source and destination storage system.

Figure 31 LDAP tab


Viewing Migration Data InformationTo view migration data, follow these steps:1. Select Peer Motion in the Manager Pane.2. Select Migrate Data under Peer Motion Configuration in the Peer Motion tree.

Figure 32 Migrate Data screen

The Migrate Data screen (Figure 32 (page 47)) displays the available, admitted (peer), importing,and imported hosts and virtual volumes for the peer host system, along with capacity informationfor volumes in imported and importing states. Selecting a highlighted item opens the correspondingscreen. For example, selecting Available under Hosts opens to the Available Hosts Summary screen.For more information, see the following topics:

• “Available/Imported Hosts Tab” (page 47)

• “Available/Imported Host Sets Screen” (page 49)

• “Available/Imported Linked Hosts Screen” (page 49)

• “Admitted/Importing Hosts Screen” (page 49)

• “Admitted/Importing Linked Hosts Screen” (page 50)

• “Available/Imported Volumes Screen” (page 51)

• “Admitted/Imported Volumes Screen” (page 51)

Available/Imported Hosts TabThe Hosts tab (Figure 33 (page 48)) displays the hosts that can be migrated. It is divided into alist pane and a detail pane.

Viewing Migration Data Information 47

Figure 33 Hosts: Available—Hosts tab


DescriptionColumn

The name of a host on the source system.Name

The domain (if any) of which the host is a member.Domain

The number of host ports on the system.Host Ports

The number of storage system ports.Storage System Ports

The port node IDs.Node ID(s)

The persona information for the specified port (for example, 1– Generic).Persona

The number of exported volumes on the system.Volumes Exported

The total reserved size(in GiB) of the volume.Total Reserved Size


The detail pane contains a Summary, Virtual Volumes, and VLUNs tab.


Available/Imported Host Sets ScreenThe Host Sets tab (Figure 34 (page 49)) is divided into a list pane and a detail pane.

Figure 34 Hosts: Available—Host Sets tab


DescriptionColumn

The name of a host set on the source system.Name

The domain (if any) to which the host set belongs.Domain

The number of hosts on the system.Hosts

The total amount of reserved space (in GiB).Total Reserved Size



Available/Imported Linked Hosts ScreenThe Linked Hosts screen is divided into a list pane and a detail pane.The list pane provides the following information:

DescriptionColumn




The number of exported volumes.Volumes Exported





The detail pane contains a Virtual Volumes and VLUNs tab.

Admitted/Importing Hosts ScreenThe Host: Admitted screen (Figure 35 (page 50)) displays hosts that have volumes that are in theAdmitted (peer) state. The Importing Hosts screen displays hosts that have volumes that are in theImporting state. The screens are divided into a list pane and a detail pane.


Figure 35 Hosts: Admitted screen

The list pane displays a 1:1 mapping between the source and destination hosts. (The source storagesystem must be connected for the source information to be displayed.)

DescriptionColumn

The name of the source host.Source Host

The name of the source storage system.Source System

The number of volumes exported from the source storage system.Source Volumes Exported

The total size (in GiB) of the volumes exported from the source storage system.Source Total Exported Size

The name of the destination host.Destination Host

The name of the destination domain (if any).Destination Domain

The name of the destination storage system.Destination System

The number of volumes exported to the destination storage system.Destination Volumes Exported

The total size (in GiB) of the volumes exported to the destination storage system.Destination Total Exported Size

Indicates if the migration is minimally disruptive.Minimally Disruptive Migration

The detail pane provides Summary, Virtual Volume, VLUN template, and Active VLUNs tab, andinformation for both the source and destination hosts. (The source system must be connected forthe source information to be displayed.)

Admitted/Importing Linked Hosts ScreenThe Linked Hosts screen is divided into a list pane and a detail pane.The list pane provides the following information:

DescriptionColumn




The number of exported volumes.Volumes Exported




DescriptionColumn



The detail pane contains a VLUNs and a Virtual Volumes tab.

Available/Imported Volumes ScreenThe Virtual Volumes: Available screen displays the volumes that are visible to the source anddestination storage system but that have not yet been admitted. The Virtual Volumes: Importedscreen (Figure 36 (page 51)) displays the volumes that have been imported to the destinationstorage system.

Figure 36 Virtual Volumes: Imported screen

The screen is divided into a list pane and a detail pane.

Admitted/Imported Volumes ScreenThe Virtual Volumes: Admitted screen displays the volumes that have been admitted. The VirtualVolumes: Importing screen displays the volumes that are currently in an importing state.

Figure 37 Virtual Volumes: Admitted screen


The screen is divided into a list pane and a detail pane. The summary screen displays a side-by-sidemapping between the source and destination volumes. The source system must be connected todisplay source volume information.The list pane displays the following information:

DescriptionColumn

The name of the source volumeSource Name

The state of the source volumeSource State

The type of provisioning of the source volume (Thin or Full).Source Provisioning

The name of the user CPG associated with the source volume.Source User CPG

The name of the copy CPG associated with the source volume.Source Copy CPG

The name of the destination volume.Destination Name

The state of the destination volume.Destination State

The type of provisioning of the destination volume (Thin or Full).Destination Provisioning

The name of the user CPG associated with the destination volume.Destination User CPG

The name of the copy CPG associated with the source volume.Destination Copy CPG

The current peer motion status of the volume (for example, Admitted or Importing).Peer Motion Status

The name of the destination host.Destination Export

The detail pane displays the following tabs:

• Summary (see “Summary Tab” (page 52))

• Settings (see “Settings Tab” (page 53))

• Active VLUNs (see “Active VLUNs Tab” (page 54))

• Hosts (see “Hosts Tab” (page 54))

Summary TabThe Summary tab provides the following information for both the source and destination storagesystems:


The name of the virtual volumeNameGeneral

The virtual volume IDID

The domain in which the volume is locatedDomain

The name of the volume set to which the volume belongsSet

The type of volume (base, physical copy, or virtual copy)Type

Indicates whether the selected volume is fully provisioned or athinly provisioned virtual volume

Provisioning

The World Wide Name of the volumeWWN

The volume from which the selected volume was copiedCopy Of

The number of copies of the selected volumeCopies

Indicates whether the volume is read-only (RO) or read-write(RW)

Mode



Indicates the RAID type of a volumeRAID

Indicates the size of the volume (in GiB)Virtual Size

The host to which the volume is exportedExported To

The number of new virtual volume alertsNew AlertsHealth

The current state of the virtual volumeState

Description of the virtual volume stateState Description

Select the device type, Fast Class (FC), Near Line (NL), or SolidState Device (SSD). The capacity and capacity usage of theselected device type displays in graphical form.

Device TypeCapacity

The logical capacityLogical

The raw capacityRaw

The allocation of admin, copy, and user space for the volumeVirtual Volume Allocation

Settings TabThe Settings tab displays a side-by-side comparison of source and destination volume settings.


The type of provisioning of the volume (Thin or Full)ProvisioningUser SpaceProvisioning

The name of the CPG associated with the volumeCPG

The device type of the volume (for example, FC)Device TypeUser Space Allocation/ Copy SpaceAllocation The disk speed

NOTE: The Device RPM number does not represent a rotational speedfor the drives without spinning media (SSDs). It is meant as a roughestimation of the performance difference between the drive and theother drives in the system. For FC and NL drives, the numbercorresponds to both a performance measure and actual rotationalspeed. For SSD drives, the number is to be treated as relativeperformance benchmark that takes into account (in I/O per second),bandwidth, and the access time.

Device RPM

The RAID configuration of the volumeRAID Type

The current volume configuration (such as cage)ConfiguredAvailability

The level of failure tolerance for this volume: <System Default>, Cage,Port, or Magazine.

Availability

The set size of the volumeSet Size

The step size of the volumeStep Size

The type of provisioning of the volume (Thin or Full)ProvisioningCopy SpaceProvisioning

The name of the CPG associated with the volumeCPG

Indicates whether Allocation Warning is enabled or disabledAllocation Warning

Indicates whether Allocation Limit is enabled or disabledAllocation Limit


Active VLUNs TabThe Active VLUNs tab provides the following information for both the source and destination storagesystems:

DescriptionColumn

The exported LUN valueLUN

The exported volumeVirtual Volume

The name of the host to which the VLUN is exportedHost

The port to which the path is connectedPort

The host WWN or iSCSI nameHost WWN/iSCSI Name

The size of the VLUN in GiBExported Size

Hosts TabThe Hosts tab provides the following information for both the source and destination storagesystems:

DescriptionColumn

The name of the hostName

The name of the systemSystem

The number of Node ID(s) associated with the hostNode ID(s)

The persona associated with the hostPersona

The number of exported volumesVolumes Exported

The total size (in GiB) of exported volumesTotal Exported Size

Viewing Source and Destination Storage SystemsThe source and destination storage systems screens include a Summary tab (“Summary Tab”(page 55)) and an Alerts tab (“Alerts Tab” (page 56)). The Summary tab provides information forthe source and destination storage systems. The Alerts tab displays alerts that are associated withthe specified system.


Summary Tab

Figure 38 Peer Motion Configuration—Source Summary tab

The Summary tab (Figure 38 (page 55)) provides the following information. Click any highlightedtext to open the corresponding screen and view more detailed information.


The virtual volume's name.NameGeneral

The model number of the storage system.Model

The serial number of the storage system.Serial Number

The operating system version in use by the system.OS Version

Indicates whether the system is configured with SNMP.SNMP Configuration

Displays the IP address of the NTP server, if available.NTP Server Configuration

Displays IP address of the DNS server, if available.DNS Server

Select to view the system's Ports screen.Ports

The number of host ports on the system.Host

The number of peer ports on the system.Peer

The number of free ports on the system.Free

The total number of physical disks in the system, followed bythe type and number of each type of disk (for example, FC, NL,SSD).

Physical Disks

The number of hosts on the system.HostsHost

The number of host sets on the system.Host Sets

Lists current operating system in use.Operating System

The total number of paths on the system and the number ofunassigned paths.

Paths

The number of CPGs on the system.CPGsProvisioning

Viewing Source and Destination Storage Systems 55


The number of virtual volumes on the system.Virtual Volumes

The number of base volumes on the system.Base Volumes

The number of thinly provisioned volumes on the system.Thinly Provisioned

The number of fully provisioned volumes on the system.Fully Provisioned

The number of virtual copies on the system.Virtual Copies

The number of physical copies on the system.Physical Copies

The number of remote copy volumes on the system.Remote Copy Volumes

The number of expired volumes on the system.Expired Volumes

The number of unexported volumes on the system.Unexported Volumes

The number of active VLUNs on the system.Active VLUNs

GeneralSecurity and Domains

The number of user accounts on the system.Users

Indicates whether the system is configured for LDAP.LDAP configuration



User Roles

Lists the global user roles on the system, itemized by role andthe number of users having the specified role.

Global

Lists the domain user roles on the system, itemized by role andthe number of users having the specified role.

Domain

Alerts TabThe Alerts tab (Figure 39 (page 57)) is divided into a list pane and a detail pane. For details aboutthe list and detail panes, see “Alerts Tab” (page 39).


Figure 39 Peer Motion Configuration—Alerts tab

Ports ScreenThe Ports screen contains a Peer Capable Ports tab and a Host Ports tab when viewing both sourceand destination storage systems. When viewing the destination storage system, the Peer Ports tabis also included. All three tabs are divided into a list pane and a detail pane and provide similarinformation.The list pane provides the following information:

DescriptionColumn

The port location in Node:Slot:Port format.Position

The port label.Label

WWN or MAC address of the connected device.WWN/MAC

The state of the port.State

Indicates whether the port is FC, iSCSI, RCIP, or RCFC.Type

Indicates whether the connection device type is Host or Peer.Connected Device Type

The name of device that the port is connected to.Connected Device

Port firmware mode setting: Initiator or Target.Mode

The partner port, in Node:Slot:Port format.Partner

The WWN of the partner port.Partner WWN

Indicates whether the system is in a failover state.Failover State

Viewing Source and Destination Storage Systems 57

The detail pane contains the following information:


The port location in Node:Slot:Port format.PositionGeneral

The port’s World Wide Name.Port WWN

The node’s World Wide Name.Node WWN

Indicates whether the port is FC, iSCSI, RCIP, or RCFC.Type

The rate that data can be transferred over the port (1, 2, 4, or 8 Gbps). Whenthere is no specified value, no connection exists.

Rate

The type of device that the port is connected to: Host or Peer.Connected DeviceType

The name of the system associated with the selected port.Connected Device

Port firmware mode setting.Mode

The current state of the port.State

The type of port connection: Host or Peer.Connection ModeSettings(displayed for

Connection type or port connection setting: Loop or Point.Connection TypeFC and RCFCports)

Data transfer rate setting (for example, 1 Gbps). Auto indicates that the systemautomatically selects the rate.

Configured Rate

Maximum rate of connection from the port.Max Rate

Indicates whether FC service Class 2 is Disabled, Ack 1 or Ack 0.Class 2

For fabric attached ports, indicates the VLUN change notification setting. Whenset to Enabled, notices are generated and sent to the fabric controller. Whenset to Disabled, no notification is sent.

VCN

Indicates whether the node's WWN is Enabled or Disabled.Unique NodeWWN

If disabled, each I/O generates a separate interrupt to the HBA port driver ratherthan generating one interrupt for multiple I/O completion.

Interrupt Coalesce

For RCIP ports, the MAC address of the Ethernet interface.MACIP Settings(displayed for

For iSCSI ports, indicates whether the DHCP protocol is enabled.DHCPRCIP and iSCSIports - notshown) IP address of the iSCSI or RCIP port.IP Address

The address of a local IP router on the same network as the system, used toforward traffic to destinations beyond the local network.

Gateway

The netmask address for the iSCSI or RCIP interface.Subnet Mask

The greatest amount of data or "packet" size that can be transferred at one timeover a particular network connection without overburdening the connection. The

MTU

default MTU setting for an iSCSI port is 1500. When supported by the network,an MTU value of 9000 should be used.

For RCIP ports. The configured data transfer rate. A value of 0 indicates that nodata is being transferred.

ConfiguredRate

For iSCSI ports. Data transfer rate. A value of 0 indicates that no data is beingtransferred.

Rate

The TCP port number used by the iSCSI card.TCP Port

For RCIP ports. The duplex speed: Half or Full.Duplex

For RCIP ports, the model of the adapter that contains the port (for example,Intel PRO/1000MT).

Adapter Type



The type of connection (for example, Fabric Attached).TopologyFC Settings(displayed forFC and RCFCports)

Identifies which FC classes of service are enabled (2, 3, or 2/3). A value of2/3 indicates that both Class 2 and Class 3 are enabled.

Class

Model of the FC adapter that contains the port (such as QLOGIC 2302).Adaptor Type

Indicates whether port mode change from initiator to target or vice versa isAllowed or Prohibited. This setting is configured using the CLI controlportcommand.

Mode Change

Primary Internet Storage Name Service (iSNS) server IP address. iSNS protocolallows for automated discovery, management, and configuration of iSCSI.

Primary IP AddressiSNSSettings(displayedfor iSCSI ports- not shown) The port on the iSNS server with which to communicate.TCP Port

Viewing Available Storage SystemsThe Available Storage tree node lists the names of all available Storage systems that can be usedfor data migration and provides summary information in the Peer Motion: Available Storage Systemsmanagement window (Figure 40 (page 59)).

Figure 40 Peer Motion: Available Storage Systems

Click a system name to display available Storage system summary information and alerts that areassociated with the system. For information, see “Viewing Source and Destination Storage Systems”(page 54). For information about peer-capable, peer and host ports on an available system, see“Ports Screen” (page 57).

DescriptionColumn

The name of an available system.System

The number of available peer capable ports on the system.Peer Capable Ports

The number of peer ports on the system.Peer Ports


The number of hosts on the system.Hosts

The number of host sets on the system.Host Sets

The number of CPGs on the system.CPGs

The number of virtual volumes on the system.Virtual Volumes

The number of virtual volume sets on the system.Virtual Volume Sets

The number of user accounts on the system.Users



Viewing Available Storage Systems 59

Migration Phase IssuesSee Migration Phase Issues in “Troubleshooting” (page 113).


4 Using the HP 3PAR Peer Motion UtilityHP 3PAR Peer Motion Utility controls the migration of a host and its data from a source HP 3PARStoreServ Storage system to a destination HP 3PAR StoreServ Storage system with as little disruptionto the host as possible. It provides a set of commands for performing the migration operations.You can use it to script migrations of virtual volumes from one HP 3PAR StoreServ Storage systemsto another.The HP 3PAR Peer Motion Utility is for users who have good knowledge of storage administrationand migration workflow. For additional details about the CLI commands, see “HP 3PAR Peer MotionUtility Commands” (page 97).The HP 3PAR Peer Motion Utility supports three types of data migration:• Online migration

Online windows cluster migration◦◦ Single VV migration

• Minimally disruptive migration (MDM)

• Offline migrationFor details regarding data migration types, see “Migration Types” (page 6).To use the HP 3PAR Peer Motion Utility:1. Verify that prerequisites are met. See “Pre-Migration Tasks” (page 61).2. Complete installation of the HP 3PAR Peer Motion Utility software. See “Installing the HP 3PAR

Peer Motion Utility” (page 62).3. Verify services are running. See “Confirming Services” (page 70).4. Launch the application the HP 3PAR Peer Motion Utility application. See “Launching the HP

3PAR Peer Motion Utility” (page 70).5. Execute the Peer Motion Utility commands. See “Using the HP 3PAR Peer Motion Utility

Commands” (page 70).

Pre-Migration TasksRefer to “Data Migration Requirements” (page 11) for requirements.The following must be performed and verified before using the HP 3PAR Peer Motion Utility:On the storage system:

• Two ports to be configured as host ports on the source HP 3PAR StoreServ Storage system,say 2:2:3(Host Port 1) and 3:2:3(Host Port 2) using HP 3PAR Management Console or 3PARCLI.

• Configure two adjacent host ports as peer ports on the destination HP 3PAR StoreServ Storagesystem, say 2:1:1(Peer Port 1) and 3:1:1(Peer Port 2), using HP 3PAR Management Consoleor 3PAR CLI.For online windows cluster migration, create NPIV ports for above peer ports configured ondestination using HP 3PAR CLI and zone them to respective peer ports.

• Two ports to be configured as host ports on the destination 3PAR storage system, say 2:2:1(Hostport of destination 1) and 3:2:1(Host port of destination 2), using HP 3PAR ManagementConsole or 3PAR CLI.

On the fabric:• Create first zone, Z1 with Host Port 1 zoned to Peer Port 1.

• Create second zone, Z2 with Host Port 2 zoned to Peer Port 2.

Pre-Migration Tasks 61

• There is a third zone Z3 between Host Port 1, Host Port 2 of Source Array and Host HBA,already.

• Create the fourth zone Z4 with Host ports of destination Host HBA.

• Save and enable the configuration with Z1 and Z2.

Installing the HP 3PAR Peer Motion Utility

System RequirementsThe following are operating system requirements:

SoftwareFor information on the supported operating systems, see the Support Matrix on HP SPOCK:http://www.hp.com/storage/spock

NOTE: HP 3PAR Peer Motion Utility server runs only on a Windows system.

HardwareThe following are the hardware requirements for installing HP 3PAR Peer Motion Utility:

• Multi-core processor

• 2GB space must be available on the hard drive for installation

• Minimum of 512 MB of free RAM must be available on the system

Installation on a Windows SystemUse the following procedures to install the HP 3PAR Peer Motion Utility on a Windows system.Download the HP 3PAR Peer Motion Utility.exe file from the software portal at:http://www.software.hp.comTo install on Windows:1. Double-click the installer. The Welcome screen appears.2. On the Welcome screen, click Next.

62 Using the HP 3PAR Peer Motion Utility


http://www.software.hp.com

Figure 41 Welcome Screen

3. In the License Agreement screen, read the HP EULA, then select the I accept the terms in thelicense agreement radio button to proceed and click Next.

Figure 42 License Agreement

Installing the HP 3PAR Peer Motion Utility 63

4. In the Custom Setup screen, you can specify a folder where you want to install the applicationfor the client, server, or both (optional). The default locationis:<Installation_Drive>\ProgramFiles(x86)\Hewlett-Packard\hp3parpmu.

Figure 43 Program Features

To change the current destination folder, click Change, click Browse and select or enter afolder location. Click OK and Next.


Figure 44 Destination Folder

NOTE:• During installation, the Windows User Groups called HP Storage Migration Admins and

HP Storage Migration Users are created for use with HP 3PAR Peer Motion Utility.• During first time install, HP 3PAR Peer Motion Utility installer supports feature-wise

installation, but does not support feature-wise uninstallation.• For information about adding a CA signed certificate, “Adding a CA signed certificate”

(page 68).

5. By default, HP 3PAR Peer Motion Utility uses the ports 2390 for server and 2388 for shutdown.The Port Configuration screen appears only when the HP 3PAR Peer Motion Utility Server isselected in step 3. Click Next to proceed.If a port is busy during installation, a message displays and the installer prompts you to entera free port.

Figure 45 Error—Port Busy


NOTE: If you need to assign new port numbers, enter the new port numbers in the ServerPort and Shutdown Port fields, then click Next.For example, if you specify port 9090 during the installation, then edit the OIUCli.bat fileat:<Install location>\Hewlett-Packard\hp3parpmu\CLI with new port: java-jar ..\CLI\oiucli-1.0.0-jar-with-dependencies.jar %* -port 9090.

Figure 46 Port Configuration

6. Click Install in the Ready to Install the Program screen to complete installation.The installation may take several minutes to complete. While the installation is in progress,status messages appear.


Figure 47 Install Program

7. Click Finish to exit the installation wizard.To view the installer log details after the installation completes, select the Show the WindowsInstaller log check box, and then click Finish.

Figure 48 Installation Complete


After installation, you must add users to these groups to grant administrator and user access rights.See “Adding Users to Groups” (page 69).

Adding a CA signed certificate• The Certificate Authority Signed Certificate dialog box displays, if HP 3PAR Peer Motion Utility

Server is selected. Click No to generate and install the self-signed certificate, then click Browseand select a folder location to store the certificate. Click Yes if you already have a CA signedcertificate, then click Browse to navigate to the folder location.

Upgrading on a Windows System

NOTE: Upgrade installation of HP 3PAR Peer Motion Utility is supported from the followingversions: 1.1.0 to 1.3.0 and 1.2.0 to 1.3.0.

1. Double-click the installer.The Welcome screen appears.

Figure 49 Welcome Screen—Upgrade


2. Click Yes.The installer begins the upgrade on the system.

Installation on Linux SystemsUse following procedures to install the HP 3PAR Peer Motion Utility on a Linux system. Downloadthe HP3PARPMUtility_x64/x86 tar file at the HP Software Depot at http://www.software.hp.com.

NOTE: Use HP3PARPMUTILITY_x86.tar for 32 bit or HP3PARPMUTILITY_x64.tar for 64bit systems.

Pre-requisites

• Log in with root permissions.

• Ensure you are on a supported Red Hat Enterprise Linux version. See the HP SPOCK websitefor details:HP SPOCK.

• Disk space should be more than 100MB.

• JRE should be greater than or equal to 1.7.To install on a Linux system:1. Extract the tar file by running Linux command: tar -xvf HP3PARPMUTILITY_x86 or tar

-xvf HP3PARPMUTILITY_x64 on the console.2. See the Linux installer on the console using the ls command.3. Set Execution permission to Linux_local_install.sh file by using following command:

chmod -R 777 Linux_local_install.sh.4. Execute ./Linux_local_install.sh and enter y when prompted to install.5. After the successful installation of client, execute ./hp3parpmu.sh under

"/opt/hewlett-packard/hp3parpmu".

Adding Users to GroupsHP 3PAR Peer Motion Utility helps prevent unauthorized use by validating the user name providedat the time of login against the user name added in the user groups created during installation.The application can only be accessed by authorized users. By default, the HP 3PAR Peer MotionUtility installer creates the following user groups on your system during installation of servercomponent:

• HP Storage Migration Admins

• HP Storage Migration Users

NOTE:

• When running the client-side of HP 3PAR Peer Motion Utility on Linux, the authentication stillhappens on the server side on Windows.

• Refer Windows documentation for your release to add a user to a group.

• Users belonging to the HP Storage Migration Admins user group have privileges to use thefollowing commands: addsource, removesource,adddestination,removedestination, createmigration, startmigration,removemigration, and all the show commands such as, showmigration. Users belongingto the HP Storage Migration Users user group have privileges to execute only show commands,such as showmigration.





Confirming ServicesThe HP 3PAR Peer Motion Utility automatically starts when the installation completes.To confirm that these services have started, perform the following:1. Click Start→Run.....2. In the Run dialog box, type, services.msc, then click OK.3. In the Services window, verify that the HP 3PAR Peer Motion Utility services appears in "Started"

mode (in the Status column), then close the window.

Launching the HP 3PAR Peer Motion UtilityDouble-click the HP 3PAR Peer Motion Utility shortcut created on your Desktop.To log into the CLI:1. For the IP address, type the IP address of the system running the HP 3PAR Peer Motion Utility

server.2. For the USER NAME, type the user name, using which the HP 3PAR Peer Motion Utility server

can log in.3. For the PASSWORD, type the user password.The following is optional: Port—enter the port which the CLI should communicate to the HP 3PARPeer Motion Utility server. The default value is 2390.

CLI Version 1.3.0

Enter IP address: 11.11.111.11

Enter USER NAME: administrator

Enter PASSWORD:

>Successfully logged in

Using the HP 3PAR Peer Motion Utility CommandsThe following are the general guidelines and execution order of the commands for migration usingthe HP 3PAR Peer Motion Utility.General Information

• The CLI commands and their arguments are case insensitive, but the values that the commandargument takes, such as user name, password, volume name, host name, etc. are case sensitive.

• For usage details a specific command, use the <command name> -help option.

• If any value with a space to be specified in commands, it needs to be enclosed in doublequotes (").

• If any value to be specified has double quotes, it can be escaped using backslash ("\").

• If any value to be specified has ("\"), it can be escaped using another backslash ("\\").

• Any hyphen (“-“) when specified within a value of parameter should also be escaped bybackslash("\").

• Information about which sub-steps are under execution will be displayed in the output.

• ERROR or SUCCESS of the overall command execution is displayed as last statement.

• All show commands have the –csvtable option, which when used will print delimited output.

• All show commands have the –filewrite option, which when used will print delimitedoutput to a .txt file.


• Any error executing a command will display as: ERROR: <Error code>:<Errormessage>:<Resolution code>:<Resolution message>.

• For a list of host OS when migrating a host, see the HP SPOCK website:HP SPOCK

For Read-Only Commands

• Default behavior is to display all details with headings in a readable format.

• If nothing is specified with the commands, the default parameter is –all.

• For any entry that is not known, |unknown| is displayed.

• If no entry found in the data base, an empty list is displayed.

• You can cannot modify the sort order.

• Any argument that follows -showcols depicts field to display (columns). CLI provides outputwith only those columns that are mentioned in showcols.

• Any argument that follows -<parameter> after a space depicts input for that command.

• Delimiter: Primarily comma (,) is the delimiter used. Semi-colon (;) is the delimiter used withinmultiple entries for same field.

• To filter, parameter by column name, use the wildcard entry can be specified with value asthat uses only "*".

• If the value for an entry is not available, "--NA--" appears.For Write CommandsAny successful execution of write command appears as:<message> SUCCESS: Added source storage system.

NOTE: The following output is an example only. Your system may not reflect the specific examplesused in this guide.

HP 3PAR Peer Motion Utility Workflow

Figure 50 HP 3PAR Peer Motion Utility workflow

Using the HP 3PAR Peer Motion Utility Commands 71


Online MigrationTo perform online migration, follow the steps and execute the commands in the following order:1. addsource -mgmtip <ipaddress> -user <username> -password <password>

-type 3PAR

2. showsource

3. adddestination -mgmtip <ipaddress> -user <username> -password<password> -type 3PAR

4. showdestination

5. showconnection

6. createmigration -sourceuid <sourceuid> -srcvolmap[{"<volumename>","<destinationprovisioning>","<destinationCPG>"}]-migtype online

7. showmigration -migrationid <migrationid>

NOTE:• In case there is a need to abort the prepared migration, use the removemigration

command for the same: removemigration -migrationid <migrationid>.• Online migration can be performed using the srchost parameter or the -volmapfile

parameter or the srcvolmap parameter.

IMPORTANT:• Re-run a scan on the host systems to discover the new paths to the migrating volume(s).

• Verify that the host paths to the destination storage system are active.

• If path verification is successful, remove zone Z3.

8. startmigration –migrationid <migrationid>

9. showmigrationdetails –migrationid <migrationid>

This completes the successful flow of the migration.

You can remove the added source and destination storage systems, when the Complete status forthe migrating volumes appear. After the migrations have completed successfully and if no additionalmigration need to be carried out, the following optional commands are to be used to remove theadded source and destination storage systems:1. removesource -uid <uid> -type 3par

2. removedestination -uid <uid>

NOTE: Removing a source or destination storage system also removes the migration history forthe respective source or destination storage system.

Online Windows Cluster MigrationVirtual peer ports must be created as NPIV ports for the peer motion configured physical peerports. The number of NPIV ports that must be created on each peer port is twice the number ofnodes that are being migrated. For example, migration of two node clusters require that each peerport be configured with four NPIV ports. The destination storage system must be an HP 3PARStoreServ 7000 or an HP 3PAR StoreServ 10000 and must be running HP 3PAR OS 3.1.3, orlater. Cluster sizes of up to four hosts are supported.


Pre-requisitesVirtual peer ports must be created as NPIV ports using the following commands on HP 3PAR OSCLI. For example, #controlport config peer –virt_ports 8 2:2:1 (where 8 is thenumber of NPIV ports and 2:2:1 is peer port number).To perform online windows cluster migration, follow the steps and execute the commands in thefollowing order:1. addsource -mgmtip <ipaddress> -user <username> -password <password>

-type 3PAR

2. showsource


4. showdestination

5. showconnection

6. createmigration -sourceuid <sourceuid> -srcvolmap[{"<volumename>","<destinationprovisioning>","<destinationCPG>"}]-migtype online



command:removemigration -migrationid <migrationid>

• Windows cluster migration can be performed using the srchost or the srcvolmapparameter.

IMPORTANT:• Re-run a scan on the host systems to discover the new paths to the migrating volume(s).


• If path verification is successful, remove zone Z3.




You can remove the added source and destination storage systems, when the Complete status forthe migrating volumes appear. The following optional commands are to be used to remove theadded source and destination storage systems:1. removesource -uid <uid> -type 3par



Single VV MigrationThe -singlevv option can be used to migrate a subset of volumes provisioned to a host. In thiscase, there is no need to unzone the source storage system from the host that is being migrated.


In order to use single vv migration, the following conditions must be satisfied:• Both the source and destination storage systems must be running at least HP 3PAR OS 3.1.3.

• The host(s) to which the volumes are exported to must be defined using an ALUA persona onboth source and destination storage systems.

To perform single vv migration, follow the steps and execute the commands in the following order:1. addsource -mgmtip <ipaddress> -user <username> -password <password>

-type 3PAR

2. showsource


4. showdestination

5. showconnection

6. createmigration -sourceuid <sourceuid> -srcvolmap[{"<volumename>","<destinationprovisioning>","<destinationCPG>"}]-migtype online -singlevv



command for the same: removemigration -migrationid <migrationid>.• Single vv migration can be performed using the srchost or the srcvolmap parameter.







Minimally Disruptive MigrationTo perform minimally disruptive migration, follow the steps and execute the commands in thefollowing order:1. addsource -mgmtip <ipaddress> -user <username> -password <password>

-type 3PAR

2. showsource


4. showdestination

5. showconnection

6. createmigration -sourceuid <sourceuid> -srcvolmap[{"<volumename>","<destinationprovisioning>","<destinationCPG>"}]-migtype MDM




command for the same: removemigration -migrationid <migrationid>.• Minimally disruptive migration can be performed using the srchost or the srcvolmap

parameter.

IMPORTANT:• Re-run a scan on the host systems to discover the new volume.


• On fabric, remove zone Z3 and add zone Z4 upon successful preparation completion.







Offline MigrationIn order to perform offline migration, follow the steps and execute the commands in the followingorder:1. addsource -mgmtip <ipaddress> -user <username> -password <password>

-type 3PAR

2. showsource


4. showdestination

5. showconnection

6. createmigration -sourceuid <sourceuid> -srcvolmap[{"<volumename>","<destinationprovisioning>","<destinationCPG>"}]-migtype offline


NOTE: In case there is a need to abort the prepared migration, use the removemigrationcommand for the same: removemigration -migrationid <migrationid>.




You can remove the added source and destination storage systems, when the Complete status forthe migrating volumes appear. The following optional commands are to be used to remove theadded source and destination storage systems:


1. removesource -uid <uid> -type 3par



Virtual Volume SetHP 3PAR Peer Motion Utility supports volume set and host set migration.• With volume set migration, all volumes of set will be migrated to destination storage system

along with their presentation. Individual volumes of a set are migrated and volume set iscreated at destination storage system.

• With host set migration, all hosts of host set are migrated and will be part of correspondinghost set as in source storage system.

• The hosts to which the volumes are exported must be defined using an Asymmetric LogicalUnit Access (ALUA) host persona.

• The hosts must be configured to use ALUA. See host-specific documentation for enabling ALUA.

• Virtual volume set can be migrated consistently by either using allvolumesincg orcgvolmap parameter.

The following are use cases of volume set and host set migration:

Host set-based migration examples1. When a volume from a volume set is exported to host set and host-based migration is triggered;

all volumes that are exported to selected host set are migrated.

NOTE: Host set name should be preceded with "set:" to identify input as host set nameinstead of host name.

Command syntax: createmigration -sourceuid 270002AC001BA1 -srchost"set:hostset1" -migtype online -destcpg TEST_CPG -destprov thin

2. When volume set is exported to host set and host-based migration is triggered, all volumes ofvolume set are migrated and exported to the host set (and corresponding host members).Command syntax:createmigration -sourceuid 270002AC001BA1 -srchost"set:hostset1" -migtype online -destcpg TEST_CPG -destprov thin

3. If a volume set or an individual volume that is part of a volume set, is exported to non ALUAsupported host or host set, then host set-based migration is not supported.Command syntax: createmigration -sourceuid 2FFXXXX2AC003F8E-srchost"set:hostset1" -migtype online -destcpg TEST_CPG -destprovthin

Expected behavior:OIUERRPREP1022: Unsupported alua for an vvset migration. Please try migration with ALUAbased hosts.

Volume set-based migration examples1. When volume set is exported to host and volume-based migration is triggered, all volumes of

volume set are migrated and exported to host.

NOTE: Volume set name should be preceded with "set:" to identify input as volume set nameinstead of volume name.


Command syntax: createmigration -sourceuid 270002AC001BA1 -srcvolmap"[{set:volset1, thin, TEST_CPG}]" -destcpg TEST_CPG -destprov thin–migtype online

2. When volume set is exported to host set and volume-based migration is triggered, all volumesof set are migrated.Command syntax: createmigration -sourceuid 270002AC001BA1 -srcvolmap"[{set:volset1, thin, TEST_CPG}]" -destcpg TEST_CPG -destprov thin–migtype online

3. If volume set based migration is triggered through volmap file parameter, then the set nameshould be specified in file preceded by set, the expected behavior is same as either 1 or 2(above) based on presentation of volume set (either to host/host set).Command syntax: createmigration -sourceuid 270002AC001BA1 –volmapfile"c:\volmapfilename.txt” where volmap file contains one or more volume set detailsto be migrated.

4. When volume set is exported to host set or host and migration triggered for the volume set.All the volumes and the volume set are migrated and exported to the host or host set.Command syntax: createmigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap"[{set:set1,thin,ARCH_CPG}]" -destcpg ARCH_CPG -destprov thin-migtype online

Expected behavior: Migration succeeds. All volumes, volume set, host and host set are createdand exports are same as the source storage system.

5. When the volumes of a volume set are exported to host or host set and the migration triggeredfor the volume set. All the volumes and the volume set are migrated and exported to the hostor host set.Command syntax: createmigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap"[{set:set2,thin,ARCH_CPG}]" -destcpg ARCH_CPG -destprov thin-migtype online

Expected behavior: Migration succeeds. All volumes, volume set, host and host set will becreated and exports are same as the source storage system.

6. When the volumes of a volume set are exported to host or host set and the migration triggeredfor the individual volumes. Then, implicitly all the volumes are migrated and exported to hostor host set.Command syntax: createmigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap"[{vol1,thin,ARCH_TEST_CPG},{vol2,thin,ARCH_TEST_CPG}]" -destcpgARCH_TEST_CPG -destprov thin -migtype online

Expected behavior: Migration succeeds. Implicitly, all the volumes are migrated and exportedto host or host set. Volume set will not create at destination storage system and the volumesare removed from the volume set at source storage system.

7. When a volume set is selected for migration, and at least one of its virtual volume is part ofanother volume set, which is exported to a host or host set; the migration fails in preparationphase with an appropriate error message.Command syntax: createmigration -sourceuid 2FFXXXX2AC003F8E –srcvolmap"[{set: set1, thin, ARCH_CPG}]" -destcpg ARCH_CPG -destprov thin-migtype online


Error message: OIUERRVVS0006: Migration cannot proceed.OIURSLVVS0006:One or more VV is part of another VVset.

8. When a volume that is part of a volume set is selected for migration, where the volume set isexported to host or host set; the migration fails in preparation phase with an appropriate errormessage.Command syntax: createmigration -sourceuid 2FFXXXX2AC003F8E-srcvolmap"[{vol, thin, ARCH_CPG]" -destcpg ARCH_CPG -destprov thin-migtype online

Error message: OIUERRVVS0004: Migration of volumes is not supported whenvvset is exported to a host/hostset.

NOTE: Volume set and individual volumes cannot be migrated in a single createmigrationcommand.

Volume Set Offline Migration1. Volume set can be migrated in offline mode. In offline migrations, all volumes of set are

migrated to destination storage system.Command syntax: createmigration -sourceuid 270002AC001BA1 -srcvolmap"[{set:volset1, thin, TEST_CPG}]" -destcpg TEST_CPG -destprov thin–migtype offline

2. If migration is triggered for a volume that is part of a volume set, then the volume set is notcreated at destination storage system and the volume is removed from the volume set of thesource storage system.Command syntax: createmigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap"[{vol,thin,ARCH_TEST_CPG}]" –migtype offline

Expected behavior: Migration succeeds for all volumes. Volume set will not create at destinationand the volumes are removed from the volume set at source storage system.

Consistency GroupThe Consistency Group feature enables users to consistently migrate dependent volumes ofapplications. All the volumes in the consistency group are owned by either source or destinationstorage system at any given time. In case of migration failure, you can go back to source withoutrisk of any data failure.

NOTE: The Consistency Group support is available on a destination HP 3PAR StoreServ Storagesystem that runs HP 3PAR OS version 3.2.1 or later of the supported platforms.

Best Practices• To migrate consistently, minimum two volumes must be added in consistency group.

• Limit the number of volumes in the Consistency Group for consistent imports to 20.

• Limit the volumes in the set to just those that really need to be consistent with each other. Donot add all of the volumes exported to the host in one big Consistency Group.

• Limit the total size of volumes in the set to 40 TB to avoid long switchover times at the end ofimports.

Detailed scenarios are described below.


Volume Based Migration• Migrate subset of volumes consistently

Syntax of the command:createmigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap "[{vol1,thin, testcpg} {vol2, thin, testcpg} {vol3, thin, testcpg}]" -destcpgtestcpg -destprov testcpg -cgvolmap {"values":{"cg1":["vol1","vol2]}}

Where cgvolmap is a parameter which accepts name of a consistency group and volumenames to be migrated consistently.Expected behavior: vol1, vol2, vol3 are created at the destination source system and vol1and vol2 are migrated consistently.

• Migrate all volumes consistentlySyntax of the command:createmigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap "[{vol1,thin, testcpg} {vol2, thin, testcpg} {vol3, thin, testcpg}]" -destcpgtestcpg -destprov testcpg -allvolumesincg

-allvolumesincg is an optional parameter. If this parameter is specified, all volumes aremigrated consistently.Expected behavior - vol1, vol2, vol3 are created at the destination source system and migratedconsistently.

Host Based Migration• Migrate all volumes exported to a host consistently

Syntax of the command:createmigration -sourceuid 2FFXXXX2AC003F8E -srchost "hostname"-migtype online -destcpg testcpg -allvolumesincg

Expected behavior: At the destination all volumes (including implicit volumes) exported to hostare created and migrated consistently.

• Migrate subset of volumes consistently which are exported to hostcreatemigration -sourceuid 2FFXXXX2AC003F8E -srchost "hostname"-migtype online -destcpg testcpg -destprov thin -cgvolmap{"values":{"cg1":["vol1","vol2","vol3"],"cg2":["vol4","vol5","vol6"]}}

All volumes specified in the cgvolmap parameter are exported to host specified for migration.Expected behavior: At the destination all volumes (including implicit volumes) exported to hostare created and volumes specified in the cgvolmap parameter are migrated consistently.

LUN conflict autoresolveHP 3PAR Peer Motion Utility supports migration from multiple source arrays into the same destinationin 1:1 mode. With this, there are chances of host being presented to destination and some LUNsthat are already assigned. As a result, if LUN conflict occurs data migration can abort and theentire volume can be marked as failed at preparation stage.

LUN conflict autoresolve 79

HP 3PAR Peer Motion Utility resolves LUN conflicts automatically by using the autoresolveoption. The default value of the autoresolve option is true.

• Host Basedcommand syntax: createmigration -sourceuid 2FFXXXX2AC003F8E -srchost"hostname" -migtype online -destcpg testcpg -destprov thin-autoresolve true

• Volume Basedcreatemigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap "[{pvol3, thin, testcpg}]"-migtypeonline -destcpg testcpg -destprov thin -autoresolve false

NOTE: The autoresolve parameter is optional and the default value is true. Specify theautoresolve parameter as false to deactivate automatic resolution.

Example 1 Output in case of conflict

showmigration

Table 2

VALUEFIELD

1422860307064MIGRATIONID

onlineTYPE

DMMT3PAR03SOURCE_NAME

PMMF400_3PAR_Array_Migration_EVDESTINATION_NAME

Mon Feb 02 12:28:27 IST 2015START_TIME

NAEND_TIME

preparationfailed(-NA-) (OIUERRPREP1021: Lun numberconflict exists for LUN# 0, 1, while presenting tohosts phost1

STATUS (PROGRESS)

HP 3PAR Peer Motion Utility Commands Quick ReferenceTable 3 CLI commands quick reference

ParametersDetailsDefinitionCommand

helpDisplays help for all the commandsLists common help forall the commands

“help” (page 97)

Adds a source storage system to theHP 3PAR Peer Motion Utility formigration.

Adds source storagesystem

“addsource”(page 97)

• type

• name

• uid

• mgmtip

• user

• password

• port

• secure

• help

Lists the source storage system thatare already added to the HP 3PAR

Lists source storagesystem

“showsource”(page 98)

• showcols

• unique_id


Table 3 CLI commands quick reference (continued)


Peer Motion Utility to be treated assource for a migration job.

• all

• listcols

• firmware

• name

• type

• management_server

• operational_state

• filewrite

• csvtable

• help

Displays supporteddestination host OS

“showpersona”(page 110)

• showcols

• filewritefor specified sourcehost OS • all

• hosttype

• osversion

• listcols

• hostpersona

• csvtable

Adds a destination storage system tothe HP 3PAR Peer Motion Utility thatis intended to be migrated.

Adds destinationstorage system

“adddestination”(page 99)

• type

• name

• uid

• mgmtip

• user

• password

• port

• secure

• help

Lists the Storage system that arealready added to the HP 3PAR Peer

Lists destinationstorage system

“showdestination”(page 101)

• showcols

• unique_id

HP 3PAR Peer Motion Utility Commands Quick Reference 81



Motion Utility to be treated asdestination of migration job.

• all

• listcols

• peer_ports

• firmware

• name

• type

• csvtable

• filewrite

• management_server

• operational_state

• help

Given a source storage system,shows a map of all connected sourceand destination storage system.

Lists connecteddestination or sourcestorage system

“showconnection”(page 101)

• all

• source_unique_id

• destination_unique_id

• showcols

• listcols

• source_name

• destination_name

• csvtable

• filewrite

• source_host_port

• destination_peer_port

• help

Performs preparation phase of amigration. Data transfer is not betriggered.

Performs thepreparation phase ofmigration

“createmigration”(page 103)

• sourceuid

• srcvolmap

• volmapfile

• srchost

• destcpg

• destprov

• migtype

• destinationuid

• clunodes

• singlevv

• help

• allvolumesincg

• autoresolve

• cgvolmap

Lists active migrations in preparationor data transfer phase and those that

Lists migrations“showmigration”(page 105)

• type

• migrationidare successful or aborted. By defaultall migrations are listed. Status of a • statusmigration will show the current state,

• showcols




progress percentage, and failurereason.

• listcols

• all

• filewrite

• csvtable

• sourcename

• destinationname

• help

Shows details at volume level areprovided for a given migration.

Shows details of aspecific migration

“showmigrationdetails”(page 107)

• migrationid

• showcols

• all

• taskid

• filewrite

• csvtable

• destinationvolume

• sourcevolume

• help

Starts the prepared migration orrestarts a prepared migration. Data

Starts the datatransfer of amigration

“startmigration”(page 107)

• migrationid

• helptransfer phase of migration isprocessed and historic data fromsource volumes is moved todestination volume over peer port.At storage system, presentation ofsource volume to source host will beremoved.

Clear completed or abort preparedmigrations. Active/Incompletemigrations cannot be removed.

Removes migration“removemigration”(page 108)

• migrationid

• help

Removes already added sourcestorage system and clears all relatedmigrations.

Removes sourceStorage system

“removesource”(page 108)

• uid

• type

• help

Removes already added destinationstorage system and clears all relatedmigrations.

Removes destinationStorage system

“removedestination”(page 109)

• uid

• type

• help

Adds the source or destinationstorage system in secure mode. It

Installs the certificatefrom specifiedStorage system

“installcertificate”(page 109)

• mgmtip

• Portfetches and displays certificatedetails. • Force

• Source

• help

Uninstalling the HP 3PAR Peer Motion UtilityThe following steps describe how to uninstall the HP 3PAR Peer Motion Utility from your system.

WARNING! Removing the software also completely deletes the database containing the sourceand destination storage system details and the migration definitions.

Uninstalling the HP 3PAR Peer Motion Utility 83

To remove the application from a Windows system:1. In Control Panel, select Programs→Programs and Features→Uninstall a Program, then select

the HP 3PAR Peer Motion Utility from the list and click Uninstall.2. In the Programs and Features dialog box, click Yes to delete the application.To remove the application from a Linux system:

• In the console, execute ./Linux_local_install.sh and enter y when prompted touninstall (the file is located under the directory where the binaries are extracted).


5 Post-Migration TasksSystem Post-Migration Tasks

Use the Post Migration Cleanup operation to remove the peer host after the data migration processis complete. The following conditions are required:

• Super user role


• No admitted volumes or importing volumes on the destination storage system

• A peer host existsUse the Remove PM Configuration operation to remove the peer motion configuration and alsoremove the peer host. You can keep the peer ports for later use or change them to host ports.

Fabric Topology Post-Migration TasksThe only task is to clean up the zoning between the source and destination storage systems afterall migrations between the two are complete.

Volume Post-Migration TasksAfter you verify that everything has been correctly migrated to the destination storage system, youcan reclaim the space on the source system by deleting the migrated volumes. Additionally, removethe host definition and volume exports on the source storage system. For more information onPost-Migration Cleanup, see “Post Migration Cleanup ” (page 33).

Remote Copy Post-Migration TasksIf you are using HP 3PAR Remote Copy Software, the next step is to perform the remote copypost-migration tasks:

• If necessary, recreate the remote copy groups on the destination storage system to match theremote copy groups on the source system.

• Perform the remote copy synchronization task.

• Remove the remote copy groups from the source system.

• Configure and start the remote copy groups on the destination storage system from a speciallycreated snapshot that represents the end step of the data migration.

For more information, see the HP 3PAR Remote Copy Software User's Guide and the HP 3PAR OSCLI Administrator’s Manual, available at the following website:HP Enterprise Library

System Post-Migration Tasks 85

http://www.hp.com/go/storage/docs

6 Support and Other ResourcesContacting HP

For worldwide technical support information, see the HP support website:http://www.hp.com/support

Before contacting HP, collect the following information:

• Product model names and numbers

• Technical support registration number (if applicable)

• Product serial numbers

• Error messages

• Operating system type and revision level

• Detailed questionsSpecify the type of support you are requesting:

Support requestHP 3PAR storage system

StoreServ 7000 StorageHP 3PAR StoreServ 7000 Storage


3PAR or 3PAR StorageHP 3PAR StoreServ 10000 Storage


HP 3PAR documentation

See:For information about:

The Single Point of Connectivity Knowledge for HPStorage Products (SPOCK) website:

Supported hardware and software platforms

SPOCK (http://www.hp.com/storage/spock)

The HP Storage Information Library:Locating HP 3PAR documentsStorage Information Library(http://www.hp.com/go/storage/docs/)By default, HP 3PAR Storage is selected under Productsand Solutions.

The HP Customer Self Repair Services Media Library:Customer Self Repair procedures (media)Customer Self Repair Services Media Library(http://h20464.www2.hp.com/index.html)Under Product category, select Storage. Under Productfamily, select 3PAR StoreServ Storage for HP 3PARStoreServ 7000, 8000, 10000, and 20000 Storagesystems.

HP Support Center:All HP productsHP Support Center(http://h20564.www2.hpe.com/portal/site/hpsc)

86 Support and Other Resources

http://www.hp.com/support


http://www.hp.com/go/storage/docs/

http://h20464.www2.hp.com/index.html

http://h20564.www2.hpe.com/portal/site/hpsc

Typographic conventionsTable 4 Document conventions

ElementConvention

Bold text • Keys that you press

• Text you typed into a GUI element, such as a text box

• GUI elements that you click or select, such as menu items, buttons,and so on

Monospace text • File and directory names

• System output

• Code

• Commands, their arguments, and argument values

<Monospace text in angle brackets> • Code variables

• Command variables

Bold monospace text • Commands you enter into a command line interface

• System output emphasized for scannability

WARNING! Indicates that failure to follow directions could result in bodily harm or death, or inirreversible damage to data or to the operating system.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

NOTE: Provides additional information.

RequiredIndicates that a procedure must be followed as directed in order to achieve a functional andsupported implementation based on testing at HP.

Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

Typographic conventions 87

mailto:[email protected]

7 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

88 Documentation feedback

mailto:[email protected]

A Peer Motion in a Remote Copy EnvironmentHP 3PAR Peer Motion allows the seamless migration of data from one storage system to anotherHP 3PAR StoreServ Storage system. Use the following procedures when migrating both primaryand secondary storage remote copy volumes to a new system using peer motion. These proceduresdo not use the GUI nor the HP 3PAR Peer Motion Utility, but execute directly from the HP 3PARCLI.

NOTE: When configuring peer motion, it may be necessary to make modifications to the FCswitch because the WWNs will change when moving from peer to host modes.

Migration of a Primary SystemMigrating from A to C, where A is currently in a Remote Copy group with B, the following scenariois envisaged:1. importvv begins the migration from A to C. Because all writes are passed onto A, Remote

Copy to B can continue without any changes.2. Once importvv has completed, it blocks I/O to A automatically, and provides us with

snapshot of the original base volume, A. In a synchronous RC system, A->B should be fullysynced. In a periodic system, it will require a final re-sync to ensure volumes are mirrored.

3. At this point, the secondary volume, B, can be admitted to a Remote Copy Group with theimported volume C, and the Remote Copy relationship can resume, with minimal downtimeand disruption.

Figure 51 Primary system migration

Detailed instructionsA) VV name under migration on old RC primary system: <old_primary_vv>B) VV name under migration on RC secondary system: <secondary_vv>C) VV name under migration on new RC primary system: <new_primary_vv>Assuming an existing RC relationship between A and B:1. On new storage system C: Set two unused FC ports to peer, where n:s:p is the port address.

Migration of a Primary System 89

NOTE: HP 3PAR Peer Motion requires two FC ports.

• controlport offline -f n:s:p

• controlport config peer -ct point n:s:p

2. On old storage system A: Set two FC ports to host. For each FC port to the host:

NOTE: You may not need to do this step as these would typically be available for host onthe old storage system.

• controlport offline -f n:s:p

• controlport config host -ct point -f n:s:p

3. On old storage system A: Configure the new storage system as a host and export every VVunder migration to it.• createhost <new_primary_host> <Port1_WWN> <Port2_WWN>

<Port1_WWN> and <Port2_WWN> are WWNs of the peer ports.

• showport n:s:p

• createlun <old_primary_vv> <LUN> <new_primary_host>

4. On new storage system C: Import the exported VVs. When showtarget is executed, twoports should now be active. These are from the host ports created in the previous step. TwoWWNs are exported, Node_WWN and Port_WWN. Node_WWN should be the same forboth ports. When issuing admitvv, specify the new VV name, and the Lun_WWN of thenode shown.• showtarget

• showtarget -rescan

• showtarget -lun <Node_WWN>

• admitvv <new_primary_vv>:<Lun_WWN>

• importvv -tpvv -snap @[email protected] -snp_cpg cpg_pri cpg_pri<new_primary_vv>

• showtask -d <task_ID>

Once this completes, stop the RC on the old storage system. At this point, there is a completereplica of the old primary on the new storage system and a snapshot of the data on the oldstorage system. new_primary_vv is the new name of the vlun which is being imported fromthe old storage system.

5. On old storage system A: When the peer motion completes, the following should be performedto stop the Primary -> Secondary. The first command syncrcopy is only applicable for theperiodic groups.• syncrcopy PM_group

• stoprcopygroup PM_group

• dismissrcopyvv <old_primary_vv> PM_group

6. On secondary B: When peer motion completes, remove the copy group (configured from theold storage system).• removercopytarget <old_primary_vv>

7. Restart rcopy with the new host on C on two ports, with two IP addresses:• creatercopytarget C IP n:s:p:<IP_ADDR_1> n:s:p:<IP_ADDR_2>

• showrcopy

90 Peer Motion in a Remote Copy Environment

8. On new storage system C: Bring up RC. When peer motion completes, a snapshot of the basevolume at the point of completed migration displays.• showport -rcip

• controlport rcip addr <IP_ADDR_1> 255.255.255.0 n:s:p

• controlport rcip addr <IP_ADDR_2> 255.255.255.0 n:s:p

9. Create new RC target for B at IP_ADDR_B:• creatercopytarget B IP n:s:p:<IP_ADDR_B>

• creatercopygroup PM_group B:periodic

• admitrcopyvv <new_primary_vv> PM_group B: <secondary_vv>

• startrcopygroup PM_group <new_primary_vv>:<new_primary_vv>.ro

• showrcopy

New volume has now been migrated from old primary to new primary, and remote copyre-established.

Migration of a Secondary SystemThe following details migrating from B to C, where B is currently acting as a secondary volume forA. During a peer motion migration, no data can be written to the original volume (in this case, B).For the secondary, migration is done from a snapshot, which allows for maintaining an activesecondary at all times.

Figure 52 Secondary system migration

A) VV name under migration on old RC primary system: <primary_vv>B) VV name under migration on RC secondary system: <old_secondary_vv>C) VV name under migration on new RC primary system: <new_secondary_vv>Remote copy group: RCPM_GroupNew RC group: New_PM_Group

Migration of a Secondary System 91

NOTE: The following assumes that C has been configured as a host on B. See “Migration of aPrimary System” (page 89) for details.

1. On A, ensure no resyncs are running. Once any remaining syncs complete, stop the RC groupand take snapshots of the primary and secondary VVs:• stoprcopygroup RCPM_Group

2. When an RC group stops, it creates a snapshot of the VV. Create a copy of the most recentsnapshot. The showvv displays the most recent snapshot, usually named, rcopy.xx.YYYY.zz,where YYYY is the ID of the VV. Use showrcopy –d for more information.• createsv RCPM_ResumeSS rcopy.xx.YYYY.zz

3. On B:• createsv <old_secondary_vv_SS> <old_secondary_vv>

4. Export the snapshot to C as a disk.• createvlun <old_secondary_vv_SS> 1 C

5. On C: When exported, rescan the bus and admit the volume. Where 2FF70002AC000091is the Node_WWW shown and 50002AC003E80091 is the Lun_WWW of the disk.• showtarget -rescan

• showtarget

• showtarget -lun 2FF70002AC000091

• admitvv RCNewSecVV:50002AC003E80091

• importvv -tpvv -snap @[email protected] -snp_cpg cpg_pri cpg_pri<new_secondary_vv>

6. On A, restart the group. You do not have to wait for the importvv to complete.• startrcopygroup RCPM_Group

7. At this point, maintain a full primary -> secondary relationship for the duration of the import,minimizing downtime. Once the peer motion migration completes, stop and delete the remotecopy group.

NOTE: When remote copy groups are removed, all associated snapshots are removed withit (why the earlier copy was made).

• stoprcopygroup RCPM_Group

• removercopygroup RCPM_Group

8. Create new RC target (in this case RCIP):• creatercopytarget C IP n:s:p:10.100.37.164

• creatercopygroup New_PM_group C:periodic

• admitrcopyvv <primary_vv> New_PM_group C:<new_secondary_vv>

9. Start the new group• startrcopygroup New_PM_group <primary_vv>:RCPM_ResumeSS.ro

• showrcopy

The new system should be up and running.

NOTE: The following only affects synchronous groups: There are potential corner cases whichmay result in miss compares occurring between the primary and the new secondary, such as if thesnapshots are not exact, due to I/Os not being propagated to the secondary after the RC groupstops. However, the planned feature of user initialized synchronous snapshots between the twosystems will mitigate this risk.

92 Peer Motion in a Remote Copy Environment

B Additional Steps to Migrate HP-UX HostsNOTE: The procedures described in this section are only for disks under HP-UX's LVM volumemanagement.

Rescanning for New LUN PathsBefore continuing with migration, it is recommended that you rescan for new LUN paths and makea note of the new paths to the volumes:

#ioscan -fnC disk

HP-UX 11i V3HP-UX 11i v3 standalone and Serviceguard clustered hosts can be migrated by using the onlinemigration procedure. No additional configuration is required on the hosts.

HP-UX 11i V2HP-UX 11iv2 standalone hosts can be migrated by using the online migration procedure. However,after zoning in the destination storage system to the standalone hosts, the new paths/physicalvolumes (PVs) must be added to the volume group/PVLinks configuration by using the vgextendcommand before removing the paths to the source storage system. For example:

# vgextend my_standalone_VG new_pv_path1 new_pv_path2 …

To confirm configuration of the PVLinks configuration, execute the vgdisplay command.A Serviceguard cluster, running on HP-UX 11i V2, can also be migrated by using the onlinemigration procedure, but if shared volume groups that use the Shared Logical Volume Manager(SLVM) are used, then additional configuration steps are required because the shared volumegroup does not automatically recognize new paths to the volume exported through the destination.Use the following single-node online reconfiguration (SNOR) operation (see “Single-node OnlineReconfiguration” (page 93) to change the configuration of a shared volume group, while keepingit active in only a single node. During the volume group reconfiguration, applications on at leastone node will be available.

Single-node Online Reconfiguration1. Identify the shared volume group on which a configuration change is required. Name it

vg_shared.2. Identify one node of the cluster which is running an application using the shared volume group.

Call it node1. The applications on this node that are using the volume group, vg_shared,will remain unaffected during the procedure.

3. Stop the applications using the shared volume group on all the other cluster nodes, thus scalingdown the cluster application to the single cluster node, node1.

4. Deactivate the shared volume group on all other nodes of the cluster, except node1, by issuingthe vgchange command -a n option:

# vgchange -a n vg_shared

5. Ensure that the volume group, vg_shared, is now active only on a single cluster node, node1,by using the vgdisplay command on all cluster nodes. The Status should show that thevolume group is available on a single node only.

Rescanning for New LUN Paths 93

6. On node1, change the activation mode to exclusive by issuing the following command:

# vgchange -a e -x vg_shared

7. On node1, make a note of the new pv_paths to the PVs already in the volume group (fromthe output of the LUN rescan; see “Rescanning for New LUN Paths” (page 93)). Add all thenew paths to the volume group, using the following command:

# vgextend vg_shared pv_path

8. Export the changes to other cluster nodes:a. From node1, export the mapfile for vg_shared:

# vgexport -s -p -m /tmp/vg_shared.map vg_shared

b. Copy this mapfile, /tmp/vg_shared, to all the other nodes of the cluster.c. On the other cluster nodes, export vg_shared and re-import it using the new map file:

# ls -l /dev/vg_shared/groupcrw-rw-rw- 1 root sys 64 0x050000 Nov 16 15:27 /dev/vg_shared/group

d. Make a note of the minor number (0x050000 in the example above); it should matchthe minor number as shown in the mknod ... command in the following example:

# vgexport vg_shared# mkdir /dev/vg_shared# mknod /dev/vg_shared/group c 64 0x050000# vgimport -m /tmp/vg_shared.map -s vg_shared

9. Change the activation mode back to shared on all the cluster nodes:a. Change the mode back to shared on node1 by issuing the following command:

# vgchange -a s -x vg_shared

b. Change the mode to shared on the other cluster nodes by issuing the following command:

# vgchange -a s vg_shared

Applications using the shared volume group can now be restarted on other hosts.For more information about SLVM, see SLVM Online Volume Re-configuration. To obtain a copyof this documentation, see the HP Support Center website:HP Support CenterIf you are migrating cluster lock disks, you can update cluster lock disk configuration online byfollowing these steps:1. Make a note of the new pv_paths to the lock disks from the output of the LUN rescan (see

“Rescanning for New LUN Paths” (page 93).2. Execute the following command:

# vgcfgrestore -n /dev/vg_lock pv_path

94 Additional Steps to Migrate HP-UX Hosts

http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?lang=en&cc=usm/bizsupport/TechSupport/Home.jsp?lang=en&cc=us.com/bc/docs/support/SupportManual/c01914684/c01914684.pdf

3. For each node in the cluster configuration file, modify the values of FIRST_CLUSTER_LOCK_PVand SECOND_CLUSTER_LOCK_PV.

4. To check the configuration, run the cmcheckconf command.5. To apply the configuration, run the cmapplyconf command.For more information on updating cluster lock disk configuration, see Managing ServiceguardSeventeenth Edition. To obtain a copy of this documentation, see the HP Support Center website:HP Support Center

Single-node Online Reconfiguration 95

http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?lang=en&cc=us

C Data Migration for VMware vSphere ESXi hostsThis chapter provides information about using HP 3PAR Peer Motion to migrate VMware vSphereESXi hosts from a source storage system running HP 3PAR StoreServ Storage system OS 3.1.1 toa destination storage system running HP 3PAR StoreServ Storage system OS 3.2.1. For moreinformation about supported migration paths with VMware vSphere ESXi, see the HP SPOCK 3PARPeer Motion Support Matrix.VMware vSphere ESXi is supported exclusively with Host Persona 6 on HP 3PAR OS 3.1.1 andexclusively with Persona 11 from the HP 3PAR StoreServ Storage 3.2.1, onwards. This implies thatthere is no common persona between source and destination storage systems that can be used formigration. Therefore, migration procedure for ESXi hosts in this scenario requires the volumes onthe HP 3PAR source and destination storage systems be concurrently exported to the ESXi hostsvia different host personas (6 on the source and 11 on the destination). However, at the conclusionof the data migration, the user must make the required ESXi configuration setting changes to supportongoing host connectivity with the newly migrated volumes through host persona 11.

Peer Motion Storage ConfigurationAs part of the migration process, use the Copy Storage Settings and Configurations wizard fromHP 3PAR Management Console (IMC) to copy the storage settings from source to destinationstorage system. However, the resulting host definition on the destination storage system will usepersona 6, which is not a supported persona with 3.2.1 and onwards. These host definitions mustbe changed to persona 11, before proceeding with the Migrate Data step of the migration process.To change the host persona, ensure that no active or online paths exist from the ESXi hosts to thedestination storage system, before changing the persona for the hosts being migrated.

Post Peer Motion Data Migration ProcedureAfter the migration, the original custom SATP rule being use with host persona 6 needs to bechanged to reflect the SATP rules required for persona 11. For more information about how toapply the recommended SATP rules, see the HP 3PAR VMware vSphere ESX/ESXi ImplementationGuide (Multipath Failover Considerations and I/O Load Balancing section in Chapter 5).

96 Data Migration for VMware vSphere ESXi hosts

D HP 3PAR Peer Motion Utility CommandsNOTE: Examples shown in this sections are examples only and may not reflect your system output.

helpLists help for all CLI commands.

DESCRIPTIONThe help command lists all commands details that are supported by CLI.

EXAMPLES

DescriptionName

Lists the source storage systems that are already added to be treated as source for amigration job. It shows an empty table if no source storage systems are found.

showsource

Displays the list of available migrations.showmigration

Removes the migration identified by the migration ID specified.removemigration

Starts prepared migration OR restarts a prepared migration.startmigration

Removes already added source storage system and clears all related migrations.removesource

Adds a source storage system that is intended to be migrated.addsource

Displays connection between all the configured source and destination storage systems.-source or -destination can't be used together.

showconnection

Performs preparation phase of a migration.createmigrationActual data transfer is not triggered by this command.

Installs certificate from a given storage systeminstallcertificate

Removes already added destination storage system and clears all related migrations.removedestination

Displays global help command for CLIhelp

Lists the destination storage systems, already added and treated as destination for amigration job. It shows an empty table if no destination storage systems are found.

showdestination

Adds a destination storage system that is intended to be migrated.adddestination

Displays the list of volumes associated with the specified migration and their correspondingstatus.

showmigrationdetails

addsourceAdds a source storage system.

DESCRIPTIONThe addsource command adds a source storage system to the HP 3PAR Peer Motion Utility thatis intended to be migrated.While adding a new source or destination HP 3PAR StoreServ Storage System that has 3.1.2 MU3P16 or later applied, follow the error and resolution message to solve the problem:"ERROR: OIUERRDST0010 Unable to validate certificate for HP 3PAR StorageSystem OIURSLDST0010. Please use the installcertificate command toaccept the certificate."OR

help 97

"ERROR: OIUERRCER0000 Unable to validate CA signed certificate.OIURSLCER0000 Please follow steps mentioned in migration guide to installthe certificate."

NOTE:• While adding a new destination for HP 3PAR StoreServ Storage system that has CA signed

certificate, the following error message appears: ERROR: OIUERRCER0000 Unable tovalidate CA signed certificate. OIURSLCER0000 Please follow stepsmentioned in migration guide to install the certificate.

• Copy the CA Certificate and the Intermediate Certificate to the \InForm MC\Security\folder to make sure that the Management Console can recognize the Root CA and theIntermediate Certificates from the HP 3PAR StoreServ Storage System.

• Perform addsource again to add HP 3PAR StoreServ Storage System.

PARAMETERS

Mandatory/optionalDescriptionName

MandatoryStorage system family type like3PAR.

type

MandatoryIP address of the managementstation to connect to get details.

mgmtip

MandatoryUsername to be used to connect tomanagement application.

user

MandatoryPlain text password to be used.password

OptionalFriendly name of the Storagesystem. This is required especially

name

when there are multiple storagesystems managed under same IPaddress.

OptionalUnique number that represents asource in the HP 3PAR Peer MotionUtility.

uid

OptionalPort number on which managementapplication accepts request to

port

connect and provide sourcestorage system details. If not founddefault based on storage systemtype will be used.

OptionalTrue/False. This enables ordisables secure channel

secure

communication with source Storagesystem, wherever applicable.Default value will be true or defaultused by source storage systemcommunication layer.

EXAMPLES

>addsource -mgmtip 11.11.11.11 -user 3parsrc -password 3parpeer -type 3PAR>SUCCESS: Added source storage system.

showsourceLists source storage systems.

98 HP 3PAR Peer Motion Utility Commands

DESCRIPTIONThe Showsource command lists the source storage systems that are already added to the HP3PAR Peer Motion Utility to be treated as source for a migration job.

PARAMETERS


OptionalFriendly name of the storagesystem.

name

OptionalThis can be specific storagesystem name with model

type

identifier or the storage systemfamily name at least (Forexample, 3PAR).

OptionalDisplay all details withheadings.

all

OptionalThis is serial number or WWNor hyphenated WWN.

unique_id

OptionalAny argument that followsshowcols depicts field to

showcols

display columns. Accepts acomma separated list of columnnames.

OptionalDisplay the list of column namesapplicable to that command.

listcols

These column names can beused for filtering using theshowcols command.

OptionalFirmware version.firmware

OptionalThe IP address/FQDN of themanagement server thatmanages this storage system.

management_server

OptionalOperational state of the storagesystem (Good, Failed,Attention).

operational_state

OptionalThis command can be used toprint delimited output.

csvtable

OptionalRedirects the output of thecommand to a file.

filewrite

EXAMPLES

showsource >NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE >PMM3PAR 3PAR <sourceuid> 3.1.3 11.11.11.11 Good

adddestinationAdds a destination storage system.

DESCRIPTIONThe adddestination command adds a destination Storage system to the HP 3PAR Peer MotionUtility that is intended to be migrated.

adddestination 99

While adding a new source or destination HP 3PAR StoreServ Storage System that has 3.1.2 MU3P16 or later applied, follow the error and resolution message:“ERROR: OIUERRDST0010 Unable to validate certificate for HP 3PAR StorageSystem OIURSLDST0010. Please use the installcertificate command toaccept the certificate..”OR“ERROR: OIUERRCER0000 Unable to validate CA signed certificate.OIURSLCER0000 Please follow steps mentioned in migration guide to installthe certificate.”Add the following steps for CA signed certificate storage system:

NOTE:• While adding a new destination for HP 3PAR StoreServ Storage system that has CA signed

certificate, the following error message appears: ERROR: OIUERRCER0000 Unable tovalidate CA signed certificate. OIURSLCER0000 Please follow stepsmentioned in migration guide to install the certificate.

• Copy the CA Certificate and the Intermediate Certificate to the \InForm MC\Security\folder to make sure that the Management Console can recognize the Root CA and theIntermediate Certificates from the HP 3PAR StoreServ Storage System.

• Perform adddestination again to add HP 3PAR StoreServ Storage System.

PARAMETERS


MandatoryIP address of the management station toconnect to get details.

mgmtip

MandatoryUsername to be used to connect tomanagement application.

user

MandatoryPlain text password to be used.password

OptionalStorage system family type like 3PARtype

OptionalFriendly name of the storage system. This isrequired especially when there are multiple

name

Storage systems managed under same IPaddress.

OptionalUnique number that represents a source inthe HP 3PAR Peer Motion Utility.

uid

OptionalPort number on which managementapplication accepts request to connect and

port

provide source storage system details. If portnumber is not found, the default numberbased on storage system type is used.

OptionalTrue/False. This enables or disables securechannel communication with source storagesystem, wherever applicable.

secure

The default value is false or default used bysource storage system communication layer.

EXAMPLES

>adddestination -mgmtip 11.11.11.11 -user 3pardst -password 3parhelp -type 3PAR>SUCCESS: Added destination storage system.


showdestinationLists destination storage systems.

DESCRIPTIONThe showdestination command lists the storage systems that are already added to the HP3PAR Peer Motion Utility to be treated as destination of migration job. It shows an empty table, ifno destination storage systems are found.

PARAMETERS


OptionalFriendly name of the storagesystem.

name

OptionalThis is storage system family name(for example, 3PAR).

type


csvtable


filewrite

OptionalDisplay all details with headings.all

OptionalAny argument that followsshowcols depicts field to display

showcols

(columns).Accepts a commaseparated list of column names.

OptionalThis is serial number or WWN orhyphenated WWN.

unique_id

OptionalList of host ports hyphenated 64bit WWN (N:S:P). Peer will bemarked as peer.

peer_ports

OptionalDisplays the list of column namesapplicable to that command.

listcols

OptionalFirmware version.firmware

OptionalThe IP address/FQDN of themanagement server that managesthis storage system.

management_server

OptionalOperational state of the storagesystem (Good, Failed, Attention).

operational_state

EXAMPLES

showdestination>NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE PEER_PORTS >DMMT3PAR02 3PAR 2FF70002AC003F9C 3.1.3 11.11.11.11 Normal 2211-0202-AC00-3F9C(2:1:1) 2311-0202-AC00-3F9C(3:1:1)

showconnectionLists connected destination and source storage systems.

showdestination 101

DESCRIPTIONBy default, the showconnection command shows a map of all connected source and destinationstorage systems. There should be 1:1 mapping between source and destination storage systemsand destination and source systems for peer port FC connection. Given a source storage system,this shows all the configured destination storage systems, and vice versa.

PARAMETERS



csvtable


filewrite

OptionalDisplays all details withheadings.

all

OptionalUID of the source storagesystem. Displays all peer

source_unique_id

connections for the givensource storage system.

OptionalUID of the destination storagesystem. Displays all peer

destination_unique_id

connections for the givendestination storage system.

OptionalHost OS type of destinationstorage system

persona

OptionalAny argument that followsshowcols depicts field to

showcols

display (columns). Accepts acomma separated list ofcolumn names.

OptionalDisplay the list of columnnames applicable to that

listcols

command. These columnnames can be used for filteringusing the showcolscommand.

OptionalFriendly name of the sourcestorage system.

source_name

OptionalFriendly name of thedestination storage system.

destination_name

OptionalHost port WWPN (name) ofthe source which is connectedto corresponding peer port.

source_host_port

OptionalPeer portWWPN(WWNN)(N:S:P) towhich source is connected.

destination_peer_port

EXAMPLES

showsource >SOURCE_NAME SOURCE_UNIQUE_ID DESTINATION_NAME DESTINATION_UNIQUE_ID DESTINATION_PEER_PORT SOURCE_HOST_PORe >PMM3PAR <sourceuid> DMMT3PAR02 2FF70002AC003F9C 2311-0202-AC00-3F9C(3:1:1) 2223-0002-AC00-1BA0(2:2:3)


>PMM3PAR <sourceuid> DMMT3PAR02 2FF70002AC003F9C 2311-0202-AC00-3F9C(3:1:1) 2323-0002-AC00-1BA0(3:2:3)>PMM3PAR <sourceuid> DMMT3PAR02 2FF70002AC003F9C 2211-0202-AC00-3F9C(2:1:1) 2223-0002-AC00-1BA0(2:2:3)>PMM3PAR <sourceuid> DMMT3PAR02 2FF70002AC003F9C 2211-0202-AC00-3F9C(2:1:1) 2323-0002-AC00-1BA0(3:2:3)

createmigrationPerforms the preparation phase of migration.

DESCRIPTIONThe createmigration command performs preparation phase of a migration. Actual data transferwill not be triggered by this command. This does following for a given set of source volumes whilepresenting to HP 3PAR destination storage system.

NOTE: After using this command and before start of migration, you should perform unzoningactivities and/or rescan of HBA and/or reboot of source host and/or any other management jobsas required.

1. An entry of destination storage system is created on source storage system. It is treated as aLinux host.

2. Source volumes are made available to this host representing HP 3PAR destination.3. Source host information is captured from source storage system and accordingly created at

destination storage system.4. Admit phase in case of HP 3PAR will create a corresponding entry of virtual volume to host

mapping at HP 3PAR. The virtual volume is exported to source host if online migration. Else,export is deferred in case of minimally disruptive migration. Persona setting for volume atdestination will be set accordingly. The virtual volume will be in peer mode. There is someproxy volume that is created to handle the I/Os in this stage.

5. If a source volume has implicit relationship with other source volumes, that gets auto-selectedand source volume’s CPG and provisioning applicable is applied to these implicit selections,as well.

6. The RAID level at the destination, once migrated, will be dependent on the CPG chosen andcan be different.

NOTE: If a destination storage system has dedupe capability, you can reduce its storage spaceby eliminating redundant data during migration at the 3PAR destination. To do this, for thecreatemigration command, specify the destprov parameter as dedupe. You can thenspecify those CPGs as destcpg that support the dedupe feature.

PARAMETERS


OptionalMigrates all volumes specified in srcvolmapconsistently

allvolumesincg

OptionalMigrates subset of volumes consistentlycgvolmap

NOTE: At any given point, either theallvolumesincg or the cgvolmapparameter can be provided, not both.

OptionalResolves LUN conflicts automaticallyautoresolve

MandatoryMigrates the uid from which source volumeswill be migrated.

sourceuid

createmigration 103

A combination of this is mandatory asspecified by user.

Map which informs about the source volumesfor migration. A list of volume name that

srcvolmapor volmapfile

For example, if srchost is there, destcpgand destprov should be there.

identifies the volume or volume set name thatshould be provided.Note: The volume set name must precedewith "set:".

If srcvolmap is there, srchost should notbe there.

It can also have mapping of every sourcevolume to required provisioning or

If srcvolmap has CPG and Provinformation, then destcpg and destprovare not required.destination common provisioning group

(CPG). This is required if destCPG anddestProv is not provided.-srcvolmap[{"source volume path/uniquename", desired destination provisioning aftermigration (Thin/Full/Dedupe), desireddestination CPG name},{…},…]Sample content of volmapfile:TestVolume,Thin,Test_CPGProvisioning and CPG entry here willoverride default in destcpg and destprov.Possibilities:"vv2",thin"vv3",cpg3"vv""vv4",full,cpg4"vv5",dedupe,cpg5

Name of the host/host set or full nameincluding path of the host for which all

srchost

source volumes should be considered formigration. This should not be there ifsrcvolmap or volmapfile is there.Note: In the case of host set, the name ofhost set should be preceded by “set:”.

CPG’s friendly name where the migratedvolumes will be made available (If notprovided).

destcpg

Provisioning type of the volumes that will becreated in destination as a result of migration(Thin/full/dedupe)

destprov

OptionalView HP SPOCK (at http://www.hp.com/storage/spock) and choose appropriate type

migtype

(minimally disruptivemigration/online/offline). For differentversion of operating system, we can havedifferent migration type. Since, there is nohost interaction layer, user has to give thisas manual input. If this parameter is notprovided, default will be offline. If thisparameter is not applicable, error should bethrown.

OptionalUID of the destination storage system. Sincethere is a 1:1 mapping, this is an optional

destinationuid

parameter as the destination will beauto-selected.




OptionalNumber of nodes in cluster. This signifiesthat the host under consideration for

clunodes

migration is clustered host. Also, the numberof NPIV ports created will be same asspecified in this param. This happens onlyfor almost online migration type.

OptionalUse to migrate a subset of volumesprovisioned to a host.

singlevv

EXAMPLES

createmigration -sourceuid 2FFXXXX2AC003F8E -srcvolmap "[{vol1, thin, testcpg} {vol2, thin, testcpg} {vol3, thin, testcpg}]" -destcpg testcpg -destprov testcpg cgvolmap{"values":{"cg1":["vol1","vol2]}}>SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1397243589759

Where the cgvolmap parameter accepts the name of consistency group name and volumes names to be migratedconsistently.Expected behavior: vol1, vol2, vol3 shall be created at the destination, and vol1 and vol2 will be migrated consistently.createmigration -sourceuid 2FFXXXX2AC003F8E -srchost "hostname" -migtype online -destcpg testcpg -allVolumesInCG>SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1397243589759

Expected behavior: At the destination system, all volumes including implicit volumes exported to host will be createdand migrated consistently.createmigration -sourceuid 2FFXXXX2AC003F8E -srchost "hostname" -migtype online -destcpg testcpg -destprov thin -autoresolve true/false>SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1397243589759

Expected behavior: If there is any lun conflict during migration then conflict will be resolved automatically if value istrue or if the autoresolve parameter is not specified.createmigration -sourceuid 2FF70002AC001BA1 -srcvolmap [{"test","thin","test"}] >SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1397243589759

createmigration -sourceuid 2FF70002AC001BA1 -srcvolmap [{"test","thin","test"}] -migtype MDM -clunodes 2>SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1397243589759

createmigration -sourceuid 2FF70002AC001B0 -srchost "h1" -migtype MDM -destcpg FC_r1 -destprov full>SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1397243589759

createmigration -sourceuid 2FF70002AC001BA1 -volmapfile "C:\\testmigrationcommands.txt">SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1397243589759

showmigrationLists migrations.

showmigration 105

DESCRIPTIONThe showmigration command lists active migrations in preparation or data transfer phase aswell as the ones that are successful or aborted. By default all migrations are listed. The status of amigration shows the current state, as well as the progress percentage and failure reason wheneverapplicable.

NOTE: If the showmigration command displays the migration status as failed, this means thatat least one volume migration has failed.To get details for individual volumes, use the showmigrationdetails command.For restarting the failed migration, use the startmigration command again with the samemigration ID.

PARAMETERS


OptionalOnline/MDM/Offline. Display allmigrations that are of the typespecified.

type

OptionalDisplays migrations that are in thespecified state.

status

OptionalUnique number that identifies amigration after createmigration

migrationid

is complete. If this is specified, thereis no need to provide source anddestination details.

OptionalThis command can be used to printdelimited output.

csvtable

OptionalRedirects the output of the commandto a file.

filewrite

OptionalDisplays all details with headings.all

OptionalAny argument that follows showcolsdepicts field to display (columns).

showcols

Accepts a comma separated list ofcolumn names.

OptionalDisplay the list of column namesapplicable to that command. These

listcols

column names can be used for filteringusing the showcols command.

OptionalSource storage system name. Displaysmigrations created between this source

sourcename

and destination storage systemsconnected to it.

OptionalDestination storage system name.Displays migrations created between

destinationname

this destination and source storagesystems connected to it.

EXAMPLES

showmigration>MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE)


>1397244158146 offline PMM3PAR DMMT3PAR02 Sat Apr 12 00:52:38 IST 2014 -NA- preparationcomplete(100%)(-NA-)

showmigrationdetailsShows details of a specific migration.

DESCRIPTIONUse the showmigrationdetails command to view details at volume level for a specificmigration. Task ID is the corresponding 3PAR task ID, if found. Status at individual volume levelsis on similar lines as status of migration.

PARAMETERS


MandatoryUnique ID that gets generated afterthe CreateMigration operation.

migrationid

Displays the migrationcorresponding to the ID specified.

OptionalThis command can be used to printdelimited output.

csvtable

OptionalRedirects the output of the commandto a file.

filewrite

OptionalDisplays all details with headings.all

OptionalAny argument that follows showcolsdepicts field to display (columns).

showcols

Accepts a comma separated list ofcolumn names.

OptionalDisplays the list of column namesapplicable to that command.

listcols

OptionalOnline/MDM/Offline. Displays allmigrations that are of the typespecified.

taskid

OptionalSource volume name. Displaysinformation corresponding to thisvolume.

sourcevolume

OptionalDestination volume name. Displaysinformation corresponding to thisvolume.

destinationvolume

EXAMPLES

showmigrationdetails -migrationid 1397244158146>SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS>test test 6134 Completed

startmigrationStarts the data transfer of a migration.

DESCRIPTIONThe startmigration command starts or restarts a prepared migration to go through data transferphase of migration.

showmigrationdetails 107

PARAMETERS


MandatoryUnique number representing themigration that is in prepared orincomplete state.

migrationid

EXAMPLES

startmigration –migrationid 1394789473527 >SUCCESS: Data transfer started successfully.

removemigrationRemoves migration.

DESCRIPTIONThe removemigration command clears completed or abort prepared migrations.Active/Incomplete migrations cannot be removed.

PARAMETERS


MandatoryNumber that represents amigration in completed/abortedstate.

migrationid

EXAMPLES

removemigration –migrationid 1122334456 >SUCCESS: The specified migration is successfully removed.

removesourceRemoves source storage system.

DESCRIPTIONThe removesource command removes already added source storage system and clears allrelated migrations.If the state of the source storage system is:• "No migration created," the command will delete the source storage system from the HP 3PAR

Peer Motion Utility• "Active migration (prepared or data transfer in progress)" the command will output error• "Completed migrations" the command removes already added source storage system and

clears all related migrations.

NOTE: When using the removesource command, historic information about previous completedmigrations related to the source or destination storage systems will be removed.


PARAMETERS


MandatoryUnique number that representsa source in HP 3PAR PeerMotion Utility.

uid

MandatoryType of source storage system.type

EXAMPLES

removesource –uid 2FF70002AC00DB5 –type 3PAR >SUCCESS: Removed source storage system.

removedestinationRemoves an added destination storage system.

DESCRIPTIONThe removedestination command removes already added destination storage system andclears all related migrations.

NOTE: When using theremovedestination command, historic information about previouscompleted migrations related to the source/destination storage systems will be removed.

PARAMETERS


MandatoryUnique number that representsa source in the HP 3PAR PeerMotion Utility.

uid

OptionalType of source storage system.type

EXAMPLES

removedestination –uid 2FF70002AC003F8E >SUCCESS: Removed destination storage system.

installcertificateInstalls the certificate from specified storage system.

DESCRIPTIONThe installcertificate command fetches and displays the certificate details for a storagesystem that is planned to be added as source or destination.

removedestination 109

NOTE:• Follow the screen instructions to accept or reject the certificate. If you accept the certificate,

the certificate downloads in the InFormMC/security folder of the user directory and theninstalls.

• After the certificate is installed successfully, you can add the storage system in secure mode.• In the scripting mode, user can choose the force option to render the confirmation certificate

screen as non–interactive. Therefore, the certificate will not appear and the screen to confirmor reject the certificate will not appear.

• By default, the command is interactive and cannot be used for scripting.

PARAMETERS


MandatoryIP address of storage system to connect and get the details.mgmtip

OptionalPort number on which management application accepts request to connectand provide source/destination storage system details. If the port numberis not found, the default number based on storage system type is used.

port

OptionalUse this option to determine whether to display the certificate details orskip to display the certificate details.

force

OptionalUse this option to determine the type of source storage system. It is amandatory argument. Provide source parameter as 3PAR.

source

EXAMPLESaddsource

OutputCommand

Do you accept the certificate? Y/NSUCCESS: installed certificate successfully.

installcertificate –mgmtip 1.1.1.1Y

SUCCESS: installed certificate successfully.installcertificate – mgmtip 1.1.1.1 –force

SUCCESS: installed certificate successfully.installcertificate – mgmtip 1.1.1.1 –force –source 3par

showpersonaThe showpersona command displays the supported destination host OS for a specified sourcehost OS.

Table 5 Host Persona

HOST PERSONA3PAR OS VERSIONHOST TYPE

Windows 20123.1.2windows2012

Solaris 9/103.1.2sunsolaris

Solaris 113.1.2sunsolaris

AIX3.1.2ibmaix

HP-UX3.1.2hpux

Windows 2008/2008 R23.1.2windows2008

ESX 4.x/5.x3.1.2vmware


Table 5 Host Persona (continued)

HOST PERSONA3PAR OS VERSIONHOST TYPE

Red Hat Enterprise Linux3.1.2linux

SuSE3.1.2linux

OpenVMS3.1.2openvms

Windows 20033.1.2mswindows

Windows 2012 / WS 2012 R23.1.3windows2012

Solaris 9/103.1.3sunsolaris

Solaris 113.1.3sunsolaris

AIX3.1.3ibmaix

HP-UX (11i v1, 11i v2)3.1.3hpux

HP-UX (11i v3)3.1.3hpux

Windows 2008/2008 R23.1.3windows2008

ESX 4.x/5.x3.1.3vmware

RHE Linux (5.x, 6.x)3.1.3linux

SuSE (10.x, 11.x)3.1.3linux

OpenVMS3.1.3openvms

Windows 20033.1.3mswindows

EXAMPLE

NOTE: Execute the showpersona command to see the list of host persona values:

>showpersona>HOSTTYPE OSVERSION HOSTPERSONA

>windows2012 3.1.2 Windows 2012

>sunsolaris 3.1.2 Solaris 9/10

>sunsolaris 3.1.2 Solaris 11

>ibmaix 3.1.2 AIX

>hpux 3.1.2 HP-UX

>windows2008 3.1.2 Windows 2008/2008 R2

>vmware 3.1.2 ESX 4.x/5.x

>linux 3.1.2 Red Hat Enterprise Linux

>linux 3.1.2 SuSE

>openvms 3.1.2 OpenVMS

>mswindows 3.1.2 Windows 2003

>windows2012 3.1.3 Windows 2012 / WS2012 R2

>sunsolaris 3.1.3 Solaris 9/10

showpersona 111

>sunsolaris 3.1.3 Solaris 11

>ibmaix 3.1.3 AIX

>hpux 3.1.3 HP-UX (11i v1, 11i v2)

>hpux 3.1.3 HP-UX (11i v3)

>windows2008 3.1.3 Windows 2008/2008 R2

>vmware 3.1.3 ESX 4.x/5.x

>linux 3.1.3 RHE Linux (5.x, 6.x)

>linux 3.1.3 SuSE (10.x, 11.x)

>openvms 3.1.3 OpenVMS

>mswindows 3.1.3 Windows 2003


E TroubleshootingThe following describes troubleshooting for HP 3PAR Peer Motion data migration and the HP 3PARPeer Motion Utility.

Troubleshooting Peer Motion Data MigrationIf issues arise, you can access the event log through the HP 3PAR Management Console EventManager. Additionally, the HP 3PAR Management Console has a log file directory on the clientsystem. This directory is located at C:\Users\<userID>\InFormMC\log.Very often, errors in data migration are caused by zoning issues. Verify the zoning status in theHP 3PAR Management Console on the Summary tab, as shown in the following figure:

Migration Phase IssuesTroubleshooting a volume admit or import failure:

• For minimally disruptive migration and offline migration, verify the destination storage systemhas no active paths. This can be done by checking the host screen on HP 3PAR ManagementConsole or using the CLI command, showhost.

• Monitor the migration task by checking the task screen or using the CLI command, showtask.Then, determine where the operation failed.

• If a failure occurs before the volume import stage, but after volumes have been admitted onthe destination storage system, it is possible to manually return the system to the pre-admitstate. This process is non-disruptive to the hosts provided the appropriate zoning and hostmultipathing have been re-established. The host must have access to the volume through thesource system.

NOTE: Unzoning operations are not required for single volume migration.

To return the system to its state before a volume admit failure:1. On the fabric and host—If the host has already been unzoned from the source system

then rezone it back to that system and confirm that I/O is once again being directed tothe source system.

2. On the fabric and host—Unzone the host from the destination storage system and verifythat all access to the volumes is now only through the source system.

3. On the destination storage system—Remove the VLUNs on the destination storage systemfor the peer volumes exported to the host(s).

Troubleshooting Peer Motion Data Migration 113

4. On the destination storage system—Remove the peer volumes from the destination storagesystem.

5. On the destination storage system—When there are no volumes exported from thedestination array to the host, remove the host from the destination storage system.

6. On the source storage system—Remove the VLUN exports to the host representing thedestination storage system from the source storage system.

7. On the source storage system—Remove the host representing the destination storagesystem from the source storage system.

If a failure occurs after volume import tasks have started, the hosts' access to the volumes on thesource system is interrupted. A failed import returns the system to the point where the import canbe retried after the cause of failure is resolved. It is also possible to revert the configuration backso that the I/O access is via the source system, but this is a manual process and requires downtime. To revert the configuration so that the source system is servicing I/O:1. On the host—To prevent consistency issues, any active applications should be cleanly shutdown

before shutting down the hosts. Cleanly stop access to the destination storage system from thehost. The host will lose access to the volumes being migrated, as part of the procedure.

2. On the destination storage system—Cancel any active import tasks for the volumes that werebeing migrated.

3. On the destination storage system—Remove the VLUNs on the destination storage system forthe volumes exported to the host.

4. On the destination storage system—Remove the peer volumes from the destination storagesystem.

5. On the destination storage system—Only if no other volumes are exported from the destinationarray to the host, remove the host from the destination storage system.

6. On the source system—Remove the VLUN exports to the destination storage system from thesource system.

7. On the source system—Remove the host representing the destination storage system from thesource system.

8. On the source system—Execute the setvv –clrrsv CLI command to all volumes that werebeing migrated or on the source system, if the source system is running HP 3PAR OS 3.1.3or above, execute the setvv –clralua CLI command to all volumes that were beingmigrated.

9. On the fabric and host—Rezone the host back to the source system, if needed.10. On the host—Restart the host and any applications that were shutdown at the beginning of

this process.

Troubleshooting HP 3PAR Peer Motion UtilityThe following are issues you may encounter when using the HP 3PAR Peer Motion Utility:

Unable to connect HP 3PAR Peer Motion Utility toolSymptom: When you open HP 3PAR Peer Motion Utility and enter the management IP, username,and password, the following error message(s) may appear:Error: Invalid credentials, Please try with valid credentials.Error: Error connecting to server using IP address x.x.x.x.Error: Cannot communicate with serverError: Authorization error. This user is not part of supported user groupsResolution: Verify the following:• The management IP, user name, and password are correct.• The username is a member of the "HP Storage Admins" or "HP Storage Users" group.

114 Troubleshooting

• The HP 3PAR Peer Motion service is running on the server to which HP 3PAR Peer MotionUtility is communicating.

• If HP 3PAR Peer Motion Utility is running on another server, ping the server on which HP 3PARPeer Motion service is installed.

Zoning problemSymptom: You open HP 3PAR Peer Motion Utility and enter the createmigration command,and results in the following error:Error: There is no one-to-one mapping between peer ports and source host ports.Resolution:Ensure that there is one host port zoned to one peer port and another host port zoned to anotherpeer port or network connectivity from server to source is proper or 3PAR source/destinationstorage system is in communication."

Source or destination storage system is unreachableSymptom: While adding an HP 3PAR StorServ Storage system as a source or destination storagesystem, it took too long to load the 3PAR details.Error: Unable to connect to source or destination HP 3PAR StorServ Storage, ensure that IP addressetc. is proper.Resolution: Use the following steps to isolate and solve the problem:1. Ping the HP 3PAR StoreServ Storage system IP address from the server where HP 3PAR Peer

Motion Utility is running.2. Make sure the port number specified when adding the source/destination storage system is

correct. If you are still unable to add destination storage system, continue to step 3.3. Restart the HP 3PAR Peer Motion Utility.

Contact HP Customer Support for assistance before attempting to restart the HP 3PAR PeerMotion Utility.

Losing communication with 3PAR storage systemSymptom In rare instances, HP 3PAR Peer Motion Utility loses communication with HP 3PAR storagesystem and results in the following error:Error OIUERRDST0001 Unable to connect to HP 3PAR storage system OIURSLDST0001 Pleaseensure that IP address etc. is properResolution Restart HP 3PAR Peer Motion Utility.

Resolving general errors:Symptom: Source or destination storage system is unreachable or failed to load data on time.• Failed to start data transfer• Preparation stage failed because data from the source or destination storage system could

not be fully loaded• Host set creation failed because data from destination storage system could not be fully loadedError:• The source or destination storage system is busy and did not provide the required data within

the expected time.• Network latency between server component and the source or destination storage system.Resolution:1. Verify that the source or destination storage system is not overloaded.2. Identify and correct any network latency issues.

Troubleshooting HP 3PAR Peer Motion Utility 115

3. Retry the operation.4. If the problem persists, restart the HP 3PAR Peer Motion Utility.

Migration preparation failed (createmigration)Symptom: Create migration failed.Error: The preparation process failed to admit volumes on the destination storage system.Resolution: Verify the following:1. The destination storage system is accessible.2. The destination CPGs has enough capacity. If they do not, free up enough capacity in the

CPGs or add more capacity to the CPGs on the destination storage system.3. No duplicate volumes exist. This may occur if either a virtual volume with same name or with

the same WWN exists on the destination storage system.4. The required LUN number is available on the host object on the destination storage system.

Log locationsLog content can be useful in identifying and solving problems that may occur during data migration.Log in as administrator in order to run the HP 3PAR Peer Motion Utility. HP 3PAR Peer MotionUtility log in fails with the message: oiu.keystore (Access is denied), when logging inwith User privileges

HP 3PAR Peer Motion Utility log file and data fileWhen more details are needed, HP 3PAR Peer Motion Utility can have logging levels increasedfor more detailed entries by editing the file, C:\Program Files (x86)\ Hewlett-Packard\hp3parpmu\ OIUTools\ tomcat\ 32-bit\ apache-tomcat-7.0.37\ webapps\oiuweb\ WEB-INF\ classes\ applicationconfig.properties and then restarting theHP 3PAR Peer Motion Utility service, so that the logging changes are picked up.HP 3PAR Peer Motion Utility logs are located in the following location:<Installdrive/folder>\Hewlett-Packard\hp3parpmu\OIUTools\tomcat\32-bit\apache-tomcat-7.0.27\logs

HP 3PAR Peer Motion Utility configuration and migration data is located in the following location:<Install drive/folder>\Hewlett-Packard\hp3parpmu\OIUData\data

ERROR MESSAGESThe following table shows error messages and the resolutions for resolving the errors:

Resolution MessagesResolution Codes

An unexpected error occurred.OIUERRAPP0000

Contact HP support. You may try restarting the application service.OIURSLAPP0000

Component is unimplemented.OIUERRAPP0002

If component is already implemented, ensure component class mapping is there incomponentConfig.properties.

OIURSLAPP0002

Component load failure.OIUERRAPP0003

Method might be unimplemented or access of aspects of component class might bedisallowed.

OIURSLAPP0003

User is not authorized to login.OIUERRAPP0004

Check if the credentials are correct and if the user is a member of the 'HP StorageMigration Admins' or 'HP Storage Migration Users' group.

OIURSLAPP0004

Either the configuration file is unavailable or the required entry is missing.OIUERRAPP0005

116 Troubleshooting

Please check the installation and make sure configuration file is available.OIURSLAPP0005

Unable to identify the specified array type.OIUERRAPP0006

Please ensure that the plugin corresponding to the specified array is installed.OIURSLAPP0006

Failed to discover source arrays.OIUERRAPP0007

Contact HP Support.OIURSLAPP0007

Failed to execute job.OIUERRAPP0008


Job might have executed successfully but couldn't receive any handle to track it.OIUERRAPP0009


SMI-S EMC Provider WBEM Operations error.OIUERRAPP0010

Please check SMI-S ECOM connectivity and access, see Log file for details, and/orContact HP Support.

OIURSLAPP0010

EMC Provider WBEM Connection, Malformed URL.OIUERRAPP0011

Application internal error, see Log file for details. Contact HP Support.OIURSLAPP0011

EMC Provider WBEM Connection, Client initialization error.OIUERRAPP0012

Unsupported EMC Provider version for SMI-S.OIUERRAPP0013

Check support matrix and upgrade EMC Provider.OIURSLAPP0013

Either the Rules XML file(s) is/are unavailable or the required entries are missing.OIUERRAPP0014

Please check the installation and make sure Rules XML file(s) is/are available.OIURSLAPP0014

SMI-S EMC Provider Connection error.OIUERRAPP0015

Please check SMI-S ECOM connectivity (IP Address, Port number), see Log file fordetails, and/or Contact HP Support.

OIURSLAPP0015

SMI-S EMC Provider Authorization error.OIUERRAPP0016

Please check SMI-S ECOM Access Configuration and/or User Credentials, see Logfile for details, and/or Contact HP Support.

OIURSLAPP0016

SMI-S Provider WBEM Operations error.OIUERRAPP0020

Please check SMI-S connectivity and access, see Log file for details, and/or ContactHP Support.

OIURSLAPP0020

Storage Provider WBEM Connection, Malformed URL.OIUERRAPP0021


Storage Provider WBEM Connection, Client initialization error.OIUERRAPP0022


Unsupported Storage Provider version for SMI-S.OIUERRAPP0023

Check support matrix and upgrade Storage Provider.OIURSLAPP0023

Either the Rules XML file(s) is/are unavailable or the required entries are missing.OIUERRAPP0024

Please check the installation and make sure Rules XML file(s) is/are available.OIURSLAPP0024

SMI-S Storage Provider Connection error.OIUERRAPP0025

Please check SMI-S connectivity (IP Address, Port number), see Log file for details,and/or Contact HP Support.

OIURSLAPP0025

SMI-S Storage Provider Authorization error.OIUERRAPP0026


Please check SMI-S Access Configuration and/or User Credentials, see Log file fordetails, and/or Contact HP Support.

OIURSLAPP0026

Database is not running.OIUERRDB1000

Stop and start database service.OIURSLDB1000

Failed to access the database due to locking error.OIUERRDB1001

Please retry the operation after some time.OIURSLDB1001

Failed to read the database.OIUERRDB1002

Please retry the operation after some time.OIURSLDB1002

Internal Database error. Invalid object type specified for Database operation.OIUERRDB1003

Ensure that the correct object type is specified.OIURSLDB1003

Internal Database error. Invalid tag type encountered while reading XML.OIUERRDB1004

Contact HP Support.OIURSLDB1004

Database write failed.OIUERRDB1005

Please retry the operation after some time. If the problem persists contact HP support.OIURSLDB1005

Database constraint violated.OIUERRDB1006

Ensure that the object is not already added and that the dependent objects areavailable.

OIURSLDB1006

No entry matching the search criteria is found.OIUERRDB1007

Ensure that the object is already added.OIURSLDB1007

File unlocking failed.OIUERRDB1008

Failed to unlock a file. Please restart the application service.OIURSLDB1008

Database is inconsistent.OIUERRDB1009

Contact HP support.OIURSLDB1009

Invalid data passed to database.OIUERRDB1010

Please ensure that valid data is entered.OIURSLDB1010

More than one record found in DataBase for given combination of migrationid,destvolID, srcvolID, srcArrID, destArrID.

OIUERRDB1011

Please ensure that valid data is entered.OIURSLDB1011

Unknown source type.OIUERRCS1000

Install appropriate source array plugin or choose right source array type.OIURSLCS1000

Unable to find the array details.OIUERRCS1001

Ensure that proper array ID is provided.OIURSLCS1001

There is no one-to-one mapping between the peer ports and the source host ports.OIUERRCS1002

Ensure that there is a one-to-one mapping between the peer ports and the source hostports, and that network connectivity between the host, source array and destinationarray is proper.

OIURSLCS1002

There is no one-to-one mapping between the peer ports/NPIV port and the sourcehost ports.

OIUERRCS1003

Ensure that there is a one-to-one mapping between the peer ports, NPIV port and thesource host ports, and that network connectivity between the host, source array anddestination array is proper.

OIURSLCS1003

118 Troubleshooting

NPIV port visible in destination array, Unable to show connection.OIUERRCS1004

Please verify one-to-one mapping using IMC GUI.OIURSLCS1004

Invalid port type.OIUERRCC1000

Use appropriate port number.OIURSLCC1000

Invalid security mode.OIUERRCC1001

Use true/false. No value will take default.OIURSLCC1001

Invalid strict param.OIUERRCC1002

Use true/false. No value will take default.OIURSLCC1002

Source array UID not provided.OIUERRMC1000

Ensure that source array UID is provided as input.OIURSLMC1000

Command cannot be processed.OIUERRMC1001

Either the srchost or srcvolmap or volmapfile should be provided.OIURSLMC1001

Source volume details are supplied with wrong syntax.OIUERRMC1003

Ensure that entries are provided in accordance with the user guide.OIURSLMC1003

Invalid migration type.OIUERRMC1004

Provide migtype as online or MDM or offline.OIURSLMC1004

Invalid clunode parameter.OIUERRMC1005

Provide a number greater than 1.OIURSLMC1005

Clunodes not provided though migration type is AO.OIUERRMC1006

With AO migration type clunodes parameter should be more than or equal to 1. Seesupport matrix for max value.

OIURSLMC1006

Number of entries in volume map is invalid.OIUERRMC1007

Number of volume map entries should be between 1 and 3.OIURSLMC1007

The destcpg and/or destprov are not provided.OIUERRMC1008

Default values required at least for one entry of volume map.OIURSLMC1008

Value for destcpg or destprov is not provided.OIUERRMC1009

Either provide the values through volume map or provide default values via destprovor destcpg options.

OIURSLMC1009

Empty volume identifier specified.OIUERRMC10010

Provide a valid identifier for source volume.OIURSLMC10010

destprov is not specified.OIUERRMC10011

Specify destprov as 'thin' or 'full'.OIURSLMC10011

Invalid value provided for destprov.OIUERRMC10012

destprov should be 'thin' or 'full'.OIURSLMC10012

destcpg is not specified.OIUERRMC10013

destcpg should be provided as cpg information is missing for atleast one entry involume map.

OIURSLMC10013

Invalid migration type specified.OIUERRMC10014


If atleast one of the volume being migrated is provisioned to a host then migrationtype can be either be MDM or online.

OIURSLMC10014

destprov/destcpg is not specified with source host.OIUERRMC10015

If source host is mentioned, both destprov and destcpg should be specified.OIURSLMC10015

One or more of the volumes, selected explicitly or implicitly, are ineligible for migrationdue to a remote copy relation.

OIUERRMC10016

Remove the remote copy relation for the volume(s) selected for migration.OIURSLMC10016

One or more of the volumes, selected explicitly or implicitly, are ineligible for migrationdue to an iSCSI provisioning.

OIUERRMC10017

Remove the iSCSI presentations for the volume(s) selected for migration.OIURSLMC10017

One or more of the volumes, selected explicitly or implicitly, are reserved, thereforeineligible for migration.

OIUERRMC10018

Remove the volume(s) selected for migration from reserved group(s).OIURSLMC10018

Duplicate migrations are not allowed, for Source Array of type.OIUERRMC10019

Create another migration, when this Array had finished migration and has beenremoved from migration list.

OIURSLMC10019

One or more volumes are selected implicitly. -destprov and -destcpg options need tobe specified.

OIUERRMC10020

Please specify both -destprov and -destcpg values.OIURSLMC10020

No volumes found.OIUERRMC10021

Please make sure that at least one volume is selected either explicitly or implicitly.OIURSLMC10021

Create Migration failed while parsing cg volmap input.OIUERRMC10022

Please pass proper input as specified in command help.OIURSLMC10022

Invalid input for autoresolve option.OIUERRMC10023

Use either true or false.OIURSLMC10023

Destination array not found.OIUERRMS10001

Ensure that destination array specified is already added and that the correct arrayID is specified.

OIURSLMS10001

Source array not found.OIUERRMS10002

Ensure that the source array specified is already added to OIU and that valid UID isused.

OIURSLMS10002

Source host not found.OIUERRMS10003

Ensure that the unique name specified for the source host is valid.OIURSLMS10003

Could not fetch source volume details.OIUERRMS10004

Ensure that the volume you are trying to migrate is present in the source array. Waitfor some time and retry.

OIURSLMS10004

One or more of the volume(s) selected for migration explicitly or implicitly is alreadyunder migration process.

OIUERRMS10005

Ensure that the volume specified and the corresponding linked volumes are not undermigration.

OIURSLMS10005

Failed to start Data transfer.OIUERRMS10006

Ensure that all prerequisites are met.OIURSLMS10006

120 Troubleshooting

Number of source volumes selected for offline migration is more than the maximumlimit.

OIUERRMS10007

Verify support matrix and restrict the number of volumes accordingly.OIURSLMS10007

Migration details not found.OIUERRMS10008

Ensure that proper migration ID is specified.OIURSLMS10008

Required domain not present at destination storage system.OIUERRMS10009

Please create domain before triggering migration.OIURSLMS10009

Volumes belong to different domain.OIUERRMS10010

All volumes should be in same domain for domain based migrations.OIURSLMS10010

Invalid host Set Name or host set is empty.OIUERRMS10011

Provide valid host set name or add hosts to host set and try migration.OIURSLMS10011

Invalid volume Set Name or volume set is empty.OIUERRMS10012

Provide valid volume set name or add volumes to volume set and try migration.OIURSLMS10012

Unable to connect to the 3PAR storage systemOIUERRDST0001

Please ensure that the IP address and login credentials are correct.OIURSLDST0001

If necessary remove the array and add it again.OIURSLDST0002

3PAR storage system is already added.OIUERRDST0002

The 3PAR array is not in an usable state.OIUERRDST0003

Contact HP support.OIURSLDST0003

Unsupported 3PAR storage system version.OIUERRDST0004

Check support matrix and upgrade 3PAR.OIURSLDST0004

3PAR storage system does not have peer motion license.OIUERRDST0005

Apply peer motion license on 3PAR.OIURSLDST0005

3PAR storage system is not connected.OIUERRDST0006

Ensure that the storage system is already added and that the proper ID is specified.OIURSLDST0006

This 3PAR storage system does not support minimally disruptive migration.OIUERRDST0007

Use other type of migration or upgrade to a firmware that supports minimally disruptivemigration.

OIURSLDST0007

Admit has failed.OIUERRDST0008

Fix the issue according to the error observed and retry.OIURSLDST0008

Volumes partially admitted.OIUERRDST0009

Contact HP support.OIURSLDST0009

Unable to validate certificate for HP 3PAR Storage System.OIUERRDST0010

Please use the installcertificate command to accept the certificate.OIURSLDST0010

This storage system cannot be removed. It is involved in an active migration.OIUERRDST0011

Migrations have to be in complete/abort state for the storage system to be removed.OIURSLDST0011

The destination storage system doesn't support dedupe feature.OIUERRDST0012

Please use dedupe supported array.OIURSLDST0012

Selected CPG/provision does not support dedupe.OIUERRDST0013


Please select supported CPG/provision for dedupe and try again.OIURSLDST0013

No such destination storage system found.OIUERRDST0014

Please verify whether destination is present.OIURSLDST0014

Destination array firmware version is older than 3.2.1, so it wont support consistencygroup.

OIUERRDST0015

Please upgrade firmware version and try again.OIURSLDST0015

Volume set creation failed at destination storage system.OIUERRDST0020

Please try migration again.OIURSLDST0020

Volume set removal failed at destination storage system.OIUERRDST0021

Please remove consistency group using IMC GUI or CLI.OIURSLDST0021

Host with same name and a different WWN already exists at destination.OIUERRDST0025

Cannot proceed until tried again with a different host name.OIURSLDST0025

Unable to connect to the XP array.OIUERRSRC0001

Contact HP Support.OIURSLSRC0001

Unable to connect to the SVP of the XP array.OIUERRSRC0002

Make sure that the SVP is up and running.OIURSLSRC0002

Unable to find the array specified.OIUERRSRC0003

Make sure the array is already added in CV AE. Otherwise contact support.OIURSLSRC0003

The array you are trying to add is not supported.OIUERRSRC0004

Check the support matrix and make sure that only the supported arrays with supportedfirmware versions are added.

OIURSLSRC0004

An unexpected error occurred when communicating with the XP array.OIUERRSRC0005

Contact HP support. You may check if the XP array used is operational.OIURSLSRC0005

Unable to find the array specified serial number.OIUERRSRC0212

Please ensure that UID is specified with addsource command.OIURSLSRC0212

This storage system cannot be removed. It is involved in an active migration.OIUERRSRC0012

Migrations have to be in complete/abort state for the storage system to be removed.OIURSLSRC0012

The object is not available in the array.OIUERRSRC0013

Retry the operation after some time.OIURSLSRC0013

A migration is already going on between the selected source and destination array.OIUERRSRC0014

Please wait till the ongoing migration is complete or delete the migration and thenretry the operation.

OIURSLSRC0014

Peer port is already assigned to another host object.OIUERRSRC0015

Please delete the host(s) that has the peer ports assigned to it to proceed.OIURSLSRC0015

One or more hosts associated with the migration does not support single VV migration.OIUERRSRC0016

Please ensure that the hosts associated with migration have persona 2, 11, 13 or15.

OIURSLSRC0016

Single VV migration is not supported for the selected source array.OIUERRSRC0017

Please ensure that single VV option is only used when the source array is of type3par.

OIURSLSRC0017

122 Troubleshooting

The source/destination HP 3PAR StoreServ firmware version does not support singleVV migration.

OIUERRSRC0018

Please ensure that both the source and destination arrays are running the firmwareversion necessary for single VV migration.

OIURSLSRC0018

The number of nodes migrated exceeds the maximum limit.OIUERRSRC0019

Ensure that the number of nodes migrated does not exceed 4.OIURSLSRC0019

The source/destination HP 3PAR StoreServ firmware version does not support onlinewindows cluster migration.

OIUERRSRC0120

Please ensure that both the source and destination arrays are running the firmwareversion necessary for online windows cluster migration.

OIURSLSRC0120

The destination HP 3PAR StoreServ model does not support online windows clustermigration.

OIUERRSRC0121

Please ensure that only supported array models are used for online windows clustermigration.

OIURSLSRC0121

The number of NPIV ports is less than the required count.OIUERRSRC0122

Please ensure that each peer port is configured with twice as many NPIV ports as thenumber of nodes being migrated.

OIURSLSRC0122

The source HP 3PAR StoreServ array is running on higher firmware version.OIUERRSRC0123

Please ensure that source HP 3PAR StoreServ array is running on either the samefirmware version or the lower firmware version than destination HP 3PAR StoreServarray.

OIURSLSRC0123

No such source storage system found.OIUERRSRC0124

Please verify whether source is present.OIURSLSRC0124

Unsupported EMC storage system version.OIUERRSRC0020

Check support matrix and upgrade EMC.OIURSLSRC0020

There is a active migration on this source. So this source can not be removed.OIUERRSRC0021

Migration have to be complete/abort for source to be removed.OIURSLSRC0021

Cannot find specified source Array.OIUERRSRC0022

An Array has to be added first in order to be removed.OIURSLSRC0022

You have selected a migration with an unsupported storage group configuration.OIUERRSRC0023

Verify that your storage group configuration matched one of the supportedconfigurations.

OIURSLSRC0023

Authorization failed.OIUERRSEC0000

This user is not part of the supported user groups.OIURSLSEC0000

Invalid credentials.OIUERRSEC0001

Please try again with correct username and password.OIURSLSEC0001

The target port chosen for migration has already reached the maximum permissiblehost group objects.

OIUERRSRC0006

Delete the host group objects that are not required or connect the peer port to anothertarget port.

OIURSLSRC0006

There is no free LUN available in the selected host group object.OIUERRSRC0007

Contact HP Support.OIURSLSRC0007

Command execution on XP array timed out.OIUERRSRC0008


Make sure the array is not busy in performing other management operations. Ifrequired increase the timeout value in config file.

OIURSLSRC0008

Unable to find the LUN to be unpresented.OIUERRSRC0009

Contact HP Support if the problem persists.OIURSLSRC0009

Unable to find the peer host port for host creation.OIUERRSRC0010


An internal error occurred when processing the command.OIUERRSRC0011


Unable to present the volume to the host in 3PAR arrayOIUERRSRC0101


Unable to unpresent the volume from the host in 3PAR array.OIUERRSRC0102


Unable to present the volume to the host in EMC array.OIUERRSRC0111


Unable to unpresent the volume from the host in EMC array.OIUERRSRC0112


Unable to validate CA signed certificate.OIUERRCER0000

Please follow steps mentioned in migration guide to install the certificate.OIURSLCER0000

Not able to establish connection with storage array.OIUERRCER0002

Please verify input parameters.OIURSLCER0002

Not able to fetch and publish the certificate details.OIUERRCER0003

Please verify input parameters and the connection with array.OIURSLCER0003

Currently this command not supported for this array type.OIUERRCER0004

Please verify input parameters and the array type.OIURSLCER0004

No matching persona found for the provided persona value.OIUERRPER0000

Please select another supported persona.OIURSLPER0000

Persona cannot be empty for online or MDM migration for non 3par source array.OIUERRPER0001

Please select supported persona. Use showpersona command for list of supportedpersona.

OIURSLPER0001

Preparation stage failed as virtual volume set by given name already exists.OIUERRCG00000

Please use different consistency group name.OIURSLCG00000

Preparation stage failed as virtual volume set name and consistency group name aresame.

OIUERRCG00001

Please use -allVolumesInCG option to migrate entire vvset consistently.OIURSLCG00001

Preparation stage failed as one of virtual volume in cgvolmap is not part of volumesto be migrated.

OIUERRCG00002

Please make sure all volumes specified in cgvolmap are part of volumes to be migrated.OIURSLCG00002

Preparation stage failed as there are less than 2 volumes in consistency group.OIUERRCG00003

Please add at least 2 volumes in consistency group and try again.OIURSLCG00003

124 Troubleshooting

Preparation stage failed as volume is part of more than one consistency group.OIUERRCG00004

Please make sure volume is part of one consistency group only.OIURSLCG00004

Import failed as virtual volume set by given name doesn't exist at the destinationsystem.

OIUERRCG00005

Please try migration again.OIURSLCG00005

Import failed as Less than two volumes found for virtual volume set at the destination.OIUERRCG00006

Please add 2 or more volumes to virtual volume set and try migration again.OIURSLCG00006

Import failed as virtual volume set doesn't have a default CPG name.OIUERRCG00007

Please provide default CPG to volumes of virtual volume set and try migration again.OIURSLCG00007

Import failed as virtual volume set doesn't have volumes in it.OIUERRCG00008

Please add volumes to virtual volume set and try migration again.OIURSLCG00008

Remove Migration failed to remove volume or vvset.OIUERRCG00009

Please fire remove migration command again.OIURSLCG00009

Data transfer failed as volume set doesn't have default CPG value.OIUERRCG00012

Please provide default CPG value for volume set and try again.OIURSLCG00012

Preparation stage failed as virtual volume set by given name already exists.OIUERRVVS0000

Please use different virtual volume set name.OIURSLVVS0000

Preparation stage failed as virtual volume set by given name doesn't exist.OIUERRVVS0001

Please make sure that volume set to be migrated is present in array.OIURSLVVS0001

Preparation stage failed as no volumes found in volume set.OIUERRVVS0002

Please add volumes to volume set and try migration.OIURSLVVS0002

Migration failed.OIUERRVVS0003

Please provide either vvset or volume as input.OIURSLVVS0003

Migration cannot proceed.OIUERRVVS0005

All the Volumes of the vvset are found in another VVset which has presentation.OIURSLVVS0005

Migration cannot proceed.OIUERRVVS0006

One or more VV is part of another VVset.OIURSLVVS0006


Index

Aadddestination, 99Addsource, 97

Cconstraints

pre-migration, 15conventions

text symbols, 87Copy Storage Settings and Configurations wizard, 25createmigration, 103

DData Migration Troubleshooting, 113documentation

providing feedback on, 88

Hhelp, 97HP 3PAR Peer Motion Manager, 17HP 3PAR Peer Motion Utility, 61HP 3PAR Peer Motion Utility troubleshooting, 114HP-UX standalone hosts

migrating, 93

IImport Volumes wizard, 31installcertificate, 109Installing the HP 3PAR Peer Motion Utility on Linux, 69Installing the HP 3PAR Peer Motion Utility on Windows,

62

LLUN paths

scanning for, 93

MMigrate Data wizard, 26migration types, 6

OOnline Windows Cluster migration, 12

Ppeer motion, 6

configuration, 18peer motion configuration

removing, 35viewing, 37

peer volumescreating, 28removing, 32

port informationviewing, 40

Post Migration Cleanup, 33

Post-MIgration Tasks, 85

Rremovedestination, 109removemigration, 108removesource, 108requirements

ALUA, 14general, 11volume, 14

SServiceguard clustered hosts

migrating, 93showconnection, 101showdestination, 101showmigration, 105showmigrationdetails, 107showsource, 98single volume migration, 13startmigration, 107symbols in text, 87

Ttext symbols, 87

Vvolumes

importing, 29, 31

126 Index

Documents

HP 3PAR Peer Motion Data Migration Guideh20628. · "ERROR: OIUERRDST0010 Unable to validate certificate for HP 3PAR Storage >