EMC SAN Copy/E Command Line Interfaces Reference · PDF fileEMC SAN Copy/E Command Line...

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748 -91031-508 -435 -1000www.EMC.com

EMC SAN Copy/ECommand Line Interfaces

REFERENCEP/N 300-002-665

REV A01

www.emc.com

EMC SAN Copy/E Command Line Interfaces Referenceii

Copyright © 2005EMC 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, FLARE, Powerlink, MirrorView, SAN Copy, and SnapView are trademarks of EMC Corporation.

All other trademarks used herein are the property of their respective owners.

EMC SAN Copy/E Command Line Interfaces Reference iii

Chapter 1 About EMC SAN Copy/E SoftwareTerminology...................................................................................... 1-2Introducing SAN Copy/E Software.............................................. 1-5SAN Copy/E Features and Benefits ............................................. 1-6SAN Copy/E Software Components ............................................ 1-8SAN Copy/E Operations Overview ............................................. 1-9

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/E Ports to CLARiiON Storage Groups...................................................................................... 2-10

Implementing SAN Copy/E over Extended Distances ........... 2-13Performance Considerations................................................. 2-13

Chapter 3 Using the admhost Utility with SAN Copy/EAbout admhost for SAN Copy/E ................................................. 3-2Admhost SAN Copy/E Command Functions ............................ 3-3Preparing Logical Units for a SAN Copy/E Session .................. 3-5

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

Contents

EMC SAN Copy/E Command Line Interfaces Referenceiv

Contents

Chapter 4 SAN Copy/E CLI CommandsSAN Copy/E Command Functions.............................................. 4-2About Secure CLI............................................................................. 4-4naviseccli ........................................................................................... 4-5About Classic CLI .......................................................................... 4-10navicli .............................................................................................. 4-10sancopy -create............................................................................... 4-14sancopy -destinfo........................................................................... 4-19sancopy -duplicate......................................................................... 4-23sancopy -info .................................................................................. 4-25sancopy -mark................................................................................ 4-31sancopy -modify ............................................................................ 4-33sancopy -pause............................................................................... 4-38sancopy -remove............................................................................ 4-39sancopy -resume ............................................................................ 4-41sancopy -settings............................................................................ 4-43sancopy -start ................................................................................. 4-46sancopy -stop.................................................................................. 4-48sancopy -throttle ............................................................................ 4-50sancopy -transfer ........................................................................... 4-52sancopy -unmark ........................................................................... 4-54sancopy -updateconnections........................................................ 4-55sancopy -verify............................................................................... 4-56

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 Command Line Interfaces Reference 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 manual describes the two command line interfaces to EMC® SAN Copy™/E software: the admhost utility and the CLI (Command Line Interface).

You should read this manual if you will use typed or scripted commands (instead of or in addition to EMC Navisphere® Manager software) to configure and run the SAN Copy/E software.

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 CLI to set up and manage SAN Copy/E software.

This manual assumes that you are familiar with the operating system running on the servers you will manage and with storage-system components and configurations.

vi EMC SAN Copy/E Command Line Interfaces Reference

Preface

Organization This manual contains four chapters as follows:

Related DocumentationEMC SAN Copy/E for Navisphere Administrator’s Guide (P/N 300-002-664)

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

EMC Navisphere Command Line Interface Reference (P/N 069001038)

Conventions Used in This GuideThis manual uses the following format conventions:

Chapter 1 Introduces terminology and the software products.

Chapter 2 Explains the basic requirements, restrictions and configuration guidelines for using SAN Copy/E.

Chapter 3 Explains admhost commands that the operating system uses to manage devices with SAN Copy/E.

Chapter 4 Describes the CLI commands that SAN Copy/E uses to manage copy sessions.

Appendix A Lists and describes the SAN Copy/E CLI error codes.

Appendix B Describes the EMC process for detecting and resolving software problems.

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.

EMC SAN Copy/E Command Line Interfaces Reference vii

Preface

Finding CurrentInformation

The most up-to-date information about the EMC SAN Copy/E software is posted on the EMC Powerlink™ website. We recommend that you download the latest information before you start the SAN Copy/E 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 Admhost Release Notes

◆ EMC CX-Series SAN Copy/E Release Notes

◆ 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:

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.

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

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

Worldwide: (508) 497-7901

http://powerlink.emc.com

viii EMC SAN Copy/E Command Line Interfaces Reference

Preface

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 Web site 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.

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


mailto:[email protected]

About EMC SAN Copy/E Software 1-1

1Invisible Body Ta

This chapter introduces the EMC® SAN Copy™/E software and its command line utilities: admhost, with commands that the operating system uses to manage SAN Copy/E devices; and the CLI, with commands that manage copy sessions. Major topics 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◆ SAN Copy/E Operations Overview ...............................................1-9

About EMC SANCopy/E Software

1-2 EMC SAN Copy/E Command Line Interfaces Reference

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

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.

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 session that 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 A session that 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).

Terminology 1-3


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

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.

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.

pre-FC4700 systems An FC4500, FC5300, FC5500, FC5700, or C-Series storage system.

remote storage system A storage system with logical units that are participating in a copy session, but does not own the copy session.

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 SAN Copy/E storage systems and other CLARiiON storage systems .

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

SAN Copy/E storage system The CLARiiON storage system that owns the copy session. A SAN Copy/E storage system must be running SAN Copy/E and Access Logix software.

Term Meaning



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.

volume A logical unit on a Symmetrix storage system.

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 system 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/E over Extended Distances on page 2-13). 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 a SAN Copy/E Session on page 3-5). 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 CenterSAN 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 ApplicationSAN 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 takes place on the SAN, the copy process is much faster than the LAN-based, host-involved copy process.

SAN Copy/E Features and Benefits 1-7


