data migration service for isr6200 planning...

ISR654607-00 D

Data Migration Service for iSR6200

Planning Guide

ii ISR654607-00 D


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. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.

Document Revision History

Revision A, February 4, 2010

Revision B, March 31, 2011

Revision C, August 26, 2011

Revision D, November 5, 2011

Changes Sections Affected

Updated the router management utility name from SANsurfer iSCSI/FC Router Manager to SANsurfer Router Manager.

“Related Materials” on page vii and “General Steps for Data Migration” on page 1-3

Renamed the data migration spreadsheet attach-ment.

“General Steps for Data Migration” on page 1-3

Expanded the introduction to Step 4 and replaced the LUN ID mappings checklist (Table 2-4).

“Step 4: List and Create LUN ID Mappings” on page 2-3

Removed the statement regarding the destination LUN size requirement for Veritas Volume Manager.

“UNIX OS (HP-UX, Linux, AIX, Solaris)” on page 4-2

Updated the Appendix A, Step 3 example checklist (Table A-3).

“Step 3: List Applications, Mount Points, and Paths to the Physical Device” on page A-2

Replaced the Appendix A, Step 4 introduction and example checklist (Table A-4).

“Step 4: List and Create LUN ID Mappings” on page A-3

Added new section for assigning LUNs from a Fujitsu ETERNUS DX440 S2 array.

“Assigning LUNs from an ETERNUS DX440 Array” on page B-52

Added new section for assigning LUNs from a Fujitsu ETERNUS DX8400 array.


ISR654607-00 D iii

Table of Contents

Preface

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiRelated Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWhat’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiDocumentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiLicense Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixTechnical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xContact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xKnowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

1 Getting Started

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Relationship Between Application Data and Physical Storage. . . . . . . . . . . 1-2LUN Access to a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3General Steps for Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Inventory Checklists

Step 1: List the Source and Destination Storage Array . . . . . . . . . . . . . . . . 2-2Step 2: List the Servers Impacted by the Data Migration Project . . . . . . . . . 2-2Step 3: List the Applications, Mount Points, and Paths to the Physical

Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Step 4: List and Create LUN ID Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Step 5: List and Create Fibre Channel Zoning . . . . . . . . . . . . . . . . . . . . . . . 2-4

3 Performance and Downtime

Optimizing Performance During Data Migration. . . . . . . . . . . . . . . . . . . . . . 3-1Minimizing Downtime for Offline Migration . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Before Application Downtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2During Application Downtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Validating Integrity of the Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

4 Operating Systems Dependencies

Windows OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1UNIX OS (HP-UX, Linux, AIX, Solaris). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

iv ISR654607-00 D


Planning Guide

A Checklist Examples

Step 1: List the Source and Destination Storage Array . . . . . . . . . . . . . . . . A-1Step 2: List the Servers Impacted by the Data Migration Project . . . . . . . . . A-2Step 3: List Applications, Mount Points, and Paths to the Physical

Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Step 4: List and Create LUN ID Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Step 5: List and Create Fibre Channel Zoning . . . . . . . . . . . . . . . . . . . . . . . A-3

B Assigning LUNs to the iSR6200 for Data Migration

Assigning LUNs from an HP MSA2012fc Array . . . . . . . . . . . . . . . . . . . . . . B-2Assigning LUNs from an HP MSA1000/1500 Array . . . . . . . . . . . . . . . . . . . B-5Assigning LUNs from an HP 3PAR Array. . . . . . . . . . . . . . . . . . . . . . . . . . . B-8Assigning LUNs from an HP EVA 4/6/8000 Series Array. . . . . . . . . . . . . . . B-16Assigning LUNs from an HDS Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20Assigning LUNs from an EMC CLARiiON Array . . . . . . . . . . . . . . . . . . . . . B-25Assigning LUNs from an EMC Symmetrix DMX-4 Array . . . . . . . . . . . . . . . B-31Assigning LUNs from an IBM DS4K/DS5K/LSI Array . . . . . . . . . . . . . . . . . B-34Assigning LUNs from an IBM V7000 Array . . . . . . . . . . . . . . . . . . . . . . . . . B-38Assigning LUNs from a NetApp FAS2040 System Using FilerView. . . . . . . B-42Assigning LUNs from a NetApp FAS2040 System Using NetApp System

Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45Assigning LUNs from a Xiotech Emprise 5000 Array. . . . . . . . . . . . . . . . . . B-48Assigning LUNs from a Xiotech Magnitude 3D 4000 Array . . . . . . . . . . . . . B-50Assigning LUNs from an ETERNUS DX440 Array. . . . . . . . . . . . . . . . . . . . B-52Assigning LUNs from an ETERNUS DX8400 Array. . . . . . . . . . . . . . . . . . . B-56

Index

ISR654607-00 D v


Planning Guide

List of FiguresFigure Page

