EMC SAN Copy/E Administrator's Guide · PDF fileEMC2, EMC, CLARiiON, Navisphere, PowerPath, ... MirrorView, and SnapView are ... 1-2 EMC SAN Copy/E for Navisphere Administrator’s

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC SAN Copy/Efor Navisphere

ADMINISTRATOR’S GUIDE

P/N 300-002-664REV A01

www.emc.com

EMC SAN Copy/E for Navisphere Administrator’s Guideii

Copyright © 2005 EMC Corporation. All rights reserved.

Published July, 2005

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.

Trademark InformationEMC2, EMC, CLARiiON, Navisphere, PowerPath, Symmetrix, and TimeFinder are registered trademarks, and Access Logix, EMC ControlCenter, FLARE, Powerlink, SAN Copy, MirrorView, and SnapView are trademarks of EMC Corporation.All other trademarks used herein are the property of their respective owners.

EMC SAN Copy/E for Navisphere Administrator’s Guide iii

Preface.............................................................................................................................. v

Chapter 1 About EMC SAN Copy/E SoftwareTerminology ..................................................................................... 1-2Introducing SAN Copy/E Software.............................................. 1-5SAN Copy/E Features and Benefits ............................................. 1-6

Incremental Copying from Remote Systems to Data Center ......................................................................................... 1-6Storage-System-Based Data-Mover Application ................. 1-6Easy-to-Use Web-Based Application ..................................... 1-7Use with Replication Software ............................................... 1-7

SAN Copy/E Software Components ............................................ 1-8Using Online Help ........................................................................... 1-8

Chapter 2 SAN Copy/E Configuration GuidelinesSAN Copy/E Configuration Requirements................................. 2-2

Copying Data Between CLARiiON Storage Systems ......... 2-2SAN Copy/E Zoning Requirements and Recommendations ... 2-4Preparing a CLARiiON Storage System for a Copy Session ..... 2-9

Connecting SAN Copy Ports to CLARiiON Storage Groups...................................................................................... 2-10

Implementing SAN Copy over Extended Distances ................ 2-14Performance Considerations................................................. 2-14

Contents

EMC SAN Copy/E for Navisphere Administrator’s Guideiv

Contents

Chapter 3 Setting Up and Using SAN Copy/ESetting Up SAN Copy/E ................................................................ 3-2Creating SAN Copy/E Sessions .................................................... 3-3

Creating Sessions Using the Wizard...................................... 3-4Creating a Session Using a LUN’s Right-Click Menu Option ........................................................................................ 3-9

Preparing Logical Units for Copy Sessions................................ 3-11Preparing Source and Destination Logical Units for Full and Incremental Sessions .............................................................. 3-11

Starting SAN Copy/E Sessions ................................................... 3-14Starting Full Copy Sessions................................................... 3-15Starting Incremental Copy Sessions .................................... 3-15

Remounting the Source and Destination Logical Units........... 3-17Using SAN Copy/E to Manage Sessions ................................... 3-19Modifying Properties for Copy Sessions.................................... 3-21

Editing the Environmental Properties for All Sessions on a Storage System........................................................................ 3-21Editing a Single Copy Session’s Properties ........................ 3-22

Viewing Copy Session Status....................................................... 3-24To View Status of a Single Session....................................... 3-24To View Status of All Sessions on a Storage System......... 3-25

Monitoring and Responding to SAN Copy/E Events ............. 3-27

Appendix A Handling SAN Copy/E Session FailuresHandling Session Failures ............................................................. A-2

Unable to Create Copy Sessions............................................ A-2Copy Session Fails ................................................................... A-3

Appendix B Customer SupportOverview of Detecting and Resolving Problems ...................... B-2Troubleshooting the Problem ....................................................... B-3Before Calling the Customer Support Center ............................ B-4Documenting the Problem ........................................................... B-5Reporting a New Problem ............................................................ B-6Sending Problem Documentation ............................................... B-7

Index................................................................................................................................ i-1

EMC SAN Copy/E for Navisphere Administrator’s Guide v

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 This guide describes the tasks for setting up, configuring, and managing a storage system using EMC® SAN Copy™/E software. Each major section includes introductory information and a general procedure for completing a task. This manual is not intended for use during the actual setup, configuration, and management of storage systems so the steps in the procedures purposely do not include screen captures of the dialog boxes.

The introductory information and detailed steps for each procedure appear in the SAN Copy software online help so you have the complete information available when you actually set up, configure, and manage storage systems, should you require help.

Audience This guide is part of the EMC SAN Copy/E (referred to as SAN Copy/E later in this document) documentation set, and is intended for use by customers and service providers who use EMC Navisphere® Manager to set up and manage SAN Copy/E software.

Readers of this guide are expected to be familiar with EMC Navisphere Manager.

vi EMC SAN Copy/E for Navisphere Administrator’s Guide

Preface

Organization This guide is organized as follows:.

RelatedDocumentation

Other related documents include:

◆ EMC Navisphere Manager Administrator’s Guide (P/N 069001125)

◆ EMC SAN Copy/E Command Line Interfaces Reference (P/N 300-002-665)

◆ EMC CX-Series SAN Copy/E Release Notes

◆ EMC admhost Release Notes

Conventions Used inThis Guide

EMC uses the following conventions for notes, cautions, warnings, and danger notices.

A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.

Chapter 1 Introduces the EMC SAN Copy/E application; defines SAN Copy software and other terms used in this guide; lists and describes some of its features and benefits.

Chapter 2 Describes SAN Copy/E configuration guidelines.

Chapter 3 Describes the steps required for setting up and using SAN Copy/E, such as creating full and incremental copy sessions, and using SAN Copy/E to manage copy sessions.

Appendix A Describes recovery strategies for copy session failures.

Appendix B Reviews the EMC process for detecting and resolving software problems, and provides essential questions that you should answer before contacting the EMC Support Center.

EMC SAN Copy/E for Navisphere Administrator’s Guide vii

Preface

Typographical ConventionsThis manual uses the following format conventions:

Finding CurrentInformation

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:

http://powerlink.emc.com

After you log in, select Support > Document Library and find the following:

◆ EMC CX-Series SAN Copy/E Release Notes

◆ EMC admhost Release Notes

This typeface

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.

This typeface 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.

This typeface

Represents a system response (such as a message or prompt), a file or program listing.

x > y 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.

http://powerlink.emc.com

viii EMC SAN Copy/E for Navisphere Administrator’s Guide

Preface

◆ The latest version of this guide that is applicable to your software revision

EMC Installation Roadmap for CX-Series, AX-Series, and FC-Series 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 For questions about technical support, call your local sales office or service provider.

If you have a valid EMC service contract, contact EMC Customer Service at:

Follow the voice menu prompts to open a service call and select the applicable product support.

Sales and CustomerService Contacts

For the list of EMC sales locations, please access the EMC home page at:

http://www.EMC.com/contact/

For additional information on the EMC products and services available to customers and partners, refer to the EMC Powerlink™ website at:

http://powerlink.EMC.com

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 [email protected] with your opinions of this guide.

United States: (800) 782-4362 (SVC-4EMC)

Canada: (800) 543-4782 (543-4SVC)

Worldwide: (508) 497-7901

http://www.EMC.com/contact/


mailto:[email protected]

About EMC SAN Copy/E Software 1-1

1Invisible Body Tag Lite

This chapter introduces the EMC® SAN Copy™/E software and describes the application’s main features and benefits.

Major sections are

◆ Terminology........................................................................................1-2◆ Introducing SAN Copy/E Software................................................1-5◆ SAN Copy/E Features and Benefits................................................1-6◆ SAN Copy/E Software Components ..............................................1-8◆ Using Online Help .............................................................................1-8

About EMC SANCopy/E Software

1-2 EMC SAN Copy/E for Navisphere Administrator’s Guide

About EMC SAN Copy/E Software

Terminology

Term Meaning

Access Logix™ option See shared storage system.

admhost utility The admhost utility is an executable program that you can run interactively via script. It runs on Microsoft Windows NT®, Windows® 2000, and Windows Server™ 2003 systems.

auto recovery The state of a copy session that is trying to resume failed sessions.

buffer space Memory used for temporary data storage.

checkpoint interval A user-defined time interval that lets an interrupted copy session resume from the last checkpoint, rather than having to start the session over.

CLI EMC Navisphere® Command Line Interface.

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

copy-on-first-write An algorithm that copies current contents of a source LUN to the reserved LUN pool before it is modified (written to).

destination logical unit A logical unit to which SAN Copy/E is copying the source data. On a CLARiiON® storage system, this device is called a LUN.

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

Event Monitor EMC Navisphere Event Monitor.

full copy session A full copy session copies all the data on the source logical unit to one or many destination logical units.

Host Agent EMC Navisphere Agent that runs on a storage-system server.

incremental copy session An incremental copy session copies only the data that has changed since the last copy session.

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

link bandwidth The bandwidth of the network connection used to transfer copy data.

Terminology 1-3


logical unit (LU) 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.

LUN CLARiiON term for logical unit.

managed Agent A Host Agent or SP Agent managed by Navisphere management software.

managed storage system A storage system managed by Navisphere management software.

Manager EMC Navisphere Manager.

metaLUN A type of LUN whose capacity is the combined capacities of all the LUNs that comprise it.

multi-domain environment A group of domains that you can manage from a single instance of Navisphere Manager.

portal A server or storage system through which you manage one or more storage systems using Navisphere 6.X. Generally the managed systems are legacy systems such as FC4500s and FC5300s.

remote storage system A storage system with logical units that are participating in a copy session, but it does not own the copy session.A remote storage system must be a CX-Series storage system runningSAN Copy.

reserved LUN pool The reserved LUN pool works with SAN Copy/E 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 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 Administrator’s Guide or the online help.

reserved session A private session created by SAN Copy/E 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.

SAN Storage area network: One or more servers connected to one or more storage systems via Fibre Channel switches. Switch zoning and EMC Access Logix software control server access to storage systems and LUNs.

SAN Copy/E Software running on a SAN Copy/E storage system that lets you copy logical unit information between the SAN Copy/E storage systems and other CLARiiON storage systems running SAN Copy.