Easy-to-Use Web-Based ApplicationSAN 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 SoftwareIf 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 (e.g. from the production server); but does not track server writes to the destination LUN (e.g. 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 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.

SAN Copy/E Operations Overview 1-9


SAN Copy/E Operations OverviewThe following steps explain how to configure and use SAN Copy/E.

1. Set up your SAN Copy/E configuration. This procedure includes the following tasks:

• Zoning switches — see SAN Copy/E Zoning Requirements and Recommendations on page 2-4.

• Registering SAN Copy/E ports — see Preparing a CLARiiON Storage System for a Copy Session on page 2-9.

• Adding logical units to Storage Groups and connecting ports to Storage Groups. — see Preparing a CLARiiON Storage System for a Copy Session on page 2-9.

• Configuring the reserved LUN Pool for incremental copy sessions—see Navisphere Command Line Interface Reference.

2. On the SAN Copy/E storage system, create full or incremental SAN Copy copy descriptors using the sancopy -create or sancopy -create -incremental command (see page 4-14).

3. Prepare the source and destination logical units for a copy session (see Preparing Logical Units for a SAN Copy/E Session on page 3-5).

4. For full sessions, proceed to step 5 to start the session.

For incremental sessions, mark any sessions using the sancopy -mark command (see page 4-31).

Once you receive confirmation that the mark operation was successful, you can make the source logical units available to the host and resume I/O to these logical units. This applies only to source logical units participating in incremental copy sessions.

5. On the production host’s storage system, start the copy sessions using the sancopy -start command (see page 4-46).

More than one session at a time per source logical unit can be active on a host, provided the source and destination logical units are unmounted (see step 3 above).

6. Let the copy session complete.

7. On both hosts, make the source logical unit (if not done previously) and destination logical units available to the operating system.



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

With Windows hosts, issue the admhost lun_activate command. This command rescans the bus for new devices and assigns a drive letter to all CLARiiON logical units which do not already have one. Use the -l and -d options with the admhost lun_activate command to assign a drive letter to a LUN with a specific world wide name (WWN).

What Next? Depending on your needs, go to one of the following chapters:

◆ To learn about admhost commands — Chapter 3

◆ To learn about SAN Copy/E CLI commands — Chapter 4.

SAN Copy/E Configuration Guidelines 2-1

2visible 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/E over Extended Distances..............2-13

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.

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

◆ All CLARiiON storage systems must be running Access Logix software.

◆ 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/E 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.

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

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

SAN Copy/E Configuration Requirements 2-3


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.

◆ When copying data to a Symmetrix system, use the navicli -lunmapinfo command to obtain the world wide name (WWN) of any Symmetrix volumes that you want to include in the SAN Copy session. These volumes must be mounted and the Navisphere Host Agent must be installed on the hosts that own the volumes. For the required Host Agent revision, refer to the CX-Series SAN Copy/E Release Notes, available on Powerlink (see Finding Current Information in the Preface).

◆ In order for the logical units to participate in a SAN Copy/E 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 a remote storage system. This results in a consistent easy-to-troubleshoot zoning configuration.

Zones SAN Copy/E 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 dual SP AX-Series storage system running 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

EMC2698L

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 1to 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

EMC3051

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. Register the SAN Copy/E ports with any other SP ports in the same zone using the navicli -h spname sancopy -updateconnections command (see page 4-55).

The SAN Copy/E ports register with each storage system to which it has a connection, and the software adds a record for each port to the storage system’s host initiator table.

3. Verify that the SAN Copy/E ports are connected and registered with any storage systems that will participate in a copy session using the following command for each SP on the SAN Copy/E storage system:

navicli -h spname -port -list where spname is the name of an SP in the SAN Copy/E storage system.

4. Connect the SAN Copy/E ports to CLARiiON Storage Groups.



Connecting SAN Copy/E Ports to CLARiiON Storage GroupsIn 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/E 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/E 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.

For more information on the following CLI commands, refer to the EMC Navisphere Command Line Interface (CLI) Reference.

1. Use the following command to create Storage Groups:

navicli -h spname storagegroup -create -gname storagegroupname

2. Use the following command to add LUNs to Storage Groups:

navicli -h spname storagegroup -addhlu -gname storagegroupname -hlu hlunnumber -alu alunnumber

3. Use the following command to add the SAN Copy/E ports to Storage Groups:

navicli -h spname storagegroup -setpath -gname storagegroupname-hbauid hbawwn -sp a or b -spport portnumber

where

spname is the IP address of the SP on the storage system to which the Storage Group belongs.

storagegroupname is the name of the Storage Group to which you want to connect

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


If the sharing state of the Storage Group is Dedicated (only a single host can access the LUNs in the Storage Group), you must also specify one of the following switches: -host hostname, or -ip ipaddress where

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/E 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 source LUN 3 is copying data to the LUN 2 in SG 1. Since LUN 1 and LUN 2 belong to the same Storage Group, you can connect the same SAN Copy/E port directly to this Storage Group and both sessions can use this 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.

hbawwn is the world wide name of the SAN Copy/E port (from the -portlist command)

a or b is the SP that owns the Storage Group

portnumber is the the ID of the SP port hat owns the Storage Group (from the -portlist command)

hostname is the name of the host that has access to the LUNs in the Storage Group

ipaddress is the IP address of the host that has access to the LUNs in the 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/E Storage Group Configuration

What Next? ◆ To prepare the logical units for a copy session, go to Preparing Logical Units for a SAN Copy/E Session on page 3-5.

◆ To create and start a SAN Copy/E session, continue to Chapter 4, SAN Copy/E CLI Commands.

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/E over Extended Distances 2-13


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

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.



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

Using the admhost Utility with SAN Copy/E 3-1

3Invisible Body Tag Utility

This chapter explains how to use the admhost utility.

◆ About admhost for SAN Copy/E....................................................3-2◆ Admhost SAN Copy/E Command Functions...............................3-3◆ Preparing Logical Units for a SAN Copy/E Session ....................3-5

Using the admhost Utilitywith SAN Copy/E


Using the admhost Utility with SAN Copy/E

About admhost for SAN Copy/E The admhost utility is an executable program that you can run interactively via script. The admhost commands can activate and deactivate the source and destination logical units being used in a copy session, and flush data from operating system buffers to ensure that the information on the source logical unit is current.

Currently, admhost is supported only on the following Microsoft® Windows platforms: Windows Server 2003, Windows 2000, and Windows NT. For the supported versions of these operating systems, see the EMC CX-Series SAN Copy/E Release Notes, or the EMC admhost Release Notes.

Admhost SAN Copy/E Command Functions 3-3


Admhost SAN Copy/E Command FunctionsTable 3-1 lists the admhost commands and describes their function in copy sessions.

The admhost utility is not supported on a UNIX® host. Use the commands your operating system normally uses to discover new logical units, flush buffers, and unmount the logical units.

Table 3-1 Admhost Functions and Descriptions

Function Description Syntax and Examples

admhost lun_activate The admhost lun_activate command scans the bus for new devices and assigns a drive letter to all CLARiiON devices that do not already have one. Use the -l and -d switches to scan the bus for new devices and assign a drive letter to a device that has a specific world wide name (WWN). This command does not assign drive letters to any other devices.

If admhost_activate is used and no new devices are found, and drive letters are already assigned to the CLARiiON logical units, admhost reports an error message.

admhost lun_activate [-l lun_wwn -d drive_letter][-h]where -l lun_wwn specifies the world wide name (WWN) of the LUN to which you want to assign a drive letter (requires the -d switch).-d drive_letter specifies the drive letter you want to assign to the specified LUN (requires the -l switch).-h displays the help message.

If the admhost lun_activate command activates more than one device, the drive letter is assigned to the first device in the list.

admhost lun_deactivate

The admhost lun_deactivate command attempts to take devices offline and make them inaccessible to the operating system. The command deletes the drive letter and dismounts the device. Use the admhost lun_activate command to bring the volume back online.

Use this command on the source or destination host prior to starting a copy session (see Preparing Logical Units for a SAN Copy/E Session on page 3-5).

admhost lun_deactivate -o object_name [-t object_type][-h]where--o object_name specifies the drive letter of the device you want to deactivate.When you specify the object name, admhost finds the device, deletes its drive letter, dismounts it, and then takes the device offline.-t object_type is an optional switch that specifies the object type (device or driveletter) of the device you want to deactivate.-h displays the help message.



What Next? Before you start a copy session, complete the steps described in the next section, Preparing Logical Units for a SAN Copy/E Session.

Function Description Syntax and Examples

admhost lun_flush On a Windows host, the command flushes all data for the specified object_type so that the data in the write cache is written to disk.

Use this command on the source or destination host prior to starting a copy session (see Preparing Logical Units for a SAN Copy/E Session on page 3-5).

admhost lun_flush [-h] -o object_name [-t object_type device|driveletter]where-h displays a help message.-o object_name specifies the name or drive letter of the device you want to flush.-t object_type is an optional switch that specifies the object type (device or driveletter) of the device you want to flush.If you specify the device name, admhost identifies the corresponding device and drive letter.

admhost lun_list Use to perform a list operation. This command lists the drive letters and WWNs for all host devices.

admhost lun_list [-h] [-l lun_wwn][-d object_name] [-a output_style]where-h displays a help message.-l lun_wwn specifies the WWN of the device you want to list.-d object_name specifies the drive letter or name of the device you want to list.-a output_style specifies an alternative output style for the list output. The default style lists the drive letter and WWN for the logical unit. The -a switch lets you specify physicaldrive as the output style.

admhost help This command displays the syntax for each admhost command and the revision number of the admhost utility. Output for the dmhost help command is shown below.Revision number: V1.1.0.0.0 - 0Valid operations include:

lun_flush, lun_activate, lun_deactivate, lun_list, and help.

Valid types include: device and driveletter.

admhost help

Preparing Logical Units for a SAN Copy/E Session 3-5


Preparing Logical Units for a SAN Copy/E SessionBefore you start a full copy session, and before you mark an 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 and incremental sessions.

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. Stop all I/O to the source and destination logical units.

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 similar utility to make the data copy mountable. In this situation, the data copy may not contain the unflushed server data.

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

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

Preparing Logical Units for a SAN Copy/E Session 3-7


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

What Next? ◆ For incremental sessions, mark the session using the sancopy -mark command on page 4-31.

◆ For full sessions, you are now ready to start the session using the sancopy -start command on page 4-46.

SAN Copy/E CLI Commands 4-1

4Invisible Body Tag

This chapter explains the sancopy commands used with naviseccli or navicli CLI commands to manage the SAN Copy/E software.

The commands in this chapter function only with a storage system that has the optional SAN Copy/E software installed.

Topics are

◆ SAN Copy/E Command Functions ................................................4-2◆ About Secure CLI ...............................................................................4-4◆ naviseccli .............................................................................................4-5◆ About Classic CLI ............................................................................4-10◆ navicli.................................................................................................4-10◆ sancopy -create .................................................................................4-14◆ sancopy -destinfo .............................................................................4-19◆ sancopy -duplicate ...........................................................................4-23◆ sancopy -info.....................................................................................4-25◆ sancopy -mark ..................................................................................4-31◆ sancopy -modify...............................................................................4-33◆ sancopy -pause .................................................................................4-38◆ sancopy -remove ..............................................................................4-39◆ sancopy -resume...............................................................................4-41◆ sancopy -settings..............................................................................4-43◆ sancopy -start....................................................................................4-46◆ sancopy -stop ....................................................................................4-48◆ sancopy -throttle...............................................................................4-50◆ sancopy -transfer..............................................................................4-52◆ sancopy -unmark .............................................................................4-54◆ sancopy -updateconnections ..........................................................4-55◆ sancopy -verify .................................................................................4-56

SAN Copy/E CLICommands


SAN Copy/E CLI Commands

SAN Copy/E Command FunctionsThe EMC Navisphere CLI provides one of the two interfaces to the SAN Copy/E software. The Navisphere Manager UI provides the other. The CLI command is naviseccli sancopy or navicli sancopy and you specify functions with switches.

The sancopy command functions, listed alphabetically, are

◆ sancopy -create

◆ sancopy -destinfo

◆ sancopy -duplicate

◆ sancopy -info

◆ sancopy -mark

◆ sancopy -modify

◆ sancopy -pause

◆ sancopy -remove

◆ sancopy -resume

◆ sancopy -settings

◆ sancopy -start

◆ sancopy -stop

◆ sancopy -throttle

◆ sancopy -transfer

◆ sancopy -unmark

◆ sancopy -updateconnections

◆ sancopy -verify

The sancopy command functions are listed functionally, in the order you would perform them, in the following table.

SAN Copy/E Command Functions 4-3


Table 4-1 naviseccli or navicli sancopy Command Functions, Listed in Order of Use

Command Description

Essential Functions (in Order Performed)

sancopy -create, orsancopy -create -incremental

Creates a full copy sessionCreates an incremental copy session

sancopy -mark (incremental copy sessions only)

Creates a point-in-time copy of the changes that have taken place since the last copy session up to the time the session is marked

sancopy -start Starts a copy session based on copy descriptor information

Optional Status Functions (Alphabetically)

sancopy -destinfo Displays information on a particular session from the destination point of view

sancopy -info Displays information on all copy sessions or displays attributes for a particular session

sancopy -stop Stops a copy session

sancopy -verify Ensures that the copy software can access a logical unit

Optional Reconfiguration Functions (Alphabetically)

sancopy -duplicate (full copy sessions only) Creates a duplicate copy descriptor

sancopy -modify Changes parameters in a copy descriptor

sancopy -pause Pauses a copy session

sancopy -remove Deletes a copy descriptor

sancopy -resume Continues a paused, stopped or failed session

sancopy -throttle Changes the throttle (execution rate) of an existing, running session

sancopy -unmark (incremental copy sessions only)

Removes the existing mark in preparation for inserting a new mark.

sancopy -transfer Transfers control of a copy descriptor to the peer SP

sancopy -settings Gets or sets environmental control parameters

sancopy -updateconnections Updates storage-system registration information



About Secure CLISecure CLI is a comprehensive Navisphere CLI solution that provides one application and one security model for all CLI commands. Secure CLI combines key features of the existing Classic (see About Classic CLI on page 4-10) and Java CLI functionalities. Similar to Classic CLI, you do not need to install a JRE to run Secure CLI. Secure CLI implements the security features of Java CLI, providing role-based authentication, audit trails of CLI events, and SSL-based data encryption.

Secure CLI is not supported on all operating systems. Refer to the Agent/CLI Release Notes, available on Powerlink, for a list of supported operating systems. You must be running FLARE Operating Environment version 02.19.xxx.5.yyy or higher.

Secure CLI commands run in a command window. Each command consists of the naviseccli command (and switches) together with another subcommand (and its switches). The naviseccli command replaces navicli (Classic CLI) and java-jar navicli.jar (Java CLI) in the command line and, in general, preserves the original command syntax and output for script compatibility.

For commands that originated in Classic CLI, some command output may be enhanced; for example, Secure CLI can retrieve and display information from peer SPs. For Classic CLI commands that produce multiple warnings and require multiple confirmations, Secure CLI provides a single summary of warnings and a single confirmation.

For more information on the Secure CLI functionality, refer to EMC Navisphere Command Line Interface (CLI).

naviseccli 4-5


naviseccli Sends status or configuration requests to a storage system via command line

Description The naviseccli command sends storage system management and configuration requests to a storage system via the Internet.

User Access Anyone that can log in to the host running Navisphere CLI 6.X or later.

Format The naviseccli command is used as follows:

naviseccli -help or naviseccli

[-address IPaddress|NetworkName|-h IPaddress|NetworkName][-AddUserSecurity]

[-f filename][-m][-nopoll|-np] [-parse|-p] [-password password] [-port port][-q][-RemoveUserSecurity][-scope 0|1][-timeout |-t timeout][-user username] [-v][-xml] CMD [optional_command_switches]

where the naviseccli switches are

-help

Displays the help screen and does not start the naviseccli process. To start the naviseccli process, use one or more of the switches that follow instead.



-address IPaddress|NetworkName|-h IPaddress|NetworkName

Specifies the IP address or network name of the targeted SP on the desired storage system. The default, if you omit this switch, is localhost.

-AddUserSecurity

Directs the CLI to add user security information to the security file on this host. You must use the -scope switch to add scope information to the security file. You can use the -password switch or enter your password into the password prompt (see -password), to supply the required password information to the security file. The -user and -secfilepath switches are optional with this command.

If you specify the -user switch, you can create an alternative username to your host login name in the security file you create on this host. If you use the -secfilepath switch, you can specify an alternative location to your default home directory, for the security file on this host. You must then use the -secfilepath switch in each subsequent command you issue.

-f filename

Specifies to store data in a file.

-m

Suppresses output except for values. This option is most useful when used as part of a script.

Only supported for commands that originated in Classic CLI.

-nopoll|-np

Directs the feature provider not to issue a poll request. This switch significantly increases performance when dealing with large or multiple storage systems. The feature provider automatically polls unless this switch is specified.

When the -nopoll switch is set, get commands may return stale data and set commands may erase previously changed settings. Use caution when the -nopoll switch is set.

naviseccli 4-7


-parse |-p

Directs the CLI to validate the command. The CLI verifies the command syntax and displays a message stating whether the command was valid. The CLI takes no other action.

-password password

Specifies the password on the storage system you want to log in to. The password is visible in the command line. Passwords are case sensitive.

If you want to mask the password, and you are not using a security file, you can omit this switch from the command line. The CLI then prompts you to enter a password. The information you enter into the password prompt is concealed.

You can omit this switch if you are using a security file. See -AddUserSecurity.

-port portnumber

Sets the port number (type) of the storage system. The default is 443. If you choose to change the default port number, management port 2163 will be supported; however, you will need to specify the -port switch and number 2163 in every subsequent command you issue.

-q

Suppresses error messages. This switch is useful when included as part of a script.


-RemoveUserSecurity

Directs the CLI to remove user security information about the current user from the security file on this host.

-scope 0|1

Specifies whether the user account on the storage system you want to log in to is local or global. A 0 (default) indicates global; a 1 indicates local.



A global account is effective throughout the domain. When the administrator creates a global account, the software copies the definition of this account to the domain directory, which makes it accessible on all storage systems in the domain.

A local account is effective on only the storage systems for which the administrator creates the account. The user can log in to only those storage systems on which he has a local account.

-secfilepath filepath

Stores the security file in a file path location you specify. When you create a security file on a host using the -addusersecurity command, the security file is saved to your default home directory. If you want to store the security file in an alternative location, you can use the optional -secfilepath switch with the -addusersecurity command.

If you use the -secfilepath switch to set up an alternative path for your security file, you must use this switch in every subsequent CLI command you issue, to ensure the CLI locates the security file.

-timeout |-t timeout

Sets the timeout value in seconds. The default is 600 seconds.

-user username

Specifies the username on the storage system you want to log in to. Usernames are case sensitive. You can omit this if your username has been added to the security file.

You can use this switch when establishing a security file, to specify an alternative username. See -AddUserSecurity.

-v

Enables verbose error descriptions. This is the default unless -q is specified.


-xml

Specifies command output in XML format. Use the -o (override switch) when specifying -xml on commands that require confirmation. Otherwise, the XML output will contain your confirmation string.

naviseccli 4-9


CMD

One of a set of commands used with the naviseccli command.

CMD Switches The CMD switches are described on the pages that follow.

Spaces in Arguments Normally, each argument to a CLI command consists of numbers, letters, and other valid printable characters for the operating system on which the CLI is running.

If a filename or other argument includes a space, you must enclose the entire string that includes the name in quotation marks ("xx xx").



About Classic CLIClassic CLI commands run in a command window. Each command consists of the navicli command (and switches) together with another subcommand (and its switches). The navicli command does nothing when executed by itself. However, when you use it in combination with the other commands described in this manual, you can configure and manage any storage system supported by Navisphere CLI version 6.X.

If a CLI command fails and the CLI does not generate its own error message, it displays an error message generated by the Host Agent or SP Agent. The CLI generates errors about command line syntax for commands and options and their values.

navicliSends status or configuration requests to the storage system via the command line

Before you can use Navisphere CLI commands to configure a storage system (as opposed to receive storage-system configuration or status information), you must be a privileged user in the SP Agent configuration file on each SP in the storage system.

Description The navicli command sends storage-system management and configuration requests to a Navisphere Agent running on a local or remote host. The Agent then sends the request to the specified storage system.

User Access Anyone that can log in to the host running the Navisphere CLI can use navicli.

Format Use the navicli command as follows:

navicli -helpor navicli [-d device] [-f filename]-h hostname] [ -help] [-m] [-np] [-p] [-t timeout] -[v|q] CMD [optional-command-switches]

