EMC SAN Copy Command Line Interfaces: P/N 069001189 Rev A01

EMC SAN Copy Command Line Interfaces ADMINISTRATORS GUIDE
P/N 069001189 REV A01
EMC Corporation
Corporate Headquarters: Hopkinton, MA 01748-9103 (800) 424-EMC2 http://www.EMC.com
Copyright 2003 EMC Corporation. All rights reserved.

Published February, 2003 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 Information
EMC2, EMC, CLARiiON, Navisphere, and Symmetrix are registered trademarks and PowerPath, Access Logix, MirrorView, SAN Copy, and SnapView are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.
ii
EMC SAN Copy Command Line Interfaces Administrators Guide
Contents
Preface.............................................................................................................................. v Chapter 1 Introducing SAN Copy and Its Command Line Utilities
Finding Current Information ......................................................... 1-2 Terminology...................................................................................... 1-3 Introducing SAN Copy Software .................................................. 1-5 SAN Copy Features and Benefits .................................................. 1-7 SAN Copy Software Components................................................. 1-9 SAN Copy Operations Overview ................................................ 1-10
Chapter 2
SAN Copy Configuration Guidelines

SAN Copy Configuration Requirements and Restrictions ........ 2-2 SAN Copy Zoning Requirements and Recommendations ........ 2-4 Requirements ............................................................................ 2-4 Recommendations .................................................................... 2-4 Making Logical Units Accessible to the SAN Copy Port ........... 2-5 Registering SAN Copy Ports With Target Systems............. 2-5 Connecting SAN Copy Ports to CLARiiON Storage Groups........................................................................................ 2-6 Connecting SAN Copy Ports to Symmetrix Volumes......... 2-7
Chapter 3
Using the admhost Utility with SAN Copy

About admhost for SAN Copy ...................................................... 3-2 admhost SAN Copy Command Functions .................................. 3-3 admhost Function Switches ................................................... 3-5 Preparing Logical Units for a SAN Copy Session ....................... 3-6
iii
Contents
Chapter 4
SAN Copy CLI Commands

Navicli SAN Copy Command Functions..................................... 4-2 About Navisphere CLI Commands .............................................. 4-4 navicli ................................................................................................ 4-4 sancopy -create................................................................................. 4-8 sancopy -destinfo........................................................................... 4-11 sancopy -duplicate......................................................................... 4-13 sancopy -info .................................................................................. 4-14 sancopy -modify ............................................................................ 4-17 sancopy -pause............................................................................... 4-20 sancopy -remove............................................................................ 4-21 sancopy -resume ............................................................................ 4-23 sancopy -settings............................................................................ 4-25 sancopy -start ................................................................................. 4-27 sancopy -stop.................................................................................. 4-28 sancopy -throttle ............................................................................ 4-29 sancopy -transfer ........................................................................... 4-31 sancopy -updateconnections........................................................ 4-32 sancopy -verify............................................................................... 4-33
Appendix A
SAN Copy Error Codes

SAN Copy Error Codes ................................................................. A-2
Index ................................................................................................................................ i-1
iv
Preface
This manual describes the two command line interfaces to EMC SAN Copy 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 ControlCenter Navisphere Manager) to configure and run the SAN Copy software. This manual assumes that you are familiar with the operating system running on the servers you will manage and with storage-system components and configurations. How This Manual Is Organized Chapter 1 Chapter 2 Chapter 3 Chapter 4 Appendix A Introduces terminology and the software products. Explains the basic requirements, restrictions and configuration guidelines for using SAN Copy. Explains admhost commands that the operating system uses to manage devices with SAN Copy. Describes the CLI commands that SAN Copy uses to manage SAN Copy sessions. Describes SAN Copy error codes.
Preface
Related Manuals EMC SAN Copy 1.X for EMC ControlCenter Navisphere 6.X Administrators Guide (P/N 069001188) EMC ControlCenter Navisphere Manager 6.X Administrators Guide (P/N 069001125) EMC Storage Systems CX400-Series and CX-600-Series Storage System Configuration Planning Guide (P/N 014003113) EMC FC4700-2 Storage System Configuration Planning Guide (P/N 014003087) Conventions Used in This Manual This manual uses the following format conventions: 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. Represents variables for which you supply the values; for example, the name of a directory or file, your username or password, and explicit arguments to commands. Represents a system response (such as a message or prompt), a file or program listing. Represents a menu path. For example, Operations -> Poll All Storage Systems tells you to select Poll All Storage Systems on the Operations menu. Encloses optional entries. Separates alternative parameter values; for example: LUN-name | LUN-number means you can use either the LUN-name or the LUN-number.
This typeface
This typeface x -> y
[ ] |
vi
Preface
Where to Get Help
For questions about technical support and service, contact your service provider. If you have a valid EMC service contract, contact EMC Customer Service at: United States: (800) 782-4362 (SVC-4EMC) Canada: Worldwide: (800) 543-4782 (543-4SVC) (508) 497-7901
Follow the voice menu prompts to open a service call, then select CLARiiON Product Support. Sales and Customer Service 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 techpub_comments@emc.com with your opinions of this guide.
vii
Preface
viii
Invisible Body Tag
1
Introducing SAN Copy and Its Command Line Utilities
This chapter introduces the SAN Copy software and its command line utilities: admhost, with commands that the operating system uses to manage SAN Copy devices; and the CLI, with commands that manage SAN Copy sessions. Major topics are

Finding Current Information ...........................................................1-2 Terminology ........................................................................................1-3 Introducing SAN Copy Software.....................................................1-5 SAN Copy Features and Benefits ....................................................1-7 SAN Copy Software Components ...................................................1-9 SAN Copy Operations Overview ..................................................1-10
1-1
Finding Current Information