i Jagged Edged Screen Shot Depicting Partial Interface . . . . . . . . . . . . . . . . . . . . . . ixB-1 Viewing the Storage Management Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3B-2 Viewing WWPNs in Storage Management Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4B-3 Selecting LUNs in Storage Management Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5B-4 Configure Available Device(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6B-5 Entering a Connection Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7B-6 Selecting the Host Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7B-7 Selecting LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8B-8 Creating a Host: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9B-9 Creating a Host: Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10B-10 Creating a CPG: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11B-11 Creating a CPG: Allocation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12B-12 Creating a Virtual Volume: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13B-13 Exporting a Virtual Volume: Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15B-14 Viewing Host Details: Path Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16B-15 Opening Command View EVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17B-16 Adding a Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18B-17 Adding a Second Host Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19B-18 Presenting Vdisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20B-19 Changing to Management Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21B-20 Selecting a Port for New Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22B-21 Selecting DM-Host Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23B-22 Array System Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24B-23 Modifying Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25B-24 Viewing Enterprise Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26B-25 Registering Initiator Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27B-26 Creating Storage Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-28B-27 Adding DM-Host to Storage Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29B-28 Adding LUNs to DM-Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-30B-29 Selecting Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32B-30 Selecting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33B-31 Selecting Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-34B-32 Selecting Host to Define. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-35B-33 Defining the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36B-34 Selecting Host Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37B-35 Defining Additional Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38B-36 Creating the Fibre Channel Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-39B-37 Creating a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-40B-38 Viewing the New Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-41B-39 Confirming Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-42B-40 Adding Initiator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-43B-41 Managing LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44B-42 Mapping LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44

vi ISR654607-00 D


Planning Guide

B-43 Verifying LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45B-44 Adding an Initiator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-46B-45 Adding an Initiator ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-47B-46 Selecting Hosts to Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-48B-47 Configuring a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-49B-48 Mapping Host Initiators to Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-51B-49 Confirming LUN Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-52B-50 Creating a Host Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-53B-51 Creating a Controller Adapter Port Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54B-52 Creating a Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-55B-53 Creating a Host Affinity Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-56B-54 Creating a Host Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-57B-55 Setting the Host WWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-58B-56 Allocating a Host Affinity Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-59B-57 Mapping LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-59

List of TablesTable Page

2-1 Storage Array Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22-2 Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22-3 Physical Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32-4 LUN ID Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42-5 Pre-Migration Fibre Channel Zoning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42-6 Post-Migration Fibre Channel Zoning Information . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5A-1 Example: Storage Array Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1A-2 Example: Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2A-3 Example: Physical Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2A-4 Example: LUN ID Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3A-5 Example A: Pre-Migration Fibre Channel Zoning Information . . . . . . . . . . . . . . . . . A-4A-6 Example B: Pre-Migration Fibre Channel Zoning Information . . . . . . . . . . . . . . . . . A-4A-7 Example: Post-Migration Fibre Channel Zoning Information . . . . . . . . . . . . . . . . . . A-5

ISR654607-00 D vii

Preface

The Data Migration Service for iSR6200 Planning Guide provides end-to-end “best practices” for using the iSR6200 Intelligent Storage Router data migration service. iSR6200-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.

Intended AudienceThis guide is intended for administrators planing to implement data migration projects. The administrator should be familiar with SAN development, configuration, and storage management.

Related MaterialsFor reference information and procedures for using the Data Migration Service (DMS) features of the SANsurfer Router Manager utility for the iSR6200 data transport device, refer to the following materials:

Data Migration Service for iSR6200 Intelligent Storage Router User’s Guide

SANsurfer Router Manager help system

What’s in This GuideThis preface provides a general overview of data migration service and identifies the intended audience, related materials, document conventions, and contact information for technical support.

The remainder of this guide is organized into the following chapters and appendices:

Chapter 1 Getting Started defines data migration terms, provides basic understanding of the planning process, and helps the administrator to associate the new data LUN (destination LUN) back to the application.

Chapter 2 Inventory Checklists outlines the details the administrator must incorporate for data migration planning.

Chapter 3 Performance and Downtime describes methods for optimizing data migration performance and minimizing downtime using the iSR6200.

Preface

Documentation Conventions

viii ISR654607-00 D

Chapter 4 Operating Systems Dependencies provides some specific information on operating system dependencies.

Appendix A Checklist Examples provides examples of completed data migration checklists.

Appendix B Assigning LUNs to the iSR6200 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 quickly locate the needed information.

Documentation ConventionsThis guide uses the following documentation conventions:

NOTE: provides additional information.

CAUTION! indicates the presence of a hazard that has the potential of causing damage to data or equipment.

Text in blue font indicates a hyperlink (jump) to a figure, table, or section in this guide. Links to Web sites are shown in underlined blue. For example:

Table 9-2 lists problems related to the user interface and remote agent.

See “Installation Checklist” on page 3-6.

For more information, visit www.qlogic.com.

Text in bold font indicates user interface elements such as a menu items, buttons, check boxes, or column headings. For example:

Click the Start button, point to Programs, point to Accessories, and then click Command Prompt.

Under Notification Options, select the Warning Alarms check box.

Text in Courier font indicates a file name, directory path, or command line text. For example:

To return to the root directory from anywhere in the file structure:Type cd /root, and then press ENTER.

Enter the following command: sh ./install.bin

Key names and key strokes are indicated with UPPERCASE:

Press CTRL+P.

Press the UP ARROW key.

Preface

License Agreements

ISR654607-00 D ix

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.

Screen shots that depict only the portion of the interface currently under discussion are shown with jagged edges. For example:

Figure i. Jagged Edged Screen Shot Depicting Partial Interface

License AgreementsRefer to the QLogic Software End User License Agreement for a complete listing of all license agreements affecting this product.

Technical SupportCustomers should contact their authorized maintenance provider for technical support of their QLogic products. QLogic-direct customers may contact QLogic Technical Support; others will be redirected to their authorized maintenance provider. Visit the QLogic support Web site listed in Contact Information for the latest firmware and software updates.

For details about available service plans, or for information about renewing and extending your service, visit the Service Program Web page at http://www.qlogic.com/services.

http://www.qlogic.com/services

Preface

Technical Support

x ISR654607-00 D

TrainingQLogic offers training for technical professionals for all iSCSI, InfiniBand, and Fibre Channel products. From the main QLogic Web page at www.qlogic.com, click the Support tab at the top, and then click Training and Certification on the left. The QLogic Global Training portal offers online courses, certification exams, and scheduling of in-person training.

Technical Certification courses include installation, maintenance and troubleshooting QLogic products. Upon demonstrating knowledge using live equipment, QLogic awards a certificate identifying the student as a certified professional. You can reach the training professionals at QLogic by e-mail at [email protected].

Contact InformationQLogic Technical Support for products under warranty is available during local standard working hours excluding QLogic Observed Holidays. For customers with extended service, consult your plan for available hours. For Support phone numbers, see the Contact Support link at support.qlogic.com.

Knowledge DatabaseThe QLogic knowledge database is an extensive collection of QLogic product information that you can search for specific solutions. We are constantly adding to the collection of information in our database to provide answers to your most urgent questions. Access the database from the QLogic Support Center: http://support.qlogic.com.

Support Headquarters QLogic Corporation4601 Dean Lakes Blvd.Shakopee, MN 55379 USA

QLogic Web Site www.qlogic.com

Technical Support Web Site http://support.qlogic.com

Technical Support E-mail [email protected]

Data Migration Support E-mail [email protected]

Technical Training E-mail [email protected]

http://www.qlogic.com

mailto:[email protected]

http://support.qlogic.com

http://www.qlogic.com






ISR654607-00 D 1-1

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 iSR6200 can deliver up to 4TB/hr. migration rate. Following the suggestions outlined in this guide will enable performance of most migration jobs using simple offline migration, while meeting application downtime requirements. Thus, it removes the complexity of performing online data migration using other data migration tools.

TerminologyThis guide uses the following terms:

Mount point: A node or a directory where application data is stored.

Volume: A single, logical presentation of one or more physical disks.

Physical disk: The raw disk device discovered and configured in the operating system. The object represented in the operating system is usually associated to a LUN on a storage array.

Multipathing software: The LUN may be accessed through multiple ports on a storage array. Each port of a storage array may be accessed through multiple ports (adapters) in the server. Multipathing software in the host manages the multiple paths to a LUN.

1–Getting Started

Relationship Between Application Data and Physical Storage

1-2 ISR654607-00 D

Relationship Between Application Data and Physical Storage

Successful data migration requires an understanding of the relationship between the application data and the physical device (LUN).

Typically, the application accesses the data using a mount point. For example:

The Windows® SharePoint® application accesses its data through a mount point F:\Sharepoint.

The Oracle® application running on a HP-UX (UNIX) host accesses its data through a mount point /home/oracle.

The Apache™ Web Server application on a Linux (UNIX) host access its data through a mount point /data/webinfo.

Typically, the administrator creates a mount point on a volume. On Windows, volume refers to a drive letter (for example, D:\ or F:\). On UNIX operating systems, a mount point may be on a volume managed by a logical volume manager (Veritas™ or native), or a mount point may be directly on a raw device (/dev/rdsk/c0t1d4).

One can create a volume either on a single physical disk or on multiple physical disks. For example, in Windows, drive letter F:\ may span multiple physical disks (Disk2, Disk3, and so on). On UNIX, a Veritas Volume Manager may have a volume /dev/vg-1/vol1 created on three physical disks: /dev/rdsk/c0t1d2, /dev/rdsk/c0t1d3, and /dev/rdsk/c0t1d4.

The physical disk or a raw device is associated with a LUN. For example, in Windows, Disk2 is LUN 5 on a storage array and Disk3 is LUN 6 on a storage array. In UNIX, /dev/rdsk/c0t1d2 is LUN 2 on a storage array and /dev/rdsk/c0t1d3 is LUN 3 on a storage array.

NOTE:

UNIX® operating system in this discussion refers to HP-UX, Linux®, Solaris®, and AIX®.

1–Getting Started

LUN Access to a Server

ISR654607-00 D 1-3

LUN Access to a ServerMultipathing software installed on the server typically manages multipaths to a LUN. In a typical SAN:

A single storage array serves multiple servers and provides controlled access to the LUN, often referred to as LUN presentation.

Multiple servers and storage arrays are present. Server access to a storage array is often controlled by name server zoning.

General Steps for Data MigrationTo 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.

3. Based on the type of migration (offline, online local, or online remote), prepare the zones and setups. For zone configuration information, see the Data Migration Service for iSR6200 User’s Guide.

4. Configure the iSR6200 for migration. For detailed instructions, see the Data Migration Service for iSR6200 User’s Guide (recommendations in the “Performance” chapter) and the SANsurfer Router Manager help system (“Using DMS” book).

5. Migrate the data.

6. Adjust the Fibre Channel zoning in the Fibre Channel switches, and then update the LUN presentation from the destination storage array to the server.

NOTE:

The data migration planning template is attached to this guide as a Microsoft® Excel® spreadsheet. To view the template:

1. In Adobe Reader®, open the View menu, point to Navigation Panels, and then click Attachments.

2. Double-click the iSR6200_Data_Migration_Planning_Template.xlsx file to open it.

1–Getting Started

General Steps for Data Migration

1-4 ISR654607-00 D

7. After data is migrated from one storage to another storage, do the following:

Update the multipathing software on the server, if necessary.

Adjust the mount point for the volume, if necessary. In most cases, volumes are automatically discovered under Windows and UNIX (HP-UX, Linux, Solaris) systems configured with logical volume managers. For details, see Appendix B Assigning LUNs to the iSR6200 for Data Migration.

8. For record keeping, save the migration logs.

ISR654607-00 D 2-1

2 Inventory Checklists

Data migration checklists help the system administrator 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 to identify possible changes required on the server after migration.

The tables in this chapter are designed to take proper inventory used for planning data migration, including:

Step 1: List the Source and Destination Storage Array

Step 2: List the Servers Impacted by the Data Migration Project

Step 3: List the Applications, Mount Points, and Paths to the Physical Devices

Step 4: List and Create LUN ID Mappings

Step 5: List and Create Fibre Channel Zoning

2–Inventory Checklists


2-2 ISR654607-00 D


The information requested in Table 2-1 can be retrieved from the storage administrator in the data center.


The information requested in Table 2-2 can be retrieved by the server administrator(s). Installation of new multipathing software may be required when changing the class of an array or changing the array vendor, as may be an upgrade to existing software for the same class of array.

Table 2-1. Storage Array Information

Storage Array

Source or Destina-

tionFirmware Version

Array Man-agement Software a

a The storage array specific software that is used in data migration to present the source LUNs to the iSR6200, and to create destination LUNs to be presented to the iSR6200 and to the server. The array management software also provides the controller and WWPN information for the storage array ports.

Num-ber of Con-

trollersWWPN b (Fibre Chan-

nel)

b World wide port name of the Fibre Channel array; used in performing zoning in Fibre Channel switch firmware.

Table 2-2. Server Information

Server

Operating System and

Version IP Address

Multipathing Software for Source Array

Logical Vol-ume Manager

(if any)

Multipathing Software for Destination

Array



ISR654607-00 D 2-3


The applications, mount points, and paths to the physical device requested in Table 2-3 can be retrieved by the server administrator. For the Windows operating system (OS) or for any UNIX OS with a logical volume manager (LVM), the LUN ID association with the server or application and volume is the most important because, in most cases, the OS will automatically discover the relationship between the volume and the migrated LUN(s) on a destination storage array.

Step 4: List and Create LUN ID MappingsCreate a list of LUNs containing the size and mapping information that shows how the LUNs are seen by the server and the iSR6200, as shown in Table 2-4. Although a specific LUN may be presented at a different LUN ID to a server other than to iSR6200, it is recommended that the same LUN ID is used, if possible. This practice will be very helpful while creating new LUNs on a destination array, and while presenting source and destination LUNs to iSR6200 data migration service. For operating systems other than Windows, it is highly recommended that source and destination LUNs are the same size.

This step uses the LUN remapping feature of SANsurfer Router Manager to map the LUNs to the server through iSR6200. With LUN remapping, you can present LUNs to the iSR6200 at any available ID, without regard for the IDs that are presented to the server. You can also present the same LUNs to the server through the iSR6200 as presented by the array.

Table 2-3. Physical Device Information

Server ApplicationMount Point

(if any) Volume

Physical Disk or Raw Device

Node LUN ID



2-4 ISR654607-00 D

Step 5: List and Create Fibre Channel ZoningFor a Fibre Channel SAN, create a list of fabric zones that contain the WWPN associated with servers, storage arrays (source and destination) and iSR6200, as shown in Table 2-5. The destination array should be zoned in only with the iSR6200 before migration. After migration, the destination arrays should be zoned in with servers, as shown in Table 2-6.

Table 2-4. LUN ID Mappings

Server

Source LUN

Seen by the

Server as LUN

ID

Volume ID,

Source Array (if applica-

ble)Capac-

ity

Source LUN Destination LUN

Capac-ity

Pre-sented to iSR6200

as LUN ID

Remapped and Pre-sented to

Host Through

iSR6200 at LUN ID

Pre-sented to iSR6200

as LUN ID

Pre-sented to Server as

LUN ID

Table Notes

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 some-times on large arrays, different LUNs with the same LUN ID are presented to different hosts.

Table 2-5. Pre-Migration Fibre Channel Zoning Information

Fibre Channel Switch and IP

AddressFibre Channel

Zone Name Zone Members (WWPNs)Server, iSR6200, Storage Name



ISR654607-00 D 2-5

Table 2-6. Post-Migration Fibre Channel Zoning Information






2-6 ISR654607-00 D

ISR654607-00 D 3-1

3 Performance and Downtime

This chapter provides recommendations designed to improve performance and minimize downtime during data migration.

Optimizing Performance During Data MigrationThe iSR6200 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. One set of LUNs shows active optimized paths on one controller, while another set of LUNs shows active optimized paths on a different controller.

Where high availability (HA) configuration as redundant SAN is deployed, QLogic highly recommends the following:

Connect one Fibre Channel port from the iSR6200 blade to one SAN, and connect the other port to the redundant SAN.

Connect Fibre Channel ports from the destination array to both SANs.

Maximize array performance by simultaneously running 4 to 8 active jobs on a single array. The iSR6200 can have up to 256 migration jobs per blade.

Balance across two controllers the LUNs used in migration jobs that run simultaneously.

Minimizing Downtime for Offline MigrationThe iSR6200's ability to deliver a migration rate of 4TB/hr. per blade—combined with seamless integration of the iSR6200 in the SAN and data protection features such as array attributes (source/destination)—make it likely that the downtime objective will be met by offline data migration. The following recommendations will simplify the data migration project:

Configure all migration jobs in the iSR6200 before application downtime begins.

Deploy dual blade configuration in the iSR6200 to achieve up to 8TB/hr. (for storage arrays that are capable of delivering such performance).

3–Performance and Downtime

Minimizing Downtime for Offline Migration

3-2 ISR654607-00 D

Before Application DowntimeBefore application downtime, follow these steps:

1. Plan the data migration project:

a. Create the migration checklist.

b. Determine if a change in multipathing 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 iSR6200.

d. Plan to migrate together the LUNs from the same server/cluster.

2. Configure the iSR6200 in the SAN: Perform proper zoning such that the iSR6200 can see ports from both the source and destination arrays.

3. On the destination array, create LUNs that are of equal or greater size than the source LUNs.

Do not present LUNs from the destination array to the server until migration is complete.

4. Based on the order in which LUNs should be migrated, balance the LUNs across multiple controllers of the same array.

5. Present the source LUNs and destination LUNs to the iSR6200.

6. Using the iSR6200 user interface, assign appropriate (source/destination) attributes to the storage array.

7. Using the iSR6200, create user-defined groups to assign the migration jobs related to the same server in a single group.

8. Using the user interface wizard, configure migration jobs.

During Application DowntimeDuring application downtime, follow these steps:

1. Confirm with the storage administrator that the application and server are down, and that the server no longer has access to the storage under migration.

2. Remove the server access to the source storage array by changing the Fibre Channel zoning such that server adapter ports can no longer see the source or destination array ports.

3. Start the previously configured migration jobs.

4. If required, install the new multipathing software on the server.



ISR654607-00 D 3-3

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.

Validating Integrity of the DataIf there is a file system on the LUN, perform a quick file system check by bringing up the application and confirming access to the data.



3-4 ISR654607-00 D

ISR654607-00 D 4-1

4 Operating Systems Dependencies

If the source array type is different from the destination array type, installation of the new multipathing software associated with the destination array may be required.

Windows OSMigrating data for Windows servers is not difficult. Windows offers two types of disks: basic disks and dynamic disks. In most cases, Windows will discover the migrated volumes whenever migrated LUNs are seen by the server.

Take the following precautions:

Do not create new drive letters while data migration is in process.

Ensure that the destination LUN size is equal or greater than the source LUN size.

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.

NOTE:

A dynamic disk may appear in an offline state after migration and even after presenting the new LUN to the server. To bring the disk to an online state:

1. In the Device Manager, right-click the disk.

2. Depending on the Windows OS version, click either Import Foreign Disk or Reactivate Disk.

When all dynamic disks are brought back online, the volume will be mounted for application access.

4–Operating Systems Dependencies

UNIX OS (HP-UX, Linux, AIX, Solaris)

4-2 ISR654607-00 D

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:

For offline migration, export the volume before migration begins.

For online migration, SANsurfer Router Manager exports volumes when the migration job is complete and applications are ready to be moved to the destination array.

Import the volume after migration is complete and destination LUNs are presented to the server.

If volumes are not managed through a logical volume manager in the system, it is very important to follow the pre-migration checklists to identify the physical device node(s) (/dev/rdsk/c0t1d1) on which the volume is mounted. After data migration, the physical device node may change. Change the volume mount such that it now it points to the new physical device (dev/rdsk/c0t2d5).

To discover current active mount points, issue the mount command on the system console.

Some applications, such as the Oracle Cluster File system (OCFS) may directly use the raw devices. Consult the system administrator. OCFS may automatically discover the migrated devices. Follow the procedure listed in OCFS manual.

The destination LUN size must be equal to or greater than that of the source LUN. Expand the destination LUN after the migration is complete and the migrated volume is remounted. (Destination LUN expansion is not supported on Solaris.)

ISR654607-00 D A-1

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.


Table A-1. Example: Storage Array Information

Storage Array

Source or Destination

Firmware Version

Array Management

Softwarea

a The storage array specific software that will be used in data migration to present the source LUNs to the iSR6200, and to create destination LUNs to be presented to the iSR6200 and to the server. The array management software will also provide the controller and WWPN information for the storage array ports.

Number of Con-trollers

WWPNb (Fibre Channel)

b World wide port name of the Fibre Channel array; used in performing zoning in Fibre Channel switch firmware.

EMC CX3-20 Source 03.24.040.5.006

Navisphere 2 50-06-01-60-41-e0-18-94

50-06-01-61-41-e0-18-94

50-06-01-62-41-e0-18-94

50-06-01-63-41-e0-18-94

HP EVA 4400 Destination CR0D63xc3p-6000

Command View

2 50-00-1F-E1-50-06-22-A1

50-00-1F-E1-50-06-22-A2

50-00-1F-E1-50-06-22-A2

50-00-1F-E1-50-06-22-A3

50-00-1F-E1-50-06-22-A4

A–Checklist Examples


A-2 ISR654607-00 D


Table A-2 shows an example of the server information that can be retrieved by the server administrator.

Step 3: List Applications, Mount Points, and Paths to the Physical Device

Table A-3 shows an example of the applications, mount points, and path to the physical device, which can be retrieved from the server administrator.

Table A-2. Example: Server Information

Server

Operating System and

Version IP Address

Multipathing Software for Source Array

Logical Volume

Manager (if any)

Multipathing Software for Destination

Array

HR-Dept Windows SP2 10.3.3.1 EMC Power-Path® for Windows

N/A MPIO DSM for EVA

iPortal SUSE 10 10.4.3.2 EMC Power-Path for Linux

None Device Mapper

Sales HP-UX 11.3 10.4.3.3 EMC Power-Path for HP-UX

Veritas Secure Path for HP-UX

Table A-3. Example: Physical Device Information

ServerApplica-

tionMount Point

(if any) Volume

Physical Disk or Raw Device

Node LUN ID

HR-Dept Sharepoint F:\Sharepoint F:\ Disk0, Disk1 (Dynamic Disks)

0, 1

iPortal Apache Web Server

/data/webinfo /dev/sdb /dev/sdb 0

Sales Oracle /home/oracle /dev/vg-2/vol2

/dev/rdsk/c0t1d0

/dev/rdsk/c0t1d1

/dev/rdsk/c0t1d2

0, 1, 2


Step 4: List and Create LUN ID Mappings

ISR654607-00 D A-3

Step 4: List and Create LUN ID MappingsTable A-4 shows LUNs presented to the iSR6200 at LUN IDs that are different from the IDs presented to the server. You can later use the LUN remapping feature to present LUNs to the server with the original LUN IDs. Through the iSR6200, a different LUN from a storage array is presented as the same LUN ID (2) on two different servers: HR-Dept and iPortal.

Step 5: List and Create Fibre Channel ZoningTable A-5 assumes a redundant configuration, meaning there are:

Two Fibre Channel switches Multiple servers, each with two adapter ports One storage array with two controllers Four ports per controller

Table A-4. Example: LUN ID Mappings

Server

Source LUN

Seen by the

Server as LUN

ID

Volume ID,

Source Array (if applica-

ble)Capac-

ity

Source LUN Destination LUN

Capac-ity

Pre-sented to iSR6200 as LUN

ID

Remapped and Pre-sented to

Host Through

iSR6200 at LUN ID

Pre-sented to iSR6200 as LUN

ID

Pre-sented to Server as

LUN ID

HR-Dept.

0

1

1

2

100GB

250GB

0

1

0

1

0

1

0

1

200GB

500GB

iPortal 0 3 250GB 2 0 2 0 250GB

Sales 0

1

2

4

5

6

300GB

300GB

300GB

3

4

5

0

1

2

3

4

5

0

1

2

300GB

300GB

300GB



A-4 ISR654607-00 D

Table A-6 shows new Fibre Channel zones information to configure iSR6200 for data migration and to migrate the data. The iSR6200 Fibre Channel ports are configured with source and destination arrays.

Table A-5. Example A: Pre-Migration Fibre Channel Zoning Information




FC-SW-1

10.5.3.1

Zone-A 21-00-00-C0-DD-C0-8A-D7

21-00-00-C0-DD-C0-55-57

21-00-00-C0-DD-C0-60-66

50-06-01-60-41-E0-18-94

50-06-01-62-41-E0-18-94

HR-Dept: P1

iPortal: P1

Sales: P1

SRC-Array-ABC: P1

SRC-Array-ABC: P3

FC-SW-2

10.5.3.2

Zone-B 21-00-00-C0-DD-C0-8A-D8

21-00-00-C0-DD-C0-55-58

21-00-00-C0-DD-C0-60-67

50-06-01-61-41-E0-18-94

50-06-01-63-41-E0-18-94

HR-Dept: P2

iPortal: P2

Sales: P2

SRC-Array-ABC: P2

SRC-Array-ABC: P4

Table A-6. Example B: Pre-Migration Fibre Channel Zoning Information




FC-SW-1

10.5.3.1

Zone-A-DM 21-00-00-C0-DD-C0-88-81

50-06-01-60-41-E0-18-94

50-06-01-62-41-E0-18-94

50-00-1F-E1-50-06-22-A1

50-00-1F-E1-50-06-22-A2

iSR6200, FC1

SRC-Array-ABC: P1

SRC-Array-ABC: P3

DEST-Array-XYZ: P1

DEST-Array-XYZ: P3

FC-SW-1

10.5.3.2

Zone-B-DM 21-00-00-C0-DD-C0-88-82

50-06-01-61-41-E0-18-94

50-06-01-63-41-E0-18-94

50-00-1F-E1-50-06-22-A8

50-00-1F-E1-50-06-22-A9

iSR6200: FC2

SRC-Array-ABC: P2

SRC-Array-ABC: P4

DEST-Array-XYZ: P2

DEST-Array-XYZ: P4



ISR654607-00 D A-5

Table A-7 shows an example of post-migration Fibre Channel zoning information.

Table A-7. Example: Post-Migration Fibre Channel Zoning Information




FC-SW-1/10.5.3.1 Zone-A 21-00-00-C0-DD-C0-8A-D7

21-00-00-C0-DD-C0-55-57

21-00-00-C0-DD-C0-60-66

50-00-1F-E1-50-06-22-A1

50-00-1F-E1-50-06-22-A2

HR-Dept: P1

iPortal: P1

Sales: P1

DEST-Array-XYZ: P1

DEST-Array-XYZ: P3

FC-SW-2/10.5.3.2 Zone-B 21-00-00-C0-DD-C0-8A-D8

21-00-00-C0-DD-C0-55-58

21-00-00-C0-DD-C0-60-67

50-00-1F-E1-50-06-22-A8

50-00-1F-E1-50-06-22-A9

HR-Dept: P2

iPortal: P2

Sales: P2

DEST-Array-XYZ: P2

DEST-Array-XYZ: P4



A-6 ISR654607-00 D

ISR654607-00 D B-1

B Assigning LUNs to the iSR6200 for Data Migration

For successful completion of data migration, assign source and destination LUNs to the iSR6200 using storage array management tools. The iSR6200 appears as a host to the array controller. When you register the iSR6200 port WWNs, you must set the correct attributes. Ensure that you register all WWNs belonging a specific virtual port (VP) group under a single host entity.

This appendix provides procedures for using some of the array management tools to assign LUNs, including:

“Assigning LUNs from an HP MSA2012fc Array” on page B-2

“Assigning LUNs from an HP MSA1000/1500 Array” on page B-5

“Assigning LUNs from an HP 3PAR Array” on page B-8

“Assigning LUNs from an HP EVA 4/6/8000 Series Array” on page B-16

“Assigning LUNs from an HDS Array” on page B-20

“Assigning LUNs from an EMC CLARiiON Array” on page B-25

“Assigning LUNs from an EMC Symmetrix DMX-4 Array” on page B-31

“Assigning LUNs from an IBM DS4K/DS5K/LSI Array” on page B-34

“Assigning LUNs from an IBM V7000 Array” on page B-38

“Assigning LUNs from a NetApp FAS2040 System Using FilerView” on page B-42

“Assigning LUNs from a NetApp FAS2040 System Using NetApp System Manager” on page B-45

“Assigning LUNs from a Xiotech Emprise 5000 Array” on page B-48

NOTE:

For online migration for an HP-UX host, ensure that the host platform and node setting for the iSR6200 are exactly the same as the HP-UX host settings in the respective array management software.

B–Assigning LUNs to the iSR6200 for Data Migration

Assigning LUNs from an HP MSA2012fc Array

B-2 ISR654607-00 D

“Assigning LUNs from a Xiotech Magnitude 3D 4000 Array” on page B-50




To assign LUNs:

1. 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_MSA2012, and then add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports in this zone.

c. Save the zoning information and activate the new zoning configuration.

2. In Internet Explorer, open the Storage Management Utility using the IP address assigned to the storage controller.

3. In the left pane, click Manage to open the management menu (see Figure B-1).

Storage Vendor HP

Array Model MSA2012fc arrays

LUN Assignment Tool Storage Management Utility user interface



ISR654607-00 D B-3

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-4 ISR654607-00 D

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).


