HP 3PAR Online Import for EMC Storage Data Migration Guide

Transcription

1 HP 3PAR Online Import for EMC Storage Data Migration Guide Abstract This guide provides information about using HP 3PAR Online Import for EMC Storage software to migrate data from an EMC 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. Acknowledgements Microsoft and Windows 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 EMC Storage...6 Types of Data Migration...6 Understanding Which Data is Migrated...6 EMC 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...11 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 EMC SMI-S Provider...14 Configuring EMC SMI-S Provider...15 Installing the HP 3PAR Online Import Utility...16 Migrations Supported by HP 3PAR Online Import Utility...24 Migrations Supported for EMC VNX, CLARiiON CX4, and VMAX...24 Migrations Supported by the HP 3PAR Online Import Utility for EMC VMAX Only Preparing for Data Migration...29 Data Migration Considerations...29 General Considerations...29 System Requirements...30 Planning for Migration...30 Network and Fabric Zoning Requirements...31 Reconfiguring the Host Multipath Solution...32 Working with Consistency Groups Premigration Steps...34 Zoning the Source EMC Storage to the Destination HP 3PAR StoreServ Storage System...34 Identifying the Source and Destination Storage Systems...35 Prerequisites...35 Required Information...36 Adding the Source Storage System...36 Adding the Destination Storage System...36 Preparing the Host for Data Migration...37 Creating the Data Migration Task...39 Required Information...40 Issuing the createmigration Command Performing Data Migration for Red Hat Linux and Oracle RAC...42 Online Data Migration with Removal of EMC PowerPath...42 Contents 3

4 Online Data Migration with Native device-mapper Multipath Performing Minimally Disruptive Migration Using a Windows Host...54 Creating the Data Migration Task...54 Updating Host Multipath Software and Unzoning from the Source EMC Storage System...54 Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System...57 Bringing the Windows Host Back Online Performing Minimally Disruptive Migration Using a Linux Host...60 Creating the Data Migration Task...60 Updating Host Multipath Software and Unzoning from Source EMC Storage System...60 Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System...62 Bringing the Linux Host Back Online Performing Minimally Disruptive Migration Using a Hyper-V Host...65 Creating the Data Migration Task...65 Updating Host Multipath Software and Unzoning from the Source EMC Storage System...66 Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System...67 Bringing the Hyper-V Host Back Online Performing Offline Data Migration...70 Creating the Data Migration Task...70 Zoning the Host to the Destination HP 3PAR StoreServ Storage System...70 Shutting Down the Host...70 Removing the Host from the Storage Group...71 Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System...71 Performing Post-Migration Tasks Specifically for Offline Migration Performing Common Migration and Post-migration Tasks...73 Viewing Migration Status...73 Viewing all Migrations...73 Viewing Migrations for a Selected Source Storage System...73 Viewing a Selected Migration...73 Viewing Selected Migration Progress by Volume...73 Aborting a Migration...73 Performing Subsequent Migrations...73 Removing a Storage System from EMC SMI-S Provider Troubleshooting...75 HP 3PAR Online Import Utility Error Messages...75 Troubleshooting Resources...76 Understanding the HP 3PAR Online Import Utility Data Migration Process...76 HP 3PAR Online Import Utility Server Logs and Output...77 Increase the HP 3PAR Online Import Utility Server Logging Level...78 EMC SMI-S Provider Server Logs and Output...79 Increasing the EMC SMI-S Provider Server Logging Level...79 Troubleshooting Communication Between the HP 3PAR Online Import Utility Server and EMC SMI-S Provider...79 TestSmiProvider Login and Command Examples with Output...80 Troubleshooting Issues...84 Cannot Add a Source EMC Storage system...84 Cannot Create a Migration...84 Cannot Log into the HP 3PAR Online Import Utility...85 Migration Includes Unexpected LUNs and Hosts Contents

5 Masking View Required for Offline Migration of LUN with No Host...85 HP 3PAR Online Import Utility Does Not Distinguish between Source Arrays When Managing the Same Host...85 The HP 3PAR Online Import Utility Does Not Open in Windows Trailing Spaces in IP Address Return Login Error...86 The adddestination Command Returns Error OIUERRDST The createmigration Command Fails for Migrated LUNs in a Storage Group with No Host...86 The createmigration Command Fails for LUN Name or Host Name Containing Special Characters...87 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 startmigration Command Fails with Host Name That Exceeds 31 Characters...89 The startmigration Command Returns Error OIUERRMS Appendices...90 Appendix A: HP 3PAR Online Import Utility CLI Commands...90 adddestination...90 addsource...90 createmigration...92 help...95 installcertificate...95 removedestination...96 removemigration...97 removesource...97 showconnection...97 showdestination...98 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: Clearing a Persistent SCSI Reservation from EMC Storage Arrays with HP 3PAR OS MU2 or Earlier Removing a Persistent SCSI Reservation from an EMC CX4 or VNX Device Removing a Persistent SCSI Reservation from an EMC VMAX Device 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 EMC Storage HP 3PAR Online Import for EMC Storage manages the migration of data from a source EMC Storage system to a destination HP 3PAR StoreServ Storage system. Using HP 3PAR Online Import for EMC Storage, you can migrate EMC volumes and host configuration information to a destination HP 3PAR StoreServ Storage system without changing host configurations or interrupting data access. The terms storage system and array are used interchangeably throughout this guide, and may refer to either the EMC Storage system or the HP 3PAR StoreServ Storage system. The source in the migration is the EMC VMAX, VNX, or CX4 Storage system, and the destination is the HP 3PAR StoreServ Storage system. HP 3PAR Online Import for EMC 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 EMC Storage system through the HP 3PAR StoreServ Storage system. The host/volume presentation implemented on the EMC Storage is maintained on the destination HP 3PAR StoreServ Storage system. For additional information about supported EMC Storage systems, see the HP 3PAR Online Import support matrix on HP SPOCK: HP SPOCK ( Types of Data Migration HP 3PAR Online Import for EMC 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 volume presented to a host. During online migration, all presentation relationships between hosts and volumes 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 a volume 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 volumes. During offline migration, only the selected volumes are migrated. No hosts are migrated in this situation. Understanding Which Data is Migrated Data can be migrated by selecting a host or a volume on the source EMC Storage system. In addition to the host or volume explicitly selected for an online migration or for migration, other objects will be included in the migration using implicit selection. The migration process identifies the relationship between hosts and presented volumes 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 volumes. Selecting a single host results in migration of the following: The host as well as any volumes presented to it Any other hosts to which those volumes are presented Any volumes presented to those other hosts The maximum number of volumes that can be migrated with MDM or an online migration 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. 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. 6 Overview of HP 3PAR Online Import for EMC Storage

7 The migration process selects objects to migrate using the following rules: Hosts When selecting a single host or group of hosts with volume presentations, all the volumes presented to the host(s) are migrated. In addition, any presentations the source volumes have to other hosts will include those hosts and all of their presented volumes in the migration. Presented volumes When selecting a volume or group of volumes with host presentations, the selected volumes and the hosts to which they are presented are migrated. In addition, any presentations the source hosts have with other volumes will be included in the migration. Unpresented volumes Only the selected unpresented volumes are migrated. The offline migration type is the only type available for unpresented volume 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 24). EMC Storage to HP 3PAR StoreServ Storage Migration Process The process to migrate EMC Storage volumes 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. EMC 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 EMC SMI-S Provider. Install the HP 3PAR Online Import Utility. See: HP SPOCK ( See also Configuration Rules for HP 3PAR Online Import Support (page 14) Installing EMC SMI-S Provider (page 14) Installing the HP 3PAR Online Import Utility (page 16) Premigration Table 2 Premigration checklist online Number Step Zone the EMC 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 EMC Storage to the Destination HP 3PAR StoreServ Storage System (page 34) Adding the Source Storage System (page 36) Adding the Destination Storage System (page 36) Migration If EMC PowerPath 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 EMC PowerPath is not installed, see the column on the right for details. Table 3 Migration checklist online Number Step If EMC PowerPath is installed, see: If EMC PowerPath is not installed, see: 1 Zone the host to the HP 3PAR StoreServ Storage system. Online Data Migration with Removal of EMC PowerPath (page 42), step 1 Online Data Migration with Native device-mapper Multipath (page 49), step 1 2 Configure device-mapper on the 1. Uninstall EMC PowerPath. host. See: Online Data Migration with Removal of EMC PowerPath (page 42), step 2 Online Data Migration with Native device-mapper Multipath (page 49), step 2 8 Migration Process Checklists

9 Table 3 Migration checklist online (continued) Number Step If EMC PowerPath is installed, see: If EMC PowerPath is not installed, see: NOTE: A maintenance window is required. 2. Configure device-mapper on the host. See: Online Data Migration with Removal of EMC PowerPath (page 42), step 3 3. Remount application file systems. See: Online Data Migration with Removal of EMC PowerPath (page 42), step 4 3 Using the HP 3PAR Online Import Utility, create a migration with the createmigration command. Online Data Migration with Removal of EMC PowerPath (page 42), steps 5 7 Online Data Migration with Native device-mapper Multipath (page 49), steps Update path configurations. Online Data Migration with Removal of EMC PowerPath (page 42), steps 8 10 Online Data Migration with Native device-mapper Multipath (page 49), steps Using the HP 3PAR Online Import Utility, start the migration with the startmigration) command. Online Data Migration with Removal of EMC PowerPath (page 42), step 11 Online Data Migration with Native device-mapper Multipath (page 49), step 9 6 Monitor migration with the HP 3PAR Online Import Utility until completion. Viewing Migration Status (page 73) Viewing Migration Status (page 73) Post-Migration Table 4 Post-migration checklist online Number Step Optional: Remove the migration definition when the migration has completed. removemigration (page 97) Remove zoning between the EMC Storage system and HP 3PAR StoreServ Storage system after all migrations from the EMC Storage system are complete. Optional: Reconfigure peer ports to host ports. Optional: When all migrations are complete, remove the source EMC Storage system and the destination HP 3PAR StoreServ Storage from the HP 3PAR Online Import Utility, using the removesource and removedestination commands. 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 2 3 Step Install EMC SMI-S Provider. Install the HP 3PAR Online Import Utility. See: See also Configuration Rules for HP 3PAR Online Import Support (page 14) Installing EMC SMI-S Provider (page 14) Installing the HP 3PAR Online Import Utility (page 16) Premigration Table 6 Premigration checklist MDM Number Step Zone the EMC 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. Using the HP 3PAR Online Import Utility, create the migration with the createmigration command) See: Zoning the Source EMC Storage to the Destination HP 3PAR StoreServ Storage System (page 34) Adding the Source Storage System (page 36) Adding the Destination Storage System (page 36) Preparing the Host for Data Migration (page 37) Creating the Data Migration Task (page 39) 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 EMC Storage System (page 54) For Linux: Updating Host Multipath Software and Unzoning from Source EMC Storage System (page 60) For Hyper-V: Updating Host Multipath Software and Unzoning from the Source EMC Storage System (page 66) 2 Using the HP 3PAR Online Import Utility, start the For Windows: migration with the startmigration command. Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System (page 57) For Linux: Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System (page 62) For Hyper-V Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System (page 67) 3 Power up the host and rescan migrating disks. For Windows: Restart server applications (including cluster). Bringing the Windows Host Back Online (page 58) For Linux: Bringing the Linux Host Back Online (page 63) For Hyper-V Bringing the Hyper-V Host Back Online (page 69) 4 Monitor migration with the HP 3PAR Online Import Utility until completion. Viewing Migration Status (page 73) Post-Migration Table 8 Post-migration checklist MDM Number 1 2 Step Optional: Remove the migration definition when the migration has completed. See removemigration (page 97). Remove zoning between the EMC Storage system and HP 3PAR StoreServ Storage system after all migrations from the EMC Storage system are complete. Minimally Disruptive Migration 11

