EMC SAN Copy Command Line Interfaces Reference

EMC® SAN Copy™
Command Line Interfaces
REFERENCE
P/N 069001189
REV A12
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2006-2008 EMC Corporation. All rights reserved.
Published March, 2008
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and
Advisories section on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.
2
EMC SAN Copy Command Line Interfaces Reference
Contents
Preface ..................................................................................................... 5
Chapter 1
Introducing SAN Copy and Its Command Line Utilities
Introducing SAN Copy software....................................................
SAN Copy features and benefits ....................................................
Storage-system-based data-mover application .....................
Easy-to-use web-based application.........................................
Use with replication software ..................................................
Simultaneous sessions between multiple storage systems..
Incremental SAN Copy sessions .............................................
Integration with EMC SnapView software ............................
Integration with EMC MirrorView software .........................
SAN Copy software components ...................................................
SAN Copy operations overview.....................................................
Chapter 2
13
14
14
14
15
15
16
16
16
18
19
SAN Copy Configuration Guidelines
SAN Copy configuration requirements......................................... 22
Copying data between CLARiiON storage systems or
CLARiiON and Symmetrix storage systems .......................... 22
Copying data between LUNs within a CLARiiON storage
system.......................................................................................... 26
Sample SAN Copy configuration............................................. 26
Fibre Channel zoning requirements and recommendations ...... 28
Zoning recommendations ........................................................ 28
Single-initiator zoning examples without and with SAN
Copy installed ............................................................................ 32
iSCSI zoning requirements and recommendations...................... 36
Preparing a CLARiiON storage system for a copy session ........ 37
Connecting SAN Copy ports to CLARiiON
storage groups............................................................................ 38
3
Contents
Preparing a Symmetrix storage system for a copy session......... 42
Preparing a Symmetrix storage system using EMC
ControlCenter SAN Manager .................................................. 42
Preparing a Symmetrix storage system using
ESN Manager ............................................................................. 43
Chapter 3
Using the Admhost Utility with SAN Copy
About Admhost for SAN Copy ......................................................
Admhost SAN Copy command functions ....................................
Preparing logical units for a SAN Copy session ..........................
Preparing source and destination logical units for full and
incremental sessions..................................................................
Chapter 4
48
49
51
51
SAN Copy CLI Commands
SAN Copy command functions...................................................... 56
About Secure CLI.............................................................................. 59
naviseccli ............................................................................................ 60
About Classic CLI ............................................................................. 65
navicli ................................................................................................. 66
sancopy -create.................................................................................. 69
sancopy -destinfo.............................................................................. 76
sancopy -duplicate............................................................................ 80
sancopy -info ..................................................................................... 81
sancopy -mark ................................................................................... 88
sancopy -modify ............................................................................... 90
sancopy -pause.................................................................................. 98
sancopy -remove............................................................................... 99
sancopy -resume ............................................................................. 101
sancopy -settings............................................................................. 103
sancopy -start .................................................................................. 106
sancopy -stop................................................................................... 108
sancopy -throttle ............................................................................. 109
sancopy -transfer ............................................................................. 111
sancopy -unmark ............................................................................ 112
sancopy -updateconnections......................................................... 113
sancopy -verify................................................................................ 114
Appendix A
SAN Copy CLI Error Codes
SAN Copy CLI error codes ........................................................... 118
Index .................................................................................................... 121
4
EMC SAN Copy Command Line Interfaces Reference
Preface
As part of an effort to improve and enhance the performance and capabilities
of its product line, EMC from time to time releases revisions of its hardware
and software. Therefore, some functions described in this guide may not be
supported by all revisions of the software or hardware currently in use. For
the most up-to-date information on product features, refer to your product
release notes.
If a product does not function properly or does not function as described in
this guide, please contact your EMC representative
About this manual
Note: This manual does not include any content that is specific to FC series or
C series storage systems. For this information, refer to the EMC SAN Copy
Command Line Interfaces Reference, 069-001189 Rev. A07.
This manual describes the two command line interfaces to EMC®
SAN Copy™ software: the Admhost Utility and the Command Line
Interface (CLI).
You should read this manual if you will use typed or scripted
commands (instead of or in addition to EMC Navisphere® Manager
software) to configure and run the SAN Copy software. This manual
assumes that you are familiar with the operating system running on
the servers you will manage and with storage-system components
and configurations.
Audience
This guide is part of the EMC SAN Copy (referred to as SAN Copy
later in this document) documentation set, and is intended for use by
customers and service providers who use EMC Navisphere CLI to set
up and manage SAN Copy software.
5
Preface
This manual assumes that you are familiar with the operating system
running on the servers you will manage and with storage-system
components and configurations.
Organization
This manual contains four chapters and one appendix as follows:
Chapter 1
Introduces terminology and the software products.
Chapter 2
Explains the basic requirements, restrictions and
configuration guidelines for using SAN Copy.
Chapter 3
Explains admhost commands that the operating
system uses to manage devices with SAN Copy.
Chapter 4
Describes the CLI commands that SAN Copy uses to
manage SAN Copy sessions.
Appendix A
Lists and describes the SAN Copy CLI error codes.
Related documentation
Related documents include:
6
◆
The most up-to-date version of the online help, available on the
EMC Powerlink® website (http://Powerlink.EMC.com) in the
“Navisphere Management Suite” section of the Technical
Documentation and Advisories section.
◆
EMC CX3-Series and CX-Series SAN Copy Release Notes
◆
EMC Admhost Release Notes
EMC SAN Copy Command Line Interfaces Reference
Preface
Conventions used in this guide
This manual uses the following format conventions:
Finding current
information
This
typeface
Indicates text (including punctuation) that you type
verbatim, all commands, pathnames, filenames,
and directory names. It indicates the name of a
dialog box, field in a dialog box, menu, menu
option, or button.
This typeface
Represents variables for which you supply the
values; for example, the name of a directory or file,
your username or password, and explicit
arguments to commands.
This
typeface
Represents a system response (such as a message or
prompt), a file or program listing.
x > y
Represents a menu path. For example, Operations
> Poll All Storage Systems tells you to select Poll
All Storage Systems on the Operations menu.
[ ]
Encloses optional entries.
|
Separates alternative parameter values; for
example:
LUN-name | LUN-number means you can use either
the LUN-name or the LUN-number.
The most up-to-date information about the EMC SAN Copy software
is posted on the EMC Powerlink® website. We recommend that you
download the latest information before you start the SAN Copy
software. If you purchased this product from an EMC reseller and
you cannot access Powerlink, the latest product information should
be available from your reseller.
To access EMC Powerlink, use the following link:
http://Powerlink.EMC.com
After you log in, select Support > Technical Documentation and
Advisories and find the following:
◆
EMC Admhost Release Notes (P/N 300-001-713)
◆
EMC SAN Copy Release Notes (P/N 300-001-670)
◆
The latest version of this guide that is applicable to your software
revision
7
Preface
◆
Where to get help
EMC Installation Roadmap for CX3-Series, 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.
EMC support, product, and licensing information can be obtained as
follows.
Product information — For documentation, release notes, software
updates, or for information about EMC products, licensing, and
service, go to the EMC Powerlink website (registration required) at:
http://Powerlink.EMC.com
Technical support — For technical support, go to EMC WebSupport
on Powerlink. To open a case on EMC WebSupport, you must be a
WebSupport customer. Information about your site configuration and
the circumstances under which the problem occurred is required.
Your comments
8
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.
EMC SAN Copy Command Line Interfaces Reference
1
Invisible Body Tag
Introducing SAN Copy
and Its Command Line
Utilities
This chapter introduces the EMC® SAN Copy™ software and its
command line utilities: admhost, with commands that the operating
system uses to manage SAN Copy devices; and the CLI, with
commands that manage SAN Copy sessions. Major topics are:
◆
◆
◆
◆
◆
Terminology ........................................................................................
Introducing SAN Copy software .....................................................
SAN Copy features and benefits......................................................
SAN Copy software components ....................................................
SAN Copy operations overview ......................................................
10
13
14
18
19
9
Introducing SAN Copy and Its Command Line Utilities
Terminology
10
Term
Meaning
Admhost Utility
The Admhost Utility is an executable program that you can run interactively with a script. It
runs on Microsoft Windows NT, Windows 2000, and Windows Server 2003.
auto recovery
The state of a copy session that is trying to resume failed sessions.
AX4-5 series storage system
AX4-5 (AX4-5F), AX4-5i (AX4-5I), AX4-5SC (AX4-5FSC), AX4-5SCI (AX4-5ISC)
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.
connection set
A named set of information used by a CLARiiON iSCSI initiator to establish a replication
session with an iSCSI target. A connection set consists of a unique user-defined name,
credentials usage (connection specific, array-shared or none), one or more connection
paths, and when specified, an optional username and password (secret).
connection type
The network protocol for transferring data from one storage system to another. The
available choices depend on the storage systems participating in the copy session. The
choices may be fibre or iSCSI.
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).
CX series storage system
CX700, CX600, CX500, CX500i, CX400, CX300, CX200, and CX200LC
CX3 series storage system
CX3 model 80 system, CX3 model 40 systems, CX3 model 20 systems, and CX3 model 10
systems
destination logical unit
A logical unit to which SAN Copy is copying the source data. On a CLARiiON® storage
system, this device is called a LUN; on a Symmetrix® system, it is called a volume (can be
a single LUN or a metaLUN).
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.
EMC SAN Copy Command Line Interfaces Reference
Introducing SAN Copy and Its Command Line Utilities
Term
Meaning
fibre preferred
Sets the session connection type to fibre or iSCSI (if fibre path could not be found) each
time you start or resume a session that failed or was stopped.
full SAN Copy session
A full copy session copies all the data on the source logical unit to one or many destination
logical units.
host agent
EMC Navisphere agent that runs on a storage-system server.
incremental SAN Copy
session
An incremental copy session copies only the data that has changed since the last copy
session.
latency
The amount of time it takes to transmit a block of data to its destination expressed in
milliseconds. By default, latency is set to AUTO (the software computes the latency
value).
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.
pre-CX series systems
An FC4700, 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 that does not
own the copy session. A remote storage system does not need to be running SAN Copy
software.
This storage system could be a CLARiiON, Symmetrix, or supported non-CLARiiON
storage system.
reserved LUN pool
The reserved LUN pool works with SAN Copy to perform incremental copy operations. It
consists of one or more private LUNs. The reserved LUN pool is shared by both
storage-system SPs, and before starting an incremental SAN Copy session, the pool must
contain at least one LUN for each source LUN that will be participating in an incremental
session. For more information, see the Navisphere Manager online help.
11
Introducing SAN Copy and Its Command Line Utilities
12
Term
Meaning
reserved session
A private session created by SAN Copy when you start an incremental copy session. The
name assigned to the reserved session consists of the copy session name with the prefix
”SANCopy”. No user actions can be performed on a reserved session.
SAN
Storage area network: One or more servers connected to one or more storage systems with
Fibre Channel switches. Switch zoning and EMC Access Logix™ software control server
access to storage systems and LUNs.
SAN Copy
Software running on a SAN Copy storage system that lets you copy logical unit information
between SAN Copy storage systems and other CLARiiON storage systems, or within a
storage system.
SAN Copy port
An SP port initiator on a SAN Copy storage system that is participating in a SAN Copy
session.
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.
SAN Copy storage system
The CLARiiON storage system that owns the SAN Copy session. A SAN Copy storage
system must be running SAN Copy software. You can install SAN Copy on AX4-5 series
storage systems with Navisphere Manager, CX3 series or a CX400, CX500, CX600, CX700
storage system, but not on a CX300 or AX series 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 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 CX3-series, CX-series and supported
AX-series storage systems.
storage management server
software
Software that runs in a storage system or off-array management 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.
virtual disk
A logical unit on an AX-series storage system.
volume
A logical unit on a Symmetrix storage system.
zone
A way to limit access to specific logical units in a storage system, thereby increasing
security and decreasing network traffic.
EMC SAN Copy Command Line Interfaces Reference
Introducing SAN Copy and Its Command Line Utilities
Introducing SAN Copy software
EMC SAN Copy software (referred to as SAN Copy later in this
document) runs on a SAN Copy storage system (storage system with
SAN Copy software enabled). It copies data between CLARiiON
storage systems, within CLARiiON storage systems, between
CLARiiON and Symmetrix storage systems, and between CLARiiON
and qualified non-EMC storage systems. SAN Copy can copy data
directly from a source logical unit on one storage system to
destination logical units on other systems, without using host
resources. SAN Copy connects directly or through a SAN, and also
supports protocols that let you use the IP WAN (wide area network)
to send data over extended distances. SAN Copy can perform
multiple copies — each in its own copy session — simultaneously.
The RAID type of the logical units participating in a copy session
does not have to be the same; that is, the source and destination
logical units can be different RAID types.
You can use SAN Copy to create full and incremental copies of a
source logical unit. An incremental session copies only the data that
has changed since the last copy session. This can significantly reduce
the time needed to copy the data, thereby allowing the copy
operation to be performed more frequently and more effectively.
Unlike full copy sessions, the source logical unit for an incremental
session can remain online during the copy process. You must,
however, prepare the source logical unit prior to starting the session
(see “Preparing logical units for a SAN Copy session” on page 51).
Regardless of the type of copy session — full or incremental — the
participating logical units must meet certain requirements.
You can use SAN Copy for the following tasks:
◆
One-time data migration
◆
Routine copying of data for application testing
◆
Content distribution
◆
Scheduled updates to multiple databases.
To manage SAN Copy sessions, you can use either the UI-based
Navisphere Manager (described in the Navisphere Manager online
help), or the SAN Copy Command Line Interface described in this
manual.
13
Introducing SAN Copy and Its Command Line Utilities
SAN Copy features and benefits
The SAN Copy software adds value to customer systems by offering
the following features:
◆
A storage-system-based data mover application that uses a
storage area network (SAN) rather than host resources to copy
data resulting in a faster copy process.
◆
An easy-to-use, web-based application for configuring and
managing SAN Copy.
◆
Software that you can use in conjunction with replication
software, allowing I/O with the source logical unit to continue
during the copy process.
◆
Simultaneous sessions that can copy data to multiple CLARiiON
and Symmetrix storage systems.
◆
Incremental SAN Copy sessions that copy only the data that has
changed since the last update.
◆
Integration with EMC SnapView software.
◆
Integration with EMC MirrorView™ software.
Storage-system-based data-mover application
SAN Copy is a storage-system-based data-mover application that
uses a SAN (storage area network) or LAN (local area network) to
copy data between storage systems. Since SAN Copy runs on the
storage systems, this eliminates the need to move data to and from
the attached hosts and reserves host processing resources for users
and applications. Since the host is not involved in the copy process,
and the data migration takes place on the SAN, the copy process is
much faster than the LAN-based, host-involved copy process.
Easy-to-use web-based application
SAN Copy is an integrated part of Navisphere Manager, the
easy-to-use, web-based management tool for CLARiiON storage
systems. Manager lets you select the SAN Copy source and
destination logical units, create SAN Copy sessions and then manage
these sessions.
14
EMC SAN Copy Command Line Interfaces Reference
Introducing SAN Copy and Its Command Line Utilities
Use with replication software
If the storage system containing the source logical unit has device
replication technology, such as EMC SnapView or EMC TimeFinder®
software, SAN Copy can use a snapshot (full copy sessions only),
clone, or Symmetrix BCV (business continuation volume) as its
source logical unit — allowing I/O with the source logical units for
the snapshot, clone, or BCV to continue during the copy process.
Note: You must fracture a SnapView clone before using it as a source LUN in
a SAN Copy session. For more details, refer to the SnapView documentation
and online help.
Simultaneous sessions between multiple storage systems
SAN Copy lets you have more than one session active at a time. The
number of supported concurrent active sessions and the number of
logical units per session depends on the storage-system type.
Note: If the destination logical unit is a metaLUN, the metaLUN is
considered a single entity. Therefore, the metaLUN counts as one of the
maximum destination logical units. For example, if a metaLUN consists of
five LUNs, it counts only as one destination logical unit, not five.
Storage-system type
Maximum number of
concurrent sessions per
system
Maximum number of
destination logical units
per source
AX4-5 series dual FC
4 (2 per SP)
50
CX3 model 20 systems,
CX500, CX400
8 (4 per SP)
50
CX3 model 40 systems
8 (4 per SP)
100
CX3 model 80 system,
CX700, CX600
16 (8 per SP)
100
CX3 model 10 systems
4 (2 per SP)
50
15
Introducing SAN Copy and Its Command Line Utilities
Incremental SAN Copy sessions
The incremental SAN Copy feature lets you copy only the data that
has changed since the last copy session. This significantly reduces the
time needed to copy the data, thereby allowing the copy operation to
be performed more frequently and more effectively. Unlike full copy
sessions, the source logical unit can remain online during the copy
process.
To use the incremental SAN Copy feature:
◆
The source logical unit must reside in a SAN Copy storage
system. (This storage system cannot be a CX300 storage system or
an AX-series storage system running Navisphere Express).
◆
The source logical unit cannot be a SnapView snapshot.
◆
You must configure the reserved LUN pool (refer to the
EMC Navisphere Manager online help).
Integration with EMC SnapView software
SnapView can be used with SAN Copy to create a snapshot or a clone
of the destination LUN, so that the SnapView replica can be put in the
secondary server storage group, rather than the SAN Copy
destination logical unit. This allows the SAN Copy destination logical
unit to maintain consistency with its source, and be available on an
ongoing basis for incremental updates. SAN Copy tracks server
writes to the SAN Copy source LUN (for example, from the
production server); but SAN Copy does not track server writes to the
SAN Copy destination LUN (for example, from the secondary
server).
Integration with EMC MirrorView software
SAN Copy software lets you create an intra- or inter-storage-system
copy of a LUN at any point in time; however, do this only when the
image state is either synchronized or consistent and the mirror is not
updating to the secondary image. The copy is a persistent image that
can serve for other application purposes while I/O continues to the
source LUN. The MirrorView secondary image is not viewable to any
hosts, but you can use SAN Copy to create a copy of the secondary
image on a secondary storage system to perform data verification
and run parallel processes.
16
EMC SAN Copy Command Line Interfaces Reference
Introducing SAN Copy and Its Command Line Utilities
Related to the process of making the MirrorView secondary image
unavailable for host I/O, you cannot run SAN Copy full copy
sessions on MirrorView secondary images. You can, however, run
SAN Copy incremental sessions on MirrorView secondary images.
For more information on MirrorView, refer to the EMC Navisphere
Manager online help.
17
Introducing SAN Copy and Its Command Line Utilities
SAN Copy software components
SAN Copy consists of the following software components:
◆
SAN Copy software installed and enabled on a SAN Copy
storage system.
Note: All CX-series (excluding the CX300) and CX3-series storage
systems ship from the factory with SAN Copy software installed, but not
enabled. To use the SAN Copy software functionality, the SAN Copy
enabler must be installed on the storage system.
18
◆
The Admhost Utility provides a command line executable that
lets you execute certain commands — lun_activate,
lun_deactivate lun_flush, and lun_list when managing SAN
Copy sessions. The Admhost Utility ships with other Windows
host utilities (for example, the host agent and CLI), and resides on
any Windows hosts connected to storage systems that have the
SAN Copy software installed and enabled.
◆
User interface (UI) - Navisphere Manager, which must be
installed on at least one storage system on the same network as
the SAN Copy storage system.
◆
Navisphere Command Line Interface (CLI), which ships as part of
the Navisphere Host Agent packages.
EMC SAN Copy Command Line Interfaces Reference
Introducing SAN Copy and Its Command Line Utilities
SAN Copy operations overview
The following steps explain how to use SAN Copy:
1. Set up SAN Copy. This procedure includes the following tasks:
• Zoning switches — see “Fibre Channel zoning requirements
and recommendations” on page 28, or, for iSCSI, see the
Navipshere Manager online help or the Navisphere Command
Line Interface Reference.
• Registering SAN Copy ports — see “Preparing a CLARiiON
storage system for a copy session” on page 37 and “Preparing
a Symmetrix storage system for a copy session” on page 42.
• Adding logical units to storage groups and connecting ports to
storage groups and volumes — see “Preparing a CLARiiON
storage system for a copy session” on page 37 and “Preparing
a Symmetrix storage system for a copy session” on page 42.
• Configuring the reserved LUN pool for incremental SAN
Copy sessions — see the Navisphere Command Line Interface
Reference.
2. On the SAN Copy storage system, create full or incremental SAN
Copy copy descriptors using the sancopy -create or sancopy
-create -incremental command (see page 69).
3. Prepare the source and destination logical units for a SAN Copy
session (see “Preparing logical units for a SAN Copy session” on
page 51).
4. For full sessions, proceed to step 5 to start the session.
For incremental sessions, mark any sessions using the
sancopy -mark command (see page 88).
Note: Once you receive confirmation that the mark operation was
successful, you can make the source logical units available to the host
and resume I/O to these logical units. This applies only to source logical
units participating in incremental copy sessions.
5. On the production host’s storage system, start the SAN Copy
sessions using the sancopy -start command (see page 106).
Note: More than one session at a time per source logical unit can be
active on a host, provided the source and destination logical units are
unmounted (see step 3 above).
19
Introducing SAN Copy and Its Command Line Utilities
6. Let the copy session complete.
7. On both hosts, make the source logical unit (if not done
previously) and destination logical units available to the
operating system.
Note: Some operating systems do not support access by the same host to
identical LUNs. Therefore, once SAN Copy completes the copy session,
we recommend that you move any identical LUNs to different storage
groups.
With Windows hosts, issue the admhost lun_activate command.
This command rescans the bus for new devices and assigns a
drive letter to all CLARiiON and Symmetrix logical units that do
not already have one. Use the -l and -d options with the admhost
lun_activate command to assign a drive letter to a LUN with a
specific world wide name (WWN).
What next?
20
Depending on your needs, go to one of the following chapters:
◆
For information about the basic requirements, restrictions and
configuration guidelines for using SAN Copy -- Chapter 2
◆
To learn about admhost commands — Chapter 3
◆
To learn about SAN Copy CLI commands — Chapter 4
EMC SAN Copy Command Line Interfaces Reference
2
visible Body Tag
SAN Copy
Configuration
Guidelines
This chapter lists the basic requirements, restrictions and
configuration guidelines for using SAN Copy.
Major sections are:
◆
◆
◆
◆
◆
SAN Copy configuration requirements ..........................................
Fibre Channel zoning requirements and recommendations .......
iSCSI zoning requirements and recommendations.......................
Preparing a CLARiiON storage system for a copy session .........
Preparing a Symmetrix storage system for a copy session..........
22
28
36
37
42
21
SAN Copy Configuration Guidelines
SAN Copy configuration requirements
This section describes the configuration requirements and restrictions
for copying data between CLARiiON storage systems, between
CLARiiON and Symmetrix storage systems, and within CLARiiON
storage systems. Figure 3 shows a sample SAN Copy session that
includes these configurations.
Copying data between CLARiiON storage systems or CLARiiON and Symmetrix
storage systems
If you will be copying data between CLARiiON storage systems, or
between CLARiiON and Symmetrix storage systems, the
requirements in the following sections must be met before you start a
SAN Copy session.
Note: For full copy sessions, a virtual disk in an AX4-5 or series storage
system can be either a source or a destination logical unit. For incremental
sessions, it can be only a destination logical unit.
22
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
Supported SAN Copy configurations for sessions between CLARiiON systems
Table 2-1 describes the currently supported SAN Copy configurations
for sessions between CLARiiON storage systems.
Table 2-1
Supported SAN Copy configurations
Source storage
Storage system Type
Destination storage
Storage system type
CX500, CX700, CX3 series,
AX4-5 series dual SP
(SAN Copy storage systems
with Navisphere Manager)
Connection type
Session type
CX series, CX3 series (with
Navisphere Manager)
AX4-5 series, AX series (with
Navisphere Manager or
Navisphere Express)
FC
Full, Incrementatl
CX3 series
(SAN Copy storage systems
with Navisphere Manager)
CX series, CX3 series (with
Navisphere Manager)
AX4-5, AX series (With
Navisphere Manager or
Navisphere Express)
iSCSI
Full, Incrementatl
CX series , CX3 series (with
Navisphere Manager)
AX4-5 series, AX series (with
Navisphere Manager or
Navisphere Express)
CX500, CX700, CX3 series ,
AX4-5 series dual SP
(SAN Copy storage with
Navisphere Manager)
FC
Full
CX series, CX3 series (with
Navisphere Manager)
AX4-5 series, AX series (with
Navisphere Manager or
Navisphere Express)
CX3 series
(SAN Copy storage systems
with Navisphere Manager)
iSCSI
Full
All copy sessions
Both full and incremental copy sessions must meet the following
requirements. In addition, incremental sessions must meet the
requirements described in “Incremental copy sessions” on page 25.
◆
One of the CLARiiON storage systems participating in the copy
session must be a SAN Copy storage system.
◆
You must enable the VCM bit on all Symmetrix storage ports
participating in the SAN Copy session.
◆
For Fibre Channel replication, you must correctly zone SAN Copy
initiator ports to remote storage systems so that SAN Copy can
have access to these systems (see “Fibre Channel zoning
requirements and recommendations” on page 28).
23
SAN Copy Configuration Guidelines
For iSCSI replication, you must create connection sets. A
connection set is a named set of information used by a CLARiiON
iSCSI initiator to establish a replication session with an iSCSI
target. A connection set consists of a unique user-defined name,
method for assigning security credentials (connection specific,
array-shared or none), one or more connection paths, and when
specified, an optional username and password (secret).
Note: SAN Copy ports act as host initiators to the remote storage
systems. You can add them to storage groups and they must belong to
the same zone or connection set as the logical units participating in the
copy session.
◆
Either the source logical unit, destination logical units or both
must reside in a SAN Copy storage system.
Note: If the source logical unit resides in the SAN Copy storage system,
you can copy data to one or many destination logical units on one or
many storage systems. None of the remote storage systems require the
SAN Copy software.
If the source logical unit does not reside in the SAN Copy storage system,
all destination logical units must reside in the storage system that owns
the SAN Copy session.
◆
24
When copying data to a Symmetrix system, use the
navicli -lunmapinfo command to obtain the World Wide Name
(WWN) of any Symmetrix volumes that you want to include in
the SAN Copy session. These volumes must be mounted and the
Navisphere Host Agent must be installed on the hosts that own
the volumes. For the required host agent version, refer to the SAN
Copy release notes, available on Powerlink (see “Finding current
information” in the Preface).
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
◆
In order for the logical units to participate in a SAN Copy session,
you must make the logical units accessible to the participating
SAN Copy storage-system port. For example, when copying
between CLARiiON storage systems, you must add the SAN
Copy initiator port to the storage group on the remote storage
system that includes the participating destination logical units.
Note: For AX4-5 and AX series storage systems with Navisphere
Express, refer to the Navisphere Express online help for instructions on
making virtual disks accessible to the SAN Copy port.
For Symmetrix storage systems, refer to your Symmetrix documentation
for instructions on making volumes accessible to the SAN Copy port.
Incremental copy sessions
Incremental copy sessions must meet all the requirements for full
sessions with the following exceptions and additions:
Exception
◆
The source logical unit cannot reside in a remote storage system. It
must reside in the SAN Copy storage system.
◆
The source logical unit cannot be a SnapView snapshot.
Additions
◆
You must configure the reserved LUN pool before you start an
incremental SAN Copy session. The reserved LUN pool works
with SAN Copy to perform incremental SAN Copy operations. It
consists of one or more private LUNs. Before starting an
incremental SAN Copy session, the pool must contain at least one
LUN for each source LUN that will be participating in an
incremental session. For more information, see the Navisphere
Manager online help, packaged with the software and available
from Powerlink.
What next?
◆
See “Fibre Channel zoning requirements and recommendations”
on page 28, or “iSCSI zoning requirements and
recommendations” on page 36.
◆
See “Preparing a CLARiiON storage system for a copy session”
on page 37, and/or “Preparing a Symmetrix storage system using
ESN Manager” on page 43.
25
SAN Copy Configuration Guidelines
Copying data between LUNs within a CLARiiON storage system
If you will copy data from one LUN to one or many LUNs within the
same CLARiiON storage system, the following requirements must be
met before you start a SAN Copy session.
Note: You do not need to zone Fibre Channel connections or create iSCSI
connection sets when you are copying data within a storage system.
◆
The storage system must be a SAN Copy storage system.
◆
The source and all destination LUNs participating in a copy
session must belong to the same SP.
Note: If you need to copy between LUNs owned by different SPs, you
must trespass either the source or destination LUNs before starting the
session.
◆
For incremental copy sessions:
• The source logical unit cannot be a SnapView snapshot.
• You must configure the reserved LUN pool before you start an
incremental SAN Copy session. For more information, see the
Navisphere Manager online help, packaged with the software
and available from Powerlink.
Sample SAN Copy configuration
Figure 3 shows a sample SAN Copy configuration that includes a
SAN Copy storage system on the left, and a remote storage system on
the right (either a CLARiiON or Symmetrix storage system). LUNs 1,
2, 3, and 4 reside in the SAN Copy storage system and LUNs 5 and 6
reside in the remote storage system.
Within the SAN Copy storage system, the data on LUN 1 is being
copied to LUN 2. LUNs 1 and 2 must belong to the same SP, and no
zoning is required.
An incremental copy session is copying the data on LUN 4 to LUN 6.
LUN 4 (the source LUN) must reside in a SAN Copy storage system.
Since the source logical unit is on the SAN Copy system, SAN Copy is
able to copy LUN 4’s data to many destination LUNs on many
storage systems.
A full copy session is copying the data on LUN 5 to LUN 3. Since the
source LUN (LUN 5) does not reside in a SAN Copy storage system,
26
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
all the destination LUNs for LUN 5 must reside in the same SAN
Copy storage system.
Server
Server
Switch fabric
Server
Switch fabric
separate server
required for
AX-series
storage system
SAN Copy
zone
Source LUN
LUN 1
Destination LUN
LUN 2
Destination LUN
LUN 3
Source LU
LUN 5
Source LUN
LUN 4
Destination LU
LUN 6
SAN Copy storage system
Remote storage system
EMC3048
Figure 3
Sample SAN Copy configuration
27
SAN Copy Configuration Guidelines
Fibre Channel zoning requirements and recommendations
Note: Zoning is not required for copying data between LUNs within a
CLARiiON storage system.
SAN Copy software does not support configurations where a SAN Copy port
is zoned to a storage system that is not supported by SAN Copy software.
Refer to the EMC Support Matrix (ESM) or SAN Copy release notes for a list of
supported storage systems.
Currently, SAN Copy and MirrorView™ software cannot share the same SP
port (refer to the SAN Copy release notes for confirmation).
Each port in a SAN Copy storage system is a dual-mode port. When
the port is participating in a SAN Copy session, it acts as an initiator
to the remote storage systems and any other SAN Copy ports in the
same zone. When the host initiators are using the port to transfer I/O,
the port acts as a target to the host initiator. Each time a host initiator
registers with the SAN Copy port or the SAN Copy port registers
with another SP port, the SAN Copy port consumes a login resource.
If you consume all login resources for the SAN Copy port, the SAN
Copy session may not successfully complete on all destination logical
units. EMC recommends that you follow the single initiator to single
remote SP port rule when creating and configuring SAN Copy zones
— include only one SAN Copy port (initiator) and only one remote
SP port in each zone. For examples of single initiator zoning, refer to
“Single-initiator zoning examples without and with SAN Copy
installed” on page 32.
Zoning recommendations
You can create a variety of SAN Copy zoning configurations. EMC
recommends that you configure your zoning so that:
28
◆
There are redundant connection paths from the SAN Copy ports
to the logical units on the remote storage system.
◆
Each SP on the SAN Copy storage system (SAN Copy port) has
access to each SP on the remote storage system.
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
To accomplish this, EMC recommends that you create four zones
from the SAN Copy storage system to the remote storage system.
This results in a consistent easy-to-troubleshoot zoning configuration.
Zones
San Copy storage system
Remote storage system
Zone 1
SP A port 1
SP A port 1
Zone 2
SP A port 1
SP B port 1
Zone 3
SP B port 1
SP A port 1
Zone 4
SP B port 1
SP B port 1
If this zoning configuration does not meet your needs, you can also
create your zoning based on the most important criteria for the SAN
Copy session — performance, availability, or preserving host login
resources. The following sections recommend zoning configurations
for these criteria.
Note: As an absolute minimum, configure one zone that includes a single
port on a single SP in the SAN Copy storage system and a single port on a
single SP in the remote storage system. This configuration does not provide
high availability for the SAN Copy session or access to logical units
belonging to both SPs on the remote storage system.
Performance
If performance is most important, we recommend that you create
multiple zones, each with a different SAN Copy port zoned to the
same remote SP ports. SAN Copy allows multiple sessions to share a
single port, but if multiple ports are available, SAN Copy will spread
multiple sessions across available SAN Copy ports to maximize total
throughput.
Note: This configuration increases performance only when you have
multiple, concurrent copy sessions running. This configuration will not
increase performance for a single session.
In Figure 4, LUN 1 and LUN 2 on the SAN Copy storage system
belong to SP A. Zones 1 and 3 provide multiple connection paths
from LUNs 1 and 2 to the remote storage system. In this example, two
SAN Copy sessions are running. One session is copying data from
LUN 3 to LUN 1 using port 0 on SP A of the SAN Copy storage
system. The other session is copying data from LUN 2 to LUN 4 and
is using port 1 on SP A.
29
SAN Copy Configuration Guidelines
Server
Server
Switch Fabric
1
SP A
3
Switch Fabric
1 3
SP B
1 3
SP A
SP B
Destination LUN
LUN 1
Source LUN
LUN 3
Source LUN
LUN 2
Destination LUN
LUN 4
SAN Copy Storage System
Remote Storage System
EMC2698
Figure 4
Recommended zoning based on performance
Availability
For high availability when you use SAN Copy, EMC recommends
that you configure a minimum of two zones. Each zone should
include one port from a different SP in the SAN Copy storage system
and one port from each SP in the remote storage system.
Figure 5 shows the minimum recommended high-availability SAN
Copy zoning configuration using zones 1 and 2.
Zones
SAN Copy storage system
Remote storage system
Zone 1
SP A port 0
SP A port 1 and SP B port 1
Zone 2
SP B port 0
SP A port 0 and SP B port 0
In the following example, three copy sessions are running. The
session copying data from LUN 2 to LUN 4 is using zone 1. The
session copying data from LUN 3 to LUN 1 is using zone 2. The third
session, LUN 2 to LUN 1, requires no zoning.
30
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
Server
Server
Switch Fabric
separate server
required for
AX-Series
Storage System
Switch Fabric
1
2
SP A
Server
SP B
1
2
2
1
SP A
SP B
Destination LUN
LUN 1
Source LU
LUN 3
Source LUN
LUN 2
Destination LU
LUN 4
SAN Copy Storage System
Remote Storage System
EMC3052
Figure 5
Recommended zoning based on availability
Limiting host login resources
If limiting host login resources is most important because a large
number of hosts connect to a remote storage system, zone only
necessary SAN Copy ports to that storage system.
Note: For more information on limiting host login resources, refer to the
section on login resources on page 28.
The following table describes each zoning configuration:
Zones
SAN Copy storage system
Remote storage system
Zone 1
SP A port 0
SP A port 1 and SP B port 1
Zone 2
SP B port 0
SP A port 0 and SP B port 0
In Figure 6, three copy sessions are running. The session copying data
from LUN 2 to LUN 4 is using zone 1. The session copying data from
LUN 3 to LUN 1 is using zone 2. The third session, LUN 2 to LUN 1
requires no zoning.
31
SAN Copy Configuration Guidelines
Server
Server
Switch Fabric
Switch Fabric
1
2
SP A
Server
SP B
1
2
separate server
required for
AX-Series
Storage System
2
1
SP A
SP B
Destination LUN
LUN 1
Source LU
LUN 3
Source LUN
LUN 2
Destination LU
LUN 4
SAN Copy Storage System
Remote Storage System
EMC3052
Figure 6
Recommended zoning based on limiting login resources
Single-initiator zoning examples without and with SAN Copy installed
A single-initiator zone includes only one host or SAN Copy initiator.
The two exceptions to the single-initiator rule for SAN Copy are:
◆
Never place more than one SAN Copy port in the same zone
unless two SAN Copy storage systems are in the domain, and
each storage system is acting as both the SAN Copy storage
system and the remote storage system to the other.
◆
Never place a SAN Copy port in the same zone as the host unless
the host HBA initiator is connected to the SAN Copy port for the
purpose of host I/O.
Figure 7 shows an example of single-initiator zoning between a
server and two storage systems for the purpose of data I/O. Neither
storage system is a SAN Copy storage system. In this example, zone 1
includes the HBA initiator port and a target port on each SP in both
storage systems.
32
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
Server
1
Server
separate server
required for
AX-Series
Storage System
2
Switch Fabric
1
SP A
2
1
2
SP B
Storage System w/o SAN Copy
2
1
SP A
2
1
SP B
Storage System w/o SAN Copy
EMC3049
Figure 7
Sample single-initiator zoning without SAN Copy
33
SAN Copy Configuration Guidelines
If you install SAN Copy on one of the storage systems in the previous
example, change your zoning to the configuration shown in Figure 8.
This example shows each SAN Copy port in a separate zone with the
host initiator (zones 2 and 3). If you keep the zoning as it was in
Figure 7, additional login resources will be consumed for the ports,
even if you are not currently using SAN Copy.
Server
Server
separate server
required for
AX-Series
Storage System
1
2
4
3
Switch Fabric
3
SP A
2
SP B
SAN Copy Storage System
1
1
4
SP A
4
SP B
Storage System w/o SAN Copy
EMC3050
Figure 8
Sample single-initiator zoning with SAN Copy installed
Figure 9 shows an example of single-initiator zoning between a
server and two storage systems for the purpose of data I/O and SAN
Copy data transfer. One of the storage systems is a SAN Copy storage
system. In this example, the hosts are in zones with all necessary
target ports, including SAN Copy ports (zones 1,2, 3 and 6), and the
SAN Copy ports are in separate zones with the remote ports they
must access (zones 4 and 5). The six zones are configured as follows:
34
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
Zone identifier
Purpose
Includes
Zone 1
Data I/O
HBA initiator port, SP A port 1 and SP B port 1 on remote
storage system #1.
Zone 2
Data I/O
HBA initiator port, SP B port 0 on SAN Copy storage system.
Zone 3
Data I/O
HBA initiator port, SP A port 0 on SAN Copy storage system.
Zone 4
SAN Copy session
SP B port 0 on SAN Copy storage system, SP B port 1 on
remote storage system.
Zone 5
SAN Copy session
SP A port 0 on SAN Copy storage system, SP A port 1 on
remote storage system.
Zone 6
Data I/O
HBA initiator port, SP A port 1 and SP B port 1 on remote
storage system #2
Server
Server
separate server
required for
AX-Series
Storage System
1
2
6
3
Switch Fabric
1
SP A
5
3
1
4
2
SP B
SAN Copy Storage System
1
1
5
6
SP A
4
6
SP B
Remote Storage System
EMC3051
Figure 9
Sample single-initiator zoning with SAN Copy installed and configured
35
SAN Copy Configuration Guidelines
iSCSI zoning requirements and recommendations
Use data replication over iSCSI to replace replication over IP using
FC-IP bridges. Both EMC SAN Copy and EMC MirrorView support
SCSI replication between storage systems that support the feature. In
order to replicate data over iSCSI you must create connection sets
between the participating iSCSI storage systems ports. A connection
set is a named set of information used by a CLARiiON iSCSI initiator
to establish a repliation session with an iSCSI target. A connection set
consists of a unique user-defined name, optional username and
password (secret), credentials usage (connection specific,
array-shared or none), and one or more connection paths. Each
connection set should include only one iSCSI initiator.
EMC recommends that you use the SAN Copy Create Session wizard
or the MirrorView wizard to initially configure connection sets for
iSCSI replication. For informaion on connection sets and using the
wizards, see the Navisphere Manager online help.
You can also use CLI commands to create connection sets - see the
Navisphere Command Line Interface Reference.
36
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
Preparing a CLARiiON storage system for a copy session
If you will be copying data between CLARiiON storage systems or
between CLARiiON and Symmetrix storage systems, follow the SAN
Copy configuration requirements on page 22, and prepare the
CLARiiON storage systems as described in the following procedure.
You can use logical units (LUNs) in a CLARiiON storage system as
the source or destination of SAN Copy sessions.
If you will be copying data between LUNs within a CLARiiON
storage system, see “Copying data between LUNs within a
CLARiiON storage system” on page 26.
Note: For all sessions, you must install SAN Copy software on at least one of
the CLARiiON storage systems.
For incremental copy sessions, the source logical unit must reside in the SAN
Copy storage system.
1. For Fibre Channel replication, use the native switch management
tools to zone at least one port from an SP on the SAN Copy
storage system to one or more SP ports on the participating
remote storage systems (see “Fibre Channel zoning requirements
and recommendations” on page 28).
For iSCSI replication, create connection sets. A connection set
establishes a replication session between an iSCSI initiator and an
iSCSI target. A connection set consists of a unique user-defined
name, optional username and password (secret), method for
assigning security credentials (connection specific, array-shared
or none), and one or more connection paths. Each connection set
should include only one iSCSI initiator. For more information on
connection sets, see the Navisphere Manager online help or the
Navisphere Command Line Interface Reference.
Note: SAN Copy ports act as host initiators to remote storage systems
(storage system without SAN Copy software).
2. Register the SAN Copy ports with any other SP ports in the same
zone using the naviseccli or navicli -h spname sancopy
-updateconnections command (see page 113).
If the remote system is a CLARiiON storage system, the SAN
Copy ports register with each storage system, and the software
adds a record for each SAN Copy port to the storage system’s
37
SAN Copy Configuration Guidelines
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.
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:
naviseccli -h spname -port -list where spname is the name of an SP
in the SAN Copy storage system.
Note: To use this command with navicli, replace naviseccli with navicli.
4. Connect the SAN Copy ports to CLARiiON storage groups (see
the next section, “Connecting SAN Copy ports to CLARiiON
storage groups”).
Connecting SAN Copy ports to CLARiiON storage groups
Note: Each SAN Copy port acts like a host initiator and, therefore, can
connect to only one storage group at a time in a storage system.
In order for the LUNs to be accessible to the SAN Copy ports, you
must connect the SAN Copy ports to the storage groups in which the
LUNs reside. When connecting to the storage group, SAN Copy 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 of a remote 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.
Note: Some operating systems do not support the same host accessing
identical LUNs. Therefore, once SAN Copy completes the copy session, we
recommend that you move any LUN copies to different storage groups.
38
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
For more information on the following CLI commands, refer to the
EMC Navisphere Command Line Interface (CLI) Reference. To use the
navicli CLI command, replace naviseccli with navicli.
1. Use the following command to create storage groups:
naviseccli -h spname storagegroup -create -gname
storagegroupname
2. Use the following command to add LUNs to storage groups:
naviseccli -h spname storagegroup -addhlu -gname
storagegroupname -hlu hlunnumber -alu alunnumber
3. Use the following command (with information from the previous
naviseccli -port -list command) to add the SAN Copy ports to
storage groups:
naviseccli -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
hbawwn is the
World wide name of the SAN Copy 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)
39
SAN Copy Configuration Guidelines
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
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
Figure 10 shows a sample storage group configuration for SAN Copy.
The remote storage system includes three storage groups labeled SG
1, SG 2 and SG 3. SG 1 and SG 2 provide I/O access to the LUNs from
the attached hosts. SG 3 is a SAN Copy storage group.
In this example, we start with two SAN 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
storage system is copying data to LUN 1 in SG 1, and LUN 2 in SG 1
is copying data to the destination LUN on the SAN Copy system.
Since both LUN 1 and LUN 2 belong to the same storage group, you
can connect the same SAN Copy port directly to this storage group
and both sessions can use this SAN Copy port.
In the future, you may want to start a third session that copies data
from source LUN 2 to LUN 3 using the same SAN Copy 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 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.
40
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
Note: Some operating systems do not support the same host accessing
identical LUNs. Therefore, once SAN Copy completes the copy session, we
recommend that you move any LUN copies to different storage groups.
Server
Server
Source LUN 1
LUN1
SG 3
LUN3
Source LUN 2
LUN2
Destination LUN
SG 1
LUN4
SG 2
SAN Copy Storage System
Remote Storage System
EMC2693
Figure 10
What Next?
Sample SAN Copy storage group configuration
To prepare the logical units for a SAN Copy session, go to “Preparing
logical units for a SAN Copy session” on page 51.
41
SAN Copy Configuration Guidelines
Preparing a Symmetrix storage system for a copy session
You can use logical units (volumes) in Symmetrix storage systems as
the source or destination of a full SAN Copy session. For incremental
sessions, the source logical units must reside in a SAN Copy storage
system. In order to prepare a Symmetrix storage system for SAN
Copy sessions, you must follow the SAN Copy configuration
requirements and restrictions onpage 22, and use one of the following
procedures.
Preparing a Symmetrix storage system using EMC ControlCenter SAN Manager
Note: To complete this procedure, you must be familiar with Navisphere
Manager, EMC ControlCenter® SAN Manager, and Solutions Enabler Device
Manager CLI.
1. Use EMC ControlCenter SAN Manager 5.2 or higher to zone at
least one port from an SP on the SAN Copy storage system to one
or more FA ports on the participating Symmetrix storage systems
(see “Fibre Channel zoning requirements and recommendations”
on page 28).
Note: You can also use the native switch management tools to zone a
CLARiiON SP to one or more Symmetrix FA ports.
2. Verify that the host:
• Has access to the Symmetrix volumes that are participating in
the SAN Copy session
• Is running the Navisphere Host Agent
• Is connected to a CLARiiON storage system in the domain, or
• Is part of a portal configuration within the domain. For
information about portals, refer to the Navisphere Manager
online help.
3. Use Navisphere Manager to register the SAN Copy ports with
Symmetrix storage systems.
a. In the Storage tree of the Enterprise Storage window,
right-click the icon for the SAN Copy storage system.
b. Click SAN Copy > Update Connections.
The SAN Copy ports log in to the Symmetrix storage ports.
42
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
4. To verify that the SAN Copy ports have registered with the
Symmetrix storage system, use the Solutions Enabler CLI
command:
symmask -sid symmID list logins
where symmID is the Symmetrix serial ID.
Note: Use the SymmCLI command sympd list -sid to determine the
pathname for the VCM database, or run inq on the host, if available.
5. Use the following Solutions Enabler symmask command to
assign Symmetrix volumes to the SAN Copy ports:
symmask -sid symmID -wwn clariionSPportWWN add devs
SymDevname|SymDevname -dir <#> -p <#>
For example:
symmask -sid 0128 -wwn 11:22:33:44:55:66:77:88 add devs
0014,0015 -dir 16a -p 0
What Next
To prepare the logical units for a SAN Copy session, go to “Preparing
logical units for a SAN Copy session” on page 51.
Preparing a Symmetrix storage system using ESN Manager
Note: To complete this procedure, you must be familiar with both
Navisphere Manager and ESN Manager.
1. Use the native switch management tools to zone at least one port
from an SP on the SAN Copy storage system to one or more FA
ports on the participating Symmetrix storage systems (see “Fibre
Channel zoning requirements and recommendations” on
page 28).
Note: SAN Copy ports act as host initiators to remote storage systems
(storage system without SAN Copy software).
2. Use ESN Manager version 2.1 to place the CLARiiON SAN Copy
ports on the host side of the topology view.
43
SAN Copy Configuration Guidelines
Note: ESN Manager will not allow the CLARiiON SAN Copy ports (SP
ports being used as initiators) to access the Symmetrix volumes unless
the CLARiiON ports are visible on the host side of the topology view.
• If this is a new installation of the CLARiiON storage system,
complete steps a through d in the following procedure.
• If ESN Manager has already discovered the CLARiiON
storage system and it is visible on the storage side of the
topology view, complete steps b through d.
a. Configure ESN Manager to discover the CLARiiON storage
system.
Once ESN Manager discovers the storage system, it places an
icon for it on the storage side of the topology view.
b. Use ESN Manager to move the storage system to the host side
of the topology view.
a. In the Tools menu, click Options > Out Band.
b. In the Out-Band dialog box, select the CLARiiON storage
system and clear the Enable checkbox.
Icons for the CLARiiON SAN Copy ports display as hosts in
the topology view.
3. Verify that the host that has access to the Symmetrix volumes that
are participating in the SAN Copy session, is running the
Navisphere Host Agent, and is either:
• Connected to a CLARiiON storage system in the domain, or
• Part of a portal configuration within the domain. For
information about portals, see the online help or the EMC
Navisphere Manager Command Line Interface Reference.
4. Register the SAN Copy ports with any other SP ports in the same
zone using the navicli -h spname sancopy -updateconnections
command (see page 113).
The SAN Copy ports log in to the Symmetrix storage ports.
44
EMC SAN Copy Command Line Interfaces Reference
SAN Copy Configuration Guidelines
5. To verify that the SAN Copy ports have registered with the
Symmetrix storage system, use the Symmetrix CLI command:
fpath lshist -d physicaldrive
where physicaldrive is the location of the VCM database on this
host.
Note: Use the SymmCLI command fpath lshostdev to determine the
pathname for the VCM database, or run inq on the host, if available.
6. Use ESN Manager to assign Symmetrix volumes to the SAN Copy
ports.
Note: This is the same as assigning volumes to the host initiator.
7. Use ESN Manager to move the CLARiiON storage system back to
the storage side of the topology view.
8. To verify that the SAN Copy port has access to the Symmetrix
remote volumes, click the SAN Copy port entry and, in the
volumes panel, make sure that ESN Manager surrounds any
volumes that are accessible to the SP port with solid blue squares.
If you are copying data to a third-party storage system, use the
third-party storage system management documentation to:
What next?
◆
Verify that the SAN Copy initiator has logged in to the storage
system
◆
Provide access to the volume on the third-party storage system to
the SAN Copy initiator
To create and start a SAN Copy session, continue to Chapter 4, ”SAN
Copy CLI Commands.”
45
SAN Copy Configuration Guidelines
46
EMC SAN Copy Command Line Interfaces Reference
3
Invisible Body Tag
Using the Admhost
Utility with SAN Copy
This chapter explains how to use the Admhost Utility.
◆
◆
◆
About Admhost for SAN Copy ....................................................... 48
Admhost SAN Copy command functions ..................................... 49
Preparing logical units for a SAN Copy session ........................... 51
47
Using the Admhost Utility with SAN Copy
About Admhost for SAN Copy
The Admhost Utility is an executable program that you can run
interactively with a script. The admhost commands can activate and
deactivate the source and destination logical units being used in a
SAN Copy session, and can flush data from operating system buffers
to ensure that the information on the source logical unit is current.
Note: Currently, admhost is supported only on the following Microsoft
Windows platforms: Windows Server 2008, Windows Server 2003, and
Windows 2000. For the supported versions of these operating systems,
see the SAN Copy Release Notes, or the EMC Admhost Release Notes.
48
EMC SAN Copy Command Line Interfaces Reference
Using the Admhost Utility with SAN Copy
Admhost SAN Copy command functions
Table 1 lists the admhost commands and describes their function in
SAN Copy sessions.
Note: 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 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 Symmetrix®
and 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 and Symmetrix 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 drivel_etter 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 SAN Copy session (see “Preparing logical
units for a SAN Copy session” on page 51).
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.
49
Using the Admhost Utility with SAN Copy
Table 1
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 SAN Copy session (see “Preparing logical
units for a SAN Copy session” on page 51).
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 admhost help command is shown below.
Revision number: V1.1.0.0.0 - 0
Valid operations include:
lun_flush, lun_activate,
lun_deactivate, lun_list, and
help.
Valid types include: device and
driveletter.
admhost help
What next?
50
Admhost functions and descriptions (continued)
Before you start a SAN Copy session, complete the steps described in
the next section, “Preparing logical units for a SAN Copy session.”
EMC SAN Copy Command Line Interfaces Reference
Using the Admhost Utility with SAN Copy
Preparing logical units for a SAN Copy session
Before you start a full SAN 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
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 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.
Note: For incremental copy sessions, EMC strongly recommends 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.
51
Using the Admhost Utility with SAN Copy
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:
Note: If the destination logical units are not mounted, ignore this step.
• On a Windows server, 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, 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:
Note: If you want to maintain read access to the source logical unit, skip
this step.
• On a Windows server, 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, use the following command to take the
disk offline:
admhost lun_deactivate -o source-drive letter
52
EMC SAN Copy Command Line Interfaces Reference
Using the Admhost Utility with SAN Copy
For example, to take drive F: offline, enter the following
command:
admhost lun_deactivate -o F:
• On a UNIX server, use the umount command to unmount the
file system on any source logical units.
• On a NetWare server, use the dismount command to
dismount the file system on any source logical units.
What next?
◆
For incremental sessions, mark the session using the sancopy
-mark command on page 88.
◆
For full sessions, you are now ready to start the session using the
sancopy -start command on page 106.
53
Using the Admhost Utility with SAN Copy
54
EMC SAN Copy Command Line Interfaces Reference
4
Invisible Body Tag
SAN Copy CLI
Commands
This chapter explains the sancopy commands used with naviseccli or
navicli CLI commands to manage the SAN Copy software. These
commands function only with a storage system that has the optional SAN
Copy software installed.
Topics are:
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
SAN Copy command functions ....................................................... 56
About Secure CLI ............................................................................... 59
naviseccli ............................................................................................. 60
About Classic CLI .............................................................................. 65
navicli................................................................................................... 66
sancopy -create ................................................................................... 69
sancopy -destinfo ............................................................................... 76
sancopy -duplicate ............................................................................. 80
sancopy -info....................................................................................... 81
sancopy -mark .................................................................................... 88
sancopy -modify................................................................................. 90
sancopy -pause ................................................................................... 98
sancopy -remove ................................................................................ 99
sancopy -resume............................................................................... 101
sancopy -settings .............................................................................. 103
sancopy -start.................................................................................... 106
sancopy -stop .................................................................................... 108
sancopy -throttle............................................................................... 109
sancopy -transfer............................................................................... 111
sancopy -unmark ............................................................................. 112
sancopy -updateconnections .......................................................... 113
sancopy -verify ................................................................................. 114
55
SAN Copy CLI Commands
SAN Copy command functions
The EMC Navisphere CLI provides one of the two interfaces to the
SAN Copy 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 functions are listed functionally, in the order you would
perform them, in the following table.
56
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Table 2
naviseccli or navicli sancopy command functions, listed in order of
use
Command
Description
Essential functions (in order performed)
sancopy -create, or
sancopy -create -incremental
Creates a full SAN Copy session
Creates an incremental SAN 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 SAN 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 SAN Copy sessions or displays
attributes for a particular session
sancopy -stop
Stops a SAN Copy session
sancopy -verify
Ensures that the SAN 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 SAN 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
57
SAN Copy CLI Commands
Table 2
58
naviseccli or navicli sancopy command functions, listed in order of use
(continued)
Command
Description
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
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
About Secure CLI
Note: You can target naviseccli sancopy commands to sessions that
belong to either storage processor. For example if session1 belongs to
SPA, you can issue the naviseccli –h SPBName sancopy –info –name
session1 command to SP B and get the session1 information.
Secure 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 65) 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.
Note: 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.
Note: 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 the
EMC Navisphere Command Line Interface (CLI) Reference.
59
SAN Copy CLI Commands
naviseccli
Sends status or configuration requests to a storage system from a
command line
Syntax
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|2] 3|
[-timeout |-t timeout]
[-user username]
[-v]
[-xml]
CMD [optional_command_switches]
Prerequisites
Anyone that can log in to the host running Navisphere CLI 6.X or
later.
Description
The naviseccli command sends storage-system management and
configuration requests to a storage system with the Internet.
Options
-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.
60
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-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.
Note: 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 that data be stored in a file.
-m
Suppresses output except for values. This option is most useful
when used as part of a script.
Note: 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.
Note: 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.
-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.
61
SAN Copy CLI Commands
-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.
Note: 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.
Note: Only supported for commands that originated in Classic CLI.
-RemoveUserSecurity
Directs the CLI to remove user security information about the
current user from the security file on this host.
62
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-scope 0|1|2
Specifies whether the user account on the storage system you
want to log in to is local, global, or lightweight directory access
protocol (LDAP) where 0 (default) indicates global, 1 indicates
local, and 2 indicates LDAP. For authentication within the local
security directory, specify global or local scope.
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.
LDAP maps the username/password entries to an external LDAP
or active directory server for authentication.
Username/password pairs whose roles are not mapped to the
external directory will be denied access.
-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.
Note: 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.
Note: You can use this switch when establishing a security file to specify
an alternative username. See -AddUserSecurity.
63
SAN Copy CLI Commands
-v
Enables verbose error descriptions. This is the default unless -q is
specified.
Note: Only supported for commands that originated in Classic CLI.
-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.
CMD
One of a set of commands used with the naviseccli command.
CMD switches
Spaces in arguments
The CMD switches are described on the pages that follow.
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").
64
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
About Classic CLI
Note: Starting with the 02.26 and 03.26 release of FLARE, Classic CLI can be
disabled via the Navi UI or a Secure CLI command. Only Secure CLI
supports new features. SecureCLI is more secure than Classic CLI and is the
preferred interface. Other than commands issued to host agents, the R26
version of SecureCLI includes all the same commands as Classic CLI. If you
plan to use Classic CLI commands, you must make sure that Classic CLI is
enabled using the Navisphere Manager UI or SecureCLI command. For a list
of commands that SecureCLI does not support, refer to Appendix B in the
EMC Navisphere Command Line Interface manual , P/N 300-003-628.
Classic 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.
65
SAN Copy CLI Commands
navicli
Sends status or configuration requests to the storage system from
the command line
Syntax
Use the navicli command as follows:
navicli -help
or
navicli [-d device] [-f filename]-h hostname] [ -help] [-m] [-np] [-p] [-t
timeout] -[v|q] CMD [optional-command-switches]
Prerequisites
Description
Anyone that can log in to the host running the Navisphere CLI can
use navicli.
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.
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.
Options
-help
Displays the help screen and does not start the navicli process.
-d device
Specifies the communication channel to the storage system, for
pre-FC4700 SPs only. (A CX-series SP is a host that you specify
with the -h switch. The CLI ignores the -d switch for CX-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 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
66
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
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.
Note: 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.
67
SAN Copy CLI Commands
CMD
One of a set of commands used with the navicli command to
configure and manage a storage system. The CMD (command)
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 FC4700 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:
Note: 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
68
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 Navisphere Command Line Interface (CLI) Reference (for other
errors).
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -create
Creates full and incremental SAN Copy sessions
Syntax
Use the sancopy -create command with naviseccli (described on
page 60) or navicli (described on page 66) as follows:
sancopy -create [-incremental] -name sessionName
-srcwwn source-lun-wwn | -srclun source-sp sourcelunnumber
[-device devicename]
-srcportwwn destportwwn destlunnumber
-destwwn dest-lun-wwn | -destlunnumber dest-sp destlunnumber |
-destportwwn destportwwn destlunnumber
[-start] [-throttle n] [-verify] [-o]
Note: In addition to all the sancopy -create command switches, the sancopy
-create -incremental command uses the following optional switches:
-changesonly, -linkbw, and -latency (See page 73)
Prerequisites
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.
Description
The naviseccli or navicli sancopy command with the -create switch
creates a full SAN 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 SAN Copy session. An incremental session copies only
the data that has changed since the last copy session.
Note: 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.
69
SAN Copy CLI Commands
Options
-name sessionName
Specifies the SAN 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.
For incremental SAN Copy sessions, SAN Copy creates a
corresponding reserved session. The name assigned to the
reserved session consists of the SAN Copy session name
prepended with the text "SANCopy_". This text is included in the
64-character limit. For example, if a SAN Copy session has the
name june_update, the name of the corresponding reserved
session is SANCopy_june_update.
-srcwwn source-lun-wwn
Note: For incremental sessions, the source LUN cannot be a SnapView
snapshot, and it cannot be on a remote system. For incremental sessions,
the source LUN must reside in the SAN Copy storage system.
Specifies the World Wide Name (WWN) of the source logical unit
(LUN or snapshot) that will participate in the session. For full
copy sessions, the source logical unit can reside in either the SAN
Copy storage system or the remote storage system. If the source
logical unit does not reside in the storage system specified by the
-h switch all destination logical units must reside in the storage
system specified with -h.
By default, the connection type for the specified source logical
unit will be set to fibrepreferred. This sets the connection type to
fibre or iSCSI (if fibre path could not be found) each time you start
or resume a session. You can change the connection type using
one of the following switches: -fibre or -iscsi.
Note: If the source logical unit does not reside in a remote storage system,
setting the connection type will be ineffective.
-fibre
Sets the source logical unit’s connection type to Fibre
-iscsi
Sets the source logical unit’s connection type to iSCSI
70
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-srclun source-sp sourcelunnumber
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.
Note: For pre-FC4700 storage systems, if you use the -srclun source-sp
sourcelunnumber function, you must use -device devicename.
By default, the connection type for the specified source logical
unit will be set to fibrepreferred. This sets the connection type to
fibre or iSCSI (if fibre path could not be found) each time you start
or resume a session. You can change the connection type using
one of the following switches: -fibre or -iscsi.
Note: If the source logical unit does not reside in a remote storage system,
setting the connection type will be ineffective.
-fibre
Sets the source logical unit’s connection type to Fibre
-iscsi
Sets the source logical unit’s connection type to iSCSI
-device devicename
Note: This command is required for pre-FC4700 storage systems.
Specifies the device name of the source LUN or destination LUN.
-srcportwwn srcportwwn srclunnumber
Valid only for specifying source LUNs that reside in supported
non-EMC storage systems. For srcportwwn, specify the World
Wide Name of the SP port on the source storage system that owns
the source LUN; for srclunnumber specify the number of the
source LUN.
71
SAN Copy CLI Commands
-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 the
destination logical units are not reachable by the client system,
and you did not use the -o function, the CLI will display a
warning and ask for confirmation.
By default, the connection type for the specified destination
logical unit will be set to fibrepreferred. This sets the connection
type to fibre or iSCSI (if a fibre path could not be found) each time
you start or resume a session. You can change the connection type
with one of the following switches: -fibre or -iscsi.
Note: If the destination logical unit does not reside in a remote storage
system, setting the connection type will be ineffective.
-fibre
Sets the destination logical unit’s connection type to fibre.
-iscsi
Sets the destination logical unit’s connection type to iSCSI.
-destlunnumber dest-sp destlunnumber
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.
By default, the connection type for the specified destination
logical unit will be set to fibrepreferred. This sets the connection
type to fibre or iSCSI (if a fibre path could not be found) each time
you start or resume a session. You can change the connection type
with one of the following switches: -fibre or -iscsi.
Note: If the destination logical unit does not reside in a remote storage
system, setting the connection type will be ineffective.
72
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-fibre
Sets the destination logical unit’s connection type to fibre.
-iscsi
Sets the destination logical unit’s connection type to iSCSI.
-destportwwn destportwwn destlunnumber
Valid only for specifying destination LUNs that reside in
supported non-EMC storage systems. For destportwwn, specify
the World Wide Name of the SP port on the destination storage
system that owns the destination LUN; for destlunnumber specify
the number of the destination LUN.
-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 6.
-verify
Verifies that SAN Copy 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
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 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.
73
SAN Copy CLI Commands
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 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 SAN Copy sessions, or you can specify only a
portion of it.
For CX3-series storage systems, the minimum allowable value
is .016 Mb/sec and the maximum value is 4096. For all other
CX-series storage systems, the minimum allowable value is
.016 Mb/sec and the maximum value is 2048. The default
value is .15 mbps/ (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 computes the latency value), or a decimal number
with no maximum limit. The default value is auto.
Note: If you create and start incremental sessions, and the copy is
performed over a link that is slower than Fibre Channel, SAN Copy
uses the link bandwidth and latency values to calculate the optimum
buffer space for the 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. 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
74
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Examples
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.
Note: To use this command with navicli, replace naviseccli with navicli.
Incremental session example:
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 Mbits/sec., and the latency value
defaults to auto.
Note: To use this command with navicli, replace naviseccli with navicli.
75
SAN Copy CLI Commands
sancopy -destinfo
Displays information about destination logical units for a running
session
Syntax
Use sancopy -destinfo with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -destinfo [-peer]
[-descriptorid descriptorid]|[-name name]
[-destwwn dest-lun-wwn]|[-destlunnumber destsp destlunnumber]
[-destportwwn destportwwn destlunnumber]
[-complete] [-counts] [-failure] [-time] [-connectiontype] [-all]
Note: In addition to all the sancopy -destinfo command switches listed
above, incremental copy sessions use the optional -syncstate switch.
Prerequisites
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.
Description
The naviseccli or navicli sancopy command with -destinfo gets
session status from the destination point of view.
Note: 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 78).
76
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Options
-peer
Lists all destination information for the peer SP.
-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.
-destportwwn destportwwn lunnumber
The switch -destportwwn displays the status of the specified
destination LUN that resides in a supported non-EMC storage
system.
-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.
-failure
Displays failure status or No Failure for destination logical
unit(s). For more information, also use the -time, -counts, and/or
-complete switches.
77
SAN Copy CLI Commands
-time
Displays the time when any destination logical unit(s) failed.
Displays N/A when there is no failure.
-connectiontype
Displays the requested and the actual connection type used for all
destination logical units participating in the copy session.
Valid values for Requested Connection Type are fibre, iSCSI or
fibre preferred. Valid values for Actual Connection Type are
fibre, iSCSI, undetermined and N/A (for destination logical units
within the same storage system).
-all
Displays all destination information for both full and incremental
copy sessions belonging to the specified SP.
Note: 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.
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.
Output
Examples
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.
naviseccli -h
ss1_spa sancopy -destinfo
Copy Descriptor Name: DMHOST7_SAN005_10.6.92.169_00_p000
Copy Descriptor ID: 8
Owner: SPB
Copy Descriptor Type: Incremental
Copy Whole LUN: NO
Source LUN WWN:
60:06:01:60:0E:C2:1C:00:84:C4:31:B2:1C:24:DC:11
Source PortWWN and LUN: N/A
Number of Blocks to Copy: 0
78
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Size of source LUN: 8388608
Number Of Destinations: 2
Destination LUN WWN:
60:06:01:60:61:31:19:00:FD:C8:6D:54:1C:24:DC:11,
60:06:01:60:61:31:19:00:6E:F0:C3:61:1C:24:DC:11
Destination PortWWN and LUN: N/A
Session Status: Complete
Initial Throttle: 4
Current Throttle: 4
Transfer Count: 8388608
Percent Complete: 100
Start Time: 06/27/07 10:51:05
Completion Time: 06/27/07 12:55:12
Duration: 2 hr 4 min 7 sec
Failure Status: No Failure
Marked: NO
Mark Time: N/A
Blocks modified since mark: N/A
Link Bandwidth (Mbps): 1.024
Effective Bandwidth (Mbps): 0.719
Latency (msec): Auto
Measured Latency (msec): 6.140
Requested Connection Type: Fibre Preferred
Actual Connection Type: N/A
The example above displays the output for a full copy session using
the -destinfo command without the -all switch. In order to display all
the information for an incremental copy session, use the -destinfo -all
command.
naviseccli -h
dm340c-16a sancopy -destinfo -connection type
Copy Descriptor Name: Std0_1
Copy Descriptor ID: 7202
Owner: SPA
Requested Connection Type: Fibre Preferred
Actual Connection Type: N/A
Requested Connection Type: Fibre Preferred
Actual Connection Type: N/A
In the example above, the session includes two destination logical
units. The requested connection type and the actual connection type
are displayed for both destinations.
79
SAN Copy CLI Commands
sancopy -duplicate
Makes a copy of a copy descriptor
Syntax
Use sancopy -duplicate with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -duplicate -descriptorid descriptorid | -name name
Prerequisites
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.
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 SAN Copy session. You do not need to stop
the copy descriptor before duplicating it.
Note: The sancopy -duplicate command is not supported for incremental
SAN Copy sessions.
Options
-descriptorid descriptorid | -name name
Identifies the descriptor you want to duplicate.
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_SPECIFIED
DMF_NAME_OR_UID_REQUIRED
DMF_UNKNOWN_DESCRIPTOR
Examples
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.
Note: To use this command with navicli, replace naviseccli with navicli.
80
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -info
Displays information about copy descriptors
Syntax
Use sancopy -info with naviseccli (described on page 60) or navicli
(described on page 66) as follows:
sancopy -info [-peer] [-descriptorid descriptorid | -name name]
[-srcwwn] [-length] [-numdests] [-dests] [-sessionstatus] [-throttle]
[-counts] [-complete] [-time] [-failure] [-duration] [-type]
[-connectiontype] [-all]
Note: In addition to all the sancopy -info command switches listed above,
incremental copy sessions use the following optional switches:
-copywholelun, -markstatus, -srcsize, -link
Prerequisites
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.
Description
The naviseccli or navicli sancopy command with -info displays
information on copy sessions. It differs from -destinfo in that
-destinfo gets information on the destination logical units.
Note: 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 85).
81
SAN Copy CLI Commands
Options
-peer
Lists all destination information on the peer SP.
-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.
-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.
-srcwwn
Displays the WWNs of all source logical units.
-length
Displays the number of blocks to copy. Displays N/A if the
descriptor was created using the source WWN.
-numdests
Displays the number of destination logical units.
-dests
Displays the WWNs of all destinations logical units in the
specified descriptor.
-sessionstatus
Displays the status of the session associated with the copy
descriptor: not started, complete, stop, pause, failed,
This session contains one or more destinations that
require an initial copy (incremental sessions), and The
session has completed successfully and is in an
inconsistent state (unmarked full sessions).
-throttle
Displays the current throttle value for the copy session.
82
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-counts
Displays the number of disk blocks transferred.
-complete
Displays the percentage complete of the copy session.
-time
Displays the time when the copy completes.
-failure
Displays failure status or No Failure for the copy descriptor’s
source and destination logical units.
-duration
Displays the completion time and duration of the session.
-type
Displays the session type - Full or Incremental.
-connectiontype
Displays the requested and the actual connection type used for
the source logical unit participating in the copy session.
Valid values for Requested Connection Type are fibre, iSCSI or
fibre preferred. Valid values for Actual Connection Type are
fibre, iSCSI, undetermined and N/A (for source logical units
within the same storage system).
-all
Displays all session information for both full and incremental
copy sessions belonging to the specified SP.
The following optional switches are used only with incremental SAN
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 only copies the changes.
83
SAN Copy CLI Commands
-markstatus
Note: If a session is marked, SAN Copy 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 Mb/sec.
Effective Bandwidth — Actual link bandwidth for the session
measured by SAN Copy.
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.
Note: 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.
Output
84
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.
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Examples
naviseccli sancopy -info -all
This command displays the status of all copy descriptors for both
SPs, but does not include any information specific to incremental
copy sessions. The format is as follows:
Copy Descriptor name
session1
Copy Descriptor ID:
4
Owner
SP A
Copy Descriptor Type
Full
Source LUN WWN:
60:06:01:60:72:70:18:00:5A:FE:9A:58:0E:5A:DB:11
Source PortWWN and LUN
N/A
Number of Blocks to Copy:
4194304
Number Of Destinations:
1
Destination LUN WWN:
60:06:01:60:72:70:18:00:5B:FE:9A:58:0E:5A:DB:11
Destination PortWWN and LUN
N/A
Session Status:
A session was active when the Storage Processor (SP) rebooted. The
session may be restarted.
Initial Throttle:
6
Current Throttle:
4
Transfer Count:
158720
Percent Complete:
3
Start Time:
10/12/06 16:54:57
Completion Time:
10/12/06 16:59:44
Duration
4 min. 47 sec
Failure Status:
N/A
Copy Descriptor name
ses_change_ar
Copy Descriptor ID:
1
Owner
SP B
85
SAN Copy CLI Commands
86
Copy Descriptor Type
Full
Source LUN WWN:
60:06:01:60:72:70:18:00:C4:AD:19:66:0E:5A:DB:11
Source PortWWN and LUN
N/A
Number of Blocks to Copy:
4194304
Number Of Destinations:
1
Destination LUN WWN:
60:06:01:60:72:70:18:00:C45AD:19:66:0E:5A:DB:11
Destination PortWWN and LUN
N/A
Session Status:
Session is paused.
Initial Throttle:
6
Current Throttle:
6
Transfer Count:
799744
Percent Complete:
19
Start Time:
10/12/06 17:17:37
Completion Time:
N/A
Duration
N/A
Failure Status:
No Failure
Copy Descriptor Name:
SAN000_10.6.84.185_00_p1608
Copy Descriptor ID:
21646
Copy Descriptor Type:
Full
Source LUN WWN:
60:06:01:60:E3:FA:15:00:0E:4E:70:A1:8B:C5:DA:11
Source PortWWN and LUN:
60:06:01:60:E3:FA:15:00:0E:4E:70:A1:8B:C5:DA:11
Number of Blocks to Copy:
2097152
Number Of Destinations:
1
Destination LUN WWN:
60:06:01:60:E3:FA:15:00:0F:4E:70:A1:8B:C5:DA:11
Destination PortWWN and LUN:
N/A
Session Status:
Complete
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Initial Throttle:
4
Current Throttle:
4
Transfer Count:
2097152
Percent Complete:
100
Start Time:
04/19/06 09:55:39
Completion Time:
04/19/06 09:55:57
Duration
18 sec
Failure Status:
No Failure
87
SAN Copy CLI Commands
sancopy -mark
For incremental sessions only. Makes a point-in-time copy of
changes to the source logical unit since the last copy session.
Syntax
Use sancopy -mark with naviseccli (described on page 60) or navicli
(described on page 66) as follows:
sancopy -mark -descriptorid descriptorid | -name sessionName
Prerequisites
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.
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 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.
Note: 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 session” on page 51. Once you receive confirmation that the mark
operation was successful, you can resume I/O to the source logical unit.
Options
-descriptorid descriptorid | -name sessionName
Identifies the session you want to 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:
DMF_NAME_AND_UID_SPECIFIED
DMF_NAME_OR_UID_REQUIRED
DMF_UNKNOWN_DESCRIPTOR
88
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Examples
naviseccli -h 10.11.22.33 sancopy -mark -name monday
This command marks the SAN 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.
Note: To use this command with navicli, replace naviseccli with navicli.
89
SAN Copy CLI Commands
sancopy -modify
Changes the definitions for a copy session
Syntax
Use sancopy -modify with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -modify -descriptorid descriptor-id | -name name
[-adddestbywwn dest-lun-wwn]
[-adddestbylunnumber destsp destlunnumber]
[-adddestbyportwwn destportwwn destlunnumber]
[-chgdestconnectiontypebywwn destwwn]
[-chgdestconnectiontypebylunnumber destspname destlunmumber]
[-chgname newname]
[-chgsrcbylunnumber srcspname srclunnumber]
[-chgsrcbywwn srcwwn]
[-chgsrcbyportwwn srcportwwn srclunnumber]
[-chgsrcconnectiontype srcwwn]
[-chgsessiontype]
[-o]
[-rmdestbylunnumber destsp destlunnumber]
[-rmdestbywwn dest-lun-wwn]
[-rmdestbyportwwn destportwwn destlunnumber
[-throttle n]
Prerequisites
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.
Description
The naviseccli or navicli sancopy command with -modify changes
an existing SAN Copy session. This command will fail if the session
has started or is in the paused state. You must stop the session before
modifying the session.
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.
Note: If you are modifying an incremental SAN Copy session, the following
optional switches are available: -copywholelun, -chglinkbw, and
-chglatency (see “” on page 96).
90
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
Options
-descriptorid descriptorid | -name name
Identifies the descriptor you want to change.
-adddestbywwn dest-lun-wwn
Adds a destination logical unit to the descriptor by world wide
name.
By default, the connection type for the specified logical unit will
be set to fibrepreferred. This sets the connection type to fibre or
iSCSI (if fibre path could not be found) each time you start or
resume a session. You can change the connection type using one
of the following switches: -fibre or -iscsi.
Note: If the logical unit does not reside in a remote storage system,
setting the connection type will be ineffective.
-fibre
Sets the logical unit’s connection type to fibre.
-iscsi
Sets the logical unit’s connection type to iSCSI.
-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.
By default, the connection type for the specified logical unit will
be set to fibrepreferred. This sets the connection type to fibre or
iSCSI (if fibre path could not be found) each time you start or
resume a session. You can change the connection type with one of
the following switches: -fibre or -iscsi.
Note: If the logical unit does not reside in a remote storage system,
setting the connection type will be ineffective.
-fibre
Sets the logical unit’s connection type to fibre.
-iscsi
Sets the logical unit’s connection type to iSCSI.
91
SAN Copy CLI Commands
-adddestbyportwwn destportwwn destlunnumber
Adds only destination logical units that reside in supported
non-EMC storage systems. For destportwwn, specify the World
Wide Name of the SP port on the destination storage system that
owns the destination LUN; for destlunnumber specify the number
of the destination LUN.
-chgdestconnectiontypebywwn destwwn
Changes the connection type of the destination logical unit using
its World Wide Name, destwwn.
You can change the connection type of the logical unit using one
of the following switches: -fibre, -isci, or -fibrepreferred.
Note: If the destination logical unit does not reside in a remote storage
system, setting the connection type will be ineffective.
-fibre
Sets the destination logical unit’s connection type to fibre.
-iscsi
Sets the destination logical unit’s connection type to iSCSI.
-fibrepreferred
Sets the destination logical unit’s connection type to fibre or
iSCSI (if fibre path could not be found).
-chgdestconnectiontypebylunnumber destspname destlunmumber
Changes the connection type of the destination logical unit using
its destination SP (specify the SP name or IP address), destspname
and its destination logical unit number, destlunnumber.
You can change the connection type of the logical unit with one of
the following switches: -fibre, -isci, or -fibrepreferred.
Note: If the destination logical unit does not reside in a remote storage
system, setting the connection type will be ineffective.
-fibre
Sets the destination logical unit’s connection type to fibre.
-iscsi
Sets the destination logical unit’s connection type to iSCSI.
92
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-fibrepreferred
Sets the destination logical unit’s connection type to fibre or
iSCSI (if a fibre path could not be found).
-chgname newname
Note: Not available for incremental sessions.
Changes the descriptor name to newname.
-chgsrcbylunnumber srcspname srclunnumber
Note: Not available for incremental sessions.
Changes the source logical unit in the session owned by source SP
(for srcspname, specify the SP name or IP address) and source
logical unit number.
By default, the connection type for the specified source logical
unit will be set to fibrepreferred. This sets the connection type to
fibre or iSCSI (if fibre path could not be found) each time you start
or resume a session. You can change the connection type with one
of the following switches: -fibre or -iscsi.
Note: If the source logical unit does not reside in a remote storage system,
setting the connection type will be ineffective.
-fibre
Sets the source logical unit’s connection type to fibre.
-iscsi
Sets the source logical unit’s connection type to iSCSI.
-chgsrcbywwn srcwwn
Note: Not available for incremental sessions.
Changes the source logical unit in the descriptor using the World
Wide Name of the new source logical unit
93
SAN Copy CLI Commands
By default, the connection type for the specified source logical
unit will be set to fibrepreferred. This sets the connection type to
fibre or iSCSI (ifa fibre path could not be found) each time you
start or resume a session. You can change the connection type
with one of the following switches: -fibre or -iscsi.
Note: If the source logical unit does not reside in a remote storage system,
setting the connection type will be ineffective.
-fibre
Sets the source logical unit’s connection type to fibre.
-iscsi
Sets the source logical unit’s connection type to iSCSI.
-chgscrbyportwwn srcportwwn srclunnumber
Valid only for changing source logical units that reside in
supported non-EMC storage systems. For srcportwwn, specify the
World Wide Name of the SP port on the source storage system
that owns the source LUN; for srclunnumber specify the number of
the source LUN.
-chgsrcconnectiontype srcwwn
Changes the connection type of the source logical unit using its
World Wide Name(srcwwn).
You can change the connection type of the logical unit with one of
the following switches: -fibre, -isci, or -fibrepreferred.
Note: If the logical unit does not reside in a remote storage system,
setting the connection type will be ineffective.
-fibre
Sets the session connection type to fibre.
-iscsi
Sets the session connection type to iSCSI.
94
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-fibrepreferred
For connections between combo storage systems (Fibre
Channel and iSCSI), sets the connection type to fibre, if
possible. If not possible, uses iSCSI.
-chgsessiontype
Changes the type of the SAN 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 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 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 SAN Copy sessions, or you can specify only a
portion of it. For CX3-series storage systems, the minimum
allowable value is .016 megabits per second (mbps) and the
maximum value is 4096 mbps. For all other CX-series storage
systems, the minimum allowable value is .016 megabits per
second (mbps) and the maximum value is 2048 mbps. The
default value is .15 mbps (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 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.
95
SAN Copy CLI Commands
Note: If you create and start incremental sessions, and the copy is
performed over a link that is slower than Fibre Channel, SAN Copy
uses the link bandwidth and latency values to calculate the optimum
buffer space for the session.
-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 World Wide Name.
-rmdestbyportwwn destportwwn destlunnumber
Valid only for removing destination logical units that reside in
supported non-EMC storage systems. For destportwwn, specify
the World Wide Name of the SP port on the destination storage
system that owns the destination LUN; for destlunnumber specify
the number of the destination LUN.
-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.
For incremental SAN Copy sessions, the following optional switches
are available.
-copywholelun
Specifies that SAN Copy copy the entire contents of the source
logical unit the next time the session is run.
-chglinkbw
Changes the link bandwidth for the specified session.
For CX3-series storage systems, the minimum allowable value is
.016 megabits per second (mbps) and the maximum value is 4096
mbps. For all other CX-series storage systems, the minimum
96
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
allowable value is .016 megabits per second (mbps) and the
maximum value is 2048 mbps. The default value is .15 mbps
(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 computes the latency value), or a decimal number with no
maximum limit. The default value is 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_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
Examples
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 World Wide 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 will copy
the contents of the entire source LUN to the destinations.
Note: To use this command with navicli, replace naviseccli with navicli.
97
SAN Copy CLI Commands
sancopy -pause
Suspends I/O in an active SAN Copy session
Syntax
Use sancopy -pause with naviseccli (described on page 60) or navicli
(described on page 66) as follows:
sancopy -pause -descriptorid descriptor-id | -name name
Prerequisites
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.
Description
The naviseccli or 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.
Options
-descriptorid descriptor-id | -name name
Identifies the descriptor whose session you want to pause.
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_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
Examples
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.
Note: To use this command with navicli, replace naviseccli with navicli.
98
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -remove
Deletes a copy session
Syntax
Use sancopy -remove with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -remove -descriptorid descriptor-id|-name name|-all [-o]
Prerequisites
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.
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, CLI displays a message asking you
confirm the removal of the copy session.
This command can use only one of the following switches at the same
time: -descriptorid; -name; -all
Options
-descriptorid descriptor-id | -name 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.
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_AND_UID_SPECIFIED
DMF_NAME_OR_UID_REQUIRED
DMF_UNKNOWN_DESCRIPTOR
Errors returned from the driver or agent are:
UNKNOWN_DESCRIPTOR_ID
99
SAN Copy CLI Commands
Examples
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.
Note: To use this command with navicli, replace naviseccli with navicli.
100
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -resume
Continues I/O in a SAN Copy session
Syntax
Use sancopy -resume with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -resume -descriptorid descriptor-id | -name name
Prerequisites
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.
Description
The naviseccli or 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.
Options
-descriptorid descriptor-id | -name name
Identifies the descriptor whose session you want to resume.
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 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
SESSION_ALREADY_IN_PROGRESS
101
SAN Copy CLI Commands
Examples
naviseccli -h ss1_spa sancopy -resume -name copy_lun_66
For SP ss1_spa, this command resumes the sancopy_lun_66 copy
session.
Note: To use this command with navicli, replace naviseccli with navicli.
102
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -settings
Lists or changes SAN Copy environmental parameters
Syntax
Use sancopy -settings with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -settings -list
or
sancopy - settings [-setmax MaxNumSessions]
[-setcheckpoint CheckpointInterval] [-setbufsize buffersize]
[-setbufnum buffervalue]
Prerequisites
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.
Description
The naviseccli or navicli sancopy command with -settings gets and
sets four SAN Copy environmental control parameters:
◆
◆
◆
◆
the maximum number of concurrent active sessions, and
a checkpoint interval for session status
number of buffers per session
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.
Options
-list
Displays the current environmental parameter settings.
103
SAN Copy CLI Commands
-setmax maxNumSessions
Sets the maximum number of SAN Copy sessions. The maximum
number of sessions depends on the storage system type.
Storage-system type
Maximum no. of sessions
CX3-series model 80 system,
CX3-series model 40 systems,
CX600, CX700
16 (8 per SP)
CX3-series model 20 systems,
CX400, CX500
8 (4 per SP)
-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, you can start copying from the
beginning.
-setbufsize buffersize
Specifies the maximum buffer size to be used by SAN Copy
sessions on a Fibre Channel connection. The default buffer size is
1024 blocks. The minimum buffer size is 64 KB.
-setbufnum buffernumber
Specifies the maximum number of buffers to be used by SAN
Copy sessions on a Fibre Channel connection. The default
number is 4, and the minimum is 1.
104
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
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_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
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.
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.
Note: To use this command with navicli, replace naviseccli with navicli.
105
SAN Copy CLI Commands
sancopy -start
Starts a SAN Copy session based on values in a copy descriptor
Syntax
Use sancopy -start with naviseccli (described on page 60) or navicli
(described on page 66) as follows:
sancopy -start -descriptorid descriptor-id | -name name
[-copywholelun [-nomark new|all]]
Prerequisites
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.
Description
The naviseccli or 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.
Note: 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 session” on page 51.
When you start a SAN Copy session, SAN Copy automatically allocates and
retains additional memory. This additional memory counts against the total
replication software memory budget.
Options
-descriptorid descriptor-id | -name name
Identifies the copy descriptor for the session you want to start.
For incremental SAN Copy sessions, the following optional switches
are available.
-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
106
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
you start the session using this command, SAN Copy will mark
the session for you. This command overrides any existing settings
for the session.
-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 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 starts an
unmarked session that copies the contents of the source logical
unit to all destinations.
Output
If the FLARE 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
Examples
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.
Note: To use this command with navicli, replace naviseccli with navicli.
107
SAN Copy CLI Commands
sancopy -stop
Stops (terminates) a SAN Copy session
Syntax
Use sancopy -stop with naviseccli (described on page 60) or navicli
(described on page 66) as follows:
sancopy -stop -descriptorid descriptor-id | -name name
Prerequisites
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.
Description
Options
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
SAN Copy operations.
-descriptorid descriptor-id | -name name
Identifies the descriptor whose session you want to stop.
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 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
Examples
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.
Note: To use this command with navicli, replace naviseccli with navicli.
108
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -throttle
Changes the I/O rate of an active copy descriptor
Syntax
Use sancopy -throttle with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -throttle -descriptorid descriptor-id | -name name n
Prerequisites
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.
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 90)
Options
-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.
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_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
109
SAN Copy CLI Commands
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.
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.
Note: To use this command with navicli, replace naviseccli with navicli.
110
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -transfer
Transfers a copy descriptor from the peer SP
Syntax
Use sancopy -transfer with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -transfer -descriptorid descriptor-id | -name name
Prerequisites
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.
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.
Options
-descriptorid descriptor-id | -name name
Identifies the descriptor you want to transfer to the working SP.
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_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
Examples
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.
Note: To use this command with navicli, replace naviseccli with navicli.
111
SAN Copy CLI Commands
sancopy -unmark
For incremental sessions only. Removes the point-in-time copy
from a marked incremental SAN Copy session
Syntax
Use sancopy -unmark with naviseccli (described on page 60) or
navicli (described on page 66) as follows:
sancopy -unmark -descriptorid descriptor-id | -name name
Prerequisites
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.
Description
The naviseccli or navicli sancopy command with -unmark removes
the point-in-time copy from a marked incremental SAN Copy
session.
Note: You cannot unmark a session if any of the session’s destination logical
units have failed.
Options
-descriptorid descriptor-id | -name name
Identifies the session you want to unmark.
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_AND_UID_SPECIFIED
DMF_NAME_OR_UID_REQUIRED
DMF_UNKNOWN_DESCRIPTOR
Examples
naviseccli -h 10.11.22.33 sancopy -unmark -name monday
This command removes the mark from the incremental copy session
named monday.
Note: To use this command with navicli, replace naviseccli with navicli.
112
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
sancopy -updateconnections
Updates connection and registration information
Syntax
Use sancopy -updateconnections with naviseccli (described on
page 60) or navicli (described on page 66) as follows:
sancopy -updateconnections
Prerequisites
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.
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.
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.
Note: To use this command with navicli, replace naviseccli with navicli.
113
SAN Copy CLI Commands
sancopy -verify
Ensures that the SAN Copy software can access a logical unit
Syntax
Use sancopy -verify with naviseccli (described on page 60) or navicli
(described on page 66) as follows:
sancopy -verify
-wwn lun-wwn | -lunnumber sp-name lunnumber
[-device devicename] [-log] [-iscsi|-fibre]
Prerequisites
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.
Description
Options
The naviseccli or 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.
-wwn lun-wwn
Specifies the World Wide Name of the logical units. You can
specify more than one WWN.
-lunnumber sp-name lunnumber
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
Specifies the storage-system device name. This switch is required
for FC4500 and FC5400 storage systems. Omit it for CX-series
storage systems.
-log
Logs events to the SP event log.
Note: If SAN Copy cannot find a LUN on a remote storage system, use
these events to help determine the reason.
114
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Commands
-iscsi |-fibre
Specifies which connection type to use to verify the connection. If
a connection type is not specified, fibre is used first to verfiy the
connection, and if no connection is found, iSCSI is used.
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 Agent
SP A: CPM unable to locate device. Check that the device
with this WWN exists (0x712ac007)
Note: To use this command with navicli, replace naviseccli with navicli.
115
SAN Copy CLI Commands
116
EMC SAN Copy Command Line Interfaces Reference
Invisible Body Tag
A
SAN Copy CLI Error
Codes
This appendix lists the SAN Copy error codes returned by the CLI.
The numbers proceed sequentially.
Note: For reserved LUN pool error codes, refer to Rev. A09 (or later) of the
EMC Command Line Interface (CLI) Reference (P/N 069001038) or Rev. A01 (or
later) of the EMC Command Line Interface (CLI) Reference (P/N 300-003-628).
117
SAN Copy CLI Error Codes
SAN Copy CLI error codes
118
Error Value
Description
236
This version of FLARE software does not support Open SAN Copy.
237
Minimum input requirement for sancopy -create command.
238
Both the name and uid for a copy descriptor are supplied.
239
The name or uid of a copy descriptor is required.
240
Specified destination LUN does not exist.
241
Both the destination LUN wwn and number are supplied.
242
The specified copy descriptor name is not unique to this SP.
243
Specified copy descriptor does not exist.
244
Cannot list and set environment at the same time.
245
Throttle switch must be specified.
246
Valid throttles are 1 to 10.
247
Valid max session numbers are 1 to 16.
248
Valid checkpoint intervals are 5 to 90 and divisible by 5, or disable to set
checkpoint disabled.
249
Both the source wwn and number are specified.
250
The destination LUN size is less than the source LUN size.
251
The peer SP is alive. This command works only if the peer SP is down.
252
Either source or all destinations must be on the host SP.
253
Multiple descriptors have the same name.
254
Input the same LUN ID as the destination LUN more than one time.
255
The specified destination LUN already exists in this descriptor as a
destination.
256
Copy length should be greater than zero.
EMC SAN Copy Command Line Interfaces Reference
SAN Copy CLI Error Codes
Error Value
Description
257
The selected source LUN cannot be part of a SAN Copy session as it is
either a private LUN or is in a transition state.
258
One of the selected destination LUNs cannot be part of the SAN Copy
session as it is either a private LUN or is in a transition state.
259
Capacity of at least one of the destination LUNs is smaller than the source
LUN.
260
Cannot have a SAN Copy session with source LUN on peer SP.
261
Cannot have a SAN Copy session with destination LUN on peer SP.
299
Invalid LUN number of snapshot name for the switch -srclun.
300
Invalid SP name or SP IP address for the switch.
301
Cannot duplicate an incremental copy descriptor.
302
This command can be used only for an incremental SAN Copy session.
303
Cannot mark a session if it is already marked.
304
Cannot unmark a session if it is already unmarked.
305
Cannot specify -nomark switch is session is marked.
306
Cannot specify -copywholeun switch if the session is marked.
307
Source LUN for the incremental descriptor should be on the SP we are
targeting.
308
Snapshot LUN cannot be a source of an incremental copy descriptor.
309
-changesonly can be specified only for an incremental copy descriptor.
310
-copywholelun switch can be specified only for an incremental copy
descriptor.
311
-nomark switch can be specified only for an incremental copy descriptor.
312
Invalid value specified for -chgtype switch.
313
Both -changesonly and -copywholelun switches cannot be specified.
314
Invalid value specified for -nomark switch.
315
This version of FLARE (Core) software does not support incremental SAN
Copy.
316
Invalid link bandwidth value.
119
SAN Copy CLI Error Codes
120
Error Value
Description
317
Invalid link bandwidth problem. Valid values are between 0.016 and 2048.
318
Invalid latency value.
319
Invalid granularity value. Valid values are 2,4,8,16,32 and 64.
320
To create a incremental copy descriptor, you must AT LEAST input
following parameters:
• switch -name and a given name for the new copy descriptor
• switch -srcwwn and its contents OR switch -srclun and its contents
• switch -destwwn and its contents OR switch -destlunnumber and its
contents
• switch -incremental
• switch -linkbw and its value.
321
To modify the descriptor to incremental type, you must provide
the switch -linkbw and its value.
322
Cannot change the name of an incremental session.
323
Cannot specify latency for a full descriptor.
324
Cannot specify granularity for a full copy descriptor.
325
Cannot specify link bandwidth for a full copy descriptor.
339
Cannot change the source LUN of an incremental session.
340
The new descriptor type specified for the descriptor is same as the current
descriptor type.
341
There are no copy descriptors on this SP.
342
Error occurred in removing following descriptors.
343
Value of latency cannot be greater than 4294967
EMC SAN Copy Command Line Interfaces Reference
Index
A
activate command (admhost) 49
admhost
about 48
activate command 49
command functions 48
deactivate command 49
flush command 50
help command 50
list command 50
requirements 48
admhost utility, defined 10
Agent
managed, defined 11
SP, defined 12
agent
host, defined 11
arguments, spaces in 64, 68
B
benefits, SAN Copy 14
C
CLARiiON storage system, preparing for SAN
Copy session 37
CLI subcommands
-create 69
-destinfo 76
-duplicate 80
-info 81
-modify 90
-pause 98
-remove 99
-resume 101
-settings environment parameters, setting
with CLI 103
-start 106
-stop 108
-throttle 109
-transfer 111
-updateconnections 113
-verify 114
CLI, environment variables
RaidAgentDevice 68
RaidAgentHost 68
RaidAgentTimeout 68
CLI, Java
basic commands 60
spaces in arguments 64
CLI, RaidAgent environment variables 68
clone, SnapView, defined 10
command functions, admhost 48
command line format, spaces in 64, 68
copy descriptor
creating (-create) 69
getting information (-info) 81
-create subcommand 69
D
deactivate command (admhost) 49
-destinfo subcommand 76
diagnostics, navicli command 68
domain, defined 10
-duplicate subcommand 80
121
Index
E
R
environment parameters, setting 103
error codes 118
RaidAgent environment variables 68
remote storage system, defined 11
-remove subcommand 99
requirements, admhost 48
reserved LUN pool, defined 11
-resume subcommand 101
F
features, SAN Copy 14
flush command (admhost), about 50
full sessions, defined 11
function switches, admhost 53
H
help command (admhost) 50
I
incremental sessions, defined 11
-info command 81
L
list command (admhost), about 50
logical unit, defined 11
LUN pool, reserved, defined 11
LUN, destination, information (-destinfo
command) 76
lun_activate command (admhost) 49
lun_deactivate command (admhost) 49
lun_flush command (admhost) 50
lun_list command (admhost) 50
M
-mark subcommand 88
-modify subcommand 90
N
navicli command 65
command switches, see individual CLI
subcommands
diagnostics, see error codes
format 66
P
-pause subcommand 98
ports, SAN Copy connecting to CLARiiON
storage groups 38
122
S
SAN Copy
basic configuration requirements and
restrictions 22
connecting SAN Copy ports to CLARiiON
storage groups 38
features and benefits 14
introduction 13
sessions
checkpoint interval, defined 10
defined 12
full, defined 11
incremental, defined 11
preparing CLARiiON storage system for
37
preparing logical units 51
preparing Symmetrix storage system for
42, 43
software components 18
software, defined 12
zoning requirements and recommendations
28, 36
session, starting 106
session, stopping 108
set command 68
-settings subcommand 103
snapshot, SnapView, defined 12
SnapView
clone, defined 10
snapshot, defined 12
software components
command line interface 18
graphical user interface 18
SAN Copy 18
source logical units, deactivate
UNIX 52
Windows 52
spaces in arguments 68
Index
-start subcommand 106
-stop subcommand 108
storage system
CLARiiON, preparing for SAN Copy session
37
SAN Copy, defined 12
Symmetrix, preparing for SAN Copy session
42, 43
Symmetrix storage system, preparing for SAN
Copy session 42, 43
T
-throttle subcommand 109
-transfer subcommand 111
U
-unmark subcommand 112
-updateconnections subcommand 113
V
-verify subcommand 114
Z
zoning
introduction 28, 36
recommendations
based on availability 30
based on performance 29
based on preserving host HBA connections 31
123
Index
124