Assigning LUNs from an HP MSA1000/1500 Array

ISR654607-00 D B-5

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. 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.)


Storage Vendor HP

Array Model MSA 1000/1500 arrays

LUN Assignment Tool Storage Navigator Modular user interface



B-6 ISR654607-00 D

To assign LUNs:



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. Save the zoning information and activate the new zoning configuration.

2. Open the Array Configuration Utility.

The Configure Available Device(s) window appears, as shown in Figure B-4.

Figure B-4. Configure Available Device(s)

3. In the right pane under Common Tasks, click Selective Storage Presentation, and then click Enable.

A list of the WWPNs seen by the MSA controller appears, as shown in Figure B-5.



ISR654607-00 D B-7

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.

Figure B-6. Selecting the Host Mode


Assigning LUNs from an HP 3PAR Array

B-8 ISR654607-00 D

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.



To assign LUNs:

1. Create a host entity for router ports on the array; this step is needed to map the LUNs to the routers.

a. In the 3PAR Inform Management Console, select Hosts in the left pane, and then click Create Host.

b. On the Create Host wizard, General page (see Figure B-8), enter a Name for the host, and then in the Persona box, select Generic-ALUA as the host type. Click Next to continue.

Storage Vendor HP

Array Model 3PAR® Utility Storage arrays

