EMC SAN Copy Command Line Interfaces

Transcription

1 EMC SAN Copy Command Line Interfaces REFERENCE P/N REV A13 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published July, 2008 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC SAN Copy Command Line Interfaces Reference

3 Contents Preface... 5 Chapter 1 Chapter 2 Introducing SAN Copy and Its Command Line Utilities Introducing SAN Copy software SAN Copy features and benefits Storage-system-based data-mover application Easy-to-use web-based application Use with replication software Simultaneous sessions between multiple storage systems.. 15 Incremental SAN Copy sessions Integration with EMC SnapView software Integration with EMC MirrorView software SAN Copy software components SAN Copy operations overview SAN Copy Configuration Guidelines SAN Copy configuration requirements Copying data between CLARiiON storage systems or CLARiiON and Symmetrix storage systems...22 Copying data between LUNs within a CLARiiON storage system Sample SAN Copy configuration...26 Fibre Channel zoning requirements and recommendations Zoning recommendations Single-initiator zoning examples without and with SAN Copy installed iscsi zoning requirements and recommendations Preparing a CLARiiON storage system for a copy session Connecting SAN Copy ports to CLARiiON storage groups

4 Contents Preparing a Symmetrix storage system for a copy session Preparing a Symmetrix storage system using EMC ControlCenter SAN Manager Preparing a Symmetrix storage system using ESN Manager Chapter 3 Chapter 4 Appendix A Using the Admhost Utility with SAN Copy About the admhost utility for SAN Copy Admhost SAN Copy command functions Preparing logical units for a SAN Copy session Preparing source and destination logical units for full and incremental sessions SAN Copy CLI Commands SAN Copy command functions About Secure CLI naviseccli About Classic CLI navicli sancopy -create sancopy -destinfo sancopy -duplicate sancopy -info sancopy -mark sancopy -modify sancopy -pause sancopy -remove sancopy -resume sancopy -settings sancopy -start sancopy -stop sancopy -throttle sancopy -transfer sancopy -unmark sancopy -updateconnections sancopy -verify SAN Copy CLI Error Codes SAN Copy CLI error codes Index EMC SAN Copy Command Line Interfaces Reference

5 Preface As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time releases revisions of its hardware and software. Therefore, some functions described in this guide may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this guide, please contact your EMC representative About this manual Note: This manual does not include any content that is specific to FC series or C series storage systems. For this information, refer to the EMC SAN Copy Command Line Interfaces Reference, Rev. A07. This manual describes the two command line interfaces to EMC SAN Copy software: the Admhost Utility and the Command Line Interface (CLI). You should read this manual if you will use typed or scripted commands (instead of or in addition to EMC Navisphere Manager software) to configure and run the SAN Copy software. This manual assumes that you are familiar with the operating system running on the servers you will manage and with storage-system components and configurations. Audience This guide is part of the EMC SAN Copy (referred to as SAN Copy later in this document) documentation set, and is intended for use by customers and service providers who use EMC Navisphere CLI to set up and manage SAN Copy software. 5

