HP 3PAR Peer Motion Manager 1.1.0 Software User's Guide Abstract This guide provides information for using the Peer Motion Manager Software to migrate data from one storage system to another storage system.
© Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S.
Contents 1 Introduction...............................................................................................4 Overview................................................................................................................................4 Audience.................................................................................................................................4 Related Documentation..............................................................................................
1 Introduction Overview This guide provides information for installing and using the Peer Motion Manager Software. Audience This guide is for use by administrators who are responsible for maintaining the HP 3PAR operating environment. An understanding of the functions of HP 3PAR hardware platforms and the InForm OS is required.
Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. WARNING! Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system. CAUTION: NOTE: guide. Cautions alert you to actions that can cause damage to equipment, software, or data.
2 Overview HP 3PAR Peer Motion Manager Software Overview The HP 3PAR Peer Motion Manager Software script controls the migration of data from a source system to a destination system. With the Peer Motion Manager software you can copy the virtual volumes and system configuration information to a new system without changing host configurations or interrupting access to the volumes. The Peer Motion Manager software runs on a Windows host connected to the destination system.
3 Installation and Deinstallation Installation Overview This chapter describes how to install the HP 3PAR Peer Motion Manager Software script on a Windows host computer. Instructions for removing the HP 3PAR Peer Motion Manager Software script are also provided. Installation Requirements The following requirements must be satisfied to install the Peer Motion Manager Software on a Windows host computer: • Access to the HP Software Depot at www.software.hp.com. • A Windows host computer.
4. Verify the InForm CLI is in the Windows PATH variable. Open a Windows DOS cmd window, type path, and verify the following entry is included: PATH=... C:\Program Files\3PAR\inform_cli_\bin... If the InForm CLI entry is missing, please verify the InForm CLI is correctly installed. 5. Set the TPDSYSNAME Windows environment variable to the system name or IPv4 address of the destination system.
4 Using the Peer Motion Manager Software Data Migration Process Overview The 1. 2. 3. 4. Peer Motion Manager Software script executes the data migration process in several phases. Copying the system configuration data from the source system array to the destination system. Analyzing the links used for data migration. Migrating the volumes. Displaying the system information for verification.
2. 3. 4. 5. Verify the host can see the new paths and VLUNs from the destination system. Select the import parameters. You can change the import parameters for each volume by enabling the user interface option to make setting changes. Verify that the import can proceed. If the import proceeds while both source and destination systems are serving data, data corruption may occur. The status of the selected host ports on the source system is checked.
• Note the World Wide Names (WWNs) of hosts connected to the source and destination systems. • Note the InForm CLI Super user name and password for the source and destination systems. • Note the Names of volumes to be migrated from the source to the destination system. • Enabling the Peer Motion on the destination system requires a Peer Motion license. • For offline data migration, there can be no active LUNs on the host attached to the source system.
The system name of the source system. If the system name is not specified, you are prompted to enter the information before you can use the Main Menu. -srcip The IPv4 address of the source system. If the system name is not specified, you are prompted to enter the information before you can use the Main Menu. -srcpwfile The password file of the source system. If a password file is not specified, the script generates the password file.
password: 5. If prompted, enter the system name or IP address, the user name, and user password for the source system. For example: system: user: password: 6. 7. 8. If prompted, enter the name for the password file the script creates for the source system. The file is created in the folder containing the Peer Motion Manager Software script.
Migrating the Volumes to the Destination System WARNING! data. 1. 2. Data corruption may occur if both the source and destination systems are serving From the Main Menu, select option 3 ==> Migrate Volumes. From the Migrate Volumes Menu, select option 1 ==> Online Migrate Volumes or option 2 ==> Offline Migrate Volumes. For more Information see “Online and Offline Data Migration” (page 9). NOTE: If one create volume or import volume operation fails, all create and import volume operations will fail.
For more information, see the HP 3PAR Remote Copy Software User's Guide and the HP 3PAR InForm OS CLI Administrator’s Manual.
5 Troubleshooting the Peer Motion Manager Software Source System Host Configuration Issues Many source system host configuration issues can be identified with the user interface. From the Main Menu, select option 2 ==> Analyze Migration Links. Then select option 2 ==> Analyze Source Array Host Ports and Host Configuration from the Analyze Migration Links Menu. Problem No WWN. The host that represents the destination system has no WWN assigned.
Source System Host Link Configuration Issues Problem Not Configured. One of the peer ports on the destination system is not configured, or has an invalid configuration status. Solution 1 On a source system running InForm OS 2.2.4 or earlier, one or more ports on the source systems is using the wrong persona. Use the showport CLI command to check the persona. Use the sethost CLI command to specify the correct persona setting for the host. Solution 2 Verify the link status is OK.
Verify the source system has 2 separate nodes cabled to the switch fabric, and that each of the nodes is zoned to a separate node on the destination system. Destination System Peer Link Configuration Issues Problem Degraded. Occurs when any of the peer ports is not in a ready state. Solution Use showport to find the detailed status of the port and correct any issues. Problem Invalid Configuration. Occurs when the total number of peer ports is not two.
Cause 3 When any of the peer ports has the wrong source system device connected. Solution 3 Rezone the switch fabric so that the destination system peer ports are zoned to the correct source system device. Migration Phase Issues • Verify the destination system has no active paths with the showhost CLI command. • Monitor the migration task with the showtask CLI command. Determine where the operation failed.
InForm OS CLI Issues 20 • The user accounts on both systems must have Super user roles. • If unable to connect to the source or destination system, check the InForm OS event log for errors. If there are no errors in the event log, verify the connections to both systems are working. Verify the connections to the source and destination systems by logging on to the system and attempting to issue CLI commands. If you can issue CLI commands the connection is good.