LUN Assignment Tool 3PAR Inform Management Console



ISR654607-00 D B-9

Figure B-8. Creating a Host: General

c. On the Create Host wizard, Fibre Channel page (see Figure B-9), select all VP ports under Available WWNs, and then click the left arrow to move them to the Assigned WWNs column. Ensure that you create a single host entity for all WWPNs from a single VPG. For example, all VP1 ports from the router’s Fibre Channel ports must be part of one host entity. Create a separate host for VP2, VP3, and VP4. Then click Finish to create the hosts.



B-10 ISR654607-00 D

Figure B-9. Creating a Host: Fibre Channel

2. Create a common provisioning group (CPG), which is a buffer pool of logical disks that you use to create LUNs (virtual volumes). CPGs have the following qualities:

A CPG is a thin-provisioned entity. Physical space (chunklets) are assigned as and when virtual volumes are created (depending on whether the LUN is thick- or thin-provisioned).

You can create a CPG for any specific disk type and speed.

You can assign to the CPG a RAID group that ensures that any LUN (virtual volume) created using this CPG has an assigned RAID level.

You can create multiple CPGs without consuming physical space on disks.



ISR654607-00 D B-11

a. In the 3PAR Inform Management Console, select Provisioning in the left pane, and then click Create CPG.

b. On the Create CPG wizard, General page (see Figure B-10), enter a Name for the CPG, and then select values for the Device Type, Device Speed, RAID Type, and Set Size. Select the Show advanced options panel(s) check box, and then click Next to continue.