SAN Copy/E port An SP port initiator on a SAN Copy/E storage system that is participating in a copy session.

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.

Term Meaning



SAN Copy/E storage system The CX300 or AX-Series storage system that owns the copy session. A SAN Copy/E storage system must be running SAN Copy/E and Access Logix software. You can install SAN Copy/E on a CX300 or AX-Series storage system, but not on a CX400, CX500, CX600, CX700, or FC4700-Series storage system.

shared storage system A storage system with the EMC Access Logix™ option, which provides data access control (Storage Groups). A shared storage system is always a RAID Group storage system.

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

source logical unit A logical unit from which SAN Copy/E copies data. On a CLARiiON storage system, this device is called a LUN (can be a single LUN or a metaLUN).

SP Agent EMC Navisphere Agent that runs on the SPs in a CX-Series or FC4700-Series storage systems.

Storage Management Server software

Software that runs in a storage system or portal server and lets a person manage it over a network.

throttle value 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.

unshared storage system A storage system without the EMC Access Logix option.

virtual disk An AX-Series storage system term for logical unit.

zone A zone that limits access to specific logical units in a storage system, thereby increasing security and decreasing network traffic.

Term Meaning

Introducing SAN Copy/E Software 1-5


Introducing SAN Copy/E SoftwareEMC SAN Copy/E software (referred to as SAN Copy/E later in this document) runs on a SAN Copy/E storage system— the CLARiiON storage system that owns the copy session (for supported SAN Copy/E storage systems see the Terminology section on page 1-2). SAN Copy/E copies data from CX300 and AX-Series storage systems to CX-Series storage systems running SAN Copy. It copies data directly from a source logical unit on one storage system to destination logical units on other systems, without using host resources. It 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 (see Implementing SAN Copy over Extended Distances on page 2-14). SAN Copy/E 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.

When SAN Copy/E is installed on a storage system, the storage system SP ports become initiators and therefore behave much like host initiators. For example, they can be added to Storage Groups, and they must be part of any copy zoning configurations.

You can use SAN Copy/E 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 Copy Sessions on page 3-11). Regardless of the type of copy session — full or incremental — the participating logical units must meet certain requirements (see SAN Copy/E Configuration Requirements on page 2-2).

You can use SAN Copy/E for routine copying of data from remote offices to the data center for centralized backup or application testing.

To manage copy sessions, you can use either the UI-based Navisphere Manager (described in this manual), or the SAN Copy/E Command Line Interface described in the EMC SAN Copy/E Command Line Interfaces Administrator’s Guide.



SAN Copy/E Features and BenefitsThe SAN Copy/E software adds value to customer systems by offering the following features:

◆ Incremental copy sessions from an AX-Series or CX300 storage system to SAN Copy systems located in the data center.

◆ 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 copy sessions.

◆ Software that you can use in conjunction with replication software, allowing I/O with the source logical unit to continue during the copy process.

Incremental Copying from Remote Systems to Data Center

SAN Copy/E lets you use a LUN that resides on an AX-Series or CX300 storage system as the source of an incremental copy session. The incremental 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 copy feature

◆ The source logical unit cannot be a SnapView snapshot.

◆ You must configure the reserved LUN pool (see the EMC Navisphere Manager Administrator’s Guide).

Storage-System-Based Data-Mover Application

SAN Copy/E is a storage-system-based data-mover application that uses a SAN (storage area network) to copy data between storage systems. Since SAN Copy/E 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

SAN Copy/E Features and Benefits 1-7


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/E is an integrated part of Navisphere Manager, the easy-to-use, web-based management tool for CLARiiON storage systems. Manager lets you select the source and destination logical units for the copy session, create copy sessions and then manage these sessions.

Use with Replication Software

If the storage system containing the source logical unit has device replication technology, such as EMC SnapView™ software, SAN Copy/E can use a snapshot (full copy sessions only), or clone as its source logical unit — allowing I/O with the source logical units for the snapshot or clone to continue during the copy process.

AX-Series storage systems do not support SnapView clones.

You must fracture a SnapView clone before using it as a source LUN in a copy session. For more details, refer to the SnapView documentation and online help.

Integration with EMC SnapView SoftwareSAN Copy/E tracks server writes to the source LUN (for example, from the production server), but does not track server writes to the destination LUN (for example, from the secondary server). SnapView can be used with SAN Copy/E to create a snapshot of the destination LUN, so that the SnapView replica can be put in the secondary server storage group, rather than the destination logical unit. This allows the destination logical unit to maintain consistency with its source, and be available on an ongoing basis for incremental updates.



SAN Copy/E Software ComponentsSAN Copy/E consists of the following software components:

◆ SAN Copy/E software installed and enabled on a SAN Copy/E storage system.

The CX300 and AX-Series storage systems ship from the factory with SAN Copy/E software installed, but not enabled. To use the SAN Copy/E software functionality, you must install the SAN Copy/E enabler on the storage system.

◆ The admhost utility, which provides a command line executable that lets you execute certain commands — lun_activate, lun_deactivate and lun_flush, lun_list when managing 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/E 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/E storage system.

CX300 storage systems ship from the factory with Navisphere Manager installed and enabled.

◆ Navisphere Command Line Interface (CLI), which ships as part of the Navisphere Host Agent packages.

Using Online HelpThe following help is available online from the Navisphere Manager user interface.:

◆ A set of organized, linked help topics

To access the online help table of contents, click Help > Help Topics on the Menu bar in the application’s Main window, or click the help icon in the Toolbar.

◆ Context-sensitive help topics

To display context-sensitive help, click the Help button displayed in each dialog box.

SAN Copy/E Configuration Guidelines 2-1

2Invisible Body Tag

This chapter lists the basic requirements, restrictions and configuration guidelines for using SAN Copy/E.

Major sections are

◆ SAN Copy/E Configuration Requirements...................................2-2◆ SAN Copy/E Zoning Requirements and Recommendations .....2-4◆ Preparing a CLARiiON Storage System for a Copy Session .......2-9◆ Implementing SAN Copy over Extended Distances ..................2-14

SAN Copy/EConfiguration

Guidelines


SAN Copy/E Configuration Guidelines

SAN Copy/E Configuration Requirements SAN Copy/E lets you copy data from a SAN Copy/E storage system to other CLARiiON CX-Series storage systems that are running SAN Copy. This section describes the configuration requirements and restrictions for copying data between the CLARiiON storage systems.

You cannot copy data between CX300 or AX-Series storage systems and Symmetrix storage systems.

Copying Data Between CLARiiON Storage Systems To copy data between SAN Copy/E and CX-Series storage systems running SAN Copy the following requirements must be met before you start a copy session.

All Copy Sessions (Full and Incremental)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 2-3.

◆ If any of the storage systems participating in a copy session are connected to a VMware® ESX Server, all logical volumes participating in the session must be configured as raw device mapping volumes set to physical compatibility mode.If you will be using logical volumes that are not already configured as raw device mapping volumes, use the VMware vmkfstools utility to reconfigure them. For information on using this utility, refer to the Managing Raw Device Mappings - Utilities section found at http://www.vmware.com/pdf/esx25_rawdevicemapping.pdf

These requirements apply to logical volumes residing in CLARiiON storage systems.

◆ You must correctly zone SAN Copy/E storage system ports to remote storage systems so that SAN Copy/E can have access to these systems (see SAN Copy/E Zoning Requirements and Recommendations on page 2-4).

SAN Copy storage system ports act as host initiators to the remote storage systems. They can be added to Storage Groups and they must belong to the same zone as the logical units participating in the copy session.

http://www.vmware.com/pdf/esx25_rawdevicemapping.pdf

SAN Copy/E Configuration Requirements 2-3


◆ The source logical unit must reside on the SAN Copy/E storage system.

Because the source logical unit resides in the SAN Copy/E storage system, you can copy data to one or many destination logical units on one or many storage systems. All the destination storage systems must be running SAN Copy.

◆ In order for the wizard to display a list of available logical units for this copy session, and for Navisphere Manager to provide the drive letter/file system mapping of participating CLARiiON LUNs, complete the following tasks before creating a copy session:

• Place all CLARiiON storage systems in the same domain or multi-domain environment as the SAN Copy/E storage system on which you create the session.

• Mount all participating logical units.

◆ In order for the logical units to participate in a copy session, you must make the logical units accessible to the participating SAN Copy/E storage system port. For example, for CLARiiON storage systems, you must add the copy port to the Storage Group on the remote storage system that includes the participating logical unit.

Incremental Copy SessionsIncremental copy sessions must meet all the requirements for full sessions with the following exceptions and additions:

Exception◆ The source logical unit cannot be a SnapView snapshot.

Additions◆ You must configure the reserved LUN pool before you start an

incremental copy session. The reserved LUN pool works with the copy software to perform incremental copy operations. It consists of one or more private LUNs. Before starting an incremental 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 Administrator’s Guide or the online help.

What Next? ◆ SAN Copy/E Zoning Requirements and Recommendations on page 2-4.

◆ See Preparing a CLARiiON Storage System for a Copy Session on page 2-9.



SAN Copy/E Zoning Requirements and Recommendations

SAN Copy/E does not support configurations where a SAN Copy/E storage system port is zoned to a storage system that is not supported by SAN Copy/E. Refer to the ESM or CX-Series SAN Copy/E Release Notes for a list of supported storage systems.

Currently, SAN Copy/E and MirrorView™ software cannot share the same SP port (refer to the CX-Series SAN Copy/E Release Notes for confirmation).

You can create a variety of SAN Copy/E zoning configurations. We recommend that you configure your zoning so that

◆ There are redundant connection paths from the SAN Copy/E storage system ports to the logical units on the remote storage system.

◆ Each SP on the SAN Copy/E storage system has access to each SP on the remote storage system.

To accomplish this, we recommend that you create four zones from the SAN Copy/E 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 0 SP A-port 0

Zone 2 SP A-port 0 SP B-port 0

Zone 3 SP B-port 0 SP A- port 0

Zone 4 SP B-port 0 SP B-port 0

SAN Copy/E Zoning Requirements and Recommendations 2-5