To ensure that you have the most up-to-date information about the EMC SAN Copy software, EMC posts the release notes for this software on the EMC Powerlink website. We recommend that you download a copy of the release notes before you start the SAN Copy software.
Accessing EMC Powerlink
To access EMC Powerlink use the following url: http://powerlink.emc.com After you log in, select Support (or Services) Document Library CLARiiON CLARiiON Fibre Channel Storage CLARiiON FC Software, and find the EMC SAN Copy and Admhost Release Notes (P/N 085090685).
1-2
Terminology
Term Access Logix option admhost utility checkpoint interval CLI clone Meaning See shared storage system. The admhost utility is an executable program that you can run interactively via script. It runs on Microsoft Windows NT, and Windows 2000. A user-defined time interval that lets SAN Copy resume an interrupted session from the last checkpoint, rather than having to start the session over. EMC ControlCenter Navisphere Command Line Interface. A copy (local mirror) of a LUN. When synchronized, it remains a bit-for-bit copy of its source LUN. To access the clone, you must fracture it. Then, after performing the desired operations (such as data modeling or backup), you can start synchronizing it again. Clone functionality is provided with EMC SnapView software. A set of parameters you create under a unique name that specifies the source and destination devices and other settings for a SAN Copy session. Each copy descriptor is stored in an SP. You start a session using the copy descriptor. A logical unit to which SAN Copy is copying the source data. On a CLARiiON storage system, this device is called a LUN; on a Symmetrix system, it is called a volume. 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. EMC ControlCenter Navisphere Event Monitor. EMC Navisphere Agent that runs on a storage-system server. A storage device that resides on a storage system, stores data and is independent of storage-system type. For example, on a CLARiiON storage system, this device is called a LUN; on a Symmetrix system, a volume. CLARiiON term for logical unit. A Host Agent or SP Agent managed by Navisphere management software. A storage system managed by Navisphere management software. EMC ControlCenter Navisphere Manager. 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.
copy descriptor
destination logical unit
domain
Event Monitor Host Agent logical unit
LUN managed Agent managed storage system Manager portal
Terminology
1-3
Term pre-FC4700 systems SAN
Meaning An FC4500, FC5300, FC5500, FC5700, or C-Series storage system. 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. Software running on a SAN Copy storage system that lets you copy logical unit information between SAN Copy storage systems and other storage systems, or within a storage system. An SP port initiator on a SAN Copy storage system that is participating in a SAN Copy session. A descriptor that stores all data pertaining to a unique copy process, such as session name, session ID, source and destination logical units, and session status. You must start the session to begin the copy process. A storage system with SAN Copy software installed. For example, you can install SAN Copy on a CX400, CX600, or FC4700-Series storage system (refer to the SAN Copy release notes for a complete list of supported storage systems) 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. A point-in-time image of a LUN. A snapshot occupies no disk space, but appears as a normal LUN to secondary hosts. Snapshot functionality is provided with EMC SnapView software. A logical unit from which SAN Copy copies data. On a CLARiiON storage system, this device is called a LUN. EMC Navisphere Agent that runs on the SPs in a CX-Series or FC4700-Series storage systems. Software that runs in a storage system or portal server and lets a person manage it over a network. A storage system with logical units that are participating in a SAN Copy session, but is not running SAN Copy software. This parameter controls the I/O rate for a SAN Copy session. You can set the session throttle to a value between 1 and 10 where 1 is the lowest rate and 10 is the highest. The default throttle value is 6. A storage system without the EMC Access Logix option. A logical unit on a Symmetrix storage system. A zone limits access to specific logical units in a storage system.; thereby increasing security and decreasing network traffic.
SAN Copy
SAN Copy port SAN Copy session
SAN Copy storage system
shared storage system
snapshot
source logical unit SP Agent Storage Management Server software target storage system throttle value
unshared storage system volume zone
1-4
Introducing SAN Copy Software

EMC SAN Copy software (referred to as SAN Copy later in this document) runs on a SAN Copy storage system (storage system with SAN Copy installed). SAN Copy can copy data between CLARiiON storage systems, within CLARiiON storage systems, and between CLARiiON and Symmetrix storage systems. It can copy data directly from a source logical unit on one storage system to destination logical units on another, without using host resources. SAN Copy can perform multiple copies each in its own copy session simultaneously. The RAID type of the logical units participating in a copy session do not have to be the same; that is, the source and destination logical units can be different RAID types. SAN copy creates a complete copy of the source logical unit. Therefore, the source and destination logical units must be

the same size, or the destination logical unit must be larger. accessible by the same operating system. inactive (offline and/or unmounted) during the copy process. No writes to the source logical unit (unless you use replication software), and no application I/O with the destination logical unit can occur during the copy session. owned by the same SP, for a copy within one storage system.
SAN Copy runs in the storage-system storage processors (SPs), not on host servers. The host reserves processing resources for production applications while the SPs undertake the task of copying data. You can use SAN Copy for the following tasks:

One-time data migration Routine copying of data for application testing Content distribution
To manage SAN Copy sessions, you can use the SAN Copy Command Line Interface (described in this manual), or the GUI based Navisphere Manager described in EMC SAN Copy for EMC ControlCenter Navisphere 6.X Administrators Guide, P/N 069001188.
Introducing SAN Copy Software
1-5
Figure 1-1 shows two logical units being copied to two different storage systems. One SAN Copy session is copying LUN 15 in the CX600 storage system to volume 32 in the Symmetrix storage system. The second SAN Copy session is copying LUN 6 in the FC5300 storage system to LUN 14 in the CX600 storage system. In this example, SAN Copy software is required only on the CX600 storage system. All copy processing occurs in the SPs, freeing the servers for applications and other tasks.
Server
Server
Server
Switch Fabric
Switch Fabric
LUN 6 LUN 14 LUN 15 CX-Series or FC4700-Series Storage System FC5300 Storage System Volume 32 Volume 33 Symmetrix Storage System
EMC2448
Figure 1-1
Sample SAN Copy Sessions Between Storage Systems
For an example of two LUNs being copied within the same CLARiiON storage system, see Figure 2-2 on page 2-3.
1-6
SAN Copy Features and Benefits

The SAN Copy software has the following features:
A storage-system based data mover application that uses a SAN (Storage Area Network) to copy data between storage systems. An easy-to-use web-based application for configuring and managing SAN Copy. Software that you can use in conjunction with replication software, allowing I/O with the source logical unit to continue during the copy process. Simultaneous sessions that can copy data to multiple CLARiiON and Symmetrix storage systems
Storage-System Based Data-Mover Application SAN Copy is a storage-system based data-mover application that uses a SAN (Storage Area Network) to copy data between storage systems. Since SAN Copy runs on the storage systems, this eliminates the need to move data to and from the attached hosts and reserves host processing resources for users and applications. Since the host is not involved in the copy process, and the data migration takes place on the SAN, the copy process is much faster than the LAN-based, host-involved copy process. Easy-to-use Web-Based Application SAN Copy is an integrated part of Navisphere Manager, the easy-to-use web-based management tool for CLARiiON storage systems. Manager lets you select the SAN Copy source and destination logical units, create SAN Copy sessions and then manage these sessions.
SAN Copy Features and Benefits
1-7
Use with Replication Software If the storage system containing the source logical unit has device replication technology, such as EMC SnapView or EMC TimeFinder software, SAN Copy can use a snapshot, clone, or Symmetrix BCV (business continuation volume) as its source logical unit allowing I/O with the source logical units for the snapshot, clone or BCV source logical unit to continue during the copy process.
You must fracture a SnapView clone before using it as a source LUN in a SAN Copy session. For more details, refer to the SnapView documentation and online help.
Simultaneous Sessions Between Multiple Storage Systems SAN Copy lets you have more than one session active at the same time. The number of supported concurrent active sessions and the number of logical units per session depends on the storage-system type.
Maximum Number of Concurrent Sessions per System 8 16 16 Maximum Number of Destination Logical Units per Session 50 100 100
Storage-System Type CX400 CX600 FC4700 Series
1-8
SAN Copy Software Components

SAN Copy consists of the following software components:

Software that provides the SAN Copy functionality, and resides on a SAN Copy storage system. Graphical User Interface (GUI) - Navisphere Manager, which you must order separately. Navisphere Command Line Interface (CLI) and Host Agent, which ship as part of the Navisphere Host Agent package.
SAN Copy Software Components
1-9
SAN Copy Operations Overview