Figure B-10. Creating a CPG: General

c. On the Create CPG wizard, Allocation Settings page (see Figure B-11), either accept the default Availability setting, or select either Port, Magazine, or Cage, depending on the available array model and disk types. Do not change the default Step Size and Preferred Chunklets settings. Click Next to continue.



B-12 ISR654607-00 D

Figure B-11. Creating a CPG: Allocation Settings

d. On the Create CPG wizard, Disk Filter page, either accept the default disk filter, or select a new filter with which to select disks for the CPG. Click Next to continue.

e. On the Create CPG wizard, Summary page, review your settings and then either click Prev to go back and change the selections, or click Finish to create the CPG.

f. In the left pane under Provisioning, click CPGs to view the newly created CPG in the right pane. Total capacity is shown as 0.00 because no virtual volumes have been created on this CPG.

3. Create virtual volumes (LUNs) using any of the available CPGs. The LUN type (thin- or thick-provisioned) determines the actual disk consumption by a CPG.

a. In the 3PAR Inform Management Console, select Provisioning in the left pane, and then right-click Virtual Volumes.

b. On the shortcut menu, click Create Virtual Volume.

c. On the Create Virtual Volume wizard, General page (see Figure B-12), follow these steps:

Under General, enter a Name for the volume.



ISR654607-00 D B-13

Under User Space, specify the volume Size, Provisioning option, CPG name.

For thin-provisioned volumes, set the Allocation Warning based on the percentage of available space.

Under Grouping, specify the Count (number of virtual volumes to be created at one time within the set). 3PAR automatically enters a Set Name.

Click Next to continue.

Figure B-12. Creating a Virtual Volume: General

d. On the Create Virtual Volume wizard, Copy Space Settings page, select <none> for the CPG copy space. (Copy space creates a backup of the same virtual volumes, which you can store on a different CPG.) Click Next to review the virtual volume configuration.

e. On the Create Virtual Volume wizard, Summary page, review your settings and then either click Prev to go back and change the selections, or click Finish to create the virtual volume.



B-14 ISR654607-00 D

f. In the left pane under Provisioning, click Virtual Volumes to view the newly created volume details in the right pane. Thin-provisioned volumes will show minimal used space (by default, they occupy some space for administrative data).

4. Map a virtual volume to the host as follows:

a. In the 3PAR Inform Management Console, right-click Hosts in the left pane, and then on the shortcut menu, click Export Volume.

b. On the Export Virtual Volume wizard, General page, click one of the following, and then click Next:

Click the Virtual Volume button, and then manually select one or more volumes from the list.

Click the Virtual Volume Set button; all virtual volumes in the set are automatically selected.

c. On the Export Virtual Volume wizard, Settings page (see Figure B-13), do the following, and then click Next:

Click Host, and then select the host to which the virtual volumes must be presented.

For Port, accept the default option, <none>.

For LUN, either type the ID in the box, or select the Auto check box to have the LUN ID assigned automatically. If there are multiple virtual volumes, subsequent IDs are assigned starting from the entered value.



ISR654607-00 D B-15

Figure B-13. Exporting a Virtual Volume: Settings

d. On the Export Virtual Volume wizard, Summary page, review your settings and then either click Prev to go back and change the selections, or click Finish to export the virtual volume.

e. In the left pane under Hosts, click Virtual Volumes to view the volume details in the right pane. Under Host Details in the right pane, click the VLUNs tab, and then click the Path Summary tab (see Figure B-14).


Assigning LUNs from an HP EVA 4/6/8000 Series Array

B-16 ISR654607-00 D

Figure B-14. Viewing Host Details: Path Summary


To assign LUNs:



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. Save the zoning information and activate the new zoning configuration.

2. Open the Command View EVA application, as shown in Figure B-15.

Storage Vendor HP

Array Model EVA 4/6/8000 series arrays

LUN Assignment Tool Command View user interface



ISR654607-00 D B-17

Figure B-15. Opening Command View EVA

3. In the left pane, double-click the array that you want to manage. This expands the nodes under the selected array.

4. In the left pane, click the Hosts node.

5. Complete the Add a Host information in the right pane as follows (see Figure B-16):

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.



B-18 ISR654607-00 D

Figure B-16. Adding a Host

6. If you have a multipath configuration, add the second router port to the DM-Host entity as follows (see Figure B-17):

a. Under the Hosts tree in the left pane, click the DM-Host node.

b. In the right pane, click the Ports tab.

c. On the Add a Host Port page, select a WWN, and then click the Add port button.



ISR654607-00 D B-19

Figure B-17. Adding a Second Host Port

7. Present virtual disks as follows (see Figure B-18):

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.


Assigning LUNs from an HDS Array

B-20 ISR654607-00 D

Figure B-18. Presenting Vdisks



To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_HDS.

Storage Vendor HDS

Array Model AMS/WMS series arrays

LUN Assignment Tool Storage Navigator Modular user interface



ISR654607-00 D B-21



2. Open the Storage Navigator Modular application. If you are using the tool for the first time, you may have to discover the array using the IP assigned to the storage controller.

3. On the Tool menu, click Operation Mode > Change, and then change to Management Mode (see Figure B-19).

Figure B-19. Changing to Management Mode

4. Under Array Unit, double-click the name of the array to manage.

The Array System Viewer window opens.

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-20).



B-22 ISR654607-00 D

Figure B-20. 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-21.



ISR654607-00 D B-23

Figure B-21. 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:

a. Next to Platform, select Windows2003.

b. Keep the other settings as default.

c. To save the changes, click OK.

11. In the Array System Viewer dialog box, under the DM-Host group, click the WWN node. Then at the bottom of the right pane, click Modify WWN Information (see Figure B-22).



B-24 ISR654607-00 D

Figure B-22. 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. Complete the Modify Mapping dialog box as follows (see Figure B-32):

a. Under H-LUN / Available Logical Units, select an appropriate LUN.

b. Click the (up arrow) to map the LUN to the DM-Host group.

c. To accept and save the LUN assignment, click OK.


Assigning LUNs from an EMC CLARiiON Array

ISR654607-00 D B-25

Figure B-23. 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. You may have to reboot the data migration appliance or generate a registered state change notification (RSCN) to initiate a full rescan on HDS array, because it does not send any notification indicating changes in LUN assignment to the logged in initiators.


To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_EMC.

Storage Vendor EMC

Array Model CLARiiON® CX/AX series arrays

LUN Assignment Tool Navisphere