Figure 2-1 shows an example of this configuration. In this example, the SAN Copy storage system is a CX300 storage system running SAN Copy/E, and the remote storage system is a CX-Series storage system running SAN Copy.

Figure 2-1 Recommended Zoning Configuration

If this zoning configuration does not meet your needs, you can also create your zoning based on the most important criteria for the copy session — performance, availability, or preserving host login resources. The following sections recommend zoning configurations for these criteria.

As an absolute minimum, configure one zone that includes a single port on a single SP in the SAN Copy/E storage system and a single port on a single SP in the remote storage system. This configuration does not provide high availability for the copy session nor access to logical units belonging to both SPs on the remote storage system.

Server Server

EMC3076

1

132

34

2 4

SAN Copy Storage System Remote Storage System

Switch Fabric Switch Fabric

SP A SP B SP A SP B



Performance If performance is most important, we recommend that you create multiple zones, each with a different SAN Copy/E storage system port zoned to the same remote SP ports. SAN Copy/E allows multiple sessions to share a single port, but, if multiple ports are available, it will spread multiple sessions across available SAN Copy/E storage system ports to maximize total throughput.

This configuration will increase performance only when you have multiple, concurrent copy sessions running. This configuration will not increase performance for a single session.

In Figure 2-2, the SAN Copy storage system is a CX300 storage system runing SAN Copy/E. LUN 1 and LUN 2 on the SAN Copy/E storage system belong to SP A. Zones 1 and 3 provide multiple connection paths from LUNs 1 and 2 to the remote storage system (a CX-Series storage system running SAN Copy). In this example, two copy sessions are running. One session is copying data from LUN 1 to LUN 3 using port 0 on SP A of the SAN Copy/E storage system. The other session is copying data from LUN 2 to LUN 4 and is using port 1 on SP A.

Figure 2-2 Recommended Zoning Based on Performance

Server Server

1 11 3 33

Switch Fabric Switch Fabric

SP A SP B SP A SP B


Source LUNLUN 2

Source LUNLUN 1

Destination LUNLUN 3


SAN Copy/E Zoning Requirements and Recommendations 2-7


AvailabilityFor high availability when you use SAN Copy/E, we recommend that you configure a minimum of two zones. Each zone should include one port from a different SP in the SAN Copy/E storage system and one port from each SP in the remote storage system (a CX-Series storage system running SAN Copy).

Figure 2-4 shows the minimum recommended high-availability SAN Copy/E zoning configuration.

In this example, the SAN Copy storage system is a CX300 storage system running SAN Copy/E and the remote storage system is a CX-Series storage system running SAN Copy. In this example, two copy sessions are running. One session is copying data from LUN 1 to LUN 3. The other session is copying data from LUN 2 to LUN 4.

Figure 2-3 Recommended Zoning Based on Availability

Zones SAN Copy/E 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

EMC3052L

1 11

22

2

SAN Copy Storage System

SP A SP B

Source LUNLUN 1

Remote Storage System

SP A SP B



Switch Fabric

ServerServer Server

Switch Fabric

Source LUNLUN 2



Limiting Host Login ResourcesEach port in a SAN Copy/E storage system is a dual-mode port. When the port is participating in a copy session, it acts as an initiator to the remote storage systems and any other 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/E storage system port or the port registers with another SP port, the copy port consumes a login resource. If you consume all login resources for the copy port, the copy session may not successfully complete to all destination logical units. If limiting host login resources is most important because a large number of hosts connect to a remote storage system, zone only the necessary SAN Copy/E storage system ports to that storage system.

Figure 2-4 shows an example of initiator zoning between a server and two storage systems for the purpose of data I/O and SAN Copy data transfer. In this example. the SAN Copy storage system is a CX300 storage system running SAN Copy/E. The servers 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).

Figure 2-4 Recommended Zoning Based on Limiting Login Resources

Switch Fabric

5 4 5 43 2 11 1

1


separate serverrequired for AX-Series

Storage System

Server Server

1

3

2 6

66

SP A SP B SP A SP B

Preparing a CLARiiON Storage System for a Copy Session 2-9


Preparing a CLARiiON Storage System for a Copy SessionTo copy data from CX300 and AX-Series storage systems to CX-Series storage systems running SAN Copy, follow the SAN Copy/E configuration requirements, as discussed in SAN Copy/E Configuration Requirements on page 2-2, and prepare the CLARiiON storage systems as described in the following procedure.

You must install the SAN Copy/E Enabler software on the CX300 or AX-Series storage system.

For full and incremental copy sessions, the source logical unit must reside on the SAN Copy/E storage system.

To complete this procedure, you must be familiar with Navisphere Manager.

1. Use the native switch management tools to zone at least one port from an SP on the SAN Copy/E storage system to one or more SP ports on the participating remote storage systems (see SAN Copy/E Zoning Requirements and Recommendations on page 2-4).

SAN Copy/E storage system ports act as host initiators to remote storage systems.

2. On the SAN Copy/E storage system, use Navisphere Manager to register the SAN Copy/E storage system ports with the other CLARiiON storage systems as follows:

a. In the Storage tree in the Enterprise Storage window, right-click the icon for the SAN Copy/E storage system.

b. Click SAN Copy > Update Connections.

The SAN Copy/E ports register with each storage system to which they have a connection, and the software adds a record for each port to the storage system’s host initiator table. Navisphere Manager displays an entry for each registered SAN Copy/E port in the Connectivity Status dialog box, and the SAN Copy Connections Summary dialog box.

3. On the remote storage systems, use the SAN Copy Connections Summary dialog box to verify that any remote storage systems that will participate in a copy session are connected and registered withthe SAN Copy/E storage system.



• On the Tools menu, click SAN Copy > Connections Summary. This dialog box displays an entry for each SAN Copy and SAN Copy/E storage system port that is connected and registered to another storage system. Each entry uses the following format:

What Next? For CX-Series storage systems, go to the next section, Connecting SAN Copy Ports to CLARiiON Storage Groups on page 2-10.

Connecting SAN Copy Ports to CLARiiON Storage Groups

Each SAN Copy port acts like a host initiator and, therefore, can connect to only one Storage Group at a time in a storage system.

For AX-Series storage systems that are not running Navisphere Manager, you must use Navisphere Express to connect the SAN Copy ports to the virtual disks on the AX-Series storage system that will participate in the copy session (for instructions, refer to the Navisphere Express online help).

In order for the LUNs to be accessible to the SAN Copy/E storage system ports, you must connect the ports to the Storage Groups in which the LUNs reside. When connecting to the Storage Group, SAN Copy/E lets you select all the available SP ports with valid connections to the Storage Group, or it lets you select specific ports.

If all participating logical units on a remote storage system already belong to the same Storage Group, you can connect the SAN Copy

SAN Copy storage system Name of the SAN Copy and SAN Copy/E storage systems in which SAN Copy ports connected to other storage systems reside. A separate entry is displayed for each SAN Copy port connection within each SAN Copy storage system.

Initiator WWN WWN for the SAN Copy ports.

SP-Port The SP (A or B) on which this SAN Copy port resides, and the identifier for the SAN Copy port.

Fibre Logged In Current login status for the SAN Copy port to the connected storage system - Yes or No.

Storage System - Storage Group Storage system and Storage Group to which the SAN Copy port has access.



ports to the existing Storage Group. However, if the logical units belong to different Storage Groups, we recommend that you create one or more new Storage Groups, place the logical units in these Storage Groups, and then connect the SAN Copy ports to them. This is the only time we recommend placing the same logical unit in more than one Storage Group.

Some operating systems do not support the same host accessing identical LUNs. Therefore, once the copy session, completes, we recommend that you move any LUN copies to different Storage Groups.

Selecting SAN Copy Storage System Ports1. In the Storage tree, navigate to the storage system that includes

the Storage Group to which you want to connect, and double-click the storage-system icon.

2. Expand the Storage Groups icon, right-click the icon for the Storage Group to which you want to connect, and then click SAN Copy > Connections.

The SAN Copy Connections dialog box opens.

3. In the SAN Copy System list, select the storage system/SP entry that includes the SAN Copy/E storage system port you want to connect to the Storage Group.

Ports to connect lists all available SAN Copy/E ports for the selected SAN Copy/E storage system and SP.

SAN Copy/E displays only those ports on the SAN Copy/E storage system that are in the same zone as the SP ports on the Storage Group’s storage system.

4. Select all the SAN Copy/E ports that you want to connect to the selected Storage Group.

Selecting Connection PathsSelect the connection paths from the selected SAN Copy/E storage system ports to the Storage Group. You can select specific connection paths, or all available connection paths from the SAN Copy/E port.

Connection paths are any paths from the SAN Copy/E storage system port to available SP ports on the Storage Group’s storage system.



◆ To select specific connection paths to the Storage Group:

1. Highlight a SAN Copy/E storage system port and click Advanced to open the SAN Copy Advanced Connections dialog box.

You do not need to select or clear the check box preceding the port entry — simply highlight the entry.

2. In Connections Paths, select one or more connection paths to the Storage Group and click OK to make the connection, close the dialog box and return to the SAN Copy Connections dialog box.

3. Click OK in the SAN Copy Connections dialog box to save your selections and close the dialog box.

◆ To select all connection paths from the SAN Copy/E port to the Storage Group, click OK in the SAN Copy Connections dialog box to save your selections and close the dialog box.

SAN Copy/E places an icon for each connected SAN Copy/E port under the SAN Copy Connections icon that is under the icon for the selected Storage Group.

Figure 2-5 shows a sample Storage Group configuration for SAN Copy/E. The remote storage system (a CX-Series storage system running SAN Copy) includes three Storage Groups labeled SG 1, SG 2 and SG 3. SG 1 and SG 2 provide I/O access to the LUNs from the attached hosts. SG 3 is a SAN Copy Storage Group.

In this example, we start with two copy sessions running concurrently. The LUNs in Storage Group 1 (LUN 1 and LUN 2) are participating in both sessions. source LUN 1 on the SAN Copy/E storage system is copying data to LUN 1 in SG 1, and LUN 2 in SG 1 is copying data to the destination LUN on the SAN Copy system. Since both LUN 1 and LUN 2 belong to the same Storage Group, you can connect the same SAN Copy port directly to this Storage Group and both sessions can use this SAN Copy port.