where the navicli switches are

-help

Displays the help screen and does not start the navicli process.

navicli 4-11


-d device

Specifies the communication channel to the storage system, for pre-FC4700 SPs only. (A CX-Series or FC4700-Series SP is a host that you specify with the -h switch. The CLI ignores the -d switch for CX-Series or FC4700-Series.)

-f filename

Specifies that data be stored in a file.

-h hostname

Specifies the hostname of the storage-system SP or server. For a CX-Series or FC-Series storage system, each SP is a host; therefore the hostname is the IP address or network name of the destination SP. For pre-FC4700 storage systems, the hostname is the server hostname or network address. The environment variable RaidAgentHost is the default for the server if the -h switch is not present. The -h switch overrides the RaidAgentHost setting. If RaidAgentHost is not set and the -h switch is not present, the local hostname is used.

-m

Suppresses output except for values. This option is most useful when used as part of a script.

-np

Suppresses polling on initial contact with the Agent. This switch significantly increases performance when dealing with large or multiple storage systems. The Agent automatically polls unless this switch is specified.

When the -np switch is set, get commands may return stale data and set commands may erase previously changed settings. Use caution when the -np switch is set.

-p

Parses the entered CMD (command) without making a network call to the API. If the string does not parse correctly, an error message prints to stderr; otherwise a message verifying that the string parsed correctly prints to stdout.