12 Table 8 Post-migration checklist MDM (continued) Number 3 4 Step Optional: Reconfigure peer ports to host ports. Optional: When all migrations are complete, remove the source EMC Storage system and the destination HP 3PAR StoreServ Storage from the HP 3PAR Online Import Utility, using the removesource and removedestination commands. Offline Migration Prerequisite Component Installation Table 9 Prerequisite component installation offline Number Step Check the HP SPOCK website to confirm proper configuration. Install EMC SMI-S Provider. Install the HP 3PAR Online Import Utility. See: HP SPOCK ( See also Configuration Rules for HP 3PAR Online Import Support (page 14) Installing EMC SMI-S Provider (page 14) Installing the HP 3PAR Online Import Utility (page 16) Premigration Table 10 Premigration checklist offline Number Step Zone the EMC 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. 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: Zoning the Source EMC Storage to the Destination HP 3PAR StoreServ Storage System (page 34) Preparing the Host for Data Migration (page 37) Identifying the Source and Destination Storage Systems (page 35) Identifying the Source and Destination Storage Systems (page 35) Creating the Data Migration Task (page 70) Zoning the Host to the Destination HP 3PAR StoreServ Storage System (page 70) 12 Migration Process Checklists

13 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 EMC Storage System to Destination HP 3PAR StoreServ Storage System (page 71) 2 Monitor migration with the HP 3PAR Online Import Utility until completion. Viewing Migration Status (page 73) Post-Migration Table 12 Post-migration checklist offline Number Step Unzone the source EMC Storage system from the host. Restart the host. Remove the EMC PowerPath multipath software, if present, and configure 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. Optional: When all migrations are complete, remove the source EMC 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 72), step 1 Performing Post-Migration Tasks Specifically for Offline Migration (page 72), step 2 Performing Post-Migration Tasks Specifically for Offline Migration (page 72), step 3 Performing Post-Migration Tasks Specifically for Offline Migration (page 72), step 4 removemigration (page 97) removesource (page 97) removedestination (page 96) 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 EMC 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 EMC 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 EMC Storage coexistence. The supported configuration environments for installing HP 3PAR Online Import. Installing EMC SMI-S Provider The HP 3PAR Online Import Utility manages the source EMC Storage system through the EMC SMI-S Provider software. The EMC SMI-S Provider is a component of EMC Solutions Enabler and requires underlying EMC Solutions Enabler code to function. However, installation of the base EMC Solutions Enabler software does not include the EMC SMI-S Provider component. Installation of the EMC SMI-S Provider includes only the necessary underlying EMC Solutions Enabler code, not a full installation of EMC Solutions Enabler. IMPORTANT: It is technically possible to install the EMC SMI-S Provider on a machine where EMC Solutions Enabler is already installed, but be aware that the EMC SMI-S Provider installation uninstalls any existing EMC Solutions Enabler software and reinstalls only the subset of EMC Solutions Enabler that comes with the EMC SMI-S Provider. The connection between an EMC VMAX and the EMC SMI-S Provider runs over Fibre Channel. The connection between an EMC VNX or CLARiiON CX4 EMC and the EMC SMI-S Provider runs over Ethernet. For VMAX, a VMAX gatekeeper device must be presented to the SMI-S server. The EMC Solutions Enabler and the EMC SMI-S Provider are provided by EMC as separately installable products, available on the following website: NOTE: This link will take you outside the Hewlett-Packard website. HP does not control and is not responsible for information outside hp.com. The HP 3PAR Online Import Utility supports installation of the EMC SMI-S Provider only on Windows. See product release notes for full installation details: SMI Provider Release Notes ( snia/smi-s/downloads/smi_provider_rn.pdf) NOTE: This link will take you outside the Hewlett-Packard website. HP does not control and is not responsible for information outside hp.com. 14 Installation and Setup for Data Migration