In the future, you may want to start a third session that copies data from source LUN 2 to LUN 3 using the same SAN Copy/E port. Since LUN 3 is in a different Storage Group, we recommend that you create a new Storage Group (SG 3) for the SAN Copy/E sessions, and place LUN 1, LUN 2 and LUN 3 in this Storage Group. This is the only time we recommend placing the same logical unit in more than one Storage Group.



Some operating systems do not support the same host accessing identical LUNs. Therefore, once SAN Copy/E completes the copy session, we recommend that you move any LUN copies to different Storage Groups.

Figure 2-5 Sample SAN Copy Storage Group Configuration

What Next To prepare the logical units for a copy session, continue to Preparing Logical Units for Copy Sessions on page 3-11.

Server Server

EMC2693

LUN1

LUN2

SG 1

LUN3

LUN4

SG 2

SG 3

Source LUN 3

Source LUN 1

Source LUN 2




Implementing SAN Copy over Extended DistancesSAN Copy/E supports protocols that let you use the IP WAN to send LUN data over extended distances. In order to do this, you need to extend your switch fabric by using Fibre Channel-to-IP converters that allow Fibre Channel devices to communicate over TCP/IP networks.

When using SAN Copy/E over IP, a read operation will be faster than a write operation.

Performance ConsiderationsTo get the best performance when implementing SAN Copy/E over IP, it is important to consider the following performance factors:

◆ Network performance

◆ SAN Copy/E configuration

◆ Data compression

Network PerformanceThe quality of the network is a critical factor in determining SAN Copy/E performance, especially with respect to latency (delay in the network) and bandwidth (frequency of the transferred bits). SAN Copy/E lets you set the link bandwidth for your network configuration (see Specifying a Link Bandwidth Value for Incremental Sessions on page 3-7, or Modifying Properties for Copy Sessions on page 3-21).

SAN Copy/E ConfigurationIn order to address the network performance issues, SAN Copy/E lets you configure the buffers used by SAN Copy/E operations.

Data CompressionData compression allows more data to be sent in the same amount of time, effectively multiplying the effective bandwidth. The amount of data compression depends on many factors, such as data type, compression algorithm of the equipment, and line speed.

Implementing SAN Copy over Extended Distances 2-15


Figure 2-6 shows a sample SAN Copy/E over IP configuration. In this example, LUN data is being transferred over the IP storage network using two FC-IP converters. Depending on the direction of the data transfer, the converter either converts Fibre Channel data to IP data or IP data to Fibre Channel data.

Figure 2-6 Sample SAN Copy/E over IP Configuration

FC-IPConverter

Destination LUN Source LUN

FC-IPConverter

SAN Copy Storage SystemRemote Storage System

Server

IP Network

Server

Switch FabricSwitch Fabric

Converts to FC Data Converts to IP Data



Setting Up and Using SAN Copy/E 3-1

3Invisible Body Tag

This chapter provides a general overview of how to create, start and monitor full and incremental copy sessions. For detailed information on these topics, please refer to the SAN Copy online help.

Major sections in this chapter are

◆ Setting Up SAN Copy/E...................................................................3-2◆ Creating SAN Copy/E Sessions ......................................................3-3◆ Preparing Logical Units for Copy Sessions.................................. 3-11◆ Starting SAN Copy/E Sessions......................................................3-14◆ Remounting the Source and Destination Logical Units .............3-17◆ Using SAN Copy/E to Manage Sessions .....................................3-19◆ Modifying Properties for Copy Sessions ......................................3-21◆ Viewing Copy Session Status .........................................................3-24◆ Monitoring and Responding to SAN Copy/E Events................3-27

Setting Up and UsingSAN Copy/E


Setting Up and Using SAN Copy/E

Setting Up SAN Copy/EBefore you start a copy session, complete the following:

◆ Determine the SAN Copy/E configuration that you need, and make sure you have met all the requirements. See Chapter 2, SAN Copy/E Configuration Guidelines.

◆ Determine if you need to create full or incremental copy sessions.

If you are creating incremental copy sessions, be sure to configure the reserved LUN pool (for details, see the Navisphere Manager Administrator’s Guide or the online help).

◆ Determine the logical unit from which you want to copy data (source logical unit), and the logical units to which you want to copy the data (destination logical units).

The source logical unit must reside in the SAN Copy/E storage system. For full sessions, it can be a SnapView snapshot. This lets I/O continue to the source logical units for the snapshot during the copy process. In this case, the destination logical unit will not be a duplicate copy of the source storage; it will be a "point-in-time" copy.

If you are creating incremental copy sessions, you cannot use a SnapView snapshot or a virtual disk on an AX-Series storage system running Navisphere Express as the source logical unit.

For information on using the EMC SnapView feature, refer to Navisphere Manager’s online help, or the EMC SnapView for EMC Navisphere 6.X Administrator’s Guide, 069001180.

◆ Create full or incremental copy sessions (see the section, Creating SAN Copy/E Sessions on page 3-3).

◆ Set the environmental properties for all copy sessions that will run on a specific storage system (see Modifying Properties for Copy Sessions on page 3-21).

◆ Verify and modify copy session properties (see the sections, Using SAN Copy/E to Manage Sessions on page 3-19, and Viewing Copy Session Status on page 3-24).

Creating SAN Copy/E Sessions 3-3


Creating SAN Copy/E Sessions You can use the SAN Copy wizard or a LUN’s right-click menu option to create full or incremental copy sessions. The wizard lets you create multiple copy sessions at the same time, while the right-click menu option lets you create a single session using the selected LUN as the source logical unit for the session.

For full copy sessions, you can use a SnapView snapshot as the source logical unit. For incremental sessions, you cannot use a SnapView snapshot as a source logical unit.

The storage system on which you create the session must be a SAN Copy/E storage system. Once you create the session, SAN Copy/E displays an icon for that session in the Storage tree.

Creating a session does not start a session.

SAN Copy/E limits the number of sessions you can create and run concurrently based on storage system type

To create a session, select the SAN Copy/E storage system and the source logical units from which SAN Copy/E copies the data. Then, select the remote storage system and the destination logical units to which SAN Copy/E copies the source data. The wizard also lets you define the session name and session throttle value (a setting that controls the I/O rate for an active copy session), and for incremental copy sessions, it lets you specify the link bandwidth for the sessions.

You cannot change a session name once it is assigned.

Storage -System Type Maximum Sessions Maximum Concurrent Sessions

CX300 full - 300; incremental - 25 4 (2 per SP)

AX-Series (dual SP) full - 100; incremental - 10 2 (1 per SP)

AX-Series (single SP) full - 100; incremental - 10 2 per storage system



Creating Sessions Using the WizardThe following sections describe how to start the SAN Copy wizard and then use the wizard to create copy sessions.

Starting the SAN Copy WizardTo start the wizard, do the following:

1. Log in to the computer that has the required version of Microsoft Internet Explorer or Netscape browser and Java Runtime Environment (JRE).

2. Start the browser and then, in the browser, enter the IP address of an SP or Windows portal that has the SAN Copy/E UI installed.

3. Enter your username and password.

4. In the Enterprise Storage window, right-click the storage system on which you want to create the session (this storage system must have the SAN Copy/E software installed), click SAN Copy, and then click Create Session.

5. Read the wizard summary, and click Next.

Selecting Session TypeThe Select Session Type wizard screen lets you select the session type for all sessions being created at this time - full or incremental. The first time you start incremental sessions created with the wizard, SAN Copy/E performs a full copy of the source logical unit to the destination logical units. Subsequent copy sessions will copy only the changes since the end of the last incremental session. If you want to create an incremental session that does not require an initial full copy, use the source LUN’s right-click menu option to create the session (see Creating a Session Using a LUN’s Right-Click Menu Option on page 3-9).



Selecting Source StorageThe Select Storage Sources wizard screen lets you select the storage system and any source logical units from which you want to copy data.

To create a full copy session SAN Copy/E can use a snapshot as its source logical unit. This allows I/O to continue to the source logical unit for the snapshot during the copy process. For more details, refer to the SnapView or online help.

For incremental copy sessions, you cannot use a SnapView snapshot as the source logical unit.

For full or incremental copy sessions, you cannot use hot spares and private LUNs as source logical units.

1. From the Storage Source list, select the SAN Copy/E storage system (this is the only selection available). .

The Select Storage for Move list displays all the available source logical units (in and out of Storage Groups) on the SAN Copy/E storage system. For full sessions, the source logical unit can be a SnapView snapshot, but not a SnapView clone.

Note For incremental sessions, the source logical unit cannot be a SnapView snapshot.

2. In Select Storage Source for Move, select the logical units from which you want to copy data.

If you select more than one source logical unit, SAN Copy/E creates a session for each source logical unit.

For incremental copy sessions, you cannot select a source logical unit using its World Wide Name since the source logical unit must reside on the SAN Copy/E storage system.

If the source storage is connected to a VMware ESX Server, the source logical unit must be configured as a raw device mapping volume set to physical compatibility mode. If you will be using logical volumes that are not already configured as raw device mapping volumes, use the VMware vmkfstools utility to reconfigure them. For information on using this utility, refer to the Managing Raw Device Mappings - Utilities section found at http://www.vmware.com/pdf/esx25_rawdevicemapping.pdf

3. Click Next to open the Select Storage Destination for Storage Sources window.




Selecting Destination StorageThis screen lets you select the destination storage to which you want to copy the source data. When the window first opens, it displays a Storage icon and an icon for each source logical unit that you selected in the previous window. Each source logical unit represents one copy session. Once you select any destination storage, the software displays an icon for each destination logical unit under the icon for the associated source logical unit. You can expand the icon for any source logical unit to view a list of associated destination logical units, or you can collapse the icon to see only the source logical units.

The destination logical units must reside on a CX-Series storage system running SAN Copy.

If the destination storage is connected to a VMware ESX Server, the destination logical units must be configured as raw device mapping volumes set to physical compatibility mode. If you will be using logical volumes that are not already configured as raw device mapping volumes, use the VMware vmkfstools utility to reconfigure them. For information on using this utility, refer to the Managing Raw Device Mappings - Utilities section found at http://www.vmware.com/pdf/esx25_rawdevicemapping.pdf