-q

Suppresses error messages. This switch is useful when included as part of a script.

-t timeout

Sets the timeout value. timeout specifies the value in seconds. The default timeout value is 240 seconds unless the RaidAgentTimeout environment variable (described on the following page) is set differently.The timeout value includes the time allowed for the entire command to execute (including CLI, Agent, and storage-system software execution time). The timeout applies to all commands except firmware.

-v

Enables verbose error descriptions. This is the default unless -q is specified.

CMD

One of a set of commands used with the navicli command to configure and manage a storage system. The CMD (command) CMD switches are described on the pages that follow.

Spaces in Arguments Normally, each argument to a CLI command is composed of numbers, letters, and other valid printable characters for the operating system on which the CLI is running. For example:

navicli -h ss1_spa convertEMlog -pathname G:\logs\c4.log -20

If a filename or other argument (such as a Storage Group name) includes a space, you must enclose the entire string that includes the name in quotation marks ("xx xx"). For example, if the filename in the above were c 4.log, the valid command line would be

navicli -h ss1_spa convertEMlog -pathname "G:\logs\c 4.log" -20

RaidAgent Environment VariablesThe environment variables RaidAgentHost, RaidAgentDevice, and RaidAgentTimeout contain default values for the server, the device, and the timeout values respectively if you omit the -h, -d, and -t switches from the navicli command. Note that RaidAgentDevice and the -d switch are ignored on CX-Series and FC-4700 storage systems. If you do not set RaidAgentTimeout and omit the -t switch, the default timeout value is 240 seconds.

navicli 4-13


Examples The following examples show sample environment variable settings.

The commands in the following examples must be executed from the root directory.

set RaidAgentDevice \\.\A-9162244 set RaidAgentHost server1 (or for CX-Series/FC4700, ss1_spa) set RaidAgentTimeout 45

Error Codes The navicli command might return any of a numeric sequence of errors for which recovery stategies are explained in Appendix A of this manual (for SAN Copy/E errors) or the Navisphere Command Line Interface (CLI) Reference (for other errors).



sancopy -createCreates full and incremental copy sessions

Description The naviseccli or navicli sancopy command with the -create switch creates a full copy session. A full session copies all the data on the source LUN to the destination logical units. When used with the optional -incremental switch, the -create command creates an incremental copy session. An incremental session copies only the data that has changed since the last copy session.

The destination logical unit(s) must exist when you execute this command.

By default a descriptor does not start a session unless you specify the -start switch.

For information on logical units accessible to the host use the basic CLI command lunmapinfo explained in the CLI reference manual.

User Access For naviseccli, you must have a user account on the storage system on which you want to execute the command.

For navicli, you must have a username/host entry in the Navisphere SP Agent configuration file to use this command.

Format Use the sancopy -create command with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -create [-incremental] -name sessionName

-srcwwn source-lun-wwn | -srclun source-sp sourcelunnumber[-device devicename]-destwwn dest-lun-wwn | -destlunnumber dest-sp destlunnumber [-device devicename]

[-start] [-throttle n] [-verify] [-o]

In addition to all the sancopy -create command switches, the sancopy -create -incremental command uses the following optional switches: -changesonly, -linkbw, and -latency (See Incremental Sessions on page 4-16)

where

-name sessionName

Specifies the copy session name. The name can be up to 64 characters and must be unique on a per storage system basis. The names you create persist until you remove them.

sancopy -create 4-15


For incremental copy sessions, SAN Copy/E creates a corresponding reserved session. The name assigned to the reserved session consists of the copy session name prefixed 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.

-srcwwn source-lun-wwn

For full and incremental copy sessions, the source LUN must reside on the SAN Copy/E storage system. For incremental sessions, the source LUN cannot be a SnapView snapshot.

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

Specifies the WWN (worldwide name) of the source logical unit.

-srclun source-sp sourcelunnumber

This is an alternate way of adding a source logical unit entry to the copy descriptor. For source-sp, specify the SP hostname (or SP IP address) that owns the source logical unit. For sourcelunnumber, specify the logical unit number.

-device devicename

Specifies the device name of the source LUN or destination LUN.

-destwwn dest-lun-wwn

If the destination storage is connected to a VMware ESX Server, 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





Specifies which logical unit will be the destination of the copy. You can specify more than one destination logical unit if you want more than one copy of the source logical unit. If the destination logical units are not reachable, and you did not use the -o function, the CLI will display a warning and ask for confirmation.

-destlunnumber dest-sp destlunnumber

This is an alternate way of adding a destination LUN entry to the copy descriptor. For dest-sp, specify the SP hostname (or SP IP address) that owns the destination logical unit; for destlunnumber, specify the LUN number. As with -destwwn, you can specify more than one destination logical unit if you want more than one copy of the source logical unit.

If you specify the -verify function, and the software cannot reach the SP or find the logical unit on the SP, it returns an error.

-start

Starts a copy session using this copy descriptor. By default, the create command does not start a session.

-throttle n

Specifies the I/O rate of the copy. The maximum value is 10 and the minimum value is 1. If you omit this switch, the default value is 6.

-verify

Verifies that SAN Copy/E can access all of the logical units specified in the -create command.

-o

Suppresses a message asking you to confirm that you want to create a session now.

Incremental Sessions The following optional switches are used only with the sancopy -create -incremental command:

-changesonly

If the source LUN and destination LUNs are synchronized when you create the session, use this switch. When you start the session, SAN Copy/E will copy only the changes that have occurred to the source LUN since the initial synchronization.

sancopy -create 4-17


If the source LUN and destination LUNs are not synchronized (or you are unsure of the copy state), do not use this switch. The first time you run the session, SAN Copy/E will copy the entire source LUN to the destination LUNs. Any subsequent sessions will copy only the changes.

-linkbw

Specifies the available link bandwidth for the copy session. You can use the entire bandwidth of your network connection for incremental copy sessions, or you can specify only a portion of it. The minimum allowable value is .016 megabytes per second (Mbytes/sec) and the maximum value is 2048 Mbytes/sec. The default value is 1.5 Mbytes/sec (equivalent to a T1 line).

-latency

The amount of time it takes to transmit a block of data to its destination expressed in milliseconds. Valid values are auto (SAN Copy/E computes the latency value), or a decimal number with no maximum limit. The default value is auto.

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 for the session.

Conventions andRecommendations

None.

Full Session Example naviseccli -h ss1_spa sancopy -create -name copy_lun66 -srclun ss1_spa 66 -destlunnumber ss5_spa 22 -start -throttle 3

For SP ss1_spa, the -create command creates a full copy session named copy_lun66 that defines source logical unit 66 on this SP and destination logical unit 22 on host SP ss5_spa. The -start command then starts the copy session and the -throttle command specifies a throttle value of 3 for this session.

To use this command with navicli, replace naviseccli with navicli.

Incremental SessionExample

naviseccli -h 10.22.33.44 sancopy -create -incremental -name copy_77 -srclun 10.22.33.44 1 -destlunnumber ss5_spa 22 -linkbw 100



This command creates an incremental copy session named copy_77 that defines logical unit 1 on SP 10.22.33.44 as the source and logical unit 22 on SP ss5_spa as the destination. The -linkbw command specifies a bandwidth value of 100 Mbytes/sec., and the latency value defaults to auto.


Output If the version of FLARE ™ software running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other errors are