The following steps explain how to use SAN Copy. 1. Set up SAN Copy. This procedure may include steps for zoning switches, registering SAN Copy initiator ports, adding logical units to Storage Groups, and connecting the SAN Copy ports to Storage Groups and volumes. For zoning requirements, see SAN Copy Zoning Requirements and Recommendations on page 2-4. For registering SAN Copy ports, see Registering SAN Copy Ports With Target Systems on page 2-5. For adding logical units to Storage Groups and connecting ports to Storage Groups and volumes, see Connecting SAN Copy Ports to CLARiiON Storage Groups on page 2-6 and Connecting SAN Copy Ports to Symmetrix Volumes on page 2-7. 2. On the SAN Copy storage system, create a SAN Copy copy descriptor. This descriptor includes the source and destination logical units that will participate in a SAN Copy session., and all needed parameters for the SAN Copy session. To create a SAN Copy descriptor, use the CLI command sancopy -create (see page 4-8). 3. On the host that connects to the destination logical unit, make sure the destination logical unit is unmounted. With Windows hosts, you can issue the admhost lun_deactivate command, which makes the logical unit invisible to the operating system, essentially unmounting it. The admhost commands are explained in Chapter 3. With UNIX hosts, you must unmount the file system(s) on the logical unit. 4. On the host that connects to the source logical unit, make sure the source logical unit is unmounted. On a Windows host connected to the source logical unit, issue the command admhost flush (if you want to allow reads from the source) or admsnap lun_deactivate (to dismount the source and make it inaccessible).
1-10
If the system containing the source logical unit has device replication technology, such as EMC SnapView or EMC Timefinder, SAN Copy can use a snapshot, clone or Symmetrix BCV (business continuation volume) as its source logical unit -- allowing I/O with the source for the snapshot, clone and BCV to continue during the copy process. For more details, refer to the SnapView or TimeFinder documentation and online help.
CAUTION The admhost flush command does not prevent write access to the source logical unit. You must quiesce all writes to the source logical unit prior to starting and during a SAN Copy session in order to prevent data loss or data corruption. If you need to keep writing to the source logical unit, use a SnapView snapshot or a Symmetrix BCV as the SAN Copy source logical unit. 5. On the production hosts storage system, start a SAN Copy session. Use the CLI sancopy -start command, or you can specify -start in the sancopy -create command (see page 4-27). 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 (steps 3 and 4 above). 6. Let the copy session complete. 7. On both hosts, make both the source 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 SAN Copy completes the copy session, we recommend that you move any identical LUNs to different Storage Groups.
With Windows hosts, you can issue the admhost lun_activate command, which mounts the drive and returns a drive letter you can use for future operations (see page 3-2). With UNIX hosts, admhost lun_activate does nothing. It is provided for script compatibility only. Use the commands your operating system normally uses to discover new logical units. For future SAN Copy sessions that use the CLI and/or admhost (possibly in a command script), you need only steps 3 through 7.
SAN Copy Operations Overview
1-11
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 CLI commands Chapter 4.
1-12
Invisible Body Tag
2
This chapter lists the basic requirements, restrictions and configuration guidelines for using SAN Copy. Major sections are

SAN Copy Configuration Requirements and Restrictions ..........2-2 SAN Copy Zoning Requirements and Recommendations ..........2-4 Making Logical Units Accessible to the SAN Copy Port .............2-5
2-1
SAN Copy Configuration Requirements and Restrictions

This section describes the configuration requirements and restrictions for copying data between CLARiiON storage systems, between CLARiiON and Symmetrix storage systems, and within CLARiiON storage systems. If you will be copying data between CLARiiON storage systems, or between CLARiiON and Symmetrix storage systems, the following requirements must be met before you start a SAN Copy session.
One of the storage systems participating in the copy session must be a SAN Copy storage system. You must correctly zone SAN Copy ports to target storage systems so that SAN Copy can have access to these systems (see SAN Copy Zoning Requirements and Recommendations on page 2-4).
SAN Copy ports act as host initiators to the target storage systems.
Either the source logical unit, destination logical units or both must reside on a SAN Copy storage system.
If the source logical unit resides in the SAN Copy storage system, you can copy data to one or many destination logical units on one or many storage systems. None of the target storage systems require the SAN Copy software. If the source logical unit does not reside in the SAN Copy storage system on which you are creating the session, you must select all destination logical units from the storage system that owns the session.
When copying data to a Symmetrix system, use the navicli -lunmapinfo command to obtain the World Wide Name (WWN) of any Symmetrix volumes that you want to include in the SAN Copy session. The Navisphere Host Agent must be installed on the hosts that own the volumes. For the required Host Agent revision, refer to the SAN Copy release notes, available on Powerlink (see Finding Current Information on page 1-2). In order for logical units to participate in a SAN Copy session, they must be accessible to the participating SAN Copy port. See Making Logical Units Accessible to the SAN Copy Port on page 2-5.
2-2
If you will be copying data from one LUN to one or many LUNs within the same CLARiiON storage system, the following requirements must be met before you start a SAN Copy session.

The storage system must be a SAN Copy storage system. The source and all destination LUNs participating in a copy session must belong to the same SP.
If you need to copy between LUNs owned by different SPs, you must trespass either the source or destination LUNs before starting the session.
Figure 2-2 shows LUN 12 being copied to LUN 23 and LUN 14 being copied to LUN 25 within the same CLARiiON storage system.
Server
Switch Fabric
LUN 12 LUN 14 LUN 23 LUN 25
CX-Series or FC4700-Series Storage System

EMC2450
Figure 2-2
Sample SAN Copy Session Within a CLARiiON
SAN Copy Configuration Requirements and Restrictions
2-3
SAN Copy Zoning Requirements and Recommendations

This section describes basic SAN Copy zoning requirements and recommendations.
Zoning is not required for copying data within a CLARiiON storage system
Requirements
Currently, SAN Copy and MirrorView software cannot share the same SP port (refer to the SAN Copy release notes for confirmation).
Zone at least one port from each SP of the SAN Copy storage system to any other storage systems participating in SAN Copy sessions. Zone each participating SAN Copy port to one or more ports of each SP in the target storage systems. Create a single zone that includes multiple SAN Copy and target SP ports; create multiple zones with a single SAN Copy/target SP port; or a create a mixture of both zone types.
Recommendations
If performance is most important, zone multiple SAN Copy ports to a target storage system. SAN Copy allows multiple sessions to share a single port, but, if there are multiple ports available, SAN copy will spread multiple sessions across available SAN Copy ports to maximize total throughput. If preserving host HBA connections is most important because there are a large number of hosts connecting to a target storage system, zone only necessary SAN Copy ports to that storage system. Each SAN Copy port zoned to a target SP port registers itself as an initiator with that SP port, thereby reducing the available host HBA connections. If availability is most important, zone multiple SAN Copy ports to a target storage system. A SAN Copy session will fail if the port/path used by the session fails. However, if other ports/paths are available, you can re-start the session.
2-4
Making Logical Units Accessible to the SAN Copy Port

Before you can use SAN Copy to copy data between storage systems, SAN Copy ports must have access to participating logical units in the target storage systems. To make this happen, you must register each selected SAN Copy port to ports of the target storage systems. Once the registration process is complete, you can connect the SAN Copy port to a Storage Group on the target CLARiiON storage system, or to volumes on a Symmetrix storage system.
Registering SAN Copy Ports With Target Systems

To register SAN Copy ports, do the following: 1. Make sure that you zone the SAN Copy ports with the correct ports on target storage systems that will participate in a copy session (see SAN Copy Zoning Requirements and Recommendations on page 2-4). 2. Register the SAN Copy ports with any other SP ports in the same zone using the navicli -h spname sancopy -updateconnections command (see page 4-32). If the target system is a CLARiiON storage system, the SAN Copy ports register with each storage system, and the software adds a record for each SAN Copy port to the storage systems host initiator table. Navisphere Manager displays an entry for each registered SAN Copy port in the Connectivity Status dialog box, and the SAN Copy Summary dialog box. If the target system is a Symmetrix storage system, the SAN Copy ports log in to each storage system and register their WWNs with the VCM database. ESN Manager displays each registered SAN Copy port as a host entry. 3. Verify that the SAN Copy 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 storage system: navicli -h spname -port -list where spname is the name of an SP in the SAN Copy storage system.
2-5
Connecting SAN Copy Ports to CLARiiON Storage Groups