To select destination logical units, do the following:

In the Select Storage Destination for Storage Sources window, right click the icon for a source logical unit, and then click Select Destination Storage to open the Select Destination Storage dialog box.

1. In Destination Storage, select a storage system in which the destination logical units reside. The Destination Storage list displays CX-Series storage systems running SAN Copy.

2. Once you select a storage system, Available Storage lists all logical units (in or out of Storage Groups that are not private LUNs) in the remote storage systems that have the same or greater user capacity as the source logical unit.

3. From Available Storage, select the logical units that you want to use as destination storage, and click the right arrow to move them into Selected Storage.




4. Once you have selected all the destination logical units you want to use, click OK to close the Select Destination Storage dialog box.

SAN Copy/E places an icon for each destination logical unit beneath the associated source logical unit.

5. To verify that at least one SAN Copy/E storage system port has access to the source and destination logical units you selected for this session, highlight the source or any destination logical units, and click Verify Connections.

SAN Copy/E displays an error message listing any inaccessible logical units.

6. Click Next to open the Session Names window.

Specifying a Link Bandwidth Value for Incremental Sessions

The Link Utilization wizard screen is visible only for incremental copy sessions. Link bandwidth applies to sessions using either FC or IP network configurations.

You can use the entire bandwidth of your network connection for copy sessions, or you can specify only a portion of it. The minimum allowable value is .016 Mbps and the maximum value is 2048 Mbps.

For optimal performance, select the bandwidth value that matches the bandwidth of the slowest connection to any logical unit participating in the copy session. Selecting a bandwidth higher than this will waste copy buffer space (memory used for temporary data storage). Selecting a bandwidth lower than this will cause SAN Copy/E to perform slower than necessary.

Editing Session Properties Use this wizard window to edit the name (full sessions only), and throttle value for the session you are creating.



The throttle value controls the I/O rate for an active copy session. You can set the session throttle to a value between 1 and 10 where 1 is the lowest I/O rate and 10 is the highest. The default throttle value setting is 6.

A session name cannot exceed 64 characters. The default session name is a combination of the volume name and storage ID. For each incremental copy session, SAN Copy/E creates a corresponding reserved session.The name assigned to the reserved session consists of the session name prepended with the text "SANCopy_" This text is included in the 64-character limit. For example, if a copy session has the name june_update, the name of the corresponding reserved session is SANCopy_june_update.

You cannot change the name of an incremental session.

1. In the Session Names list, select the session whose properties you want to change.

2. Click Edit to open the Edit Session dialog box.

3. Enter a new name and throttle value, and then click Next to open the Summary window.

Verifying Session PropertiesThe Summary window provides a summary of each copy session that you want to create.

1. Verify the properties for the new sessions.

2. If you want to change any of the session information, click Back until you reach the wizard window that lets you change the session property.

3. If the session summary is accurate, click Finish to create the sessions.

SAN Copy/E places an icon for any new sessions in the Storage tree. To view any new sessions, do the following:

a. In the Storage tree, expand the icon for the SAN Copy/E storage system.

b. Expand the SAN Copy Sessions icon, and then expand the icon for the SP that owns the session.

c. Depending on the type of session you created, expand either the Full Sessions or Incremental Sessions icon.

d. Right-click the icon for the session whose properties you want to display and click Properties.



What Next Continue to the section, Preparing Logical Units for Copy Sessions on page 3-11.

Creating a Session Using a LUN’s Right-Click Menu Option

This section describes how to create a single session using the selected LUN, or snapshot as the source logical unit for the session. Creating a session does not start the session.

The LUN or snapshot must reside in a SAN Copy/E storage system.

1. In the Storage tree, navigate to the logical unit for which you want to create a session.

2. Right-click the icon for the logical unit and click SAN Copy > Create Session From LUN to open the Create Session From LUN dialog box.

This dialog box displays the default name for the session and information about the selected source storage.

3. In Session Type, select the type of session you want to create - Full or Incremental.

If you select Incremental as the session type, Link Bandwidth and Initial Sync Required become visible (by default, the Initial Sync Required check box is enabled). If the source LUN and destination LUNs are synchronized, clear this check box. When you start the session, SAN Copy will copy only the changes that have occurred to the source LUN since the session was created. If the source LUN and destination LUNs are not synchronized (or you are unsure of the copy state), leave the check box selected. When you start the session, SAN Copy/E will copy the entire source LUN to the destination LUNs. Any subsequent sessions will copy only the changes.

4. Click Select Destination Storage to open the Select Destination Storage dialog box.

5. In Storage Destination, select a CX-Series storage system running SAN Copy. To verify that at least one SAN Copy/E storage system port has access to the source and destination logical units you selected for this session, highlight the source or any destination logical units, and click Verify Connections.



You can highlight and verify connections for the source logical unit alone, any or all destination logical units, or a combination of source and destination logical units. If not all logical units are accessible, SAN Copy/E displays an error message describing which logical units are not accessible.

6. If needed, change the session throttle value.

For incremental sessions, you can specify the link bandwidth and latency for this session. For optimal performance, select the bandwidth value that matches the bandwidth of the slowest connection to any logical unit participating in the copy session. Selecting a bandwidth higher than this will waste copy buffer space (memory used for temporary data storage); selecting a bandwidth lower than this will cause SAN Copy/E to perform slower than necessary. If you create and start incremental sessions, and the copy is performed over a link that is slower than Fibre Channel, SAN Copy/E uses the link bandwidth and latency values to calculate the optimum buffer space (memory used for temporary data storage) for the session.

7. Click OK to create the session and close the dialog box.

What Next Continue to the next section, Preparing Logical Units for Copy Sessions.

Preparing Logical Units for Copy Sessions 3-11


Preparing Logical Units for Copy SessionsBefore you start a full or incremental copy session, you must prepare the source and destination logical units that will be participating in the session. For a copy session with logical units connected to a Windows server, use the admhost utility. For all other types of servers, use the command specific to the server’s operating system.

Use the following procedures to prepare source and destination logical units for full sessions and incremental sessions.

Also use these procedures prior to manually marking an incremental copy session (for more details on marking a session, see Manually Marking and Unmarking an Incremental Session on page 3-16).

Preparing Source and Destination Logical Units for Full and Incremental Sessions

CAUTION!You must follow this procedure explicitly to avoid data loss or data corruption.

1. For full copy sessions, you must stop all I/O to the source and destination logical units before starting the copy session.

For incremental copy sessions, we strongly recommend that you stop all I/O to the source logical unit, and flush any server buffers prior to starting/marking the session. Once you receive confirmation that the mark or start session operation was successful, you can resume I/O to the source LUN.

If you do not stop all I/O and flush the server buffers to the source logical unit, the resultant data copy will be crash consistent. This means that the contents of the copy will be similar to the contents left on a logical unit if the server crashes. You may be required to use the fsck or a similar utility to make the data copy mountable. In this situation, the data copy may not contain the unflushed server data.



2. From the server connected to the source logical unit, flush the server buffers and disconnect the source logical units from the server by doing one of the following:

If you want to maintain read access to the source logical unit, skip step 2, and proceed to step 3.

• On a Windows Server 2003 or Windows 2000 host, use the following command to flush the host buffers and write the data to disk:

admhost lun_flush -o source-drive letter

For example, to flush the host buffers on drive F:, enter the following command:

admhost lun_flush -o F:

• On a Windows Server 2003, or Windows 2000 host, use the following command to take the disk offline:

admhost lun_deactivate -o source-drive letter

For example, to take drive F: offline, enter the following command:

admhost lun_deactivate -o F:

• On a UNIX® server, use the unmount command to unmount the file system on any source logical units.

• On a NetWare® server, use the dismount command to dismount the file system on any source logical units.

3. If you want to maintain read access to the source logical unit, do one of the following:

CAUTION!Neither of the following steps prevents write access to the source logical unit. You must quiesce all writes to the source logical unit prior to starting and during a copy session in order to prevent data loss or data corruption. If you need to keep writing to a source logical unit, use a SnapView snapshot as the source logical unit.

• On a Windows 2000 or Windows NT host, use the following command:

admhost flush -o source-drive letter

Preparing Logical Units for Copy Sessions 3-13


For example, to flush the host buffers and maintain read access to logical units on drive D:, enter the following command:

admhost flush -o D:

• On a UNIX host, unmount and then mount the source logical unit.

4. From the servers connected to any destination logical units, flush the host buffers and disconnect the logical units from the server by doing one of the following:

If the destination logical units are not mounted, ignore this step.

• On a Windows Server 2003, or Windows 2000 host, use the following command to flush the host buffers and write the data to disk:

admhost lun_flush -o destination drive letter

For example, to flush the host buffers on drive F:, enter the following command:

admhost lun_flush -o F:

• On a Windows Server 2003, or Windows 2000 host, use the following command to take the disk offline:

admhost lun_deactivate -o destination-drive letter

For example, to take drive F: offline, enter the following command:

admhost lun_deactivate -o F:

• On a UNIX® server, use the unmount command to unmount the file system on any destination logical units.

• On a NetWare® server, use the dismount command to dismount the file system on any destination logical units.

What Next ◆ To start full sessions, go the section, Starting Full Copy Sessions on page 3-15.

◆ To start incremental sessions, go the section, Starting Incremental Copy Sessions on page 3-15.



Starting SAN Copy/E SessionsBefore starting a full or incremental session, make sure that you have properly prepared the logical units for the copy session (see Preparing Source and Destination Logical Units for Full and Incremental Sessions on page 3-11).

Before starting an incremental copy session, the session must be marked. You can do this yourself or the session will be marked when you start it. (For more details see Starting Incremental Copy Sessions on page 3-15).

SAN Copy/E limits the number of sessions that you can create and run concurrently on the storage system based on storage system type.

If the number of sessions that you start exceeds the maximum number of active sessions allowed for that storage system, SAN Copy/E places all sessions that exceed the limit into a queue with a status of Queued. Whenever an active session completes, SAN Copy changes the status of a Queued session to Active.