DMF_NAME_SPECIFIED_NOT_UNIQUEDMF_CREATE_PARAMSDMF_SRCLUN_WWN_AND_NUMBER_SPECIFIEDDMF_DESTLUN_WWN_AND_NUMBER_SPECIFIEDDMF_INVALID_THROTTLE_VALUE

sancopy -destinfo 4-19


sancopy -destinfoDisplays information about destination logical units for a running session

Description The naviseccli or navicli sancopy command with -destinfo gets session status from the destination point of view.

If you have only full copy sessions, issuing the -destinfo command with no arguments displays all destination information for all copy sessions belonging to the specified SP.

If you have both full and incremental copy sessions, and you issue the -destinfo command with no arguments, some parameters for full sessions and all parameters specific to incremental sessions will not display. In order to see all parameters for both full and incremental sessions, you must use the destinfo -all command.

EMC recommends that you use the -destinfo -all command for both full and incremental sessions (for output examples, see Examples on page 4-21).



Format Use sancopy -destinfo with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -destinfo [-peer][-descriptorid [descriptorid]] |[-name [name]][-destwwn [dest-lun-wwn]] |[-destlunnumber destsp destlunnumber][-complete] [-counts] [-failure] [-time] [-all]

In addition to all the sancopy -destinfo command switches listed above, incremental copy sessions use the optional -syncstate switch (See Incremental Sessions on page 4-21).



where

-complete

Displays the percentage complete of the copy session when any destination logical unit(s) failed. Displays N/A when there is no failure.

-counts

Displays the number of disk blocks transferred when any destination logical units failed. Displays N/A when there is no failure.

-descriptorid [descriptorid] | -name [name]

Used alone, -descriptorid or -name displays descriptor IDs or names of all copy descriptors of the specified SP; -descriptorid with an ID or -name with a name lists the status (WWN, failure status, transfer count, percent complete and failure time) of all destinations of the copy descriptor.

-destwwn [dest-lun-wwn]

Used alone, -destwwn displays the WWNs of all destinations of the descriptors. -destwwn with a WWN lists the status of the specified destination logical unit.

-destlunnumber destsp destlunnumber

The switch -destlunnumber cannot be used alone. When used with the SP name and LUN number, it displays the status of the specified destination logical unit.

-failure

Displays failure status or No Failure for destination logical unit(s). For more information, also use the -time, -counts, and/or -complete switches.

-peer

Lists all destination information on the peer SP.

-time

Displays the time when any destination logical unit(s) failed. Displays N/A when there is no failure.

-all

Displays all destination information for both full and incremental copy sessions belonging to the specified SP.

sancopy -destinfo 4-21


If you have both full and incremental copy sessions, and you issue the -destinfo command with no arguments, some parameters for full sessions and all parameters specific to incremental sessions will not display. In order to see all parameters for both full and incremental sessions, use the destinfo -all command.

Incremental Sessions The following optional switch is used only with incremental sessions.

-syncstate

Displays the state of the data of the specified destination logical unit with respect to the source logical unit. Valid states are N/A, Inconsistent, and Initial Copy Required.


None.

Examples naviseccli -h ss1_spa sancopy -destinfo

Copy Descriptor ID 1Destination LUN WWN:

60:06:01:6B:61:09:00:00:6A:6F:9F:ED:0B:A3:D6:11Failure Status: No FailureTransfer Count at Failure N/APercent Complete at Failure N/A

Copy Descriptor ID: 2Destination LUN WWN:

60:06:01:6B:61:09:00:00:6A:6F:9F:ED:0B:A3:D6:11Failure Status: Destination LUN is fullTransfer Count at Failure: 90Percent Complete at Failure: 12Failure Time at Failure: 08/06/02 12:34:19

In both examples, copy descriptor 1 is a full copy session and copy descriptor 2 is an incremental session. By using the -destinfo command without the -all switch, you cannot determine that copy descriptor 2 is an incremental session since none of the incremental information is displayed for the session.

naviseccli -h ss1_spa sancopy -destinfo -all

Copy Descriptor ID 1Destination LUN WWN:

60:06:01:6B:61:09:00:00:6A:6F:9F:ED:0B:A3:D6:11Failure Status: No FailureTransfer Count at Failure N/APercent Complete at Failure N/A

Copy Descriptor ID: 2



Destination LUN WWN: 60:06:01:6B:61:09:00:00:6A:6F:9F:ED:0B:A3:D6:11

Failure Status: Destination LUN is fullSync State Initial Copy RequiredTransfer Count at Failure: 90Percent Complete at Failure: 12Failure Time at Failure: 08/06/02 12:34:19By using the -destinfo command with the -all switch, all the information for both sessions is displayed as well as all the Sync State information for the incremental session.


Output If the version of FLARE software running on the SP does not support this command, a Command is not supported error message is printed to stderr.

sancopy -duplicate 4-23


sancopy -duplicateMakes a copy of a copy descriptor

The sancopy -duplicate command is not supported for incremental copy sessions.

Description The naviseccli or navicli sancopy command with -duplicate makes a copy of an existing copy descriptor. You can then modify the copy as needed (-modify). The copy descriptor that you want to duplicate can be part of an active copy session. You do not need to stop the copy descriptor before duplicating it.



Format Use sancopy -duplicate with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -duplicate -descriptorid descriptorid | -name name

where

-descriptorid descriptorid | -name name

Identifies the descriptor you want to duplicate.


None.

Example naviseccli -h ss1_spa sancopy -duplicate -name copy_lun_66

This command duplicates SP ss1_spa’s copy descriptor copy_lun_66 and assigns a default name to the new descriptor - copy of xxx, where xxx is the name of the descriptor you are duplicating. For example,copy of copy_lun_66.




Output If the version of FLARE running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other errors are

DMF_NAME_AND_UID_SPECIFIEDDMF_NAME_OR_UID_REQUIREDDMF_UNKNOWN_DESCRIPTOR

sancopy -info 4-25


sancopy -infoDisplays information about copy descriptors

Description The naviseccli or navicli sancopy command with -info displays information about copy sessions. It differs from -destinfo in that -destinfo gets information on the destination logical units.

If you have only full copy sessions, issuing the -info command with no arguments displays all destination information for all copy sessions belonging to the specified SP.

If you have both full and incremental copy sessions, and you issue the -info command with no arguments, some parameters for full sessions and all parameters specific to incremental sessions will not display. In order to see all parameters for both full and incremental sessions, use the info -all command.

EMC recommends that you use the -info -all command for both full and incremental sessions (for output examples, see Examples on page 4-28).



Format Use sancopy -info with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -info [-peer] [-descriptorid descriptorid | -name name] [-srcwwn] [-length] [-numdests] [-dests] [-sessionstatus] [-throttle] [-counts] [-complete] [-time] [-failure] [-duration] [-type] [-all]

In addition to all the sancopy -info command switches listed above, incremental copy sessions use the following optional switches: -copywholelun, -markstatus, -srcsize, -link (see Incremental Sessions on page 4-27).

where

-complete

Displays the percentage complete of the copy session.

-counts

Displays the number of disk blocks transferred.



-descriptorid descriptorid

Lists the descriptor IDs of all sessions belonging to the specified SP when you issue this command without a specific descriptor ID.

Lists the status of the specified session when you issue this command with a specific descriptor ID.

-dests

Displays the WWNs of all destination logial units in the specified descriptor.

-duration

Displays the completion time and duration of the session.

-failure

Displays failure status or No Failure for the copy descriptor’s source and destination logical units.

-length

Displays the number of blocks to copy. Displays N/A if the descriptor was created using the source WWN.

-name name

Lists the names of all copy descriptors belonging to the specified SP when you issue this command without a specific copy descriptor name.

Lists the status of the specified copy descriptor when you issue this command with a name.

-numdests

Displays the number of destination logical units.

-peer

Lists all destination information on the peer SP.

-sessionstatus

Displays the status of the session associated with the copy descriptor: not started, complete, stop, pause, or failed.

-srcwwn

Displays the WWNs of all source logical units.

sancopy -info 4-27


-throttle

Displays the current throttle value for the copy session.

-time

Displays the time when the copy completes.

-type

Displays the session type - Full or Incremental.

Incremental Sessions The following optional switches are used only with incremental copy sessions.

-copywholelun

Displays whether the session will copy the entire source logical unit or only changes to it. If Yes, the session copies the entire logical unit; if No, it copies only the changes.

-markstatus

If a session is marked, SAN Copy/E creates a point-in-time copy of the changes that have taken place since the last copy session up to the time the session is marked.

Displays whether the session has been marked, and if yes, displays the time of the mark, and the number of blocks of data that have changed since the mark occurred (these data blocks will not be copied when the session starts).

-srcsize

Displays the size, in blocks, of the source logical unit.

-link

Displays the status of any network link utilization performance parameters as follows:

Link Bandwidth — Link bandwidth of the network connection set when the session was created. Value is in Mbytes/sec.