If all participating logical units of a target storage system already belong to the same Storage Group, you can connect SAN Copy 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 SAN Copy ports to them. This is the only time we recommend placing the same logical unit in more than one Storage Group.
For more information on the following CLI commands, refer to EMC ControlCenter Navisphere Command Line Interface (CLI) Administrators Guide, P/N 069001038.
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 (with information from the previous navicli -port -list command) to add the SAN Copy ports to Storage Groups: navicli -h spname storagegroup -setpath -gname storagegroupname-hbauid hbawwn -sp a or b -spport portnumber where
spname is the storagegroupname is the hbawwn is the a or b is the portnumber is the
IP address of the SP on the storage system to which the Storage Group belongs. name of the Storage Group to which you want to connect World Wide Name of the SAN Copy port (from the -portlist command) SP that owns the Storage Group the ID of the SP port hat owns the Storage Group (from the -portlist command)
2-6
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
hostname is the ipaddress is the
name of the host that has access to the LUNs in the Storage Group IP address of the host that has access to the LUNs in the Storage Group
What Next?
You are now ready to create SAN Copy descriptors (see sancopy -create on page 4-8).
Connecting SAN Copy Ports to Symmetrix Volumes

Use ESN Manager to assign Symmetrix volumes to the SAN Copy port entries. This is the same as assigning volumes to the host initiator. You are now ready to create SAN Copy descriptors (see sancopy -create on page 4-8).
2-7
2-8
Invisible Body Tag
3
This chapter explains how to use the admhost utility.

About admhost for SAN Copy ........................................................3-2 admhost SAN Copy Command Functions.....................................3-3 Preparing Logical Units for a SAN Copy Session .........................3-6
3-1
About admhost for SAN Copy

The admhost utility is an executable program that you can run interactively via script. It runs on Microsoft Windows NT, and Windows 2000. The admhost commands can activate and deactivate the source and destination logical units being used in a SAN Copy session, and flush data from operating system buffers to ensure that the information on the source logical unit is current.
Currently, admhost is only supported on the following Microsoft Windows platforms: Windows NT and Windows 2000. For the supported versions
of these operating systems, see the SAN Copy and admhost Software Release Notes.
3-2
admhost SAN Copy Command Functions

Table 3-1 lists the admhost commands and describes their functions in SAN Copy sessions.
Table 3-1
admhost Functions and Descriptions Syntax and Examples admhost lun_activate [-l lun-worldwidename] [-d drive-letter] Examples: admhost lun_activate Scanning for new devices. Completed scanning for new devices. admhost lun_activate -l 60:06:01:EF:74:60:00:00:CD:BD:FE:45:7 7:9D:D7:11 -d v: Scanning for new devices. Successfully assigned v: to CLARiiON LUN 60:06:01:EF:74:60:00:00:CD :BD:FE:45:77: 9D:D6:11. Completed scanning for new devices. admhost lun_deactivate -o drive-letter Example: admhost lun_deactivate -o F: Deactivated the CLARiiON device on F:
Function admhost lun_activate
Description On a Windows NT or Windows 2000 host, the admhost lun_activate command tells the operating system to scan for new copy LUNs and to mount each one (make it available to Windows). The software assigns a drive letter to every new device it finds. Use admhost lun_activate on the hosts connected to both the source and destination LUNs after a copy completes to make the LUN available/visible to the hosts. If you omit switches, lun_activate simply scans for new devices and assigns drive letters to any new LUNs that have a proper file system type on them. The software assigns the drive letters according to the next available drive letter on the Windows hosts. If you include the -l and -d switches, you can change the specified LUN WWN to a drive letter. The admhost command is not supported on a UNIX host. Use the commands your operating system normally uses to discover new LUNs.
admhost lun_deactivate
On a Windows NT or Windows 2000 host, admhost lun_deactivate flushes all host buffers, unmounts the LUN, and removes the drive letter assigned by admhost lun_activate. It essentially dismounts a mounted LUN. With Windows, use admhost lun_deactivate (or flush) command on the host that connects to the destination LUN before starting a copy session. The admhost command is not supported on a UNIX host. Use the sync command to flush buffers. Then unmount the file system on the copy LUN.
3-3
Function admhost flush
Description On a Windows host, the command flushes all data and clears all buffers. However, unlike admhost lun_deactivate, it does not remove the drive letter, and allows reads from the LUN to continue. Use admhost flush or admhost lun_deactivate for a source LUN before starting a SAN Copy session to ensure that all cached data has been written to disk.
Syntax and Examples admhost lun_flush -o drive-letter Examples: admhost lun_flush -o F: Flushed F:.
The admhost command is not supported on a UNIX host. Use the commands your operating system normally uses to flush buffers. admhost lun_list On a Windows host, admhost lun_list displays the mapping information of the host devices such as drive letters or physical drives and their corresponding LUN worldwide names (WWNs). You can use admhost lun_list with the -l switch to display the current drive letter mapped to the specified LUN WWN or use the -d switch to display the LUN WWN mapped to the specified drive. Using admhost lun_list and lun_activate in sequence, you can obtain the lun wwn info and change the drive letter currently mapped to the desired drive with admhost lun_activate. admhost lun_list [[-l lun-world-wide-name] [-d drive-letter | physicaldrive]] [-a driveletter | physicaldrive] Examples: admhost lun_list F:=>60:06:01:EF:74:60:00: 00:A2:0D:40:24:C2:B5:D6:11 H: => 60:06:01:EF:74:60:00:00:CD :BD:FE:45:77:9D:D6:11 admhost lun_list -a driveletter F:=>60:06:01:EF:74:60:00: 00:A2:0D:40:24:C2:B5:D6:11 admhost lun_list -a physicaldrive PhysicalDrive1 => 60:06:01:EF:74:60:00:00:A2 :0D: 40:24:C2:B5:D6:11 PhysicalDrive2 => 60:06:01:EF:74:60:00:00:CD :BD: FE:45:77:9D:D6:11
admhost help
This command displays admhost usage information
admhost help
3-4
admhost Function Switches

-a drive-letter | physicaldrive Displays mapping information. In lun_list, use -a in conjunction with -l to display all LUN mapping information with either drive letters or physical drives. When used with -d, the -a switch is ignored. Changes device mapping or displays mapping information. In admhost lun_activate, the -d switch used with -l lets you change the specified LUN WWN to a desired drive letter. In admhost lun_activate, you can use only drive letter format. In admhost lun_list, you can use either a drive letter or a physical drive specifier. Displays the drive associated with a worldwide name (WWN) In admhost lun_list, displays the drive mapped to a WWN. For the name, use the following format:
-d drive-letter | physicaldrive
-l lun-worldwidename
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:X X:XX
XX should be digits 0-9 and/or letters A-F. Place an extra 0 in front of any single digit or a single character; for example, 01:02:03:04:0A -o drive-letter | physicaldrive Identifies the output drive. In admhost lun_deactivate, you can use only drive letter format.
What Next?
Before you start a SAN Copy session, complete the steps described in the next section, Preparing Logical Units for a SAN Copy Session.
3-5
Preparing Logical Units for a SAN Copy Session