B-26 ISR654607-00 D

c. Add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports in this zone.


2. 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-24.

Figure B-24. Viewing Enterprise Storage

3. Select the appropriate storage array, right-click the array name, and then click Connectivity Status.

4. Select the WWPN associated with the data migration appliance, and then click Register.



ISR654607-00 D B-27

5. Complete the Register Initiator Record dialog box as follows (see Figure B-25):

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-25. Registering Initiator Record

6. Create a storage group to add to the newly-registered DM-Host entity as follows (see Figure B-26):

a. In the Enterprise Storage window, Storage page, right-click the Storage Groups node.

b. Click Create Storage Group.



B-28 ISR654607-00 D

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-26. Creating Storage Group

The new DM-Host storage group is listed under the Storage Groups tree in the main window.

7. Add the DM-Host host entity to the DM-Host storage group entity as follows (see Figure B-27):

a. Under the Storage Groups node, right-click DM-Host.

b. Click Connect Hosts.

c. In the DM-Host: Storage Group Properties dialog box, click the Hosts tab.

d. On the Hosts page under Available Hosts, select the DM-Host host entity.



ISR654607-00 D B-29

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-27. Adding DM-Host to Storage Group

8. Add LUNs to the DM-Host storage group entity as follows (see Figure B-28):

a. Under the Storage Groups tree, right-click DM-Host.

b. Click Select LUNs to view a list of available LUNs.

NOTE:

Before you assign LUNs, your must register as a single host entity all router ports that will access the same LUNs. If you later add a new router port to an existing host entity, that port will not appear as a new path for the assigned LUNs in the router’s show luninfo command output.



B-30 ISR654607-00 D

c. In the DM-Host: Storage Group Properties dialog box, click the LUNs tab.

d. On the LUNs page, select All on the Show LUNs list to view all LUNs that have been assigned to the host and will be part of the data migration jobs.

e. Under Available LUNs, select the check box next to each LUN to be assigned for data migration jobs (as determined during the planning phase of the data migration activity).

Figure B-28. Adding LUNs to DM-Host

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 update the display.)


Assigning LUNs from an EMC Symmetrix DMX-4 Array

ISR654607-00 D B-31


To assign LUNs:

1. Perform zoning by creating and activating zones containing DMX Fibre Adapter ports and iSR6200 Fibre Channel ports for data migration.

2. Launch the EMC Symmetrix Management Console.

3. (Optional) If the server is running firmware 3.3.0.3 and earlier, you must disable the volume set addressing bit and enable the SCSI Primary Commands - 2 (SPC-2) protocol version bit. Follow these steps to set those port properties:

a. Click the Properties Task button, and then under Director > Fibre > Port, right-click the port.

b. Select Port and Director Configuration > Set Port Properties.

c. Clear the Volume Set Addressing check box.

d. Select the SPC2 Protocol Version check box.

4. To start the masking wizard, click the Tasks button, and then under Operations > Provisioning, click Provision Storage (Masking Wizard).

5. In the wizard’s right pane under 1. Welcome, click Next to continue.

6. Under 2. Select Symmetrix ID, select the ID, and then click Next.

7. Under 3. Select Initiators, follow these steps (see Figure B-29):

a. Click Initiators.

b. Under Available Initiators, select one or more initiators and then click Add to move your selections to the Selected Initiators table.

c. Select the Refresh VCMDB check box.

d. Click Next to continue.

Storage Vendor EMC

Array Model Symmetrix® DMX-4 arrays

LUN Assignment Tool EMC Symmetrix Management Console



B-32 ISR654607-00 D

Figure B-29. Selecting Initiators

8. Under 4. Select Ports, follow these steps (see Figure B-30):

a. Under Available Ports, select one or more ports and then click Add to move your selections to the Selected Ports table.

b. Click Next to continue.



ISR654607-00 D B-33

Figure B-30. Selecting Ports

9. In the right pane under 5. Select Devices, follow these steps (see Figure B-31):

a. For Group Type, select Ungrouped.

b. Under Available Devices, select one or more devices, and then click Add to move your selections to the Selected Devices table.

c. Select the Map selected devices to all ports check box.

d. Click Next to continue.


Assigning LUNs from an IBM DS4K/DS5K/LSI Array

B-34 ISR654607-00 D

Figure B-31. Selecting Devices

10. In the right pane under 6. Summary, review your masking selections and then either click Back to modify a previous step, click Next to continue, or click Finish to close the masking wizard and return to the Tasks page of the EMC Symmetrix Management console.

A message box informs you that the Symmetrix device masking session completed successfully.


Storage Vendor IBM

Array Model IBM DS4000/Engineo series arrays

LUN Assignment Tool Storage Manager Client 1e



ISR654607-00 D B-35

To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_IBM.



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. In the left pane, right-click Default Group, point to Define, and then click Host. (see Figure B-32).

Figure B-32. Selecting Host to Define

5. Complete the Define Host wizard as follows (see Figure B-33):



B-36 ISR654607-00 D

Figure B-33. Defining the Host

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. Click Edit, and then in the Edit Identifier/Alias dialog box, type an alias for the WWPN. Click OK to close the dialog box.

e. Click Next.

f. In the Specify Host Type window (see Figure B-34) under Host type (operating system), click Windows 2000/Server 2003 Non-Clustered.



ISR654607-00 D B-37

Figure B-34. 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. Complete the Define Additional Mapping dialog box as follows (see Figure B-35):

a. In the Host group or host box, click DM-Host.

b. In the Logical unit number (LUN) (0 to 255) box, click the previously planned LUN number.

c. Under Logical Drive, click the appropriate logical drive.

d. To accept and save the LUN assignment, click Add.


Assigning LUNs from an IBM V7000 Array

B-38 ISR654607-00 D

Figure B-35. Defining Additional Mapping



Storage Vendor IBM®

Array Model IBM Storwize® V7000 disk system

LUN Assignment Tool IBM Storwize V7000 management utility



ISR654607-00 D B-39

To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_IBMV7000.



2. In a Web browser, open the IBM Storwize V7000 management tool by entering the IP address of the array controller.

3. In the left pane, select Hosts, and then Ports by Host.

4. In the right pane, complete the Add a Host information as follows:

a. Click the New Host button, and then under Choose the Host Type, click the Fibre-Channel Host icon, as shown in Figure B-36.

Figure B-36. Creating the Fibre Channel Host

b. (Optional) Type the host name in the Host Name box.

c. Select the WWPN from the Fibre-Channel Ports list, and then click the Add Port to List button.

d. Create one host for each virtual port group (VPG), and then assign a host name to each VPG.



B-40 ISR654607-00 D

5. Complete the Create Host dialog box as follows (see Figure B-37):

a. (Optional) In the Host Name (optional) box, type a user-defined name for the new host.

b. Under Fibre-Channel Ports, select the WWPN associated with the host, and then click the Add Port to List button.

c. Under Advanced Settings, click Generic (default) as the Host Type.

d. Click the Create Host button.

Figure B-37. Creating a Host

The newly created host is now listed with the registered WWPNs under Host Filter, as shown in Figure B-38.

NOTE:

If the zoned data migration appliance port is not visible as the default, manually enter the WWPN. Create a separate initiator group for each VPG. If more than one VPG is enabled and used, create a separate initiator group for each.



ISR654607-00 D B-41

Figure B-38. Viewing the New Host

6. Present volumes to the router as follows:

a. In the left pane, select Volumes, point to All Volumes, and then click the volume to be presented.

b. In the Volumes by Pool window under Status, click Map to Host.

c. On the small Modify Mappings dialog box, select the host from the list, and then click Next.

The large Modify Mappings dialog box’s right pane shows the volume with the SCSI ID, name, and the user identifier (UID).

d. In the right pane, change the SCSI ID of the volume by right-clicking the newly added volume, and clicking Edit SCSI ID.

e. To complete the presentation wizard, click OK.

7. To confirm the mappings to the host:

a. In the left pane, point to Volumes, and then click Volume by Hosts.

b. Under Host Filter, select the host.

c. Ensure that all volumes are shown with the status Online, as shown in Figure B-39.


Assigning LUNs from a NetApp FAS2040 System Using FilerView

B-42 ISR654607-00 D

Figure B-39. Confirming Mappings


To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_Netapp.



2. In a Web browser, open the NetApp FilerView tool by entering the IP address of the array controller.

Storage Vendor NetApp®

Array Model FAS2040 system

LUN Assignment Tool FilerView® CLI-based management tool



ISR654607-00 D B-43

3. Create an initiator group as follows:

a. In the left pane under LUNs, select Initiator Groups, and then click Add.

b. Complete the Add Initiator Group area in the right pane (see Figure B-40).

Figure B-40. Adding Initiator Group

c. In the Group Name box, type DM_host.