Effective Bandwidth — Actual link bandwidth for the session measured by SAN Copy/E.

Latency — Displays the latency value set when the session was created or the default value of Auto. Latency is the amount of time it takes to transmit a block of data to its destination expressed in milliseconds.



Measured Latency — The actual measured latency of the session expressed in milliseconds.

-all

Displays all session information for both full and incremental copy sessions belonging to the specified SP.

You must use the destinfo -all command to display information that is specific to incremental sessions. EMC recommends that you use the -destinfo -all command for both full and incremental sessions.

The information displayed with the -all command may change in future revisions of the software.


None.

Examples naviseccli -h ss1_spa sancopy -info

For SP ss1_spa, this -info command displays the status of all copy descriptors, but does not include any information specific to incremental copy sessions. The format is as follows:

Copy Descriptor ID:Descriptor ID.Copy Descriptor Name:Descriptor name. Source LUN WWN:16-byte worldwide nameof source logical unit (-srcwwn).Number of Blocks to Copy:Number of blocks to copy (-length).Number of Destinations: Number of destination logical unitsto be copied to (-numdests) Destination LUN WWN:16-byte worldwide name of destination logical unit (-destwwn).Session Status:Success, Stop, pause, failed.(-sessionstatus).Initial Throttle:Starting throttle value (-throttle).

Current Throttle:Current throttle value for currentrunning copy descriptor (-throttle).Transfer Count:Number of blocks copied (-counts).Percent Complete: Percent completion (-complete).Completion Time: Time that the session completed (-time).Failure Status: Source and destination failure status:No failure or Failure (-failure).

sancopy -info 4-29


naviseccli -h ss1_spa sancopy -info -all

For SP ss1_spa, this -info -all command displays the status of all copy descriptors, including any information specific to incremental copy sessions. The format for an incremental copy session is as follows:

Copy Descriptor Name: Descriptor name.Copy Descriptor ID: Descriptor ID. Copy Descriptor Type: IncrementalCopy Whole LUN: YES/NOSource LUN WWN: 16-byte worldwide name of source

logical unit (-srcwwn).Number of Blocks to Copy:Number of blocks to copy

(-length).Size of source LUN: Size in blocksNumber of Destinations: Number of destination logical units

to be copied to (-numdests) Destination LUN WWN: 16-byte worldwide name of

destination logical unit (-destwwn).Session Status: Success, Stop, pause, failed.

(-sessionstatus).Initial Throttle: Starting throttle value (-throttle).Current Throttle: Current throttle value for current

running copy descriptor (-throttle).Transfer Count: Number of blocks copied (-counts).Percent Complete: Percent completion (-complete).Completion Time: Time that the session completed (-time).Duration: Duration of the session (-duration)Failure Status: Source and destination failure status:

No failure or Failure (-failure)Marked: Is the session marked - YES/NO

(-markstatus)Mark Time: Time the session was marked

(-markstatus)Blocks modified since mark: (-markstatus)Link Bandwidth (Mbps): (-link)Effective Bandwidth (Mbps): (-link)Latency (msec): (-link)Measured Latency (msec): (-link)




Output If the version of FLARE software running on the SP does not support this command, a Command is not supported error message is printed to stderr.

sancopy -mark 4-31


sancopy -markFor incremental sessions only. Makes a point-in-time copy of changes to the source logical unit since the last copy session.

Before marking the session, make sure that you prepare the source logical unit as described in the section, Preparing Logical Units for a SAN Copy/E Session on page 3-5. Once you receive confirmation that the mark operation was successful, you can resume I/O to the source logical unit.

Description The naviseccli or navicli sancopy command with -mark creates a point-in-time copy of the changes that have taken place since the last copy session up to the time the session is marked. You can mark the session at any time before you start the session, or SAN Copy/E will mark the session at the time the session starts. When you start a marked session, all changes made to the source LUN up to the time of the mark, will be copied to the destination logical units. Any changes made to the source logical unit after the mark will not be copied until the next copy session.



Format Use sancopy -mark with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -mark -descriptorid descriptorid | -name sessionName

where

-descriptorid descriptorid | -name sessionName

Identifies the session you want to mark.


None.

Example naviseccli -h 10.11.22.33 sancopy -mark -name monday

This command marks the copy session named monday. When the session is started, it copies only the changes to the source logical unit



that have taken place since the last copy session up to the time of the mark.


Output If the version of FLARE Software running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other errors are


sancopy -modify 4-33


sancopy -modifyChanges the definitions for a copy session

Description The naviseccli or navicli sancopy command with -modify changes an existing copy session. This command will fail if the session has started or is in the paused state. The session must be stopped for modifications to be done.

The new session information will not take effect until you start a new session.

You must include a copy descriptor ID or name and one or more switches to indicate changes.



Format Use sancopy -modify with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -modify -descriptorid descriptor-id | -name name [-adddestbywwn dest-lun-wwn] [-adddestbylunnumber destsp destlunnumber] [-chgname newname] [-chgsrcbywwn srcwwn] [-chgsrcbylunnumber srcspname srclunnumber] [-chgtype] [-o][-rmdestbywwn dest-lun-wwn] [-rmdestbylunnumber destsp destlunnumber][-throttle n]

If you are modifying an incremental copy session, the following optional switches are available: -copywholelun, -chglinkbw, and -chglatency (see Incremental Sessions on page 4-36).



where

-adddestbylunnumber destsp destlunnumber

Adds a destination logical unit to the descriptor by destination SP (specify the SP name or IP address) and destination logical unit number.

-adddestbywwn dest-lun-wwn

Adds a destination logical unit to the descriptor by worldwide name.

-chgname newname

Not available for incremental sessions.

Changes the descriptor name to newname.

-chgsrcbylunnumber srcspname srclunnumber


Changes the source logical unit in the descriptor owned by source SP (for srcspname, specify the SP name or IP address) and source logical unit number.

-chgsrcbywwn srcwwn


Changes the source logical unit in the descriptor by the new source logical unit’s worldwide name.

-chgtype

Changes the type of the copy session — incremental or full.

If you change the session type from full to incremental, the following optional switches are available: -changesonly, -linkbw, and -latency.

-changesonly

If the source LUN and destination LUNs are synchronized, use this switch. When you start the session, SAN Copy/E will copy only the changes that have occurred to the source LUN since the initial synchronization, and any subsequent sessions will copy only the changes.



If the source LUN and destination LUNs are not synchronized (or you are unsure of the copy state), do not use this switch. The first time you run the session, SAN Copy/E will copy the entire source LUN to the destination LUNs. Any subsequent sessions will copy only the changes.

-linkbw

Specifies the available link bandwidth for the copy session. You can use the entire bandwidth of your network connection for incremental copy sessions, or you can specify only a portion of it. The minimum allowable value is .016 megabytes per second (Mbytes/sec) and the maximum value is 2048 Mbytes/sec. The default value is 1.5 Mbytes/sec (equivalent to a T1 line).

-latency

Specifies the latency value for the incremental session. Latency is the amount of time it takes to transmit a block of data to its destination expressed in milliseconds. Valid values are auto (SAN Copy/E computes the latency value), or a decimal number with no maximum limit. The default value is auto. Entering a 0 latency value is the equivalent to entering auto.

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 for the session.


Identifies the descriptor you want to change.

-o

Suppresses a confirmation message describing the descriptor.

-rmdestbylunnumber destsp destlunnumber

Removes a destination logical unit from the specified descriptor by destination SP (specify the SP name or IP address) and destination logical unit number.

-rmdestbywwn dest-lun-wwn

Removes a destination logical unit from the specified descriptor by worldwide name.



-throttle n

Changes the I/O rate to n (valid values 1 through 10). The default value is 6. To change the throttle value of an active session, use the command sancopy -throttle.

Incremental Sessions For incremental copy sessions, the following optional switches are available.

-copywholelun

Specifies that the session will the copy entire contents of the source logical unit the next time the session is run.

-chglinkbw

Changes the link bandwidth for the specified session. The minimum allowable value is \.016 megabytes per second (Mbytes/sec) and the maximum value is 2048 Mbytes/sec. The default value is 1.5 Mbytes/sec (equivalent to a T1 line).

-chglatency

Changes the latency value for the specified session. Latency is the amount of time it takes to transmit a block of data to its destination expressed in milliseconds. Valid values are auto (SAN Copy/E computes the latency value), or a decimal number with no maximum limit. The default value is auto.


None.

Example naviseccli -h ss1_spa sancopy -modify -name copy_66 -adddestbywwn 60:06:01:6B:61:09:00:00:6A:6F:9F:ED:0B:A3:D6:11

For SP ss1_spa, copy descriptor copy_66 is a full copy session. This command adds the destination logical unit whose worldwide name is 60:06:01:6B:61:09:00:00:6A:6F:9F:ED:0B:A3:D6:11.