For example, if you create and start six sessions on a CX300 storage system, SAN Copy places two of these sessions in queue since the maximum number of active sessions for a CX300 is four. As soon as one of the active sessions completes, SAN Copy/E starts one of the queued sessions.

What’s Next ◆ To start full sessions, continue to the next section, Starting Full Copy Sessions.

◆ To start incremental sessions, go to the section Starting Incremental Copy Sessions on page 3-15.

Storage-System Type Maximum No. of Sessions

CX300 4 (2 per SP)

AX-Series (dual SP) 2 (1 per SP)

AX-Series (single SP) 2 per stoage system

Starting SAN Copy/E Sessions 3-15


Starting Full Copy SessionsTo start a new session, restart one that has completed or one that has stopped due to a fault or because someone clicked the Stop button, do the following:

1. In the Storage tree, navigate to the icon for the session you want to start.

If you are using a snapshot as the source logical unit for this session, the snapshot must be active before you start the session. Otherwise, the session will fail.

2. Right-click the session icon, and then click Start.

3. SAN Copy/E asks you to confirm the start of the session, and when you click OK, the copy session begins.

You can also use the SAN Copy Status dialog box to start a copy session.

Starting Incremental Copy Sessions

The first time you start incremental copy sessions created with the wizard, SAN Copy/E performs a full copy of the source logical unit to the destination logical units. Subsequent copy sessions will copy only the changes since the end of the last incremental session.

Before starting an incremental copy session, the session must be marked. You can let SAN Copy/E auto mark and start the session, or you can mark the session yourself without necessarily starting it.

Once the session is marked, if any new I/O to the source LUN overwrites the marked data, a copy of that marked data is transferred to a reserved LUN in the reserved LUN pool. This is called a copy-on-first- write operation. Copy-on-first-write occurs from the time the session is marked and continues for the duration of the session. When you start an incremental session, SAN Copy copies all changes made to the source LUN, up to the time of the mark, to the destination logical units. Changes made to the source LUN after the mark operation are not copied to the destination LUN until the next copy session. For example, if you manually mark an incremental session at 1:00 P.M., and then start the session at 3:00 P.M., any



changes made to the LUN between 1:00 P.M. and 3:00 P.M. are not included in the session started at 3:00 P.M.

EMC recommends that you let SAN Copy/E mark the session when you start the session, in order to reduce the risk of running out of reserved LUN pool space. If you want to manually mark the session, see Manually Marking and Unmarking an Incremental Session on page 3-16.

For more information on configuring the reserved LUN pool, refer to the Setting Up and Using the Reserved LUN Pool chapter in the EMC Navisphere Manager Administrator’s Guide.

Starting an Incremental SessionTo start a new session, restart one that has completed or one that has stopped due to a fault or because someone clicked the Stop button, do the following:

1. In the Storage tree, navigate to the icon for the session you want to start.

2. Right-click the session icon, and then click Start.

3. SAN Copy/E asks you to confirm the start of the session, and when you click OK, the copy session begins.

You can also use the SAN Copy Status dialog box to start an incremental SAN Copy session.

Manually Marking and Unmarking an Incremental Session

Before marking an incremental copy session, be sure to properly prepare the participating logical units (see Preparing Source and Destination Logical Units for Full and Incremental Sessions on page 3-11).

You may want to manually mark a session, for example, if you want to capture a specific image of your data, but you want to start the session at a later time, when there will be less impact on performance.

When you manually mark a session, you begin the copy-on-first-write operation. Be sure that the reserved LUN pool has enough space. (For more details, refer to the EMC Navisphere Manager Administrator’s Guide).

Remounting the Source and Destination Logical Units 3-17


You may also want to remove the mark from a previously marked session in order to stop the copy-on-first write operation, and to free up reserved LUN pool space.

◆ To mark a session, do the following:

In the Storage tree, from SAN Copy Sessions > SP A (SP B) > Incremental Sessions, right-click the session that you want to mark, and click Mark.

◆ To unmark a session, do the following:

In the Storage tree, from SAN Copy Sessions > SPA (SPB) > Incremental Sessions, right-click the session that you want to unmark, and click Unmark.

Remounting the Source and Destination Logical UnitsOnce the copy session is complete, remount the source and destination logical units.

The SAN Copy/E software does not track changes made to the destination LUN between incremental updates (that is, host writes). In order to ensure data consistency between the source logical unit and the destination logical units, we strongly recommend that you do not perform any host writes to the destination logical units.

If you have SnapView software installed on the remote host, we recommend that you create either a SnapView snapshot or BCV (clone) of the destination logical units and mount these to the remote host. This will prevent host writes to the destination logical units and maintain data consistency between logical units.

If you do not have SnapView software installed, and you perform host writes to the destination logical unit, you must perform a full copy session of the data on the source logical unit to the destination logical units in order to maintain data consistency between logical units.

To mount the source and destination logical units, do the following:

◆ On a Windows 2000 or Windows NT host, use the following command:

admhost lun_activate -l source/destination WWN -d driveletter



For example, to activate a source LUN with the following WWN (World Wide Name) that resides on drive V:, enter the following command:

admhost lun_activate -l 60:06:01:EF:74:60:00:00:CD:BD:FE:45:77:9D:D7:11 -d V:

◆ On UNIX® hosts, use the commands your operating system normally uses to discover new logical units.

◆ On Novell NetWare® hosts, run the command list devices or use the command scan all LUNs on the console.

Some operating systems do not support access by the same host to identical LUNs. Therefore, once SAN Copy/E completes the copy session, we recommend that you move any LUN copies to different Storage Groups.

What Next ◆ Use the SAN Copy session right-click menu options to manage the sessions (refer to the table Right-Click Menu Options for Managing Sessions on page 3-19).

◆ Edit session properties (see Modifying Properties for Copy Sessions on page 3-21).

◆ View session status (see Viewing Copy Session Status on page 3-24).

Using SAN Copy/E to Manage Sessions 3-19


Using SAN Copy/E to Manage Sessions

The Duplicate option is not available for incremental copy sessions.

After you create your copy sessions, use the session’s right-click menu options to start and manage the session, and view its status and properties. Table 3-1 lists and describes the available right-click menu options.

The information in Table 3-1 assumes that Checkpoint Interval is enabled. See Modifying Properties for Copy Sessions on page 3-21.

For more detailed information on managing copy sessions, refer to the SAN Copy online help.

Table 3-1 Right-Click Menu Options for Managing Sessions

Right-Click Option Use to Results

Start Start a new session; restart one that has completed or one that has stopped due to a fault or because someone clicked the Stop button. See Starting SAN Copy/E Sessions on page 3-14.

When you use Start to restart a session, the session starts at block 0, not from the checkpoint, or the block where the session stopped.

Stop Stop or cancel a session that is active, queued or paused.

The session is cancelled, but you can restart the session using Start or Resume.• Start restarts the session at block 0.• Resume restarts the session from the last

checkpoint.

Pause Pause a session that is active or queued. Use Resume to restart the session from where it was paused.

Resume Restart a session that is paused or stopped (with the Stop button or due to a fault).

• Resume restarts a paused session from where it was paused.

• Resume restarts a session that was stopped with the Stop button or due to a fault from the last checkpoint.

Status Display the status of a selected session (see Viewing Copy Session Status on page 3-24).

Lets you view the progress of a session and, depending on the session status, lets you start, pause, resume or stop the session.

Remove Remove the selected session. You must stop the session in order to remove it.

SAN Copy/E removes the icon for the session from the Storage tree.



Right-Click Option Use to Results

Duplicate(full sessions only)

Create a duplicate copy of the selected session. You must stop a session in order to duplicate it.

The duplicate session is given a unique identifier and name. Use the SAN Copy Session Properties dialog box to assign a new name, modify any session properties, and to assign new source and destination storage.

Transfer SP Owner Transfer ownership of the selected session from one SP to the peer SP. For example, transfer a session if the SP that owns the session fails, or, if due to I/O demand on the current owner SP, the peer SP is better able to handle the session.

SAN Copy/E transfers ownership of the session to the peer SP and, in the Storage tree, moves the session icon to the peer SP.The logical units associated with the transferred session do NOT automatically fail over to the peer SP. You must manually trespass them.

Properties View and modify the properties of the selected session. This is especially useful after you create a duplicate of a session and you want to modify the name or change the source or destination storage of the duplicate session (see Modifying Properties for Copy Sessions on page 3-21).

SAN Copy/E changes the properties of an existing session.

Mark(Incremental copy sessions only)

Create a point-in-time copy of the data you want to copy. Do this by designating an end point, on the incremental session, to the body of data that will be copied when you start the session. See Manually Marking and Unmarking an Incremental Session on page 3-16.

If any new I/O to the source LUN overwrites any of the marked data, the software performs a copy-on- first-write of the old data to a reserved LUN in the reserved LUN pool. The session copies the old data from the reserved LUN and the unchanged data on the source LUN.

Unmark(Incremental copy sessions only)

Remove the existing mark in preparation for inserting a new mark. The new mark will create a new point-in-time copy of changes to the source logical unit. See Manually Marking and Unmarking an Incremental Session on page 3-16.

SAN Copy/E removes the previous mark. The point-in-time copy created with the previous mark is lost.

Table 3-1 Right-Click Menu Options for Managing Sessions (continued)

Modifying Properties for Copy Sessions 3-21


Modifying Properties for Copy SessionsSAN Copy/E lets you modify the environmental properties for all sessions on a storage system, or for a specific session.

Editing the Environmental Properties for All Sessions on a Storage System

EMC recommends that you use the default values for Checkpoint Interval, Number of Concurrent Sessions, Number of Buffers per Session, and Buffer Size. As the default, Checkpoint Interval is enabled and set to 10 minutes; Number of Concurrent Sessions varies per storage system type; Number of Buffers per Session defaults to 4, and Buffer Size defaults to 1024 blocks.

SAN Copy/E lets you edit the environmental properties for all copy sessions residing on a selected storage system. These properties include the checkpoint interval for each session running on the storage system and the number of sessions that can concurrently run on a storage system. You can set different values for each SP in the storage system or apply the same values to both SPs. The storage system for which you set session properties must be a SAN Copy/E storage system.