15 To install the EMC SMI-S Provider software, follow these steps: 1. Download EMC SMI-S Provider Installer from EMC. An EMC login account is required. To download the program, go to the following website: EMC ( NOTE: This link will take you outside the Hewlett-Packard website. HP does not control and is not responsible for information outside hp.com. 2. Launch the se76226 installer. The EMC Solutions Enabler welcome page appears, prompting you to install Solutions Enabler with SMI-S version V Click Next to begin the installation process. 4. The Destination Folder dialog box opens and prompts you to select an install directory for Solutions Enabler and EMC SMI-S Provider. It is recommended that you choose the default directory. 5. Click Next to continue. The Provider List dialog box opens. 6. Select Array Provider. 7. Click Next to continue. The Ready to Install Program dialog box opens. 8. Click Install to begin installing files to your selected folder. This may take several minutes. 9. When the Installation Wizard Completed dialog box opens, click Finish to complete the setup. Configuring EMC SMI-S Provider The EMC SMI-S Provider must be configured to allow remote software to connect to the EMC Storage system. 1. Open a Windows command prompt on the server where the EMC SMI-S Provider software was installed. 2. Change the directory to the location of the EMC SMI-S Provider installation. The default is: C:\Program Files\EMC\ECIM\ECOM\bin 3. Start the testsmiprovider program. 4. Accept all default settings when prompted. 5. Attach the storage system to the EMC SMI-S Provider. NOTE: If both an EMC VMAX and an EMC CLARiiON or VNX storage system are being migrated, both of the following steps must be performed. a. For VMAX storage systems, any VMAX storage arrays connected to the EMC SMI-S Provider server will be automatically detected, provided that: SMI-S and VMAX have a Fibre Channel connection and are zoned. A gatekeeper LUN is presented to the SMI-S server. If the VMAX does not show up, run the disco command to rescan for arrays. Proceed to step 6, unless you want to add an EMC CLARiiON or VNX storage system. b. To attach an EMC CLARiiON or VNX storage system to SMI-S Provider, use the addsys command: (localhost:5988)? addsys Add System {y n} [n]: y ArrayType (1=Clar, 2=Symm) [1]: One or more IP address or Hostname or Array ID Elements for Addresses IP address or hostname or array id 0 (blank to quit): <IP address of SPA> Configuring EMC SMI-S Provider 15

16 IP address or hostname or array id 1 (blank to quit): <IP address of SPB> IP address or hostname or array id 2 (blank to quit): Address types corresponding to addresses specified above. (1=URL, 2=IP/Nodename, 3=array ID) Address Type (0) [default=2]: Address Type (1) [default=2]: User: <Global Administrator> global administrator user for CX4 array Password [null]: <password> ++++EMCAddSystem++++ OUTPUT : 0 Output codes are shown in the following table: Success Not Supported Unknown Timeout Failed Invalid Parameter Job Queued Size Not Supported 6. Use the dv command to verify that the storage system is discovered. NOTE: If your EMC SMI-S Provider has client IP filtering enabled, you need to add the IP address of the HP 3PAR Online Import Utility server to the trusted IP address list. To add an HP 3PAR Online Import Utility server to the EMC SMI-S Provider trusted IP address list: 1. Log into SMI-S ECOM administration page using one of the SMI-S user and password configured: IP address>:5989/ecomconfig IP address>:5988/ecomconfig 2. Select the Client IP Filtering link on the ECOM Administration page. 3. Add the HP 3PAR Online Import Utility server IP address in the Trusted client s IP field on the Client IP Filtering page and click Execute to complete. Installing the HP 3PAR Online Import Utility The HP 3PAR Online Import Utility can be obtained from the HP Software Depot using the following link: HP Software Depot ( 16 Installation and Setup for Data Migration

17 NOTE: If you are upgrading from an earlier version of the HP 3PAR Online Import Utility to a later version, you must uninstall the earlier version before upgrading to the latest version. See the HP SPOCK website for supported target environments for the HP 3PAR Online Import Utility server: HP SPOCK ( The HP 3PAR Online Import Utility software consists of two installable applications: the HP 3PAR Online Import Utility client and the HP 3PAR Online Import Utility server. If one component has already been installed on a given system, and you want to add the second component on the same system, first run the installer to remove the component already installed, and then rerun the installer to install both components at once. 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. Installing the HP 3PAR Online Import Utility 17

18 2. When the Welcome screen appears, click Next. 18 Installation and Setup for Data Migration

19 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, Installing the HP 3PAR Online Import Utility 19

20 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 1 Editing the service port in the OIUCli.bat file java -jar..\cli\oiucli jar-with-dependencies.jar %* -port Click Install. 20 Installation and Setup for Data Migration

21 7. Monitor the progress of the installation. When complete, click Next. 8. Tomcat services will begin installation. When complete, click Next. Installing the HP 3PAR Online Import Utility 21

22 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. 22 Installation and Setup for Data Migration

23 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. Installing the HP 3PAR Online Import Utility 23

24 Migrations Supported by HP 3PAR Online Import Utility For migration types supported by the HP 3PAR Online Import Utility for EMC VNX, CLARiiON CX4, and VMAX, see Table 14 (page 24) For migration types supported by the HP 3PAR Online Import Utility for EMC VMAX only, see Table 15 (page 28) See Table 13 (page 24) for a legend for the migration-type tables. Table 13 Legend for the migration support tables LUN Host Storage group Item selected by user input on the HP 3PAR Online Import Utility Migrations Supported for EMC VNX, CLARiiON CX4, and VMAX Migrations supported by the HP 3PAR Online Import Utility for are shown in Table 14 (page 24). Table 14 Migration supported by the HP 3PAR Online Import Utility Supported Configuration Description Single LUN, single host 24 Installation and Setup for Data Migration

25 Table 14 Migration supported by the HP 3PAR Online Import Utility (continued) Supported Configuration Description 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. 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. Migrations Supported by HP 3PAR Online Import Utility 25

26 Table 14 Migration supported by the HP 3PAR Online Import Utility (continued) Supported Configuration Description 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. 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. 26 Installation and Setup for Data Migration

27 Table 14 Migration supported by the HP 3PAR Online Import Utility (continued) Supported Configuration Description 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. 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. Migrations Supported by the HP 3PAR Online Import Utility for EMC VMAX Only IMPORTANT: The migrations shown here are supported only for VMAX. Migrations Supported by HP 3PAR Online Import Utility 27

28 NOTE: These configurations are not supported for EMC VNX or CLARiiON CX4: The createmigration command checks for these configurations and blocks migrations of unsupported configuration. In most cases, unsupported configurations are those in which multiple LUNs that span multiple storage groups are to be added to the migration (either explicitly or implicitly). It is an error when the added storage groups do not contain exactly the same LUNs. Table 15 Migration supported by the HP 3PAR Online Import Utility for VMAX only Configurations Supported by VMAX Only Description A LUN in multiple storage groups is selected, and the groups are not identical. A LUN in a single storage group is selected, but it is grouped with a shared LUN, and the shared LUN s storage groups are not identical. A host is selected, but it is grouped with a shared LUN, and the shared LUN s storage groups are not identical. LUNs are selected spanning multiple groups, and the storage groups are not identical. LUNs are selected spanning multiple storage groups, and the storage groups are not identical. 28 Installation and Setup for Data Migration

29 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 EMC 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 volumes presented to Fibre Channel hosts can be migrated. Volumes presented to iscsi or FCoE hosts cannot be migrated. All LUNs present in a source group are migrated, even if only one was selected. All hosts present in a host group are migrated. 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. HP 3PAR host persona/host OS: EMC Storage arrays do not implement specific OS settings when registering host initiators on the EMC Storage array. During migration, online import cannot determine the host OS when migrating the hosts to the HP 3PAR StoreServ Storage. All hosts that are being created on the HP 3PAR StoreServ Storage during EMC migration are set by default to host persona 2. Change the HP 3PAR host persona/host OS to the appropriate setting before enabling access to the HP 3PAR array. LUNs identified for migration should not be part of any current replication or backup jobs. The LUN limit for offline migrations is 25. The maximum number of volumes 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 EMC Storage storage group at a time. When a volume on the source EMC Storage system is migrated, a SCSI-3 reservation is issued to prevent any unwanted management changes to the volume during the migration. With HP 3PAR OS MU2 and earlier, the SCSI-3 reservation remains on the volume after the migration. With HP 3PAR OS MU3 and later, the SCSI reservation is removed upon successful migration. For information about removing a SCSI reservation following an unsuccessful migration, see: Appendix D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later (page 109) Appendix E: Clearing a Persistent SCSI Reservation from EMC Storage Arrays with HP 3PAR OS MU2 or Earlier (page 110) Only one EMC Storage system at a time can be attached as a source to the destination HP 3PAR StoreServ Storage system. EMC volumes 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 Data Migration Considerations 29

30 boundary-based. A volume, even one that is not a multiple of 256 MB, can still be migrated, provided that the volume is not smaller than 256 MB. EMC volumes cannot be migrated if they are larger than 16 TB, the maximum volume size on the HP 3PAR StoreServ Storage system. Snapshots become standalone objects on the destination 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 ( System Requirements NOTE: For detailed information about ensuring the source EMC 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 EMC Storage system to an HP 3PAR StoreServ Storage system using HP 3PAR Online Import for EMC Storage, the system environment must meet the following requirements: Source EMC 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 EMC PowerPath, if present. Identify which volumes and/or hosts will be migrated. If you do not want to migrate all the volumes presented to a host, you must unpresent the volumes that you do not want migrated. Otherwise, all the volumes will be implicitly included in the migration. When you migrate TPVVs from the EMC 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 thin, full, or dedupe provisioning on the destination storage system. This decision impacts the amount of capacity needed on the destination storage system. NOTE: For HP 3PAR Online Import, TDVVs are supported on a destination with HP 3PAR OS MU2 or later. 30 Preparing for Data Migration

31 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, then before performing a migration, set the system option mode on the EMC Storage array 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 EMC documentation for more information. When selecting objects for migration, be aware of any overlap or sharing of volumes between hosts. In this situation, selecting a host or a volume in any set results in every volume and every host in all sets being implicitly selected for migration due to the overlap. For additional information, see Migrations Supported by HP 3PAR Online Import Utility (page 24). For VMAX only: Gatekeeper LUNs are widely used for communication between host and VMAX array or for array operations such as backups. Gatekeeper LUNs are typically smaller than 256 MB, and are therefore too small to be migrated. If gatekeeper LUNs have been presented to hosts explicitly in the masking view that corresponds to a migration, they cause the migration to fail. Gatekeeper LUNs (or any small LUNs) must be removed from masking views being migrated. Identify which functions on the host are relying on the gatekeeper and ensure that they are properly shut down. In the case of operations such as automated backup, plan to perform the operation after the migration. 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 Figure 1 (page 31). A blue line indicates a peer link between the HP 3PAR StoreServ Storage and the EMC Storage system. A red line indicates a data link. Figure 1 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 EMC Storage system must be connected Data Migration Considerations 31

32 to two peer ports on the destination HP 3PAR StoreServ Storage system. See Zoning the Source EMC Storage to the Destination HP 3PAR StoreServ Storage System (page 34). Paths between the host and the source EMC 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 EMC 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. 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 EMC 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 EMC Storage system from the host. IMPORTANT: If you unzone the host from the EMC Storage system but do not reconfigure the host multipathing software, the host/cluster will experience an outage, because it will not be able to communicate with the destination HP 3PAR StoreServ Storage system. 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: Consistency groups are supported on the destination HP 3PAR StoreServ Storage system running HP 3PAR OS version or later on supported platforms. 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. 32 Preparing for Data Migration

33 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 volumes. allvolumesincg: All volumes (including implicit volumes) will be migrated consistently. Example 2 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 3 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. Example 4 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 volume 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 5 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 volumes (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 volumes 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 33

34 5 Premigration Steps Perform these steps to prepare for migration. Zoning the Source EMC Storage to the Destination HP 3PAR StoreServ Storage System The correct zoning must be present between the source EMC 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 EMC 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 6 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 EMC Storage system and the destination HP 3PAR StoreServ Storage system, ensuring that one EMC 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 separate EMC controllers in a one-to-one mapping. For example, zone the peer port on node 0 on the HP 3PAR StoreServ Storage system to controller 34 Premigration Steps

35 A on the EMC Storage system, and zone the peer port on node 1 on the HP 3PAR StoreServ Storage system to controller B on the EMC Storage system. 3. Verify that the EMC 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 using VMAX, follow these steps: a. Issue the following command: # symaccess -sid <vmax id> list logins b. Check the Identifier listed for each HP 3PAR peer port and make sure they are logged in (Yes). C:\Users\Administrator>symaccess -sid 1212 list logins Symmetrix ID : Director Identification : FA-7E Director Port : 0 User-generated Logged On Identifier Type Node Name Port Name FCID In Fabric ac005f91 Fibre ac005f ac005f Yes Yes Director Identification : FA-8E Director Port : 0 User-generated Logged On Identifier Type Node Name Port Name FCID In Fabric ac005f91 Fibre ac005f ac005f Yes Yes Alternatively, verify that the EMC Storage system is shown as a connected device on both peer ports of the destination HP 3PAR StoreServ Storage system. To check peer port connections from the HP 3PAR StoreServ Storage, issue the showtarget command with the -rescan option, and then issue the showtarget command. In this example, Node_WWN is the WWN of the source array # showtarget -rescan # # showtarget Port ----Node_WWN Port_WWN Description :2: C012F C012F11C reported_as_scsi_target 0:2: C012F C012F118 reported_as_scsi_target 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. EMC SMI-S Provider is installed and operational. The source EMC Storage system must be registered in the EMC SMI-S Provider application. The source EMC Storage system has one or more storage groups configured with the hosts and volumes to be migrated. Identifying the Source and Destination Storage Systems 35

36 The HP 3PAR Online Import Utility is installed and operational with access to the SMI-S Provider server managing the source EMC Storage system and the destination HP 3PAR StoreServ Storage system. The source EMC Storage system and destination HP 3PAR StoreServ Storage system are zoned to each another. Required Information EMC Storage source system: IP address of the EMC SMI-S Provider server that is managing the source EMC Storage system from which the volumes are being migrated and the WWN of the source EMC Storage system being managed by the EMC SMI-S Provider. User name and password for the EMC SMI-S Provider. Port to access the EMC SMI-S Provider. Secure port default Non-secure port default 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 7 addsource command # addsource -type VNX -mgmtip XX.XX.XX.XX -user admin -password adminpw uid xxxxxxxxxxxxxxxx # SUCCESS: Added source storage system where XX.XX.XX.XX is the IP address of the EMC SMI-S Provider server, and xxxxxxxxxxxxxxxx is the WWN of the EMC Storage system. 2. Issue the showsource command to verify the source storage system information. Example 8 showsource command # showsource type VNX NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE CLARiiON+APM VNX BEE0177F 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. 36 Premigration Steps

37 Example 9 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 10 Certificate validation error ), first run the installcertificate command (see Example 11 Installcertificate command ), then run the adddestination command again. Example 10 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 11 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 12 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. For Hyper-V running on Windows Server 2008 R2, follow these steps to prepare the host for migration: 1. Stop all applications currently running on the virtual machine. 2. Shut down the virtual machines using Failover Cluster Manager. 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 Preparing the Host for Data Migration 37

38 2008 R2, this can be achieved by stopping all applications running on the cluster, then stopping the cluster service on all nodes. When a Windows Server 2012 active/passive cluster is migrated, maintenance mode must be set on the cluster disks to clear SCSI reservations on the disks. Because the quorum disk cannot be set in the maintenance mode, it must be set to the offline mode to clear its SCSI reservations. Then, the cluster service must be stopped 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 Veritas Clusters for Migration NOTE: Only EMC VMAX arrays are supported with Veritas clusters at this time. 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 LUNs used in the cluster: Example 13 Listing LUNs in a cluster # vxdisk list DEVICE TYPE DISK GROUP STATUS cciss/c0d0 auto:none - - online invalid emc0_00fe auto:cdsdisk - - online thinrclm emc0_00ff auto:cdsdisk - - online thinrclm emc0_0100 auto:cdsdisk - - online thinrclm emc0_0101 auto:cdsdisk - - online thinrclm emc0_0102 auto:cdsdisk - - online thinrclm emc0_0103 auto:cdsdisk - - online thinrclm emc0_0104 auto:cdsdisk - - online thinrclm emc0_0105 auto:cdsdisk - - online thinrclm emc0_0106 auto:cdsdisk - - online thinrclm 2. Create a tmpfile in the /root directory with all the LUNs. the tmpfile will be similar to the following example: 38 Premigration Steps

39 Example 14 tmpfile with LUNs /dev/vx/rdmp/emc0_00fe /dev/vx/rdmp/emc0_00ff /dev/vx/rdmp/emc0_0100 /dev/vx/rdmp/emc0_0101 /dev/vx/rdmp/emc0_0102 /dev/vx/rdmp/emc0_0103 /dev/vx/rdmp/emc0_0104 /dev/vx/rdmp/emc0_0105 /dev/vx/rdmp/emc0_ Issue the following command to verify that the reservation keys are clear: Example 15 Verifying that reservation keys are clear # vxfenadm -s all -f tmpfile Device Name: /dev/vx/rdmp/emc0_00fe Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_0100 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_00ff Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_0101 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_0102 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_0106 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_0105 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_0103 Total Number Of Keys: 0 No keys... Device Name: /dev/vx/rdmp/emc0_0104 Total Number Of Keys: 0 4. 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: Creating the Data Migration Task 39

40 Required Information EMC Storage source system The WWN of the source EMC Storage system being managed by the EMC SMI-S Provider. The list of volumes that are being migrated. As a best practice, all volumes should be in the same storage group, or in different storage groups with identical volume membership. OR Name of the host associated with volumes to be migrated. Host and volumes must be in supported storage group configuration on the source EMC Storage system. For details, see Migrations Supported by HP 3PAR Online Import Utility (page 24). Destination HP 3PAR StoreServ Storage system Provisioning type for the volumes being created on the destination storage system (thin, full, or dedupe). NOTE: For HP 3PAR Online Import, TDVVs are supported on a destination with HP 3PAR OS MU2 or later. 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 a VNX or CLARiiON CX4 source storage system, two HP 3PAR initiators are added to the storage group that contains the hosts or volumes being migrated. The host name of the HP 3PAR initiators is unknown. The initiator name appears as the WWN of the peer port on the HP 3PAR StoreServ Storage. On a VMAX source storage system, the following groups are created for the migration: One storage group is added, containing the devices being migrated. The naming convention is: OIU_<migrationID>_SG One initiator group per HP 3PAR peer port is added. The naming convention is: <hostname>_<migrationid> One initiator group parent is added and associated to the HP 3PAR peer port initiator groups. The naming convention is: OIU_<migrationID>_IG One port group is added, containing the required ports based on the original masking views. The naming convention is: OIU_<migrationID>_PG After all of these groups have been created and populated, a migration masking view is added and associated to the migration storage group, initiator group, and port group. The naming convention is: OIU_<migrationID>_MV NOTE: For VMAX, these groups remain on the VMAX system after migration is completed; they are not cleaned up. 40 Premigration Steps

41 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 volumes being migrated are admitted to the destination system and exported to the host. For MDM, the volumes 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 EMC Storage system. The source storage system group configuration is valid. The volumes or hosts specified in the createmigration command are mapped to a storage group on the associated source EMC Storage system. All LUNs and all hosts in the mapped storage 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 24). EMC SMI-S Provider version. Source storage system model number. NOTE: See the HP SPOCK website for the latest supported versions: HP SPOCK ( 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 EMC PowerPath is installed: Online Data Migration with Removal of EMC PowerPath (page 42), steps 5 8 Online migration, if EMC PowerPath is not installed: Online Data Migration with Native device-mapper Multipath (page 49), step 3 MDM Linux: Creating the Data Migration Task (page 60) Windows: Creating the Data Migration Task (page 54) Hyper-V: Creating the Data Migration Task (page 65) Offline migration: Creating the Data Migration Task (page 70) Creating the Data Migration Task 41

42 6 Performing Data Migration for Red Hat Linux and Oracle RAC If EMC PowerPath is installed, it must be uninstalled, and the native Linux device-mapper must be used to configure multipathing. Follow the online data migration procedure in Online Data Migration with Removal of EMC PowerPath (page 42). If EMC PowerPath is not installed, follow the online data migration procedure in Online Data Migration with Native device-mapper Multipath (page 49). Online Data Migration with Removal of EMC PowerPath To perform online data migration when EMC PowerPath is present, follow these steps. NOTE: A maintenance window is required to complete an online data migration with removal of EMC PowerPath (see step 2). NOTE: Before using the HP 3PAR Online Import Utility for Oracle RAC=based configurations, it is critical to verify that the cluster registry, voting, and data disks reside on the same source array and are not distributed across multiple arrays. 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 EMC PowerPath, the devices get a /dev/emcpower* 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 EMC PowerPath-based names, issue the following command: # oracleasm querydisk -p /dev/emcpower* EMC PowerPath based-device names are being used if the output is similar to the following example. Example 16 EMC PowerPath device names Device "/dev/emcpowera1" is marked an ASM disk with the label "ASM_DISK_*" 1. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication. 2. Uninstall EMC PowerPath by following these steps: CAUTION: EMC PowerPath must not be present during the migration process. The native Linux device-mapper-multipath must be managing the paths. Stop all applications before removing EMC PowerPath. 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. 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. 42 Performing Data Migration for Red Hat Linux and Oracle RAC

43 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 EMC PowerPath from the host, following the EMC PowerPath 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: 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 EMC PowerPath was enabled. For example: multipath { wwid e00029a62ca76d3e411 alias <DEVICE_ALIAS>} The value for alias must match the label used by EMC PowerPath for that device. 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. Example 17 Starting the native device-mapper multipath # /etc/init.d/multipathd restart ok Stopping multipathd daemon: [ OK ] Starting multipathd daemon: [ OK ] Online Data Migration with Removal of EMC PowerPath 43

44 Example 18 Rescanning HBAs and listing the updated multipath mapping with RHEL 5.x # ls /sys/class/fc_host host2 host3 # echo "1" > /sys/class/fc_host/host2/issue_lip # echo "- - -" > /sys/class/scsi_host/host2/scan # echo "1" > /sys/class/fc_host/host3/issue_lip # echo "- - -" > /sys/class/scsi_host/host3/scan # multipath -ll mpath13 ( bf902a00e03cb1bb3c3fe411) dm-4 DGC,VRAID [size=150g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:2 sdg 8:96 [active][ready] \_ 2:0:1:2 sdj 8:144 [active][ready] mpath12 ( bf902a00cae2a2a33c3fe411) dm-3 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:1 sdf 8:80 [active][ready] \_ 2:0:1:1 sdi 8:128 [active][ready] mpath11 ( bf902a002ac0388f3c3fe411) dm-2 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:0 sdb 8:16 [active][ready] \_ 2:0:1:0 sdh 8:112 [active][ready] 4. If EMC PowerPath was uninstalled in step 2, and after multipathing has been configured again on the host, follow these steps: a. If EMC PowerPath 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, EMC PowerPath devices are presented as /dev/emcpower* (for example, /dev/emcpowera). Removal of EMC PowerPath 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 EMC PowerPath, consider combining /dev/sdb and /dev/sdc into /dev/emcpowera. After removal of EMC PowerPath, /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/emcpowera as /var. After removal of EMC PowerPath, /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. 44 Performing Data Migration for Red Hat Linux and Oracle RAC

45 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 EMC PowerPath-based /dev/ emcpower* 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="emcpower" 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 appropriate 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_1" 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 EMC PowerPath 45

46 Example 19 Using createmigration with -migtype online for RHEL 5.x or RHEL 6.x # 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: For Oracle RAC: Using the HP 3PAR Online Import Utility, issue the createmigration command with the -migtype online and -allvolumesincg parameters. Example 20 Using createmigration with -migtype online for Oracle RAC # createmigration -sourceuid xxxxxxxxxxxxxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "RHEL_5_6" This step admits LUNs presented to the EMC Storage system and exports them to the HP 3PAR host created on the EMC 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 21 Issuing the showmigration command # showmigration MIGRATIONID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online SYMMETRIX 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 2 (page 47)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. 46 Performing Data Migration for Red Hat Linux and Oracle RAC

47 Figure 2 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. Online Data Migration with Removal of EMC PowerPath 47

48 Example 22 Rescanning HBAs and listing the updated multipath mapping with RHEL 5.x # ls /sys/class/fc_host host2 host3 # echo "1" > /sys/class/fc_host/host2/issue_lip # echo "- - -" > /sys/class/scsi_host/host2/scan # echo "1" > /sys/class/fc_host/host3/issue_lip # echo "- - -" > /sys/class/scsi_host/host3/scan # multipath -ll mpath13 ( bf902a00e03cb1bb3c3fe411) dm-4 DGC,VRAID [size=150g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:2 sde 8:64 [active][ready] \_ 3:0:0:2 sdg 8:96 [active][ready] \_ 2:0:1:2 sdj 8:144 [active][ready] \_ 3:0:1:2 sdm 8:192 [active][ready] mpath12 ( bf902a00cae2a2a33c3fe411) dm-3 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:1 sdf 8:80 [active][ready] \_ 2:0:0:1 sdd 8:48 [active][ready] \_ 2:0:1:1 sdi 8:128 [active][ready] \_ 3:0:1:1 sdl 8:176 [active][ready] mpath11 ( bf902a002ac0388f3c3fe411) dm-2 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:0 sdb 8:16 [active][ready] \_ 2:0:0:0 sdc 8:32 [active][ready] \_ 2:0:1:0 sdh 8:112 [active][ready] \_ 3:0:1:0 sdk 8:160 [active][ready] 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. Example 23 Output after unzoning the host from the source array with RHEL 5.x # multipath ll mpath13 ( bf902a00e03cb1bb3c3fe411) dm-4 3PARdata,VV [size=150g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:2 sde 8:64 [active][ready] \_ 3:0:1:2 sdm 8:192 [active][ready] mpath12 ( bf902a00cae2a2a33c3fe411) dm-3 3PARdata,VV [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:1 sdd 8:48 [active][ready] \_ 3:0:1:1 sdl 8:176 [active][ready] mpath11 ( bf902a002ac0388f3c3fe411) dm-2 3PARdata,VV [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:0 sdc 8:32 [active][ready] \_ 3:0:1:0 sdk 8:160 [active][ready] 11. Start the migration by using the HP 3PAR Online Import Utility startmigration command. 48 Performing Data Migration for Red Hat Linux and Oracle RAC

49 Example 24 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 volumes have been migrated successfully. Example 25 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online CLARiiON+APM00 3par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Online Data Migration with Native device-mapper Multipath To perform online data migration using RHEL 5.x, RHEL 6.x, or Oracle RAC, follow these steps. NOTE: Before using the HP 3PAR Online Import Utility for Oracle RAC=based configurations, it is critical to verify that the cluster registry, voting, and data disks reside on the same source array and are not distributed across multiple arrays. 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. 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> 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 Native device-mapper Multipath 49

50 Example 26 Starting the native device-mapper multipath # /etc/init.d/multipathd restart ok Stopping multipathd daemon: [ OK ] Starting multipathd daemon: [ OK ] Example 27 Rescanning HBAs and listing the updated multipath mapping with RHEL 5.x # ls /sys/class/fc_host host2 host3 # echo "1" > /sys/class/fc_host/host2/issue_lip # echo "- - -" > /sys/class/scsi_host/host2/scan # echo "1" > /sys/class/fc_host/host3/issue_lip # echo "- - -" > /sys/class/scsi_host/host3/scan # multipath -ll mpath13 ( bf902a00e03cb1bb3c3fe411) dm-4 DGC,VRAID [size=150g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:2 sdg 8:96 [active][ready] \_ 2:0:1:2 sdj 8:144 [active][ready] mpath12 ( bf902a00cae2a2a33c3fe411) dm-3 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:1 sdf 8:80 [active][ready] \_ 2:0:1:1 sdi 8:128 [active][ready] mpath11 ( bf902a002ac0388f3c3fe411) dm-2 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:0 sdb 8:16 [active][ready] \_ 2:0:1:0 sdh 8:112 [active][ready] 3. For 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. For Oracle RAC, you must issue the createmigration command using the -allvolumesincg parameter. Example 28 Using createmigration for RHEL 5.x or RHEL 6.x # createmigration -sourceuid xxxxxxxxxxxxxxxx -srchost "X8dtuf-01" -migtype online destcpg testcpg -destprov full -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 29 Using createmigration for Oracle RAC # createmigration -sourceuid xxxxxxxxxxxxxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "RHEL_5_6" This step admits LUNs presented to the EMC Storage system and exports them to the HP 3PAR host created on the EMC Storage system. NOTE: The createmigration command may take several minutes to complete. 50 Performing Data Migration for Red Hat Linux and Oracle RAC

51 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 30 Issuing the showmigration command # showmigration MIGRATIONID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online SYMMETRIX 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 3 (page 51)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. Figure 3 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. Online Data Migration with Native device-mapper Multipath 51

52 Example 31 Rescanning HBAs and listing the updated multipath mapping with RHEL 5.x # # 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 #multipath -ll mpath13 ( bf902a00e03cb1bb3c3fe411) dm-4 DGC,VRAID [size=150g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:2 sde 8:64 [active][ready] \_ 3:0:0:2 sdg 8:96 [active][ready] \_ 2:0:1:2 sdj 8:144 [active][ready] \_ 3:0:1:2 sdm 8:192 [active][ready] mpath12 ( bf902a00cae2a2a33c3fe411) dm-3 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:1 sdf 8:80 [active][ready] \_ 2:0:0:1 sdd 8:48 [active][ready] \_ 2:0:1:1 sdi 8:128 [active][ready] \_ 3:0:1:1 sdl 8:176 [active][ready] mpath11 ( bf902a002ac0388f3c3fe411) dm-2 DGC,VRAID [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 3:0:0:0 sdb 8:16 [active][ready] \_ 2:0:0:0 sdc 8:32 [active][ready] \_ 2:0:1:0 sdh 8:112 [active][ready] \_ 3:0:1:0 sdk 8:160 [active][ready] 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. Example 32 Output after unzoning the host from the source array with RHEL 5.x # multipath -ll mpath13 ( bf902a00e03cb1bb3c3fe411) dm-4 3PARdata,VV [size=150g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:2 sde 8:64 [active][ready] \_ 3:0:1:2 sdm 8:192 [active][ready] mpath12 ( bf902a00cae2a2a33c3fe411) dm-3 3PARdata,VV [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:1 sdd 8:48 [active][ready] \_ 3:0:1:1 sdl 8:176 [active][ready] mpath11 ( bf902a002ac0388f3c3fe411) dm-2 3PARdata,VV [size=200g][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=0][active] \_ 2:0:0:0 sdc 8:32 [active][ready] \_ 3:0:1:0 sdk 8:160 [active][ready] 9. Start the migration by using the HP 3PAR Online Import Utility startmigration command. 52 Performing Data Migration for Red Hat Linux and Oracle RAC

53 Example 33 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 volumes have been migrated successfully. Example 34 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) online CLARiiON+APM00 3par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Online Data Migration with Native device-mapper Multipath 53

54 7 Performing Minimally Disruptive Migration Using a Windows Host The MDM process is used when migrating a Windows host attached to a source EMC 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 35 createmigration command # createmigration -sourceuid C6E059EE -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 36 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NA- preparationcomplete(100%)(-na-) Updating Host Multipath Software and Unzoning from the Source EMC Storage System CAUTION: EMC PowerPath 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 EMC PowerPath. 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: 54 Performing Minimally Disruptive Migration Using a Windows Host

55 1. If EMC PowerPath software is present, remove it from the host, following the EMC PowerPath documentation instructions. IMPORTANT: If you are uninstalling EMC PowerPath 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. The removal of EMC PowerPath Multipath software may have also disabled the MPIO installation without removing it. Manually check to see whether the native Microsoft 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 EMC Storage System 55

56 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 4 (page 56). The path details are in the Host Details pane. Figure 4 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. 56 Performing Minimally Disruptive Migration Using a Windows Host

57 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 EMC Storage system from the host. Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System 1. From the HP 3PAR Online Import Utility, issue the startmigration command. Example 37 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 38 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM00 3par_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 39 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_01 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 EMC Storage System to Destination HP 3PAR StoreServ Storage System 57

58 Example 40 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_ % TIP: The STATUS column in the showmigration command output will indicate success when all volumes have been migrated successfully. Example 41 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM00 3par_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 42 Unsafe to bring the host online # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_01 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 43 Safe to bring the host online: # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_ % 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. 58 Performing Minimally Disruptive Migration Using a Windows Host

59 TIP: The STATUS column in the showmigration command output will indicate success when all volumes 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 CLARiiON+APM00 3par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Bringing the Windows Host Back Online 59

60 8 Performing Minimally Disruptive Migration Using a Linux Host The MDM type can be used when migrating a Linux host attached to a source EMC 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 and Oracle RAC (page 42). 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 45 createmigration command # createmigration -sourceuid C6E059EE -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 46 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NA- preparationcomplete(100%)(-na-) Updating Host Multipath Software and Unzoning from Source EMC Storage System CAUTION: EMC PowerPath must not be installed during the migration process. Native device-mapper multipath must be managing the paths. Stop all applications before removing EMC PowerPath. 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: 60 Performing Minimally Disruptive Migration Using a Linux Host

61 1. If EMC PowerPath software is present, remove it from the host, following the EMC PowerPath documentation instructions. 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 EMC PowerPath from the host, following the EMC PowerPath 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 5 (page 61)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. Figure 5 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. Updating Host Multipath Software and Unzoning from Source EMC Storage System 61

62 4. Restart device-mapper multipath. 5. If EMC PowerPath 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 EMC Storage system from the host. Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System 1. From the HP 3PAR Online Import Utility, issue the startmigration command. Example 47 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 48 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM 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 49 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS OIU_Test_Lun_01 OIU_Test_Lun_01 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. 62 Performing Minimally Disruptive Migration Using a Linux Host

63 Example 50 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS OIU_Test_Lun_01 OIU_Test_Lun_ % TIP: The STATUS column in the showmigration command output will indicate success when all volumes have been migrated successfully. Example 51 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM00 3par_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 52 Unsafe to bring the host online # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_01 unknown 0% 2. After all volumes have a value for their TASK_ID, bring the Linux host online. Example 53 Safe to bring the host online: # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_ % 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 54 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 63

64 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 volumes have been migrated successfully. Example 55 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM00 3par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) 64 Performing Minimally Disruptive Migration Using a Linux Host

65 9 Performing Minimally Disruptive Migration Using a Hyper-V Host The MDM process is used when migrating a Hyper-V host attached to a source EMC Storage system. The host multipathing solution be updated to communicate with the destination HP 3PAR StoreServ Storage system, and the host must be shutdown 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 56 createmigration command # createmigration -sourceuid C6E059EE -srchost "HPDL585-01" -destcpg FC_r5 -destprov thin -migtype MDM -persona WINDOW_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 task, the STATUS column in the showmigration command output will indicate preparationcomplete(100%). Example 57 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NA- preparationcomplete(100%)(-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 58 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS OIU_Test_Lun_01 OIU_Test_Lun_01 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. Creating the Data Migration Task 65

66 Example 59 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS OIU_Test_Lun_01 OIU_Test_Lun_ % TIP: The STATUS column in the showmigration command output will indicate success when all volumes have been migrated successfully. Example 60 showmigration command showing successful migration # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM00 3par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success(-na-)(-na-) Updating Host Multipath Software and Unzoning from the Source EMC Storage System CAUTION: EMC PowerPath must not be installed during the migration process. Native MPIO must be managing the paths. Stop all applications before removing EMC PowerPath. 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 Hyper-V host: 1. If EMC PowerPath software is present, remove it from the host, following the EMC PowerPath documentation instructions. NOTE: 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. The removal of EMC PowerPath multipath software might have also disabled the MPIO installation, but not removed it. Manually check to see whether native Microsoft MPIO is still loaded, and if it is, fully remove it at this time. Now power off the host and power up again. 3. Check the cluster reservation on the LUNs by shutting down the cluster by performing the following steps: a. Using the Failover Cluster Manager, stop the cluster. b. Clear the cluster reservation by following the appropriate Microsoft documentation about Hyper-V clusters. 4. 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 6 (page 67)). This number of paths is listed in the Node ID(s) column. The path details are in the Host Details pane. 66 Performing Minimally Disruptive Migration Using a Hyper-V Host

67 Figure 6 HP 3PAR Management Console Host Details 5. Configure the MPIO multipath software on the host. a. Install MPIO. 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 power off at this point, as this MDM procedure will already require stopping and restarting the Hyper-V host in the following step. 6. Shut down the Hyper-V host. Leave the host offline until the migration is started. 7. Unzone the source EMC Storage system from the host. Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System To start the data migration, follow these steps: 1. From the HP 3PAR Online Import Utility, issue the startmigration command. Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System 67

68 Example 61 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 62 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) MDM CLARiiON+APM00 3par_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 63 showmigrationdetails command # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_01 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 Test_Lun_01 Test_Lun_ % TIP: The STATUS column in the showmigration command output will indicate success when all volumes have been migrated successfully. TIP: The showmigration command output will indicate success when all volumes 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 CLARiiON+APM00 3par_7200_DCB_01 Fri Apr 04 16:38:24 EDT NA- success (-NA-) (-NA-) 68 Performing Minimally Disruptive Migration Using a Hyper-V Host

69 Bringing the Hyper-V Host Back Online To bring the Hyper-V 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 Test_Lun_01 Test_Lun_01 unknown 0% 2. After the import has started for the volumes, bring the Hyper-V host that was shut down back online. Example 67 Safe to bring the host online # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Test_Lun_01 Test_Lun_ % 3. Bring the quorum and CSV disks back online and start virtual machines from the Failover Cluster Manager. 4. Restart all applications and services. The host can now resume normal operations. Bringing the Hyper-V Host Back Online 69

70 10 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 68 createmigration command # createmigration -sourceuid C6E059EE -srcvolmap [{"EMC_10"}] -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 69 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) Offline CLARiiON+APM par_7200_DCA_01 Wed Mar 26 13:08:19 PDT NA- preparationcomplete(100%)(-na-) NOTE: Unlike during MDM, HP 3PAR Online Import for EMC 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 72). 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. 70 Performing Offline Data Migration

71 Removing the Host from the Storage Group Using the EMC Unisphere tool, remove the hosts from the storage group containing LUNs to be migrated. Starting the Data Migration from Source EMC Storage System to Destination HP 3PAR StoreServ Storage System To start the migration from the source EMC 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 70 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 71 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) Offline CLARiiON+APM 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. # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Volume Volume_00145 unknown 0% Volume Volume_00146 unknown 0% A task ID will be assigned and percentage of progress will be shown while the task is being executed. # showmigrationdetails -migrationid SOURCE_VOLUME DESTINATION_VOLUME TASK_ID PROGRESS Volume Volume_ % Volume Volume_ % Removing the Host from the Storage Group 71

