HP 3PAR Online Import for HDS Storage Data Migration Guide

Transcription

1 HP 3PAR Online Import for HDS Storage Data Migration Guide Abstract This guide provides information on using HP 3PAR Online Import for HDS Storage software to migrate data from an HDS Storage system to an HP 3PAR StoreServ Storage system. HP Part Number: QL Published: May 2015 Edition: 1

2 Copyright 2014, 2015 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. 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. Links to third-party websites take you outside the HP website. HP has no control over and is not responsible for information outside HP.com. Acknowledgements Microsoft, Windows, Windows 7, and Windows Server are trademarks of the Microsoft Group of companies. Oracle RAC is a registered trademark of Oracle and/or its affiliates.

3 Contents 1 Overview of HP 3PAR Online Import for HDS Storage...6 Types of Data Migration...6 Understanding Which Data is Migrated...6 HDS Storage to HP 3PAR StoreServ Storage Migration Process Migration Process Checklists...8 Online Migration...8 Prerequisite Component Installation...8 Premigration...8 Migration...8 Post-Migration...9 Minimally Disruptive Migration...9 Prerequisite Component Installation...9 Premigration...10 Migration...11 Post-Migration...12 Offline Migration...12 Prerequisite Component Installation...12 Premigration...12 Migration...13 Post-Migration Installation and Setup for Data Migration...14 Configuration Rules for HP 3PAR Online Import Support...14 Installing the HCS/SMI-S...14 HCS CLI SMI-S License...14 HCS Device Manager License...18 Installing the HP 3PAR Online Import Utility...20 Migrations Supported by HP 3PAR Online Import Utility...26 Migrations Supported for HDS USP_VM, HDS USP_V, HDS USP, and HDS NSC Preparing for Data Migration...31 Data Migration Considerations...31 General Considerations...31 System Requirements...32 Planning for Migration...32 Network and Fabric Zoning Requirements...32 Reconfiguring the Host Multipath Solution...33 Working with Consistency Groups Premigration Steps...36 Zoning the Source HDS Storage to the Destination HP 3PAR StoreServ Storage System...36 Identifying the Source and Destination Storage Systems...37 Prerequisites...37 Required Information...37 Adding the Source Storage System...38 Adding the Destination Storage System...38 Preparing the Host for Data Migration...39 Creating the Data Migration Task...41 Required Information...41 Issuing the createmigration Command...42 Contents 3

4 6 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v Online Data Migration with Removal of Hitachi Dynamic Link Manager...44 Online Migration with Linux Native Device-Mapper Performing Minimally Disruptive Migration Using a Windows Host...56 Creating the Data Migration Task...56 Updating Host Multipath Software and Unzoning from the Source HDS Storage System...56 Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System...59 Bringing the Windows Host Back Online Performing Minimally Disruptive Migration Using a Linux Host...62 Creating the Data Migration Task...62 Updating Host Multipath Software and Unzoning from Source HDS Storage System...62 Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System...64 Bringing the Linux Host Back Online Performing Minimally Disruptive Migration Using an AIX Host...67 Creating the Data Migration Task...67 Updating Host Multipath Software and Unzoning from Source HDS Storage System...67 Starting the Data Migration from the Source HDS Storage System to the Destination HP 3PAR StoreServ Storage System...69 Bringing the AIX Host Back Online Performing Minimally Disruptive Migration Using an HP-UX Host...73 Creating the Data Migration Task...73 Updating Host Multipath Software and Unzoning from Source HDS Storage System...73 Starting the Data Migration from the Source HDS Storage System to the Destination HP 3PAR StoreServ Storage System...74 Bringing the HP-UX Host Back Online Performing Offline Data Migration...77 Creating the Data Migration Task...77 Zoning the Host to the Destination HP 3PAR StoreServ Storage System...77 Shutting Down the Host...77 Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System...78 Performing Post-Migration Tasks Specifically for Offline Migration Performing Common Migration and Post-migration Tasks...80 Viewing Migration Status...80 Viewing all Migrations...80 Viewing Migrations for a Selected Source Storage System...80 Viewing a Selected Migration...80 Viewing Selected Migration Progress by LDEV...80 Aborting a Migration...80 Performing Subsequent Migrations Troubleshooting...81 HP 3PAR Online Import Utility Error Messages...81 Troubleshooting Resources...81 Understanding the HP 3PAR Online Import Utility Data Migration Process...81 HP 3PAR Online Import Utility Server Logs and Output...82 Increase the HP 3PAR Online Import Utility Server Logging Level...83 Troubleshooting Issues...83 Cannot Add a Source HDS Storage system Contents

5 Cannot Create a Migration...84 Cannot Log into the HP 3PAR Online Import Utility...85 The HP 3PAR Online Import Utility Does Not Open in Windows Trailing Spaces in IP Address Return Login Error...85 Powering on or Migrating a VMware ESX Virtual Machine Fails after a Successful Migration...85 VMware Datastore Errors Following a Successful Migration...86 The adddestination Command Returns Error OIUERRDST The addsource Command for HDS Storage Fails...87 The createmigration Command Fails for Migrated LUNs in a Host Group with No Host...87 The createmigration Command Fails for LUN Name or Host Name Containing Special Characters...88 The createmigration Command Returns Error OIUERRAPP0000 or OIURSLAPP The createmigration Command Returns Error OIUERRDB The createmigration Returns Error OIUERRPREP The createmigration Command Returns Error OIUERRCS The createmigration Command with -srcvolmap Returns Error OIUERRAPP The showmigration Command Returns Error OIUERRDST The showtarget Command Does Not Return HDS Storage Details...90 The startmigration Command Fails with Host Name That Exceeds 31 Characters...90 The startmigration Command Returns Error OIUERRMS Appendices...91 Appendix A: HP 3PAR Online Import Utility CLI Commands...91 adddestination...91 addsource...91 createmigration...93 help...95 installcertificate...96 removedestination...97 removemigration...97 removesource...98 showconnection...98 showdestination...99 showmigration...99 showmigrationdetails showpersona showsource startmigration Appendix B: Identifying and Deleting Source Array LUN Paths Appendix C: Rolling Back to the Original Source Array Appendix D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later Appendix E: Use Case: Data Migration for an Oracle RAC Cluster Support and Other Resources Contacting HP HP 3PAR documentation Typographic conventions HP 3PAR branding information Documentation feedback Glossary Index Contents 5

6 1 Overview of HP 3PAR Online Import for HDS Storage HP 3PAR Online Import for HDS Storage manages the migration of data from a source HDS Storage system to a destination HP 3PAR StoreServ Storage system. Using HP 3PAR Online Import for HDS Storage, you can migrate HDS LDEVs s and host configuration information to a destination HP 3PAR StoreServ Storage system without changing host configurations. The terms storage system and array are used interchangeably throughout this guide, and may refer to either the HDS Storage or HP 3PAR StoreServ Storage systems. The source in the migration is the HDS Universal Storage Platform VM (HDS USP_VM), the HDS Universal Storage Platform V (HDS USP_V), the HDS TagmaStore Universal Storage Platform (HDS USP) or the HDS TagmaStore Network Storage Controller (HDS NSC), and the destination is the HP 3PAR StoreServ Storage system. HP 3PAR Online Import for HDS Storage coordinates the movement of data from the source to the destination while servicing I/O requests from the hosts. During the data migration, host I/O is serviced from the host HDS Storage system through the HP 3PAR StoreServ Storage system. The host/ldev presentation implemented on the HDS Storage is maintained on the destination HP 3PAR StoreServ Storage system. For additional information about supported HDS Storage systems, see the HP 3PAR Online Import support matrix on HP SPOCK: HP SPOCK ( Types of Data Migration HP 3PAR Online Import for HDS Storage supports three types of data migration procedures. The appropriate type of data migration depends on the objects being migrated and the migration type. Online Migration type used when migrating a host or a LDEV presented to a host. During online migration, all presentation relationships between hosts and LDEVs being migrated are maintained. Host I/O to the data is not disrupted during an online migration. Minimally disruptive migration (MDM) Migration type used when migrating a host or an LDEV presented to a host. Host I/O is interrupted only during the time it takes to reconfigure the host. Offline Migration type used when migrating one or more unpresented LDEVs. During offline migration, only the selected LDEVs are migrated. No hosts are migrated in this situation. Understanding Which Data is Migrated Data can be migrated by selecting a host or an LDEV on the source HDS Storage system. In addition to the host or LDEV explicitly selected for migration, other objects can be included in the migration using implicit selection. The migration process identifies the relationship between hosts and presented LDEVs and selects all additional objects to completely migrate the hosts. Consequently, the objects that will be migrated are the combination of the explicit and the implicit selection and may lead to the migration of a large amount of LDEVs. Selecting a single host results in migration of the following: The host as well as any LDEVs presented to it Any other hosts to which those LDEVs are presented Any LDEVs presented to those other hosts The maximum number of LDEVs that can be migrated with MDM is 255. For an offline migration, the maximum number of volumes that can be migrated is 25. If you have more offline volumes to migrate, rerun the migration steps for the additional volumes. 6 Overview of HP 3PAR Online Import for HDS Storage

7 IMPORTANT: The implicit selection of objects for migration occurs automatically and cannot be modified. If the number of objects selected for migration exceeds 255 for MDM and 25 for offline migration, the migration will be not be submitted and will return a failed status. The migration process selects objects to migrate using the following rules: Hosts When selecting a single host or group of hosts with LDEV presentations, all the LDEVs presented to the host(s) are migrated. In addition, any presentations the source LDEVs have to other hosts will include those hosts and all of their presented LDEVs in the migration. Presented LDEVs When selecting an LDEV or group of an LDEVs with host presentations, the selected LDEVs and the hosts to which they are presented are migrated. In addition, any presentations the source hosts have with other LDEVs will be included in the migration. Unpresented LDEVs Only the selected unpresented LDEVs are migrated. The offline migration type is the only type available for unpresented LDEV migration. NOTE: For more information about supported and unsupported configurations and about the implicit selection of objects for migration, see Migrations Supported by HP 3PAR Online Import Utility (page 26). HDS Storage to HP 3PAR StoreServ Storage Migration Process The process for migrating HDS Storage LDEVs to an HP 3PAR StoreServ Storage system consists of three parts: Premigration Work done to define the source and destination storage system for a migration definition. This work is not repeated when migrating a second host or additional volumes between the same source and the destination system after the first migration. Migration Creating and executing the migration. The migration work can include the process of unzoning the host from the source storage system, zoning the host to the destination storage system, and removing the migration definition after the migration is complete. This work is repeated for every migration. Post-migration Work done to clean up the configuration after migration is completed. During migration, LDEVs are renamed for use by the HP 3PAR StoreServ Storage. In an LDEV on the HDS Storage system, the colon becomes an underscore; for example, an LDEV name like 04:6A becomes 04_6A. All emulation types for Open-x systems are supported. Mainframe volumes on the HDS Storage system cannot be migrated. HDS Storage to HP 3PAR StoreServ Storage Migration Process 7

8 2 Migration Process Checklists Follow the steps in this chapter to perform online migration, MDM, or offline migration. Online Migration Prerequisite Component Installation Table 1 Prerequisite component installation Online Number Step Check the HP SPOCK website to confirm proper configuration. Install the HCS. Install the HP 3PAR Online Import Utility. See HP SPOCK ( See also Configuration Rules for HP 3PAR Online Import Support (page 14) Installing the HCS/SMI-S (page 14) Installing the HP 3PAR Online Import Utility (page 20) Premigration Table 2 Premigration checklist online Number Step Zone the HDS Storage system and the HP 3PAR StoreServ Storage system as peers. Using the HP 3PAR Online Import Utility, add a source storage system with the addsource command. Using the HP 3PAR Online Import Utility, add a destination storage system with the adddestination command). Validate connections by using the HP 3PAR Online Import Utility showconnection command. See: Zoning the Source HDS Storage to the Destination HP 3PAR StoreServ Storage System (page 36) Adding the Source Storage System (page 38) Adding the Destination Storage System (page 38) Migration If the HDLM is installed, it must be uninstalled, and the native OS multipath software must be used to configure multipathing; see the third column in the Table 3 (page 8) for details about each step. If the HDLM is not installed, see the column on the right for details. Table 3 Migration checklist Online Number Step If the HDLM is installed, see: If the HDLM is not installed, see: 1 Zone the host to the HP 3PAR StoreServ Storage system. Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), step 1 Online Migration with Linux Native Device-Mapper (page 50), step 1 2 Configure device-mapper on the host. 1. Uninstall the HDLM. See: Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), step 2 Online Migration with Linux Native Device-Mapper (page 50), step 2 8 Migration Process Checklists

9 Table 3 Migration checklist Online (continued) Number Step If the HDLM is installed, see: If the HDLM is not installed, see: NOTE: A maintenance window is required. 2. Configure device-mapper on the host. See: Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), step 3 3. Remount application file systems. See: Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), step 4 3 Using the HP 3PAR Online Import Utility, create a migration with the createmigration command. Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), steps 5 7 Online Migration with Linux Native Device-Mapper (page 50), steps Update path configurations. Using the HP 3PAR Online Import Utility, start the migration with the startmigration) command. Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), steps 8 10 Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), step 11 Online Migration with Linux Native Device-Mapper (page 50), steps 6 8 Online Migration with Linux Native Device-Mapper (page 50), step 9 6 Monitor migration with the HP 3PAR Online Import Utility until completion. Viewing Migration Status (page 80) Viewing Migration Status (page 80) Post-Migration Table 4 Post-migration checklist online Number Step Optional: Remove the migration definition when the migration has completed. removedestination (page 97) Optional: When all migrations are complete, remove the source HDS Storage system. Optional: When all migrations are complete, remove the source HDS Storage system and the destination HP 3PAR StoreServ Storage from the HP 3PAR Online Import Utility, using the removesource and removedestination commands. Reconfigure peer ports to host ports. Minimally Disruptive Migration Prerequisite Component Installation Table 5 Prerequisite component installation MDM Number 1 Step Check the HP SPOCK website to confirm proper configuration. See HP SPOCK ( Minimally Disruptive Migration 9

10 Table 5 Prerequisite component installation MDM (continued) Number Step Install the HCS software. Install the HCS core CLI/SMI-S license or the HDS Device Manager license. Install the HP 3PAR Online Import Utility. See See also Configuration Rules for HP 3PAR Online Import Support (page 14) Installing the HCS/SMI-S (page 14) HCS CLI SMI-S License (page 14) or HCS Device Manager License (page 18) Installing the HP 3PAR Online Import Utility (page 20) Premigration Table 6 Premigration checklist MDM Number Step Zone the HDS Storage system and the HP 3PAR StoreServ Storage system as peers. Using the HP 3PAR Online Import Utility, add the source storage system with the addsource command. Using the HP 3PAR Online Import Utility, add the destination storage system with the adddestination command. Validate connections by using the HP 3PAR Online Import Utility showconnection command. Stop all server applications. Offline/unmount LUNs. Stop cluster service, if applicable. Create migration (HP 3PAR Online Import Utility: createmigration command) See Zoning the Source HDS Storage to the Destination HP 3PAR StoreServ Storage System (page 36) Adding the Source Storage System (page 38) Adding the Destination Storage System (page 38) Preparing the Host for Data Migration (page 39) Creating the Data Migration Task (page 41) 10 Migration Process Checklists

11 Migration Table 7 Migration checklist MDM Number Step See 1 Update host native multipath software, finish For Windows: zoning, and shut down the host. Updating Host Multipath Software and Unzoning from the Source HDS Storage System (page 56) For Linux: Updating Host Multipath Software and Unzoning from Source HDS Storage System (page 62) For AIX: Updating Host Multipath Software and Unzoning from Source HDS Storage System (page 67) For HP-UX Updating Host Multipath Software and Unzoning from Source HDS Storage System (page 73) 2 Using the HP 3PAR Online Import Utility, start the For Windows: migration with the startmigration command. Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System (page 59) For Linux: Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System (page 64) For AIX: Starting the Data Migration from the Source HDS Storage System to the Destination HP 3PAR StoreServ Storage System (page 69) For HP-UX: Starting the Data Migration from the Source HDS Storage System to the Destination HP 3PAR StoreServ Storage System (page 74) 3 Power up the host and rescan migrating disks. For Windows: Restart server applications (including cluster). Bringing the Windows Host Back Online (page 60) For Linux: Bringing the Linux Host Back Online (page 65) For AIX: Bringing the AIX Host Back Online (page 70) For HP-UX: Bringing the HP-UX Host Back Online (page 75) 4 Monitor migration with the HP 3PAR Online Import Utility until completion. Viewing Migration Status (page 80) Minimally Disruptive Migration 11

12 Post-Migration Table 8 Post-migration checklist MDM Number Step Optional: Remove the migration definition when the migration has completed. See removemigration (page 97). Remove zoning between the HDS Storage system and HP 3PAR StoreServ Storage system after all migrations from the HDS Storage system are complete. Optional: When all migrations are complete, remove the source HDS Storage system and the destination HP 3PAR StoreServ Storage from the HP 3PAR Online Import Utility, using the removesource and removedestination commands. Reconfigure peer ports to host ports. Offline Migration Prerequisite Component Installation Table 9 Prerequisite component installation offline Number Step Check the HP SPOCK website to confirm proper configuration. Install the HCS. Install the HCS core CLI/SMI-S license or the HDS Device Manager license. Install the HP 3PAR Online Import Utility. See HP SPOCK ( See also Configuration Rules for HP 3PAR Online Import Support (page 14) Installing the HCS/SMI-S (page 14) HCS CLI SMI-S License (page 14) or HCS Device Manager License (page 18) Installing the HP 3PAR Online Import Utility (page 20) Premigration Table 10 Premigration checklist offline Number Step Zone the HDS Storage system and the HP 3PAR StoreServ Storage system as peers. Stop all server applications; offline/unmount LUNs. Using the HP 3PAR Online Import Utility, add the source storage system with the addsource command). Add destination storage system (HP 3PAR Online Import Utility: adddestination command). Validate connections by using the HP 3PAR Online Import Utility showconnection command. See Zoning the Source HDS Storage to the Destination HP 3PAR StoreServ Storage System (page 36) Preparing the Host for Data Migration (page 39) Identifying the Source and Destination Storage Systems (page 37) Identifying the Source and Destination Storage Systems (page 37) 12 Migration Process Checklists

13 Table 10 Premigration checklist offline (continued) Number 5 6 Step Using the HP 3PAR Online Import Utility, create the migration with the createmigration command). Zone the host and the HP 3PAR StoreServ Storage system and shut down the host. See Creating the Data Migration Task (page 77) Zoning the Host to the Destination HP 3PAR StoreServ Storage System (page 77) Migration Table 11 Migration checklist offline Number Step See 1 Using the HP 3PAR Online Import Utility, start the migration with the startmigration command. Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System (page 78) 2 Monitor migration with the HP 3PAR Online Import Utility until completion. Viewing Migration Status (page 80) Post-Migration Table 12 Post-migration checklist offline Number Step Unzone the source HDS Storage system from the host. Power up the host. Remove the HDLM software, if present, and configure the native multipath software. Export the imported LUNs from the HP 3PAR StoreServ Storage system to the host. Optional: Remove the migration definition when the migration has completed. When all migrations are complete, remove the source HDS Storage system and the destination HP 3PAR StoreServ Storage from the HP 3PAR Online Import Utility, using the removesource and removedestination commands. See Performing Post-Migration Tasks Specifically for Offline Migration (page 79), step 1 Performing Post-Migration Tasks Specifically for Offline Migration (page 79), step 2 Performing Post-Migration Tasks Specifically for Offline Migration (page 79), step 3 Performing Post-Migration Tasks Specifically for Offline Migration (page 79), step 5 removemigration (page 97) removesource (page 98) removedestination (page 97) Offline Migration 13