naviseccli -h ss1_spa sancopy -modify -name copy_77 -copywholelun

For SP ss1_spa, copy descriptor copy_77 is an incremental copy session. The next time session copy_77 is run, SAN Copy/E will copy the contents of the entire source LUN to the destinations.





DMF_NAME_AND_UID_SPECIFIEDDMF_NAME_OR_UID_REQUIREDDMF_UNKNOWN_DESCRIPTORDMF_INVALID_THROTTLE_VALUEDMF_REMOVED_DEST_DOESNOT_EXIST

Errors returned from the driver or Agent are

UNKNOWN_DESCRIPTOR_IDUNKNOWN_DESCRIPTOR_NAME SESSION_NAME_EXISTS



sancopy -pauseSuspends I/O in an active copy session

Description The naviseccli or navicli sancopy command with -pause pauses an existing copy session. You must specify the descriptor ID or name.

To continue the paused session, use the sancopy -resume function.



Format Use sancopy -pause with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -pause -descriptorid descriptor-id | -name name

where


Identifies the descriptor whose session you want to pause.


None.

Example naviseccli -h ss1_spa sancopy -pause -name copy_lun_66

For SP ss1_spa, this command pauses the session with the copy_lun_ 66 descriptor.





UNKNOWN_DESCRIPTOR_IDUNKNOWN_DESCRIPTOR_NAME INVALID_SIZE

sancopy -remove 4-39


sancopy -removeDeletes a copy session

Description The naviseccli or navicli sancopy command with -remove deletes one or all previously stored copy sessions. A copy session cannot be removed if it is currently active. An active copy session must complete the copy first or be stopped.

If you omit the override -o option, the CLI displays a message to confirm the removal of the copy session. This command must have only one of following switches attached:

-descriptorid-name-all



Format Use sancopy -remove with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -remove -descriptorid descriptor-id|-name name|-all [-o]

where

-descriptorid descriptorid | -name name | -all

Identifies the descriptor you want to remove

-all

directs the CLI to remove all descriptors on the SP

-o

suppresses a message confirming the removal of the descriptor.


None.

Example naviseccli -h ss1_spa sancopy -remove -name copy_lun_80

Do you really want to remove the copy descriptor(y/n)[n]? y y



For SP ss1_spa, this command deletes the copy descriptor named copy_lun_80.





UNKNOWN_DESCRIPTOR_ID

sancopy -resume 4-41


sancopy -resumeContinues I/O in a copy session

Description The naviseccli or navicli sancopy command with -resume resumes an existing copy session that was paused, stopped or failed. If the copy session was paused, it will start at the paused point.

If the copy session was stopped or failed, the resume command will restart the copy session from the latest checkpoint (explained in the settings command). In case the checkpoint feature is disabled (the checkpoint was set to disable), the copy session will restart from the beginning.

You must specify the descriptor ID or name.



Format Use sancopy -resume with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -resume -descriptorid descriptor-id | -name name

where


Identifies the descriptor whose session you want to resume.


None.

Example naviseccli -h ss1_spa sancopy -resume -name copy_lun_66

For SP ss1_spa, this command resumes the sancopy_lun_66 copy session.




Output If the version of FLARE running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other error messages are



UNKNOWN_DESCRIPTOR_IDUNKNOWN_DESCRIPTOR_NAME SESSION_ALREADY_IN_PROGRESS

sancopy -settings 4-43


sancopy -settingsLists or changes SAN Copy/E environmental parameters

Description The naviseccli or navicli sancopy command with -settings gets and sets four SAN Copy/E environmental control parameters:

◆ the maximum number of concurrent active sessions◆ a checkpoint interval for session status ◆ the number of buffers per session◆ the buffer size

To find the current settings, use the -list switch; to change a setting, omit -list and specify the setting.

If you do not change the setting specifications, the software uses default values.



Format Use sancopy -settings with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -settings -list

or

sancopy - settings [-setmax MaxNumSessions][-setcheckpoint CheckpointInterval] [-setbufnum buffervalue] [-setbufsize buffersize]

where

-list

Displays the current environmental parameter settings.



-setmax maxNumSessions

Sets the maximum number of copy sessions that can run concurrently. This number depends on the storage system type.

-setcheckpoint CheckpointInterval

Sets the checkpoint interval in minutes (values 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, or 90) or, with the literal Disable, disables the checkpoint feature. The default checkpoint value is 10 minutes.

The SAN Copy/E software can track the progress of a copy session by checkpoint interval. If a session fails while checkpointing is enabled, then after correcting the problem you can direct the software to resume (-resume function). It will continue copying from the last checkpoint, if possible. If checkpointing is disabled, or if resuming is not possible, you can start copying from the beginning.

-setbufsize buffersize

Specifies the maximum buffer size to be used by copy sessions on a Fibre Channel connection. The default buffer size is 1024 blocks. The minimum buffer size is 64 Kbytes.

-setbufnum buffernumber

Specifies the maximum number of buffers to be used by copy sessions on a Fibre Channel connection. The default number is 4, and the minimum is 1.


None.

Examples naviseccli -h ss1_spa sancopy -settings -list

For SP ss1_spa, this command lists the current value for maximum number of sessions, checkpoint interval, number of buffers per session, and buffer size.

Storage -System Type Maximum Concurrent Sessions

CX300 4 (2 per SP)

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

AX-Series (single SP) 2 per storage system

sancopy -settings 4-45


naviseccli -h ss1_spa sancopy -settings -setcheckpoint 45

For SP ss1_spa, this command changes the checkpoint interval to 45 minutes.

naviseccli -h ss1_spa sancopy -settings -setbufnum 3

For SP ss1_spa, this command changes the number of buffers to 3.



DMF_LIST_AND_SET_SPECIFIEDDMF_INVALID_MAX_SESSION_VALUEDMF_INVALID_CHECKPOINT_INTERVAL_VALVE

Errors Returned From Driver or Agent are

SESSION_MAX_OVER_LIMITSESSION_POLL_OVER_LIMIT



sancopy -startStarts a copy session based on values in a copy descriptor

Before starting a copy session, make sure you prepare the source and destination logical units as described in the section, Preparing Logical Units for a SAN Copy/E Session on page 3-5.

Description The naviseccli or navicli sancopy command with -start starts a copy session with the source and destination logical unit(s) identified in the copy descriptor. You can start a session using the descriptor ID or name.

The command works only when issued to the SP that owns the copy descriptor.

The sancopy -info command provides useful information for the sancopy -start command.



Format Use sancopy -start with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -start -descriptorid descriptor-id | -name name [-copywholelun [-nomark new|all]]

where


Identifies the copy descriptor for the session you want to start.

Incremental Sessions -copywholelun

Specifies that this incremental session will copy the entire contents of the source logical unit to all the destination logical units.To use this command the session must be unmarked. When you start the session using this command, SAN Copy/E will mark the session for you.

-copywholelun overrides any existing settings for the session.

sancopy -start 4-47


-nomark new|all

Used with the -copywholelun switch, and works only if the session is not already marked. Specifies that this session will not be marked when it is started. A session run with the -copywholelun -nomark command completes more quickly, but at the end of the session, the source and destination logical units are inconsistent. To make them consistent, you must run the session again.

When -nomark is used with the new option, SAN Copy/E starts an unmarked session that copies the contents of the source logical unit to any new destinations.

When -nomark is used with the all option, SAN Copy/E starts an unmarked session that copies the contents of the source logical unit to all destinations.


None.

Example naviseccli -h ss1_spa sancopy -start -name copy_lun_66

For SP ss1_spa, this command starts a copy session based on the copy descriptor named copy_lun_66.


Output If the FLARE running in the SP does not support the command, the CLI prints a Command is not supported error message to stderr. Other errors are



UNKNOWN_DESCRIPTOR_IDUNKNOWN_DESCRIPTOR_NAME SESSION_ALREADY_IN_PROGRESS



sancopy -stop Stops (terminates) a copy session

Description The naviseccli or navicli sancopy command -stop terminates the specified session. The session stops automatically when it is complete, so this command is not needed in the normal course of copy operations.



Format Use sancopy -stop with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -stop -descriptorid descriptor-id | -name name

where


Identifies the descriptor whose session you want to stop.


None.

Example naviseccli -h ss1_spa sancopy -stop -name copy_lun_66

For SP ss1_spa, this command stops the copy session with the copy descriptor name copy_lun_66.


sancopy -stop 4-49


Output If the version of FLARE running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other error messages are



UNKNOWN_DESCRIPTOR_IDUNKNOWN_DESCRIPTOR_NAME



sancopy -throttleChanges the I/O rate of an active copy descriptor

Description The naviseccli or navicli sancopy command with -throttle lets you change the throttle of an existing, running copy descriptor. The new throttle value is valid only while the session is running and will not change the value in the descriptor database.