72 TIP: The showmigration command output will indicate success when all volumes have been migrated successfully. Example 72 showmigration command # showmigration -migrationid MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME START_TIME END_TIME STATUS(PROGRESS)(MESSAGE) Offline CLARiiON+APM 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 EMC Storage system from the host. 2. Power up the host. 3. Remove the EMC PowerPath Multipath software, if present, and configure the native OS multipath software. For additional information, see the following: For Windows: Updating Host Multipath Software and Unzoning from the Source EMC Storage System (page 54) For Linux: Updating Host Multipath Software and Unzoning from Source EMC Storage System (page 60) For Hyper-V: Updating Host Multipath Software and Unzoning from the Source EMC Storage System (page 66) 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. Add HBA WWNs to the host entry. d. 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 ( 72 Performing Offline Data Migration

73 11 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 EMC 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 Volume 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 EMC 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. Removing a Storage System from EMC SMI-S Provider Follow this procedure to remove a system from the list after the migration has completed or if you have added the wrong system for migration. CAUTION: You cannot remove a system or abort the migration during the migration process. You can remove the system only before migration begins or after it has completed. 1. In the SMI-S CLI, issue the ein command. When prompted for a Class value, enter: Clar_StorageSystem Viewing Migration Status 73

74 Example 73 Removing the Storage System ++++ Testing EnumerationInstanceNames: Clar_StorageSystem ++++ Instance 0: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name=" CLARiiON+APM Instance 1: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " 2. Issue the SMI-S CLI remsys command. Copy the entire path of the array Instance that you wish to remove. See Example 74 Verifying that the Storage System Has Been Removed. NOTE: The APM value in the object path should match the serial number of the storage system that you wish to remove. 3. At the SMI-S CLI ObjectPatch[null]: prompt, paste the path of the array Instance. 4. Follow the rest of the prompts and look for a message indicating success. When you run an SMI-S CLI dv or ein command, you should no longer see the storage system that you just removed. Example 74 Verifying that the Storage System Has Been Removed (localhost:5988)? dv... Firmware version information: (Remote) CLARiiON Array APM (Rack Mounted CX4_120) : (Remote) CLARiiON Array APM (Rack Mounted VNX5300) : (Remote) CLARiiON Array APM (Rack Mounted VNX5200) : (localhost:5988)? ein Class: Clar_StorageSystem ++++ Testing EnumerationInstanceNames: Clar_StorageSystem ++++ Instance 0: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " Instance 1: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " Instance 2: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " Enumerate 3 instance names; repeat count 1;return data in seconds (localhost:5988)? remsys Remove System {y n} [n]: y System's ObjectPath[null]: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " About to delete system Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " Are you sure {y n} [n]: y ++++ EMCRemoveSystem ++++ OUTPUT : 0 Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed 5=Invalid Parameter 4096=Job Queued, 4097=Size Not Supported Note: Not all above values apply to all methods - see MOF for the method. (localhost:5988)? dv... Firmware version information: (Remote) CLARiiON Array APM (Rack Mounted CX4_120) : (Remote) CLARiiON Array APM (Rack Mounted VNX5300) : Performing Common Migration and Post-migration Tasks

