HP EVA to 3PAR StoreServ Online Import Migration Guide Abstract This guide provides information on using HP EVA to 3PAR StoreServ Online Import to migrate data from an EVA storage system to a 3PAR storage system.
© Copyright 2012, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, 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.
Contents 1 Overview of HP EVA to 3PAR StoreServ Online Import....................................5 How HP EVA to 3PAR StoreServ Online Import works....................................................................5 Types of data migration.............................................................................................................6 Understanding what data is migrated..........................................................................................
7 Documentation feedback...........................................................................33 A EVA and 3PAR terms................................................................................34 Index.........................................................................................................
1 Overview of HP EVA to 3PAR StoreServ Online Import HP EVA to 3PAR StoreServ Online Import manages the migration of data from a source EVA storage system to a destination 3PAR storage system. Using HP EVA to 3PAR StoreServ Online Import, you can migrate EVA virtual disks and host configuration information to a 3PAR destination storage system without changing host configurations or interrupting data access.
5. The 3PAR storage system begins copying data from the EVA to local storage on the 3PAR storage system. No writes of new data will be made to the 3PAR storage system or the EVA while the host is shutdown. Data from the EVA is written to the 3PAR once the import process begins. 6. Once the 3PAR has started copying the data the host is zoned to the destination 3PAR array and brought back up. The host is now accessing its data via the destination 3PAR while the migration of data from the EVA continues. 7.
virtual disks have to other hosts will include those hosts and all of their presented virtual disks in the migration. • Presented virtual disks—When selecting a virtual disk or group of virtual disks with host presentations, the selected virtual disks and the hosts to which they are presented are migrated. In addition, any presentations the source hosts have with other virtual disks will include those virtual disks in the migration.
2 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. System requirements NOTE: For detailed information on ensuring the EVA source and the 3PAR destination are configured properly for data migration, see the following: • HP P6000 Enterprise Virtual Array Compatibility Reference. See “Related information” (page 31) for the document location.
Considerations when migrating data Before migrating data using EVA to 3PAR Online Import, be aware of the following: General • HP recommends that a single host be migrated at a time, unless a cluster is being migrated, in which all the hosts have to move at once. • If available, a CPG of the same RAID level as the virtual disk being migrated is automatically selected on the destination. Otherwise, the first CPG discovered will be presented as the destination CPG.
Local replication • Any sharing relationships among snapshots and mirrorclones are lost during migration. Snapshots become standalone objects on the destination 3PAR storage system. Mirrorclones cannot be migrated. Remote replication • If the source EVA storage system is using HP Continuous Access data replication, virtual disks that are in data replication relationships cannot be migrated. To migrate a virtual disk in a data replication relationship, stop the replication and migrate the virtual disk.
ports on the destination 3PAR storage system. See “Zoning the source EVA to the destination 3PAR storage system” (page 11). • Paths must be zoned between the host and destination 3PAR storage system. The time at which these paths are created is determined by the type of host—Windows or non-Windows. For more information, see “Zoning a host to the destination 3PAR storage system” (page 12). • Paths must exist between the host and source EVA. These paths will be unzoned during the migration.
3. Verify that the EVA can detect both ports on the 3PAR. Ensure that the peer port WWNs appear in the discovered port list. Alternately, verify that the EVA is shown as a connected device on both peer ports of the destination 3PAR storage system. Zoning a host to the destination 3PAR storage system The migration process requires each host involved in the migration to be zoned to the destination 3PAR storage system. Paths must be created from the host to the destination 3PAR storage system.
3. Click Add Source. The Add a Source Storage System screen displays the P6000 EVA Storage Systems qualified to serve as sources. Only storage systems in the local management group are displayed. An EVA that is associated with any other Online Import in the same management group will not be displayed. IMPORTANT: A source EVA must have an Operational State of Good. If it does not, resolve any issues before continuing with the migration. 4. 5.
7. Enter the following information for the destination 3PAR storage system: • IP address—The DNS hostname of the storage system • User name—User with Super access • Password—Valid password for the user Secure data port and Event port are filled in automatically with default values. 8. Click Add Destination System. You are returned to the Eligible HP EVA to 3PAR StoreServ Online Import Source/Destination Systems screen.
3 Performing the data migration Data migration can be performed by selecting a host or a virtual disk. The sequence of tasks differs between Windows and non-Windows hosts. Migrating a Windows host The minimally disruptive migration process is used when migrating a Windows host. The host DSM must be reconfigured to communicate with the destination 3PAR 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. 1.
11. Review the summary information, then click Add Migration. The Host HP EVA to 3PAR StoreServ Online Import Status Summary page is displayed with the newly added migration in the list of Migrations in Progress. The Preparation status displays a clock indicating that migration preparation is being performed. When complete, the Preparation status changes to Done, and the Unzoned button is displayed in Data Transfer, indicating that the host must be unzoned from the EVA before beginning the migration. 12.
NOTE: • Before migrating a non-Windows host, verify that the operating system of the host is supported. For information on supported operating systems, see the HP P6000 Enterprise Virtual Array Compatibility Reference. • Make sure you have zoned the host to the 3PAR destination storage system before performing the migration. For more information, see “Zoning a host to the destination 3PAR storage system” (page 12).
10. Click Next. The Summary screen is displayed. 11. Review the summary information, then click Add Migration. The Host HP EVA to 3PAR StoreServ Online Import Status Summary page is displayed with the newly added migration in the list of Migrations in Progress. The Preparation status displays a progress bar indicating that migration preparation is being performed..
NOTE: If any object selected for migration is not ready for data migration, the appropriate status is displayed in the object Migration OK? field, and the Next button is disabled. In this case, click Export Selections to save the selections information to a file for troubleshooting. Then click Cancel to stop the migration wizard. Using the saved selections information, correct the problem and run the migration wizard again. 9.
18. When all the conditions have been met, click Start Data Transfer. A progress bar indicates how much of the data has been migrated. The progress bar is refreshed every 15 seconds. 19. Zone the host to the 3PAR destination storage system, establishing the data paths between the host and the destination. 20. Bring the Windows host that was shut down back online. The host now communicates with the destination 3PAR storage system. 21.
11. Click Next. The Summary screen is displayed. 12. Review the summary information, then click Add Migration. The Virtual Disks HP EVA to 3PAR StoreServ Online Import Status Summary page is displayed with the newly added migration in the list of Migrations in Progress. The Preparation status displays a progress bar indicating that migration preparation is being performed.
9. Ensure the 3PAR Destination Storage System is ready for migration, then click Next. The Configure Destination Volumes screen is displayed. NOTE: If the Migration OK? status is not OK, the tooltip provides information on why the migration cannot be performed until the necessary action is taken. 10. Set a. b. c. the Destination Virtual Volume Attributes. Set the Configuration to Set individually. Select the desired Destination Provisioning for the destination virtual volume.
2. In the left navigation pane, select the HP EVA to 3PAR StoreServ Online Import instance. The HP EVA to 3PAR StoreServ Online Import screen displays all the migrations in progress or completed. Viewing migrations for a storage system 1. 2. 3. In Command View, select the Storage Systems point of view. In the left navigation pane, select the storage system. In the content pane, select the HP EVA to 3PAR StoreServ Online Import aspect tab. All migrations for the storage system are displayed.
4 Post-migration tasks System post-migration tasks • If the boot LUN for a host server was migrated, the boot setting on the server/adapter must be changed to point to the new 3PAR destination data paths. Exporting migration job histories You can export migration job histories in csv format to an external file to track data migrations. 1. In Command View, select the Settings point of view. 2. In the left navigation pane, select the HP EVA to 3PAR StoreServ Online Import instance.
Destination 3PAR tasks 1. 2. 3. Unzone the 3PAR from the host. Delete the respective virtual volumes and virtual LUNs. Delete the host if it did not exist before the migration.
5 Troubleshooting The following are problems you may encounter when using HP EVA to 3PAR StoreServ Online Import. NOTE: During the migration process, it is important to remember that the data continues to be served from the source EVA until the import of each volume is complete. If host errors occur, both the destination 3PAR and the source EVA should be checked for potential problems.
◦ • – The specified 3PAR storage system has already been added as a destination – A Peer Motion license is not installed Solution: Check each of the above conditions to identify which may be causing the problem, then resolve it. EVA to 3PAR Online Import aspect tab is not appearing in the content pane ◦ Possible cause: The storage system has not been added as a source for EVA to 3PAR Online Import.
IMPORTANT: It may be necessary to restart the EVA to 3PAR Online Import service to solve this problem. Contact HP Customer Support for assistance before attempting to restart the EVA to 3PAR Online Import service. • ◦ 28 Reload the content on the Content Pane. – Refresh the browser screen. – Log in to the application again. – Perform the following steps: 1. Stop the EVA to 3PAR Online Import service. 2. Stop the HP P6000 Command View service. 3. Start the HP P6000 Command View service. 4.
◦ Host set creation failed because data from destination storage system could not be fully loaded ◦ Data from destination storage system could not be fully loaded ◦ Possible cause: ◦ – The destination storage system is busy and did not provide the required data within the expected time. – Network latency between server component and the destination storage system. Solution IMPORTANT: It may be necessary to restart the EVA to 3PAR Online Import service to solve this problem.
• Migration preparation failed ◦ Cause: The preparation process failed to admit volumes on the destination storage system. Solution: Verify the following: • – The destination CPGs have enough capacity. If they do not, free up enough capacity in the CPGs or add more capacity to the CPGs on the destination storage system. – No duplicate volumes exist. This may occur if either a virtual volume with same name or with the same WWN exists on the destination storage system.
6 Support and other resources Contacting HP Before you contact HP Be sure to have the following information available before you call contact HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error message • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level HP contact information For the name of the nearest HP authorized reseller
http://www.hp.com/support/manuals In the Storage section, click Disk Storage Systems or Storage Software, and then select your product. Websites 32 • HP Technical Support website: http://www.hp.com/support • Single Point of Connectivity Knowledge (SPOCK) website: http://www.hp.
7 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 (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
A EVA and 3PAR terms In some cases, different terms are used for the same item or concept on the EVA storage system and the 3PAR storage system. The following table lists the relationship between terms.
Index A N aborting migration, 22 network and fabric zoning requirements, 10 non-Windows host migrating, 16 C considerations when migrating data, 9 D data migration considerations, 9 identifying source and destination, 12 non-Windows host, 16 performing, 15 planning for, 8 post-migration tasks, 24 preparing for, 8 presented vistual disks, 18 tasks after failure, 24 types, 6 unpresented vistual disks, 21 viewing status, 22 what is migrated, 6 Windows clusters, 10 Windows host, 15 destination storage syst
