Data Migration Service for HP StorageWorks MPX200 Planning Guide ISR654605-00 A
Data Migration Service for HP StorageWorks MPX200 Planning Guide Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are for illustrative purposes only.
Table of Contents Preface Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP Technical Support. . . . . . . . . . . . . . . . . . . . . . . . .
Data Migration Service for HP StorageWorks MPX200 Planning Guide A Checklist Examples Step 1: List the Source and Destination Storage Array . . . . . . . . . . . . . . . . Step 2: List the Servers Impacted by the Data Migration Project . . . . . . . . . Step 3: List Applications, Mount Points, and Paths to the Physical Device . Step 4: List and Create LUN ID Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5: List and Create Fibre Channel Zoning . . . . . . . . . . . . . . . . . . . . . .
Data Migration Service for HP StorageWorks MPX200 Planning Guide List of Tables Table 2-1 2-2 2-3 2-4 2-5 2-6 A-1 A-2 A-3 A-4 A-5 A-6 A-7 Storage Array Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LUN ID Mappings. . . . . .
Data Migration Service for HP StorageWorks MPX200 Planning Guide Notes vi ISR654605-00 A
Preface The Data Migration Service for HP StorageWorks MPX200 Planning Guide provides end-to-end “best practices” for using HP StorageWorks MPX200 data migration service. MPX200-based data migration service migrates the data at block level. Successful data migration means the application is able to access the same data after the data is migrated to a new logical unit number (LUN). Proper planning for data migration reduces downtime and creates first-pass success.
Preface Documentation Conventions Appendix A Checklist Examples provides some examples of completed data migration checklists. Appendix B Assigning LUNs to the MPX200 for Data Migration provides specific steps for data migration using various storage array management tools. In addition, following the appendices is an index to help you quickly locate the information you need. Documentation Conventions This guide uses the following documentation conventions: NOTE: provides additional information.
Preface HP Technical Support Text in italics indicates terms, emphasis, variables, or document titles. For example: For a complete listing of license agreements, refer to the QLogic Software End User License Agreement. What are shortcut keys? To enter the date type mm/dd/yyyy (where mm is the month, dd is the day, and yyyy is the year). Titles between quotation marks identify related sections within this guide.
Preface HP Websites x http://www.hp.com/support http://www.docs.hp.com http://www.hp.
1 Getting Started In a typical storage area network (SAN), the storage array serves one or more servers. When data is migrated from a source LUN to a destination LUN on a different storage array or the same storage array, it is important to understand: Which applications and servers (or cluster) are affected? How is application data related to a physical storage? How does the server access old and new physical storage? A single blade of the MPX200 can deliver up to 4TB/hr. migration rate.
1–Getting Started Relationship Between Application Data and Physical Storage Relationship Between Application Data and Physical Storage Successful data migration requires that you understand the relationship between the application data and the physical device (LUN). NOTE: UNIX operating system in this discussion refers to HP-UX, Linux, Solaris, and AIX. Typically, the application accesses the data using a mount point.
1–Getting Started General Steps for Data Migration General Steps for Data Migration To perform a successful data migration, follow these recommended steps: 1. Create a data migration checklist. Chapter 2 Inventory Checklists provides an explanation of each of the checklists, and Appendix A Checklist Examples shows examples of completed checklists for a specific data migration scenario. To obtain the template for the checklists, go to QLogic’s HP OEM Solutions Web page: http://qlogic.
1–Getting Started General Steps for Data Migration Notes 1-4 ISR654605-00 A
2 Inventory Checklists Data migration checklists help you take inventory of all items affected by a data migration project. This chapter provides a list of servers and applications, and defines relationships of application data to LUNs and how LUNs are accessed through the server. The migration checklists will also help you identify the changes you may need to make to the server after migration.
2–Inventory Checklists Step 1: List the Source and Destination Storage Array Step 1: List the Source and Destination Storage Array The information requested in Table 2-1 can be retrieved from the storage administrator in the data center. Table 2-1.
2–Inventory Checklists Step 3: List the Applications, Mount Points, and Paths to the Physical Devices Step 3: List the Applications, Mount Points, and Paths to the Physical Devices The applications, mount points, and paths to the physical device requested in Table 2-3 can be retrieved by the server administrator.
2–Inventory Checklists Step 5: List and Create Fibre Channel Zoning Table Notes You should complete the information for the source and destination LUN during the planning phase of data migration. Determine the unique volume ID for the source storage array to make it easier to refer to the LUN, because sometimes on large arrays, different LUNs with the same LUN ID are presented to different hosts.
3 Performance and Downtime This chapter provides recommendations designed to improve performance and minimize downtime during data migration. Optimizing Performance During Data Migration The MPX200 detects the multiple paths of a specified LUN and performs load balancing using active optimized paths. To get the best performance, QLogic highly recommends that LUNs for the source array and destination array are balanced across both controllers.
3–Performance and Downtime Minimizing Downtime Before Application Downtime Before application downtime, follow these steps: 1. Plan the data migration project: a. Create the migration checklist. b. Determine if a change in multi-pathing software is required. c. Build the LUN ID table for both the source and destination array to establish the LUN ID relationship between the server and the MPX200. d. Plan to migrate together the LUNs from the same server/cluster. 2.
3–Performance and Downtime Minimizing Downtime 5. After the data is migrated for the specified server or cluster, present the destination LUNs to the server or cluster by changing the fabric zoning and LUN presentation from the array. 6. Reboot the server, and then validate that the new LUNs are seen by the system and that the volumes are mounted on the destination LUNs.
3–Performance and Downtime Minimizing Downtime Notes 3-4 ISR654605-00 A
4 Operating Systems Dependencies If the source array type is different from the destination array type, you may need to install the new multi-pathing software associated with the destination array. CAUTION! Do not expose the destination LUNs to a server until the data migration is complete and server access to the source LUN is removed. Windows OS Migrating data for Windows servers is not difficult. Windows offers two types of disks: basic disks and dynamic disks.
4–Operating Systems Dependencies UNIX OS (HP_UX, Linux, AIX, Solaris) UNIX OS (HP_UX, Linux, AIX, Solaris) On UNIX operating systems—HP_UX, Linux, AIX, and Solaris—If volumes are managed through logical volume managers, follow these general guidelines: Export the volume before migration begins. Import the volume after migration is complete and destination LUNs are presented to the server.
A Checklist Examples This appendix provides examples of completed data migration checklists. These examples depict a scenario where a customer is upgrading from an old EMC CX3-20 storage array to a new HP EVA 4400 storage array. Three applications and servers are using the CX3-20 array. Each of these three servers has a different operating system. The information shown with bold text in these tables represents changes from the existing configuration.
A–Checklist Examples Step 2: List the Servers Impacted by the Data Migration Project Step 2: List the Servers Impacted by the Data Migration Project Table A-2 shows an example of the server information that can be retrieved by server administrator(s) Table A-2. Example: Server Information Server Operating System and Version IP Address Multi-Pathing Software for Source Array Logical Volume Manager (if any) Multi-Pathing Software for Destination Array HR-Dept Windows SP2 10.3.3.
A–Checklist Examples Step 4: List and Create LUN ID Mappings Step 4: List and Create LUN ID Mappings Table A-4 shows that a different LUN from a storage array is presented as the same LUN ID (2) on two different servers (HR-Dept, iPortal). Table A-4.
A–Checklist Examples Step 5: List and Create Fibre Channel Zoning Table A-5. Example A: Pre-Migration Fibre Channel Zoning Information FC Switch and IP Address FC-SW-1 FC Zone Name Zone-A 10.5.3.1 FC-SW-2 Zone-B 10.5.3.
A–Checklist Examples Step 5: List and Create Fibre Channel Zoning Table A-7 shows an example of post-migration Fibre Channel zoning information: Table A-7. Example: Post-Migration Fibre Channel Zoning Information FC Switch and IP Address FC-SW-1/10.5.3.1 FC-SW-2/10.5.3.
A–Checklist Examples Step 5: List and Create Fibre Channel Zoning Notes A-6 ISR654605-00 A
B Assigning LUNs to the MPX200 for Data Migration For successful completion of data migration, you must assign source and destination LUNs to the MPX200 using storage array management tools. The MPX200 appears as a host to the array controller.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an MSA2012fc Array 2. In Internet Explorer, open the Storage Management Utility using the IP assigned to the storage controller. 3. In the left pane, click Manage to open the management menu (see Figure B-1). Figure B-1 Viewing the Storage Management Utility 4. In the left pane, click VOLUME MANAGEMENT, click volume mapping, and then click manage host list. Figure B-2 shows the WWPN of the data migration appliance in the right pane.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an MSA2012fc Array Figure B-2 Viewing WWPNs in Storage Management Utility 5. In the Manufacturer Nickname box, type DM-Host. 6. To accept and save the changes, click Update. 7. In the left pane, click VOLUME MANAGEMENT, click volume mapping, and then click map hosts to volume. 8. In the right pane, click the LUN to be assigned to the data migration appliance (see Figure B-3).
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an MSA1000/1500 Array Figure B-3 Selecting LUNs in Storage Management Utility 9. In the Assign Host Access Privileges table, select the DM-Host in the Host WWN - Name list, and then enter the appropriate, planned LUN ID. 10. To accept and save the LUN assignment, click Map it. 11.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an MSA1000/1500 Array To assign LUNs: 1. 2. Perform zoning as follows: a. Connect the Fibre Channel ports of the data migration appliance to a switch where the storage controller ports are also logged. b. Using switch management tools, create a zone DM_Host_MSA1000, and then add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports in this zone. c.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an MSA1000/1500 Array Figure B-5 Entering a Connection Name 4. Enter DM-Host as the connection name for the data migration appliance WWPN. 5. From the list box, select Windows as the host mode value, as shown in Figure B-6.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an HDS Array 6. Select the LUNs to be assigned to the DM-Host by checking the box associated with the previously planned LUNs, as shown in Figure B-7. Figure B-7 Selecting LUNs 7. To accept and save the LUN assignment, click OK. 8. Refresh the data migration user interface to see if the LUN assignment is reflected properly, and that the appropriate array entity appears under FC Array.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an HDS Array Figure B-8 Changing to Management Mode 4. Under Array Unit, double-click the name of the array to manage. The Array System Viewer window opens. B-8 5. In the left pane, click the Logical Status tab. 6. In the left pane, right-click the port of the array that has been zoned with the data migration appliance, and then click Add New Host Group (see Figure B-9).
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an HDS Array Figure B-9 Selecting a Port for New Host Group 7. In the Host Group dialog box, type DM-Host in the Name box, and then click OK. 8. In the Array System Viewer left pane under Host Groups, click the + sign next to the port to expand the newly-created DM-Host group entity. Three nodes are listed: Options, Logical Unit, and WWN, as shown in Figure B-10.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an HDS Array Figure B-10 Selecting DM-Host Nodes 9. In the left pane, click the Options node, and then at the bottom of the right pane, click Simple Setting. 10. Complete the Simple Setting dialog box as follows: 11. B-10 a. Next to Platform, select Windows2003. b. Keep the other settings as default. c. To save the changes, click OK. In the Array System Viewer dialog box, under the DM-Host group, click the WWN node.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an HDS Array Figure B-11 Array System Viewer 12. Complete the Modify WWN Information dialog box as follows: a. Under Assignable WWN, click the WWN of the data migration appliance. b. Click Add. c. To accept and save the WWN information, click OK. 13. Under the DM-Host group, click the Logical Unit node. Then at the bottom of the right pane, click Modify Mapping. 14.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an IBM DS4K/DS5K/LSI Array Figure B-12 Modifying Mapping 15. Refresh the data migration user interface to see if the LUN assignment is reflected properly, and that the appropriate array entity appears under FC Array.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an IBM DS4K/DS5K/LSI Array c. In this zone, add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports. d. Save the zoning information and activate the new zoning configuration. 2. Open the Storage Manager Client configuration utility, and then select the array to manage. 3. On the Subsystem Management window, in the left pane, click the Mappings View tab. 4.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an IBM DS4K/DS5K/LSI Array Figure B-14 Defining the Host B-14 a. Under Specify name of host, type DM-Host as the name for the data migration appliance. b. In the Known HBA host port identifiers box, click the WWPN of the data migration appliance. c. Click Add to move the selected WWPN to the Selected HBA host port identifiers/aliases box. d.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an IBM DS4K/DS5K/LSI Array Figure B-15 Selecting Host Operating System g. Click Next. 6. On the Subsystem Management window, in the left pane’s Mapping View page, click either Undefined Mappings or the host group/host that currently has access to the LUNs that need to be part of data migration jobs. 7. Select the LUNs to be assigned to the DM-Host by right-clicking the LUN in the right pane, and then clicking Change Mappings. 8.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EVA 4/6/8000 Series Array Figure B-16 Defining Additional Mapping 9. Refresh the data migration user interface to see if the LUN assignment is reflected properly, and that the appropriate array entity appears under FC Array. (You may need to click the Refresh button several times to correctly reflect the changes.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EVA 4/6/8000 Series Array To assign LUNs: 1. 2. Perform zoning as follows: a. Connect the Fibre Channel ports of the data migration appliance to a switch where the storage controller ports are also logged. b. Using switch management tools, create a zone, DM_Host_EVA. c. In this zone, add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports. d.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EVA 4/6/8000 Series Array 5. Complete the Add a Host information in the right pane as follows (see Figure B-18): a. Under Basic Settings in the Name box, type DM-Host. b. Under Port World Wide Name, click the WWN of the data migration appliance. c. Under Operating System, click Microsoft Windows. d. Click the Add host button. Figure B-18 Adding a Host 6.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EVA 4/6/8000 Series Array Figure B-19 Adding a Second Host Port 7. ISR654605-00 A Present virtual disks as follows (see Figure B-20): a. In the left pane, double-click the Virtual Disks node. b. Click the LUN that needs to be presented to the data migration appliance for data migration. c. In the right pane, click the Presentation tab, and then click the DM-Host. d. To accept and save the LUN assignment, click Present Vdisk.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EMC CLARiiON Array Figure B-20 Presenting Vdisks 8. Refresh the data migration user interface to see if the LUN assignment is reflected properly, and that the appropriate array entity appears under FC Array. (You may need to click the Refresh button several times to correctly reflect the changes.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EMC CLARiiON Array 2. c. Add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports in this zone. d. Save the zoning information and activate the new zoning configuration. Using Internet Explorer, open the Navisphere utility using the IP assigned to the storage controller. The Enterprise Storage dialog box opens, as shown in Figure B-21. Figure B-21 Viewing Enterprise Storage 3.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EMC CLARiiON Array 5. Complete the Register Initiator Record dialog box as follows (see Figure B-22): a. In the Initiator Type box, click CLARIION Open. b. Under Host Information, type the values for Host Name and IP Address. c. Click OK. Figure B-22 Registering Initiator Record 6. B-22 Create a storage group to add to the newly-registered DM-Host entity as follows (see Figure B-23): a.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EMC CLARiiON Array c. In the Create Storage Group dialog box, type DM-Host as the Storage Group Name. d. To save the changes, click either OK or Apply. Figure B-23 Creating Storage Group The new DM-Host storage group is listed under the Storage Groups tree in the main window. 7. ISR654605-00 A Add the DM-Host host entity to the DM-Host storage group entity as follows (see Figure B-24): a.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EMC CLARiiON Array e. Click the (right arrow) button to move DM-Host to the right pane’s Host to be Connected box. f. To save the changes, click either OK or Apply. Figure B-24 Adding DM-Host to Storage Group 8. B-24 Add LUNs to the DM-Host storage group entity as follows (see Figure B-25): a. Under the Storage Groups tree, right-click DM-Host. b. Click Select LUNs to view a list of available LUNs. c.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EMC CLARiiON Array Figure B-25 Adding LUNs to DM-Host 9. ISR654605-00 A Refresh the data migration user interface to see if the LUN assignment is reflected properly, and that the appropriate array entity appears under FC Array. (You may need to click the Refresh button several times to correctly reflect the changes.
B–Assigning LUNs to the MPX200 for Data Migration Assigning LUNs from an EMC CLARiiON Array Notes B-26 ISR654605-00 A
Index A access, LUN to server 1-2 active optimized paths, load balancing with 3-1 applications downtime, minimizing 3-1 server, listing 2-3 arrays assigning LUNs for data migration B-1 listing storage 2-2 management tools, assigning LUNs B-1 multi-pathing software for 2-2 assigning LUNs for data migration B-1 from EMC CLARiiON array B-20 from EVA 4/6/8000 series array B-16 from HDS array B-7 from IBM DS4K array B-12 from IBM DS5KL array B-12 from IBM LSI array B-12 from MSA2012fc array B-1 audience vii cre
Data Migration Service for HP StorageWorks MPX200 Planning Guide F fabric zones, listing 2-4 Fibre Channel switches, listing 2-4 Fibre Channel zoning, listing 2-4 file system check, validating data 3-3 G getting started 1-1 H HDS array, assigning LUNs from B-7 HP technical support ix HP websites ix I IBM DS4K array, assigning LUNs from B-12 IBM DS5K array assigning LUNs from B-12 IBM LSI array, assigning LUNs from B-12 inventory checklists 2-1 LUN IDs mappings, listing 2-3 server, listing for 2-3 LUNs
Data Migration Service for HP StorageWorks MPX200 Planning Guide planning data migration 2-1 post-migration Fibre Channel zoning 2-4 pre-migration Fibre Channel zoning 2-4 R raw device node (server), listing 2-3 related materials vii relationship between data and storage 1-2 S saving data migration logs 1-3 servers impacted by data migration, listing 2-2 LUN access to 1-2 physical device information, listing 2-3 source arrays listing 2-2 multi-pathing software for 2-2 source LUNs, assigning B-1 storage a
Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 Europe Headquarters QLogic (UK) LTD. Quatro House Lyon Way, Frimley Camberley Surrey, GU16 7ER UK www.qlogic.com +44 (0) 1276 804 670 © 2009 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic and the QLogic logo are registered trademarks of QLogic Corporation. Apache is a trademark of The Apache Software Foundation.