75 12 Troubleshooting This section describes problems you may encounter when using EMC 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 EMC 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 EMC Storage system should be checked for potential problems. HP 3PAR Online Import Utility Error Messages Table 16 (page 75) describes error messages that can occur with the HP 3PAR Online Import Utility. Table 16 Error Messages OIUERRSRC0020 = "Unsupported EMC storage system version "; OIURSLSRC0020 = "Check support matrix and upgrade EMC."; Problem: Source EMC Storage system version check failed. Solution: Source EMC Storage system must be running at supported version. OIUERRSRC0111 = "Unable to present the volume to the host in EMC array"; OIURSLSRC0111 = "Contact HP Support if the problem persists."; Problem: Unable to add HP 3PAR peer port host to source storage system group. Solution: Check the HP 3PAR Online Import Utility log file for specific description of the problem from SMI-S Provider. OIUERRSRC0112 = "Unable to unpresent the volume from the host in EMC array" OIURSLSRC0112 = "Contact HP Support if the problem persists." Problem: Unable to remove HP 3PAR peer port host from source storage system group. Solution: Check the HP 3PAR Online Import Utility log file for specific description of the problem from SMI-S Provider. OIUERRSRC0021 = "There is a active migration on this source. So this source can not be removed."; OIURSLSRC0021 = "Migration have to be complete/abort for source to be removed."; Problem: Tried to issue the HP 3PAR Online Import Utility removemigration command while the specified migration is still in progress. Solution: Wait for migration to complete before removing. OIUERRSRC0022 = "Cannot find specified source Array."; OIURSLSRC0022 = "An Array has to be added first in order to be removed." Problem: Tried to issue the HP 3PAR Online Import Utility removesource command with specific UID and that UID does not exist in the HP 3PAR Online Import Utility database. Solution: Issue the HP 3PAR Online Import Utility showsource command to determine storage systems that are currently known. OIUERRSRC0023 = "You have selected a migration with an unsupported storage group configuration." OIURSLSRC0023 = "Verify that your storage group configuration matched one of the supported configurations." Problem: The LUN associated with the HP 3PAR Online Import Utility createmigration command that was issued is not in a supported storage group configuration. Solution: Review supported storage group configurations in Migrations Supported by HP 3PAR Online Import Utility (page 24) and make appropriate changes before creating the migration. OIUERRAPP0013 = "Unsupported EMC Provider version for SMI-S" HP 3PAR Online Import Utility Error Messages 75

76 Table 16 Error Messages (continued) OIURSLAPP0013 = "Check support matrix and upgrade EMC Provider." Problem: The SMI-S Provider that was entered is running an unsupported version. Solution: Storage systems for migration must be managed by SMI-S Provider with supported version. OIUERRAPP0009 = "Job might have executed successfully but couldn't receive any handle to track it."; OIURSLAPP0009 = "Contact HP Support" Problem: A problem occurred during an SMI-S related job. Solution: Check the HP 3PAR Online Import Utility log file for a specific description of the problem. HP support may be required. OIUERRAPP0010 = "SMI-S EMC Provider WBEM Operations error."; OIURSLAPP0010 = "Please check SMI-S ECOM connectivity and access, see Log file for details, and/or Contact HP Support." Problem: There could be a problem with communication or access. Solution: Logs will show the exact cause as an exception trace. Configuration (remote IP access, local access) of the ECOM might need to be rectified. OIUERRAPP0011 = "EMC Provider WBEM Connection, Malformed URL."; OIURSLAPP0011 = "Application internal error, see Log file for details. Contact HP Support." Problem: This would indicate a defect in accessing the provider due to incorrect protocol (HTTP, HTTPS allowed), or no protocol at all. Solution: Try different combinations of secure settings and port settings in the HP 3PAR Online Import Utility CLI command. Verify enabled ports on the SMI-S provider. OIUERRAPP0012 = "EMC Provider WBEM Connection, Client initialization error."; OIURSLAPP0012 = "Application internal error, see Log file for details. Contact HP Support." Problem: This might be caused by a blank user name or password when connecting to SMI-S provider. Solution: Ensure that the user name and password are specified. OIUERRAPP0015 = "SMI-S EMC Provider Connection error."; OIURSLAPP0015 = "Please check SMI-S ECOM connectivity (IP Address, Port number), see Log file for details, and/or Contact HP Support." Problem: The wrong IP address or wrong port is specified for SMI-S Provider. Solution: Use correct SMI-S Provider and IP address. OIUERRAPP0016 = "SMI-S EMC Provider Authorization error."; OIURSLAPP0016 = "Please check SMI-S ECOM Access Configuration and/or User Credentials, see Log file for details, and/or Contact HP Support." Problem: The SMI-S Provider credentials are wrong, or the HP 3PAR Online Import Utility is not on the trusted client IP address list. Solution: Use correct SMI-S Provider credentials. If Trusted IP Address list is enabled, make sure the HP 3PAR Online Import Utility server is on the trusted IP address list on the ECOM server. 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 EMC Storage is Unisphere; for the HP 3PAR StoreServ Storage, it is the HP 3PAR Online Import Utility management interface. This section provides an 76 Troubleshooting

77 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: The HP 3PAR peer ports are added into the storage group which contains the LUNs/hosts that are being migrated (will display with name=unknown) 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: Hosts are removed from the storage group (except 3PAR peer port hosts) On the destination storage system: LUNs are presented to the hosts (MDM) Import is started Once the migration is completed: The HP 3PAR peer ports are removed from the source storage system group 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. Troubleshooting Resources 77

78 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. 78 Troubleshooting

79 EMC SMI-S Provider Server Logs and Output When an issue occurs, get all the EMC SMI-S Provider 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 to get the EMC SMI-S Provider logs: Windows: C:\Program Files\EMC\ECIM\ECOM\log\cimomlog Get EMC SMI-S Provider output by issuing these commands: dv command to see EMC SMI-S Provider version information and lists of storage systems being managed by EMC SMI-S Provider. Example 75 dv command (localhost:5988)? dv eq command to see storage system information in the format that is being passed to the EMC plugin for all storage systems being managed by the EMC SMI-S Provider. NOTE: below. Select statement parameters are case-sensitive and should be entered as displayed Example 76 eq command (localhost:5988)? eq Query Language[DMTF:CQL]: Query []: select Tag,ElementName,Manufacturer,Model from Clar_ArrayChassis Increasing the EMC SMI-S Provider Server Logging Level Perform the following steps to set the SMI-S log to the most verbose level: 1. Log into the ECOM administration interface. 2. Select Log Options. 3. Set the Log file to CIMOMLOG. 4. Set the Log Severity to NAVI_TRACE. 5. Set Trace Settings to turn on all 3 traces. 6. Save the Log Setting. Troubleshooting Communication Between the HP 3PAR Online Import Utility Server and EMC SMI-S Provider 1. In the HP 3PAR Online Import Utility server, issue the showsource command. 2. Execute the desired URL from the HP 3PAR Online Import Utility server: Secure: Server IP address>:<port>/ecomconfig Unsecure: Server IP address>:<port>/ecomconfig 3. Replace these variables: <SMI-S Server IP address> with the Management_Server IP address displayed in HP 3PAR Online Import Utility showsource output. <port> with the port that was used when the addsource command was issued The unsecure port default is 5988 The secure port default is 5989 Troubleshooting Resources 79