Before you start a SAN Copy session, you must prepare the source and destination logical units that will be participating in the session. For a SAN 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 servers operating system.
CAUTION You must follow this procedure explicitly to avoid data loss or data corruption. 1. From the hosts connected to any destination logical units, flush the host buffers and disconnect the destination logical units from the host by doing one of the following:
If the destination logical units are not mounted, ignore this step.
On a Windows 2000 or Windows NT host, use the following command: admhost lun_deactivate -o destination-drive letter For example, to flush the host buffers and disconnect any logical units on drive D:, enter the following command: admhost lun_deactivate -o D: On a UNIX host, unmount the file system on any destination logical units. On a Novell NetWare host, use the dismount command on the volume to dismount the file system. 2. From the host connected to the source logical unit, stop all I/O to the source logical unit.
In addition to a LUN or volume, SAN Copy can use a SnapView snapshot, a fractured clone, or a TimeFinder BCV (business continuation volume) as its source logical unit allowing I/O with the source logical units for the snapshot, clone or BCV source logical unit to continue during the copy process
3. From the host connected to the source logical unit, flush the host buffers and disconnect the source logical unit from the host by doing one of the following.
3-6
If you want to maintain read access to the source logical unit, skip step 3, and proceed to step 4.
On a Windows 2000 or Windows NT host, use the following command: admhost lun_deactivate -o source-drive letter For example, to flush the host buffers and disconnect any logical units on drive D:, enter the following command: admhost lun_deactivate -o D: On a UNIX host, unmount the source logical unit. 4. If you want to maintain read access to the source logical unit, do one of the following:
CAUTION Neither of the following steps prevents write access to the source logical unit. You must quiesce all writes to the source logical unit prior to starting and during a SAN Copy session in order to prevent data loss or data corruption. If you need to keep writing to a source logical unit, use a SnapView snapshot or a Symmetrix BCV as the source logical unit. On a Windows 2000 or Windows NT host, use the following command: admhost flush -o source-drive letter For example, to flush the host buffers and maintain read access to logical units on drive D:, enter the following command: admhost flush -o D: On a UNIX host, unmount and then mount the source logical unit.
What Next?
For an explanation of SAN Copy CLI commands, continue to Chapter 4.
Preparing Logical Units for a SAN Copy Session
3-7
3-8
Invisible Body Tag
4
This chapter explains the CLI commands that manage SAN Copy software.
The commands in this chapter function only with a storage system that has the optional SAN Copy software installed.
Topics are

Navicli SAN Copy Command Functions .......................................4-2 sancopy -create ...................................................................................4-8 sancopy -destinfo ............................................................................. 4-11 sancopy -duplicate ...........................................................................4-13 sancopy -info.....................................................................................4-14 sancopy -modify...............................................................................4-17 sancopy -pause .................................................................................4-20 sancopy -remove ..............................................................................4-21 sancopy -resume...............................................................................4-23 sancopy -settings ..............................................................................4-25 sancopy -start....................................................................................4-27 sancopy -stop ....................................................................................4-28 sancopy -throttle...............................................................................4-29 sancopy -transfer..............................................................................4-31 sancopy -updateconnections ..........................................................4-32 sancopy -verify .................................................................................4-33
4-1
Navicli SAN Copy Command Functions

The EMC ControlCenter Navisphere CLI provides one of the two interfaces to the SAN Copy software. The Navisphere Manager GUI provides the other. The CLI command is navicli sancopy and you specify functions with switches. The sancopy command functions, listed alphabetically, are

navicli sancopy -create navicli sancopy -destinfo navicli sancopy -duplicate navicli sancopy -info navicli sancopy -modify navicli sancopy -pause navicli sancopy -remove navicli sancopy -resume navicli sancopy -settings navicli sancopy -start navicli sancopy -stop navicli sancopy -throttle navicli sancopy -transfer navicli sancopy -updateconnections navicli sancopy -verify
The sancopy CLI functions are listed functionally, in the order you would perform them, in the following table.
4-2
Table 4-1
Navicli sancopy Command Functions, Listed in Order of Use
Command
Description Essential Functions (in Order Performed)
navicli sancopy -create navicli sancopy -start
Creates a SAN Copy copy descriptor Starts a SAN Copy session based on copy descriptor information
Optional Status Functions (Alphabetically)

navicli sancopy -destinfo navicli sancopy -info Displays information on a particular session from the destination point of view Displays information on all SAN Copy sessions or displays attributes for a particular session. Stops a SAN Copy session Ensures that the SAN Copy software can access a logical unit
navicli sancopy -stop navicli sancopy -verify
Optional Reconfiguration Functions (Alphabetically)

navicli sancopy -duplicate Creates a duplicate copy descriptor
navicli sancopy -modify navicli sancopy -pause
Changes parameters in a copy descriptor Pauses a SAN Copy session
navicli sancopy -remove navicli sancopy -resume navicli sancopy -throttle navicli sancopy -transfer navicli sancopy -settings navicli sancopy -updateconnections
Deletes a copy descriptor Continues a paused, stopped or failed session Changes the throttle (execution rate) of an existing, running session. Transfers control of a copy descriptor to the peer SP Gets or sets environmental control parameters Updates storage-system registration information
Navicli SAN Copy Command Functions
4-3
About Navisphere CLI Commands