6 Preface This manual assumes that you are familiar with the operating system running on the servers you will manage and with storage-system components and configurations. Organization This manual contains four chapters and one appendix as follows: Chapter 1 Chapter 2 Chapter 3 Chapter 4 Appendix A Introduces terminology and the software products. Explains the basic requirements, restrictions and configuration guidelines for using SAN Copy. Explains admhost commands that the operating system uses to manage devices with SAN Copy. Describes the CLI commands that SAN Copy uses to manage SAN Copy sessions. Lists and describes the SAN Copy CLI error codes. Related documentation Related documents include: The most up-to-date version of the online help, available on the EMC Powerlink website ( in the Navisphere Management Suite section of the Technical Documentation and Advisories section. EMC CX4 Series, CX3 Series and CX Series SAN Copy Release Notes EMC Admhost Release Notes 6 EMC SAN Copy Command Line Interfaces Reference

7 Preface Conventions used in this guide This manual uses the following format conventions: This typeface This typeface This typeface x > y Indicates text (including punctuation) that you type verbatim, all commands, pathnames, filenames, and directory names. It indicates the name of a dialog box, field in a dialog box, menu, menu option, or button. Represents variables for which you supply the values; for example, the name of a directory or file, your username or password, and explicit arguments to commands. Represents a system response (such as a message or prompt), a file or program listing. Represents a menu path. For example, Operations > Poll All Storage Systems tells you to select Poll All Storage Systems on the Operations menu. [ ] Encloses optional entries. Separates alternative parameter values; for example: LUN-name LUN-number means you can use either the LUN-name or the LUN-number. Finding current information The most up-to-date information about the EMC SAN Copy software is posted on the EMC Powerlink website. We recommend that you download the latest information before you start the SAN Copy software. If you purchased this product from an EMC reseller and you cannot access Powerlink, the latest product information should be available from your reseller. To access EMC Powerlink, use the following link: After you log in, select Support > Technical Documentation and Advisories and find the following: EMC Admhost Release Notes EMC SAN Copy Release Notes The latest version of this guide that is applicable to your software revision 7

8 Preface Installation Roadmap for CLARiiON Storage Systems, which provides a checklist of the tasks that you must complete to install your storage system in a storage area network (SAN) or direct attach configuration. Where to get help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: Technical support For technical support, go to EMC WebSupport on Powerlink. To open a case on EMC WebSupport, you must be a WebSupport customer. Information about your site configuration and the circumstances under which the problem occurred is required. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a message to techpub_comments@emc.com with your opinions of this guide. 8 EMC SAN Copy Command Line Interfaces Reference

9 Invisible Body Tag 1 Introducing SAN Copy and Its Command Line Utilities This chapter introduces the EMC SAN Copy software and its command line utilities: admhost, with commands that the operating system uses to manage SAN Copy devices; and the CLI, with commands that manage SAN Copy sessions. Major topics are: Terminology Introducing SAN Copy software SAN Copy features and benefits SAN Copy software components SAN Copy operations overview

10 Introducing SAN Copy and Its Command Line Utilities Terminology Term admhost utility auto recovery AX4-5 series storage system buffer space checkpoint interval CLI clone connection set connection type copy-on-first-write Meaning An executable program that includes commands that the operating system uses to manage SAN Copy devices. The state of a copy session that is trying to resume failed sessions. AX4-5 (AX4-5F), AX4-5i (AX4-5I), AX4-5SC (AX4-5FSC), AX4-5SCI (AX4-5ISC) Memory used for temporary data storage. A user-defined time interval that lets an interrupted copy session resume from the last checkpoint, rather than having to start the session over. EMC Navisphere Command Line Interface. A copy (local mirror) of a LUN. When synchronized, it remains a bit-for-bit copy of its source LUN. To access the clone, you must fracture it. Then, after performing the desired operations (such as data modeling or backup), you can start synchronizing it again. Clone functionality is provided with EMC SnapView software. A named set of information used by a CLARiiON iscsi initiator to establish a replication session with an iscsi target. A connection set consists of a unique user-defined name, credentials usage (connection specific, array-shared or none), one or more connection paths, and when specified, an optional username and password (secret). The network protocol for transferring data from one storage system to another. The available choices depend on the storage systems participating in the copy session. The choices may be fibre or iscsi. An algorithm that copies current contents of a source LUN to the reserved LUN pool before it is modified (written to). CX series storage system CX700, CX600, CX500, CX500i, CX400, CX300, CX200, and CX200LC CX3 series storage system CX3 model 80 system, CX3 model 40 systems, CX3 model 20 systems, and CX3 model 10 systems. CX4 series storage system3 destination logical unit domain CX4-960, CX-480, CX4-240, CX-120 storage systems. A logical unit to which SAN Copy is copying the source data. On a CLARiiON storage system, this device is called a LUN; on a Symmetrix system, it is called a volume (can be a single LUN or a metalun). In the context of Navisphere 6.X, a group of storage systems and/or portal servers that you can manage from a single management application session. You can divide the storage systems into multiple domains as long as each storage system or portal is in only one domain. 10 EMC SAN Copy Command Line Interfaces Reference

11 Introducing SAN Copy and Its Command Line Utilities Term Event Monitor fibre preferred full SAN Copy session host agent incremental SAN Copy session latency link bandwidth logical unit (LU) LUN managed agent managed storage system Manager metalun pre-cx series systems remote storage system reserved LUN pool Meaning EMC Navisphere Event Monitor. Sets the session connection type to fibre or iscsi (if fibre path could not be found) each time you start or resume a session that failed or was stopped. A full copy session copies all the data on the source logical unit to one or many destination logical units. EMC Navisphere agent that runs on a storage-system server. An incremental copy session copies only the data that has changed since the last copy session. The amount of time it takes to transmit a block of data to its destination expressed in milliseconds. By default, latency is set to AUTO (the software computes the latency value). The bandwidth of the network connection used to transfer copy data. A storage device that resides on a storage system, stores data and is independent of storage-system type. For example, on a CLARiiON CX series storage system, this device is called a LUN; on a CLARiiON AX-series storage system, a virtual disk; on a Symmetrix system, a volume. A logical unit can be a single LUN or a metalun. CLARiiON term for logical unit. A host agent or SP agent managed by Navisphere management software. A storage system managed by Navisphere management software. EMC Navisphere Manager. A type of LUN whose capacity is the combined capacities of all the LUNs that comprise it. An FC4700, FC4500, FC5300, FC5500, FC5700, or C series storage system. A storage system with logical units that are participating in a copy session, but that does not own the copy session. A remote storage system does not need to be running SAN Copy software. This storage system could be a CLARiiON, Symmetrix, or supported non-clariion storage system. The reserved LUN pool works with SAN Copy to perform incremental copy operations. It consists of one or more private LUNs. The reserved LUN pool is shared by both storage-system SPs, and before starting an incremental SAN Copy session, the pool must contain at least one LUN for each source LUN that will be participating in an incremental session. For more information, see the Navisphere Manager online help. 11

12 Introducing SAN Copy and Its Command Line Utilities Term reserved session SAN SAN Copy SAN Copy port SAN Copy session SAN Copy storage system snapshot source logical unit SP agent storage management server software throttle value virtual disk volume zone Meaning A private session created by SAN Copy when you start an incremental copy session. The name assigned to the reserved session consists of the copy session name with the prefix SANCopy. No user actions can be performed on a reserved session. Storage area network: One or more servers connected to one or more storage systems with Fibre Channel switches. Switch zoning and EMC Access Logix software control server access to storage systems and LUNs. Software running on a SAN Copy storage system that lets you copy logical unit information between SAN Copy storage systems and other CLARiiON storage systems, or within a storage system. An SP port initiator on a SAN Copy storage system that is participating in a SAN Copy session. A descriptor that stores all data pertaining to a unique copy process, such as session name, session ID, source and destination logical units, and session status. You must start the session to begin the copy process. The CLARiiON storage system that owns the SAN Copy session. A SAN Copy storage system must be running SAN Copy software. You cannot install SAN Copy on a CX300 or AX series storage system. A point-in-time image of a LUN. A snapshot occupies no disk space, but appears as a normal LUN to secondary hosts. Snapshot functionality is provided with EMC SnapView software. A logical unit from which SAN Copy copies data. On a CLARiiON storage system, this device is called a LUN (can be a single LUN or a metalun). EMC Navisphere Agent that runs on the SPs in supported storage systems. Software that runs in a storage system or off-array management server and lets a person manage it over a network. A parameter that controls the I/O rate for a copy session. You can set the session throttle to a value between 1 and 10 where 1 is the lowest rate and 10 is the highest. The default throttle value is 6. A logical unit on an AX-series storage system. A logical unit on a Symmetrix storage system. A way to limit access to specific logical units in a storage system, thereby increasing security and decreasing network traffic. 12 EMC SAN Copy Command Line Interfaces Reference

13 Introducing SAN Copy and Its Command Line Utilities Introducing SAN Copy software EMC SAN Copy software (referred to as SAN Copy later in this document) runs on a SAN Copy storage system (storage system with SAN Copy software enabled). It copies data between CLARiiON storage systems, within CLARiiON storage systems, between CLARiiON and Symmetrix storage systems, and between CLARiiON and qualified non-emc storage systems. SAN Copy can copy data directly from a source logical unit on one storage system to destination logical units on other systems, without using host resources. SAN Copy connects directly or through a SAN, and also supports protocols that let you use the IP WAN (wide area network) to send data over extended distances. SAN Copy can perform multiple copies each in its own copy session simultaneously. The RAID type of the logical units participating in a copy session does not have to be the same; that is, the source and destination logical units can be different RAID types. You can use SAN Copy to create full and incremental copies of a source logical unit. An incremental session copies only the data that has changed since the last copy session. This can significantly reduce the time needed to copy the data, thereby allowing the copy operation to be performed more frequently and more effectively. Unlike full copy sessions, the source logical unit for an incremental session can remain online during the copy process. You must, however, prepare the source logical unit prior to starting the session (see Preparing logical units for a SAN Copy session on page 51). Regardless of the type of copy session full or incremental the participating logical units must meet certain requirements. You can use SAN Copy for the following tasks: One-time data migration Routine copying of data for application testing Content distribution Scheduled updates to multiple databases. To manage SAN Copy sessions, you can use either the UI-based Navisphere Manager (described in the Navisphere Manager online help), or the SAN Copy Command Line Interface described in this manual. 13

14 Introducing SAN Copy and Its Command Line Utilities SAN Copy features and benefits The SAN Copy software adds value to customer systems by offering the following features: A storage-system-based data mover application that uses a storage area network (SAN) rather than host resources to copy data resulting in a faster copy process. An easy-to-use, web-based application for configuring and managing SAN Copy. Software that you can use in conjunction with replication software, allowing I/O with the source logical unit to continue during the copy process. Simultaneous sessions that can copy data to multiple CLARiiON and Symmetrix storage systems. Incremental SAN Copy sessions that copy only the data that has changed since the last update. Integration with EMC SnapView software. Integration with EMC MirrorView software. Storage-system-based data-mover application SAN Copy is a storage-system-based data-mover application that uses a SAN (storage area network) or LAN (local area network) to copy data between storage systems. Since SAN Copy runs on the storage systems, this eliminates the need to move data to and from the attached hosts and reserves host processing resources for users and applications. Since the host is not involved in the copy process, and the data migration takes place on the SAN, the copy process is much faster than the LAN-based, host-involved copy process. Easy-to-use web-based application SAN Copy is an integrated part of Navisphere Manager, the easy-to-use, web-based management tool for CLARiiON storage systems. Manager lets you select the SAN Copy source and destination logical units, create SAN Copy sessions and then manage these sessions. 14 EMC SAN Copy Command Line Interfaces Reference

15 Introducing SAN Copy and Its Command Line Utilities Use with replication software If the storage system containing the source logical unit has device replication technology, such as EMC SnapView or EMC TimeFinder software, SAN Copy can use a snapshot (full copy sessions only), clone, or Symmetrix BCV (business continuation volume) as its source logical unit allowing I/O with the source logical units for the snapshot, clone, or BCV to continue during the copy process. Note: You must fracture a SnapView clone before using it as a source LUN in a SAN Copy session. For more details, refer to the SnapView documentation and online help. Simultaneous sessions between multiple storage systems SAN Copy lets you have more than one session active at a time. The number of supported concurrent active sessions and the number of logical units per session depends on the storage-system type. Note: If the destination logical unit is a metalun, the metalun is considered a single entity. Therefore, the metalun counts as one of the maximum destination logical units. For example, if a metalun consists of five LUNs, it counts only as one destination logical unit, not five. Storage-system type Maximum number of concurrent sessions per system Maximum number of destination logical units per source Maximum number of incremental source logical units CX4-120, CX (4 per SP) CX4-480, CX (8 per SP) AX4-5 series dual FC 4 (2 per SP) (requires Navispshere Manager) CX3 model 20 systems, CX500, CX400 8 (4 per SP) CX3 model 40 systems 8 (4 per SP) CX3 model 80 system, CX700, CX (8 per SP) CX3 model 10 systems 4 (2 per SP)

16 Introducing SAN Copy and Its Command Line Utilities Incremental SAN Copy sessions The incremental SAN Copy feature lets you copy only the data that has changed since the last copy session. This significantly reduces the time needed to copy the data, thereby allowing the copy operation to be performed more frequently and more effectively. Unlike full copy sessions, the source logical unit can remain online during the copy process. To use the incremental SAN Copy feature: The source logical unit must reside in a SAN Copy storage system. (This storage system cannot be a CX300 storage system or an AX-series storage system running Navisphere Express). The source logical unit cannot be a SnapView snapshot. You must configure the reserved LUN pool (refer to the EMC Navisphere Manager online help). Integration with EMC SnapView software SnapView can be used with SAN Copy to create a snapshot or a clone of the destination LUN, so that the SnapView replica can be put in the secondary server storage group, rather than the SAN Copy destination logical unit. This allows the SAN Copy destination logical unit to maintain consistency with its source, and be available on an ongoing basis for incremental updates. SAN Copy tracks server writes to the SAN Copy source LUN (for example, from the production server); but SAN Copy does not track server writes to the SAN Copy destination LUN (for example, from the secondary server). Integration with EMC MirrorView software SAN Copy software lets you create an intra- or inter-storage-system copy of a LUN at any point in time; however, do this only when the image state is either synchronized or consistent and the mirror is not updating to the secondary image. The copy is a persistent image that can serve for other application purposes while I/O continues to the source LUN. The MirrorView secondary image is not viewable to any hosts, but you can use SAN Copy to create a copy of the secondary image on a secondary storage system to perform data verification and run parallel processes. 16 EMC SAN Copy Command Line Interfaces Reference

17 Introducing SAN Copy and Its Command Line Utilities Related to the process of making the MirrorView secondary image unavailable for host I/O, you cannot run SAN Copy full copy sessions on MirrorView secondary images. You can, however, run SAN Copy incremental sessions on MirrorView secondary images. For more information on MirrorView, refer to the EMC Navisphere Manager online help. 17

18 Introducing SAN Copy and Its Command Line Utilities SAN Copy software components SAN Copy consists of the following software components: SAN Copy software installed and enabled on a SAN Copy storage system. Note: All CX4 series, CX3 series and CX series (excluding the CX300) storage systems ship from the factory with SAN Copy software installed, but not enabled. To use the SAN Copy software functionality, the SAN Copy enabler must be installed on the storage system. The admhost utility provides a command line executable that lets you execute certain commands lun_activate, lun_deactivate lun_flush, and lun_list when managing SAN Copy sessions. The admhost utility ships with other Windows host utilities (for example, the host agent and CLI), and resides on any Windows hosts connected to storage systems that have the SAN Copy software installed and enabled. User interface (UI) - Navisphere Manager, which must be installed on at least one storage system on the same network as the SAN Copy storage system. Navisphere Command Line Interface (CLI), which ships as part of the Navisphere Host Agent packages. 18 EMC SAN Copy Command Line Interfaces Reference

19 Introducing SAN Copy and Its Command Line Utilities SAN Copy operations overview The following steps explain how to use SAN Copy: 1. Set up SAN Copy. This procedure includes the following tasks: Zoning switches see Fibre Channel zoning requirements and recommendations on page 28, or, for iscsi, see the Navipshere Manager online help or the Navisphere Command Line Interface Reference. Registering SAN Copy ports see Preparing a CLARiiON storage system for a copy session on page 37 and Preparing a Symmetrix storage system for a copy session on page 42. Adding logical units to storage groups and connecting ports to storage groups and volumes see Preparing a CLARiiON storage system for a copy session on page 37 and Preparing a Symmetrix storage system for a copy session on page 42. Configuring the reserved LUN pool for incremental SAN Copy sessions see the Navisphere Command Line Interface Reference. 2. On the SAN Copy storage system, create full or incremental SAN Copy copy descriptors using the sancopy -create or sancopy -create -incremental command (see page 69). 3. Prepare the source and destination logical units for a SAN Copy session (see Preparing logical units for a SAN Copy session on page 51). 4. For full sessions, proceed to step 5 to start the session. For incremental sessions, mark any sessions using the sancopy -mark command (see page 88). Note: Once you receive confirmation that the mark operation was successful, you can make the source logical units available to the host and resume I/O to these logical units. This applies only to source logical units participating in incremental copy sessions. 5. On the production host s storage system, start the SAN Copy sessions using the sancopy -start command (see page 106). Note: More than one session at a time per source logical unit can be active on a host, provided the source and destination logical units are unmounted (see step 3 above). 19

20 Introducing SAN Copy and Its Command Line Utilities 6. Let the copy session complete. 7. On both hosts, make the source logical unit (if not done previously) and destination logical units available to the operating system. Note: Some operating systems do not support access by the same host to identical LUNs. Therefore, once SAN Copy completes the copy session, we recommend that you move any identical LUNs to different storage groups. With Windows hosts, issue the admhost lun_activate command. This command rescans the bus for new devices and assigns a drive letter to all CLARiiON and Symmetrix logical units that do not already have one. Use the -l and -d options with the admhost lun_activate command to assign a drive letter to a LUN with a specific world wide name (WWN). What next? Depending on your needs, go to one of the following chapters: For information about the basic requirements, restrictions and configuration guidelines for using SAN Copy -- Chapter 2 To learn about admhost commands Chapter 3 To learn about SAN Copy CLI commands Chapter 4 20 EMC SAN Copy Command Line Interfaces Reference

21 visible Body Tag 2 SAN Copy Configuration Guidelines This chapter lists the basic requirements, restrictions and configuration guidelines for using SAN Copy. Major sections are: SAN Copy configuration requirements Fibre Channel zoning requirements and recommendations iscsi zoning requirements and recommendations Preparing a CLARiiON storage system for a copy session Preparing a Symmetrix storage system for a copy session

22 SAN Copy Configuration Guidelines SAN Copy configuration requirements This section describes the configuration requirements and restrictions for copying data between CLARiiON storage systems, between CLARiiON and Symmetrix storage systems, and within CLARiiON storage systems. Figure 1 shows a sample SAN Copy session that includes these configurations. Copying data between CLARiiON storage systems or CLARiiON and Symmetrix storage systems If you will be copying data between CLARiiON storage systems, or between CLARiiON and Symmetrix storage systems, the requirements in the following sections must be met before you start a SAN Copy session. Note: For full copy sessions, a virtual disk in an AX4-5 or series storage system can be either a source or a destination logical unit. For incremental sessions, it can be only a destination logical unit. 22 EMC SAN Copy Command Line Interfaces Reference

23 SAN Copy Configuration Guidelines Supported SAN Copy configurations for sessions between CLARiiON systems Table 1 describes the currently supported SAN Copy configurations for sessions between CLARiiON storage systems. Source storage Storage system Type Table 1 Supported SAN Copy configurations Destination storage Storage system type Connection type* Session type CX3 series, CX4 series, CX500, CX700, AX4-5 series dual SP (SAN Copy storage systems with Navisphere Manager) CX4 series, CX3 series CX series (with Navisphere Manager) AX4-5 series, AX series (with Navisphere Manager or Navisphere Express) FC Full, Incremental CX4 series, CX3 series (SAN Copy storage systems with Navisphere Manager) CX4 series, CX3 series, CX series (with Navisphere Manager) AX4-5, AX series (With Navisphere Manager or Navisphere Express) iscsi Full, Incremental CX4 series, CX3 series, CX series (with Navisphere Manager) AX4-5 series, AX series (with Navisphere Manager or Navisphere Express) CX4 series, CX3 series CX series, CX500, CX700,, AX4-5 series dual SP (SAN Copy storage with Navisphere Manager) FC Full CX4 series, CX3 series, CX series (with Navisphere Manager) AX4-5 series, AX series (with Navisphere Manager or Navisphere Express) CX4 series, CX3 series (SAN Copy storage systems with Navisphere Manager) iscsi Full * For CX4 series storage systems, the connection type applies only if the front-end ports for the storage systems have that connection type. All copy sessions Both full and incremental copy sessions must meet the following requirements. In addition, incremental sessions must meet the requirements described in Incremental copy sessions on page 25. One of the CLARiiON storage systems participating in the copy session must be a SAN Copy storage system. 23

24 SAN Copy Configuration Guidelines You must enable the VCM bit on all Symmetrix storage ports participating in the SAN Copy session. For Fibre Channel replication, you must correctly zone SAN Copy initiator ports to remote storage systems so that SAN Copy can have access to these systems (see Fibre Channel zoning requirements and recommendations on page 28). For iscsi replication, you must create connection sets. A connection set is a named set of information used by a CLARiiON iscsi initiator to establish a replication session with an iscsi target. A connection set consists of a unique user-defined name, method for assigning security credentials (connection specific, array-shared or none), one or more connection paths, and when specified, an optional username and password (secret). Note: SAN Copy ports act as host initiators to the remote storage systems. You can add them to storage groups and they must belong to the same zone or connection set as the logical units participating in the copy session. Either the source logical unit, destination logical units or both must reside in a SAN Copy storage system. Note: If the source logical unit resides in the SAN Copy storage system, you can copy data to one or many destination logical units on one or many storage systems. None of the remote storage systems require the SAN Copy software. If the source logical unit does not reside in the SAN Copy storage system, all destination logical units must reside in the storage system that owns the SAN Copy session. When copying data to a Symmetrix system, use the navicli -lunmapinfo command to obtain the World Wide Name (WWN) of any Symmetrix volumes that you want to include in the SAN Copy session. These volumes must be mounted and the Navisphere Host Agent must be installed on the hosts that own the volumes. For the required host agent version, refer to the SAN Copy release notes, available on Powerlink (see Finding current information in the Preface). 24 EMC SAN Copy Command Line Interfaces Reference

25 SAN Copy Configuration Guidelines In order for the logical units to participate in a SAN Copy session, you must make the logical units accessible to the participating SAN Copy storage-system port. For example, when copying between CLARiiON storage systems, you must add the SAN Copy initiator port to the storage group on the remote storage system that includes the participating destination logical units. Note: For AX4-5 and AX series storage systems with Navisphere Express, refer to the Navisphere Express online help for instructions on making virtual disks accessible to the SAN Copy port. For Symmetrix storage systems, refer to your Symmetrix documentation for instructions on making volumes accessible to the SAN Copy port. Incremental copy sessions Incremental copy sessions must meet all the requirements for full sessions with the following exceptions and additions: Exception The source logical unit cannot reside in a remote storage system. It must reside in the SAN Copy storage system. The source logical unit cannot be a SnapView snapshot. Additions You must configure the reserved LUN pool before you start an incremental SAN Copy session. The reserved LUN pool works with SAN Copy to perform incremental SAN Copy operations. It consists of one or more private LUNs. Before starting an incremental SAN Copy session, the pool must contain at least one LUN for each source LUN that will be participating in an incremental session. For more information, see the Navisphere Manager online help, packaged with the software and available from Powerlink. What next? See Fibre Channel zoning requirements and recommendations on page 28, or iscsi zoning requirements and recommendations on page 36. See Preparing a CLARiiON storage system for a copy session on page 37, and/or Preparing a Symmetrix storage system using ESN Manager on page

26 SAN Copy Configuration Guidelines Copying data between LUNs within a CLARiiON storage system If you will copy data from one LUN to one or many LUNs within the same CLARiiON storage system, the following requirements must be met before you start a SAN Copy session. Note: You do not need to zone Fibre Channel connections or create iscsi connection sets when you are copying data within a storage system. The storage system must be a SAN Copy storage system. The source and all destination LUNs participating in a copy session must belong to the same SP. Note: If you need to copy between LUNs owned by different SPs, you must trespass either the source or destination LUNs before starting the session. For incremental copy sessions: The source logical unit cannot be a SnapView snapshot. You must configure the reserved LUN pool before you start an incremental SAN Copy session. For more information, see the Navisphere Manager online help, packaged with the software and available from Powerlink. Sample SAN Copy configuration 26 EMC SAN Copy Command Line Interfaces Reference Figure 1 shows a sample SAN Copy configuration that includes a SAN Copy storage system on the left, and a remote storage system on the right (either a CLARiiON or Symmetrix storage system). LUNs 1, 2, 3, and 4 reside in the SAN Copy storage system and LUNs 5 and 6 reside in the remote storage system. Within the SAN Copy storage system, the data on LUN 1 is being copied to LUN 2. LUNs 1 and 2 must belong to the same SP, and no zoning is required. An incremental copy session is copying the data on LUN 4 to LUN 6. LUN 4 (the source LUN) must reside in a SAN Copy storage system. Since the source logical unit is on the SAN Copy system, SAN Copy is able to copy LUN 4 s data to many destination LUNs on many storage systems. A full copy session is copying the data on LUN 5 to LUN 3. Since the source LUN (LUN 5) does not reside in a SAN Copy storage system,

27 SAN Copy Configuration Guidelines all the destination LUNs for LUN 5 must reside in the same SAN Copy storage system. Server Server Server Switch fabric Switch fabric separate server required for AX-series storage system Source LUN LUN 1 SAN Copy zone Destination LUN LUN 2 Destination LUN LUN 3 Source LU LUN 5 Source LUN LUN 4 Destination LU LUN 6 SAN Copy storage system Remote storage system EMC3048 Figure 1 Sample SAN Copy configuration 27

28 SAN Copy Configuration Guidelines Fibre Channel zoning requirements and recommendations Note: Zoning is not required for copying data between LUNs within a CLARiiON storage system. SAN Copy software does not support configurations where a SAN Copy port is zoned to a storage system that is not supported by SAN Copy software. Refer to the EMC Support Matrix (ESM) or SAN Copy release notes for a list of supported storage systems. Currently, SAN Copy and MirrorView software cannot share the same SP port (refer to the SAN Copy release notes for confirmation). Each port in a SAN Copy storage system is a dual-mode port. When the port is participating in a SAN Copy session, it acts as an initiator to the remote storage systems and any other SAN Copy ports in the same zone. When the host initiators are using the port to transfer I/O, the port acts as a target to the host initiator. Each time a host initiator registers with the SAN Copy port or the SAN Copy port registers with another SP port, the SAN Copy port consumes a login resource. If you consume all login resources for the SAN Copy port, the SAN Copy session may not successfully complete on all destination logical units. EMC recommends that you follow the single initiator to single remote SP port rule when creating and configuring SAN Copy zones include only one SAN Copy port (initiator) and only one remote SP port in each zone. For examples of single initiator zoning, refer to Single-initiator zoning examples without and with SAN Copy installed on page 32. Zoning recommendations You can create a variety of SAN Copy zoning configurations. EMC recommends that you configure your zoning so that: There are redundant connection paths from the SAN Copy ports to the logical units on the remote storage system. Each SP on the SAN Copy storage system (SAN Copy port) has access to each SP on the remote storage system. 28 EMC SAN Copy Command Line Interfaces Reference

29 SAN Copy Configuration Guidelines To accomplish this, EMC recommends that you create four zones from the SAN Copy storage system to the remote storage system. This results in a consistent easy-to-troubleshoot zoning configuration. Zones San Copy storage system Remote storage system Zone 1 SP A port 1 SP A port 1 Zone 2 SP A port 1 SP B port 1 Zone 3 SP B port 1 SP A port 1 Zone 4 SP B port 1 SP B port 1 If this zoning configuration does not meet your needs, you can also create your zoning based on the most important criteria for the SAN Copy session performance, availability, or preserving host login resources. The following sections recommend zoning configurations for these criteria. Note: As an absolute minimum, configure one zone that includes a single port on a single SP in the SAN Copy storage system and a single port on a single SP in the remote storage system. This configuration does not provide high availability for the SAN Copy session or access to logical units belonging to both SPs on the remote storage system. Performance If performance is most important, we recommend that you create multiple zones, each with a different SAN Copy port zoned to the same remote SP ports. SAN Copy allows multiple sessions to share a single port, but if multiple ports are available, SAN Copy will spread multiple sessions across available SAN Copy ports to maximize total throughput. Note: This configuration increases performance only when you have multiple, concurrent copy sessions running. This configuration will not increase performance for a single session. In Figure 2, LUN 1 and LUN 2 on the SAN Copy storage system belong to SP A. Zones 1 and 3 provide multiple connection paths from LUNs 1 and 2 to the remote storage system. In this example, two SAN Copy sessions are running. One session is copying data from LUN 3 to LUN 1 using port 0 on SP A of the SAN Copy storage system. The other session is copying data from LUN 2 to LUN 4 and is using port 1 on SP A. 29

30 SAN Copy Configuration Guidelines Server Server Switch Fabric Switch Fabric SP A SP B SP A SP B Destination LUN LUN 1 Source LUN LUN 3 Source LUN LUN 2 SAN Copy Storage System Destination LUN LUN 4 Remote Storage System EMC2698 Figure 2 Recommended zoning based on performance Availability For high availability when you use SAN Copy, EMC recommends that you configure a minimum of two zones. Each zone should include one port from a different SP in the SAN Copy storage system and one port from each SP in the remote storage system. Figure 3 shows the minimum recommended high-availability SAN Copy zoning configuration using zones 1 and 2. Zones SAN Copy storage system Remote storage system Zone 1 SP A port 0 SP A port 1 and SP B port 1 Zone 2 SP B port 0 SP A port 0 and SP B port 0 In the following example, three copy sessions are running. The session copying data from LUN 2 to LUN 4 is using zone 1. The session copying data from LUN 3 to LUN 1 is using zone 2. The third session, LUN 2 to LUN 1, requires no zoning. 30 EMC SAN Copy Command Line Interfaces Reference

31 SAN Copy Configuration Guidelines Server Server Server Switch Fabric Switch Fabric separate server required for AX-Series Storage System SP A SP B SP A SP B Destination LUN LUN 1 Source LU LUN 3 Source LUN LUN 2 SAN Copy Storage System Destination LU LUN 4 Remote Storage System EMC3052 Figure 3 Recommended zoning based on availability Limiting host login resources If limiting host login resources is most important because a large number of hosts connect to a remote storage system, zone only necessary SAN Copy ports to that storage system. Note: For more information on limiting host login resources, refer to the section on login resources on page 28. The following table describes each zoning configuration: Zones SAN Copy storage system Remote storage system Zone 1 SP A port 0 SP A port 1 and SP B port 1 Zone 2 SP B port 0 SP A port 0 and SP B port 0 In Figure 4, three copy sessions are running. The session copying data from LUN 2 to LUN 4 is using zone 1. The session copying data from LUN 3 to LUN 1 is using zone 2. The third session, LUN 2 to LUN 1 requires no zoning. 31

32 SAN Copy Configuration Guidelines Server Server Server Switch Fabric Switch Fabric separate server required for AX-Series Storage System SP A SP B SP A SP B Destination LUN LUN 1 Source LU LUN 3 Source LUN LUN 2 SAN Copy Storage System Destination LU LUN 4 Remote Storage System EMC3052 Figure 4 Recommended zoning based on limiting login resources Single-initiator zoning examples without and with SAN Copy installed A single-initiator zone includes only one host or SAN Copy initiator. The two exceptions to the single-initiator rule for SAN Copy are: Never place more than one SAN Copy port in the same zone unless two SAN Copy storage systems are in the domain, and each storage system is acting as both the SAN Copy storage system and the remote storage system to the other. Never place a SAN Copy port in the same zone as the host unless the host HBA initiator is connected to the SAN Copy port for the purpose of host I/O. Figure 5 shows an example of single-initiator zoning between a server and two storage systems for the purpose of data I/O. Neither storage system is a SAN Copy storage system. In this example, zone 1 includes the HBA initiator port and a target port on each SP in both storage systems. 32 EMC SAN Copy Command Line Interfaces Reference

33 SAN Copy Configuration Guidelines Server Server 1 2 Switch Fabric separate server required for AX-Series Storage System SP A SP B SP A SP B Storage System w/o SAN Copy Storage System w/o SAN Copy EMC3049 Figure 5 Sample single-initiator zoning without SAN Copy 33

34 SAN Copy Configuration Guidelines If you install SAN Copy on one of the storage systems in the previous example, change your zoning to the configuration shown in Figure 6. This example shows each SAN Copy port in a separate zone with the host initiator (zones 2 and 3). If you keep the zoning as it was in Figure 5, additional login resources will be consumed for the ports, even if you are not currently using SAN Copy. Server Server 4 separate server required for AX-Series Storage System 3 2 Switch Fabric SP A SP B SP A SP B SAN Copy Storage System Storage System w/o SAN Copy EMC3050 Figure 6 Sample single-initiator zoning with SAN Copy installed Figure 7 shows an example of single-initiator zoning between a server and two storage systems for the purpose of data I/O and SAN Copy data transfer. One of the storage systems is a SAN Copy storage system. In this example, the hosts are in zones with all necessary target ports, including SAN Copy ports (zones 1,2, 3 and 6), and the SAN Copy ports are in separate zones with the remote ports they must access (zones 4 and 5). The six zones are configured as follows: 34 EMC SAN Copy Command Line Interfaces Reference

35 SAN Copy Configuration Guidelines Zone identifier Purpose Includes Zone 1 Data I/O HBA initiator port, SP A port 1 and SP B port 1 on remote storage system #1. Zone 2 Data I/O HBA initiator port, SP B port 0 on SAN Copy storage system. Zone 3 Data I/O HBA initiator port, SP A port 0 on SAN Copy storage system. Zone 4 SAN Copy session SP B port 0 on SAN Copy storage system, SP B port 1 on remote storage system. Zone 5 SAN Copy session SP A port 0 on SAN Copy storage system, SP A port 1 on remote storage system. Zone 6 Data I/O HBA initiator port, SP A port 1 and SP B port 1 on remote storage system #2 Server Server separate server required for AX-Series Storage System 1 Switch Fabric SP A SP B SP A SP B SAN Copy Storage System Remote Storage System EMC3051 Figure 7 Sample single-initiator zoning with SAN Copy installed and configured 35

36 SAN Copy Configuration Guidelines iscsi zoning requirements and recommendations Use data replication over iscsi to replace replication over IP using FC-IP bridges. Both EMC SAN Copy and EMC MirrorView support SCSI replication between storage systems that support the feature. In order to replicate data over iscsi you must create connection sets between the participating iscsi storage systems ports. A connection set is a named set of information used by a CLARiiON iscsi initiator to establish a repliation session with an iscsi target. A connection set consists of a unique user-defined name, optional username and password (secret), credentials usage (connection specific, array-shared or none), and one or more connection paths. Each connection set should include only one iscsi initiator. EMC recommends that you use the SAN Copy Create Session wizard or the MirrorView wizard to initially configure connection sets for iscsi replication. For informaion on connection sets and using the wizards, see the Navisphere Manager online help. You can also use CLI commands to create connection sets - see the Navisphere Command Line Interface Reference. 36 EMC SAN Copy Command Line Interfaces Reference

37 SAN Copy Configuration Guidelines Preparing a CLARiiON storage system for a copy session If you will be copying data between CLARiiON storage systems or between CLARiiON and Symmetrix storage systems, follow the SAN Copy configuration requirements on page 22, and prepare the CLARiiON storage systems as described in the following procedure. You can use logical units (LUNs) in a CLARiiON storage system as the source or destination of SAN Copy sessions. If you will be copying data between LUNs within a CLARiiON storage system, see Copying data between LUNs within a CLARiiON storage system on page 26. Note: For all sessions, you must install SAN Copy software on at least one of the CLARiiON storage systems. For incremental copy sessions, the source logical unit must reside in the SAN Copy storage system. 1. For Fibre Channel replication, use the native switch management tools to zone at least one port from an SP on the SAN Copy storage system to one or more SP ports on the participating remote storage systems (see Fibre Channel zoning requirements and recommendations on page 28). For iscsi replication, create connection sets. A connection set establishes a replication session between an iscsi initiator and an iscsi target. A connection set consists of a unique user-defined name, optional username and password (secret), method for assigning security credentials (connection specific, array-shared or none), and one or more connection paths. Each connection set should include only one iscsi initiator. For more information on connection sets, see the Navisphere Manager online help or the Navisphere Command Line Interface Reference. Note: SAN Copy ports act as host initiators to remote storage systems (storage system without SAN Copy software). 2. Register the SAN Copy ports with any other SP ports in the same zone using the naviseccli or navicli -h spname sancopy -updateconnections command (see page 113). If the remote system is a CLARiiON storage system, the SAN Copy ports register with each storage system, and the software adds a record for each SAN Copy port to the storage system s 37