80 4. If the SMI-S Provider ECOM login page does not appear, check the following: Make sure you have the correct IP address for SMI-S Provider server. Make sure you are using the correct port for the EMC SMI-S Provider server. Log into the EMC SMI-S Provider server and look at the port configuration file which shows which ports are enabled for use and whether they are expecting a secure or unsecure connection. Windows: C:\Program Files\EMC\ECIM\ECOM\conf\Port_settings.xml Make sure there is network connectivity between the HP 3PAR Online Import Utility server and the EMC SMI-S Provider. NOTE: Determine whether SMI-S Client filtering is enabled. If enabled, your HP 3PAR Online Import Utility server must be on the Trusted client IP list. Make sure that the SMI-S Provider is running. Windows Check that the EMC SMI-S Provider (ECOM/EMC) services are started: 5. If the ECOM login page does appear, login using the credentials that you used when you issue the HP 3PAR Online Import Utility addsource command. If that fails, then you need to determine which are the correct credentials. TestSmiProvider Login and Command Examples with Output 1. Start SMI-S Provider TestSmiProvider tool. SMI-S Provider on Windows: 80 Troubleshooting

81 Example 77 Output on Windows C:\Program Files\EMC\ECIM\ECOM\bin>TestSmiProvider.exe Connection Type (ssl,no_ssl,native) [no_ssl]: Host [localhost]: Port [5988]: Username [admin]: Password [#adminpw]: adminpw Log output to console [y n (default y)]: Log output to file [y n (default y)]: Logfile path [Testsmiprovider.log]: Connecting to localhost:5988 Using user account 'admin' with password 'adminpw' ######################################################################## ## ## ## EMC SMI Provider Tester ## ## This program is intended for use by EMC Support personnel only. ## ## At any time and without warning this program may be revised ## ## without regard to backwards compatibility or be ## ## removed entirely from the kit. ## ######################################################################## slp - slp urls slpv - slp attributes cn - Connect dc - Disconnect disco - EMC Discover rc - RepeatCount addsys - EMC AddSystem remsys - EMC RemoveSystem refsys - EMC RefreshSystem ec - EnumerateClasses ecn - EnumerateClassNames ei - EnumerateInstances ein - EnumerateInstanceNames ens - EnumerateNamespaces miner - Mine classes a - Associators an - AssociatorNames r - References rn - ReferenceNames gi - GetInstance gc - GetClass i - CreateInstance di - DeleteInstance mi - ModifyInstance eq - ExecQuery gp - GetProperty sp - SetProperty tms - TotalManagedSpace tp - Test pools ecap - Extent Capacity pd - Profile Discovery im - InvokeMethod active - ActiveControls ind - Indications menu tv - Test views st - Set timeout value lc - Log control sl - Start listener dv - Display version info ns - NameSpace vtl - VTL menu chp - consolidated host provider menu q - Quit h - Help ######################################################################## Built with EMC SMI-S Provider: V4.6.1 Namespace: root/emc repeat count: 1 (localhost:5988)? 2. Use the dv command in the TestSmiProvider tool to see: SMI-S Provider version information List of storage systems being managed by SMI-S Provider Troubleshooting Resources 81

82 Example 78 dv command output (localhost:5988)? dv ++++ Display version information ++++ CIM ObjectManager Name: EMC:XX.XX.XX.XX CIMOM Version: EMC CIM Server Version SMI-S qualified version: SMI-S Provider version: V SMI-S Provider Location: Proxy SMI-S Provider Server: Windows_NT WinSrv2008-testB Service Pack 1 x86_64 VM Guest OS (64bit Libraries) Solutions Enabler version: V Firmware version information: (Remote) CLARiiON Array APM (Rack Mounted CX4_120) : (Remote) CLARiiON Array APM (Rack Mounted VNX5300) : Retrieve and Display data - 1 Iteration(s) In Seconds Please press enter key to continue Use the eq command in the TestSmiProvider tool to see storage system information in the format that is being passed to the EMC plugin for all storage systems being managed by the SMI-S Provider. NOTE: Some statement parameters are case-sensitive and should be entered as displayed. 82 Troubleshooting

83 Example 79 eq command output (localhost:5988)? eq Query Language[DMTF:CQL]: Query []: select Tag,ElementName,Manufacturer,Model from Clar_ArrayChassis ++++ Testing ExecQuery: ++++ Instance 0: ObjectPath : // /root/emc:Clar_ArrayChassis.CreationClassName="Clar_ArrayChassis",Tag="CLARiiON+APM " <INSTANCE CLASSNAME="Clar_ArrayChassis" > <PROPERTY NAME="Tag" TYPE="string"> <VALUE>CLARiiON+APM </VALUE> </PROPERTY> <PROPERTY NAME="ElementName" TYPE="string"> <VALUE>CLARiiON Array APM </VALUE> </PROPERTY> <PROPERTY NAME="Manufacturer" TYPE="string"> <VALUE>EMC Corporation</VALUE> </PROPERTY> <PROPERTY NAME="Model" TYPE="string"> <VALUE>Rack Mounted CX4_120</VALUE> </PROPERTY> </INSTANCE> Number of instance qualifiers: 0 Number of instance properties: 4 Property: Tag Number of qualifiers: 0 Property: ElementName Number of qualifiers: 0 Property: Manufacturer Number of qualifiers: 0 Property: Model Number of qualifiers: 0 Instance 1: ObjectPath : // /root/emc:Clar_ArrayChassis.CreationClassName="Clar_ArrayChassis",Tag="CLARiiON+APM " <INSTANCE CLASSNAME="Clar_ArrayChassis" > <PROPERTY NAME="Tag" TYPE="string"> <VALUE>CLARiiON+APM </VALUE> </PROPERTY> <PROPERTY NAME="ElementName" TYPE="string"> <VALUE>CLARiiON Array APM </VALUE> </PROPERTY> <PROPERTY NAME="Manufacturer" TYPE="string"> <VALUE>EMC Corporation</VALUE> </PROPERTY> <PROPERTY NAME="Model" TYPE="string"> <VALUE>Rack Mounted VNX5700</VALUE> </PROPERTY> </INSTANCE> Number of instance qualifiers: 0 Number of instance properties: 4 Property: Tag Number of qualifiers: 0 Property: ElementName Number of qualifiers: 0 Property: Manufacturer Number of qualifiers: 0 Property: Model Number of qualifiers: 0 Instance 2: ObjectPath : // /root/emc:Clar_ArrayChassis.CreationClassName="Clar_ArrayChassis",Tag="CLARiiON+APM " <INSTANCE CLASSNAME="Clar_ArrayChassis" > <PROPERTY NAME="Tag" TYPE="string"> <VALUE>CLARiiON+APM </VALUE> </PROPERTY> <PROPERTY NAME="ElementName" TYPE="string"> <VALUE>CLARiiON Array APM </VALUE> </PROPERTY> <PROPERTY NAME="Manufacturer" TYPE="string"> <VALUE>EMC Corporation</VALUE> </PROPERTY> <PROPERTY NAME="Model" TYPE="string"> <VALUE>Rack Mounted VNX5300</VALUE> </PROPERTY> </INSTANCE> Number of instance qualifiers: 0 Number of instance properties: 4 Property: Tag Number of qualifiers: 0 Property: ElementName Number of qualifiers: 0 Property: Manufacturer Number of qualifiers: 0 Property: Model Number of qualifiers: 0 ExceQuery 3 instances; repeat count 1;return data in seconds Retrieve and Display data - 1 Iteration(s) In Seconds Please press enter key to continue... Troubleshooting Resources 83

84 Troubleshooting Issues Cannot Add a Source EMC Storage system Problem: The addsource command fails. Possible causes: The EMC SMI-S Provider 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 EMC SMI-S Provider. An invalid IP address or port (secure/unsecure) is provided for the EMC SMI-S Provider. The EMC SMI-S Provider has client IP address filtering enabled and the HP 3PAR Online Import Utility server is not on the trusted IP address list. The EMC SMI-S Provider is not managing the EMC Storage system. The HP 3PAR Online Import Utility server and the EMC SMI-S Provider do not have network connectivity. The EMC SMI-S Provider and EMC Storage system do not have network connectivity. The EMC 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: 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. EMC SMI-S Provider is running an unsupported software version. The EMC SMI-S Provider user name/password have changed since source storage system was added. The EMC SMI-S Provider is not managing the EMC Storage system. The HP 3PAR Online Import Utility server and the EMC SMI-S Provider do not have network connectivity. EMC SMI-S Provider and EMC Storage system do not have network connectivity. The EMC Storage system is running an unsupported firmware version. The LUNs or host provided are in an invalid storage group configuration. 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 EMC 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 80 HP 3PAR Online Import Utility login error. Example 80 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. Migration Includes Unexpected LUNs and Hosts Problem: When the SMI-S provider manages multiple EMC VMAX Storage systems, LUNs with the same device ID or a host with the same name can result in the createmigration command migrating unexpected LUNs and hosts. Workaround: SMI-S provider used during migration should only manage VMAX that is being migrated. Masking View Required for Offline Migration of LUN with No Host Problem: If you are migrating a LUN without a host, it still needs to be in a masking view in order to be successfully migrated. Workaround: The LUN must be added to a storage group and the storage group must be part of a masking view on the EMC VMAX Storage system. HP 3PAR Online Import Utility Does Not Distinguish between Source Arrays When Managing the Same Host Problem: The SMI-S provider is managing more than one array which have the same host in different storage groups on each array. This problem occurs when the HP 3PAR Online Import Utility asks the SMI-S provider to retrieve host information. If the same host is on two arrays, you will get LUNs on both source arrays. Workaround: The SMI-S provider should not manage multiple arrays where the same host is provisioned in different storage groups. In cases where the SMI-S provider is installed only for migration, only the array being migrated should be added. In cases where the SMI-S provider is already installed and being used by some other application, a separate SMI-S provider should be installed for the migration. 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: Troubleshooting Issues 85

86 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: Could not process your request. Illegal character in authority at index... 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. The adddestination Command Returns Error OIUERRDST0004 Problem: When you issue the HP 3PAR Online Import Utility adddestination command, error OIUERRDST0004 is displayed. See Figure 7 (page 86) 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. Figure 7 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 createmigration Command Fails for Migrated LUNs in a Storage Group with No Host Problem: When you issue the createmigration for LUNs in a storage group that has no host, the command fails. Cause: LUNs in a storage group without a host cannot be migrated. 86 Troubleshooting

87 Solution: For LUNs that do not have an associated host, you must use the offline migration type. 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 LUN name or 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 LUN or 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 storage group containing LUNs identified for migration contains a replication LUN. Solution: Remove the replication LUN from the storage 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 storage group. Solution: Add the LUNs to be migrated into the storage 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 storage group, even if the WWN is not managing any LUNs. Subsequent migration of any WWN for this host will find a match. Troubleshooting Issues 87

88 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. 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 81 createmigration command and error OIUERRCS1002. Example 81 createmigration command and error OIUERRCS1002 # createmigration -sourceuid BEA 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 82 createmigration command with -srcvolmap and error OIUERRAPP0000. Example 82 createmigration command with -srcvolmap and error OIUERRAPP0000 # createmigration -sourceuid C6E0167A -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 83 Successful createmigration command with -srcvolmap. 88 Troubleshooting

89 Example 83 Successful createmigration command with -srcvolmap # createmigration -sourceuid C6E0167A -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..." Solution: Increase the size of the source LUN on the EMC Storage array to a minimum of 256 MB, and then retry the createmigration command. The startmigration Command Fails with Host Name That Exceeds 31 Characters Problem: When you migrate a host with a long name or a name with spaces, 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. Troubleshooting Issues 89

90 13 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 90 Appendices DESCRIPTION The addsource command adds a source storage system to the HP 3PAR Online Import Utility that is intended to be migrated.

91 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: VNX CX VMAX 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. 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 by the same SMI-S server. IP address of the SMI-S provider system that is managing storage system that is being added. User name for SMI-S Provider that is managing storage system that is being added. Password for the user of the SMI-S provider 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 EMC SMI-S Provider. Options are: true false The default setting is -secure true. EXAMPLE # addsource -type VNX -mgmtip XX.XX.XX.XX -user admin -password adminpw -uid xxxxxxxxxxxxxxxx # SUCCESS: Added source storage system. Appendix A: HP 3PAR Online Import Utility CLI Commands 91

92 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 values for the type parameter are VNX, CX, or VMAX. 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 EMC 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 storage group on the associated source EMC Storage system. All LUNs and all hosts in the mapped storage group will be migrated even if only a subset are entered in the createmigration command. 92 Appendices

93 PARAMETERS Parameter sourceuid srcvolmap or volmapfile srchost 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. Description Source storage system WWN. 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: vdisk4,thin,cpg1 vdisk2,full,cpg2 vdisk2,dedupe,cpg2 Any implicitly defined volumes will get their provisioning type from the value of -destprov, and their CPG from the value of -destcpg. Possibilities: vdisk, thin vdisk, cpg vdisk vdisk, thin, cpg vdisk,dedupe,cpg For VMAX, use the following format: Volume <device id> The <device id> value must be five characters in length. If the actual device ID is less than five characters, add 0 at the front to make five characters. For example, if the VMAX device ID is 0192: createmigration -sourceuid C012F400 -srcvolmap [{"Volume 00192"}] -destcpg testcpg1 -destprov thin -migtype MDM -persona "RHEL_5_6" 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. For VMAX, use the name of the initiator group on the VMAX that contains the initiator WWN that is being migrated. If nested initiator groups are being used, the parent initiator group (which Appendix A: HP 3PAR Online Import Utility CLI Commands 93

94 Parameter destprov destcpg cgvolmap allvolumesincg migtype destinationuid persona Mandatory/Optional Optional Optional Defaults to offline Optional Mandatory for online migration and MDM Description does not have a direct reference to a WWN) cannot be used. 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 EMC Storage system, the supported migration type is MDM or offline. UID of the destination storage system. Since only one destination storage 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 C6E059EE -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 AF0002AC001BA1 -srcvolmap "[{vol1, thin, testcpg},{vol2, thin, testcpg},{vol3, thin, testcpg}]" -destcpg testcpg -destprov testcpg -cgvolmap{ values":{"cg1":["vol1","vol2"]}} -persona RHEL_5_6 To create migration with mixed provisioning (for example, with a single LUN to be thinemc 1 to be thin, but others to be fully provisioned), issue the following command: # createmigration -sourceuid C6E059EE -srcvolmap [{"EMC_1", thin, FC_r5}] -destcpg FC_r5 -destprov full -migtype MDM -persona WINDOWS_2008_R2 # SUCCESS: Migration job submitted successfully. Please check status/details using 94 Appendices

95 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 startmigration removesource addsource installcertificate showconnection createmigration removedestination help showdestination adddestination 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 -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. Appendix A: HP 3PAR Online Import Utility CLI Commands 95

96 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. 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. 96 Appendices

97 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. 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 Source storage system WWN. Type of storage system: VNX CX VMAX EXAMPLE # removesource uid BEE0177F type VNX 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 Appendix A: HP 3PAR Online Import Utility CLI Commands 97

98 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 Source storage system WWN. In accordance with HP 3PAR Online Import Utility documentation. EXAMPLE # showconnection -source BEE0177F SOURCE_NAME SOURCE_UNIQUE_ID DESTINATION_NAME DESTINATION_UNIQUE_ID DESTINATION_PEER_PORT SOURCE_HOST_PORT CLARiiON+APM BEE0177F 3PAR_Array_1 2FF70002DY005F DY00-5F92(0:2:4) EE0-177F(Port SP_B:0) CLARiiON+APM BEE0177F 3PAR_Array_1 2FF70002DY005F DY00-5F92(0:2:4) EE0-177F(Port SP_A:0) 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 Mandatory/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. This is serial number or WWN or hyphenated WWN of the destination storage system. List of host ports hyphenated 64 bit WWN (N:S:P). Peer will be marked as peer. 98 Appendices

99 listcols firmware management_server operational_state Optional Optional Optional Optional 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. 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 Mandatory/optional Optional Optional Optional Optional Optional Optional Optional Description Online/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. Appendix A: HP 3PAR Online Import Utility CLI Commands 99

100 listcols sourcename destinationname Optional Optional Optional 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 CLARiiON+APM DMMT3PAR02 Sat Apr 12 00:52:38 IST NA- preparationcomplete(100%)(-na-) 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 Mandatory/optional Mandatory 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 100 Appendices

101 sourcevolume destinationvolume Optional Optional 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 test test 6134 Completed showpersona DESCRIPTION This command displays the supported destination HP 3PAR host entry persona values for all the specified host operating systems. PARAMETERS Table 17 Host Persona HOSTYPE windows2012 sunsolaris sunsolaris ibmaix hpux windows2008 vmware linux linux openvms mswindows windows2012 sunsolaris sunsolaris ibmaix hpux hpux windows2008 vmware 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 Appendix A: HP 3PAR Online Import Utility CLI Commands 101

102 Table 17 Host Persona (continued) HOSTYPE linux linux openvms mswindows OSVERSION HOSTPERSONA 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 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_ Appendices

103 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: CLARiiON+APM Storage system family name: CX VNX VMAX Storage system WWN. Firmware version of the source storage system. IP address of the SMI-S Provider that is managing storage systems. Operational state of the storage system. EXAMPLE # showsource type VNX NAME TYPE UNIQUE_ID FIRMWARE MANAGEMENT_SERVER OPERATIONAL_STATE CLARiiON+APM VNX BEE0177F 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. Once the data transfer is complete, export to the source host will be executed if the data migration type is MDM. At the source storage system, the presentation of the source volume to the source host will be removed. If possible, the source volume will be locked but not deleted. 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. Appendix A: HP 3PAR Online Import Utility CLI Commands 103

104 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 EMC 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 DGC, VRAID 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 DGC, VRAID 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 DGC, VRAID # cat /sys/block/sdg/device/model DGC, VRAID DGC, VRAID # cat /sys/block/sdp/device/model VV # cat /sys/block/sdl/device/model VV Paths sde and sdg belong to the EMC 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. Appendix B: Identifying and Deleting Source Array LUN Paths 105

106 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 8 (page 107) shows a general overview of the rollback process for a failed online migration. 106 Appendices

107 Figure 8 Rollback process for a failed online migration *For HP 3PAR OS MU3 or later, see Appendix D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later (page 109). For HP 3PAR OS MU2 or earlier, see Appendix E: Clearing a Persistent SCSI Reservation from EMC Storage Arrays with HP 3PAR OS MU2 or Earlier (page 110). Figure 9 (page 108) shows a general overview of the rollback process for a failed MDM. Appendix C: Rolling Back to the Original Source Array 107

108 Figure 9 Rollback process for a failed MDM *For HP 3PAR OS MU3 or later, see Appendix D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later (page 109). For HP 3PAR OS MU2 or earlier, see Appendix E: Clearing a Persistent SCSI Reservation from EMC Storage Arrays with HP 3PAR OS MU2 or Earlier (page 110). 108 Appendices

109 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 106). 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 84 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 D: Clearing a Persistent SCSI Reservation with HP 3PAR OS MU3 or Later 109

110 Appendix E: Clearing a Persistent SCSI Reservation from EMC Storage Arrays with HP 3PAR OS MU2 or Earlier HP Online Import for EMC Storage sets a SCSI reservation on the EMC Storage source storage device (LUN) during its import to the HP 3PAR array to ensure exclusive access by the HP 3PAR peer ports. With HP 3PAR OS MU3 or later, the SCSI reservation is automatically cleared after the HP 3PAR copy task is successfully completed. However, the SCSI reservation might not be cleared automatically in some scenarios, such as when an earlier version of HP 3PAR OS is on the destination array, or if an import fails. With HP 3PAR OS MU2 and earlier, the SCSI reservation is not automatically cleared after an HP 3PAR copy task is completed. Removing a Persistent SCSI Reservation from an EMC CX4 or VNX Device To remove a SCSI reservation on an EMC CX4 or VNX array, remove the HP 3PAR Peer Port initiator WWPNs from the storage group used for migration. The HP 3PAR Peer Port initiator WWPNs can be removed by using EMC s Navisphere CLI (NAVISECCLI) commands. For more information, see the latest edition of the EMC Navisphere Command Line Interface (CLI) Reference, available at the following website: EMC Storage ( NOTE: This link will take you outside the Hewlett-Packard website. HP does not control and is not responsible for information outside hp.com. In the following procedure, HP 3PAR Peer Port initiators 20:11:02:02:AC:00:73:62 and 20:11:02:02:AC:00:73:62 are removed from the EMC storage group R115-S09: 1. Issue the naviseccli command to find the EMC storage group that contains the HP 3PAR Peer Port WWPNs: # naviseccli -address storagegroup list Storage Group Name: R115-S09 Storage Group Storage Group UID: C6:7F:A9:19:DD:E9:E3:11:98:C0:00:60:16:5F:8A:FF HBA/SP Pairs: HBA UID SP Name SPPort :01:43:80:02:3C:BE:E9:50:01:43:80:02:3C:BE:E8 SP B 0 50:01:43:80:02:3C:BE:EB:50:01:43:80:02:3C:BE:EA SP A 1 2F:F7:02:02:AC:00:73:62:21:11:02:02:AC:00:73:62 SP A 0 50:01:43:80:02:3C:BE:EB:50:01:43:80:02:3C:BE:EA SP B 1 2F:F7:02:02:AC:00:73:62:20:11:02:02:AC:00:73:62 SP B 1 50:01:43:80:02:3C:BE:E9:50:01:43:80:02:3C:BE:E8 SP A 0 HLU/ALU Pairs: HLU Number ALU Number Shareable: YES 2. Remove both HP 3PAR Peer Port initiator WWPNs from the EMC storage group: # naviseccli -address storagegroup -disconnecthost -host 2F:F7:02:02:AC:00:73:62:21:11:02:02:AC:00:73:62 -gname "R115-S09 Storage Group" -o # naviseccli -address storagegroup -disconnecthost -host 2F:F7:02:02:AC:00:73:62:20:11:02:02:AC:00:73:62 -gname "R115-S09 Storage Group" -o 110 Appendices

111 Removing a Persistent SCSI Reservation from an EMC VMAX Device Use EMC Solutions Enabler Symmetrix CLI (SYMCLI) commands to clear the SCSI reservation from a LUN. See the EMC Solutions Enabler Symmetrix CLI Command Reference, which is available on the following website: language=en_us ( In the following procedure, a SCSI reservation is removed from a VMAX device, LUN 0C4. 1. Issue the symdev command to verify that there is a persistent reservation on the device: Example 85 showvv command # symdev -sid 1234 list -pgr Symmetrix ID : Device Reservation Sym Config Init SA :P WWN Key A9 TDEV 00 01F: AC00B08A b08a C4 TDEV 00 01E: AC00B08A b08a C5 TDEV 00 01E: AC00B08A b08a List the storage groups containing the device: # symaccess -sid 1234 list -type storage dev 0c4 Symmetrix ID : Storage Group Name OIU_ _SG R65-S02-SG 3. If the device is part of an HP 3PAR Online Import Utility storage group, delete the entire HP 3PAR Online Import Utility masking view. # symaccess -sid 1234 delete view -noprompt -name OIU_ _MV # symaccess -sid 1234 delete -type initiator -force -noprompt -name OIU_ _IG # symaccess -sid 1234 delete -type initiator -force -noprompt -name HOST_FOR R1231_ # symaccess -sid 1234 delete -type initiator -force -noprompt -name HOST_FOR R1232_ # symaccess -sid 1234 delete -type storage -force -noprompt -name OIU_ _SG # symaccess -sid 1234 delete -type port -force -noprompt -name OIU_ _PG 4. Remove the device from the server storage group. NOTE: A storage group associated with a masking view cannot be empty. If multiple devices in the storage group have SCSI reservations, then these steps must be run against each device one at a time. # symaccess -sid name R65-S02-SG -type storage remove dev 0C4 5. Modify the device that was removed from the storage group to be in the not_ready state: # symdev -sid 1234 noprompt not_ready 0C4 'Not Ready' Device operation successfully completed for the device. 6. Unmap the device using the three symconfigure commands shown in the following example: # symconfigure -sid 1234 noprompt -cmd "unmap dev 0C4 from dir ALL:ALL;" preview A Configuration Change operation is in progress. Please wait... Establishing a configuration change session...established. Processing symmetrix Performing Access checks...allowed. Checking Device Reservations...Allowed. Locking devices...locked. Validating configuration changes...validated. Appendix E: Clearing a Persistent SCSI Reservation from EMC Storage Arrays with HP 3PAR OS MU2 or Earlier 111

112 Closing configuration change request...closed. Terminating the configuration change session...done. The configuration change session has completed successfully. # symconfigure -sid 1234 noprompt -cmd "unmap dev 0C4 from dir ALL:ALL;" prepare A Configuration Change operation is in progress. Please wait... Establishing a configuration change session...established. Processing symmetrix Performing Access checks...allowed. Checking Device Reservations...Allowed. Locking devices...locked. Validating configuration changes...validated. Closing configuration change request...closed. Terminating the configuration change session...done. The configuration change session has completed successfully. # symconfigure -sid 1234 noprompt -cmd "unmap dev 0C4 from dir ALL:ALL;" commit A Configuration Change operation is in progress. Please wait... Establishing a configuration change session...established. Processing symmetrix Performing Access checks...allowed. Checking Device Reservations...Allowed. Locking devices...locked. Initiating COMMIT of configuration changes...queued. COMMIT requesting required resources...obtained. Step 004 of 028 steps...executing. Local: COMMIT...Done. Terminating the configuration change session...done. The configuration change session has successfully completed. 7. Confirm that the device is no longer listed as a device with a reservation: # symdev -sid 1234 list -pgr Symmetrix ID : Device Reservation Sym Config Init SA :P WWN Key A9 TDEV 00 01F: AC00B08A b08a C5 TDEV 00 01E: AC00B08A b08a Confirm that the device is unmapped: # symdev -sid 1234 list -noport Symmetrix ID: Device Name Directors Device Cap Sym Physical SA :P DA :IT Config Attribute Sts (MB) F5 Not Visible???:? 08C:D0 2-Way Mir N/Grp'd (M) RW FD Not Visible???:? 08C:D2 2-Way Mir N/Grp'd (M) RW C4 Not Visible???:? 08C:D4 2-Way Mir N/Grp'd (M) RW D Not Visible???:? 08A:C1 2-Way Mir N/Grp'd (M) RW Not Visible???:? 08A:C3 2-Way Mir N/Grp'd (M) RW Modify the device to be in the ready state: # symdev -sid 1234 noprompt ready 0C4 The device is already in the requested state 10. Add the device and verify that it has been added back into the storage group: # symaccess -sid name R65-S02-SG -type storage -dev 0C4 add # symaccess -sid 1234 show R65-S02-SG -type storage 112 Appendices

113 Symmetrix ID : Storage Group Name : R65-S02-SG Last updated at : 05:10:54 PM on Tue Aug 26,2014 Devices : 00C3,00C4 Masking View Names { HPDL MV } 11. Repeat steps 4 10 for each device for which a reservation must be removed. Appendix E: Clearing a Persistent SCSI Reservation from EMC Storage Arrays with HP 3PAR OS MU2 or Earlier 113

114 14 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 114 Support and Other Resources

115 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 HP 3PAR documentation 115

116 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 116 Support and Other Resources

117 Typographic conventions Table 18 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. Typographic conventions 117

118 15 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. 118 Documentation feedback

119 Glossary ASM controller CPG DM FCoE firmware (controller software) HP SPOCK iscsi MDM MPIO MSFC presentation (to host) redundancy level (Vraid) remote replication RHEL SMI-S snapclone storage group TDVV TPVV WWN WWPN 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 ( Automatic Storage Management EMC Storage term for node or controller node common provisioning group Device-mapper Fibre Channel over Ethernet EMC Storage term for HP 3PAR Operating System HP Single Point of Connectivity Knowledge. Internet Small Computer System Interface minimally disruptive migration multipath input/output Microsoft Failover Cluster EMC Storage term for export (to host) EMC Storage term for RAID EMC Storage term for remote copy Red Hat Enterprise Linux Storage Management Initiative Specification EMC Storage term for physical copy EMC Storage term for common provisioning group (CPG) thinly provisioned deduplicated virtual volume thinly provisioned virtual volume World Wide Name World Wide Port Name 119

120 Index A aborting a migration, 73 adddestination CLI command, 90 adding destination storage system, 36 source storage system, 36 addsource CLI command, 90 B bringing online Hyper-V host, 69 Linux host, 63 Windows host, 58 C checklist migration process, 8 migration MDM, 11 migration offline, 13 migration online, 8, 9 post-migration MDM, 11 post-migration offline, 13 post-migration online, 9 premigration MDM, 10 premigration offline, 12 premigration online, 8 prerequisite component installation MDM, 9 prerequisite component installation offline, 12 prerequisite component installation online, 8 CLARiiON CX4 Ethernet connection, 14 CLI commands, 90 adddestination, 8, 10, 12, 36, 73, 86, 90 adddestination -secure, 37 addsource, 8, 10, 12, 36, 73, 77, 79, 80, 84, 90 createmigration, 9, 10, 12, 28, 29, 40, 41, 54, 60, 65, 70, 86, 87, 88, 92 createmigration -allvolumesincg, 45, 50 createmigration -destcpg, 88 createmigration -destprov, 88 createmigration -migtype online, 45, 50 createmigration -srcvolmap, 88 help, 95 installcertificate, 37, 96 removedestination, 9, 12, 13, 96 removemigration, 73, 75, 97 removesource, 9, 12, 13, 75, 97 showconnection, 78, 97 showdestination, 10, 37, 78, 98 showmigration, 46, 51, 54, 60, 62, 68, 70, 71, 73, 89, 99 showmigration -migrationid, 57, 73 showmigration -source, 73 showmigration migrationid, 78 showmigrationdetails, 57, 58, 62, 63, 65, 68, 69, 100 showmigrationdetails -migrationid, 73, 78 showpersona, 101 showsource, 36, 75, 78, 79, 103 showtarget -rescan, 35 startmigration, 11, 13, 48, 52, 57, 62, 67, 71, 89, 103 client IP filtering, 16 command prompt Windows, 15 addsys, 15 disco, 15 dv, 16 testsmiprovider, 15 communication troubleshooting, 79 configuration HP SPOCK, 8, 9, 12 configuration rules, 14 configuring MPIO software on the host, 56 multipath software, 72 SMI-S Provider on Windows, 15 considerations when migrating data, 29 controller, 31 conventions text symbols, 117 createmigration CLI command, 92 creating data migration task, 39, 40, 70 D data migration, 6 aborting, 73 considerations, 29 explicit, 6 implicit, 6 installation and setup, 14 performing, 54, 60, 65 planning for, 30 preparing for, 29 process, 76 starting, 57, 67 types, 6 viewing, 73 Windows clusters, 37 data migration task creating, 39, 40, 70 destination storage system adding, 36 documentation providing feedback on, Index

121 dv SMI-S Provider command, 79 TestSmiProvider command, 81 E EMC and HP 3PAR, 119 EMC MirrorView, 30 EMC PowerPath removing, 61 vs native MPIO, 66 EMC Powerpath, 54 EMC PowerPath Multipath, 72 fully removing, 55 EMC SMI-S Provider installing, 14 EMC Solutions Enabler installing, 14 EMC Storage-to-HP 3PAR StoreServ Storage online import overview, 6 eq SMI-S Provider command, 79 TestSmiProvider command, 82 errors adddestination command unsupported HP 3PAR OS version, 86 createmigration command host already exists, 87 migrated LUNs with no host, 86 no associated LUNs in storage group, 87 no one-to-one mapping between ports, 88 special characters, 87 unexpected error, 87 createmigration command with -srcvolmap unexpected error, 88 HP 3PAR Online Import Utility, 75 HP 3PAR Online Import Utility does not open, 85 installcertificate command, 37 invalid credentials, 85 OIUERRAPP0000, 87, 88 OIUERRAPP0009, 76 OIUERRAPP0010, 76 OIUERRAPP0011, 76 OIUERRAPP0013, 75 OIUERRAPP0015, 76 OIUERRAPP0016, 76 OIUERRCS1002, 88 OIUERRDB1006, 87 OIUERRDST0004, 86 OIUERRDST0008, 89 OIUERRDST0010, 37 OIUERRMS10006, 89 OIUERRPREP1014, 87 OIUERRSRC0020, 75 OIUERRSRC0021, 75 OIUERRSRC0022, 75 OIUERRSRC0023, 75 OIUERRSRC0111, 75 OIUERRSRC0112, 75 OIURSLAPP0000, 87 OIURSLAPP0009, 76 OIURSLAPP0010, 76 OIURSLAPP0011, 76 OIURSLAPP0012, 76 OIURSLAPP0013, 76 OIURSLAPP0015, 76 OIURSLAPP0016, 76 OIURSLSRC0020, 75 OIURSLSRC0021, 75 OIURSLSRC0022, 75 OIURSLSRC0023, 75 OIURSLSRC0111, 75 OIURSLSRC0112, 75 showmigration command for LUN smaller than 256 MB, 89 SMI-S provider managing multiple arrays with the same host, 85 startmigration command failed to start data transfer, 89 host name exceeds 31 characters, 89 trailing spaces in IP address, 86 unexpected LUNs or hosts, 85 Ethernet, 14 F Fibre Channel, 14 H help CLI command, 95 host, 7 Linux, 63 Windows, 58 host multipath software updating, 54 host multipathing solution reconfiguring, 32 HP 3PAR CLI commands controlport, 34 HP 3PAR Management Console, 13, 42, 49, 56, 61, 66, 70, 72 HP 3PAR Online Import Utility CLI commands, 90 migrations, 24 migrations supported, 24 migrations supported for VMAX only, 27 HP 3PAR Online Import Utility service starting, 77 stopping, 77 HP 3PAR Peer Motion license, 30 HP SPOCK, 14 Hyper-V host, migrating, 65 I identifying source and destination storage systems, 35 installation and setup,

122 installcertificate CLI command, 96 installing EMC SMI-S Provider, 14 EMC Solutions Enabler, 14 Installing HP 3PAR Online Import Utility, 16 L license HP 3PAR Peer Motion, 30 HP End User License Agreement, 19 logging level (HP 3PAR Online Import Utility) modifying, 78 logging level (SMI-S Provider) modifying, 79 logs HP 3PAR Online Import Utility, 78 SMI-S Provider, 79 LUNs limits for offline migration, 29 masking view, 85 migrating, 29 scanning, 63 M masking view required for offline migration of LUN with no host, 85 maximum volumes that can be migrated, 6 MDM for a Linux host, 60 for a Windows host, 54 migration, 6 migrating a Hyper-V host, 65 LUNs, 29 volumes, 29 migration, 7, 9, 11 aborting, 73 MDM, 6, 54, 60, 65 offline, 6, 7, 70 online, 6, 42 process, 7 supported, 24 unsupported, 24 migration process migration, 9, 11, 13 post-migration, 9, 11 premigration, 10, 12 minimally disruptive migration see MDM modifying HP 3PAR Online Import Utility logging level, 78 SMI-S Provider logging level, 79 MPIO path management, 54 multipathing software, 32 N native MPIO vs EMC PowerPath, 66 network and fabric zoning requirements, 31 O offline migration, 6, 7, 70 offline migration process post-migration, 13 online migration, 6, 42 overview, 6 P performing data migration, 54, 60, 65 planning data migration, 30 ports controller (on source system), 31 peer, 35 peer (on destination system), 31 post-migration, 7, 9, 11 offline migration process, 13 tasks, 72 PowerPath see EMC PowerPath premigration, 7, 10, 12 preparing for data migration, 29 host, 37 process migration, 7 R reconfiguring host multipathing solution, 32 removedestination CLI command, 96 removemigration CLI command, 97 removesource CLI command, 97 removing EMC PowerPath (from Linux host), 61 EMC PowerPath Multipath (from Windows host), 55 replication, 29, 37, 41, 84, 87 requirements data migration, 14 network and zoning, 31 system, 30 S scanning LUNs, 63 showconnection CLI command, 97 showdestination CLI command, 98 showmigration CLI command, 99 showmigrationdetails CLI command, 71, Index

123 showpersona CLI command, 101 showsource CLI command, 103 Single Point of Connectivity Knowledge website see HP SPOCK SMI-S CLI commands dv, 74 ein, 73, 74 remsys, 74 SMI-S Provider logs, 79 removing, 73 SMI-S provider managing multiple arrays, 85 SMI-S Provider commands dv, 79 eq, 79 source storage system adding, 36 starting data migration, 57, 67 HP 3PAR Online Import Utility service, 77 startmigration CLI command, 103 stopping HP 3PAR Online Import Utility service, 77 symbols in text, 117 system requirements, 30 migrating, 29 presented, 7 unpresented, 7 W Windows clusters preparing for migration, 37 Z zoning between source EMC and destination HP 3PAR StoreServ Storage, 34 data migration requirements, 31 paths, 31 the host, 56, 70 T terms, 119 TestSmiProvider commands dv, 81 eq, 82 TestSmiProvider tool, 80 text symbols, 117 troubleshooting, 75, 84 communication, 79 EMC-to-HP 3PAR StoreServ Storage online import issues, 75 types of data migration, 6 U updating host multipath software, 54 V viewing migration progress, 73 migrations, 73 selected migrations, 73 VMAX Fibre Channel connection, 14 gatekeeper device, 14 VNX Ethernet connection, 14 volumes maximum for MDM or online migration,