d. For host Type, select FCP.

e. For Operating System, select Microsoft Windows.

f. In the Initiators box, select the WWPN of the data migration appliance Fibre Channel port.

g. At the bottom of the right pane, click Add.

NOTE:

If the zoned data migration appliance port is not visible in the Initiators box, manually type the WWPN. Remove all other WWPNs (if any) that do not belong to the data migration appliance. If more than one VPG is enabled and used, create a separate initiator group for each virtual port group.



B-44 ISR654607-00 D

4. Present the LUN as follows:

a. In the left pane under LUNs, click Manage to open the Manage LUNs area in the right pane (see Figure B-41).

Figure B-41. Managing LUNs

b. In the Maps Group : LUN ID column, click the LUN to be presented to the DM_host.

c. In the LUN Map pane (see Figure B-42), click Add Groups to Map.

Figure B-42. Mapping LUNs

d. Under Initiator Group, select the DM_host initiator.

e. Under LUN ID, type the ID at which this LUN is presented to the DM_host.


Assigning LUNs from a NetApp FAS2040 System Using NetApp System Manager

ISR654607-00 D B-45

f. To save this mapping, click Apply.

5. Verify the updated assignment as follows:

a. In the left pane under LUNs, click Manage to open the Manage LUNs area in the right pane.

b. In the Maps Group : LUN ID column, confirm the new DM_host assignment (see Figure B-43).

Figure B-43. Verifying LUN Mapping


To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_Netapp.



Storage Vendor NetApp®

Array Model FAS2040 system

LUN Assignment Tool NetApp System Manager



B-46 ISR654607-00 D

2. Start NetApp System Manager.

3. In the left pane, expand the tree, and then under the Storage node, click LUNs.

4. In the right pane, click the Initiator Groups tab, and then under Initiator Groups, click the Add button.

5. Complete the Add Initiator Group dialog box (see Figure B-44) as follows:

a. In the Group Name box, type a user-defined name (this example uses DM-Appliance).

b. For Group Type, select FCP.

c. For Operating System, select Windows.

d. Select the ALUA (Asymmetric Logical Unit Access) features enabled check box.

e. Click Add.

Figure B-44. Adding an Initiator Group

6. On the Initiator Groups page under Initiator IDs, click the Add button.

7. Complete the Add Initiator ID dialog box (see Figure B-45) as follows:

a. For Group Type, select FCP.

b. For Group Name, select the user-defined name that you specified in Step 5 (DM-Appliance, for example).

c. In the Initiator Name box, type the WWPN of the appliance.

d. Click Add.



ISR654607-00 D B-47

Figure B-45. Adding an Initiator ID

8. Repeat Step 7 to add the WWPN of each virtual port.

9. Present the LUN as follows:

a. In the left pane, expand the tree, and then under the Storage node, click LUNs.

b. In the right pane, click the LUN Management tab.

c. On the LUN Management page, right-click the volume that you want to present to the data migration appliance, and then click Properties.

d. Complete the LUN ‘Volume xx’ Properties page (see Figure B-46) as follows.

1. Click the Initiators tab.

2. Under Known initiator hosts, select the initiator group name that you specified in Step 5.

3. Click the right-arrow button to move the selected initiator group to the Hosts to connect box on the right.

4. Click Apply.

NOTE:

If more than one virtual port is enabled and used, create an initiator group for each virtual port group.


Assigning LUNs from a Xiotech Emprise 5000 Array

B-48 ISR654607-00 D

Figure B-46. Selecting Hosts to Connect


To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_Emprise5000.



2. In a Web browser, open the Emprise 5000 Management tool by entering the array management IP address.

Storage Vendor Xiotech® Corporation

Array Model Emprise 5000 arrays

LUN Assignment Tool Emprise 5000 Management



ISR654607-00 D B-49

3. Click Login, and then type the login user name and password.

4. On the At-A-Glance Status Summary window, click Hosts, and then select create host.

5. Complete the Host Configuration window (see Figure B-47) as follows:

a. In the Name box, type a user-defined host name.

b. Under Operating System Type, select Windows.

c. Under Available HBA Ports, select the WWPN, and then click Add to move the port number to the Selected HBA Ports column.

d. Under Available Volumes, select the volume, and then click Add to move the volume to the Selected HBA Ports column.

e. To create the host, click Submit.

Figure B-47. Configuring a Host


Assigning LUNs from a Xiotech Magnitude 3D 4000 Array

B-50 ISR654607-00 D

The Host Summary Page now lists the newly created host in the Host Information table.


To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_XiotechMagnitude3D_4000.



2. Launch ICON Manager and log in by typing data in the Hostname (IP address), Username, and Password boxes.

3. In the left pane, expand the Console Root tree, select a DSC, and then click Server View.

4. In the Actions pane on the right, click Add Server.

5. Complete the Add Server Initiator wizard (see Figure B-48) as follows:

a. On the Welcome window, click Other Server, and then click Continue.

b. On the Select Initiator window, click FC, and then click Next.

c. On the Map Host Initiators to Servers window, select the host initiator by WWN, and then under Server Name, type a user-defined name. Then click Next.

Storage Vendor Xiotech Corporation

Array Model Magnitude® 3D 4000 arrays

LUN Assignment Tool ICON Manager 3.3

NOTE:

The Magnitude 3D 4000 array requires that the ICON Manager 3.3 tool is installed on the host.



ISR654607-00 D B-51

Figure B-48. Mapping Host Initiators to Servers

d. When the Mapping Servers… window informs you that server mapping is complete, click Next to continue.

e. On the Configure Another Server Initiator? window, click Yes to configure a second server initiator, or No to stop configuring servers. Then click Next to continue.

f. On the wizard’s Done window, click Finish.

6. On the Group Servers dialog box, click Close.

7. In the ICON Manager left pane, click Server View.

8. In the middle pane, ensure that the Server View lists the newly created volume.

9. Assign the volume to the initiator as follows:

a. In the Server View pane, select the newly created volume.

b. In the Action pane (right pane), click Assign Virtual Disk.

c. On the Assign Virtual Disk: <volume_name> dialog box, click Browse.

d. On the Select A Host Initiator dialog box, select the initiator, and then click Select.

e. On the Assign Virtual Disk: <volume_name> dialog box, click OK, and then on the confirmation window, click OK again.


Assigning LUNs from an ETERNUS DX440 Array

B-52 ISR654607-00 D

f. In the left pane, click Storage View, and then ensure that the LUN is assigned to the initiator. Figure B-49 shows an example.

Figure B-49. Confirming LUN Assignment


To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_DX440.



Storage Vendor Fujitsu®

Array Model ETERNUS® DX440 S2 arrays

LUN Assignment Tool ETERNUS SF Storage Cruiser



ISR654607-00 D B-53

2. In a Web browser, open the ETERNUS SF utility by entering the IP address of the array controller.

3. In the left pane, click Host Interface Management, and then click Set Host Response.

4. In the right pane, click Add Host Response, and then complete the host response information as follows (see Figure B-50):

a. In the host response Name box, type a user-defined name.

b. For the Inquiry Standard Data Version, click Version 3.

c. Accept the default values for all of the remaining parameters.

d. Click OK to return to the previous window.

e. Click Set, and then click Confirm to create the host response.

Figure B-50. Creating a Host Response

5. Create a host as follows (see Figure B-51):

a. In the left pane, click a port group.

b. In the right pane, click Create FC Port Group.

NOTE:

A port group determines the front end ports—ports that provide access to the data migration appliance—to be used for a common host configuration.



B-54 ISR654607-00 D

c. Select the controller adapter and port to which the data migration appliance is connected.

d. Under CA Port Group Setting, type a user-specified name, and then click Create to create the host group.

Figure B-51. Creating a Controller Adapter Port Group

6. Create a host group as follows (see Figure B-52):

a. In the left pane, click Host Group.

b. In the right pane, click the FC/FCoE Host.

c. In the New Group Name box, type a name for the data migration appliance.

d. Select all WWNs that belong to this data migration appliance’s VPG.

e. To detect the connected ports, click Rediscover.



ISR654607-00 D B-55

f. Select the host response for the host created in Step 5.

g. To confirm, click Add.

Figure B-52. Creating a Host Group

7. Create a host affinity group as follows (see Step B-53):

a. On the left side, click Connectivity.

b. In the right pane, click Create Host Affinity.

c. In the next window, select the previously-created Host Group, CA Port Group, and LUN Group.

NOTE:

If the zoned data migration appliance port is not visible by default, manually enter the WWPN on the Manual Input page. If more than one VPG is enabled and used, create an individual host group for each VPG.

NOTE:

This procedure assumes that a LUN group has already been created. A LUN group contains all of the LUNs and the LUN to Host LUN definition to be used for a specific host.



B-56 ISR654607-00 D