You run EMC Navisphere CLI from 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 used in combination with the other CLI commands, you can configure and manage any of the storage systems supported by Navisphere CLI version 6.X. The CLI commands begin with the command navicli, described as follows.
navicli
Sends status or configuration requests to the storage system via the command line Before you can use Navisphere SAN Copy 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. Anyone that can log in to the host running the Navisphere CLI can use navicli. Use the navicli command as follows: navicli -help or navicli [-d device] [-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.
User Access Format
4-4
-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.) -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.
navicli
4-5
-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 Variables The 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. Examples The following examples show sample environment variable settings.
The commands in the following examples must be executed from the root directory.
4-6
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 explained in Appendix A of this manual (for SAN Copy errors) or the CLI Reference manual, P/N 069001038 (for other errors).
navicli
4-7
sancopy -create
Creates a copy descriptor for use in SAN Copy sessions Description The navicli sancopy command with -create creates a copy descriptor that you can use to start, stop, and otherwise manipulate SAN Copy sessions. 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 Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use the sancopy -create command with navicli (described on page 4-4) as follows: sancopy -create -name descriptor-name -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] where -name descriptor-name Specifies the SAN Copy descriptor name. The name can be up to 64 characters and must be unique on a per storage system basis. The descriptors you create persist until you remove them.
4-8
-srcwwn source-lun-wwn Specifies the WWN (worldwide name) of the source logical unit (LUN or snapshot). The source logical unit does not need to exist on the storage system specified by the -h switch. If it does not exist, SAN Copy assumes that the copy is to destination logical units on the storage system specified with -h. -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.
For pre-FC4700 storage systems, if you use the -srclun source-sp sourcelunnumber function, you must use -device devicename.
-device devicename Specifies the device name of the source LUN or destination LUN. -destwwn dest-lun-wwn 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 all destination logical units do not exist on the storage system specified with -h, then the source logical units must exist on that storage system. If the destination logical units are not reachable, and you did not use the -o function, by the client system, the CLI will print 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.
sancopy -create
4-9
-start Starts a SAN 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 5. -verify Verifies that SAN Copy can access all of the logical units specified in the -create command. -o Suppresses any confirmation message that the descriptor was created successfully. Conventions and Recommendations Example None. navicli -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 copy descriptor 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. Output If the version of Base 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_UNIQUE DMF_CREATE_PARAMS DMF_SRCLUN_WWN_AND_NUMBER_SPECIFIED DMF_DESTLUN_WWN_AND_NUMBER_SPECIFIED DMF_INVALID_THROTTLE_VALUE
4-10
sancopy -destinfo
Displays information about destination logical units for a running session Description The navicli sancopy command with -destinfo gets session status from the destination point of view. Issuing this command with no arguments displays all destination information for all copy descriptors belonging to the specified SP. You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -destinfo with navicli (described on page 4-4) as follows: sancopy -destinfo [-peer] [-descriptorid [descriptorid]] |[-name [name]] [-destwwn [dest-lun-wwn]] |[-destlunnumber destsp destlunnumber] [-complete] [-counts] [-failure] [-time] 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.
User Access Format
sancopy -destinfo
4-11
-destlunnumber destsp destlunnumber The switch -destlunnumber can not 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. Conventions and Recommendations Examples None. navicli -h ss1_spa sancopy -destinfo
Copy Descriptor ID 1 Destination LUN WWN: 60:06:01:6B:61:09:00:00:6A:6F:9F:ED:0B:A3:D6:11 Failure Status: No Failure Transfer Count at Failure N/A Percent 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 full Transfer Count at Failure: 90 Percent Complete at Failure: 12 Failure Time at Failure: 08/06/02 12:34:19
This display shows the status of the two SAN Copy copy descriptors belonging to SP ss1_spa. The first descriptor shows no failure, the second shows a failure. Output If the version of Base Software running on the SP does not support this command, a Command is not supported error message is printed to stderr.
4-12
sancopy -duplicate
Makes a copy of a copy descriptor Description The 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 SAN Copy session. You do not need to stop the copy descriptor before duplicating it. You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -duplicate with navicli (described on page 4-4) as follows: sancopy -duplicate -descriptorid descriptorid| -name name where -descriptorid descriptorid | -name name Either -descriptorid or -name identifies the descriptor you want to duplicate. Conventions and Recommendations Example None. navicli -h ss1_spa sancopy -duplicate -name copy_lun_66 This command duplicates SP ss1_spas 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 Base 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_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR
User Access Format
sancopy -duplicate
4-13
sancopy -info
Displays information about copy descriptors Description The navicli sancopy command with -info displays information on copy descriptors. It differs from -destinfo in that -destinfo gets information on the destination logical units. Issuing this command with no arguments displays all information on all copy descriptors of the specified SP. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -info with navicli (described on page 4-4) as follows: sancopy -info [-peer] [-descriptorid descriptorid | -name name] [-srcwwn] [-length] [-numdests] [-destwwn] [-sessionstatus] [-throttle] [-counts] [-complete] [-time] [-failure] 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 destinations logial units in the specified descriptor. -failure Displays failure status or No Failure for the copy descriptors source and destination logical units.
4-14
-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. -throttle Displays the current throttle value for the copy session. -time Displays the time when the copy completes. Conventions and Recommendations None.
sancopy -info
4-15
Example
navicli -h ss1_spa sancopy -info For SP ss1_spa, this -info command displays the status of all copy descriptors. The format is as follows: Copy Descriptor ID:Descriptor ID. Copy Descriptor Name:Descriptor name. Source LUN WWN: 16-byte worldwide name of source logical unit (-srcwwn). Number of Blocks to Copy:Number of blocks to copy (-length). Number 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). Failure Status: Source and destination failure status: No failure or Failure (-failure).
Output
If the version of Base Software running on the SP does not support this command, a Command is not supported error message is printed to stderr.
4-16
sancopy -modify
Changes the definitions in a copy descriptor Description The navicli sancopy command with -modify changes an existing copy descriptor. This command will fail if the descriptor has started or is in the paused state. The session must be stopped for modifications to be done. The new descriptor information will not take effect until you start a new session using the descriptor. You must include a copy descriptor ID or name and one or more switches to indicate changes. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -modify with navicli (described on page 4-4) as follows: sancopy -modify -descriptorid descriptor-id | -name name [-adddestbywwn dest-lun-wwn] [-adddestbylunnumber destsp destlunnumber] [-chgname newname] [-chgsrcbywwn srcwwn] [-chgsrcbylunnumber srcspname srclunnumber] [-o] [-rmdestbywwn dest-lun-wwn] [-rmdestbylunnumber destsp destlunnumber] [-throttle n] 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 Changes the descriptor name to newname.
sancopy -modify
4-17
-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 units worldwide name. -descriptorid descriptorid | -name name Either -descriptorid or -name 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 original default value is 5. To change the throttle value of an active session, use the command sancopy -throttle. Conventions and Recommendations Example None. navicli -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, 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.
4-18
Output
If the version of Base 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_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR DMF_INVALID_THROTTLE_VALUE DMF_REMOVED_DEST_DOESNOT_EXIST Errors returned from the driver or Agent are UNKNOWN_DESCRIPTOR_ID UNKNOWN_DESCRIPTOR_NAME SESSION_NAME_EXISTS
sancopy -modify
4-19
sancopy -pause
Suspends I/O in an active SAN Copy session Description The navicli sancopy command with -pause pauses an existing SAN Copy session. You must specify the descriptor ID or name. To continue the paused session, use the sancopy -resume function. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -pause with navicli (described on page 4-4) as follows: sancopy -pause -descriptorid descriptor-id | -name name where -descriptorid descriptorid | -name name Either -descriptorid or -name identifies the descriptor whose session you want to pause. Conventions and Recommendations Example None. navicli -h ss1_spa sancopy -pause -name copy_lun_66 For SP ss1_spa, this command pauses the session with the copy_lun_ 66 descriptor. Output If the version of Base 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_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR Errors returned from the driver or Agent are UNKNOWN_DESCRIPTOR_ID UNKNOWN_DESCRIPTOR_NAME INVALID_SIZE
4-20
sancopy -remove
Deletes a copy descriptor Description The navicli sancopy command with -remove deletes one or all previously stored copy descriptor(s). A copy descriptor cannot be removed if it is currently active. An active copy descriptor 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 descriptor(s). This command must have only one of following switches attached: -descriptorid -name -all User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -remove with navicli (described on page 4-4) as follows: sancopy -remove -descriptorid descriptor-id|-name name|-all [-o] where -descriptorid descriptorid | -name name | -all Either -descriptorid or -name 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. Conventions and Recommendations Example None. navicli -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.
sancopy -remove
4-21
Output
If the version of Base 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_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR
Errors returned from the driver or Agent are

UNKNOWN_DESCRIPTOR_ID
4-22
sancopy -resume
Continues I/O in a SAN Copy session Description The navicli sancopy command with -resume resumes an existing SAN 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. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -resume with navicli (described on page 4-4) as follows: sancopy -resume -descriptorid descriptor-id | -name name where -descriptorid descriptorid | -name name Either -descriptorid or -name identifies the descriptor whose session you want to resume. Conventions and Recommendations Example None. navicli -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 Base Software running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other error messages are DMF_NAME_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR
sancopy -resume
4-23
Errors returned from the driver or Agent are UNKNOWN_DESCRIPTOR_ID UNKNOWN_DESCRIPTOR_NAME SESSION_ALREADY_IN_PROGRESS
4-24
sancopy -settings
Lists or changes SAN Copy environmental parameters Description The navicli sancopy command with -settings gets and sets two SAN Copy environmental control parameters:

the maximum number of concurrent active sessions, and a checkpoint interval for session status
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. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -settings with navicli (described on page 4-4) as follows: sancopy -settings -list or sancopy - settings [-setmax MaxNumSessions] [-setcheckpoint CheckpointInterval] where -list Displays the current environmental parameter settings. -setmax maxNumSessions Sets the maximum number of SAN Copy sessions. The maximum number of sessions depends on the storage system type.
Storage-System Type FC4700-2, FC4700, CX600 CX400 Maximum No. of Sessions 16 (8 per SP) 8 (4 per SP)
sancopy -settings
4-25
-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. By default, checkpointing is enabled with a value of 10 minutes. The SAN Copy 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, the software will start copying from the beginning. Conventions and Recommendations Examples None. navicli -h ss1_spa sancopy -settings -list For SP ss1_spa, this command lists the current value for maximum number of sessions and the checkpoint interval. navicli -h ss1_spa sancopy -settings -setcheckpoint 45 For SP ss1_spa, this command changes the checkpoint interval to 45 minutes. Output If the version of Base 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_LIST_AND_SET_SPECIFIED DMF_INVALID_MAX_SESSION_VALUE DMF_INVALID_CHECKPOINT_INTERVAL_VALVE Errors Returned From Driver or Agent are SESSION_MAX_OVER_LIMIT SESSION_POLL_OVER_LIMIT
4-26
sancopy -start
Starts a SAN Copy session based on values in a copy descriptor Description The navicli sancopy command with -start starts a SAN 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. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -start with navicli (described on page 4-4) as follows: sancopy -start -descriptorid descriptor-id | -name name where -descriptorid descriptorid | -name name Either -descriptorid or -name identifies the copy descriptor for the session you want to start. Conventions and Recommendations Example None. navicli -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 Base Software running in the SP does not support the command, the CLI prints a Command is not supported error message to stderr. Other errors are DMF_NAME_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR Errors returned from the driver or Agent are
UNKNOWN_DESCRIPTOR_ID UNKNOWN_DESCRIPTOR_NAME SESSION_ALREADY_IN_PROGRESS
sancopy -start
4-27
sancopy -stop
Stops (terminates) a SAN Copy session Description The 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 SAN Copy operations. You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -stop with navicli (described on page 4-4) as follows: sancopy -stop -descriptorid descriptor-id | -name name where -descriptorid descriptorid | -name name Either -descriptorid or -name identifies the descriptor whose session you want to stop. Conventions and Recommendations Example None. navicli -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. Output If the version of Base Software running on the SP does not support this command, a Command is not supported error message is printed to stderr. Other error messages are DMF_NAME_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR Errors returned from the driver or Agent are UNKNOWN_DESCRIPTOR_ID UNKNOWN_DESCRIPTOR_NAME
User Access Format
4-28
sancopy -throttle
Changes the I/O rate of an active copy descriptor Description The 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-17) User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -throttle with navicli (described on page 4-4) as follows: sancopy -throttle -descriptorid descriptor-id | -name name n where -descriptorid descriptor-id | -name name Either -descriptorid or -name identifies the descriptor whose throttle value you want to change. n is the new throttle value, ranging from 1 (slowest) to 10 (highest) -Conventions and Recommendations Examples None. navicli -h ss1_spa sancopy -info -name copy_lun_66 (For SP ss1_spa descriptor copy_lun_66, this command displays information, including throttle information. navicli -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.
sancopy -throttle
4-29
Output
If the version of Base 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_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_INVALID_THROTTLE_VALUE DMF_UNKNOWN_DESCRIPTOR Errors returned from the driver or Agent are UNKNOWN_DESCRIPTOR_ID UNKNOWN_DESCRIPTOR_NAME
4-30
sancopy -transfer
Transfers a copy descriptor from the peer SP Description The 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. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -transfer with navicli (described on page 4-4) as follows: sancopy -transfer -descriptorid descriptor-id | -name name where -descriptorid descriptorid | -name name Either -descriptorid or -name identifies the descriptor you want to transfer to the working SP. Conventions and Recommendations Example None. navicli -h ss1_spb sancopy -transfer -name copy_lun_66 This command transfers the copy descriptor copy_lun_66 to the SP named ss1_spb. Output If the version of Base 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_AND_UID_SPECIFIED DMF_NAME_OR_UID_REQUIRED DMF_UNKNOWN_DESCRIPTOR DMF_PEER_SP_ALIVE Errors returned from the driver or Agent are UNKNOWN_DESCRIPTOR_ID UNKNOWN_DESCRIPTOR_NAME
sancopy -transfer
4-31
sancopy -updateconnections
Updates connection and registration information Description The navicli sancopy command with -updateconnections updates registration information for all attached storage systems. You should run this command for each SP. User Access Format You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -updateconnections with navicli (described on page 4-4) as follows: sancopy -updateconnections Conventions and Recommendations Examples None. navicli -h ss1_spa sancopy -updateconnections navicli -h ss1_spb sancopy -updateconnections These commands update connections on both SPs, ss1_spa and ss1_spb.
4-32
sancopy -verify
Ensures that the SAN Copy software can access a logical unit Description The navicli sancopy command with -verify ensures that the SAN Copy 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. You must have a username/host entry in the Navisphere SP Agent configuration file to use this command. Use sancopy -verify with navicli (described on page 4-4) as follows: sancopy -verify -wwn lun-wwn | -lunnumber sp-name lunnumber [-device devicename] where -wwn lun-wwn Specifies the worldwide name of the logical unit. -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. -device devicename Specifies the storage-system device name. This switch is required for FC4500 and FC5400 storage systems. Omit it for FC4700-Series and CX-Series storage systems. Conventions and Recommendations None.
User Access Format
sancopy -verify
4-33
Examples
navicli -h 11.12.13.14 sancopy -verify -lunnumber 12.34.56.78 22 Storage device is reachable. navicli -h 11.12.13.14 sancopy -verify -lunnumber 12.34.56.78 6 Error: sancopy command failed Error returned from Agent SP A: CPM unable to locate device. Check that the device with this WWN exists (0x712ac007)
4-34
Invisible Body Tag
A
This appendix lists the SAN Copy error codes returned by the CLI. The numbers proceed sequentially.
A-1

Error Value 227 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 Description Insert test event failed. Cannot unbind logical unit because it is in use as an active Hot Spare. Cannot unbind logical unit because a feature of the storage system is using it. Cannot unbind logical unit because it contains a Storage Group. Logical unit is in a Storage Group. This version of Core Software does not support SAN Copy. Minimum input requirement for SAN Copy -create command. Both the name and uid for a copy descriptor are supplied. The name or uid of a copy descriptor is required. Both the destination logical unit WWN and number are supplied. Specified destination logical unit does not exist. The specified copy descriptor name is not unique to this SP. Specified copy descriptor does not exist. Cannot list and set environment at the same time. Throttle switch must be specified. Valid throttle values are 1 to 10. Valid max session numbers are 1 to 16. Valid checkpoint intervals are number 5 to 90 and divisible by 5 or the word disable to disable the checkpoint feature. Both the source logical unit WWN and number are specified. The destination logical unit size is less than the source logical unit size. The peer SP is alive. This command works only if the peer SP is down. Either source or all destinations must be on the host SP. Multiple descriptors have the same name.
A-2
Error Value 252 253 254
Description Cannot display logical unit WWN and update logical unit map info at the same time. Input the same logical unit ID as the destination logical unit more than one time. The specified destination logical unit already exists in this descriptor as the destination.
A-3
A-4
Index
A
-a switch (admhost) 3-5 Access Logix, defined 1-4 activate command (admhost) 3-3 admhost about 3-2 activate command 3-3 command functions 3-2 deactivate command 3-3 flush command 3-4 help command 3-4 list command 3-4 requirements 3-2 session overview 4-2 admhost utility defined 1-3 Agent Host, defined 1-3 managed, defined 1-3 SP, defined 1-4 arguments, spaces in 4-6
B
benefits, SAN Copy 1-7
-pause 4-20 -remove 4-21 -resume 4-23 -settings environment parameters, setting with CLI 4-25 -start 4-27 -stop 4-28 -throttle 4-29 -transfer 4-31 -updateconnections 4-32 -verify 4-33 CLI, environment variables RaidAgentDevice 4-6 RaidAgentHost 4-6 RaidAgentTimeout 4-6 CLI, RaidAgent environment variables 4-6 clone, SnapView, defined 1-3 command functions, admhost 3-2 command line format, spaces in 4-6 copy descriptor creating (-create) 1-10, 4-8 getting information (-info) 4-14 -create subcommand 4-8
D
-d switch (admhost) 3-5 deactivate command (admhost) 3-3 destination logical units deactivate for NetWare 3-6 for UNIX 3-6 for Windows 3-6 -destinfo subcommand 4-11
C
CLI subcommands -create 4-8 -destinfo 4-11 -duplicate 4-13 -info 4-14 -modify 4-17
i-1
Index
diagnostics, navicli command 4-7 domain, defined 1-3 -duplicate subcommand 4-13
O
-o switch (admhost) 3-5
E
environment parameters, setting 4-25 error codes for SAN Copy subcommands A-2
P
-pause subcommand 4-20 portal, defined 1-3 ports, SAN Copy connecting to CLARiiON Storage Groups 2-6 connecting to Symmetrix volumes 2-7 registering 2-5 Powerlink 1-2
F
features, SAN Copy 1-7 flush command (admhost), about 3-4 function switches, admhost 3-5, 3-7
R H
help command (admhost) 3-4 RaidAgent environment variables 4-6 RaidAgent environment variables, CLI 4-6 -remove subcommand 4-21 requirements, admhost 3-2 -resume subcommand 4-23
I
-info command 4-14
L
-l switch (admhost) 3-5 list command (admhost), about 3-4 logical unit defined 1-3 making accessible to the SAN Copy port initiator 2-5 LUN destination, information (-destinfo command) 4-11 lun_activate command (admhost) 3-3 lun_deactivate command (admhost) 3-3 lun_flush command (admhost) 3-4 lun_list command (admhost) 3-4
S
SAN Copy configuration requirements and restrictions 2-2 connecting SAN Copy ports to CLARiiON Storage Groups 2-6 connecting SAN Copy ports to Symmetrix volumes 2-7 error codes A-2 features and benefits 1-7 introduction 1-5 making logical units accessible to the SAN Copy ports 2-5 operations overview 4-2 registering SAN Copy ports with target systems 2-5 session overview 4-2 sessions checkpoint interval, defined 1-3 defined 1-4 preparing logical units 3-6 software components 1-9 software, defined 1-4 zoning requirements and recommendations 2-4 sancopy CLI subcommand, see Chapter 4
M
-modify subcommand 4-17
N
navicli command 4-4 command switches, see individual CLI subcommands diagnostics, see error codes format 4-4
i-2
Index
session, starting 4-27 session, stopping 4-28 set command 4-7 -settings subcommand 4-25 shared storage, defined 1-4 snapshot, SnapView, defined 1-4 SnapView clone, defined 1-3 snapshot, defined 1-4 software components command line interface 1-9 graphical user interface 1-9 SAN Copy 1-9 source logical units deactivate Unix 3-6 Windows 3-6 stop I/O 3-6 spaces in arguments 4-6 -start subcommand 4-27
-stop subcommand 4-28 storage system SAN Copy, defined 1-4 shared, defined 1-4 switches admhost 3-5 CLI, see individual command
T
-throttle subcommand 4-29 -transfer subcommand 4-31
U
unshared storage systems, defined 1-4 -updateconnections subcommand 4-32
V
-verify subcommand 4-33
i-3
Index
i-4

EMC SAN Copy Command Line Interfaces: P/N 069001189 Rev A01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EMC SAN Copy Command Line Interfaces: P/N 069001189 Rev A01

Uploaded by

Copyright:

Available Formats

EMC SAN Copy Command Line Interfaces ADMINISTRATORS GUIDE

P/N 069001189 REV A01

Copyright 2003 EMC Corporation. All rights reserved.

EMC SAN Copy Command Line Interfaces Administrators Guide

SAN Copy Configuration Guidelines

Using the admhost Utility with SAN Copy

EMC SAN Copy Command Line Interfaces Administrators Guide

SAN Copy CLI Commands

SAN Copy Error Codes

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

EMC SAN Copy Command Line Interfaces Administrators Guide

EMC SAN Copy Command Line Interfaces Administrators Guide

This typeface x -> y

EMC SAN Copy Command Line Interfaces Administrators Guide

Where to Get Help

EMC SAN Copy Command Line Interfaces Administrators Guide

EMC SAN Copy Command Line Interfaces Administrators Guide

Invisible Body Tag

Introducing SAN Copy and Its Command Line Utilities

Introducing SAN Copy and Its Command Line Utilities

Finding Current Information

Accessing EMC Powerlink

EMC SAN Copy Command Line Interfaces Administrators Guide

Introducing SAN Copy and Its Command Line Utilities

destination logical unit

Event Monitor Host Agent logical unit

LUN managed Agent managed storage system Manager portal

Introducing SAN Copy and Its Command Line Utilities

Term pre-FC4700 systems SAN

SAN Copy port SAN Copy session

SAN Copy storage system

shared storage system

unshared storage system volume zone

EMC SAN Copy Command Line Interfaces Administrators Guide

Introducing SAN Copy and Its Command Line Utilities

Introducing SAN Copy Software

Introducing SAN Copy Software

Introducing SAN Copy and Its Command Line Utilities

Sample SAN Copy Sessions Between Storage Systems

EMC SAN Copy Command Line Interfaces Administrators Guide

Introducing SAN Copy and Its Command Line Utilities

SAN Copy Features and Benefits

SAN Copy Features and Benefits

Introducing SAN Copy and Its Command Line Utilities

Storage-System Type CX400 CX600 FC4700 Series

EMC SAN Copy Command Line Interfaces Administrators Guide

Introducing SAN Copy and Its Command Line Utilities

SAN Copy Software Components

SAN Copy Software Components

Introducing SAN Copy and Its Command Line Utilities

SAN Copy Operations Overview

EMC SAN Copy Command Line Interfaces Administrators Guide

Introducing SAN Copy and Its Command Line Utilities

Introducing SAN Copy and Its Command Line Utilities

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

EMC SAN Copy Command Line Interfaces Administrators Guide

Invisible Body Tag

SAN Copy Configuration Guidelines

SAN Copy Configuration Guidelines

SAN Copy Configuration Requirements and Restrictions

EMC SAN Copy Command Line Interfaces Administrators Guide

SAN Copy Configuration Guidelines

LUN 12 LUN 14 LUN 23 LUN 25