When you enable and set the checkpoint interval and then start a copy session, SAN Copy/E records, in permanent storage, the total number of blocks copied at the end of each checkpoint. This lets a session resume from the last checkpoint, rather than having to start over.

The number of sessions that can run concurrently on a storage system is based on the storage-system type.

To set the number of concurrent sessions allowed per SP and to change the checkpoint interval for any sessions running on this SP, do the following:

Storage -System Type Maximum No. of Sessions

CX300 4 (2 per SP)

AX-Series (dual SP) 2 (1 per SP)

AX-Series (single SP) 2 per storage system



1. In the Enterprise Storage tree, right-click the icon for a SAN Copy/E storage system, click SAN Copy and then Settings to open the SAN Copy Settings dialog box.

2. To set the same values for both SPs on the storage system:

a. Select Set Same Settings on SP B as SP A.

b. Under SP A, select a value for Number of Concurrent Sessions, Checkpoint Interval, Number of Buffers per Session, and Buffer Size, or accept the default values.

3. To set different values for each SP on the storage system:

a. Clear Set Same Settings on SP B as SP A.

b. Under SP A, select a value for Number of Concurrent Sessions, and then enable and select a value for Checkpoint Interval.

c. Repeat the previous step for SP B.

4. Click OK to save your changes and close the dialog box.

Editing a Single Copy Session’s PropertiesYou can edit the properties for a specific copy session. This is especially useful when you create a duplicate of an existing session and you want to change the properties of the new session. You can change the following session properties:

◆ Session name (full sessions only)

◆ Session Type - Full or Incremental

◆ Sync Copy Required - (visible only for incremental session type) Default state is enabled. Leave the check box selected if the source and destination storage are not synchronized and you want to perform a full copy. Clear the check box if the source and destination storage are synchronized and you want only to copy changes to the source storage that have occurred since the last copy session.

◆ Source Storage (full sessions only)

◆ Destination Storage

◆ Session Throttle (You can also change the throttle value for an active session. See Changing the Throttle Value for an Active Session on page 3-23.)

◆ SP that owns the session

Modifying Properties for Copy Sessions 3-23


◆ Link Bandwidth (incremental sessions only)

◆ Link Latency (incremental sessions only)

Refer to the online help for detailed descriptions of the dialog box properties.

1. In the Storage tree, navigate to the storage system on which the copy session resides.

2. Expand the storage-system icon, the SAN Copy Sessions icon, and the SP icon that owns the session.

3. Right-click the icon for the session whose status you want to display, and click Properties to open the SAN Copy Session Properties dialog box.

4. Modify any of the available session properties.

5. To verify that at least one SAN Copy/E storage system port has access to the source and destination logical units you selected for this session, highlight the source or any destination logical units, and click Verify Connections.

You can highlight and verify connections for the source logical unit alone, any or all destination logical units, or a combination of source and destination logical units. If not all logical units are accessible, SAN Copy/E displays an error message describing which logical units are not accessible.

6. Click OK to save your changes and close the dialog box.

Changing the Throttle Value for an Active SessionSAN Copy/E also lets you change the throttle value for an active session. For example, you may want to decrease the throttle value of a particular session if the session is consuming too much SP processing power.

The new throttle value applies only while the session is active. Once the session completes, the throttle value returns to its previous value.

1. Right-click the icon for the session whose throttle value you want to change, and click Status to open the SAN Copy Status dialog box.

2. In Change Active Session Throttle, enter a new throttle value.

3. Click OK to save the changes and close the dialog box.



Viewing Copy Session StatusSAN Copy/E lets you view the status of a single copy session, or all sessions on a selected storage system.

To View Status of a Single SessionTo view the status of a single copy session, do the following:

1. In the Storage tree, navigate to the storage system on which the copy session resides.

2. Expand the storage-system icon, the SAN Copy Sessions icon, and the SP sessions icon that owns the session.

3. Right-click the icon for the session whose status you want to display, and click Status to open the SAN Copy Session Status dialog box.

4. In the Copy tab, view the current status of the selected session, and perform a variety of actions on the session, such as Start Pause, Resume and Stop the session.

5. In the Mark tab (visible for incremental sessions only), view a summary of the selected incremental session’s settings, such as blocks to be copied and time marked.

6. In the Source tab, view the status of the source logical unit participating in the selected session.

7. In the Destination tab, view the status for all destination logical units participating in the selected session.

8. Session Progress displays the current progress of the selected session.

Viewing Copy Session Status 3-25


To View Status of All Sessions on a Storage SystemTo view the status of all copy sessions on a storage system, in the Enterprise Storage tree, right-click the icon for a SAN Copy storage system. Then click SAN Copy > Session Summary to open the SAN Copy Summary dialog box.

This dialog box displays the status for all copy sessions (full and incremental) on the selected storage system using the following format.

Heading Description

Name User-entered session name.

Type Type of copy session - Full or Incremental.

Identifier Session identifier.

Status Current state of the session.

Not Started The session was created but not started.

Active The session is running.

Partially Active A session with multiple destination logical units, and one of the destination LUNs participating in the session fails. The copy session continues to the non-failed destination logical units

Queued The session was created and started, but the maximum number of concurrent sessions allowed for that storage system has already been reached. A queued session will become Active when an already active session completes.

Completed The session completed successfully.

Paused The session was temporarily halted (can apply to an active or queued session).

Partially Paused In a session with multiple destination logical units, one of the destination logical units participating in the session fails. When you pause the session, SAN Copy pauses the copy process only to the non-failed logical units.



Heading Description

Failed The session did not complete successfully.

Partially Failed In a session with multiple destination logical units, one of the destination logical units participating in the session fails. When this session completes, SAN Copy/E displays the partially failed status.

Aborted The session was manually stopped, using the Stop button (a fault did not cause the session to stop).

Halted on Reboot The SP on which a session is running was rebooted.

Bad Block Failure Session failed due to bad block on source logical unit.

Auto Recovery in Progress SAN Copy/E is trying to resume failed sessions. If an SP fails, causing copy sessions to fail, and you reboot the SAN Copy storage system, SAN Copy/E tries to automatically resume any failed sessions caused by the SP failure. SAN Copy/E tries to resume the session once every 3 minutes, up to a maximum of five times.

Initial Copy Required (incremental copy sessions only)

When this session is started, the entire contents of the source logical unit will be copied to all destination logical units.

Percentage Percentage of the session that is completed.

SP Owner SP that owns the session.

Monitoring and Responding to SAN Copy/E Events 3-27


Monitoring and Responding to SAN Copy/E EventsUse the Event Monitor to monitor events specific to SAN Copy/E. The Event Monitor is an enterprise tool that supports centralized or distributed monitoring of storage systems in a heterogeneous environment. The Event Monitor software consists of two distinct parts: the Event Monitor User Interface (UI), and the Event Monitor.

The Event Monitor User Interface (UI) is part of Navisphere Manager and runs on the web browser. The user interface provides you with an intuitive tool to set up responses for events and to choose which storage systems to observe. The user interface lets you customize a configuration to use any of the supported notification methods. It can be easily configured to e-mail, page, or send an SNMP trap to an industry-standard event-management tool. The user interface need only be used when setting up configurations or viewing the Event History log.

Event Monitor resides on both the Navisphere SP Agent and Host Agent, and is available on many operating systems. Once configured, the Event Monitor runs continuously as a service or daemon, observing the state of all specified storage systems and notifying you when selected events occur.

You can configure Navisphere Manager to send an event notification when the reserved LUN pool becomes 50, 75, 80, 85, 90, or 95 percent full. The application will generate the following warning event code and description when each of the reserved LUN pool capacities is reached:

To configure Event Monitor for SAN Copy/E, refer to the online help Table of Contents entry, Monitoring and responding to events, or Chapter 5 in the EMC Navisphere Manager Administrator's Guide.

Event Code Description

0x71004000 The reserved LUNs assigned to LUN X have become Y% percent full, where X is the source LUN and Y is either 50, 75, 80, 85, 90, or 95.



Handling SAN Copy/E Session Failures A-1

AInvisible Body Tag

This appendix describes recovery strategies for SAN Copy/E session failures.

Topics include

◆ Handling SAN Copy/E Session Failures ......................................A-1

Handling SAN Copy/ESession Failures

A-2 EMC SAN Copy/E for Navisphere Administrator’s Guide

Handling SAN Copy/E Session Failures

Handling Session FailuresThis section describes recovery strategies for session failures that could occur between a CX300 or AX-Series storage system running SAN Copy/E and a CLARiiON CX-Series storage system running SAN Copy.

Unable to Create Copy Sessions

You are unable to create a copy session due to one of the following reasons.

◆ One or more of the destination logical units that you selected for the new copy session fails to meet the requirements for compatibility with SAN Copy/E.

Verify the following:

• The destination LUNs must reside on the CX-Series storage system running SAN Copy.

• The revision of FLARE software running on the remote storage system must be at least 2.19.xxx.x.xxx

• SAN Copy must be enabled on the remote storage system.

◆ The source LUN you selected resides on a remote storage system.

The source LUN must reside on the SAN Copy/E storage system. The source LUN cannot reside on a remote storage system.

◆ The destination LUNs you selected reside on the same storage system as the source LUN.

SAN Copy/E does not support destination LUNs on the same storage system as the source LUN. Choose a destination LUN on a remote CX-Series storage system running SAN Copy.

◆ The full session could not be created because the limit for full sessions has been reached — 300 for CX300 storage systems and 100 for AX-Series storage systems.

SAN Copy/E has a hard limit on the number of full copy sessions that can exist on the storage system at one time. When this limit is reached, no new sessions can be created until one or more of the existing full sessions is removed.

Handling Session Failures A-3


◆ The incremental session could not be created because the limit for incremental sessions has been reached — 25 for CX300 storage systems and 10 for AX-Series storage systems.

SAN Copy/E has a hard limit on the number of incremental copy sessions that can exist on the storage system at one time. When this limit is reached, no new incremental copy sessions can be created until one or more of the existing incremental copy sessions has been removed or modified to a full copy session.