Figure B-53. Creating a Host Affinity Group


To assign LUNs:



b. Using switch management tools, create a zone, DM_Host_DX8400.



2. In a Web browser, open the ETERNUS SF utility by entering the IP address of the array controller.

3. In the left pane, click Host Interface Management, and then click Set Host Response.

4. In the right pane, click Add Host Response, and then complete the host response information as follows (see Figure B-54):

a. In Host Response Name box, type a user-defined name.

b. For the Inquiry Standard Data Version, click Version 03.

Storage Vendor Fujitsu

Array Model ETERNUS DX8400 arrays

LUN Assignment Tool ETERNUS SF Storage Cruiser



ISR654607-00 D B-57

c. Accept the default values for all of the remaining parameters.

d. Click OK to return to the previous window.

e. Click Set, and then click Confirm to create the host response.

Figure B-54. Creating a Host Response

5. Create a host as follows (see Figure B-55):

a. In the left pane, click Host Interface Management, and then click Set Host WorldWideName(s).

b. In the right pane under Add WNN, create a host by typing the host Name and selecting the WWN.

c. Select the controller adapter (CA) and port to which the data migration appliance is connected.

d. To refresh the visible WWNs and select the correct entry, click Collect.

e. Select the WWPN of the data migration appliance’s Fibre Channel ports. If the zoned appliance port is not visible by default, type the WWPN in the WWN box.

f. Select the Host Response created in Step 4.

g. To apply the changes, click Add.



B-58 ISR654607-00 D

Figure B-55. Setting the Host WWN

6. Create a host affinity group as follows:

a. In the left pane, click Host Interface Management, and then click Allocate Host-Infinity Group.

b. In the right pane under Select a CA, click the port on which the data migration appliance WWPN is available (for which host was created in Step 5), and then click Set (see Figure B-56.)

NOTE:

Create a separate host for each WWPN of the data migration appliance, and then register each Fibre Channel port of the appliance as a separate host on the array.



ISR654607-00 D B-59

Figure B-56. Allocating a Host Affinity Group

c. In the right pane, select a WWPN visible on the selected registered host WWN and the Affinity Group to be accessed by the host, and then click Add (see Figure B-57).

Figure B-57. Mapping LUNs

d. After all needed host WWNs are added, click Set to confirm the additions and map all LUNs in the affinity group to the data migration.



B-60 ISR654607-00 D

NOTE:

This procedure assumes that the affinity group has already been created for the LUNs directly presented to the host. The same affinity group also presents these LUNs to the data migration appliance.

ISR654607-00 D Index-1

Index

Numerics3PAR array, assigning LUNs from B-8

Aaccess, LUN to server 1-3active optimized paths, load balancing with

3-1agreements, license ixapplications

downtime, minimizing 3-1server, listing 2-3

arraysassigning LUNs for data migration B-1listing storage 2-2management tools, assigning LUNs B-1multipathing software for 2-2

assigning LUNs for data migration B-1from EMC CLARiiON array B-25from EMC Symmetrix DMX-4 array B-31from ETERNUS DX440 array B-52from ETERNUS DX8400 array B-56from EVA 4/6/8000 series array B-16from HDS array B-20from HP 3PAR array B-8from IBM DS4K array B-34from IBM DS5KL array B-34from IBM LSI array B-34from MSA2012fc array B-2from NetApp FAS2040 system B-42, B-45from Xiotech Emprise 5000 array B-48from Xiotech Magnitude 3D 4000 array B-50

audience vii

Bbefore you begin 1-1

Cchecklists

examples of A-1inventory 2-1

confirming access to data 3-3contacting QLogic xcontrollers, balancing LUNs across 3-1conventions viiicreating

Fibre Channel zoning 2-4LUN ID mappings 2-3

Ddata migration

checklists, examples of A-1checklists, inventory 2-1general steps for 1-3LUNs, assigning B-1performance, improving 3-1planning 2-1

data, validating integrity of 3-3definitions of terms 1-1dependencies, operating systems 4-1destination arrays

listing 2-2multipathing software for 2-2

destination LUNs, assigning B-1


Planning Guide

Index-2 ISR654607-00 D

downtime, minimizing 3-1dual blade configuration, minimizing downtime

with 3-1

EEMC CLARiiON array, assigning LUNs from

B-25EMC Symmetrix DMX-4 array, assigning

LUNs from B-31Emprise 5000 array, assigning LUNs from

B-48end user license agreement ixETERNUS DX440 array, assigning LUNs from

B-52ETERNUS DX8400 array, assigning LUNs

from B-56EULA ixEVA 4/6/8000 series array, assigning LUNs

from B-16examples of completed checklists A-1

Ffabric zones, listing 2-4FAS2040 system, assigning LUNs from B-42,

B-45Fibre Channel switches, listing 2-4Fibre Channel zoning, listing 2-4file system check, validating data 3-3Fujitsu ETERNUS DX440 array, assigning

LUNs from B-52Fujitsu ETERNUS DX8400 array, assigning

LUNs from B-56

Ggetting started 1-1

HHDS array, assigning LUNs from B-20HP 3PAR array, assigning LUNs from B-8

IIBM DS4K array, assigning LUNs from B-34IBM DS5K array, assigning LUNs from B-34IBM LSI array, assigning LUNs from B-34inventory checklists 2-1

Kknowledge database, QLogic x

Llicense agreements ixlisting

destination storage array 2-2Fibre Channel zoning 2-4items affected by data migration 2-1LUN ID mappings 2-3physical device info for server 2-3source storage array 2-2

load balancing for optimal performance 3-1logical volume managers

listing for server 2-2OS dependencies 4-2

logs, migration, saving 1-4LUN IDs

mappings, listing 2-3server, listing for 2-3

LUNsaccess to server 1-3assigning for data migration B-1controllers, balancing across 3-1size recommendations 4-2

ISR654607-00 D Index-3


Planning Guide

MMagnitude 3D 4000 array, assigning LUNs

from B-50mappings

assigning using storage array management tools B-1

LUN ID, listing and creating 2-3migration logs, saving 1-4minimizing downtime 3-1mount points

creating 1-2server, listing 2-3

MSA2012fc array, assigning LUNs from B-2multipathing software

LUNs, managing paths to 1-3OS dependencies 4-1

NNetApp FAS2040 system, assigning LUNs

from B-42, B-45

Ooffline data migration, minimizing downtime

with 3-1operating systems

dependencies with 4-1server, listing 2-2

optimizing performance during data migration 3-1

Oracle Cluster File System, OS dependencies 4-2

Pperformance (data migration), improving 3-1physical devices, listing 2-3physical disks (server), listing 2-3planning data migration 2-1post-migration Fibre Channel zoning 2-4pre-migration Fibre Channel zoning 2-4

Rraw device node (server), listing 2-3related materials viirelationship between data and storage 1-2

Ssaving data migration logs 1-4servers

impacted by data migration, listing 2-2LUN access to 1-3physical device information, listing 2-3

software EULA ixsource arrays

listing 2-2multipathing software for 2-2

source LUNs, assigning B-1storage arrays, See arrays

Ttechnical support ixterminology 1-1training at QLogic x

UUNIX OS dependencies 4-2

Vvalidating data integrity 3-3volume (server), listing 2-3

WWindows OS, dependencies with 4-1WWPNs

listing for FC array 2-2listing for zone members 2-4


Planning Guide

Index-4 ISR654607-00 D

XXiotech Emprise 5000 array, assigning LUNs

from B-48Xiotech Magnitude 3D 4000 array, assigning

LUNs from B-50

Zzone members, WWPNs for 2-4zoning, Fibre Channel, listing and creating 2-4

Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 www.qlogic.com

International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan

© 2010, 2011 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic, the QLogic logo, and SANsurfer are registered trademarks of QLogic Corporation. Adobe Reader is a registered trademark of Adobe Systems Incorporated. Apache is a trademark of The Apache Software Foundation. AIX is a registered trademark of International Business Machines Corporation. EMC, CLARiiON, PowerPath, and Symmetrix are registered trademarks of EMC Corporation. Fujitsu and ETERNUS are registered trademarks of Fujitsu Limited. HP is a registered trademark of Hewlett-Packard Company. Linux is a registered trademark of Linus Torvalds. Microsoft, Windows, and Excel are registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation. Solaris is a registered trademark of Sun Microsystems, Inc. UNIX is a registered trademark of The Open Group. Veritas is a trademark of Symantec Corporation. Xiotech and Magnitude are registered trademarks of Xiotech Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. Information supplied by QLogic Corporation is believed to be accurate and reliable. QLogic Corporation assumes no responsibility for any errors in this brochure. QLogic Corporation reserves the right, without notice, to make changes in product design or specifications.

www.qlogic.com

data migration service for isr6200 planning...

Documents