To change the throttle value of an existing copy descriptor that is not running, use the -sancopy -modify -throttle command (see page 4-33)



Format Use sancopy -throttle with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -throttle -descriptorid descriptor-id | -name name n

where

-descriptorid descriptor-id | -name name

Identifies the descriptor whose throttle value you want to change.

n

is the new throttle value, ranging from 1 (slowest) to 10 (highest. The default value is 6.


None.

Examples naviseccli -h ss1_spa sancopy -info -name copy_lun_66 For SP ss1_spa descriptor copy_lun_66, this command displays information, including throttle information.

sancopy -throttle 4-51


naviseccli -h ss1_spa sancopy -throttle -name copy_lun_66 8

For SP ss1_spa descriptor copy_lun_66, these commands get information (including throttle value), then change the throttle value to 8.



DMF_NAME_AND_UID_SPECIFIEDDMF_NAME_OR_UID_REQUIREDDMF_INVALID_THROTTLE_VALUEDMF_UNKNOWN_DESCRIPTOR





sancopy -transfer Transfers a copy descriptor from the peer SP

Description The naviseccli or navicli sancopy command with -transfer moves the specified descriptor from the peer SP to the SP you specify in the command.

After transferring the copy descriptor, you can start a new session on the working SP using that descriptor.



Format Use sancopy -transfer with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -transfer -descriptorid descriptor-id | -name name

where


Identifies the descriptor you want to transfer to the working SP.


None.

Example naviseccli -h ss1_spb sancopy -transfer -name copy_lun_66

This command transfers the copy descriptor copy_lun_66 to the SP named ss1_spb.


sancopy -transfer 4-53



DMF_NAME_AND_UID_SPECIFIEDDMF_NAME_OR_UID_REQUIREDDMF_UNKNOWN_DESCRIPTORDMF_PEER_SP_ALIVE





sancopy -unmarkFor incremental sessions only. Removes the point-in-time copy from a marked incremental copy session

Description The naviseccli or navicli sancopy command with -unmark removes the point-in-time copy from a marked incremental copy session.

You cannot unmark a session if any of the session’s destination logical units have failed.



Format Use sancopy -unmark with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -unmark -descriptorid descriptorid | -name name

where


Identifies the session you want to unmark.


None.

Example naviseccli -h 10.11.22.33 sancopy -unmark -name monday

This command removes the mark from the incremental copy session named monday.


Output If the version of FLARE software running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other errors are


sancopy -updateconnections 4-55


sancopy -updateconnectionsUpdates connection and registration information

Description The naviseccli or navicli sancopy command with -updateconnections updates registration information for all attached storage systems.

You should run this command for each SP.



Format Use sancopy -updateconnections with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -updateconnections


None.

Examples naviseccli -h ss1_spa sancopy -updateconnections naviseccli -h ss1_spb sancopy -updateconnections

These commands update connections on both SPs, ss1_spa and ss1_spb.




sancopy -verifyEnsures that the SAN Copy/E software can access a logical unit

Description The naviseccli or navicli sancopy command with -verify ensures that the SAN Copy/E software can access a logical unit. You should issue the command to both SPs as one SP might have access, where the other does not.



Format Use sancopy -verify with naviseccli (described on page 4-5) or navicli (described on page 4-10) as follows:

sancopy -verify-wwn lun-wwn | -lunnumber sp-name lunnumber[-device devicename] [-log]

where

-wwn lun-wwn

Specifies the worldwide name of the logical units. You can specify more than one WWN.

-lunnumber sp-name lunnumber

Is an alternate way of specifying a logical unit. For sp-name, specify the SP hostname (or SP IP address). For lunnumber, specify the source or destination logical unit number. You can specify more than one LUN number.

-device devicename

Not supported for CX-Series storage systems.

-log

Logs events to the SP event log.

If SAN Copy/E cannot find a LUN on a remote storage system, use these events to help determine the reason.

sancopy -verify 4-57



None.

Examples naviseccli -h 11.12.13.14 sancopy -verify -wwn 60:06:01:FA:2C:09:00:00:2B:89:4C:E9:65:D7:11 -log

This example uses the LUN’s world wide name to verify if the LUN is reachable, and logs any events to the SP event log. If the LUN is reachable, the software displays the following message:

Storage device is reachable.

naviseccli -h 11.12.13.14 sancopy -verify -lunnumber 12.34.56.78 6 12.34.56.78 12

This example verifies two LUNs using the SP name and LUN number. If one or both LUNs are not reachable, the software displays a message similar to the following:

Error: sancopy command failed

Error returned from AgentSP A: CPM unable to locate device. Check that the device with this WWN exists (0x712ac007)


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 Command Line Interfaces Reference

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 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 copy 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 Command Line Interfaces Reference

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 Command Line Interfaces Reference i-1

AAccess Logix, defined 1-4activate command (admhost) 3-3admhost

about 3-2activate command 3-3command functions 3-2deactivate command 3-3flush command 3-4help command 3-4list command 3-4requirements 3-2session overview 4-2

admhost utility, defined 1-2Agent

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

arguments, spaces in 4-9, 4-12

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-9CLI

Javabasic commands 4-5spaces in arguments 4-9

CLI subcommands-create 4-14-destinfo 4-19-duplicate 4-23-info 4-25-modify 4-33-pause 4-38-remove 4-39-resume 4-41-settings environment parameters, setting

with CLI 4-43-start 4-46-stop 4-48-throttle 4-50-transfer 4-52-updateconnections 4-55-verify 4-56

CLI, environment variablesRaidAgentDevice 4-13RaidAgentHost 4-13RaidAgentTimeout 4-13

CLI, RaidAgent environment variables 4-12clone, SnapView, defined 1-2command functions, admhost 3-2command line format, spaces in 4-9, 4-12copy descriptor

creating (-create) 4-14getting information (-info) 4-25

-create subcommand 4-14Customer support B-3Customer Support Center B-7

Index

EMC SAN Copy/E Command Line Interfaces Referencei-2

Index

Ddeactivate command (admhost) 3-3-destinfo subcommand 4-19diagnostics, navicli command 4-13domain, defined 1-2-duplicate subcommand 4-23

Eenvironment parameters, setting 4-43

Ffailures, session, handling A-2features, SAN Copy/E 1-6flush command (admhost), about 3-4full sessions

defined 1-2function switches, admhost 3-7

Hhelp command (admhost) 3-4

I-info command 4-25

Llist command (admhost), about 3-4logical unit

defined 1-3LUN

destination, information (-destinfo command) 4-19

LUN pool, reserved, defined 1-3lun_activate command (admhost) 3-3lun_deactivate command (admhost) 3-3lun_flush command (admhost) 3-4lun_list command (admhost) 3-4

M-mark subcommand 4-31-modify subcommand 4-33

Nnavicli command 4-10

command switches, see individual CLI subcommands

diagnostics, see error codesformat 4-10

P-pause subcommand 4-38portal, defined 1-3ports, SAN Copy/E, connecting to CLARiiON

Storage Groups 2-10

RRaidAgent environment variables 4-12remote storage system, defined 1-3-remove subcommand 4-39requirements, admhost 3-2reserved LUN pool, defined 1-3-resume subcommand 4-41

SSAN Copy/E

basic configuration requirements and restrictions 2-2

features and benefits 1-6introduction 1-5operations overview 4-2session overview 4-2sessions

checkpoint interval, defined 1-2defined 1-2full, defined 1-2preparing CLARiiON storage system for

2-9preparing logical units 3-5

software components 1-8software, defined 1-3zoning requirements and recommendations

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

CLARiiON Storage Groups 2-10sancopy CLI subcommand, see Chapter 4session, starting 4-46session, stopping 4-48

i-3EMC SAN Copy/E Command Line Interfaces Reference

Index

set command 4-13-settings subcommand 4-43shared storage, defined 1-4snapshot, SnapView, defined 1-4SnapView

clone, 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-6Windows 3-6

spaces in arguments 4-12-start subcommand 4-46-stop subcommand 4-48Storage Groups, connecting SAN Copy/E ports

2-10storage system

CLARiiON, preparing for SAN Copy/E session 2-9

SAN Copy/E, defined 1-3shared, defined 1-4

TTechnical support B-3-throttle subcommand 4-50-transfer subcommand 4-52

U-unmark subcommand 4-54unshared storage systems, defined 1-4-updateconnections subcommand 4-55

V-verify subcommand 4-56VMware server

destination LUN prerequisites 4-15prerequisites for copy sessions 2-2source LUN prerequisites 4-15

Zzoning

introduction 2-4recommendations

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

connections 2-8

EMC SAN Copy/E Command Line Interfaces Referencei-4

Index

EMC SAN Copy/E Command Line Interfaces Reference · PDF fileEMC SAN Copy/E Command Line...

Documents

Transcript of EMC SAN Copy/E Command Line Interfaces Reference · PDF fileEMC SAN Copy/E Command Line...