Copy Session Fails

◆ Port and connection path that the SAN Copy/E session is using fails.

1. If other ports and connection paths are available to this session, resume the session using the other paths and ports.

If not, repair the failed path and resume the session.

2. Verify zoning and make sure that the SAN Copy/E storage system has access to the logical units on the remote storage systems.

◆ SP that owns the copy session fails.

1. If the storage system has dual SPs:

a. Transfer the session to the peer SP.

b. Trespass the source logical unit to the peer SP.

c. Verify that ports and connection paths are available from the peer SP to the remote storage systems.

d. Resume the session.

2. If no ports or connection paths exist, establish connectivity from the peer SP to the remote storage system, and resume the session.

3. If the storage system's only SP has failed, the SP must be restored before the sessions can continue.

◆ The source LUN in a copy session fails.

• If the source LUN is not owned by the SP that owns the SAN copy session, you must trespass the LUN to the SP owning the session.



• If the source logical unit failed for any other reason, it must be repaired before the SAN Copy/E session can continue.

◆ SP that owns the only destination LUN in the session fails.

1. Trespass the destination logical unit to the peer SP on the remote system.

2. Verify that ports and connection paths are available from the SAN Copy/E storage system to the peer SP on the remote system.

3. Resume the session.

◆ One or more destination logical units in a session fails.

The session will continue copying to the remaining non-failed destination logical units. These destination logical units must be on remote storage systems.

• If the destination logical units trespass to the peer SP or become unowned on the remote system, and you want to trespass the logical units back to the original SP:

1. Verify that the host still has access to the logical units.2. If yes, trespass the logical units back to the original SP.3. Resume the session.

• If the destination logical units trespass to the peer SP and you do not want to trespass them back to the original SP:

1. Verify that ports and connection paths are available from the SAN Copy/E storage system to the peer SP on the remote system.

2. Resume the session.• If the destination logical unit fails because the SAN Copy/E

port and connection path that the session is using fails, refer to the case, "Port and connection path that the SAN Copy/E session is using fails.." on page A-3.

• If the destination logical units failed due to any other reason, repair the failed destination logical units, and resume the session.

Handling Session Failures A-5


When the destination logical units fail, the amount of data copied to each one may be different. For example, if two destination logical units fail, the copy process on one logical unit may be 50% complete, but only 20% complete on the other. When you resume this session, SAN Copy/E determines the start point of the copy process based on the logical unit with the least amount of data and begins copying the remaining data to all destination logical units.

To perform a full copy only to the failed destination logical units:

1. Duplicate the session (not supported for incremental sessions).

2. Modify the duplicated session to remove the destination logical units that completed successfully.

3. Start the modified session.



Customer Support B-1

Bnvisible Body Tag

This appendix reviews the EMC process for detecting and resolving software problems, and provides essential questions that you should answer before contacting the EMC Customer Support Center.

This appendix covers the following topics:

◆ Overview of Detecting and Resolving Problems ......................... B-2◆ Troubleshooting the Problem .......................................................... B-3◆ Before Calling the Customer Support Center ............................... B-4◆ Documenting the Problem............................................................... B-5◆ Reporting a New Problem ............................................................... B-6◆ Sending Problem Documentation................................................... B-7

Customer Support

B-2 EMC SAN Copy/E for Navisphere Administrator’s Guide

Customer Support

Overview of Detecting and Resolving ProblemsEMC software products are supported directly by the EMC Customer Support Center in the United States.

EMC uses the following process to resolve customer problems with its software products (Figure B-1).

Figure B-1 Problem Detection and Resolution Process

ProblemDetection

Refer to thisCustomer Support

Appendix for Instructions

Collect ProblemInformation as

Directed

Contact the EMC CustomerSupport Center:

U.S.:Canada:Worldwide:

(800) SVC-4EMC(800) 543-4SVC(508) 497-7901

Confirm that theProblem is Software

Related

Call will be Directedto an EMC SoftwareSupport Engineer

Problem isTracked andManaged toResolution

Troubleshooting the Problem B-3

Customer Support

Troubleshooting the ProblemPlease perform the relevant diagnostic steps before you contact the EMC Customer Support Center:

1. Read the documentation carefully.

2. Reconstruct the events leading up to the problem and describe them in writing.

3. Run some test cases to reproduce the problem.

If you encounter a problem that requires technical programming or analysis, call the nearest EMC office or contact the EMC Customer Support Center at one of the following numbers:

United States: (800) 782-4362 (SVC-4EMC)

Canada: (800) 543-4782 (543-4SVC)

Worldwide: (508) 497-7901

Please do not request a specific support representative unless one has already been assigned to your particular system problem.

For additional information on EMC products and services available to customers and partners, refer to the EMC Powerlink website at:




Customer Support

Before Calling the Customer Support CenterHave the following information available before calling the Customer Support Center or your support representative (if one has been assigned to you):

❑ Your company name

❑ Your name

❑ Your phone number

❑ Your site ID, if known

❑ For an existing problem, the problem tracking system ID, if one was previously assigned to the problem by a support representative

Documenting the Problem B-5

Customer Support

Documenting the ProblemIf the EMC Customer Support Center requests information regarding the problem, please document it completely, making sure to include the following information:

❑ Your company name and address

❑ Your name

❑ Your telephone number

❑ Your site ID

❑ The importance of the problem, so that it can be assigned a priority level

To expedite the processing of your support request, you can photocopy this list and include it with the package.


Customer Support

Reporting a New ProblemFor a new problem, please provide the following information:

❑ Release level of the software that you are running

❑ Software installation parameters

❑ Host type on which you are running

❑ Operating system you are running and its release number

❑ Functions of the software that you are running

❑ Whether you can reproduce the problem

❑ Previous occurrences of the problem

❑ Whether the software has ever worked correctly

❑ Time period that the software did work properly

❑ Conditions under which the software worked properly

❑ Changes to your system between the time the software worked properly and the problem began

❑ Exact sequence of events that led to the system error

❑ Message numbers and complete text of any messages that the system produced

❑ Log file dated near the time the error occurred

❑ Results from tests that you have run

❑ Other related system output

❑ Other information that may help solve the problem

Sending Problem Documentation B-7

Customer Support

Sending Problem DocumentationUse one of the following methods to send documentation of the problem to the EMC Customer Support Center:

◆ E-mail

◆ FTP

◆ U.S. mail to the following address:

EMC Customer Support Center171 South StreetHopkinton, MA 01748-9103

If the problem was assigned a number or a specific support representative, please include that information in the address as well.


Customer Support

EMC SAN Copy/E for Navisphere Administrator’s Guide i-1

AAccess Logix, defined 1-4admhost utility, defined 1-2Agent

Host, defined 1-2managed, defined 1-3SP, defined 1-4

Bbenefits, SAN Copy/E 1-6

CCLARiiON storage system

connecting SAN Copy/E ports to Storage Groups 2-10

preparing for SAN Copy/E session 2-9clone, SnapView, defined 1-2Customer support B-3Customer Support Center B-7

Ddestination logical units

remount after session ends 3-17select for session 3-6

domain, defined 1-2

Eevents, monitoring and responding to 3-27

Ffailures, session, handling A-2features, SAN Copy/E 1-6full sessions

defined 1-2starting 3-15

Iincremental sessions

marking and unmarking 3-16starting 3-15

Llogical unit

defined 1-3remounting after session stops 3-17

LUN pool, reserved, defined 1-3

Mmonitoring SAN Copy/E events 3-27

Oonline help, using 1-8

Pportal, defined 1-3ports, SAN Copy/E, connecting to CLARiiON

Storage Groups 2-10

Index

EMC SAN Copy/E for Navisphere Administrator’s Guidei-2

Index

Rremote storage system, defined 1-3reserved LUN pool, defined 1-3responding to SAN Copy/E events 3-27

SSAN Copy/E

basic configuration requirements and restrictions 2-2

features and benefits 1-6introduction 1-5sessions

active, changing throttle value 3-23checkpoint interval, defined 1-2creating a single session 3-9creating multiple sessions 3-4creating using right-click option 3-9creating using Wizard 3-4defined 1-3full, defined 1-2incremental

marking and unmarking 3-16starting 3-15

modifying properties 3-21preparing CLARiiON storage system for

2-9preparing logical units 3-11starting

full 3-15viewing status for all storage system

sessions 3-25viewing status for single session 3-24

setting upcreating a single session 3-9creating multiple sessions 3-4

setting up overview 3-2software components 1-8software, defined 1-3zoning requirements and recommendations

2-4SAN Copy/E, connecting SAN Copy/E ports to

CLARiiON Storage Groups 2-10shared storage, defined 1-4snapshot, SnapView, defined 1-4

SnapViewclone, defined 1-2snapshot, defined 1-4

software componentscommand line interface 1-8graphical user interface 1-8SAN Copy/E 1-8

source logical unitsdeactivate

UNIX 3-12Windows 3-12

remount after session ends 3-17select for session 3-5

status, sessionviewing all on storage systems 3-25viewing single session 3-24

Storage Groups, connecting SAN Copy/E ports 2-10

storage systemCLARiiON, preparing for SAN Copy/E

session 2-9SAN Copy/E, defined 1-4shared, defined 1-4

TTechnical support B-3throttle value, session

changing for a session 3-22changing for an active session 3-23

Uunshared storage systems, defined 1-4

VVMware Server

destination LUN prerequisites 3-6prerequites for copy sessions 2-2source LUN prerequisites 3-5

i-3EMC SAN Copy/E for Navisphere Administrator’s Guide

Index

WWizard, SAN Copy/E

editing session properties 3-7selecting destination storage 3-6selecting source storage 3-5using to create sessions 3-4verifying session properties 3-8

Zzoning

introduction 2-4recommendations

based on availability 2-7based on performance 2-6based on preserving host HBA

connections 2-8

EMC SAN Copy/E for Navisphere Administrator’s Guidei-4

Index

Documents

EMC SAN Copy/E Administrator's Guide · PDF fileEMC2, EMC, CLARiiON, Navisphere, PowerPath, ... MirrorView, and SnapView are ... 1-2 EMC SAN Copy/E for Navisphere Administrator’s