Beruflich Dokumente
Kultur Dokumente
Abstract
This guide provides information on using EVA to 3PAR Online Import to migrate data from an EVA storage system to a 3PAR storage system.
Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 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. 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, Windows, and Windows Server are U.S. registered trademarks of Microsoft Corporation.
Contents
1 Overview of EVA to 3PAR Online Import.......................................................5
How EVA to 3PAR Online Import works.......................................................................................5 Types of data migration.............................................................................................................6 Understanding what data is migrated..........................................................................................6 Installing EVA to 3PAR Online Import..........................................................................................7
4 Post-migration tasks...................................................................................23
System post-migration tasks......................................................................................................23 Exporting migration job histories..........................................................................................23 Network and fabric topology post-migration tasks.......................................................................23 Marking migrated hosts and volumes........................................................................................23 Deleting virtual disks from the source EVA..................................................................................23 What to do if the migration fails...............................................................................................23
5 Troubleshooting........................................................................................25
Log locations..........................................................................................................................29 HP P6000 Command View logs..........................................................................................29 EVA to 3PAR Online Import logs..........................................................................................29
Contents
Contents
3. 4. 5.
6.
7.
8.
9.
3. 4.
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. The 3PAR continues to mirror writes to the EVA, so the EVA retains a consistent copy of the data on the volumes being migrated. 8. Once the 3PAR storage system has copied all the data on a volume to local storage, it stops mirroring writes to the EVA for that volume. The volume is now a normal local volume on the 3PAR storage system. 9. When all of the host volumes have been copied to the 3PAR storage system, the migration is complete. The exports from the EVA to the 3PAR storage system and the host can now be removed. 10. If no additional migrations are to be performed, the zoning between the source EVA and the destination 3PAR storage system can now be removed.
virtual disks have to other hosts will include those hosts and all of their presented virtual disks in the migration. Presented virtual disksWhen 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. Unpresented virtual disksOnly the selected virtual disks are migrated offline.
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 30) for the document location. Single Point of Connectivity Knowledge (SPOCK) website: http://www.hp.com/storage/spock Before migrating data from an EVA to a 3PAR storage system using EVA to 3PAR Online Import, the system environment must meet the following requirements: Source EVA storage system must be running a supported firmware level. See the SPOCK website for supported firmware versions. Source EVA storage systems must be managed by Command View 10.2. The destination 3PAR storage system must have a Peer Motion license installed. The destination 3PAR storage system must be at InForm OS level 3.1.2. or later. Source EVA storage systems must have external, not internal, FC switches.
General
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. Only non-domain CPGs are used for migration. Only virtual disks presented to Fibre Channel hosts can be migrated. Virtual disks presented to iSCSI or FCoE hosts cannot be migrated. LUNs identified for migration should not be part of any other current application jobs. For example, make sure the LUN is not part of a Replication Solutions Manager Job or a Data Protector backup job. The limit for active offline migrations is 25. The limit for online migrations is 255. When a virtual disk on the source EVA is migrated, a management lock is installed to prevent any unwanted management changes to the virtual disk during the migration. The Management Lock remains on the virtual disk after the migration. Only one EVA storage system at a time can be attached as a source to the 3PAR destination storage system. EVA virtual disks cannot be migrated if they are larger than 16 TB, the maximum volume size on the 3PAR storage system.
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. When migration is complete, you can use Remote Copy on the 3PAR storage system to recreate the original remote replication structure between 3PAR storage systems.
10
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 hostWindows 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.
To create the zoning: 1. On the destination 3PAR storage system, configure two free ports as peer ports using adjacent node pairs: 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. 2. Create two zones between the source EVA storage system and destination 3PAR storage system, ensuring that one EVA host port is in the same zone with one 3PAR peer port. Each zone should contain only two ports: one from each storage system. Adjacent 3PAR peer nodes should be zoned to separate EVA controllers in a one-to-one mapping. For example, zone the peer port on node 0 on the 3PAR storage system to controller A on the EVA, and zone the peer port on node 1 on the 3PAR storage system to controller B on the EVA.
1 1
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.
12
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.
Select one EVA storage system that will be used as source storage system. Click Add Source System. The Eligible EVA to 3PAR Online Import Source/Destination Systems screen displays the EVA storage systems selected as sources.
6.
Click Add Destination. The Add a Destination Storage System screen is displayed.
13
7.
Enter the following information for the destination 3PAR storage system: IP addressThe DNS hostname of the storage system User nameUser with Super access PasswordValid 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 EVA to 3PAR Online Import Source/Destination Systems screen. If the destination storage system was added successfully, it is displayed in the Eligible 3PAR Destination Storage Systems list. NOTE: Before being added as a destination, the specified 3PAR storage system is validated for proper configuration. An alert is displayed if the storage system is not eligible to serve as a destination due to any of the following conditions: 9. Wrong IP address or the IP address not being reachable Wrong credentials (user name/password) Wrong value for Secure data port or Event port Inform OS version is earlier than 3.1.2 The specified 3PAR storage system has already been added as a destination A Peer Motion license is not installed
14
15
1 1. Review the summary information, then click Add Migration. The Host EVA to 3PAR 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. Perform the following steps on the host: a. Reconfigure the host to use the 3PAR DSM (Windows 2003) or the native Microsoft MPIO DSM (Windows 2008, 2008R2). Contact your local HP representative for information on acquiring the HP 3PAR MPIO for Windows. When reconfiguring a host to use the native Microsoft MPIO DSM on Windows 2008, use 3PARdataVV as the devices. b. c. Shut down the Windows host. Leave the host offline until the migration is started.
13. If the host is a member of a cluster, clear all the SCSI reservations on the cluster disks. For more information, see Preparing Windows clusters for migration (page 10). 14. Unzone the source EVA from the host. 15. When the host has been unzoned, click Unzoned. The Data Transfer status displays the Start button. 16. Click Start to begin the migration. A confirmation screen identifies conditions that must be met before beginning the migration. IMPORTANT: Once a migration begins, it cannot be stopped.
17. 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. 18. Zone the host to the 3PAR destination storage system, establishing the data paths between the host and the destination. 19. Bring the Windows host that was shut down back online. The host now communicates with the destination 3PAR storage system. 20. When the migration is complete, the migration entry is deleted, and the Migration History is updated with the information about the migration.
5. 6. 7.
Read the information on the Introduction screen, then click Next. The Select explicit migration source screen is displayed. Select the host that will be the source, then click Next. The Confirm Explicit and Implicit Migration Sources screen is displayed. Check the implicit and explicit host and virtual disk selections to ensure they are ready for migration, then click Next. The Confirm Your Migration Destination screen is displayed. NOTE: If any object selected for migration is not ready for data migration, the appropriate status is displayed in the 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.
8.
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.
9.
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. Select the desired Destination Common Provisioning Group (CPG) for the destination virtual volume. d. To use these settings for all the virtual volumes, set the Configuration to Set all the same. To use different settings for each volume, repeat the steps for each volume. The Summary screen is displayed.
10. Click Next. 1 1. Review the summary information, then click Add Migration. The Host EVA to 3PAR 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.. 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. Perform a LUN rescan on each host being migrated and ensure that the paths to the destination 3PAR storage system are correct. 13. Unzone the source EVA from the host. 14. When the host has been unzoned, click Unzoned. The Data Transfer status displays the Start button. 15. Click Start to begin the migration. A confirmation screen identifies conditions that must be met before beginning the migration. IMPORTANT: Once a migration begins, it cannot be stopped.
16. 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. 17. When the migration is complete, the migration entry is deleted, and the Migration History is updated with the information about the migration.
Migrating a non-Windows host 17
1 1. Click Next.
18
13. Perform the following steps on the host: a. Reconfigure the host to use the 3PAR DSM (Windows 2003) or the native Microsoft MPIO DSM (Windows 2008, 2008R2). Contact your local HP representative for information on acquiring the HP 3PAR MPIO for Windows. When reconfiguring a host to use the native Microsoft MPIO DSM on Windows 2008, use 3PARdataVV as the devices. b. c. Shut down the Windows host. Leave the host offline until the migration is started.
14. If the host is a member of a cluster, clear all the SCSI reservations on the cluster disks. For more information, see Preparing Windows clusters for migration (page 10). 15. Unzone the source EVA from the host. 16. When the host has been unzoned, click Unzoned. The Data Transfer status displays the Start button. 17. Click Start to begin the migration. A confirmation screen identifies conditions that must be met before beginning the migration. IMPORTANT: Once a migration begins, it cannot be stopped.
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. When the migration is complete, the migration entry is deleted, and the Migration History is updated with the information about the migration.
19
8.
Ensure the implicit and explicit host and virtual disk selections are ready for migration, then click Next. The Confirm migration destination screen is displayed. 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.
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. Select the desired Destination Common Provisioning Group (CPG) for the destination virtual volume. d. To use these settings for all the virtual volumes, set the Configuration to Set all the same. To use different settings for each volume, repeat the steps for each volume. The Summary screen is displayed.
1 1. Click Next. 12. Review the summary information, then click Add Migration. The Virtual Disks EVA to 3PAR 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. 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. 13. Perform a LUN rescan on each host being migrated and ensure that the paths to the destination 3PAR storage system are correct. 14. Unzone the source EVA from the host. 15. When the hosts have been unzoned, click Unzoned. The Data Transfer status displays the Start button. 16. Click Start to begin the migration. A confirmation screen identifies conditions that must be met before beginning the migration. IMPORTANT: Once a migration begins, it cannot be stopped.
17. 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. 18. When the migration is complete, the migration entry is deleted, and the Migration History is updated with the information about the migration.
2. 3. 4. 5. 6. 7. 8.
Select the EVA to 3PAR Online Import tab. In the left navigation pane, select a virtual disk. You can select a virtual disk folder or an individual virtual disk. Click Add Migration. The Add Migration from a Virtual Disk Selection wizard runs. Read the information on the Introduction screen, then click Next. The Select explicit migration source screen is displayed. Select one or more unpresented virtual disks as the source virtual disks. Click Next. The Confirm Explicit and Implicit Migration Sources screen is displayed. Ensure the explicit virtual disk selections are ready for migration, then click Next. The Confirm migration destination screen is displayed. 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.
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. Select the desired Destination Common Provisioning Group (CPG) for the destination virtual volume. d. To use these settings for all the virtual volumes, set the Configuration to Set all the same. To use different settings for each volume, repeat the steps for each volume. The Summary screen is displayed.
1 1. Click Next. 12. Review the summary information, then click Add Migration. The Virtual Disks EVA to 3PAR 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 migration preparation is being performed. When complete, the Preparation status changes to Done, and Data Transfer displays the Start button. 13. Click Start to begin the migration. A confirmation screen identifies conditions that must be met before beginning the migration. IMPORTANT: Once a migration begins, it cannot be stopped.
14. 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. 15. When the migration is complete, the migration entry is deleted, and the Migration History is updated with the information about the migration.
Migrating unpresented virtual disks 21
Aborting a migration
A migration can be aborted in the following ways: A migration can be aborted by clicking Cancel at any time during the Add Migration Wizard. If the migration preparation process is complete, a migration can be aborted by clicking on Abort in the Data Transfer column. You must click Unzoned to display the Abort button, unless you are migrating unpresented virtual disks. In that case, the Abort button is displayed immediately. Once a migration has started, it cannot be aborted.
22
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.
After a failed migration, to return the source EVA and destination 3PAR storage systems to their original configuration, perform the following tasks:
23
24
Post-migration tasks
5 Troubleshooting
The following are problems you may encounter when using EVA to 3PAR 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. Not able to see EVA Storage System when clicked on Add Source
Cause: The EVA is running an unsupported firmware version. Solution: Upgrade the EVA storage system firmware to a supported version. Cause: The EVA storage system has already been added as a source in another EVA to 3PAR Online Import instance in the same management group. Solution: Remove the EVA storage system from the other EVA to 3PAR Online Import instance.
Cause: HP P6000 Command View did not register managed EVA details in Management Integration Framework. Solution: If there are no active migrations, restart the HP P6000 Command View service. If there are active migrations, wait for them to complete before restarting the service.
Destination array is unreacheable. Please ensure array is configured for use and is accessible. 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.
Cause: While adding a 3PAR storage system as a destination, it took too long to load the 3PAR details. Solution: Use the following steps to isolate and solve the problem: 1. Ping the 3PAR storage system's IP address from the server where EVA to 3PAR Online Import is installed. 2. Make sure the port number specified when adding the destination is correct. If you are still unable to add destination, continue to step 3. 3. 4. Restart the EVA to 3PAR Online Import service. Increase the 3par_num_retry_anydata_load value at
<EVA to 3PAR Online import install location>\PMMTools\tomcat \32-bit\apache-tomcat-7.0.27\webapps\p6000pm\WEB-INF \classes\applicationConfig.properties
5.
Possible cause: Wrong IP address or the IP address not being reachable Wrong credentials (user name/password) Wrong value for Secure Data Port Inform OS version is earlier than 3.1.2
25
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. Solution: Add the storage system as a source as described in Identifying source and destination storage systems (page 12).
The EVA to 3PAR Online Import instance does not appear in the Settings point of view navigation pane
Cause: The management server on which the EVA to 3PAR Online Import instance is installed is not accessible. Solution: Determine why the management server is not accessible.
Cause: The management server on which the EVA to 3PAR Online Import instance is installed has been moved to a different management group. Solution: Move the management server back to the existing management group. Log in to the new management group to which the management server belongs.
Cause: The EVA to 3PAR Online Import service is not running. Solution: Start the EVA to 3PAR Online Import service. If the above solution did not resolve the problem, perform the following steps: IMPORTANT: The following procedure involves restarting the EVA to 3PAR Online Import service. Contact HP Customer Support for assistance before attempting to restart the EVA to 3PAR Online Import service. 1. 2. 3. 4. 5. 6. Re-login to Command View using the existing browser instance and determine if the EVA to 3PAR Online Import instance is now displayed. If not, continue to step 2. Stop the EVA to 3PAR Online Import Server service. Stop the HP MIF service. Start the HP MIF service. Start the EVA to 3PAR Online Import service. Re-login to Command View using the existing browser instance and verify that the EVA to 3PAR Online Import instance appears in the Settings point of view navigation pane.
Internal server error. Please refresh the current content pane and retry.
Possible cause: An unexpected event has occurred. Expected data was not available from the underlying layer. The server may be in an unstable state.
Solution:
26
Troubleshooting
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. 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. Start the EVA to 3PAR Online Import service.
Server response time out has happened. Server might still be processing request. Please refresh the current content pane after some time.
Possible cause: The server is too busy to respond to the GUI. Latency in underlying layers leads to delayed server response while processing large number of objects. Network latency between the browser and server component. Network latency between server component and underlying components (such as Command View, destination 3-PAR storage system). EVA to 3PAR Online Import service starvation due to CPU being consumed by another process (such as antivirus).
Solution: Reload the content on the Content Pane. Refresh the browser screen. Log in to the application again. Identify and correct any network latency issues. Determine whether the 3PAR destination is experiencing latency on the CLI server. The following problems all share a common cause and solution.
NOTE:
Destination storage system is unreachable or failed to load data on time Failed to start data transfer Preparation stage failed because data from the destination storage system could not be fully loaded
27
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. Contact HP Customer Support for assistance before attempting to restart the EVA to 3PAR Online Import service. 1. 2. 3. 4. Verify that the destination storage system is not overloaded. Identify and correct any network latency issues. Retry the operation. If the problem persists, restart the EVA to 3PAR Online Import service.
Migration failed due to insufficient capacity even though Capacity Check indicates OK
Possible cause: The Capacity Check may not be able to determine accurately the capacity available on the destination 3PAR storage system. Solution: Check the migration history. The migration may have succeeded even though insufficient capacity was indicated. If the migration failed, it will be necessary to ensure adequate capacity is available on the destination 3PAR storage system before attempting the migration again.
A migration has stopped due to the failure of data transfer of one or more virtual disks
Possible cause: I/O latency on the source EVA due to heavy load or SAN switch is overloaded. Solution: Restart the migration when the load is less on the EVA or the corresponding SAN.
Possible cause: The CPG on the destination 3PAR does not have enough space. Solution: Free up enough capacity in the CPG or add more capacity to the CPG on the destination 3PAR.
Possible cause: The LUN number of the Virtual disk is already in use on the destination 3PAR for the corresponding host. Solution: Make the required LUN numbers available on the host or reconfigure the host to use new LUN numbers for the virtual disks that are being migrated.
Possible cause: Fibre Channel connectivity between the source EVA and the destination 3PAR has either degraded (one path lost) or gone down. Solution: Check cabling and ensure that the source virtual disks are visible to the 3PAR through two distinct paths.
NOTE: When the problem has been solved, click Restart to continue the migration. This does not restart ongoing or completed migration tasks, only the failed tasks.
28
Troubleshooting
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. The required LUN number is available on the host object on the destination storage system. The source volumes are visible to the destination storage system through both paths.
Cause: The preparation process failed to create a host object on the destination storage system. Solution: Verify the following: The destination storage system is accessible. There is no other host on the destination storage system with a subset of HBA ports of the host being created. There is no host on the destination storage system with a duplicate name but a different HBA port. There is no host on the destination storage system with a duplicate name and a subset of a HBA port with a different operating system. If a host pre-exists on the destination storage system, verify that the operating system field contains the correct value. Possible values are sunsolaris, vmware, linux, windows2008, mswindows, hpux, ibmaix.
Log locations
Log content can be useful in identifying and solving problems that may occur during data migration.
EVA to 3PAR Online Import configuration and migration data is located in the following location:
<Install drive/folder>\Hewlett-Packard\PMM\PMMData\data
Log locations
29
HP contact information
For the name of the nearest HP authorized reseller: See the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/ en/wwcontact.html). In the United States, for contact options see the Contact HP United States webpage (http:// welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone:
Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com/hps). In other locations, see the Contact HP worldwide (in English) webpage (http:// welcome.hp.com/country/us/en/wwcontact.html)
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/country/us/en/contact_us.html After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources.
Related information
The following documents provide related information: HP P6000 Command View Software Suite Installation Guide HP P6000 Enterprise Virtual Array Compatibility Reference HP StorageWorks Command View EVA user guide HP StorageWorks Command View EVA release notes
You can find the documents referenced in this guide on the Manuals page of the HP Business Support Center website:
30 Support and other resources
http://www.hp.com/support/manuals In the Storage section, click Disk Storage Systems or Storage Software, and then select your product.
Websites
HP Technical Support website: http://www.hp.com/support Single Point of Connectivity Knowledge (SPOCK) website: http://www.hp.com/storage/spock
Related information
31
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.
32
Documentation feedback
33
Index
A
aborting migration, 22
N
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, 23 preparing for, 8 presented vistual disks, 18 tasks after failure, 23 types, 6 unpresented vistual disks, 20 viewing status, 22 what is migrated, 6 Windows clusters, 10 Windows host, 15 destination storage systems, identifying, 12 document related documentation, 30 documentation HP website, 30 providing feedback on, 32 DSM, reconfiguring, 10
O
overview, 5
P
planning data migration, 8 post-migration tasks, 23 exporting migration job histories, 23 marking migrated hosts and volumes, 23 network and fabric topology, 23 system, 23 preparing for data migration, 8 presented vistual disks migrating, 18
R
reconfiguring Windows host DSM, 10 related documentation, 30
S
source storage systems, identifying, 12 system requirements, 8
T
technical support, 31 terms, 33 troubleshooting, 25 EVA to 3PAR Online Import issues, 25 types of data migration, 6
E
EVA and 3PAR terms, 33 EVA to 3PAR Online Import installing, 7 overview, 5 exporting migration job histories, 23
U
unpresented vistual disks migrating, 20
F
failure of data migration tasks , 23
V
viewing migration status, 22
I
identifying source and destination storage systems, 12 installing EVA to 3PAR Online Import, 7
W
websites, 31 product manuals, 30 Windows clusters preparing for migration, 10 Windows host migrating, 15 Windows host DSM, reconfiguring, 10
L
log locations, 29
M
marking migrated hosts and volumes, 23 migration job histories, 23 migration status, viewing, 22
Z
zoning requirements, 10
34
Index