14 3 Installation and Setup for Data Migration This chapter describes requirements for data migration using the HP Online Import Utility. Configuration Rules for HP 3PAR Online Import Support For detailed information about ensuring that the source HDS Storage system and the destination HP 3PAR StoreServ Storage system are configured properly for data migration, see the HP SPOCK website: HP SPOCK ( The HP SPOCK website lists the supported system environment, including: The supported source HDS Storage systems and their associated firmware levels. The supported destination HP 3PAR StoreServ Storage systems and their associated HP 3PAR OS levels. The supported host operating systems. The supported HBAs and the associated BIOS/firmware/driver versions to allow HP 3PAR StoreServ Storage and HDS Storage coexistence. The supported configuration environments for installing HP 3PAR Online Import. Installing the HCS/SMI-S To access the SMI-S portion of the HCS, full implementation of the HCS is not required. The SMI-S functionality can be obtained from either of the following licenses: 1. HCS CLI SMI-S license 2. HCS Device Manager license NOTE: If you do not have either of these licenses, contact your HDS representative. HCS CLI SMI-S License The HCS CLI SMI-S license entitles you to use the SMI-S provider and the core CLI of HCS software. To install the HCS CLI SMI-S License, first obtain a license key using the registration number from the HCS CLI SMI-S License entitlement certificate. Follow these steps: 1. Install the HCS Device Manager by selecting default settings. When you install the HCS, the SMI-S component is installed and enabled by by-default. NOTE: See HP SPOCK for supported versions of the HCS: HP SPOCK ( 2. After successful installation, the HCS program appears under Windows Start programs as Hitachi Command Suite. 3. From the Hitachi Command Suite program, select Login - HCS. The Hitachi Command Suite login screen appears (Figure 1 (page 15)) 14 Installation and Setup for Data Migration

15 Figure 1 Hitachi Command Suite login screen 4. Click the License button and browse to the license file. 5. Apply the HCS CLI SMI-S license, and then click Save. 6. Validate the license key by inspecting the Device Manager License Information screen (Figure 2 (page 15)) Figure 2 HCS core license 7. Log into the HCS, using the following credentials: User system Password: manager Installing the HCS/SMI-S 15

16 8. Download the HCS by selecting Hitachi Command Suite Tools Download In the Device Manager Software Deployment dialog box, select Device Manager Command Line Interface (CLI) Application and download the Windows edition (see Figure 3 (page 16)). Figure 3 Downloading the Windows edition of the HCS CLI 9. Move the HCS CLI download to a directory of your choice, and double-click the file to install the application. 10. To configure the HCS CLI, edit HiCommandCLI.properties in the directory where the HCS CLI was installed, using the following settings: hdvmcli.serverurl = user = system password = manager NOTE: For this configuration, it is assumed that the HCS CLI application is installed in the same system as the HCS and uses the default login credentials. If any of these have been modified, update HiCommandCLI.properties accordingly. 11. Add the HDS USP_VM, HDS USP_V, HDS USP, or HDS NSC to the HCS, using the HCS CLI. Follow these steps: a. Open a Windows command prompt and change the path to the location where the HCS CLI was installed. b. Issue the AddStorageArray command to register the HDS USP_VM, HDS USP_V, HDS USP, or HDS NSC with the HCS (see Example 1 AddStorageArray command ). 16 Installation and Setup for Data Migration

17 Example 1 AddStorageArray command HiCommandCLI AddStorageArray ipaddress=x.x.x.x family=usp_v userid=******** arraypasswd=****** displayfamily=usp_v where: ipaddress: The IP address or host name of the HDS Storage system. userid: The user ID used to access the storage system (a user ID for the HDS Storage Navigator for the HDS Storage array) arraypasswd: The user password used to access the storage system (a password for the HDS Storage Navigator for the HDS Storage array) Figure 4 AddStorageArray command and output Installing the HCS/SMI-S 17

18 NOTE: When the HDS Storage system is being added, the service processor must be in View Mode. Adding the storage system might take up to 3 minutes. HCS Device Manager License To install the HCS Device Manager License, first obtain a license key using the registration number from the HCS Device Manager License Entitlement Certificate. Follow these steps: 1. On the HCS login screen, click the License button and browse to the license file (see Figure 5 (page 18)). Figure 5 Hitchi Command Suite login screen 2. Apply the HCS Device Manager license, and then click Save.. 3. Validate the license key by inspecting the Device Manager License Information screen (Figure 6 (page 19)). 18 Installation and Setup for Data Migration

19 Figure 6 HCS Device Manager license 4. Log into the HCS, using the following credentials: User system Password: manager 5. Using the HCS, add the HDS Storage system. Follow these steps: a. Click Hitachi Command Suite, click the Resources tab, and then, under Storage Systems, select Add Storage System (see Figure 7 (page 19)). Figure 7 Adding an HDS Storage system b. Use the following settings: Storage System Type: USP or USP_V IP Address/Host Name: The IP address or host name of the target storage system. Installing the HCS/SMI-S 19

20 User ID: The user ID used to access the storage system (a user ID for the HDS Storage Navigator for the HDS Storage array) Password: The user password used to access the storage system (a password for the HDS Storage Navigator for the HDS Storage array) NOTE: When the HDS Storage system is being added, the service processor must be in View Mode. Adding the storage system might take up to 3 minutes. Installing the HP 3PAR Online Import Utility These steps describe the process for installing the HP 3PAR Online Import Utility. The default directories and options are shown below: Default installation directory: C:\Program Files (x86)\hewlett-packard\hp3paroiu Default log file name : C:\Program Files (x86)\hewlett-packard\hp3paroiu\oiutools\ tomcat\32-bit\apache-tomcat \logs\hpoiu.log Default port numbers: Service port: 2370 Shutdown port: Double-click the installer package image icon to begin the installation process. The HP 3PAR Online Import Utility splash screen appears with the InstallShield Wizard. 20 Installation and Setup for Data Migration

21 2. When the Welcome screen appears, click Next. Installing the HP 3PAR Online Import Utility 21

22 3. Accept the end user license agreement and click Next. The Custom Setup dialog box appears. 4. To choose the default setup (installation of the HP 3PAR Online Import Utility server and client on this machine), click Next. Otherwise, select the component that you want to omit from this installation. Use this option if you want to install the HP 3PAR Online Import Utility server and client on separate machines, 22 Installation and Setup for Data Migration

23 and then click Next to continue. 5. Click Yes if you have a CA signed certificate, or click No to generate a certificate from the installer. NOTE: After the certificate installation dialog box is passed, the installer checks whether the default ports are already in use on this machine. If they are, another dialog box will be displayed, prompting you to specify available ports to use for this installation. This is not a common occurrence. If there was a conflict with the default port numbers and different port numbers were supplied to the installation process, the following steps must be taken after installation is complete to properly use the new ports: a. Edit OIUCli.bat, located at: <Install location>\hewlett-packard\hp3paroiu\cli b. If port 2396 was chosen as the alternative to 2370, make the change in the OIUCli.bat file, as shown in the following example: Example 2 Editing the service port in the OIUCli.bat file java -jar..\cli\oiucli jar-with-dependencies.jar %* -port Click Install. Installing the HP 3PAR Online Import Utility 23

24 7. Monitor the progress of the installation. When complete, click Next. 8. Tomcat services will begin installation. When complete, click Next. 24 Installation and Setup for Data Migration

25 IMPORTANT: The installer does not support doing a close, cancel, or kill action during the Tomcat Installation. If the installation of Tomcat is interrupted, the software installation is not fully cancelled and is left in an indeterminate state. Do not click the Cancel button or close the window by clicking the X in the upper-right corner. 9. Select the Show the Windows Installer log check box, and then click Finish. Installing the HP 3PAR Online Import Utility 25

26 10. After you click the Finish button, the log appears in a separate window. Save the log in a location of your choice. 11. The HP 3PAR Online Import Utility shortcut is installed on your desktop. 12. After successful installation, verify that the following groups have been created: HP Storage Migration Admins group has been created. HP Storage Migration Admins HP Storage Migration Users 13. Add the Administrator account or another account with administrator privileges as a member of HP Storage Migration Admins group. This is the USERNAME that will be used in starting the HP 3PAR Online Import Utility. 14. To start the utility, double-click the HP 3PAR Online Import Utility desktop icon, and provide local credentials as stated in the note below. NOTE: If the client and server components have been installed on the same machine, you can use the keyword LOCALHOST to connect to the local server. Otherwise, use the IP address or the DNS hostname of the machine where the server is located. Migrations Supported by HP 3PAR Online Import Utility For migration types supported by the HP 3PAR Online Import Utility for the HDS USP_VM, the HDS USP_V, the HDS Tagmastore USP, and the HDS Tagmastore NSC, see Table 14 (page 27). See Table 13 (page 26) for a legend for the migration-type tables. Table 13 Legend for the migration support tables LUN Host 26 Installation and Setup for Data Migration

27 Table 13 Legend for the migration support tables (continued) Host group Item selected by user input on the HP 3PAR Online Import Utility Migrations Supported for HDS USP_VM, HDS USP_V, HDS USP, and HDS NSC Migrations supported by the HP 3PAR Online Import Utility for HDS USP_VM, HDS USP_V, HDS USP, and HDS NSC are shown in Table 14 (page 27). Table 14 Migration supported by the HP 3PAR Online Import Utility Supported Configuration Description Single LUN, single host The host is selected in the HP 3PAR Online Import Utility. Single LUN, single host The LUN is selected in the HP 3PAR Online Import Utility. Multiple LUNs, single host The host is selected in the HP 3PAR Online Import Utility. Multiple LUNs, single host All LUNs are selected in the HP 3PAR Online Import Utility. Migrations Supported by HP 3PAR Online Import Utility 27

28 Table 14 Migration supported by the HP 3PAR Online Import Utility (continued) Supported Configuration Description Multiple LUNs, single host Not all LUNs are selected in the HP 3PAR Online Import Utility. All LUNs will be migrated. Single LUN, multiple hosts The host is selected in the HP 3PAR Online Import Utility. Single LUN, multiple hosts The LUN is selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts The host is selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts All LUNs are selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts Not all LUNs are selected in the HP 3PAR Online Import Utility. Single LUN, multiple hosts The host is selected in the HP 3PAR Online Import Utility. 28 Installation and Setup for Data Migration

29 Table 14 Migration supported by the HP 3PAR Online Import Utility (continued) Supported Configuration Description Single LUN, multiple hosts The LUN is selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts One of the hosts is selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts All LUNs are selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts Not all LUNs are selected in the HP 3PAR Online Import Utility. Single LUN, multiple hosts One of the hosts is selected in the HP 3PAR Online Import Utility. Single LUN, multiple hosts The LUN is selected in the HP 3PAR Online Import Utility. Migrations Supported by HP 3PAR Online Import Utility 29

30 Table 14 Migration supported by the HP 3PAR Online Import Utility (continued) Supported Configuration Description Multiple LUNs, multiple hosts One of the hosts is selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts All LUNs are selected in the HP 3PAR Online Import Utility. Multiple LUNs, multiple hosts Not all LUNs are selected in the HP 3PAR Online Import Utility. 30 Installation and Setup for Data Migration

31 4 Preparing for Data Migration Use the information in this chapter to ensure all necessary tasks are performed and considerations are understood before beginning a migration. Data Migration Considerations Before migrating data using 3PAR Online Import for HDS Storage, be aware of the following general considerations, system requirements, and other tasks associated with planning, host configuration, and network and zoning requirements. General Considerations LUNs and hosts can be implicitly added to the migration, even if they are not specified by the input. Only LDEVs presented to Fibre Channel hosts can be migrated. LDEVs presented to iscsi hosts cannot be migrated. Only LUNs presented to Open-x systems are supported. All LUNs present in a host group are migrated, even if only one was selected. When a host is selected for migration, all LUNs presented to that host are migrated to the same CPG. When a cluster is being migrated, all the hosts in the cluster must be migrated at once. LDEVs identified for migration should not be part of any current replication or backup jobs. The LDEV limit for offline migrations is 25. The maximum number of LDEVs that can be migrated with MDM or online migration is 255. A createmigration command cannot simultaneously contain a host and a LUN for migration. Only one createmigration is allowed at a time because 3PAR Peer Ports can be in only one HDS Storage host group at a time. When an LDEV on the source HDS Storage system is migrated, a SCSI-3 reservation is issued to prevent any unwanted management changes to the LDEV during the migration. The SCSI-3 reservation is removed after the migration. Only one HDS Storage system at a time can be attached as a source to the destination HP 3PAR StoreServ Storage system. HDS LDEVs cannot be migrated if they are less than 256 MB, the minimum volume size on the HP 3PAR StoreServ Storage systems. The HP 3PAR StoreServ Storage is 256 MB boundary-based. An LDEV, even one that is not a multiple of 256 MB, can still be migrated, provided that the LDEV is not smaller than 256 MB. HDS LDEVs cannot be migrated if they are larger than 16 TB, the maximum volume size on the HP 3PAR StoreServ Storage system. For more information, see the appropriate HP 3PAR implementation guide. Implementation guides are available at the following website: HP Storage Information Library ( Data Migration Considerations 31

32 System Requirements NOTE: For detailed information about ensuring the source HDS Storage system and the destination HP 3PAR StoreServ Storage system are configured properly for data migration, see the HP SPOCK website: HP SPOCK ( Before migrating data from an HDS Storage system to an HP 3PAR StoreServ Storage system using HP 3PAR Online Import for HDS Storage, the system environment must meet the following requirements: Source HDS Storage system must be running a supported firmware level. See the HP SPOCK website for supported firmware versions: HP SPOCK ( The destination HP 3PAR StoreServ Storage system must have a valid HP 3PAR Online Import or HP 3PAR Peer Motion license installed. The destination HP 3PAR StoreServ Storage system must be at a supported HP 3PAR OS level. See HP SPOCK: HP SPOCK ( Planning for Migration Advanced planning ensures that you achieve the desired results when migrating data. It is a recommended best practice to make a backup of your host/data before starting a migration. A maintenance window is required for the removal of the HDLM, if present. Identify which LDEVs and/or hosts will be migrated. If you do not want to migrate all the LDEVs presented to a host, you must unpresent the LDEVs that you do not want migrated. Otherwise, all the LDEVs will be implicitly included in the migration. When you migrate TPVVs from the HDS Storage system, only those volumes can be migrated where the TPVV pool size is greater than or equal to the total size of the volumes selected for migration. NOTE: Volume size is the actual size, not merely the space used by the TPVV. Determine whether you will be using dynamic, full, or dedupe provisioning on the destination storage system. This decision impacts the amount of capacity needed on the destination storage system. Because there is some impact on performance, you may want to schedule migrations during off-peak hours, if possible. Hosts with a lighter load/less data should be migrated first. If you are using any LUNs larger than 2 TB on an HDS USP, then before performing a migration, set the system option mode to enable the 16 byte commands for LUNs larger than 2 TB. Setting this system option mode does not change the behavior on the host side, so it can be set at any time before migration. See HDS documentation for more information. The system option mode need not be specially set for an HDS USP_V or an HDS USP_VM. Network and Fabric Zoning Requirements Data migration requires zoning operations to create paths between the source and destination storage systems and any hosts involved in the migration. The data paths used are shown in. A blue line indicates a peer link between the HP 3PAR StoreServ Storage and the HDS Storage system. A red line indicates a data link. 32 Preparing for Data Migration

33 Figure 8 Data migration zoning Two unique paths must be zoned between the source and destination storage systems. To create two paths, two controller ports on the source HDS Storage system must be connected to two peer ports on the destination HP 3PAR StoreServ Storage system. See Zoning the Source HDS Storage to the Destination HP 3PAR StoreServ Storage System (page 36). Paths between the host and the source HDS Storage system are unzoned before the data migration starts. The timing for this depends on the operating system of the host and the migration type. During data migration, paths must be zoned between the host and destination HP 3PAR StoreServ Storage system. The time at which these paths are created is determined by the operating system of the host and the migration type. Reconfiguring the Host Multipath Solution Data migration may involve reconfiguring the host multipath solution from an HDS multipath solution to one supported by an HP 3PAR Storage system. For the supported multipath solutions for HP 3PAR StoreServ Storage systems, see HP SPOCK: HP SPOCK ( After the migration preparation phase is complete, the host must be reconfigured to use the multipath software for the HP 3PAR StoreServ Storage system. The HDS multipath software installed on the host can stay present until the last HDS LDEVs are migrated. The HDS multipath software can be removed at the next maintenance window, but this is not required. For MDM, the host must be shut down for the zoning changes and multipath reconfiguration. While the host is down, data transfer is started, after which the host is brought back online. This process ensures that the host is never multipathing between the source HDS Storage system and the destination HP 3PAR StoreServ Storage system. Even if the native multipath software is already configured, it is necessary to restart the host after unzoning the source HDS Storage system from the host. NOTE: After the migration has completed, if the host connects to another HDS Storage array, the HDS multipathing software must remain installed on the host. If no other HDS arrays are connected, then optionally, the HDS multipathing software may be uninstalled. Data Migration Considerations 33

34 Working with Consistency Groups The optional HP 3PAR Consistency Group feature allows you create and consistently migrate dependent volumes of applications. I/O that is issued to volumes that are members of a consistency group is mirrored to the source array until all members are completely migrated to the destination array, keeping the source volumes in a consistent state. NOTE: A consistency group can be created for all volumes of a host or a subset of volumes of a host. The HP 3PAR Consistency Group feature can be used for host-based migration. A consistency group can be created for all volumes of a host or a subset of volumes of a host. The HP 3PAR Consistency Group feature can be used for host-based migration. For consistent imports, HP recommends that you limit the number of volumes in a consistency group to 20. To avoid long switch-over times at the end of imports, HP recommends that you limit the total size of volumes in a set to 40 TB. Creating a Consistency Group Consistency groups are defined in the createmigration command. The following parameters are available to create consistency groups: cgvolmap: Defines the consistency groups and their member LDEVs. allvolumesincg: All volumes (including implicit volumes) will be migrated consistently. Example 3 Volume-based migration with specified volumes in consistency groups # createmigration -sourceuid AF0002AC001BA1 -srcvolmap "[{vol1, thin, testcpg},{vol2, thin, testcpg},{vol3, thin, testcpg}]" -destcpg testcpg -destprov testcpg -cgvolmap{ values":{"cg1": ["vol1","vol2]}} migtype online -persona RHEL_5_6 Three volumes (vol1, vol2 and vol3) are chosen for migration. A consistency group named cg1 will be created, containing vol1 and vol2. When a startmigration command is issued, I/O to both vol1 and vol2 will be mirrored to both the source storage array and the HP 3PAR StoreServ Storage until both vol1 and vol2 import tasks are complete. After both vol1 and vol2 import tasks are complete, I/O for both volumes will cut over to the HP 3PAR StoreServ Storage. Example 4 Volume-based migration with all volumes in a consistency group # createmigration -sourceuid AE0002AC001BA2 -srcvolmap "[{vol1, thin, testcpg},{vol2, thin, testcpg},{vol3, thin, testcpg}]" -allvolumesincg -destcpg testcpg -destprov testcpg migtype online -persona RHEL_5_6 All volumes (including implicit volumes) will be placed in a single consistency group. When a startmigration command is issued, I/O to all volumes will be mirrored to both the source storage array and the HP 3PAR StoreServ Storage until all import tasks complete. After all import tasks are complete, I/O for all volumes will cut over to the HP 3PAR StoreServ Storage. 34 Preparing for Data Migration

35 Example 5 Host-based migration with specified volumes in consistency groups # createmigration -sourceuid 8F0002AC001BA4 -srchost "hostname" -migtype online -destcpg testcpg -destprov thin -cgvolmap{ values":{"cg1":["vol1","vol2","vol3"],"cg2":["vol4","vol5","vol6"]}} migtype online -persona RHEL_5_6 All volumes (including implicit volumes) presented to the host are chosen for migration. Two consistency groups will be created: cg1, containing vol1, vol2, and vol3 cg2, containing vol4, vol5, and vol6 Any other LDEV that was defined explicitly in the createmigration command, or that was added implicitly, will be migrated, but not as a part of a consistency group. When a startmigration command is issued, I/O for volumes in both cg1 and cg2 will be mirrored to both the source storage array and the HP 3PAR StoreServ Storage until all cg1 or cg2 import tasks are complete. After cg1 or cg2 import tasks are complete, I/O to the respective consistency group volumes will cut over to the HP 3PAR StoreServ Storage. Example 6 Host-based migration with all volumes in a consistency group # createmigration -sourceuid 8F0002AC001BA3 -srchost "hostname" -migtype online -destcpg cpg1 -allvolumesincg migtype online -persona RHEL_5_6 NOTE: HP recommends that only allvolumesincg be used with Oracle RAC. All LDEVs (including implicit volumes) presented to the host will be placed in a single consistency group. When a startmigration command is issued, I/O to all LDEVs will be mirrored to both the source storage array and the HP 3PAR StoreServ Storage until all import tasks are complete. After all import tasks complete, I/O for all volumes will cut over to the HP 3PAR StoreServ Storage. Working with Consistency Groups 35

36 5 Premigration Steps Perform these steps to prepare for migration. Zoning the Source HDS Storage to the Destination HP 3PAR StoreServ Storage System The correct zoning must be present between the source HDS Storage system and destination HP 3PAR StoreServ Storage system at every stage of the migration operation. The following zoning rules apply: There must be two unique paths between the source and destination storage systems. To create two paths, the two controller host ports on the source HDS Storage system must be zoned to two peer ports on the destination HP 3PAR StoreServ Storage system. The peer ports on the destination HP 3PAR StoreServ Storage system must be on adjacent nodes: 0/1, 2/3, 4/5, or 6/7. Zone the source and destination systems together and make sure they are visible to each other before zoning hosts to the destination system. Do not unzone the source and destination systems from each other until the data migration is complete. To create the zoning: 1. On the destination HP 3PAR StoreServ Storage system, configure two free ports as peer ports using adjacent nodes: 0/1, 2/3, 4/5, or 6/7. a. Set the port connection type to point. b. Set the port connection mode to peer. Example 7 HP 3PAR CLI controlport command # controlport offline n:s:p # controlport config peer -ct point n:s:p # controlport rst n:s:p 2. Create two zones between the source HDS Storage system and the destination HP 3PAR StoreServ Storage system, ensuring that one HDS host port is in the same zone with one HP 3PAR peer port. NOTE: The WWN of a host port changes when it is set to become a peer port. Use the new WWN of the peer port in the zoning. Each zone should contain only two ports: one from each storage system. Adjacent HP 3PAR peer nodes should be zoned to an HDS CHA board in separate array power domains in a one-to-one mapping. For example, zone the peer port on node 0 on the HP 3PAR StoreServ Storage system to a CHA in domain 1 on the HDS Storage system, and zone the peer port 36 Premigration Steps

37 on node 1 on the HP 3PAR StoreServ Storage system to a CHA in domain 2 on the HDS Storage system. 3. Verify that the HDS Storage system can detect both ports on the HP 3PAR StoreServ Storage system. Ensure that the peer port WWNs appear in the discovered port list. To check peer port connections from the HP 3PAR StoreServ Storage, issue the showportdev command. See Example 8 Checking peer port connections using the showportdev command Example 8 Checking peer port connections using the showportdev command Identifying the Source and Destination Storage Systems Prerequisites This section provides information on how to identify and add the source and destination storage systems for migration. Before beginning, prerequisites must be met and information about the source and destination systems must be gathered. The HiCommand Suite is installed and licensed with either the CLI/SMI-S or the Device Manager license. The source HDS Storage system must be registered in the HiCommand Suite application. The source HDS system has one or more host groups configured with the hosts and volumes to be migrated. The HP 3PAR Online Import Utility is installed and operational with access to the HiCommand Suite server managing the source HDS Storage system and the destination HP 3PAR StoreServ Storage system. The source HDS Storage system and destination HP 3PAR StoreServ Storage system are zoned to each another. After all changes, refresh your HDS Storage array in the HiCommand Suite, using the HiCommand Suite Device Manager or the HDS Storage CLI. Required Information HDS Storage source system: IP address of the HiCommand Suite server that is managing the source HDS Storage system from which the volumes are being migrated and the serial number of the source HDS Storage system. User name and password for the HiCommand Suite. Port access to the HiCommand Suite. Secure port default Non-secure port default Identifying the Source and Destination Storage Systems 37

38 Destination HP 3PAR StoreServ Storage system IP address of the destination HP 3PAR StoreServ Storage system. User name and password for the HP 3PAR management application with Super user permission. Adding the Source Storage System To identify the source storage system, follow these steps: 1. From the HP 3PAR Online Import Utility, issue the addsource command. NOTE: Use local user credentials to log into the HP 3PAR Online Import Utility. Example 9 addsource command # addsource -type HDS -mgmtip XX.XX.XX.XX -user admin -password adminpw uid xxxxx # SUCCESS: Added source storage system where XX.XX.XX.XX is the IP address of the HiCommand Suite server, and xxxxx is the 5-digit serial number of the HDS Storage system. 2. Issue the showsource command to verify the source storage system information. Example 10 showsource command # showsource type HDS NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE USP_V XX.XX.XX.XX Good Adding the Destination Storage System To add the destination storage system, follow these steps: 1. From the HP 3PAR Online Import Utility, issue the adddestination command. Example 11 adddestination command # adddestination mgmtip XX.XX.XX.XX user 3paradm password 2Password # SUCCESS: Added destination storage system where XX.XX.XX.XX is the HP 3PAR management port IP address. If a certificate validation error occurs on the adddestination command (see Example 12 Certificate validation error ), first run the installcertificate command (see Example 13 Installcertificate command ), then run the adddestination command again. 38 Premigration Steps

39 Example 12 Certificate validation error # adddestination -mgmtip xx.x.xx.xx -user 3paradm -password ******* -port 5783 # ERROR: OIUERRDST0010 Unable to validate certificate. C:\\InFormMC\security\HP-3PAR-MC-TrustStore Example 13 Installcertificate command # installcertificate mgmtip xx.xx.xx.xx TParCertifacteVO [issuedto=hp 3PAR HP_3PAR , commonname=null, issuedbyorganization=null, issuedtoorganization=null, serialno=null, issedby=hp 3PAR HP_3PAR , fingerprint=89:e5:d0:13:6f:d1:07:80:70:76:5c:fe:5b:65:e5:54:c0:18:21:2f, signaturealgo=sha1withrsa, version=v1,validfrom=08/14/2014, validto=08/11/2024. issuedon=null, expireson=null, validdaterange=true] Do you accept the certificate? Y/YES Y # SUCCESS: Installed certificate successfully. 2. Issue the showdestination command to verify the destination storage system information. Example 14 showdestination command # showdestination NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE PEER_PORTS 3par_7200_DCB_01 3PAR 2FF70002AC005F (MU3) XX.XX.XX.XX Normal AC00-5F91(0:2:1) AC00-5F91(1:2:1) Preparing the Host for Data Migration NOTE: This section does not apply to online migration. To prepare for a successful migration: Stop all applications on the host that may be accessing the LUNs to be migrated. This also includes any replication and backup applications on the LUNs. Set the LUNs to be migrated to an offline/unmounted state. NOTE: Modify the startup scripts for all applications and services that are using the migrating LUNs to prevent them from starting at the next reboot. They should remain disabled until after the migration has started and documentation instructs you to bring your host back online. Preparing Windows Clusters for Migration When a Windows cluster is migrated, the cluster must first be disabled so that any SCSI reservations in use are released. For active/passive cluster running Windows Server 2008 or Windows Server 2008 R2, this can be achieved by stopping all applications running on the cluster, then stopping the cluster service on all nodes. For Hyper-V running on Windows Server 2008 R2, follow these steps to stop the cluster: 1. Set the quorum disk to Offline, CSV disks in Maintenance mode. 2. Using the Failover Cluster Manager, select Shutdown Cluster. 3. Clear the cluster reservation, if present, by following the appropriate Microsoft documentation about Hyper-V clusters. For Windows Server 2003 or Windows Server 2003 R2, stop the cluster service on each cluster node. For more information, see Microsoft documentation on how to start/stop the cluster services. Preparing HP-UX Clusters for Migration For HP-UX 11i v3, the Serviceguard cluster must be stopped gracefully before the node is shut down during MDM. For active/active clusters, offline all disks. For more information, see HP Serviceguard documentation. See the following website: Preparing the Host for Data Migration 39

40 HP-UX ServiceGuard ( Preparing Veritas Clusters for Migration NOTE: On Veritas clusters, stop the clusters by issuing the following command: # /opt/vrtsvcs/bin/hastop -all Then verify cluster status by issuing the following command: # /opt/vrtsvcs/bin/hastatus When the clusters are down, messages like the following will appear: attempting to connect... VCS ERROR V Cannot connect to VCS engine attempting to connect...not available; will retry To verify that a reservation is clear after stopping a cluster, follow these steps: 1. Issue the following command to get a list of all LDEVs used in the cluster: Example 15 Listing LDEVs in a cluster # vxdisk list DEVICE TYPE DISK GROUP STATUS hitachi_usp0_1000 auto:cdsdisk - - online hitachi_usp0_1001 auto:cdsdisk - - online hitachi_usp0_1002 auto:cdsdisk - - online hitachi_usp0_1003 auto:cdsdisk - - online hitachi_usp0_1004 auto:cdsdisk - - online hitachi_usp0_1005 auto:cdsdisk - - online hitachi_usp0_1006 auto:cdsdisk - - online hitachi_usp0_1007 auto:cdsdisk - - online hitachi_usp0_1008 auto:cdsdisk - - online 2. Create a tmpfile in the /root directory with all the LDEVs. the tmpfile will be similar to the following example: Example 16 tmpfile with LDEVs /dev/vx/rdmp/hitachi_usp0_1000 /dev/vx/rdmp/hitachi_usp0_1001 /dev/vx/rdmp/hitachi_usp0_1002 /dev/vx/rdmp/hitachi_usp0_1003 /dev/vx/rdmp/hitachi_usp0_1004 /dev/vx/rdmp/hitachi_usp0_1005 /dev/vx/rdmp/hitachi_usp0_1006 /dev/vx/rdmp/hitachi_usp0_1007 /dev/vx/rdmp/hitachi_usp0_ Issue the following command to verify that the reservation keys are clear: 40 Premigration Steps

41 Example 17 Verifying that reservation keys are clear # vxfenadm -s all -f tmpfile Device Name: /dev/vx/rdmp/hitachi_usp0_1000 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1002 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1001 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1004 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1003 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1005 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1007 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1006 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/hitachi_usp0_1008 Total Number Of Keys: 0 No keys If the reservation keys are not clear, issue the following commands on any one cluster node to clear them: # vxfenadm -a -k f tmpfile # vxfenadm -c -k f tmpfile The reservation keys are clear when each device in the tmpfile indicates No keys. Creating the Data Migration Task The data migration task performs the following actions in the preparation required for data migration: Required Information HDS Storage source system The serial number of the source HDS Storage system from which the volumes are being migrated. The list of one or more LDEV names that are being migrated, or the host name of the host that is being migrated. As a best practice, all LDEVs should be in the same host group, or in different host groups with identical LDEV membership. Creating the Data Migration Task 41

42 Destination HP 3PAR StoreServ Storage system Provisioning type for the volumes being created on the destination storage system (thin, full, or dedupe). The name of the CPG on the destination storage system where the volumes are being migrated. Issuing the createmigration Command The data migration task performs the following actions in the preparation required for data migration: On an HDS Storage system source, the HP 3PAR Online Import Utility creates two host groups containing the HP 3PAR Peer port initiators. The host group name format is HCMDXXXX. For online migration and MDM, the host or hosts that are being migrated are created on the destination storage system. A host set is also created on the destination storage system. For offline migration, the host definitions must be created by the storage administrator. For online migration, the LDEVs being migrated are admitted to the destination system and exported to the host. For MDM, the LDEVs are admitted to the destination storage system but are not exported to the host. If the createmigration calls for using consistency groups, then VV sets are created on the destination storage system. The VV sets will be removed from the destination storage system after migration completed. The createmigration command performs the following checks before creating the migration: No migration task for the specified source storage system exists. Only one migration at a time can be provisioned for a given source HDS Storage system. The source storage system group configuration is valid. The volumes or hosts specified in the createmigration command are mapped to a host group on the associated source HDS Storage system. All LUNs and all hosts in the mapped host group will be migrated even if only a subset are entered in the createmigration command. To determine whether your configuration is valid, see Migrations Supported by HP 3PAR Online Import Utility (page 26). LUN migration eligibility: Protocol must be Fibre Channel. A LUN under replication cannot be migrated. To create the migration for a given migration type using the createmigration command, see: Online migration, if the HDLM is installed: Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44), steps 5 8 Online migration, if the HDLM is not installed: Online Migration with Linux Native Device-Mapper (page 50), step 3 MDM Linux: Creating the Data Migration Task (page 62) Windows: Creating the Data Migration Task (page 56) 42 Premigration Steps

43 AIX: Creating the Data Migration Task (page 67) HP-UX: Creating the Data Migration Task (page 73) Offline migration: Creating the Data Migration Task (page 77) Creating the Data Migration Task 43

44 6 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3 If Hitachi Dynamic Link Manager (HDLM) is installed, it must be uninstalled, and the native Linux device-mapper must be used to configure multipathing before migrating the data. Follow the online data migration procedure in Online Data Migration with Removal of Hitachi Dynamic Link Manager (page 44). If HDLM is not installed, follow the online data migration procedure in Online Migration with Linux Native Device-Mapper (page 50). Online Data Migration with Removal of Hitachi Dynamic Link Manager To perform online data migration when the HDLM is present, follow these steps. NOTE: A maintenance window is required to complete an online data migration with removal of the HDLM. NOTE: Before migrating a SAN-based Oracle RAC cluster using the HP 3PAR Online Import Utility, it is critical to understand whether and how the Oracle RAC cluster registry (CRS), voting disks, and data disks are distributed across the source arrays, and to plan migrations accordingly. Since the HP 3PAR Online Import Utility is currently designed to execute a migration exclusively from one source array at a time, multiple migrations must be executed serially in order to transfer all the Oracle-based disks from multiple source arrays to a single destination HP 3PAR StoreServ Storage. This use-case scenario is described in detail in Appendix E: Use Case: Data Migration for an Oracle RAC Cluster (page 112). At the time of this publication, the coexistence or distribution of Oracle RAC disks is supported across the HP 3PAR StoreServ Storage and HDS Storage arrays listed in HP SPOCK: HP SPOCK ( NOTE: For ASM-based Oracle RAC configurations, the persistent device names that are used by the ASMlib to label ASM disks must be modified. With the HDLM, the devices get a /dev/sddlm* name, whereas with Linux native device-mapper multipath software, the devices get a /dev/mapper/mpath* name. To ascertain whether the current ASMlib is using the HDLM-based names, issue the following command: # oracleasm querydisk -p /dev/sddlm* HDLM-based-device names are being used if the output is similar to the following example: Device "/dev/sddlmaa1" is marked as an ASM disk with the label "ASM_DISK01" 1. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. 2. Uninstall the HDLM by following these steps: CAUTION: The HDLM must not be present during the migration process. The native Linux device-mapper multipath must be managing the paths. Stop all applications before removing the HDLM. For cluster configurations, also stop the cluster services and the cluster. Applications should be restarted after migration has started. a. Close all applications on the host. 44 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3

45 NOTE: Stop the Oracle RAC database services by issuing the following command on the primary node: # $ORACLE_HOME/bin/srvctl stop database -d <DB_name> -o immediate b. Unmount the application file systems, bring offline any raw devices (if configured), and deactivate any volume groups where Logical Volume Manager is in use. c. For a cluster, stop the cluster services, and then stop the cluster. NOTE: For Oracle RAC, stop the cluster services and the ASM by performing the following steps: 1) Issue the following command on the primary node: # $GRID_HOME/bin/crsctl stop cluster -all 2) To confirm that the cluster services have stopped, issue the following command on any of the nodes: # $GRID_HOME/crs_stat -t The expected output is as follows: CRS-0184: Cannot communicate with CRS Daemon 3) Stop the ASM by issuing the following command on each node: # /etc/init.d/oracleasm stop d. Uninstall the HDLM from the host, following HDS documentation instructions. 3. Configure the native device-mapper multipath on the host. In a cluster environment, update the multipath.conf file on each of the cluster nodes. NOTE: For Oracle RAC, multipath should be configured in accordance with Oracle recommendations. Edit the /etc/multipath.conf file to map the device WWNs to a persistent device alias. This alias will be used by the ASMlib to label ASM disks for the Oracle RAC application. The /etc/multipath.conf files should be edited identically on each of the cluster nodes. Make a note of the device type (for instance, ASM data disk, OCR disk, or FRA disk) while naming the disks, and keep them consistent with the way they were configured when the HDLM was enabled. For example: multipath { wwid e00029a62ca76d3e411 alias <DEVICE_ALIAS>} The value for alias must match the label used by the HDLM for that device. NOTE: For ESXi 5.5, set the multipath load balance policy to round-robin for all the devices on all ESX cluster nodes. To verify newly discovered paths using ESXi 5.5, issue the esxcfg-mpath -b command on the ESX node, or use the vcenter console. For HP-UX 11i v3, issue the ioscan -m lun command to verify newly discovered paths. If the HP 3PAR LUNs are not whitelisted, register the HP 3PAR LUN types with native device-mapper multipath by whitelisting HP 3PAR-specific information. (In the /etc/ multipath.conf file, the vendor is 3PARdata and the product is VV.) See the HP 3PAR StoreServ product documentation on the Linux host configuration. NOTE: 3PARdata and VV are case sensitive. If the HP 3PAR LUNs are whitelisted, start the native device-mapper multipath. Online Data Migration with Removal of Hitachi Dynamic Link Manager 45

46 Example 18 Starting the native device-mapper multipath # /etc/init.d/multipathd restart ok Stopping multipathd daemon: [ OK ] Starting multipathd daemon: [ OK ] Example 19 Rescanning HBAs and listing the updated multipath mapping for RHEL 5.x and RHEL 6.x # ls /sys/class/fc_host host4 host5 # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "1" > /sys/class/fc_host/host5/issue_lip # echo "- - -" > /sys/class/scsi_host/host4/scan # echo "- - -" > /sys/class/scsi_host/host5/scan # multipath -ll mpath2 (360060e80045be be ) dm-3 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] mpath1 (360060e80045be be ) dm-2 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready] 4. If the HDLM was uninstalled in step 2, and after multipathing has been configured again on the host, follow these steps: a. If the HDLM was removed, modify /etc/fstab for new mount points. Base the new mount points on discovered LUNs, if the migrating LUN alias was not created in the multipath.conf file. Remount file systems. IMPORTANT: In Linux, the HDLM devices are presented as /dev/sddlm* (for example, /dev/sddlmaa1). Removal of the HDLM in Linux also removes this device type. This changes when the Linux native device-mapper multipath assumes management of these devices. For example, before removal of the HDLM, consider combining /dev/sdb and /dev/sdc into /dev/sddlmaa1. After removal of the HDLM, /dev/sdb and /dev/ sdc would be represented by /dev/mpathx. This represents a challenge for customers who use direct device referencing in /etc/fstab or other custom scripts. HP generally recommends that fstab mounts be performed using blkid/uuid; however, this is not always employed. In that case, consider mounting /dev/sddlmaa1 as /var. After removal of the HDLM, /var would not automatically mount to /dev/mpathx. b. Where applicable, make the appropriate changes to the Logical Volume Manager configuration. c. If this is for a cluster configuration, initialize the cluster and start cluster services. 46 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3

47 NOTE: For Oracle RAC, edit the /etc/sysconfig/oracleasm file on both nodes in order to redirect the ASMlib to use the newly defined persistent device names from the etc/multipath.conf file, which will replace the HDLM-based /dev/sddlm* names that were being used to label the ASM disks. 1) In the /etc/sysconfig file, change the following: # ORACLEASM_SCANORDER: Matching patterns to order disk scanning ORACLEASM_SCANORDER="" # ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan ORACLEASM_SCANEXCLUDE="" to: # ORACLEASM_SCANORDER: Matching patterns to order disk scanning ORACLEASM_SCANORDER="dm" # ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan ORACLEASM_SCANEXCLUDE="sddlm" 2) Reset the oracleasm services by issuing the following commands on all cluster nodes, beginning with the primary node: # /etc/init.d/oracleasm start # oracleasm scandisks # oracleasm listdisks 3) Verify that all ASM disks are visible from all nodes. Also verify that the ASM disk labels are now using the Linux native device-mapper multipath-generated names by issuing the following command: # oracleasm querydisk -p <ASM_label> The output should be similar to the following example for all configured ASM disks: Device <DEVICE_ALIAS> is marked as an ASM disk with the label "ASM_DISK_*" 4) Restart the Oracle RAC cluster and database services by issuing the following command on the primary node: # $GRID_HOME/bin/crsctl start cluster -all # $ORACLE_HOME/bin/srvctl start database -d <DB_name> 5) Verify that all cluster services have been restarted by issuing the following commands on all nodes: # $GRID_HOME/bin/crs_stat t # $GRID_HOME/bin/crsctl stat res t init d. Start applications. 5. RHEL 5.x or RHEL 6.x: Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype online option. Optionally, migrations with consistency groups are also supported, using the -allvolumesincg or -cgvolmap parameters. NOTE: For Oracle RAC, you must issue the createmigration command using the -allvolumesincg parameter. Online Data Migration with Removal of Hitachi Dynamic Link Manager 47

48 Example 20 Using createmigration with -migtype online # createmigration -sourceuid xxxxxxxxxxxxxxxx -srchost "X7DBU-02-IG" -destcpg testcpg -destprov full -migtype online -persona RHEL_5_6 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: Example 21 Using createmigration with -migtype online for RHEL 5.x or RHEL 6.x # createmigration -sourceuid xxxxx -srchost "X7DBU-02-IG" -destcpg testcpg -destprov full -migtype online persona RHEL_5_6 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: For Oracle RAC: Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype online and -allvolumesincg parameters. Example 22 Using createmigration with -migtype online for Oracle RAC # createmigration -sourceuid xxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "RHEL_5_6" This step admits LUNs presented to the HDS Storage system and exports them to the HP 3PAR host created on the HDS Storage system. NOTE: The createmigration command may take several minutes to complete. TIP: Make a note of the migration ID, as it will be used in commands to track migration progress. 6. Issue the showmigration command to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the createmigration task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). When this status is indicated, continue to the next step. Example 23 Issuing the showmigration command # showmigration MIGRATIONID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online USP_V par_7200_DCA_01 Thu Sep 25 15: 23:50 EDT NA- preparationcomplete(100%)(-na-) 7. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN (see Figure 9 (page 49)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. 48 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3

49 Figure 9 HP 3PAR Management Console Host Details 8. Update path configuration on the host by rescanning all HBAs and issuing the multipath -ll command to verify the newly discovered paths. Multipath now recognizes extra paths to the HP 3PAR StoreServ Storage, but all paths are still managed as source array devices. NOTE: With ESXi 5.5 and HP-UX 11i v3, HBA rescanning verifies new paths on the destination storage system. Example 24 Rescanning HBAs and listing the updated multipath mapping with RHEL 5.x # ls /sys/class/fc_host host4 host5 # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "- - -" > /sys/class/scsi_host/host5/scan # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "- - -" > /sys/class/scsi_host/host5/scan # multipath -ll mpath2 (360060e80045be be ) dm-3 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 4:0:4:1 sdf 8:80 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] \_ 5:0:2:1 sdj 8:144 [active][ready] mpath1 (360060e80045be be ) dm-2 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 4:0:4:0 sde 8:64 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready] \_ 5:0:2:0 sdi 8:128 [active][ready] Online Data Migration with Removal of Hitachi Dynamic Link Manager 49

50 9. Delete the migrating LUN paths pertaining to the source array. For details about identifying and deleting LUN paths, see Appendix B: Identifying and Deleting Source Array LUN Paths (page 105). 10. Unzone the host from the source array, if applicable. Example 25 Output after unzoning the host from the source array with RHEL 5.x # multipath -ll mpath2(360060e80045be be ) dm-3 3PARdata,VV [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] mpath1(360060e80045be be ) dm-2 3PARdata,VV [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready] 11. Start the migration by using the HP 3PAR Online Import Utility startmigration command. Example 26 Starting migration by using startmigration # startmigration -migrationid # SUCCESS: Data transfer started successfully. NOTE: The -migrationid (in the example above, ) will have been assigned by the createmigration command. TIP: The STATUS column in the showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 27 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Online Migration with Linux Native Device-Mapper To perform online data migration using RHEL 5.x, RHEL 6.x, or Oracle RAC, follow these steps. 50 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3

51 NOTE: Before migrating a SAN-based Oracle RAC cluster using the HP 3PAR Online Import Utility, it is critical to understand whether and how the Oracle RAC cluster registry (CRS), voting disks, and data disks are distributed across the source arrays, and to plan migrations accordingly. Since the HP 3PAR Online Import Utility is currently designed to execute a migration exclusively from one source array at a time, multiple migrations must be executed serially in order to transfer all the Oracle-based disks from multiple source arrays to a single destination HP 3PAR StoreServ Storage. This use-case scenario is described in detail in Appendix E: Use Case: Data Migration for an Oracle RAC Cluster (page 112). At the time of this publication, the coexistence or distribution of Oracle RAC disks is supported across the HP 3PAR StoreServ Storage and HDS Storage arrays listed in HP SPOCK: HP SPOCK ( 1. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. 2. Configure the native device-mapper multipath on the host. In a cluster environment, update the multipath.conf file on each of the cluster nodes. Online Migration with Linux Native Device-Mapper 51

52 NOTE: For Oracle RAC, multipath should be configured in accordance with Oracle recommendations. Edit the /etc/multipath.conf file to map the device WWNs to a persistent device alias. This alias will be used by the ASMlib to label ASM disks for the Oracle RAC application. The /etc/multipath.conf files should be edited identically on each of the cluster nodes. For example: multipath { wwid e00029a62ca76d3e411 alias <DEVICE_ALIAS>} The value for alias must match the label used by the native OS multipath software for that device. NOTE: For ESXi 5.5, set the multipath load balance policy to round-robin for all the devices on all ESX cluster nodes. To verify newly discovered paths using ESXi 5.5, issue the esxcfg-mpath -b command on the ESX node, or use the vcenter console. For HP-UX 11i v3, issue the ioscan -m lun command to verify newly discovered paths. Example 28 Rescanning HBAs and listing the updated multipath mapping for RHEL 5.x and RHEL 6.x # ls /sys/class/fc_host host4 host5 # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "1" > /sys/class/fc_host/host5/issue_lip # echo "- - -" > /sys/class/scsi_host/host4/scan # echo "- - -" > /sys/class/scsi_host/host5/scan # multipath -ll mpath2 (360060e80045be be ) dm-3 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] mpath1 (360060e80045be be ) dm-2 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready] 3. RHEL 5.x or RHEL 6.x: Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype online option. Optionally, migrations with consistency groups are also supported, using the -allvolumesincg or -cgvolmap parameters. NOTE: For Oracle RAC, you must issue the createmigration command using the -allvolumesincg parameter. 52 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3

53 Example 29 Using createmigration with -migtype online for RHEL 5.x or RHEL 6.x # createmigration -sourceuid xxxxx -srchost "X7DBU-02-IG" -destcpg testcpg -destprov full -migtype online persona RHEL_5_6 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: For Oracle RAC: Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype online and -allvolumesincg parameters. Example 30 Using createmigration with -migtype online for Oracle RAC # createmigration -sourceuid xxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "RHEL_5_6" Example 31 Using createmigration with -migtype online for HP-UX 11i v3 (Standalone) # createmigration -sourceuid xxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "HPUX_11_v3" Example 32 Using createmigration with -migtype online for ESXi 5.5 # createmigration -sourceuid xxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "ESX_4_5" This step admits LUNs presented to the HDS Storage system and exports them to the HP 3PAR host created on the HDS Storage system. NOTE: The createmigration command may take several minutes to complete. TIP: Make a note of the migration ID, as it will be used in commands to track migration progress. 4. Issue the showmigration command to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the createmigration task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). When this status is indicated, continue to the next step. Example 33 Issuing the showmigration command # showmigration MIGRATIONID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online USP_V par_7200_DCA_01 Thu Sep 25 15: 23:50 EDT NA- preparationcomplete(100%)(-na-) 5. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN (see Figure 10 (page 54)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. Online Migration with Linux Native Device-Mapper 53

54 Figure 10 HP 3PAR Management Console Host Details 6. Update path configuration on the host by rescanning all HBAs and issuing the multipath -ll command to verify the newly discovered paths. Multipath now recognizes extra paths to the HP 3PAR StoreServ Storage, but all paths are still managed as source array devices. NOTE: With ESXi 5.5 and HP-UX 11i v3, HBA rescanning verifies new paths on the destination storage system. Example 34 Rescanning HBAs and listing the updated multipath mapping with RHEL 5.x # # ls /sys/class/fc_host host4 host5 # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "1" > /sys/class/fc_host/host5/issue_lip # echo "- - -" > /sys/class/scsi_host/host4/scan # echo "- - -" > /sys/class/scsi_host/host5/scan #multipath -ll mpath2 (360060e80045be be ) dm-3 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 4:0:4:1 sdf 8:80 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] \_ 5:0:2:1 sdj 8:144 [active][ready] mpath1 (360060e80045be be ) dm-2 HITACHI,OPEN-8 [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 4:0:4:0 sde 8:64 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready] \_ 5:0:2:0 sdi 8:128 [active][ready] 54 Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3

55 7. Delete the migrating LUN paths pertaining to the source array. For details about identifying and deleting LUN paths, see Appendix B: Identifying and Deleting Source Array LUN Paths (page 105). 8. Unzone the host from the source array, if applicable. CAUTION: With ESXi 5.5 and HP-UX 11i v3, before starting the migration, make sure that the source storage system has been removed and is no longer present on the host. If the source storage system has not been removed from the host, I/O loss can occur. Example 35 Output after unzoning the host from the source array with RHEL 5.x #multipath -ll mpath2(360060e80045be be ) dm-3 3PARdata,VV [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] mpath1(360060e80045be be ) dm-2 3PARdata,VV [size=6.8g][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready] 9. Start the migration by using the HP 3PAR Online Import Utility startmigration command. Example 36 Starting migration by using startmigration # startmigration -migrationid # SUCCESS: Data transfer started successfully. NOTE: The -migrationid (in the example above, ) will have been assigned by the createmigration command. TIP: The showmigration command status will indicate success when all LDEVs have been migrated successfully. Example 37 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Online Migration with Linux Native Device-Mapper 55

56 7 Performing Minimally Disruptive Migration Using a Windows Host The MDM process is used when migrating a Windows host attached to a source HDS Storage system. The host multipathing solution must be installed to communicate with the destination HP 3PAR StoreServ Storage system, and the host must be shut down briefly. Host I/O is interrupted only during the time it takes to reconfigure the host. Creating the Data Migration Task To create the data migration task for MDM, follow these steps: 1. Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype MDM option. Example 38 createmigration command # createmigration -sourceuid srchost "HPDL585-01" -destcpg FC_r5 -destprov thin -migtype MDM -persona WINDOWS_2008_R2 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: NOTE: The createmigration command may take several minutes to complete. TIP: Make a note of the migration ID, as it will be used in commands to track migration progress. 2. Issue the showmigration command to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the createmigration task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). When this status is indicated, continue to the next step. Example 39 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NA- preparationcomplete(100%)(-na-) Updating Host Multipath Software and Unzoning from the Source HDS Storage System CAUTION: The HDLM must not be installed during the migration process. For Windows Server 2012, Windows Server 2012 R2, Windows Server 2008, and Windows Server 2008 R2, Windows native MPIO must manage the paths. For Windows Server 2003 and Windows Server 2003 R2, the HP MPIO for Windows Server 2003 must manage the paths. Stop all applications before removing the HDLM. For cluster configurations, also stop the cluster services and the cluster. Applications should be restarted after migration has started. Perform the following steps on the Windows host: 56 Performing Minimally Disruptive Migration Using a Windows Host

57 1. If the HDLM software is present, remove it from the host, following HDS documentation instructions. IMPORTANT: If you are uninstalling the HDLM from a Windows host where the host is booting over SAN from the source system, you will be prompted to restart before removal is completed. This restart is required and must be completed. After removal, you will be prompted to restart the host in order for the changes to take effect. Do not restart at this point. 2. Removal of the HDLM software may have also disabled the MPIO installation without removing it. Manually check to see whether MPIO is still loaded, and if it is, fully remove it at this time. Now restart the host. For Windows Server 2003 R2 Cluster or Windows Server 2003 Cluster, if the cluster service has restarted after the reboot, you must stop it again on each cluster node. Updating Host Multipath Software and Unzoning from the Source HDS Storage System 57

58 3. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN. This number of paths is listed in the Node ID(s) column in Figure 11 (page 58). The path details are in the Host Details pane. Figure 11 Management Console Host Details 4. Configure MPIO multipath software on the host. For more information about configuring multipath software, see the HP 3PAR Windows Server 2012 or Windows Server 2008 Implementation Guide or the HP 3PAR Windows Server 2003 Implementation Guide. These documents are available on the following website: HP Storage Information Library ( For supported Windows Server OSs except Windows Server 2003 or Windows Server 2003 R2: a. Enable the Windows native multipath MPIO (if it is not already not enabled). b. Register HP 3PAR LUN types with MPIO by configuring MPIO to use 3PARdataVV as the device hardware ID. NOTE: 3PARdataVV is case sensitive. You will be prompted to reboot the host in order for the change to take effect. Do not reboot at this point, since the MDM procedure will require stopping the Windows host (in step 5). For Windows Server 2003 or Windows Server 2003 R2: a. Install HP MPIO for HP 3PAR. 58 Performing Minimally Disruptive Migration Using a Windows Host

59 NOTE: You will be prompted to reboot the host in order for the change to take effect. Do not reboot at this point, since the MDM procedure will require stopping the Windows host (in step 5). b. Upgrade HBA drivers if required. For information about supported HBA driver versions, see HP SPOCK: HP SPOCK ( c. Install the HP 3PAR NULL driver. The driver is available as a zip file (QL zip) on the HP Software Depot website: HP Software Depot ( displayproductinfo.do?productnumber=3par_null_driver) NOTE: You will be prompted to reboot the host in order for the change to take effect. Do not reboot at this point, since the MDM procedure will require stopping the Windows host immediately in the next step. 5. Shut down the Windows host. Leave the host offline until the migration is started. 6. Unzone the source HDS Storage system from the host. Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System 1. From the HP 3PAR Online Import Utility, issue the startmigration command. Example 40 startmigration command # startmigration -migrationid # SUCCESS: Data transfer started successfully NOTE: The -migrationid (in the example above, ) will have been assigned by the createmigration command. 2. To view the status of the migration, issue the showmigration command. Example 41 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- unpresenting(1%)(-na-) 3. Issue the showmigrationdetails command to verify the volumes being migrated. In the preparation stage, PROGRESS for each volume will be 0% and the TASK_ID will be unknown. Example 42 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System 59

60 Example 43 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % TIP: The STATUS column in the showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 44 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Bringing the Windows Host Back Online 1. Verify that the import has started and confirm that a TASK_ID is available for each volume by issuing the showmigrationdetails command. It is unsafe to bring the hosts back online if the TASK_ID number is not yet available in the output of showmigrationdetails. Example 45 Unsafe to bring the host online # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% It is safe to bring the host online when there is a valid TASK_ID in the output of the showmigrationdetails command. Example 46 Safe to bring the host online: # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % 2. After the import has started for the volumes, bring the Windows host or Windows cluster hosts that were shut down back online. NOTE: For a Windows host that is booting over SAN from the source system, the HBA BIOS must be reconfigured during host startup to select the HP 3PAR boot device. If this is not done, the host will not start up. 3. Check the disk status by pointing to diskpart.exe or by opening Disk Manager. Depending on the Windows SAN Policy, the disks that were migrated are offline or online. If offline, use diskpart or the disk manager to bring them online. 4. You can now restart the cluster, if applicable, and restart all applications and services. The host may resume normal operations. 60 Performing Minimally Disruptive Migration Using a Windows Host

61 TIP: The STATUS column in the showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 47 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Bringing the Windows Host Back Online 61

62 8 Performing Minimally Disruptive Migration Using a Linux Host The MDM type can be used when migrating a Linux host attached to a source HDS Storage system. The host must be shut down briefly during MDM. Host I/O is interrupted only during the time that the host is shut down. If you are performing online migration, see Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3 (page 44) Creating the Data Migration Task To create the data migration task for MDM, follow these steps: 1. Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype MDM option. Example 48 createmigration command # createmigration -sourceuid srchost "HPDL585-01" -destcpg FC_r5 -destprov thin -migtype MDM -persona RHEL_5_6 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: NOTE: The createmigration command may take several minutes to complete. TIP: Make a note of the migration ID, as it will be used in commands to track migration progress. 2. Issue the showmigration command to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the createmigration task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). When this status is indicated, continue to the next step. Example 49 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NA- preparationcomplete(100%)(-na-) Updating Host Multipath Software and Unzoning from Source HDS Storage System CAUTION: The HDLM must not be installed during the migration process. Native device-mapper multipath must be managing the paths. Stop all applications before removing the HDLM. For cluster configurations, also stop the cluster services and the cluster. Applications should be restarted after migration has started. Perform the following steps on the Linux host: 1. If the HDLM software is present, remove it from the host, following HDS documentation instructions. 62 Performing Minimally Disruptive Migration Using a Linux Host

63 a. Close all applications on the host. b. For a cluster, stop the cluster services, and then stop the cluster. c. Unmount the application file systems, bring offline any raw devices (if configured), and deactivate any volume groups where Logical Volume Manager is in use. d. Uninstall the HDLM from the host, following HDS documentation instructions. 2. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN (see Figure 12 (page 63)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. Figure 12 HP 3PAR Management Console Host Details 3. Configure device-mapper multipath (DM) on the host. a. Install device-mapper multipath (if not already installed). b. Register HP 3PAR LUN types with DM by whitelisting HP 3PAR-specific information (the vendor is 3PARdata and the product is VV) in /etc/multipath.conf. See the HP 3PAR StoreServ product documentation on the Linux host configuration, Native Linux Device-Mapper Multipath for HP Storage Disk Arrays reference guide, which is available at the following website: Native Linux Device-Mapper Multipath for HP Storage Disk Arrays reference guide ( spock.corp.hp.com/spock/utility/document.aspx?docurl=shared%20documents/an/ solutions_linux/device_mapper_multipath_rg.2014_06_16.pdf) NOTE: 3PARdata and VV are case sensitive. 4. Restart device-mapper multipath. Updating Host Multipath Software and Unzoning from Source HDS Storage System 63

64 5. If the HDLM was removed in step 1, modify /etc/fstab for new mount points. Base the new mount points on discovered LUNs, if the migrating LUN alias was not created in the multipath.conf file. 6. Shut down the Linux host. Leave the host offline until the migration is started. 7. Unzone the source HDS Storage system from the host. Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System 1. From the HP 3PAR Online Import Utility, issue the startmigration command. Example 50 startmigration command # startmigration migrationid # SUCCESS: Data transfer started successfully NOTE: The -migrationid (in the example above, ) will have been assigned by the createmigration command. 2. To view the status of the migration, issue the showmigration command. Example 51 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- unpresenting(1%)(-na-) 3. Issue the showmigrationdetails command to verify the volumes being migrated. In the preparation stage, PROGRESS for each volume will be 0% and the TASK_ID will be unknown. Example 52 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME...DESTINATION_VOLUME TASK_ID...PROGRESS 00:07:00 00_07_00 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. 64 Performing Minimally Disruptive Migration Using a Linux Host

65 Example 53 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME...DESTINATION_VOLUME TASK_ID...PROGRESS 00:07:00 00_07_ % TIP: The STATUS column in the showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 54 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Bringing the Linux Host Back Online To bring the Linux host back online, follow these steps: 1. Verify that the import has started and confirm that a TASK_ID is available for each volume by issuing the showmigrationdetails command. Example 55 Unsafe to bring the host online # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% 2. After all volumes have a value for their TASK_ID, bring the Linux host online. Example 56 Safe to bring the host online: # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % 3. Optionally, if LUNs are not discovered on the Linux host, scan for newly exported LUNs from the destination HP 3PAR StoreServ Storage system. Perform this step for all HBAs on the host that are connected to the HP 3PAR StoreServ Storage system. To scan for LUNs, use the following general commands: echo "1" > /sys/class/fc_host/host<#>/issue_lip echo "- - -" > /sys/class/scsi_host/host<#>/scan Example 57 Scanning the host for newly exported LUNs # ls /sys/class/fc_host host2 host3 # echo "1" > /sys/class/fc_host/host2/issue_lip # echo "1" > /sys/class/fc_host/host3/issue_lip # echo "- - -" > /sys/class/scsi_host/host2/scan # echo "- - -" > /sys/class/scsi_host/host3/scan Bringing the Linux Host Back Online 65

66 4. All applications and services can now be restarted and the host may resume normal operations (including first restarting the cluster if applicable). TIP: The STATUS column in the showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 58 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) 66 Performing Minimally Disruptive Migration Using a Linux Host

67 9 Performing Minimally Disruptive Migration Using an AIX Host The MDM type can be used when migrating an AIX host attached to a source HDS Storage system. The host must be shut down briefly during MDM. Host I/O is interrupted only during the time that the host is shut down. Creating the Data Migration Task To create the data migration task for MDM, follow these steps: 1. Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype MDM option. Example 59 createmigration command # createmigration -sourceuid srchost "HPDL585-01" -destcpg FC_r5 -destprov thin -migtype MDM -persona AIX # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: NOTE: The createmigration command may take several minutes to complete. TIP: Make a note of the migration ID, as it will be used in commands to track migration progress. 2. Issue the showmigration command to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the createmigration task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). When this status is indicated, continue to the next step. Example 60 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NApreparationcomplete(100%)(-NA-) Updating Host Multipath Software and Unzoning from Source HDS Storage System CAUTION: The HDLM must not be installed during the migration process. Native OS multipath software must be managing the paths. Stop all applications before removing the HDLM. For cluster configurations, also stop the cluster services and the cluster. Applications should be restarted after migration has started. Perform the following steps on the AIX host: 1. If the HDLM software is present, remove it from the host, following HDS documentation instructions. a. Close all applications on the host. b. For a cluster, stop the cluster services, and then stop the cluster. Creating the Data Migration Task 67

68 c. Unmount the application file systems, bring offline any raw devices (if configured), and deactivate any volume groups where Logical Volume Manager is in use. d. Uninstall the HDLM from the host, following HDS documentation instructions. 2. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN (see Figure 13 (page 68)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. Figure 13 HP 3PAR Management Console Host Details 3. Using the lspv command, make a note of the volume group to physical-volume identifier (PVID) mapping. 4. Using the exportvg command, export the volume groups. 5. On the host, use the rmdev -dl <disk> command to delete all disks that are on the HDS Storage and being migrated. 6. If the host is a member of a cluster, clear all the SCSI reservations on the cluster disks. 7. Install HP 3PAR Multipath I/O ODM for IBM (if not already installed). 8. Configure HP 3PAR Multipath I/O ODM for IBM on the host. For more information about configuring multipath software, see the HP 3PAR AIX and IBM Virtual I/O Server Implementation Guide. This document is available on the following website: HP Storage Information Library ( 9. Shut down the AIX host. Leave the host offline until the migration is started. 10. Unzone the source HDS Storage system from the host. 68 Performing Minimally Disruptive Migration Using an AIX Host

69 Starting the Data Migration from the Source HDS Storage System to the Destination HP 3PAR StoreServ Storage System 1. From the HP 3PAR Online Import Utility, issue the startmigration command. Example 61 startmigration command # startmigration migrationid # SUCCESS: Data transfer started successfully 2. To view the status of the migration, issue the showmigration command. Example 62 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NAunpresenting(1%)(-NA-) 3. Issue the showmigrationdetails command to verify the volumes being migrated. In the preparation stage, PROGRESS for each volume will be 0% and the TASK_ID will be unknown. Example 63 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. Example 64 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % TIP: The STATUS column in the showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 65 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Starting the Data Migration from the Source HDS Storage System to the Destination HP 3PAR StoreServ Storage System 69

70 Bringing the AIX Host Back Online To bring the AIX host back online, follow these steps: 1. Verify that the import has started and confirm that a TASK_ID is available for each volume by issuing the showmigrationdetails command. Example 66 Unsafe to bring the host online # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% 2. After all volumes have a value for their TASK_ID, bring the AIX host online. Example 67 Safe to bring the host online: # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % 3. On the AIX host, perform the following steps: a. Using the cfgmgr command, rescan the host for disks with the HP 3PAR signature. b. Verify that the AIX host is now seeing the volumes on the HP 3PAR StoreServ Storage by using the lsdev command. Example 68 Using the lsdev command # lsdev -Cc disk hdisk0 Available Virtual SCSI Disk Drive hdisk1 Available PAR InServ Virtual Volume hdisk2 Available PAR InServ Virtual Volume hdisk3 Available PAR InServ Virtual Volume hdisk4 Available PAR InServ Virtual Volume hdisk5 Available PAR InServ Virtual Volume hdisk6 Available PAR InServ Virtual Volume c. Using the volume group to PVID mapping information collected earlier, import the volume group(s) using the vgimport -y vgname pvid command, where pvid is a physical disk on which the volume group is created. For details, see Example 69 Volume group to PVID mapping before removing HDS Storage disks from the system. If a volume group is mapped to multiple physical disks, specify one disk from the list of disks. The importvg command automatically identifies the remaining set of disks that were mapped to the given volume group. 70 Performing Minimally Disruptive Migration Using an AIX Host

71 Example 69 Volume group to PVID mapping before removing HDS Storage disks from the system # lspv hdisk0 00f825bdd5f7e96e rootvg active hdisk1 00f825bd4a05917b None hdisk2 00f825bd5dfc80c6 AIX1VG active hdisk3 00f825bd5dfc82c1 AIX2VG active NOTE: The AIX1VG volume group is mapped to the disk with PVID 00f825bd5dfc80c6, and AIX2VG is mapped to the disk with PVID 00f825bd5dfc82c1. After the rescan of the disks following the zoning of the host to the HP 3PAR StoreServ Storage, the lspv command output will be as follows: # lspv hdisk0 00f825bdd5f7e96e rootvg active hdisk1 00f825bd4a05917b None hdisk7 00f825bd5dfc80c6 None hdisk8 00f825bd5dfc82c1 None Import the volume groups by specifying the corresponding disks with the same PVIDs, as follows: # importvg -y AIX1VG hdisk7 AIX1VG # importvg -y AIX2VG hdisk8 AIX2VG # lspv hdisk0 00f825bdd5f7e96e rootvg active hdisk1 00f825bd4a05917b None hdisk7 00f825bd5dfc80c6 AIX1VG active hdisk8 00f825bd5dfc82c1 AIX2VG active If the applications use HDS Storage LDEVs in raw format, reconfigure them to point to the corresponding HP 3PAR StoreServ Storage volumes that have the same PVID. 4. On the host, use the lspath command to verify that all disks exported from the HP 3PAR StoreServ Storage have the expected number of paths. Example 70 AIX Host with Multiple LUNs # lspath Enabled hdisk0 scsi0 Enabled hdisk1 scsi0 Enabled hdisk2 scsi0 Enabled hdisk3 fscsi0 Enabled hdisk4 fscsi0 Enabled hdisk3 fscsi1 Enabled hdisk4 fscsi1 5. All applications and services can now be restarted and the host may resume normal operations (including first restarting the cluster if applicable). Bringing the AIX Host Back Online 71

72 TIP: The showmigration command status will indicate success when all LDEVs have been migrated successfully. Example 71 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) 72 Performing Minimally Disruptive Migration Using an AIX Host

73 10 Performing Minimally Disruptive Migration Using an HP-UX Host The MDM type can be used when migrating an HP-UX host attached to a source HDS Storage system. The host multipathing solution must be updated to communicate with the destination HP 3PAR StoreServ Storage system, and the host must be shut down briefly during MDM. Host I/O is interrupted only during the time it takes to reconfigure the host. Creating the Data Migration Task To create the data migration task for MDM, follow these steps: 1. From the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype MDM option. Example 72 createmigration command # createmigration -sourceuid srchost "HPDL585-01" -destcpg FC_r5 -destprov thin -migtype MDM -persona HPUX_11_v3 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: NOTE: The createmigration command may take several minutes to complete. TIP: Make a note of the migration ID, as it will be used in commands to track migration progress. 2. Issue the showmigration command to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the createmigration task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). When this status is indicated, continue to the next step. Example 73 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NApreparationcomplete(100%)(-NA-) Updating Host Multipath Software and Unzoning from Source HDS Storage System Perform the following steps on the HP-UX host: 1. If the HDLM software is present, remove it from the host, following HDS documentation instructions. a. Close all applications on the host. b. For a cluster, stop the cluster services, and then stop the cluster. Creating the Data Migration Task 73

74 c. Unmount the application file systems, bring offline any raw devices (if configured), and deactivate any volume groups where Logical Volume Manager is in use. d. Uninstall the HDLM from the host, following HDS documentation instructions. 2. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN (see Figure 14 (page 74)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. Figure 14 HP 3PAR Management Console Host Details 3. Configure the multipath software on the host. For more information about configuring multipath software, see the HP 3PAR HP-UX Implementation Guide. This document is available at the following website: HP Storage Information Library ( 4. Upgrade HBA drivers, if required. For information about supported HBA driver versions, see HP SPOCK: HP SPOCK ( 5. Shut down the host and leave the host offline until the migration is started. 6. Unzone the source HDS Storage system from the host. Starting the Data Migration from the Source HDS Storage System to the Destination HP 3PAR StoreServ Storage System 1. From the HP 3PAR Online Import Utility, issue the startmigration command. 74 Performing Minimally Disruptive Migration Using an HP-UX Host

75 Example 74 startmigration command # startmigration migrationid # SUCCESS: Data transfer started successfully 2. To view the status of the migration, issue the showmigration command. Example 75 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- unpresenting(1%)(-na-) 3. Issue the showmigrationdetails command to verify the volumes being migrated. In the preparation stage, PROGRESS for each volume will be 0% and the TASK_ID will be unknown. Example 76 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. Example 77 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % TIP: The STATUS column in the showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 78 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Bringing the HP-UX Host Back Online To bring the HP-UX host back online, follow these steps: Bringing the HP-UX Host Back Online 75

76 1. Verify that the import has started and confirm that a TASK_ID is available for each volume by issuing the showmigrationdetails command. Example 79 Unsafe to bring the host online # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% 2. After the import has started for the volumes, bring back online the HP-UX server host or HP-UX Serviceguard cluster hosts that were shut down. NOTE: For an HP-UX server host that is booting over SAN from the source system, the HBA BIOS must be reconfigured during host startup to select the HP 3PAR boot device. If this is not done, the host will not start up. Example 80 Safe to bring the host online: # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % 3. After all the HP-UX cluster nodes come online, run the HP-UX Serviceguard cluster. 4. Use the ioscan -fnc disk command to verify the status of the migrated disks. All migrated disks should be in the CLAIMED state. 5. All applications and services can now be restarted and the host may resume normal operations (including first restarting the cluster if applicable). TIP: The showmigration command status will indicate success when all LDEVs have been migrated successfully. Example 81 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) 76 Performing Minimally Disruptive Migration Using an HP-UX Host

77 11 Performing Offline Data Migration Creating the Data Migration Task To create the data migration task, follow these steps: 1. Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype offline option. The command performs the following checks before creating the migration: Example 82 createmigration command # createmigration -sourceuid srcvolmap [{"03:A4"}] -destcpg FC_r5 -destprov full -migtype offline # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: NOTE: The createmigration command may take several minutes to complete. TIP: Make a note of the migration ID, as it will be used in commands to track migration progress. 2. Issue the showmigration command to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). Example 83 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS (PROGRESS)(MESSAGE) Offline USP_V par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NApreparationcomplete(100%)(-NA-) NOTE: Unlike during MDM, HP 3PAR Online Import for HDS Storage will not create the host definition on the HP 3PAR StoreServ Storage during an offline migration. The storage administrator must do this manually, during the post-migration steps for offline migrations. See Performing Post-Migration Tasks Specifically for Offline Migration (page 79). Zoning the Host to the Destination HP 3PAR StoreServ Storage System Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN. Shutting Down the Host Modify the startup scripts of all applications using the LUNs that will be migrated, to prevent them from starting at the next reboot. Shut down the host to continue offline migration. Creating the Data Migration Task 77

78 Starting the Data Migration from Source HDS Storage System to Destination HP 3PAR StoreServ Storage System To start the migration from the source Storage system to the destination HP 3PAR Storage system, follow these steps: 1. From the HP 3PAR Online Import Utility, issue the startmigration command. Example 84 startmigration command # startmigration migrationid # SUCCESS: Data transfer started successfully NOTE: The -migrationid (in the example above, ) will have been assigned by the createmigration command. 2. To view the status of the migration, issue the showmigration command. Example 85 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) Offline USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- unpresenting(1%)(-na-) 3. Issue the showmigrationdetails command to verify the volumes being migrated. In the preparation stage, PROGRESS for each volume will be 0% and the TASK_ID will be unknown. Example 86 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_00 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. Example 87 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ % 78 Performing Offline Data Migration

79 TIP: The showmigration command output will indicate success when all LDEVs have been migrated successfully. Example 88 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) Offline USP_V par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Performing Post-Migration Tasks Specifically for Offline Migration Perform the following tasks after successful completion of the offline migration: 1. Unzone the source HDS Storage system from the host. 2. Power up the host. 3. Configure the native OS multipath software. For additional information, see the following: For Windows: Updating Host Multipath Software and Unzoning from the Source HDS Storage System (page 56) For Linux: Updating Host Multipath Software and Unzoning from Source HDS Storage System (page 62) For AIX: Updating Host Multipath Software and Unzoning from Source HDS Storage System (page 67) For HP-UX: Updating Host Multipath Software and Unzoning from Source HDS Storage System (page 73) 4. Export the LUNs to the host on the HP 3PAR StoreServ Storage system. Using the HP 3PAR Management Console, perform the following steps: a. Create a host entry on the HP 3PAR StoreServ Storage system (if it does not already exist). b. Set the HP 3PAR host persona/host OS to the appropriate setting before enabling access to the HP 3PAR array. c. Export the migrated LUNs to the newly created host entry. NOTE: For more information about this process, see the HP 3PAR implementation guides for your specific host and the HP 3PAR Host Explorer User Guide. These documents are available at the following website: HP Storage Information Library ( Performing Post-Migration Tasks Specifically for Offline Migration 79

80 12 Performing Common Migration and Post-migration Tasks This chapter describes tasks that can be performed to monitor a migration, as well as common tasks that can be performed after a migration is complete. Viewing Migration Status Using the HP 3PAR Online Import Utility, you can view the status of all migrations, or view the migration status for a selected source storage system, for a selected migration, or for a selected volume. Viewing all Migrations To view all migrations, use the showmigration command from the HP 3PAR Online Import Utility. Viewing Migrations for a Selected Source Storage System To view all migrations for a selected source HDS Storage system, use the showmigration command with the -source option from the HP 3PAR Online Import Utility. All migrations for the storage system are displayed. Viewing a Selected Migration To view a selected migration, use the showmigration command with the -migrationid option from the HP 3PAR Online Import Utility. Viewing Selected Migration Progress by LDEV To view details for a selected migration by source storage system volume, use the showmigrationdetails command with the -migrationid option from the HP 3PAR Online Import Utility. Aborting a Migration A migration can be aborted before it has started by using the removemigration command from the HP 3PAR Online Import Utility. Once a migration has started, it cannot be aborted. To completely remove a migration, the removemigration command must be issued a second time. See removemigration (page 97). Performing Subsequent Migrations The source HDS Storage system and destination HP 3PAR StoreServ Storage system that have been defined using the HP 3PAR Online Import Utility addsource/adddestination commands, can remain defined for subsequent migrations. You only need to run the HP 3PAR Online Import Utility addsource and adddestination commands if a subsequent migration will be using a new source or destination storage system. 80 Performing Common Migration and Post-migration Tasks

81 13 Troubleshooting This section describes problems you may encounter when using HDS Storage-to-HP 3PAR StoreServ Storage Online Import. NOTE: During the migration process, it is important to remember that the data continues to be served from the source HDS Storage system until the import of each volume is complete. If host errors occur, both the destination HP 3PAR StoreServ Storage system and the source HDS Storage system should be checked for potential problems. HP 3PAR Online Import Utility Error Messages Table 15 (page 81) describes error messages that can occur with the HP 3PAR Online Import Utility. Table 15 Error messages Problem - OIUERRSRC0001 = "Unable to connect to the array."; Resolution - OIURSLSRC0001 = "Contact HP Support"; Problem - OIUERRSRC0002 = "Unable to connect to the SVP of the array"; Resolution - OIURSLSRC0002 = "Make sure that the SVP is up and running"; Problem - OIUERRSRC0003 = "Unable to find the array specified"; Resolution - OIURSLSRC0003 = "Make sure the array is already added in CV AE. Otherwise contact support"; Problem - OIUERRSRC0004 = "The array you are trying to add is not supported"; Resolution - OIURSLSRC0004 = "Check the support matrix and make sure that only the supported arrays with supported firmware versions are added"; Problem - OIUERRSRC0005 = "An unexpected error occured when communicating with the array"; Resolution - OIURSLSRC0005 = "Contact HP support. You may check if storage array used is operational."; Problem - OIUERRSRC0212 = "Unable to find the array specified serial number"; Resolution - OIURSLSRC0212 = "Please ensure that UID is specified with addsource command."; Problem OIUERRSRC0213 = Unable to find the array specified serial number"; Resolution - OIURSLSRC0213 = "Please ensure that array type has been entered correctly."; Troubleshooting Resources Understanding the HP 3PAR Online Import Utility Data Migration Process Understanding the migration process and the order of the procedures is helpful when troubleshooting. The diagnostic tool for HDS Storage is the HiCommand Suite; for the HP 3PAR StoreServ Storage, it is the HP 3PAR Online Import Utility management interface. This section HP 3PAR Online Import Utility Error Messages 81

82 provides an overview of the HP 3PAR Online Import Utility CLI commands used and what happens when you use them, from setup to completion of the migration. HP 3PAR Online Import Utility: addsource No change on source or destination storage system Source storage system information added into the HP 3PAR Online Import Utility database HP 3PAR Online Import Utility: adddestination No change on source or destination storage system Destination storage system information added into the HP 3PAR Online Import Utility database HP 3PAR Online Import Utility: createmigration On the source storage system: Two host groups containing HP 3PAR peer ports are created on channel adapters with names in the following format: HCMDxxxx Migrating LDEV(s) get exports to both newly created host groups representing HP 3PAR peer ports. On the destination storage system: One or more hosts are created LUNs are admitted LUNs are presented to the hosts (online migration) HP 3PAR Online Import Utility: startmigration On the source storage system: LUNs are unpresented from the migrating host group. On the destination storage system: LUNs are presented to the hosts (MDM) Import is started Once the migration is completed: After migration has been completed, LUNs are unpresented from the host group, representing HP 3PAR peer ports from the source storage system. HP 3PAR Online Import Utility Server Logs and Output The HP 3PAR Online Import Utility service must be stopped before getting the logs or changing the logging level and restarted afterward. To do this, go to the Windows Computer Manage screen, right-click Service Name, and select Stop/Start. 82 Troubleshooting

83 When an issue occurs, get all the HP 3PAR Online Import Utility server logs and output to assist with troubleshooting. Use the following action and commands to get the logs and output. Go to this file location for the HP 3PAR Online Import Utility logs: C:\Program Files (x86)\hewlett-packard\hp3paroiu\oiutools\tomcat\32-bit\apache-tomcat \logs All versions of the log if it has rolled over Get HP 3PAR Online Import Utility output by issuing these commands: showmigration migrationid xxx showmigrationdetails migrationid xxx showconnection showsource showdestination Increase the HP 3PAR Online Import Utility Server Logging Level Perform the following to set the HP 3PAR Online Import Utility log to the most verbose level: 1. Edit the following file: C:\Program Files (x86)\hewlett-packard\hp3paroiu\oiutools\ tomcat\ 32-bit\apache-tomcat \webapps\oiuweb\ WEB-INF\classes\ applicationconfig.properties 2. Change log4j.rootcategory=info, DebugLogAppender to log4j.rootcategory=all, DebugLogAppender. 3. Restart the HP 3PAR Online Import Utility service so that the logging changes are picked up. Troubleshooting Issues Cannot Add a Source HDS Storage system Problem: The addsource command fails. Possible causes: The HDS Storage system is in a failed stage within the HiCommand Suite. The HiCommand Suite is running an unsupported software version. An invalid source array UID is specified when executing the addsource command. An invalid user and/or password is provided for the HiCommand Suite. An invalid IP address or port (secure/unsecure) is provided for the HiCommand Suite. The HiCommand Suite has client IP address filtering enabled and the HP 3PAR Online Import Utility server is not on the trusted IP address list. Troubleshooting Issues 83

84 The HiCommand Suite is not managing the HDS Storage system. The HP 3PAR Online Import Utility server and the HiCommand Suite do not have network connectivity. The HiCommand Suite and HDS Storage system do not have network connectivity. The HDS Storage system is running an unsupported firmware version. Solution: Check each of the above conditions to identify which may be causing the problem, then resolve it. Cannot Create a Migration Problem: The migration cannot be created. Possible causes: If a LUN ID has been changed through the HDS service processor, the HDS Storage system must be refreshed through the HiCommand Suite manually. If changes to a LUN number have been made using the HDS CLI or HiCommand Suite, a manual refresh is not required. IMPORTANT: If the HDS service processor is open in Modify Mode, then SMI-S calls to the HDS Storage system may fail. The HDS service processor must be kept in View Mode during the migration phase. IMPORTANT: The HDS SMI-S interface does not have a refresh array interface. If any changes in the HDS Storage system have been made through the HDS service processor or the HDS Storage Navigator, then the HDS Storage system must be refreshed through the HiCommand Suite manually. The HiCommand Suite takes approximately 3 minutes to refresh a single HDS Storage system. Duplicate volumes exist. This may occur if a virtual volume with either the same name or with the same WWN exists on the destination storage system. The destination storage system has the same host name with a different WWN. The destination storage system does not have enough capacity. The HiCommand Suite user name/password have changed since source storage system was added. The HiCommand Suite is not managing the HDS Storage system. The HP 3PAR Online Import Utility server and the HDS HiCommand Suite do not have network connectivity. HDS HiCommand Suite and HDS Storage system do not have network connectivity. The LUNs or host provided are not found within the HiCommand Suite. If LUNs or host are found within the HDS service processor, refresh the HiCommand Suite for the storage system. LUNs or host names are case-sensitive. The LUNs are not eligible for migration (a LUN must be Fibre Channel, and cannot be a replication LUN or reserved). The operational state of HDS Storage system does not allow migration. There is no connection between source and destination storage systems. The wrong migration type is used. Solution: Check each of the above conditions to identify which may be causing the problem, then resolve it. 84 Troubleshooting

85 Cannot Log into the HP 3PAR Online Import Utility Problem: When you attempt to log into the HP 3PAR Online Import Utility, the following error occurs: Invalid credentials, Please try with valid credentials See Example 89 HP 3PAR Online Import Utility login error. Example 89 HP 3PAR Online Import Utility login error CLI Version: Enter IPADDRESS: Enter USERNAME: tester Enter PASSWORD: >ERROR: Invalid credentials, Please try with valid credentials Enter IPADDRESS: Solution: When the user in the User group was created, the User must change password at next logon check box was selected by default. Clear the check box, and log in again. The HP 3PAR Online Import Utility Does Not Open in Windows 7 Problem: When using Windows 7, when you double-click the icon to open the HP 3PAR Online Import Utility, or when you right-click the icon and select Run As Administrator, the utility does not open. Workaround: Run a command prompt window and perform the following steps: 1. Change the directory to the location where the HP 3PAR Online Import Utility was installed. The default location is: C:\Program Files (x86)\hewlett-packard\hp3paroiu 2. Change the directory to the CLI subfolder. 3. Run OIUCLI.bat to start the utility. Trailing Spaces in IP Address Return Login Error Problem: When logging into the HP 3PAR Online Import Utility CLI, you receive the following error: ERROR: Error connecting to server using IP XX.XX.XX.XX This error is caused by a trailing space in the IP address. Solution: Re-open the HP 3PAR Online Import Utility CLI and enter the IP address without any spaces at the end. Powering on or Migrating a VMware ESX Virtual Machine Fails after a Successful Migration Problem: Powering on or migrating an ESX virtual machine with a raw device mapping (RDM) may fail. The following error appears: Virtual Disk 'X' is a mapped direct access LUN that is not accessible When you check the VML identifier for an RDM on two or more ESX hosts, you see they are not referring to the same VML ID. Possible causes: This error can occur upon rebooting the ESX host after a successful migration. The VML number generated by ESX changes after the host is rebooted. Solution: Correct the mappings. For more information, see VMware KB article , available at the following website: VMware KB ( Troubleshooting Issues 85

86 VMware Datastore Errors Following a Successful Migration Problem: A datastore is missing, though you can still see the LUN presented to the host. When forcing a LUN that is formatted as VMFS-5 to mount (either with the name or the UUID), you may see errors like the following: # esxcli storage vmfs snapshot mount -l DEV-LUN03 No unresolved VMFS snapshots with volume label 'DEV-LUN03' found. # esxcli storage vmfs snapshot mount -u 4f1d a3d2d2-f46b-14feb5cc149a No unresolved VMFS snapshots with volume UUID '4f1d a3d2d2-f46b-14feb5cc149a' found. In the vmkernel or messages.log file, you may see entries like the following: LVM: 8445: Device naa :1 detected to be a snapshot: LVM: 8445: Device eui :1 detected to be a snapshot: LVM: 8452: queried disk ID: <type 1, len 17, lun 36, devtype 0, scsi 0, h(id) > LVM: 8459: on-disk disk ID: <type 1, len 17, lun 17, devtype 0, scsi 0, h(id) > When force mounting a VMFS datastore, you may experience these symptoms: Other hosts in the same datacenter cannot mount that VMFS datastore from vcenter Server. The Resolve VMFS Volumes automatic task, seen in the task list of the vcenter Client, generates the following error: Error: Cannot change the host configuration. Error Stack Call "HostStorageSystem.ResolveMultipleUnresolvedVmfsVolumes" for object "storagevolume" on vcenter Server "MyVC" failed. where storagevolume is the name of the datastore and MyVC is the name of your vcenter server. Possible causes: In VMware/ESXi environments, upon the next ESX host reboot after a successful online migration, the ESX host might not mount the VMFS datastores automatically. To prevent duplicate copies of the same datastore being mounted in various replication scenarios, the ESX operating system might declare the migrated datastore as a snapshot and not mount it automatically. Solution: After confirming that the original copy of datastore is no longer accessible by the ESX host, see the VMware KB article for available methods (vsphere client GUI or the esxcli command line) for mounting the datastore. Once the datastores are persistently mounted with an existing signature, or a re-signature is performed, the datastores are automatically mounted during subsequent reboots. If the re-signature method is used, additional steps might be required for updating references to the original signature in virtual machine files. For more information, see the following website: VMware KB ( The adddestination Command Returns Error OIUERRDST0004 Problem: When you issue the HP 3PAR Online Import Utility adddestination command, error OIUERRDST0004 is displayed. See Figure 15 (page 87) Cause: Error OIUERRDST0004 occurs when the HP 3PAR Online Import Utility detects a destination HP 3PAR storage system with firmware version earlier than the minimum. The following figure shows a successful and an unsuccessful execution of the addsource operation. The failure occurs because the HP 3PAR OS version is not supported. 86 Troubleshooting

87 Figure 15 adddestination and error OIUERRDST0004 Solution: Upgrade the HP 3PAR storage system to a supported version. See HP SPOCK for the minimum supported version: HP SPOCK ( The addsource Command for HDS Storage Fails Problem: Issuing the addsource command for an HDS Storage system fails (see Example 90 HP 3PAR CLI: addsource command output ), and the following error message displays: SMI-S Storage Provider Authorization error. Example 90 HP 3PAR CLI: addsource command output Solution: Verify that the HiCommand Suite SMI-S ports (5988 for http; 5989 for https) are open, and then start the HiCommand Suite on these ports. The createmigration Command Fails for Migrated LUNs in a Host Group with No Host Problem: When you issue the createmigration for LUNs in a host group that has no host, the command fails. Cause: LUNs in a host group without a host cannot be migrated. Solution: For LUNs that do not have an associated host, you must use the offline migration type. Troubleshooting Issues 87

88 The createmigration Command Fails for LUN Name or Host Name Containing Special Characters Problem: The HP 3PAR Online Import Utility does not support special characters in the host name and will return an error on the createmigration command if special characters are present in the names. Solution: To continue migration, change the unsupported host name. NOTE: The allowable characters are as follows: letters numerals. (period) - (hyphen) _ (underscore) No other special characters are allowed. The createmigration Command Returns Error OIUERRAPP0000 or OIURSLAPP0000 Problem: Issuing the HP 3PAR Online Import Utility createmigration command yields either of the following error messages: ERROR: OIUERRAPP0000 An unexpected error occurred. OIURSLAPP0000 Contact HP support. You may try restarting the application service. Possible cause: The host group containing LUNs identified for migration contains a replication LUN. Solution: Remove the replication LUN from the host group. The createmigration Command Returns Error OIUERRDB1006 Problem: When you issue the HP 3PAR Online Import Utility createmigration command, the following error message is displayed: ERROR: OIUERRDB1006 Database constraint violated Possible cause: The host specified does not have any associated LUNs in its host group. Solution: Add the LUNs to be migrated into the host group. The createmigration Returns Error OIUERRPREP1014 Problem: When you issue the HP 3PAR Online Import Utility createmigration command, the following error message is displayed: preparationfailed(-na-)(oiuerrprep1014: Error creating host on destination) Possible cause: The host already exists on the destination HP 3PAR StoreServ Storage system with a different WWN. Solution: If this is the same host, but is using a different WWN: On initial migration of a host, include all the WWNs in the host group, even if the WWN is not managing any LUNs. Subsequent migration of any WWN for this host will find a match. If this is a different host, change the host name so that it does not match the existing host name on the destination HP 3PAR StoreServ Storage system. 88 Troubleshooting

89 The createmigration Command Returns Error OIUERRCS1002 Problem: This error occurs when the HP 3PAR Online Import Utility tries to verify a one-to-one zoning between peer ports and source host ports, and there was no one-to-one mapping. See Example 91 createmigration command and error OIUERRCS1002. Example 91 createmigration command and error OIUERRCS1002 # createmigration -sourceuid srchost R123-S02 -destcpg FC_r5 -destprov full -migtype MDM -persona RHEL_5_6 # ERROR: OIUERRCS1002 There is no one-to-one mapping between the peer ports and the source host ports. OIURSLCS1002 Ensure that there is a one-to-one mapping between the peer ports and the source host ports, and that network connectivity between the host, source array and destination array is proper. Solution: Make sure that the source port on the fabric has been zoned with one peer port. The createmigration Command with -srcvolmap Returns Error OIUERRAPP0000 Problem: When you issue the createmigration command with -srcvolmap, error OIUERRAPP0000 is displayed. See Example 92 createmigration command with srcvolmap and error OIUERRAPP0000. Example 92 createmigration command with srcvolmap and error OIUERRAPP0000 # createmigration -sourceuid srcvolmap [{"temp_1", thin, "FC_r6"}] -migtype MDM -persona RHEL_5_6 # ERROR: OIUERRAPP0000 An unexpected error occured. OIURSLAPP0000 Contact HP support. You may try restarting the application service. Possible cause: This error can occur when the source array host group contains multiple volumes but only one of the volumes is specified in the -srcvolmap parameter. In this situation, the default -destprov and -destcpg parameters must also be included in the createmigration command. Without them, the migration behavior for the volumes not specified in the -srcvolmap parameter is not known. Solution: The createmigration command should be similar to Example 93 Successful createmigration command with -srcvolmap. Example 93 Successful createmigration command with -srcvolmap # createmigration -sourceuid srcvolmap [{"temp_1"}] -migtype MDM -persona RHEL_5_6 -destcpg "FC_r6" -destprov thin # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: The showmigration Command Returns Error OIUERRDST0008 Problem: After a createmigration command is issued with a LUN of size less than 256 MB, the following message occurs following a showmigration command: "OIUERRDST0008: Admit has failed..." Troubleshooting Issues 89

90 Solution: Increase the size of the source LUN on the HDS Storage array to a minimum of 256 MB, and then retry the createmigration command. The showtarget Command Does Not Return HDS Storage Details Problem: Issuing the showtarget command does not return HDS Storage details. Solution: Issue the showportdev ns <n:s:p> command on the HP 3PAR CLI to view the connection details between the HP 3PAR StoreServ Storage peer port and the source HDS array. See Example 94 HP 3PAR Online Import Utility showportdev command output. Example 94 HP 3PAR Online Import Utility showportdev command output The startmigration Command Fails with Host Name That Exceeds 31 Characters Problem: When you migrate a host with a long name, the HP 3PAR Online Import Utility truncates the host name to 31 characters or replaces spaces with underscores in order to complete the createmigration command. However, startmigration will fail with Unable to unpresent a source volume to source host error. Workaround: Before beginning the migration, rename the host so that there are no spaces in the name and the name length does not exceed 31 characters. The startmigration Command Returns Error OIUERRMS10006 Problem: After you issue the startmigration, the following error message is displayed: OIUERRMS10006:Failed to start Data transfer. Failed to find SCSI PGR keys on destination... Possible cause: This error can occur when one or more of the LUNs in the host group being migrated has a persistent reservation. Solution: On the source array, clear the persistent reservation on the LUNs before you attempt to restart the migration. 90 Troubleshooting

91 14 Appendices Appendix A: HP 3PAR Online Import Utility CLI Commands This appendix describes HP 3PAR OS CLI commands that are used with the HP 3PAR Online Import Utility during online import. adddestination Adds a destination system. DESCRIPTION The adddestination command adds a destination storage system to the HP 3PAR Online Import Utility that is intended to be migrated. PARAMETERS Parameter mgmtip user password type name uid port secure Mandatory/Optional Mandatory Mandatory Mandatory Optional Optional Optional Optional Optional Description Management port IP address of the HP 3PAR controller. User name to be used to connect to management application. Plain text password to be used to connect to management application. Storage system family type like 3PAR Name of the storage system. This is required especially when there are multiple storage systems managed under same IP address. Unique number that represents a source in the HP 3PAR Online Import Utility. Port number on which management application accepts request to connect and provide source storage system details. If not supplied, default based on storage system type will be used. True/False. This enables or disables secure channel communication with source storage system, wherever applicable. Default value will be false or default used by source storage system communication layer. EXAMPLES # adddestination -mgmtip user 3pardst -password 3parhelp # SUCCESS: Added destination storage system. addsource DESCRIPTION The addsource command adds a source storage system to the HP 3PAR Online Import Utility that is intended to be migrated. Appendix A: HP 3PAR Online Import Utility CLI Commands 91

92 PARAMETERS Parameter type name uid mgmtip user password port secure Mandatory/Optional Mandatory Optional Mandatory Mandatory Mandatory Mandatory Optional Optional Description Storage system family name: HDS Name of the storage system or serial number or 64 bit hyphenated/non-hyphenated WWN to identify the storage system. This is required especially when multiple storage systems are managed under the same IP address. Serial number of the HDS Storage source array. IP address of the SMI-S provider system that is managing storage system that is being added. User name for HiCommand Suite that is managing storage system that is being added. Password for the user of the HiCommand Suite that is managing the storage system being added. Port number on which management application accepts request to connect and provide source storage system details. Mandatory if secure flag is used to set non-default. SMI-S port defaults are: secure port: 5989 unsecure port: 5988 This enables or disables secure channel communication between the HP Online Import Utility and the HiCommand Suite. Options are: true false The default setting is -secure true. EXAMPLE # addsource -type HDS -mgmtip XX.XX.XX.XX -user admin -password adminpw -uid xxxxx # SUCCESS: Added source storage system. 92 Appendices

93 NOTE: Issuing the addsource -help command displays the following results: # addsource help Command addsource Syntax addsource -type <3PAR> [-name uid <name UID>] -mgmtip <ip address FQDN> user <user name> password <password> [-port <port number>] [-secure <true false>] addsource -help Description Add a source storage system that is intended to be migrated. -port -secure -password -mgmtip -uid -name -user -type : Port number on which management application accepts request to connect & provide source storage system details. If not found default based on storage system type will be used. : True/False. This enables or disables secure channel communication with source storage system, wherever applicable. Default value will be false or default used by source array communication layer. : Plain text password to be used. : IP address of the management station to connect to get details. : 64 bit hyphenated WWN to identify the storage system. This is required especially when there are multiple storage systems managed under same IP address : Friendly name of the storage system. : Username to be used to connect to management application. : Storage system family type. Example: 3PAR. Example addsource -type 3PAR -name 3PAR1 -mgmtip user administrator -password exposedpwd -port secure true For the HP 3PAR Online Import Utility, the valid value for the type parameter is HDS. createmigration DESCRIPTION The createmigration command performs preparation phase of a migration. Actual data transfer will not be triggered by this command. NOTE: NOTE: Can only create one migration at a time per source HDS Storage system. The createmigration command may take several minutes to complete. NOTE: The volume(s) or host specified in the createmigration command are mapped to a host group on the associated source HDS Storage system. All LUNs and all hosts in the mapped host group will be migrated even if only a subset are entered in the createmigration command. Appendix A: HP 3PAR Online Import Utility CLI Commands 93

94 PARAMETERS Parameter sourceuid srcvolmap or volmapfile srchost destprov destcpg cgvolmap allvolumesincg migtype destinationuid Mandatory/Optional Mandatory A combination of commands is mandatory as specified by user for example, if srchost is used, destcpg and destprov should be used. If srcvolmap is there, srchost should not be there. If srcvolmap has CPG and Prov information, then destcpg and destprov need not be specified. If the srcvolmap has mixed Prov information ("thin" and "full") for some volumes, then destprov is mandatory for the rest of the volumes not specified in srcvolmap. Optional Optional Defaults to offline Optional Description Serial number of the HDS Storage source array. Map that provides information about the source volumes for migration. A list of volume names that identifies the volumes should be provided. It can also have mapping of every source volume to required provisioning or destination CPG. srcvolmap[{ source unique name, desired destination provisioning after migration (thin/full/dedupe), desired destination CPG name},{...},...] Sample content of volmapfile: 11:09,thin,cpg1 11:06,full,cpg2 11:06,dedupe,cpg2 Any implicitly defined volumes will get their provisioning type from the value of -destprov, and their CPG from the value of -destcpg. Provisioning and CPG entries in the srcvolmap or volmapfile parameters override the default destcpg and destprov parameters. Name of the host for which all source volumes should be considered for migration. This should not be there if srcvolmap or volmapfile is there. Provisioning type of the volumes that will be created in destination as a result of migration (thin, full, or dedupe). Name of CPG where the migrated volumes will be made available. Migrates a subset of volumes consistently. NOTE: Either the allvolumesicg parameter or the cgvolmap parameter can be present at any given point, but not both. Migrates all volumes specified in srcvolmap consistently. NOTE: Either the allvolumesicg parameter or the cgvolmap parameter can be present at any given point, but not both. Migration type. For the source HDS Storage system, the supported migration type is MDM or offline. UID of the destination storage system. Since only one destination storage 94 Appendices

95 Parameter persona Mandatory/Optional Mandatory for online migration and MDM Description system is allowed, this is an optional parameter, as the destination will be autoselected. Sets the host persona type on the destination storage system. For valid values of this option, see showpersona (page 101). EXAMPLES # createmigration -sourceuid srchost "HPDL585-01" -destcpg FC_r5 -destprov thin -migtype MDM -persona RHEL_5_6 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: # createmigration -sourceuid srcvolmap "[{"00:03:01", thin, testcpg},{"00:03:02", thin, testcpg},{"00:03:03", thin, testcpg}]" -destcpg testcpg -destprov testcpg -cgvolmap{ values":{"cg1":["00:03:01","00:03:02"]}} -persona RHEL_5_6 To create migration with mixed provisioning (for example, with a single to be thinldev to be thin, but others to be fully provisioned), issue the following command: # createmigration -sourceuid srcvolmap [{"00:1A:34", thin, FC_r5}] -destcpg FC_r5 -destprov full -migtype MDM -persona WINDOWS_2008_R2 # SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: help DESCRIPTION Global help command for the HP 3PAR CLI. PARAMETERS None. Abstract The help command displays available HP 3PAR CLI commands together with short descriptions. EXAMPLES # help CLI provides following commands showsource showmigration removemigration showpersona List the source storage systems that are already added to be treated as source for a migration job. It shows empty table if no source storage systems found. -This command displays the list of available migrations -Removes the migration identified by the Migration ID specified. Display all the supported persona for supporting firmware version and os mode Appendix A: HP 3PAR Online Import Utility CLI Commands 95

96 startmigration removesource addsource installcertificate showconnection createmigration removedestination help showdestination adddestination -Start prepared migration OR restart a prepared migration. -Removes already added source storage system & clears all related migrations. -Add a source storage system that is intended to be migrated. -Installs certificate from given server IP -This command displays connection between all the configured source and destination storage systems. source or destination can t be used together. -This will perform preparation phase of a migration. Actual data transfer will not be triggered by this command. This does following for a given set of source volumes while presenting to 3PAR destination storage system. -Removes already added destination storage system & clears all related migrations. -Global Help Command for CLI -List the destination storage systems that are already added to be treated as destination for a migration job. It shows empty table if no destination storage systems found. -Add a destination storage system that is intended to be migrated. showmigrationdetails -This command displays the list of volumes associated with the specified migration and their corresponding status Help on a specific <command> can also be obtained by typing <command> -help" installcertificate Installs certificate from a given server IP. DESCRIPTION The installcertificate command installs certificates from the specified storage system. This command is issued to add the source or destination HP 3PAR StoreServ storage systems in a secure manner. The command fetches and displays certificate details for the specified array. PARAMETERS Parameter mgmtip port force source Mandatory/Optional Mandatory Optional Optional Optional Description IP address of the management station to connect to in order to get details. Port number on which management application accepts a request to connect and provide source storage system details. If not found, the default based on the storage system type will be used. Use this option to skip displaying the certificate details. Use this option to determine whether the certificate is installed for the source array or the destination array. If used, this option requires an argument to decide the type of array. 96 Appendices

97 EXAMPLES # installcertificate mgmtip XX.XX.XX.XX TParCertifacteVO [issuedto=hp 3PAR HP_3PAR , commonname=null, issuedbyorganization=null, issuedtoorganization=null, serialno=null, issedby=hp 3PAR HP_3PAR , fingerprint=89:e5:d0:13:6f:d1:07:80:70:76:5c:fe:5b:65:e5:54:c0:18:21:2f, signaturealgo=sha1withrsa, version=v1,validfrom=08/14/2014, validto=08/11/2024. issuedon=null, expireson=null, validdaterange=true] Do you accept the certificate? Y/YES Y # SUCCESS: Installed certificate successfully. removedestination Removes an added destination storage system. DESCRIPTION The removedestination command removes an already added destination storage system and clears all related migrations. PARAMETERS Parameter uid type Mandatory/Optional Mandatory Optional Description Unique number that represents a destination in the HP 3PAR Peer Motion Utility. Type of destination storage system. EXAMPLE # removedestination uid 2FF70002AC003F8E # SUCCESS: Removed destination storage system. removemigration Removes migration. DESCRIPTION The removemigration command clears completed or aborts prepared migrations. Active/Incomplete migrations cannot be removed. PARAMETERS Parameter migrationid Mandatory/Optional Mandatory Description Number that represents a migration in completed/aborted state. EXAMPLES # removemigration migrationid # SUCCESS: The specified migration is successfully removed. Appendix A: HP 3PAR Online Import Utility CLI Commands 97

98 removesource DESCRIPTION The removesource command removes already added source storage systems. Sources cannot be removed if there is an active migration. PARAMETERS Parameter uid type Mandatory/Optional Mandatory Mandatory Description Serial number of the HDS Storage source array. Type of storage system: HDS EXAMPLE # removesource uid type HDS showconnection DESCRIPTION By default, the showconnection command shows a map of all connected source and destination storage systems. There should be 1:1 mapping between source and destination storage systems for peer port FC connection. Given a source storage system, this shows all the configured destination storage systems it can see and vice versa. However, the parameters, source and destination cannot be used together. PARAMETERS Parameter source destination Mandatory/Optional Optional Optional Description Serial number of the HDS Storage source array. In accordance with HP 3PAR Online Import Utility documentation. EXAMPLE # showconnection -source SOURCE_NAME SOURCE_UNIQUE_ID DESTINATION_NAME DESTINATION_UNIQUE_ID DESTINATION_PEER_PORT SOURCE_HOST_PORT USP_V PAR_Array_1 2FF70002DY005F DY00-5F92(0:2:4) E E62(CL7-C) USP_V PAR_Array_1 2FF70002DY005F DY00-5F92(0:2:4) E E72(CL8-C) 98 Appendices

99 showdestination Description The showdestination command lists the storage systems that are already added to the HP 3PAR Online Import Utility to be treated as destination of migration job. It shows an empty table if no destination storage systems are found. PARAMETERS Parameter name type csvtable filewrite all showcols unique_id peer_ports listcols firmware management_server operational_state Mandatory/optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Description Name of the storage system. This is storage system family name (e.g. 3PAR). This command can be used to print delimited output. Redirects the output of the command to a file. Display all details with headings. Any argument that follows showcols depicts field to display (columns). Accepts a comma separated list of column names. Serial number of the destination HDS Storage system. List of host ports hyphenated 64 bit WWN (N:S:P). Peer will be marked as peer. Displays the list of column names applicable to that command. Firmware version. The IP address/fqdn of the management server that manages this storage system. Operational state of the storage system (Good, Failed, Attention). EXAMPLE # showdestination NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE PEER_PORTS DMMT3PAR02 3PAR 2FF70002AC003F9C Normal AC00-3F9C(2:1:1) AC00-3F9C(3:1:1) showmigration Lists migrations. Appendix A: HP 3PAR Online Import Utility CLI Commands 99

100 DESCRIPTION The showmigration command lists active migrations in preparation or data transfer phase as well as the ones that are successful or aborted. By default all migrations are listed. The status of a migration will show the current state as well as the progress percentage whenever applicable and failure reason whenever applicable PARAMETERS Parameter type status migrationid csvtable filewrite all showcols listcols sourcename destinationname Mandatory/optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Description MDM/Offline. Display all migrations that are of the type specified. Displays migrations that are in the specified state. Unique number that identifies a migration after createmigration is complete. If this is specified, there is no need to provide source and destination details. This command can be used to print delimited output. Redirects the output of the command to a file. Displays all details with headings. Any argument that follows showcols depicts field to display (columns). Accepts a comma separated list of column names. Display the list of column names applicable to that command. Source storage system name. Displays migrations created between this source and destination storage systems connected to it. Destination storage system name. Displays migrations created between this destination and source storage systems connected to it. EXAMPLE # showmigration MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) offline USP_V DMMT3PAR02 Sat Apr 12 00:52:38 IST NA- preparationcomplete(100%)(-na-) 100 Appendices

101 showmigrationdetails Shows details of a specific migration. DESCRIPTION Use the showmigrationdetails command to view details at volume level for a specific migration. Task ID is the corresponding HP 3PAR task ID, if found. Status at individual volume levels is on similar lines as the status of migration. PARAMETERS Name migrationid csvtable filewrite all showcols listcols taskid sourcevolume destinationvolume Mandatory/optional Mandatory Optional Optional Optional Optional Optional Optional Optional Optional Description Unique ID that gets generated after the createmigration operation. Displays the migration corresponding to the ID specified. This command can be used to print delimited output. Redirects the output of the command to a file. Displays all details with headings. Any argument that follows showcols depicts field to display (columns). Accepts a comma separated list of column names. Displays the list of column names applicable to that command. Integer number for the ID of the import task being performed on the destination HP 3PAR StoreServ Storage. Source volume name. Displays information corresponding to this volume. Destination volume name. Displays information corresponding to this volume. EXAMPLE # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS 00:07:00 00_07_ Completed showpersona DESCRIPTION This command displays the supported destination HP 3PAR host entry persona values for all the specified host operating systems. Appendix A: HP 3PAR Online Import Utility CLI Commands 101

102 PARAMETERS Table 16 Host Persona HOSTYPE windows2012 sunsolaris sunsolaris ibmaix hpux windows2008 vmware linux linux openvms mswindows windows2012 sunsolaris sunsolaris ibmaix hpux hpux windows2008 vmware linux linux openvms mswindows OSVERSION HOSTPERSONA WINDOWS_2012 SOLARIS_9_10 SOLARIS_11 AIX HPUX WINDOWS_2008_R2 ESX_4_5 RHEL SUSE OPENVMS WINDOWS_2003 WINDOWS_2012_R2 SOLARIS_9_10 SOLARIS_11 AIX HPUX_11_v1_v2 HPUX_11_v3 WINDOWS_2008_R2 ESX_4_5 RHEL_5_6 SUSE10_11 OPENVMS WINDOWS_2003 EXAMPLE NOTE: Issue the showpersona command to see the list of host persona values: # showpersona HOSTTYPE OSVERSION HOSTPERSONA windows WINDOWS_2012 sunsolaris SOLARIS_9_10 sunsolaris SOLARIS_11 ibmaix AIX hpux HPUX windows WINDOWS_2008_R2 102 Appendices

103 vmware ESX_4_5 linux RHEL linux SUSE openvms OPENVMS mswindows WINDOWS_2003 windows WINDOWS_2012_R2 sunsolaris SOLARIS_9_10 sunsolaris SOLARIS_11 ibmaix AIX hpux HPUX_11_v1_v2 hpux HPUX_v3 windows WINDWS_2008_R2 vmware ESX_4_5 linux RHEL_5_6 linux SUSE_10_11 openvms OPENVMS mswindows WINDOWS_2003 showsource DESCRIPTION The showsource command lists the source storage systems that are already added to the CLI utility to be treated as source for a migration job. PARAMETERS Parameter name type unique_id firmware management_server operational_state Mandatory/Optional Optional Optional Optional Optional Optional Optional Description Storage system family and serial number. Example: USP_V Storage system family name: HDS Storage system serial number. Firmware version of the source storage system. IP address of the HiCommand Suite that is managing storage systems. Operational state of the storage system. Appendix A: HP 3PAR Online Import Utility CLI Commands 103

104 EXAMPLE # showsource type HDS NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE USP_V HDS XX.XX.XX.XX Good startmigration Starts the data transfer of a migration. DESCRIPTION The startmigration command starts or restarts a prepared migration to go through data transfer phase of migration. The data from source volumes is moved to destination volume over the peer ports. At the source storage system, the presentation of the source volume to the source host will be removed. The host representing the destination storage system that was created during the migration preparation stage will remain at the source storage system. For another migration, this host will be reused. When you are finished with all the migration related to the host, you may choose to delete this host. PARAMETERS Parameter migrationid Mandatory/Optional Mandatory Description Unique number representing the migration that is in prepared or incomplete state. EXAMPLE # startmigration migrationid SUCCESS: Data transfer started successfully. 104 Appendices

105 Appendix B: Identifying and Deleting Source Array LUN Paths Use this procedure to identify and delete source array LUN paths during online migration. In this example, LUN paths on an HDS Storage array are identified and deleted. Identifying and deleting source array LUN paths with Linux native device-mapper multipath 1. After the create migration task is completed successfully, rescan the HBAs and issue the multipath -ll command: # ls /sys/class/fc_host host4 host5 # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "1" > /sys/class/fc_host/host5/issue_lip # echo "- - -" > /sys/class/scsi_host/host4/scan # echo "- - -" > /sys/class/scsi_host/host5/scan # multipath -ll mpathd (360060e80045be be ) dm-5 HITACHI,OPEN-V size=14g features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active - 5:0:1:2 sde 8:64 active ready running - 4:0:2:2 sdg 8:96 active ready running - 5:0:0:2 sdp 8:240 active ready running `- 4:0:0:2 sdl 8:176 active ready running mpathc (360060e80045be be ) dm-3 HITACHI,OPEN-V size=244g features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active - 5:0:1:1 sdd 8:48 active ready running - 4:0:2:1 sdf 8:80 active ready running - 5:0:0:1 sdo 8:224 active ready running `- 4:0:0:1 sdk 8:160 active ready running 2. In the output, identify the LUN and its WWN. For example, assume that the LUN with WWN e80045be be is being migrated. The LUN with WWN e80045be be has four paths: sde, sdg, sdp, and sdl. a. To identify the paths that pertain to the source array model, issue the following command on each associated path: # cat /sys/block/sde/device/model OPEN-E # cat /sys/block/sdg/device/model OPEN-E OPEN-E # cat /sys/block/sdp/device/model VV # cat /sys/block/sdl/device/model VV Paths sde and sdg belong to the HDS Storage array. b. Issue the following command for each identified source path to delete it from the operating system: # echo "1">/sys/block/sde/device/delete # echo "1">/sys/block/sdg/device/delete 3. When more than one LUN is being migrated, repeat step 2 for each LUN. 4. Repeat steps 1 3 for all the nodes in the cluster. Identifying and deleting source array LUN paths with HP-UX 11 v3 1. After the create migration task is completed successfully, issue the following command: Appendix B: Identifying and Deleting Source Array LUN Paths 105

106 # ioscan -m lun disk /0xfa00/0x74 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk30 /dev/rdisk/disk30 disk /0xfa00/0x75 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk300 /dev/rdisk/disk300 disk /0xfa00/0x76 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk369 /dev/rdisk/disk369 disk /0xfa00/0x77 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk370 /dev/rdisk/disk370 The output shows LUNs with their source and destination array paths. 2. Remove the source array from the host zone and issue the following command. The LUN status will indicate limited. # ioscan -m lun disk /0xfa00/0x74 esdisk CLAIMED DEVICE limited HP OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk30 /dev/rdisk/disk30 disk /0xfa00/0x75 esdisk CLAIMED DEVICE limited HP OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk300 /dev/rdisk/disk300 disk /0xfa00/0x76 esdisk CLAIMED DEVICE limited HP OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk369 /dev/rdisk/disk369 disk /0xfa00/0x77 esdisk CLAIMED DEVICE limited HP OPEN-V 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x /0/0/8/0/0/0.0x50060e8005bc1f01.0x /0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk370 /dev/rdisk/disk Make a note of the source array WWNs that use zoning information. This will help identify LUN paths pertaining to the source array. In the example above, source array WWNs are 50060e8005bc1f0c and 50060e8005bc1f Delete the source array paths identified in step 2 by issuing the rmsf command. # rmsf -H 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x # rmsf -H 0/0/0/8/0/0/0.0x50060e8005bc1f01.0x # rmsf -H 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x # rmsf -H 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x # rmsf -H 0/0/0/8/0/0/0.0x50060e8005bc1f01.0x # rmsf -H 0/0/0/7/0/0/0.0x50060e8005bc1f0c.0x When all the source array paths have been deleted, issue the following command. The LUN status will be online. # ioscan -m lun disk /0xfa00/0x74 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk30 /dev/rdisk/disk30 disk /0xfa00/0x75 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk300 /dev/rdisk/disk300 disk /0xfa00/0x76 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/8/0/0/0.0x ac x Appendices

107 0/0/0/7/0/0/0.0x ac x /dev/disk/disk369 /dev/rdisk/disk369 disk /0xfa00/0x77 esdisk CLAIMED DEVICE online HITACHI OPEN-V 0/0/0/8/0/0/0.0x ac x /0/0/7/0/0/0.0x ac x /dev/disk/disk370 /dev/rdisk/disk370 Identifying and deleting source array LUN paths with ESX 5.t 1. After the create migration task is completed successfully, issue the following command to rescan HBAs. In this example, vmhba2 and vmhba3 are the Fibre Channel HBAs: # esxcfg-rescan vmhba3 # esxcfg-rescan vmhba2 The output shows LUNs with their source and destination array paths. 2. Issue the following command to list all LUNs and their corresponding paths: # esxcfg-mpath -b naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc vmhba3:c0:t2:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 50:06:0e:80:05:bc:1f:09 WWPN: 50:06:0e:80:05:bc:1f:09 naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc vmhba3:c0:t2:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 50:06:0e:80:05:bc:1f:09 WWPN: 50:06:0e:80:05:bc:1f:09 naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc vmhba3:c0:t2:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 50:06:0e:80:05:bc:1f:09 WWPN: 50:06:0e:80:05:bc:1f:09 naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc vmhba3:c0:t2:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 50:06:0e:80:05:bc:1f:09 WWPN: 50:06:0e:80:05:bc:1f:09 The output shows LUNs with their source and destination array paths. 3. Remove the source array from the host zone, and issue the following command. The host will show the status of the source path as Target: Unavailable # esxcfg-mpath -b naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc vmhba3:c0:t2:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l2 LUN:2 state:dead fc Adapter: Unavailable Target: Unavailable naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc vmhba3:c0:t2:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l3 LUN:3 state:dead fc Adapter: Unavailable Target: Unavailable naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc Appendix B: Identifying and Deleting Source Array LUN Paths 107

108 vmhba3:c0:t2:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l0 LUN:0 state:dead fc Adapter: Unavailable Target: Unavailable naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc vmhba3:c0:t2:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 50:06:0e:80:05:bc:1f:21 WWPN: 50:06:0e:80:05:bc:1f:21 vmhba2:c0:t0:l1 LUN:1 state:dead fc Adapter: Unavailable Target: Unavailable 4. Rescan the HBAs. In this example, the Fibre Channel HBAs are vmhba2 and vmhba3. # esxcfg0rescan vnba3 # esxcfg0rescan vnba2 5. Verify the LUN paths by issuing the following command: # esxcfg-mpath -b naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l2 LUN:2 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l3 LUN:3 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l0 LUN:0 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc naa.60060e8005bc1f000000bc1f : HP Fibre Channel Disk (naa.60060e8005bc1f000000bc1f ) vmhba3:c0:t3:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7f WWPN: 10:00:00:00:c9:71:bc:7f Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 20:22:00:02:ac:00:1a:bc vmhba2:c0:t3:l1 LUN:1 state:active fc Adapter: WWNN: 20:00:00:00:c9:71:bc:7e WWPN: 10:00:00:00:c9:71:bc:7e Target: WWNN: 2f:f7:00:02:ac:00:1a:bc WWPN: 21:22:00:02:ac:00:1a:bc 108 Appendices

109 Appendix C: Rolling Back to the Original Source Array This appendix provides guidelines for rolling back data migration in the event that I/O must resume on the original array. HP recommends that, before implementing any migration on live or production data, you include and test a migration fail-back policy as part of your premigration strategy. Typical considerations include: What if migration fails? What will your process be to roll back to the original array? What needs to be done to facilitate the rollback? Thoroughly understanding and documenting the rollback process can help ensure that, if you need to revert to your original storage configuration, downtime is nonexistent or minimal. The steps you take will vary, depending on the specific hardware and software configurations involved in your migration. Figure 16 (page 110) shows a general overview of the rollback process for a failed online migration. Appendix C: Rolling Back to the Original Source Array 109

110 Figure 16 Rollback process for a failed online migration *See Appendix D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later (page 112). Figure 17 (page 111) shows a general overview of the rollback process for a failed MDM. 110 Appendices

111 Figure 17 Rollback process for a failed MDM *See Appendix D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later (page 112). Appendix C: Rolling Back to the Original Source Array 111

112 Appendix D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later As part of startmigration command, the HP 3PAR StoreServ Storage applies a SCSI-3 reservation on source volumes. After a successful migration, the reservation is automatically removed by HP 3PAR Peer Motion. If a migration fails, use this procedure to clear the SCSI reservation in order to return to the original source volumes. NOTE: Clear the SCSI reservation only if you plan to return to the original source volumes, as described in Appendix C: Rolling Back to the Original Source Array (page 109). After the SCSI reservation is cleared on these volumes, the startmigration command should not be re-issued on these volumes unless you start the migration over again. To clear the reservation, follow these steps: 1. Connect to the HP 3PAR StoreServ Storage: a. Log into the HP 3PAR CLI. b. Enter the IP address of the HP 3PAR StoreServ Storage, your user name, and your password 2. Issue the showvv command to find the name of the volume for which a reservation must be removed. Example 95 showvv command # showvv Id Name Prov Type CopyOf BsId Rd -Detailed_State- Adm Snp Usr VSize 0 admin full base RW normal vol0 peer base RW exclusive vol1 peer base RW exclusive vol2 peer base RW exclusive total Identify the name of virtual volume for which the reservation must be removed. The Prov (provisioning) value will be peer and the Detailed_State value will be exclusive. 3. Using the HP 3PAR CLI, clear the reservation on the virtual volume by issuing the setvv -clrrsv <virtual volume name> command. # setvv -clrrsv vol0 Following successful execution of the setvv command, the reservation on the virtual volume will be cleared. 4. After the reservation is cleared, delete the volumes on the HP 3PAR StoreServ Storage. NOTE: Repeat this procedure for each virtual volume that has a SCSI reservation. Appendix E: Use Case: Data Migration for an Oracle RAC Cluster This use case describes data migration with the HP 3PAR Online Import Utility for an Oracle RAC cluster configured with the cluster registry (CRS), voting disks, and data disks distributed across multiple arrays on the same source HDS Storage system. Oracle supports increases to database capacity by adding more arrays. The key restriction is that if ASM is enabled, disks in an ASM disk group that are included from different arrays should all have the same performance characteristics and size. Data disks can be distributed across multiple arrays. Because the CRS and voting disks are used for cluster configuration and integrity, not for storage integrity or availability, they do not have to be configured on every array. 112 Appendices

113 Data migration using the HP 3PAR Online Import Utility for Oracle RAC clusters has been validated, and is documented here for two specific configuration scenarios, which cover all ASM-based Oracle RAC deployments: Oracle Database deployments before 11gR2, with the CRS and voting disks residing outside the ASM, and data disks included in the ASM disk group Oracle Database 11gR2 deployments with the CRS, voting disks, and data disks included in the ASM disk group Because the HP 3PAR Online Import Utility can be used to migrate data from a single source array at a time, and because, for an Oracle RAC migration, all volumes must be included in a consistency group, the number of migrations made by the HP 3PAR Online Import Utility for an Oracle RAC configuration distributed across multiple source arrays is equal to the number of source arrays deployed. For example, if the Oracle RAC database is distributed across three arrays (with the CRS and voting disks configured on one of them), then three migrations must be performed with the HP 3PAR Online Import Utility, one for each array. The order in which the migrations are executed by the HP 3PAR Online Import Utility does not matter. For this use case, the following sequences were verified: Completely migrating the source array disks with the CRS and voting disks, before migrating the source arrays with the data disks Completely migrating a source array with the data disks, before migrating the source array with the CRS and voting disks IMPORTANT: All of these migrations are performed using the online migration procedure, as described in this guide. During the migration, there will be instances when the Oracle RAC will be distributed across, and the CRS, voting, and data disks will coexist on, the deployed source arrays and the destination HP 3PAR StoreServ Storage. This coexistence is currently supported across the HP 3PAR StoreServ Storage and the HDS arrays listed in HP SPOCK: HP SPOCK ( Appendix E: Use Case: Data Migration for an Oracle RAC Cluster 113

114 Figure 18 Oracle RAC data migration from multiple arrays Figure 18 (page 114) shows two source arrays one with CRS, voting, and data disks, and the other with data disks only. The objective is to migrate the disks online from the two source arrays to a single destination HP 3PAR StoreServ Storage array, using the HP 3PAR Online Import Utility. This will be done in two serially implemented phases. Configuration details: The deployment uses Oracle Database 11gR2 RAC, with ASM enabled and the CRS, voting disk, and data disks on both source arrays included in the ASM. Implementation would not be affected even if the CRS and voting disks are excluded from the ASM, as is required by Oracle Database implementations with releases earlier than 11gR2). Node 1 and node 2 are RHEL 6.4 servers There are two source arrays: source array 1 and source array 2 NOTE: More than two nodes in a cluster and/or more than two source arrays is also supported for this implementation. Because, in this example, there are two source arrays, there are two phases or two HP 3PAR Online Import Utility migrations that must be deployed for a complete migration: Migration 1: The CRS, voting disks, and data disks are migrated from source array 1 to the destination HP 3PAR StoreServ Storage Migration 2: Data disks from source array 2 are migrated to the destination HP 3PAR StoreServ Storage NOTE: The order does not matter migration 1 and migration 2 can be reversed. 114 Appendices

115 Migration steps The steps shown here are high-level and typical. For details, see the referenced sections of this guide. Migration 1: Source array 1 to HP 3PAR StoreServ Storage 1. Follow the premigration steps for the source array and the HP 3PAR StoreServ Storage as detailed in Premigration Steps (page 36). Premigration steps for an online migration include: a. Zoning source array 1 to the destination HP 3PAR StoreServ Storage b. Identifying source array 1 and the destination HP 3PAR StoreServ Storage using the HP 3PAR Online Import Utility 2. Follow the online migration procedure described Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3 (page 44). Typical steps include: a. Zoning the Oracle RHEL nodes to the destination HP 3PAR StoreServ Storage. b. Configuring the RHEL native device-mapper multipath on all nodes. c. Issuing the createmigration command with the migtype online parameter and using the allvolumesincg parameter on source array 1. All volumes, including the CRS, voting disks, and data disks will be presented and exported to the HP 3PAR StoreServ Storage together as one volume set. d. Making a note of the migration task ID, and issuing the showmigration command to verify that the data migration task preparation has completed successfully. e. Issuing the showmigrationdetails command to verify the volumes being migrated. f. Updating the path configuration on the host by rescanning all HBAs and issuing the multipath -ll command to verify the newly discovered paths. g. Deleting the LUN paths from source array 1 and verifying that the multipath ll command shows only the newly discovered or destination HP 3PAR paths. h. Unzoning the Oracle RAC nodes from source array 1. i. Starting the migration by using the HP 3PAR Online Import Utility startmigration command j. Issuing the showmigration command against the migration task ID (generated by issuing the createmigration command) to verify that the data migration task preparation has completed successfully. 3. At this stage, although the CRS, voting and the data disks that were on the source array have been completely migrated to the HP 3PAR StoreServ Storage, and there are data disks present on the source array, the Oracle database and services should continue to be ONLINE and accessible. This can be verified by running the following Oracle based command on the primary RHEL node: # $GRID_HOME/bin/crs_stat t 4. Execute the post-migration steps for migration 1 by performing the following (optional) steps: a. Remove the migration definition when the migration has completed by issuing the removemigration command against the migration task ID (generated by the createmigration, above). b. When all migrations are complete, physically remove source array 1. c. When all migrations are complete, remove source array 1 from the HP 3PAR Online Import Utility, using the removesource command. d. Reconfigure peer ports to host ports on the HP 3PAR StoreServ Storage. Appendix E: Use Case: Data Migration for an Oracle RAC Cluster 115

116 Migration 2: Source array 2 to HP 3PAR StoreServ Storage 5. Follow the premigration steps for the source array and the HP 3PAR StoreServ Storage as detailed in Premigration Steps (page 36). Typical premigration steps for an online migration include: a. Zoning source array 2 to the destination HP 3PAR StoreServ Storage. b. Identifying source array 2 and the destination HP 3PAR StoreServ Storage using the HP 3PAR Online Import Utility. 6. Follow the online migration procedure described in Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3 (page 44). Typical steps include: a. Zoning the Oracle RHEL nodes to the destination HP 3PAR StoreServ Storage. b. Configuring the RHEL native device-mapper multipath on all nodes. c. Issuing the createmigration command with the migtype online parameter with the allvolumesincg parameter on source array 2. All volumes, including the CRS, voting disks, and data disks will be presented and exported to the HP 3PAR StoreServ Storage together as one volume set. NOTE: If a single data disk, rather than multiple data disks, is present on source array 2, the allvolumesincg parameter should not be issued. The disk should be treated like a single volume as opposed to a consistency group-based volume set. d. Making a note of the migration task ID, and issuing the showmigration command to verify that the data migration task preparation has completed successfully. e. Issuing the showmigrationdetails command to verify the volumes being migrated. f. Updating the path configuration on the host by rescanning all HBAs and issuing the multipath -ll command to verify the newly discovered paths. g. Deleting the LUN paths from the source array and verifying that the multipath ll command only shows the newly or destination 3PAR paths. h. Unzoning the Oracle RAC nodes from source array 2. i. Starting the migration by using the HP 3PAR Online Import Utility startmigration command. j. Issuing the showmigration command against the migration task ID (generated by issuing the createmigration command) to verify that the data migration task preparation has completed successfully. 7. At this point, all the data disks that were on source array 2 have completely migrated to the HP 3PAR StoreServ Storage. The Oracle database and services should continue to be online and accessible. This can be verified by running the following Oracle-based command on the primary RHEL node: # $GRID_HOME/bin/crs_stat t 8. Follow post-migration steps for migration 2 (see Performing Common Migration and Post-migration Tasks (page 80)) by performing the following optional steps: a. Remove the migration definition when the migration has completed by issuing the removemigration command against the migration task ID (generated by issuing the createmigration command). b. When all migrations are complete, physically remove source array 2. c. When all migrations are complete, remove source array 2 from the HP 3PAR Online Import Utility, using the removesource command. d. Reconfigure peer ports to host ports on the HP 3PAR StoreServ Storage This completes the Oracle RAC migration from source array 1 and source array 2 to the destination HP 3PAR StoreServ Storage. 116 Appendices

117 15 Support and Other Resources Contacting HP For worldwide technical support information, see the HP support website: 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 questions Specify the type of support you are requesting: HP 3PAR storage system HP 3PAR StoreServ 7200, 7200c, 7400, 7400c, 7440c, 7450, and 7450c Storage systems HP 3PAR StoreServ Storage systems Support request StoreServ 7000 Storage 3PAR or 3PAR Storage HP 3PAR documentation For information about: Supported hardware and software platforms Locating HP 3PAR documents Customer Self Repair procedures (media) See: The Single Point of Connectivity Knowledge for HP Storage Products (SPOCK) website: SPOCK ( The HP Storage Information Library: Storage Information Library ( By default, HP 3PAR Storage is selected under Products and Solutions. The HP Customer Self Repair Services Media Library: Customer Self Repair Services Media Library ( Under Product category, select Storage. Under Product family, select 3PAR Storage Systems for HP 3PAR E-Class, F-Class, S-Class, and T-Class Storage Systems, or 3PAR StoreServ Storage for HP 3PAR StoreServ and 7000 Storage Systems. HP 3PAR storage system software Storage concepts and terminology Using the HP 3PAR Management Console (GUI) to configure and administer HP 3PAR storage systems Using the HP 3PAR CLI to configure and administer storage systems HP 3PAR StoreServ Storage Concepts Guide HP 3PAR Management Console User's Guide HP 3PAR Command Line Interface Administrator s Manual Contacting HP 117

118 For information about: CLI commands Analyzing system performance Installing and maintaining the Host Explorer agent in order to manage host configuration and connectivity information Creating applications compliant with the Common Information Model (CIM) to manage HP 3PAR storage systems Migrating data from one HP 3PAR storage system to another Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems Using the CLI to configure and manage HP 3PAR Remote Copy Updating HP 3PAR operating systems Identifying storage system components, troubleshooting information, and detailed alert information Installing, configuring, and maintaining the HP 3PAR Policy Server See: HP 3PAR Command Line Interface Reference HP 3PAR System Reporter Software User's Guide HP 3PAR Host Explorer User s Guide HP 3PAR CIM API Programming Reference HP 3PAR-to-3PAR Storage Peer Motion Guide HP 3PAR Secure Service Custodian Configuration Utility Reference HP 3PAR Remote Copy Software User s Guide HP 3PAR Upgrade Pre-Planning Guide HP 3PAR F-Class, T-Class, and StoreServ Storage Troubleshooting Guide HP 3PAR Policy Server Installation and Setup Guide HP 3PAR Policy Server Administration Guide 118 Support and Other Resources

119 For information about: See: Planning for HP 3PAR storage system setup Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems HP 3PAR 7200, 7400, and 7450 storage systems HP 3PAR storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR StoreServ 7450 Storage Site Planning Manual HP 3PAR StoreServ Storage Physical Planning Manual HP 3PAR StoreServ Storage Third-Party Rack Physical Planning Manual Installing and maintaining HP 3PAR 7200, 7400, and 7450 storage systems Installing 7200, 7400, and 7450 storage systems and initializing the Service Processor Maintaining, servicing, and upgrading 7200, 7400, and 7450 storage systems Troubleshooting 7200, 7400, and 7450 storage systems Maintaining the Service Processor HP 3PAR StoreServ 7000 Storage Installation Guide HP 3PAR StoreServ 7450 Storage Installation Guide HP 3PAR StoreServ 7000 Storage SmartStart Software User s Guide HP 3PAR StoreServ 7000 Storage Service Guide HP 3PAR StoreServ 7450 Storage Service Guide HP 3PAR StoreServ 7000 Storage Troubleshooting Guide HP 3PAR StoreServ 7450 Storage Troubleshooting Guide HP 3PAR Service Processor Software User Guide HP 3PAR Service Processor Onsite Customer Care (SPOCC) User's Guide HP 3PAR host application solutions Backing up Oracle databases and using backups for disaster recovery Backing up Exchange databases and using backups for disaster recovery Backing up SQL databases and using backups for disaster recovery Backing up VMware databases and using backups for disaster recovery Installing and using the HP 3PAR VSS (Volume Shadow Copy Service) Provider software for Microsoft Windows Best practices for setting up the Storage Replication Adapter for VMware vcenter Troubleshooting the Storage Replication Adapter for VMware vcenter Site Recovery Manager Installing and using vsphere Storage APIs for Array Integration (VAAI) plug-in software for VMware vsphere HP 3PAR Recovery Manager Software for Oracle User's Guide HP 3PAR Recovery Manager Software for Microsoft Exchange 2007 and 2010 User's Guide HP 3PAR Recovery Manager Software for Microsoft SQL Server User s Guide HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere User's Guide HP 3PAR VSS Provider Software for Microsoft Windows User's Guide HP 3PAR Storage Replication Adapter for VMware vcenter Site Recovery Manager Implementation Guide HP 3PAR Storage Replication Adapter for VMware vcenter Site Recovery Manager Troubleshooting Guide HP 3PAR VAAI Plug-in Software for VMware vsphere User's Guide HP 3PAR documentation 119

120 Typographic conventions Table 17 Document conventions Convention Element Bold text Keys that you press Monospace text File and directory names 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 System output Code <Monospace text in angle brackets> Code variables Commands, their arguments, and argument values 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 in irreversible 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. Required Indicates that a procedure must be followed as directed in order to achieve a functional and supported implementation based on testing at HP. HP 3PAR branding information The server previously referred to as the "InServ" is now referred to as the "HP 3PAR StoreServ Storage system." The operating system previously referred to as the "InForm OS" is now referred to as the "HP 3PAR OS." The user interface previously referred to as the "InForm Management Console (IMC)" is now referred to as the "HP 3PAR Management Console." All products previously referred to as 3PAR products are now referred to as "HP 3PAR" products. 120 Support and Other Resources

121 16 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback Include the document title and part number, version number, or the URL when submitting your feedback. 121

122 Glossary CPG DM FCoE FPVV FQDN HCS HDLM HP SPOCK HP 3PAR Online Import Utility iscsi LDEV MDM MPIO MSFC PVID RHEL SMI-S SVP TDVV TPVV VMFS For additional information about the HP 3PAR operating system, see the HP 3PAR StoreServ Storage Concepts Guide, available at the following website: HP Storage Library ( common provisioning group Device-mapper Fibre Channel over Ethernet fully provisioned deduplicated virtual volume fully qualified domain name Hitachi Command Suite Hitachi Dynamic Link Manager HP Single Point of Connectivity Knowledge. HP 3PAR Online Import Utility for HDS Storage Internet Small Computer System Interface Logical device. HDS Storage term for volume. minimally disruptive migration multipath input/output Microsoft Failover Cluster physical-volume identifier Red Hat Enterprise Linux Storage Management Initiative Specification service processor thinly(dynamically) provisioned deduplicated virtual volume thinly(dynamically) provisioned virtual volume Virtual Machine File System 122 Glossary

123 Index A aborting a migration, 80 adddestination CLI command, 91 adding destination storage system, 38 source storage system, 38 addsource CLI command, 91 B bringing online AIX host, 70 HP-UX host, 76 Linux host, 65 Windows host, 60 C checklist, 13 migration MDM, 11 migration online, 8, 9 post-migration MDM, 12 post-migration online, 9 premigration MDM, 10 premigration offline, 13 premigration online, 8 prerequisite component installation MDM, 10 prerequisite component installation offline, 12 prerequisite component installation online, 8 CLI command showmigration, 69, 75 showmigrationdetails, 70, 76 startmigration, 69, 74 CLI commands, 91 adddestination, 8, 10, 12, 38, 80, 86, 91 adddestination -secure, 38 addsource, 8, 10, 12, 38, 80, 81, 82, 83, 87, 91 createmigration, 9, 13, 31, 42, 56, 62, 77, 87, 88, 89, 93 createmigration -allvolumesincg, 47, 52 createmigration -destcpg, 89 createmigration -destprov, 89 createmigration -migtype online, 47, 52 createmigration -srcvolmap, 89 help, 95 installcertificate, 38, 96 removedestination, 9, 12, 97 removemigration, 80, 97 removesource, 9, 12, 98 showconnection, 83, 98 showdestination, 10, 39, 83, 99 showmigration, 48, 53, 56, 62, 64, 77, 78, 80, 89, 99 showmigration -migrationid, 59, 80 showmigration -source, 80 showmigration migrationid, 83 showmigrationdetails, 59, 60, 64, 65, 101 showmigrationdetails -migrationid, 80, 83 showpersona, 101 showportdev, 37 showsource, 38, 83, 103 showtarget, 90 startmigration, 11, 50, 55, 59, 64, 78, 90, 104 configuration HP SPOCK, 8, 9, 12 configuration rules, 14 configuring MPIO software on the host, 58 considerations when migrating data, 31 controller, 33 conventions text symbols, 120 createmigration CLI command, 67, 73, 93 creating data migration task, 41, 42, 77 D data migration aborting, 80 considerations, 31 explicit, 6 implicit, 6 installation and setup, 14 performing, 56, 62, 67, 73 planning for, 32 preparing for, 31 process, 81 starting, 59 types, 6 viewing, 80 Windows clusters, 39 data migration task creating, 41, 42, 77 destination storage system adding, 38 device manager HCS, 18 license, 18 documentation providing feedback on, 121 E emulation types, 7 errors adddestination command unsupported HP 3PAR OS version, 86 addsource command SMI-S Storage Provider Authorization, 87 createmigration command 123

124 host already exists, 88 migrated LUNs with no host, 87 no associated LUNs in host group, 88 no one-to-one mapping between ports, 89 special characters, 88 unexpected error, 88 createmigration command with -srcvolmap unexpected error, 89 HP 3PAR Online Import Utility, 81 HP 3PAR Online Import Utility does not open, 85 installcertificate command, 38 invalid credentials, 85 OIUERRAPP0000, 88, 89 OIUERRCS1002, 89 OIUERRDB1006, 88 OIUERRDST0004, 86 OIUERRDST0008, 89 OIUERRDST0010, 38 OIUERRMS10006, 90 OIUERRPREP1014, 88 OIUERRSRC0001, 81 OIUERRSRC0002, 81 OIUERRSRC0003, 81 OIUERRSRC0004, 81 OIUERRSRC0005, 81 OIUERRSRC0212, 81 OIURSLAPP0000, 88 showmigration command for LUN smaller than 256 MB, 89 showtarget command does not return HDS Storage details, 90 startmigration command failed to start data transfer, 90 host name exceeds 31 characters, 90 trailing spaces in IP address, 85 H HCS installing, 14 HCS Device Manager, 18 HDLM, 56 fully removing, 57 removing, 62, 67, 73 HDS Storage-to-HP 3PAR StoreServ Storage online import, 6 help CLI command, 95 Hitachi Command Suite see HCS Hitachi Dynamic Link Manager see HDLM host, 7 AIX, 70 HP-UX, 76 Linux, 65 Windows, 60 host multipath software updating, 56 host multipathing solution reconfiguring, 33 HP 3PAR CLI commands controlport, 36 HP 3PAR Management Console, 13, 44, 51, 58, 63, 68, 74, 77, 79 HP 3PAR Online Import Utility CLI commands, 91 migrations, 26 migrations supported, 27 HP 3PAR Online Import Utility service starting, 82 stopping, 82 HP 3PAR Peer Motion license, 32 HP SPOCK, 14 I identifying source and destination storage systems, 37 installation and setup, 14 installcertificate CLI command, 96 installing HCS, 14 Installing HP 3PAR Online Import Utility, 20 L LDEVs limits for offline migration, 31 maximum for MDM, 31 migrating, 31 presented, 7 renamed for use by the HP 3PAR StoreServ Storage, 7 unpresented, 7 license HCS CLI SMI-S, 14 HP 3PAR Peer Motion, 32 HP End User License Agreement, 22 logging level (HP 3PAR Online Import Utility) modifying, 83 logs HP 3PAR Online Import Utility, 83 LUNs scanning, 65, 70 M maximum LDEVs that can be migrated, 6 MDM for a Linux host, 62 for a Windows host, 56 for an AIX host, 67 for an HP-UX host, 73 migration, 6 migrating LDEVs, 31 migration, 7, 9, 11 aborting, 80 MDM, 6, 56, 62, 67, 73 offline, 6, 7, 77 online, 6, Index

125 process, 7 supported, 26 unsupported, 26 migration process migration, 9, 11 post-migration, 12 premigration, 12 minimally disruptive migration see MDM modifying HP 3PAR Online Import Utility logging level, 83 MPIO path management, 56 multipathing software, 33 N network and fabric zoning requirements, 32 O offline migration, 6, 7, 77 offline migration process migration, 13 post-migration, 13 online migration, 6, 44 Open-x systems, 7 overview, 6 P performing data migration, 56, 62, 67, 73 planning data migration, 32 ports controller (on source system), 33 peer, 37 peer (on destination system), 33 post-migration, 7, 12 offline migration process, 13 tasks, 79 premigration, 7, 12 preparing for data migration, 31 host, 39 prerequisite component installation MDM, 10 process migration, 7 R reconfiguring host multipathing solution, 33 removedestination CLI command, 97 removemigration CLI command, 97 removesource CLI command, 98 removing the HDLM, 62, 67, 73 the HDLM (from Windows host), 57 replication, 31, 39, 42, 84, 88 requirements data migration, 14 network and zoning, 32 system, 32 S scanning LUNs, 65, 70 showconnection CLI command, 98 showdestination CLI command, 99 showmigration CLI command, 67, 69, 73, 75, 99 showmigrationdetails CLI command, 69, 70, 75, 76, 78, 101 showpersona CLI command, 101 showsource CLI command, 103 Single Point of Connectivity Knowledge website see HP SPOCK source storage system adding, 38 starting data migration, 59 HP 3PAR Online Import Utility service, 82 startmigration CLI command, 69, 74, 104 stopping HP 3PAR Online Import Utility service, 82 symbols in text, 120 system requirements, 32 T terms, 122 text symbols, 120 troubleshooting, 81, 83 types of data migration, 6 U updating host multipath software, 56 V viewing migration progress, 80 migrations, 80 selected migrations, 80 W Windows clusters preparing for migration, 39 Z zoning between source HDS Storage and destination HP 3PAR StoreServ Storage, 36 data migration requirements,

126 paths, 33 the host, 58, Index