SRDF 4.2

EMC Enterprise Storage
EMC Solutions Enabler SYMCLI SRDF Component

Version 4.2
PRODUCT GUIDE
P/N 200-999-625-04 REV E
EMC Corporation
Corporate Headquarters: (508) 435-1000, (800) 424-EMC2
171 South Street, Hopkinton, MA 01748-9103 Fax: (508) 435-5374 Service: (800) SVC-4EMC
Copyright 2000 EMC Corporation. All rights reserved.

Printed December 2000 No part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written consent of EMC Corporation. The information contained in this document is subject to change without notice. EMC Corporation assumes no responsibility for any errors that may appear. All computer software programs, including but not limited to microcode, described in this document are furnished under a license, and may be used or copied only in accordance with the terms of such license. EMC either owns or has the right to license the computer software programs described in this document. EMC Corporation retains all rights, title and interest in the computer software programs. EMC Corporation makes no warranties, expressed or implied, by operation of law or otherwise, relating to this document, the products or the computer software programs described herein. EMC CORPORATION DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In no event shall EMC Corporation be liable for (a) incidental, indirect, special, or consequential damages or (b) any damages whatsoever resulting from the loss of use, data or profits, arising out of this document, even if advised of the possibility of such damages.
ii
EMC Solutions Enabler SYMCLI SRDF Component Product Guide
Trademark Information
Compaq is a registered trademark and Compaq Tru64 UNIX is a trademark of Compaq Computer Corporation. Digital UNIX is a registered trademark of Digital Equipment Corporation. HP and HP-UX are registered trademarks of Hewlett-Packard Company Windows, Windows NT, Windows 2000, and MS-DOS are registered trademarks of Microsoft Corporation. Intel is a registered trademark of Intel Corporation. Linux is a registered trademark of Linus Torvalds. OSF/1 and UNIX are registered trademarks of The Open Group. SGI, Silicon Graphics, and CHALLENGE are registered trademarks and IRIX is a trademark of Silicon Graphics, Inc. Sun and Sun Microsystems are registered trademarks and Solaris and SunOS are trademarks of Sun Microsystems, Inc. Siemens and SINIX are registered trademarks of Siemens Nixdorf Information Systems. Sequent, DYNIX, and DYNIX/ptx are registered trademarks of Sequent Computer Systems, Inc. IBM, RISC System /6000, and AS/400 are registered trademarks and RS/6000, SP2, 9337, AIX, AIXwindows, MVS, and ESCON are trademarks of International Business Machines, Inc. EMC, EMC2 (the EMC logo), EMC Enterprise Storage, Symmetrix, DG/UX, and CLARiiON are registered trademarks and ControlCenter, TimeFinder, SRDF, and SymmAPI are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.
iii
iv
Contents
Preface........................................................................................................................... xiii Chapter 1 Overview

SYMCLI SRDF Component .............................................................1-2 SYMCLI .......................................................................................1-2 SRDF Commands.......................................................................1-3 Symmetrix and SYMCLI Fundamentals........................................1-5 SYMCLI and Symmetrix...........................................................1-5 Symmetrix...................................................................................1-5 Symmetrix Device Configuration............................................1-8 Consistency Groups ................................................................1-10
Chapter 2
SRDF Control Operations

Overview............................................................................................2-2 Introduction................................................................................2-2 SRDF Configurations ................................................................2-2 SRDF Modes of Implementation .............................................2-4 Finding SRDF Devices......................................................................2-6 RDF Device Groups...................................................................2-6 Listing RDF Devices ..................................................................2-6 Query SRDF Devices .................................................................2-8 Ping SRDF Devices ....................................................................2-8 Verify SRDF States .....................................................................2-8 SRDF Operations...............................................................................2-9 Types of SRDF Control Operations .........................................2-9 Composite SRDF Control Operations..........................................2-10 Full Establish ............................................................................2-11 Split ............................................................................................2-13
Contents
Incremental Establish..............................................................2-16 Full Restore...............................................................................2-18 Incremental Restore.................................................................2-20 Failover .....................................................................................2-22 Failback .....................................................................................2-24 Update R1 Mirror ....................................................................2-26 Singular SRDF Control Operations..............................................2-29 Suspend.....................................................................................2-30 Resume......................................................................................2-31 Read/Write Enable R1 Mirror ...............................................2-32 Read/Write Enable R2 Mirror ...............................................2-32 Write Disable R1 Mirror..........................................................2-33 Write Disable R2 Mirror..........................................................2-34 Refresh R1 Mirror ....................................................................2-34 Refresh R2 Mirror ....................................................................2-35 Invalidate R1 Mirror................................................................2-36 Invalidate R2 Mirror................................................................2-36 Ready R1 Mirror ......................................................................2-37 Ready R2 Mirror ......................................................................2-37 Not Ready R1 Mirror ..............................................................2-38 Not Ready R2 Mirror ..............................................................2-38 Merge Track Tables..................................................................2-39 SRDF Pair States..............................................................................2-40 RDF Operations and Applicable States .......................................2-42 Setting SRDF Modes.......................................................................2-45 Swapping R1 Devices with R2 ......................................................2-49 symrdf -g Command Line Options ..............................................2-52 All Option .................................................................................2-53 BCV Options.............................................................................2-53 Bypass Option ..........................................................................2-54 Count and Interval Options ...................................................2-54 Force Option.............................................................................2-54 Help Option..............................................................................2-55 No Echo Option .......................................................................2-55 No Prompt Option...................................................................2-55 Offline Option ..........................................................................2-55 R1 or R2 Option .......................................................................2-55 SCSI Reservations Option ......................................................2-55 Consistency State Option .......................................................2-55 Symmetrix ID Option..............................................................2-56 Enabled State Option ..............................................................2-56 Failed Over State Option ........................................................2-56 Partitioned State Option .........................................................2-56
vi
Contents
Split State Option .................................................................... 2-56 Suspended State Option......................................................... 2-56 Suspended Offline State Option ........................................... 2-56 Synchronized State Option .................................................... 2-56 Updated State Option............................................................. 2-56 Update In Progress State Option .......................................... 2-57 Valid State Option ................................................................... 2-57 Until Option............................................................................. 2-57 Verbose Option ........................................................................ 2-57 RA Group Topologies in an SRDF ............................................... 2-58 RA Groups in a Point-to-Point SRDF Link.......................... 2-58 RA Groups in a Switched SRDF Link .................................. 2-59 Various Remote Configurations................................................... 2-60 Relative Symmetrix Manager Functions..................................... 2-65 Consistency Group Operations .................................................... 2-66 Creating a Consistency Group .............................................. 2-68 Adding devices to a group .................................................... 2-68 Enable/Disable Consistency Groups ................................... 2-69 Viewing Consistency Groups ................................................ 2-69 Translating Device Groups to Consistency Groups ........... 2-70 Translating RDBMS Devices to Symmetrix Groups .......... 2-70 Translating Volume Groups to Symmetrix Groups............ 2-71 symrdf -cg Command Line Options............................................ 2-72
Appendix A
SYMCLI SRDF Command Reference

SYMCLI Conventions .................................................................... A-2 symcg ............................................................................................... A-3 symioctl .......................................................................................... A-10 symrdf ............................................................................................ A-16
Appendix B
OSM Compatibility Mode

Compatibility Mode for Existing Symmetrix Manager Sites ....B-2 Installing the Compatibility Mode ...............................................B-3 Migrating SM-CLI Scripts to SYMCLI .........................................B-5
Glossary ......................................................................................................................... g-1 Sales and Service Locations .................................................................................s-1 Index ................................................................................................................................ i-1
vii
Contents
viii
Figures
1-1 1-2 1-3 1-4 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16
Symmetrix Components .............................................................................. 1-6 Storage Device Names Using SYMCLI ..................................................... 1-8 Consistency Groups Cope with RDF Link Failure ................................ 1-11 All Data Propagation is Suspended upon any Link Failure ................ 1-12 SRDF Configurations ................................................................................... 2-3 SRDF Extended Distance Solution ............................................................. 2-4 Switched (Fabric) RDF Topology ............................................................... 2-5 Establishing an SRDF Pair ......................................................................... 2-12 Splitting an SRDF Pair ............................................................................... 2-14 Incremental Establish of an SRDF Pair .................................................... 2-17 Restoring an SRDF Device ........................................................................ 2-19 Incrementally Restoring an SRDF Device ............................................... 2-21 Failover of an SRDF Device ...................................................................... 2-23 Failback of an SRDF device ....................................................................... 2-25 Update of SRDF Device Track Tables ...................................................... 2-27 RA Group Topology in a Point-to-Point SRDF Solution ...................... 2-58 RA Group Topology in a Switched RDF Solution ................................. 2-59 Various Remote Configurations ............................................................... 2-62 Remote Multi-Hop SRDF Configurations ............................................... 2-64 All Data Propagation is Suspended upon any Link Failure ................ 2-67
ix
Figures
Tables
1-1 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 A-1 A-2 A-3 A-4 B-1
SRDF Control Operations ............................................................................ 1-3 Composite SRDF Control Operations ..................................................... 2-10 Singular SRDF Control Operations .......................................................... 2-29 SRDF States for Each RDF Pair ................................................................. 2-40 RDF Control Operations and Applicable States .................................... 2-42 RDF Device Data Preservation for a Swap ............................................. 2-50 RDF Device States for Swap Operation ................................................... 2-51 symrdf -g Control Arguments and Applicable Options ....................... 2-52 symrdf -g View Arguments and Applicable Options ........................... 2-53 Symmetrix Manager Relationship ........................................................... 2-65 symrdf -cg Control Arguments and Applicable Options ..................... 2-72 symrdf -cg View Arguments and Applicable Options ......................... 2-73 Specifiying Objects with symioctl ........................................................... A-10 Databases and Platforms for symioctl .................................................... A-11 System DB Environment Variables ......................................................... A-12 symioctl DB Environment Variables ...................................................... A-12 Symmetrix Manager Relationship ............................................................. B-5
xi
Tables
xii
Preface
As part of its effort to continuously improve and enhance the performance and capabilities of the Symmetrix product line, EMC periodically releases new revisions of Symmetrix hardware and microcode. Therefore, some functions described in this manual may not be supported by all revisions of Symmetrix microcode, software, or hardware presently in use. If your Symmetrix unit does not offer a function described in this manual, please contact your EMC representative for a hardware, software, or microcode update. This manual provides both guide and reference information for command-line users and script programmers that describes how to manage SRDF devices using the SYMCLI commands of the EMC Solutions Enabler software. The following defines the structure of this manual: Chapter 1, Overview, highlights the SYMCLI SRDF Component features, SYMCLI commands, and terminology. Chapter 2, SRDF Control Operations, describes how to monitor and control SRDF devices using SYMCLI. Appendix A, SYMCLI SRDF Command Reference, describes the SRDF component set of commands and their syntax. Appendix B, OSM Compatibility Mode, describes the issues concerned with adapting and/or migrating your current Open Symmetrix Manager SM-CLI scripts to the SYMCLI Solutions Enabler environment.
xiii
Preface
Related Documentation
Other Symmetrix publications of related interest are: EMC Solutions Enabler SYMCLI Base Component Product Guide, P/N 200-999-624, EMC Corporation EMC Solutions Enabler SYMCLI TimeFinder Component Product Guide, P/N 200-999-634, EMC Corporation EMC Solutions Enabler SYMCLI Mapping Component Product Guide, P/N 300-999-037, EMC Corporation EMC Solutions Enabler Installation Guide, P/N 200-999-635, EMC Corporation Symmetrix Remote Data Facility Product Guide, P/N 200-999-554, EMC Corporation Symmetrix Open Systems Host Environment Product Guide - Volume I and II, P/N 200-999-563, EMC Corporation Symmetrix Manager Base Component for UNIX Product Guide, P/N 200-999-568, EMC Corporation Symmetrix Manager, SRDF Component for UNIX, Product Guide, P/N 200-999-565, EMC Corporation Symmetrix High Availability Product Guide, P/N 200-999-566, EMC Corporation
Conventions Used in this Manual
The following conventions are used in this manual: In this manual, every use of the word SYMCLI means EMC Solutions Enabler.
Note: A note calls attention to any item of information that may be of special importance to the reader.
CAUTION A caution contains information essential to avoid damage or degraded integrity to storage of your data. The caution might also apply to protection of your software or hardware.
xiv
Preface
Boldface provides extra emphasis and emphasizes warnings, and specifies window names and menu items in text. Italic emphasizes new terms, identifies variables in a software syntax (non-literal notation), identifies unique word usage, and applies emphasis in examples and in references to book titles and sections.
A fixed space font identifies files and path names, and is used in command line entries, displayed text, or program listings.
Where to Get Help
EMC software products are supported directly by the EMC Customer Support Center. Obtain technical support by calling the EMC Customer Support Center at one of the following numbers: United States: Canada: Worldwide: (800) 782-4362 (SVC-4EMC) (800) 543-4782 (543-4SVC) (508) 497-7901
or by calling the number of the nearest EMC office listed at the back of this book.
Language services are available upon request.
Your Comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please e-mail us at techpub_comments@emc.com to let us know about your opinion or any errors concerning this manual.
xv
Preface
xvi
1
Overview
This chapter provides an overview of the Symmetrix Command Line Interface (SYMCLI) SRDF Component, and a discussion of the fundamentals of the SYMCLI. SYMCLI SRDF Component ..............................................................1-2 Symmetrix and SYMCLI Fundamentals.........................................1-5
Overview
1-1
Overview
SYMCLI SRDF Component

SYMCLI
The Solutions Enabler (known as SYMCLI) is a specialized library or set of UNIX formatted commands that can be invoked one at time. The SYMCLI (Symmetrix Command Line Interface) is used in single command line entries and scripts to map and perform control operations on devices and data objects toward the management of your storage complex. It also monitors device configuration and status of devices that make up the storage environment. The target storage environments are typically Symmetrix based but can be CLARiiON when you have the license and work with the SYMCLI Mapping component. The SYMCLI SRDF Component extends the basic SYMCLI command set to include SRDF commands that allow you to perform control operations on RDF devices in a Symmetrix Remote Data Facility. SRDF Devices The Symmetrix Remote Data Facility (SRDF) is a business continuance solution that maintains a mirror image of data at the device level in Symmetrix systems located in physically separate sites. SRDF provides a recovery solution for component or site failures using remotely mirrored devices. SRDF reduces backup and recovery costs and significantly reduces recovery time after a disaster. In an SRDF configuration, the individual Symmetrix devices are designated as either a source or a target to synchronize and coordinate SRDF activity. If the source (R1) device fails, the data on its corresponding target (R2) device can be accessed by the local host. When the source (R1) device is replaced, the source (R1) device can be resynchronized. SRDF configurations have at least one source (R1) device mirrored to one target (R2) device. A source (R1) device can only belong to an RDF1 device group, while a target (R2) device can only belong to an RDF2 device group.
1-2
Overview
1
SRDF Commands
Table 1-1
The SRDF commands allow you to perform control operations on SRDF devices (refer to Table 1-1).
SRDF Control Operations Command symcg Description Performs the following control operations on a Symmetrix RDF consistency groups: Creates and deletes consistency groups Adds and removes devices of a consistency group Shows detailed information about a consistency group Enables or disables the consistency mode of a device group Sends I/O control commands to a specified server application. Places objects into hot backup mode Freezes or thaws I/O to a specifed database application Issues a checkpoint to the RDBMS Archives the current log Performs the following control operations on RDF devices: Establishes (mirror) an RDF pair by initiating a data copy from the source (R1) side to the target (R2) side. This operation can be a full or incremental establish Restores remote mirroring. Initiates a data copy from the target (R2) side to the source (R1) side. This operation can be a full or incremental restore Splits an RDF pair, which stops mirroring for the RDF pair(s) in a device group Failover from the source (R1) side to the target (R2) side, switching data processing to the target (R2) side Failback from the target (R2) side to the source (R1) side, switching data processing to the source (R1) side Updates the source (R1) side after a failover, while the target (R2) side may still be operational to its local host(s) Swaps R1 and R2 designations between the target and source.
symioctl
symrdf
The symrdf command also performs operations including: Setting the RDF mode for one or more RDF pairs in a device group Returning information about the state of RDF mirroring
SYMCLI SRDF Component
1-3
Overview
1
Ping one or more Symmetrix units locally or remotely via SRDF links Singular SRDF control operations, which are the individual operations that comprise the composite SRDF control actions.
The following section is an introduction of the SYMCLI Base Component, and the basic features which are used or referenced by the SRDF Component.
1-4
Overview
Symmetrix and SYMCLI Fundamentals

SYMCLI and Symmetrix
SYMCLI resides on a host system to monitor and to perform control operations on Symmetrix units. SYMCLI commands are invoked from the host operating system command line (shell). The commands are linked with SYMAPI library functions. The library functions use system calls that generate low-level I/O SCSI commands to the Symmetrix units. To reduce the number of inquiries from the host to the Symmetrix units, configuration and status information is maintained in a Symmetrix host database file. On a UNIX system, when you run symcfg discover, a Symmetrix host database file, symapi_db.bin, is created in /var/symapi/db. On Windows NT, the database file is found under C:\Program Files\EMC\Symapi\db.
Symmetrix
Symmetrix is an integrated cached disk array (ICDA) designed for on-line data storage. A host system and Symmetrix communicate via one or more SCSI or Fibre Channel interfaces. Figure 1-1 illustrates the major functional components of a Symmetrix unit and its connection to a host system.
Major Components
1-5
Overview
Figure 1-1
Symmetrix Components
A front-end director (SA) is a card (also called a SCSI adaptor) that occupies one slot on the Symmetrix backplane. The host to Symmetrix connection is a SCSI bus cable. Your host to Symmetrix connection could also be a fibre network that uses a fibre adapter (FA) type front-end director in the Symmetrix unit. Microcode on the front-end director handles I/O requests from the host. It determines if a request can be satisfied out of Symmetrix cache memory and maintains data in cache (based on data access patterns). On a write request, the front-end director writes data to cache. A disk director later destages this data from cache to the appropriate physical disk. A Symmetrix unit can have from two to sixteen front-end directors (depending on the requirements and Symmetrix model). Each SA front-end director has two or four ports. FA and RF directors have one port. Cache memory resides on cards that occupy as many as four slots on a Symmetrix backplane. Cache memory stores currently active data. Both front-end directors and disk directors share cache.
1-6
Overview
1
A disk director (DA) is a card that occupies one slot on the Symmetrix backplane. Microcode on the card manages access to specific disk drives. This back-end director transfers data from disk to cache and destages the write-bound data from cache to disk. A Symmetrix can have up to 64 directors, depending on the Symmetrix model. Storage Devices From the perspective of software running on a host system, a Symmetrix unit appears to be a number of physical devices connected via I/O connections to one or more I/O controllers. A host application addresses each of these devices using a physical device name. Each physical device includes the attributes: vendor ID, product ID, revision level, and serial ID. As shown in Figure 1-2, a Symmetrix device can map to a part of a physical disk or to an entire disk. The part of a physical disk to which a Symmetrix device is mapped is called a hyper-volume or a hyper. Device Groups A Symmetrix device is assigned a logical name when the device is added to a device group. A device group represents several devices and can be created to provide configuration, status, and performance data on the collective devices within the device group. For example, a device group can be created to include all the physical devices used in a database application. The device group for the database application includes three devices with logical names dev1, dev2, and dev3. Devices dev1 and dev2 are mirrored, and a third device, dev3, is a RAID-S device. As shown in Figure 1-2, the mirrored hyper volumes are represented by the shaded layers of the devices.
1-7
Overview
Host
Standard DEV001
Standard DEV002
Standard DEV003
DEV001
DEV002
DEV003
Four Hyper Volumes
DEV002 M1 DEV001 M1
M1
Mirrors
DEV002 M2
M2
DEV001 M2
DEV003
Parity Data
RAID-S Group
Symmetrix
Figure 1-2
Storage Device Names Using SYMCLI
Symmetrix Device Configuration
All host I/O transactions with the Symmetrix use Symmetrix cache on a front-end director. Because no disks are involved in the I/O protocol, Symmetrix devices assume the following configuration attributes: Each device has N cylinders. This number is configurable (blocks 960). Each cylinder has 15 tracks (heads). For fixed block architecture (FBA) devices, each track has 64 blocks of 512 bytes.
1-8
Overview
1
Gatekeeper Devices SCSI commands executed by SYMAPI are transferred to the Symmetrix via a Symmetrix device that is designated as a gatekeeper device. The gatekeeper allows you to retrieve configuration and status information from the Symmetrix without interfering with normal Symmetrix operations. By default, one of the available Symmetrix devices is designated as a gatekeeper. Alternatively, you can establish the use of specific devices as gatekeepers. BCV Devices The Symmetrix TimeFinder is a business continuance solution which allows you to use special Business Continuance Volume (BCV) Symmetrix devices. A BCV device contains a copy of data from a standard Symmetrix device which are online for regular I/O operation from their host(s). Uses for the BCV copies can include backup, restore, Decision Support, and applications testing. Each BCV device has its own host address, and is configured as a stand-alone Symmetrix device. A business continuance sequence first involves establishing the BCV device as a mirror of a specific standard Symmetrix device. As a result, the BCV device becomes inaccessible via its original device address while it is in an established pair. Once the BCV device is synchronized, it may be separated (split) later from the standard device with which it is paired. The BCV device with the synchronized data becomes available for backup or other host processes through its original device address. Once host processing on the BCV device is complete, the BCV may again be mirrored to a standard Symmetrix device, either the same device to which it was previously paired, or with a different device. Meta Devices Meta devices allow individual devices to be concatenated to create larger devices. Meta devices must be adjacent Symmetrix devices and are formed by grouping physical devices that follow each other. The meta head is the first device in the meta device and is responsible for receiving incoming commands. When an incoming command for the meta head is processed, the Symmetrix determines which meta device member should execute the command. Standard meta head devices can be added to a device group while a standard meta member cannot be added to a device group. Similarly, BCV meta head devices can be associated with a device group, while a BCV meta member cannot be associated with a device group.
1-9
Overview
1
Consistency Groups
In an SRDF environment using PowerPath connected devices of the Symmetrix units, consistency group configurations are possible. Controlled by the host via SRDF links, consistency groups operate in unison to maintain the integrity and consistency of a database distributed across multiple SRDF units. When a typical DBMS application updates a database, it first writes to the disk containing a log, then it writes the data to the actual database datafiles. Finally it writes again to the log volume to flag these write I/Os (log database) that are related. Even in a remote disk copy environment, data consistency can not be ensured if one of these I/Os was remotely mirrored, but its predecessor was not remotely mirrored. This could occur, for example, in a rolling disaster where there is a communication loss that affects only a portion of the disk controllers that are performing the remote copy function. SRDF established consistency groups can prevent this from occurring by the PowerPath pseudo device driver intercepting any I/O to a disk device that cannot communicate to its remote mirror. The consistency protocol is to then suspend the remote mirroring for all devices defined to the consistency group before the intercepted I/O and returning control to the application. In this way, consistency groups prevent dependent I/O from getting out of sync, thus ensuring the integrity and consistency of the data at the remote site. Architecture Using PowerPath connected devices, consistency groups maintain coherency for an SRDF configuration by monitoring data propagation from the source (R1) devices in a consistency group to their corresponding target (R2) devices (see Figure 1-3). Figure 1-3 is an example of a Symmetrix A and B unit containing source devices in an established consistency group, which are mirrored by target devices of remote Symmetrix A and B.
1-10
Overview
Figure 1-3
Consistency Groups Cope with RDF Link Failure
If one or more source (R1) devices in a consistency group can not propagate data to their corresponding target (R2) devices, the PowerPath connected consistency group devices suspend all the source (R1) propagation from these devices in the consistency group. This ensures that all data flow to the consistency groups target (R2) side is instantly and completely halted (see Figure 1-4), and that a consistent database (up to the point in time of data propagation failure) exists on the remote side of the configuration. This enables applications to still use the remote database.
1-11
Overview
Figure 1-4
All Data Propagation is Suspended upon any Link Failure
I/O to the local consistency group devices can still occur when the RDF source (R1) devices in the consistency group are suspended. While these updates are not immediately sent to the remote side, they are propagated through normal SRDF operation once SRDF mirroring is resumed. Consistency groups can be created and maintained with the symcg SYMCLI command. Consistency group control operations with SYMCLI are described in Chapter 2.
1-12
2
This chapter presents an overview of the Symmetrix Remote Data Facility (SRDF) operations and how the SRDF can be managed using SYMCLI. The terms SRDF and RDF used throughout this chapter, refer to the Symmetrix Remote Data Facility. Overview .............................................................................................2-2 Finding SRDF Devices.......................................................................2-6 SRDF Operations................................................................................2-9 Composite SRDF Control Operations ...........................................2-10 Singular SRDF Control Operations ...............................................2-29 SRDF Pair States ...............................................................................2-40 RDF Operations and Applicable States ........................................2-42 Setting SRDF Modes ........................................................................2-45 Swapping R1 Devices with R2 .......................................................2-49 symrdf -g Command Line Options ...............................................2-52 RA Group Topologies in an SRDF .................................................2-58 Various Remote Configurations.....................................................2-60 Relative Symmetrix Manager Functions ......................................2-65 Consistency Group Operations......................................................2-66 symrdf -cg Command Line Options .............................................2-72
2-1
Overview
Introduction
The Symmetrix Remote Data Facility (SRDF) is a business continuance solution that maintains a mirror image of data at the device level in Symmetrix systems located in physically separate sites. SRDF provides a recovery solution for component or site failures between remotely mirrored devices. SRDF reduces backup and recovery costs and significantly reduces recovery time after a disaster. In an SRDF configuration, the individual Symmetrix devices are designated as either a source or a target to synchronize and coordinate SRDF activity. If the source (R1) device fails, the data on its corresponding target (R2) device can be accessed. When the source (R1) device is replaced, the source (R1) device can be resynchronized. SRDF configurations have at least one source (R1) device mirrored to one target (R2) device.
SRDF Configurations
SRDF configurations provide for either a uni-directional or a bi-directional data transfers. In a uni-directional SRDF configuration, all source (R1) devices reside in one Symmetrix unit and all target (R2) devices in the other Symmetrix unit. Data flows from the source (R1) devices to the target (R2) devices. In a bi-directional configuration, both source (R1) and target (R2) devices reside in each Symmetrix unit, as a master or slave, in the SRDF configuration. Data flows from the source (R1) devices to the target (R2) devices. Figure 2-1 illustrates the SRDF bi-directional configuration where both source (R1) and target (R2) devices reside within a Symmetrix. Data flows from the source (R1) device in each respective Symmetrix to the target (R2) device.
2-2
Figure 2-1
SRDF Configurations
A source (R1) device can only belong to a device group of type RDF1, while a target (R2) device can only belong to a device group of type RDF2.
Note: In this chapter, each source (R1) device and its corresponding target (R2) device form an RDF pair.
Overview
2-3
2
SRDF Modes of Implementation
SRDF point-to-point network implementations are the Campus Solution, and the Extended Distance Solution. The SRDF Campus Solution shown in Figure 2-2 allows Symmetrix units to be located up to 60 km (37.5 miles) apart using fiber-optic links and even farther (1000s miles) with extended distance solutions such as FarPoint. Synchronous, semi-synchronous, or adaptive copy operational modes are available for this solution. The Campus Solution supports both uni-directional and bi-directional SRDF connections.
Site A Host
Site B Host
Figure 2-2
SRDF Extended Distance Solution
The SRDF Extended Distance Solution allows the Symmetrix units to be located over 37.5 miles (60 km) apart using a T1/T3 or E1/E3 links. Figure 2-2 illustrates a Symmetrix at Site A connected via a T1 connection to a Symmetrix at Site B.
2-4
2
Switched RDF Environments An SRDF topology can incorporate open network switching (fabric) in the RDF links (see Figure 2-3). The switched RDF involves non-blocking switching devices that interconnect two or more nodes. Symmetrixes in a switched RDF topology can have each port pair running full-duplex.
Site A Host
Site B Host
Switched RDF Switched (Fabric) RDF Links Site C Host
Figure 2-3
Switched (Fabric) RDF Topology
Overview
2-5
Finding SRDF Devices

Configuration and status information can be viewed for each device on every Symmetrix containing SRDF devices. Using SYMCLI you can find all SRDF devices on a Symmetrix and view their physical (host) and Symmetrix device names. In addition, you can display details about the SRDF devices, the number of invalid tracks for both the SRDF source device and the target device, and the various SRDF device states. You can find all Symmetrix units that are reachable via the SRDF links. For example, to view how Symmetrix units are attached to your host, enter:
symcfg list
RDF Device Groups
The symdg command lists the device groups by name, and also by group type. To view all device groups that have been created in your host database file, enter:
symdg list
If the type of group is RDF1, or RDF2, the group is an SRDF group.
Listing RDF Devices
You can list the SRDF devices that are visible to your host, or SRDF devices that are configured on a given Symmetrix unit. For example, to list the SRDF devices that are visible to your host, enter:
symrdf list pd
2-6
2
The results provide details about the SRDF devices, source (R1) and target (R2), their device groups (if any), including: Symmetrix device name Remote Symmetrix device name RDF type and RA number Status of the SA, RA, and SRDF Links SRDF mode Domino mode Adaptive Copy mode Number of invalid tracks on R1 and R2 SRDF link state RDF states on the device, remote device, and SRDF pair
For example, to obtain detailed information on all SRDF devices in Symmetrix unit 123, enter:
symrdf -v -sid 123 list dev
By default, the symrdf list command provides a listing of all SRDF devices available, including SRDF BCV devices.
symrdf list
To display only the SRDF standard devices in the Symmetrix unit 123, enter:
symrdf -sid 123 -nobcv list
You can display the R1 devices separately, or the R2 devices separately by using the -R1 or -R2 option. For example, if you want to display only the SRDF R1 devices in the Symmetrix unit 123, enter:
symrdf -sid 123 -R1 list
Finding SRDF Devices
2-7
2
Query SRDF Devices
To further view the SRDF details about all devices in device group prod, enter:
symrdf -g prod query
The query results provide details about each SRDF pair in the device group, including: Logical device name Physical device name Number of invalid tracks on R1 and R2 SRDF link state RDF modes RDF local and remote SRDF states RDF pair state
Ping SRDF Devices
You can use the symrdf -rdf ping option to determine if a Symmetrix unit that is connected via SRDF links is up and running. The Symmetrix unit(s) are pinged via the SRDF links. Based on return codes, you can determine whether some or all of the Symmetrix units were successfully pinged. For more information on return codes, refer to Appendix A. For example, to ping the Symmetrix unit 123 via the SRDF links, enter:
symrdf -rdf -sid 123 ping
Verify SRDF States
You can verify that the SRDF pairs are in the Synchronized or Restored states. For example, to verify that the SRDF pair DEV007, in device group prod, is in the Synchronized state, enter:
symrdf -g prod verify DEV007
2-8
SRDF Operations
SRDF control operations, which are performed with the symrdf command support the high level operations of the SRDF environment such as failover (disaster recovery), backup or copy (decision support), and concurrent operations. Refer to the Open Symmetrix Manager SRDF Component Product Guide for general information about these operations.
Types of SRDF Control Operations
The SYMCLI symrdf command performs these operations with low level control operations, which are defined as two types: composite and singular operations. Several singular operations may comprise a composite operation.
Note: Most SRDF operations can be performed with just composite SRDF control operations. It is recommended you use the singular control operations sparingly.
The composite SRDF control operations are described next. The singular SRDF control operations are described in Singular SRDF Control Operations on page 2-29.
SRDF Operations
2-9
Composite SRDF Control Operations

In order to manage SRDF devices, you will need to invoke composite control operations of the symrdf command on a device group of remotely mirrored devices, such as a device group of type RDF1 or RDF2. Table 2-1 outlines the composite SRDF control operations, the corresponding symrdf option, and the results of implementing the symrdf command.
Table 2-1
Composite SRDF Control Operations symrdf Options -full establish Results Establishes remote mirroring and initiates a full data copy from the source (R1) device to the target (R2) device. Establishes remote mirroring and initiates an incremental data copy from the source (R1) device to the target (R2) device. Resumes remote mirroring and initiates a full data copy from the target (R2) device to the source (R1) device. Resumes remote mirroring and initiates an incremental data copy from the target (R2) device to the source (R1) device. Stops remote mirroring between the source (R1) device and the target (R2) device. The target device is made available for local host operations. Switches data processing from the source (R1) side to the target (R2) side. Switches data processing from the target side (R2) back to the source (R1) side. Updates the source (R1) side with the changes from the target (R2) side while the target (R2) side is still operational to its local host(s). Swaps the source (R1) desginations with the target (R2) designations.
Control Operation Establishing an SRDF pair Incrementally Establishing an SRDF pair Restoring from a target (R2) device Incrementally Restoring from a target (R2) device Splitting an SRDF pair
establish
-full restore restore
split
Failover Failback Update R1 mirror
failover failback update
Swap R1 designations with R2 types
swap
2-10
2
The SRDF control operations listed in Table 2-1 invoke several singular SRDF control operations, which are listed in Table 2-2 on page 2-29. The singular SRDF control operations are described in Singular SRDF Control Operations on page 2-29. The composite SRDF control operations outlined in Table 2-1 are described in the following pages of this section.
Full Establish
You need to perform a full establish on SRDF pairs only when you are initially setting up SRDF pairs, or when your R2 member of an RDF pair is either fully invalid, or has been replaced. All the RDF pairs must be in the split state before you establish the pairs. When the establish control operation has successfully completed, the SRDF pairs will contain identical data, and be in a Synchronized state. You can use verify to confirm that the SRDF pair(s) are in the Synchronized state and remote mirroring is resumed. For example, to initiate an establish for all the SRDF pairs in the device group prod, enter:
symrdf -g prod establish -full
To initiate an establish for one SRDF pair with logical device DEV001 in the device group prod, enter:
symrdf -g prod establish -full DEV001
To initiate an establish for a list of SRDF pairs in the device group prod, enter:
symrdf -g prod establish -full DEV001 DEV002 DEV003
To initiate a full establish, all RDF pairs in the group must already be in one of the following states: Split Suspended and write disabled or not ready at the source
Figure 2-4 illustrates the establishing of an SRDF pair. The SRDF pair consists of the source (R1) device which is mirrored to the target (R2) device.
2-11
Figure 2-4
Establishing an SRDF Pair
When a full establish is initiated for each specified RDF pair in a device group: The target (R2) device is write disabled to its local host(s). The tracks on the target (R2) device are marked invalid. The track tables are merged between the source (R1) device and the target (R2) device. Traffic is resumed on the SRDF links.
The SRDF pair is in the Synchronized state when the source (R1) device and the target (R2) device contain identical data.
This operation will be rejected if the source has invalid local (R1) tracks.
2-12
2
Split
You need to split SRDF pairs when you require read and write access to the target (R2) side of one or more devices in the device group. For example, to perform a split on all the SRDF pairs in the prod group, enter:
symrdf -g prod split
To perform a split on one SRDF pair with logical device DEV001 in the prod group, enter:
symrdf -g prod split DEV001
To initiate a split to a list of SRDF pairs in the device group prod, enter:
symrdf -g prod split DEV001 DEV002 DEV003
To invoke a split, the RDF pair(s) must already be in one of the following states: Synchronized Suspended R1 Updated SyncInProg and the -force option is specified
Figure 2-5 illustrates the splitting of an SRDF pair. The SRDF pair consists of the source (R1) device which is remotely mirrored to the target (R2) device.
2-13
Figure 2-5
Splitting an SRDF Pair
When a split is performed for each specified RDF pair in a device group: Traffic is suspended on the SRDF links. The target (R2) device is read/write enabled to its local host(s).
After the target (R2) device is split from the source (R1) device, the SRDF pair is in the Split state.
This operation will be rejected if any of the following occur: If the source has invalid local (R1) tracks If the target has invalid local (R2) tracks If the device pairs are in the device domino or adaptive copy mode and the -force option is not specified If the source has invalid remote (R2) tracks without using the -force option
Splits Impacting Databases
If the SRDF split will impact the access integrity of a database, additional actions such as freezing the database to user access may be necessary. The freeze action can be used in conjunction with the
2-14
2
TimeFinder or SRDF split operation. The freeze suspends the database updates being written to disk. Using the symioctl command, you can invoke I/O control operations to freeze access to a specified relational database or database object(s).
Note: First, you must set SYMCLI_RDB_CONNECT to your username and password for access to the specified database.
Freeze
To freeze all I/O access to a specified relational database, you use the following command:
symioctl freeze -type DbType Object Object
SQL Server allows some or all databases to be specified. Oracle and Informix allow a user to freeze or thaw an entire DB system. If you have set the connection environment variables, you just need to enter:
symioctl freeze Object Object
For example, to freeze databases HR and Payroll, enter:

symioctl freeze HR Payroll
Thaw
Once the freeze action is completed, the split may proceed. When the split operation completes, a symioctl thaw command must be sent to resume full I/O access to the database instance. For example:
symioctl thaw
Hot Backup Control
For Oracle only, you can perform hot backup control on a list of tablespace objects, which must be performed before and after a freeze/thaw command. The steps required to split a group of BCV devices follows: 1. symioctl begin backup 2. symioctl freeze 3. Split standard and BCV pairs. This may involve several steps depending on your environment. 4. symioctl thaw 5. symioctl end backup
2-15
2
Incremental Establish
Incrementally establishing an SRDF pair (Figure 2-6) accomplishes the same thing as the establish process, with a major time saving exception: the source (R1) device copies to the target (R2) device only the new data that was updated on the source (R1) device while the SRDF pair was split. Additionally, any data that was modified on the target (R2) device will be refreshed from the corresponding tracks on the source (R1) side. When the control operation has successfully completed, the SRDF device pair(s) will be in a Synchronized state, both devices containing identical data. For example, to initiate an incremental establish on all SRDF pairs in the prod device group, enter:
symrdf -g prod establish
To initiate an incremental establish on one SRDF pair with logical device DEV001 in the prod device group, enter:
symrdf -g prod establish DEV001
To initiate an incremental establish for a list of SRDF pairs in the device group prod, enter:
symrdf -g prod establish DEV001 DEV002 DEV003
Any changed tracks on the target (R2) device are also refreshed from the corresponding tracks on the source (R1) device. To invoke this operation, the RDF pair(s) must already be in one of the following RDF states: Split Suspended
Figure 2-6 illustrates the incremental establishing of an SRDF pair. The SRDF pair consists of the source (R1) device which is mirrored to the target (R2) device.
2-16
Figure 2-6
Incremental Establish of an SRDF Pair
When an incremental establish is initiated for each specified RDF pair in a device group: The target (R2) device is write disabled to its local host(s). The changed tracks on the target (R2) device are refreshed from the source (R1) device. The track tables are merged between the source (R1) device and the target (R2) device. Traffic is resumed on the SRDF links.
An incremental establish will be rejected if the source has invalid local (R1) tracks.
2-17
2
Full Restore
The full restore operation differs from the establish operations in that the entire contents of the target (R2) device is copied to the source (R1) device. After the restore is complete, the SRDF pairs will be in the Synchronized state. For example, to initiate a full restore on all SRDF pairs in the prod device group, enter:
symrdf -g prod restore -full
To initiate a full restore on one SRDF pair with logical device DEV001 in the prod device group, enter:
symrdf -g prod restore -full DEV001
To initiate a full restore a list of SRDF pairs in the device group prod, enter:
symrdf -g prod restore -full DEV001 DEV002 DEV003
To invoke this operation, the RDF pair(s) must already be in one of the following RDF states: Split Suspended and write disabled at the source Suspended and not ready at the source
Figure 2-7 illustrates the restoring of an SRDF pair. The SRDF pair consists of the source (R1) device which is mirrored to the target (R2) device.
2-18
Site A HOST
Site B HOST
Write Disabled
Write Disabled
Source (R1) Device SYMMETRIX
RDF Links
Target (R2) Device SYMMETRIX
R2 data copied to R1
Figure 2-7
Restoring an SRDF Device
When a restore is initiated for each specified RDF pair in a device group: The source (R1) device is write disabled to its local host(s). The target (R2) device is write disabled to its local host(s). All tracks on the source (R1) device are marked as invalid. The track tables are merged between the source (R1) device and the target (R2) device. Traffic is resumed on the SRDF links. The source (R1) device is read/write enabled to its local host(s).
The restoration process is complete when the source (R1) and target (R2) device contain identical data. After the restore is complete, the SRDF pair is in the Synchronized state.
This operation will be rejected if the target has invalid local (R2) tracks.
2-19
2
Incremental Restore
The incremental restore process accomplishes the same thing as the restore process with a major time saving exception: the target (R2) device copies to the source (R1) device only the new data that was updated on the target (R2) device while the SRDF pair was split. Any changed tracks on the source (R1) device are refreshed from the corresponding tracks on the target (R2) device. When the incremental restore is complete, the devices are in the Synchronized state. This process is useful if the results from running a new application on the target (R2) device were desirable, and the user wants to move the changed data and the new application to the source (R1) device. For example, to initiate an incremental restore on all SRDF pairs in the prod device group, enter:
symrdf -g prod restore
To initiate an incremental restore on one SRDF pair with logical device DEV001 in the prod device group, enter:
symrdf -g prod restore DEV001
To initiate an incremental restore for a list of SRDF pairs in the device group prod, enter:
symrdf -g prod restore -full DEV001 DEV002 DEV003
To invoke this operation, the RDF pair must already be in one of the following states: Split Suspended and write disabled at the source Suspended and not ready at the source Suspended and the force (-force) option is specified
Figure 2-8 illustrates the incremental restore of an SRDF pair. The SRDF pair consists of the source (R1) device which is mirrored to the target (R2) device.
2-20
Site A HOST
Site B HOST
Write Disabled
Write Disabled
RDF Links
R1 date refreshed from R2
Figure 2-8
Incrementally Restoring an SRDF Device
When an incremental restore is initiated for each specified RDF pair in a device group: The source (R1) device is write disabled to its local host(s). The target (R2) device is write disabled to its local host(s). All tracks on the source (R1) device are marked as invalid. The track tables are merged between the source (R1) device and the target (R2) device. Traffic is resumed on the SRDF links. The source (R1) device is read/write enabled to its local host(s).
2-21
2
Failover
In a period of scheduled downtime for maintenance, or after a serious system problem which has rendered either the host or Symmetrix unit containing the source (R1) devices unreachable, no read/write operations can occur on the source (R1) device. In this situation, the failover operation should be initiated to make the target (R2) devices read/write enabled to their local host(s). Figure 2-9 describes the failover procedure. For example, to perform a failover on all the SRDF pairs in the prod device group, enter:
symrdf -g prod failover
To perform a failover on one SRDF pair with device DEV001 in the prod device group, enter:
symrdf -g prod failover DEV001
To perform a failover on a list of SRDF pairs in the device group prod, enter:
symrdf -g prod failover DEV001 DEV002 DEV003
To invoke a failover, the RDF pair(s) must already be in one of the following states: Synchronized Suspended R1 Updated Partitioned (when you are invoking this operation from the target side)
This operation will be rejected if any of the device pairs are in the following states without specifying the -force option: Split SyncInProg R1 UpdInProg Invalid
2-22
2
Figure 2-9 illustrates the failover of an SRDF pair. The SRDF pair consists of the source (R1) device which is mirrored to the target (R2) device.
Figure 2-9
Failover of an SRDF Device
When a failover is performed for each specified RDF pair in a device group: If the source (R1) device is operational, the SRDF links are suspended. If the source side is operational, the source (R1) device is write disabled to its local host(s). The target (R2) device is read/write enabled to its local host(s).
This operation will be rejected if any of the following occur: If the device pairs are in the Adaptive Copy mode without specifying the -force option If the source has invalid remote (R2) tracks If the target has invalid local (R2) tracks without specifying the -force option
2-23
2
Failback
A failback, or source (R1) device takeover, is performed when you are ready to resume normal SRDF operations by initiating read/write operations on the source (R1) devices, and stopping read/write operations on the target (R2) devices. The target (R2) devices become read-only to their local host(s) while the source (R1) devices are read/write enabled to their local host(s). For example, to initiate a failback on all the SRDF pairs in the prod device group, enter:
symrdf -g prod failback
To initiate a failback on one SRDF pair, DEV001, in the prod device group, enter:
symrdf -g prod failback DEV001
To initiate a failback on a list of SRDF pairs in the device group prod, enter:
symrdf -g prod failback DEV001 DEV002 DEV003
To invoke a failback, the RDF pair(s) must already be in one of the following states: Failed Over Suspended and Write Disabled at the source Suspended and Not Ready at the source R1 Updated R1 UpdInProg
This operation will be rejected if any of the device pairs are in the Partitioned state unless you invoke this operation from the source side and specify the -force option.
Figure 2-10 illustrates the failback of an SRDF pair. The SRDF pair consists of the source (R1) device which is mirrored to the target (R2) device.
2-24
Site A HOST
Site B HOST
Write Disabled
Write Disabled
RDF Links
R2 date changes are copled to R1
Figure 2-10
Failback of an SRDF device
When a failback is initiated for each specified RDF pair in a device group: The target (R2) device is write disabled to its local host(s). If there are invalid remote (R2) tracks on the source side, the target side is operational, and the force flag is specified, tracks that were changed on the source device(s) are marked to refresh from the target side. The track tables are merged between the source (R1) device and the target (R2) device. Traffic is resumed on the SRDF links. The source (R1) device is read/write enabled to its local host(s).
This operation will be rejected if any of the following occur: If the source has invalid local (R1) tracks and the state is Partitioned If the source has invalid remote (R2) tracks and if the target side is not reachable. (If the target is reachable, use the -force option to mark the changed tracks on the source side to refresh from the target.) If the target side is reachable and the target has invalid local (R2) tracks
2-25
2
Update R1 Mirror
While the target (R2) device is still operational (write enabled to its local host(s)), an incremental data copy from the target (R2) device to the source (R1) device can be initiated in order to update the R1 mirror with changed tracks from the target (R2) device. For example, to initiate an update of all the source (R1) devices in the SRDF pairs, for device group prod, enter:
symrdf -g prod update
To initiate an update of the source (R1) device in the SRDF pair with logical device DEV001 in device group prod, enter:
symrdf -g prod update DEV001
To initiate an update on a list of SRDF pairs in the device group prod, enter:
symrdf -g prod update DEV001 DEV002 DEV003
To invoke this operation, the RDF pair must already be in one of the following states: R1 Updated Failed Over Suspended and write disabled at the source Suspended and not ready at the source
Figure 2-11 illustrates the update of an SRDF pair. The SRDF pair consists of the source (R1) device which is mirrored to the target (R2) device.
2-26
2
.
Figure 2-11
Update of SRDF Device Track Tables
An update is initiated for each specified RDF pair in a device group as: SRDF links are suspended when the SRDF links are up. When there are invalid remote (R2) tracks on the source side and the force flag is specified, tracks that were changed on the source device(s) are marked to refresh from the target side. Track tables are merged between the source (R1) device and the target (R2) device. Traffic is resumed on the SRDF links.
When the update has completed successfully, the SRDF pairs will be in the R1 Updated state.
2-27
CAUTION When you perform an update while the RDF pair is Suspended and not ready at the source, the RDF pair enters an Invalid state as the update completes. To resolve this condition, you could then rw_enable r1, then the SRDF pairs would become Synchronized.
This operation will be rejected if the source has any invalid remote (R2) tracks and the -force option is not specified.
Continuous R1 Updates
You can perform continuos updates with one command (update -until #) for situations when you have or want I/O to continue via the remote host and periodically update an inactive R1 device over an extended period of time. The until (-until) option with the update argument identifies a number of Invalid tracks that are allowed to build up from the active R2 local I/O before another update (R2 to R1 copy) is re-triggered. This allows continuous R1 updates to occur every time the invalid track threshold is reached on the active R2 side. Note that these continuous update sequences start with an immediate update once this command is started as follows: 1. Update R1 mirror 2. Changed tracks build up on R2 3. Update R1 mirror is re-triggered as the -until threshold is reached 4. Changed tracks build up on R2 5. Update R1 mirror is re-triggered as the -until threshold is reached 6. Changed tracks build up on R2 . . . Sequences stop with a new command such as a restore. For example, to update R1 mirror after every 1000 track changes on R2, enter:
symrdf -g prod update -until 1000
2-28
Singular SRDF Control Operations

The singular SRDF control operations are invoked using symrdf. The singular SRDF control operations make up the composite SRDF control operations. It is recommended that you use the composite SRDF control operations listed in Table 2-1 before attempting to use the singular SRDF control operations.
Note: The singular SRDF control operations listed in Table 2-2 should be used sparingly and only when all other composite control options have been exhausted.
Table 2-2
Singular SRDF Control Operations symrdf Options suspend resume rw_enable r1 rw_enable r2 write_disable r1 write_disable r2 refresh r1 refresh r2 invalidate r1 invalidate r2 ready r1 Results Suspends I/O traffic on the RDF links for the remotely mirrored RDF pair(s) in the group. Resumes I/O traffic on the RDF links for the remotely mirrored RDF pair(s) in the group. Write enables the source (R1) device to its local host. Write enables the target (R2) device to its local host. Write disables the source (R1) device to its local host. Write disables the target (R2) device to its local host. Marks any changed tracks on the source (R1) side to be refreshed from the R2 side. Marks any changed tracks on the target (R2) side to be refreshed from the R1 side. Invalidates all tracks on the source (R1) side so that they can be copied over from the target (R2) side. Invalidates all tracks on the target (R2) side so that they can be copied over from the source (R1) side. Sets the source (R1) device to be RDF ready to its local host.
Control Operation Suspend RDF links Resume RDF links Write enable source device Write enable target device Write disable source device Write disable target device Refresh R1 mirror Refresh R2 mirror Invalidate R1 mirror Invalidate R2 mirror Make ready the R1 mirror
2-29
2
Table 2-2
Singular SRDF Control Operations (continued) symrdf Options ready r2 not_ready r1 not_ready r2 merge Results Sets the target (R2) device to be RDF ready to its local host. Sets the source (R1) device to be RDF not ready to its local host. Sets the target (R2) device to be RDF not ready to its local host. Merges the track tables between the source (R1) and the target (R2) side.
Control Operation Make ready the R2 mirror Make the R1 mirror not ready Make the R2 mirror not ready Merge the track tables of the R1 and R2 devices
The singular SRDF control operations outlined in Table 2-2 are described in the upcoming pages of this section.
Suspend
The suspend option suspends I/O traffic on the RDF links for all remotely mirrored RDF pairs in the group. For example, to suspend the RDF links between all the SRDF pairs in device group prod, enter:
symrdf -g prod suspend
To suspend the RDF links between one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod suspend DEV007
To suspend the RDF links (between the pairs) on a list of SRDF pairs in device group prod, enter:
symrdf -g prod suspend DEV002 DEV003 DEV007
To invoke a suspend, the RDF pair(s) must already be in one of the following states: Synchronized R1 Updated
When the suspend has completed successfully, the devices will be suspended on the SRDF links and their link status set to Not Ready (NR).
2-30
2
This operation will be rejected if any of the following occur: If the source has invalid local (R1) tracks If any of the device pairs are in the following state and the -force option is not specified: SyncInProg state UpdInProg state Invalid state Split state and the link status is write disabled Suspended state and the link status is write disabled When the device pairs are in the device domino mode When the source has invalid remote (R2) tracks When the target has invalid local (R2) tracks
Resume
The resume option resumes I/O traffic on the RDF links for all remotely mirrored RDF pairs in the group. For example, to resume the RDF links between all the SRDF pairs in device group prod, enter:
symrdf -g prod resume
To resume the RDF links between one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod resume DEV007 This operation will be rejected if a merge track table is needed but has not been executed.
To resume the RDF links (between the pairs) on a list of SRDF pairs in device group prod, enter:
symrdf -g prod resume DEV002 DEV003 DEV007
To invoke this operation, the RDF pair(s) must already be in the Suspended state.
2-31
2
Read/Write Enable R1 Mirror
The read/write enable R1 mirror option write enables the source (R1) devices to their local hosts. For example, to read/write enable all the source (R1) mirrors in all the SRDF pairs in device group prod, enter:
symrdf -g prod rw_enable r1
To read/write enable the source (R1) mirrors in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod rw_enable r1 DEV007
To invoke this operation, the RDF device must be in either the Write Disabled or the Not Ready state at the source, and the pair(s) must already be in one of the following states: Synchronized SyncInProg Suspended Partitioned while you are invoking this operation from the source side Invalid
This operation will be rejected if any of the device pairs are in the FailedOver state without specifying the -force option.
Read/Write Enable R2 Mirror
The read/write enable R2 mirror option write enables the target (R2) devices to their local hosts. For example, to read/write enable all the target (R2) mirrors in the SRDF pairs in device group prod, enter:
symrdf -g prod rw_enable r2
To read/write enable the target (R2) mirror in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod rw_enable r2 DEV007
To read/write enable the target (R2) mirror of a list of SRDF pairs in device group prod, enter:
symrdf -g prod rw_enable r2 DEV002 DEV003 DEV007
2-32
2
To invoke this operation, the RDF pair(s) must already be in one of the following states: Suspended and Write Disabled at the target on the SA or RA Suspended and Not Ready at the target on the SA or RA Partitioned while you are invoking this operation from the target side and the devices are Write Disabled or Not Ready at the target on the SA or RA
Write Disable R1 Mirror
The write disable R1 mirror option write disables the source (R1) devices to their local hosts. For example, to write disable all the source (R1) mirrors in the SRDF pairs in device group prod, enter:
symrdf -g prod write_disable r1
To write disable the source (R1) mirror in the SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod write_disable r1 DEV007
To write disable the source (R1) mirror in a list of SRDF pairs, (DEV002, DEV003, DEV007) in device group prod, enter:
symrdf -g prod write_disable r1 DEV002 DEV003 DEV007
This operation can be invoked from the source side if the RDF pair(s) are already in the Partitioned state and the device is Ready on the SA at the source.
This operation will be rejected if the device pair(s) are in one the following states, and Ready on the SA at the source without specifying the force flag: Synchronized SyncInProg Suspended Split Invalid
2-33
2
Write Disable R2 Mirror
The write disable R2 mirror option write disables the target (R2) devices to their local hosts. For example, to write disable all the target (R2) mirrors in the SRDF pairs in device group prod, enter:
symrdf -g prod write_disable r2
To write disable the target (R2) mirror in the SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod write_disable r2 DEV007
To write disable the target (R2) mirror in a list of SRDF pairs in device group prod, enter:
symrdf -g prod write_disable r2 DEV002 DEV003 DEV007
This operation can be invoked from the target side if the device pair(s) are already in the Partitioned state and are Ready on the RA at the target side.
This operation will be rejected if the device pair(s) are in one of the following states without specifying the -force option: Split Failed over R1 Updated R1 UpdInProg Invalid
Refresh R1 Mirror
The refresh R1 mirror option marks any changed tracks on the source (R1) side to refresh from the R2 side. For example, to refresh all the source (R1) devices in all the SRDF pairs in the device group prod, enter:
symrdf -g prod refresh r1
To refresh the source (R1) device in the SRDF pair, DEV007, in the device group prod, enter:
symrdf -g prod refresh r1 DEV007
2-34
2
To refresh the source (R1) device in the list of SRDF pairs in the device group prod, enter:
symrdf -g prod refresh r1 DEV002 DEV003 DEV007
To invoke this operation, the RDF pair(s) must already be in one of the following states: Suspended and Write Disabled at the source Suspended and Not Ready at the source Failed Over with the force option specified
Refresh R2 Mirror
The refresh R2 mirror option marks any changed tracks on the target (R2) side to refresh from the R1 side. For example, to refresh the target (R2) devices in all the SRDF pairs in device group prod, enter:
symrdf -g prod refresh r2
To refresh the target (R2) device in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod refresh r2 DEV007
To refresh the target (R2) device for a list of SRDF pairs in device group prod, enter:
symrdf -g prod refresh r2 DEV002 DEV003 DEV007
To invoke this operation, the RDF pair(s) at the source must already be Suspended, and either: Write Disabled or Not Ready at the source or Ready at the source with the force option specified
This operation will be rejected if the source has invalid local (R1) tracks.
2-35
2
Invalidate R1 Mirror
The invalidate R1 mirror option invalidates all tracks on the source (R1) side so that they can be copied over from the target (R2) side. For example, to invalidate the source (R1) devices in all the SRDF pairs in device group prod, enter:
symrdf -g prod invalidate r1
To invalidate the source (R1) device in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod invalidate r1 DEV007
To invalidate the source (R1) device for a list of SRDF pairs in device group prod, enter:
symrdf -g prod invalidate r1 DEV002 DEV003 DEV007
To invoke this operation, the RDF pair(s) at the source must already be Suspended and Write Disabled or Not Ready.
This operation will be rejected if the target has invalid local (R2) tracks
Invalidate R2 Mirror
The invalidate R2 mirror option invalidates all tracks on the target (R2) side so that they can be copied over from the source (R1) side. For example, to invalidate the target (R2) devices in all the SRDF pairs in device group prod, enter:
symrdf -g prod invalidate r2
To invalidate the target (R2) device in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod invalidate r2 DEV007
To invoke this operation, the RDF pair(s) at the source must already be Suspended and Write Disabled or Not Ready.
This operation will be rejected if the source has invalid local (R1) tracks
2-36
2
Ready R1 Mirror
The make R1 mirror ready option sets the source (R1) devices to be RDF ready to their local hosts. This operation may only be needed after all SRDF links have been lost when running in the RDF domino mode. For example, to make the source (R1) device Ready in all the SRDF pairs in device group prod, enter:
symrdf -g prod ready r1
To make the source (R1) device Ready in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod ready r1 DEV007
To make the source (R1) device Ready in a list of SRDF pairs in device group prod, enter:
symrdf -g prod ready r1 DEV002 DEV003 DEV007
This action can be invoked in all RDF states, except when you are invoking the action from the target side and the device pair(s) are in the Partitioned state.
Ready R2 Mirror
The make R2 mirror ready option Sets the target (R2) devices to be RDF ready to their local hosts. For example, to make the target (R2) devices Ready in all the SRDF pairs in device group prod, enter:
To make the target (R2) device Ready in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod ready r2 DEV007
This action can be invoked in all RDF states, except when you are invoking the action from the source side and the device pair(s) are in the Partitioned state.
2-37
2
Not Ready R1 Mirror
The make R1 mirror not ready option sets the source (R1) devices to be RDF not ready to their local hosts. For example, to make the source (R1) devices Not Ready in all the SRDF pairs in device group prod, enter:
symrdf -g prod not_ready r1
To make the source (R1) device Not Ready in one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod not_ready r1 DEV007
To make the source (R1) device Not Ready in a list of SRDF pairs, DEV007, in device group prod, enter:
symrdf -g prod not_ready r1 DEV002 DEV003 DEV007
To invoke this operation, the RDF pair(s) must be write disabled at the source and already be in one of the following states: FailedOver R1 Updated R1 UpdInProg Suspended Partitioned and you are invoking this action from the source side
Not Ready R2 Mirror
The make R2 mirror not ready option sets the target (R2) devices to be RDF not ready to their local hosts. For example, to make the target (R2) devices Not Ready in all the SRDF pairs in device group prod, enter:
symrdf -g prod not_ready r2
To make the target (R2) device in one SRDF pair Not Ready, DEV007, in device group prod, enter:
symrdf -g prod not_ready r2 DEV007
2-38
2
To invoke this operation, the RDF pair(s) must be write disabled at the target and already in one of the following states: Synchronized SyncInProg Suspended Partitioned and you are invoking the action from the target side
Merge Track Tables
The merge track tables option merges the track tables between the source (R1) and the target (R2) side. For example, to merge the track tables of all the SRDF pairs in device group prod, enter:
symrdf -g prod merge
To merge the track table of one SRDF pair, DEV007, in device group prod, enter:
symrdf -g prod merge DEV007
To merge the track table of a list SRDF pairs in device group prod, enter:
symrdf -g prod merge DEV002 DEV003 DEV007
To invoke this operation, the RDF pair(s) must already be in one of the following states: Suspended and the force option is specified, or the device pair(s) are Write Disabled or Not Ready at the source side Failed Over and the force option is specified
This operation is rejected if any of the following occur: The source has invalid local (R1) tracks and the target has invalid local (R2) tracks. The source has invalid remote (R2) tracks and the target has invalid remote (R1) tracks. The source has invalid local (R1) tracks and the device is read/write enabled at the source The target has invalid remote (R1) tracks and the device is read/write enabled at the source
2-39
SRDF Pair States

SRDF devices that are operational are always in some SRDF Pair State. The SRDF Pair State encompasses the SRDF state on the source (R1) side, the RDF links status, and the RDF state on the target (R2) side. When you invoke a control operation on an SRDF pair, the SRDF Pair state may be changed. This depends on whether the RDF state of the source (R1) side, status of the RDF links, or the RDF state of the target (R2) side has changed. The following table summarizes the RDF state of the source (R1) device, the RDF links status, and the RDF state of the target (R2) device. The following legend provides details about elements in Table 2-3 Table Legend
Not Ready: Ready: WD: Disabled for both reads and writes Enabled for both reads and writes Write disabled
Table 2-3
SRDF States for Each RDF Pair R1 or R2 Invalid Tracks >0 0 0a > 0a
SRDF Pair State SyncInProg Synchronized Split Failed Over R1 Updated R1 UpdInProg Suspended PartitionedS
Source (R1) RDF Status Ready Ready Ready Not Ready or WD Not Ready or WD Not Ready or WD Any statusb Any status
RDF Links Status Ready Ready Not Ready or WD Not Ready Ready or WD Ready or WD Not Ready or WD Not Ready
Target (R2) RDF Status Not Ready or WD Not Ready or WD Ready Ready Ready Ready Not Ready or Write Disabled Not Available
2-40
2
Table 2-3
SRDF States for Each RDF Pair (continued) R1 or R2 Invalid Tracks
SRDF Pair State PartitionedT Mixed Invalidd
Source (R1) RDF Status Not Available *c Any statuse
RDF Links Status Not Ready *c Any status
Target (R2) RDF Status Any status *c Any status
a. Refers to invalid local (R1) tracks on source b. Any status value is possible (Ready, Not Ready, Write Disabled, or Not Available c. Mixed state is seen only with symdg show to indicate that there are different device states in the group d. When no other SRDF states apply, the state defaults to Invalid e. The combination of source RDF, RDF links, and target RDF statuses do not match any other RDF state, therefore the RDF state is considered Invalid S Viewed from the host locally connected to the source (R1) device T Viewed from the host locally connected to the target (R2) device
SRDF Pair States
2-41
RDF Operations and Applicable States

When RDF control operations are initiated, the RDF state of the device pair(s) is checked. If the device pair is not in a legal RDF state to initiate the control operation, the control will not be initiated unless the -force option is used. The -force option is used when the RDF pairs are not in a legal RDF state, in order to force a pair to a specified RDF state. For example, to initiate a failover on all the SRDF pairs, currently in the Split state, in the prod group, enter:
symrdf -g prod -force failover
To initiate a failover on one SRDF pair, DEV001, currently in the SyncInProg state, in the prod group, enter:
symrdf -g prod -force failover DEV001
Table 2-4 describes which RDF control operations can be invoked for a given RDF state, noted by the check (). The -force option must be used (where noted in Table 2-4 as F) to force a pair to a specified RDF state.
Table 2-4
RDF Control Operations and Applicable States S Y N C H R O N I Z E D R 1 R 1 U p d a t e d U p d I n P r o g
Control Operation establish -full split establish
S Y N C I N P R O G
S P L I T
S U S P E N D E D
F A I L E D O V E R
P A R T I T I O N E D
I N V A L I D
2-42
2
Table 2-4
RDF Control Operations and Applicable States (continued) S Y N C H R O N I Z E D R 1 R 1 U p d a t e d U p d I n P r o g
Control Operation restore restore -full suspend
S Y N C I N P R O G
S P L I T
S U S P E N D E D
F A I L E D O V E R
I N V A L I D
e a F F
w w
F F
resume failover failback
F F a a X a a F a Fa
RDF Operations and Applicable States
2-43
g f g f g
Ff
F F
update ready r1 ready r2 not_ready r1 not_ready r2 invalidate r1 refresh r1 invalidate r2 refresh r2
2
Table 2-4
RDF Control Operations and Applicable States (continued) S Y N C H R O N I Z E D R 1 R 1 U p d a t e d U p d I n P r o g
Control Operation merge rw_enable r1 write_disable r1
S Y N C I N P R O G
S P L I T
S U S P E N D E D e
F A I L E D O V E R
I N V A L I D
F a F
b
a
Fa
a
Fb
a F fa
Fb
Fb
fb
rw_enable r2
c F X
b. SA Ready on the source side
gc
write_disable r2
gd
F F
Fd
swap
a. SA Write Disabled or Not Ready on the source side c. SA or RA Write Disabled or Not Ready on the target side d. RA Ready on the target side e. Use Force or <SA Write Disabled or Not Ready on the source side> f. Host application run while connected to the source side g. Host application run while connected to the target side F. Force option can be used W. Write disabled on the RDF link X. Write disabled on the R1 side
2-44
Setting SRDF Modes

You can use the SYMCLI symrdf command to modify SRDF modes on remotely mirrored standard devices in a device group. Using the symrdf command, you can modify the modes which are described below. Synchronous In the Synchronous mode, the Symmetrix unit responds to the host with access to the source (R1) device on a write operation only after the Symmetrix unit containing the target (R2) device acknowledges that it has received and checked the data. For example, to set the remotely mirrored pair in the prod group to the Synchronous mode, enter:
symrdf -g prod set mode sync
This state ensures that the source (R1) and target (R2) devices remain up-to-date. Semi Synchronous In the Semi Synchronous mode, the Symmetrix unit containing the source (R1) device informs the host of successful completion of the write operation when it receives the data. The SRDF director (RA) transfers each write to the target (R2) device as the SRDF links become available. The Symmetrix unit containing the target (R2) device checks and acknowledges receipt of each write. If a new write is started for a source (R1) device before the previous write has completed to the target (R2) device, the Symmetrix unit containing the source (R1) device temporarily disconnects from the I/O bus until the previous write operation is completed and acknowledged from the remote Symmetrix unit and then reconnects to the I/O bus and continues processing. For example, to set all the remotely mirrored pairs in the prod device group to the Semi Synchronous mode, enter:
symrdf -g prod set mode semi
Setting SRDF Modes
2-45
2
Domino Effect On The device domino effect mode ensures that the data on the source (R1) and target (R2) devices are always in synch. The Symmetrix will force the source (R1) device to not ready and respond intervention required/unit not ready to the host whenever it detects one side in a remotely mirrored pair is unavailable, or all link failures have occurred and the host tries to access the device. For example, to turn the device domino effect on for the prod device group, enter:
symrdf -g prod set domino on
After the problem has been corrected, the not ready device must be made ready again to the host using the symrdf ready command. For example, to make all the source (R1) side devices Ready in the prod device group, enter:
If the failed device or links are still not available when the SRDF device is made Ready, the device becomes Not Ready again when the device is accessed. Some important issues to consider: When the device domino effect is ON, you will not be able to use the Split or Suspend control operation because it would cause the devices to become Not Ready. All RDF links will still fail regardless if link domino is enabled when all RDF R1 devices become Not Ready.
Domino Effect Off
Under normal operating conditions (domino effect not enabled), a remotely mirrored device will continue processing I/Os with its host even when an SRDF device or link failure occurs. New data written to the source (R1) or target (R2) device while its pair is unavailable or link paths are out of service are marked for later transfer. When link paths are re-established or the device becomes available, resynchronization begins between the source (R1) and target (R2) devices. For example, to turn the domino effect off for the prod device group, enter:
symrdf -g prod set domino off
2-46
2
Adaptive Copy - Write Pending When you set the SRDF mode to Adaptive Copy, Write Pending mode, Symmetrix acknowledges all writes to the source (R1) device as if it was a local device. The new data accumulates in cache until it is successfully written to the source (R1) device and the Remote Director has transferred the write to the target (R2) device. For example, to turn on the Adaptive Copy Write Pending for the prod device group, enter:
symrdf -g prod set mode acp_wp
For example, to turn off Adaptive Copy, Write Pending mode, for the prod device group, enter:
symrdf -g prod set mode acp_off
This SRDF mode is designed to have little or no impact on performance between the host and the Symmetrix unit containing the source (R1) device. Adaptive Copy - Disk The Adaptive Copy Disk mode is designed for situations requiring the transfer of large amounts of data without loss of performance. Because Symmetrix cannot fully guard against data loss should a failure occur, EMC recommends using this mode temporarily to transfer the bulk of your data to target (R2) devices and then switch to a full SRDF mode (synchronous or semi-synchronous) or Adaptive Copy-Write Pending mode (if you can tolerate some lack of synchronization between the remotely mirrored pairs) to ensure full data protection. When you set the SRDF mode to Adaptive Copy Disk, Symmetrix acknowledges all writes to source (R1) devices as if they were local devices. New data accumulates on the source (R1) device and is marked by the source (R1) side as invalid tracks until it is subsequently transferred to the target (R2) device. The Remote Director transfers each write to the target (R2) device whenever link paths become available. For example, to turn on the Adaptive Copy Disk mode for the prod group, enter:
symrdf -g prod set mode acp_disk
For example, to turn the Adaptive Copy Disk mode off for the prod group, enter:
symrdf -g prod set mode acp_off
Setting SRDF Modes
2-47
2
This attribute also has a user-configurable skew (maximum number of invalid tracks threshold), that when exceeded, causes the remotely mirrored device to operate in the pre-determined SRDF state (synchronous or semi-synchronous) when this mode is in effect. As soon as the number of invalid tracks drops for a device below this value, the remotely mirrored pair reverts back to the Adaptive Copy Write Pending mode. Adaptive Copy Change Skew This attribute is used to modify the Adaptive Copy skew threshold. When the skew threshold is exceeded, the remotely mirrored pair operates in the pre-determined SRDF state (synchronous or semi-synchronous). As soon as the number of invalid tracks drop below this value, the remotely mirrored pair reverts back to the Adaptive Copy Write Pending mode. The skew value is configured at the device level and may be set to a value between 0 and 65,534 tracks. For devices larger than a 2 GB capacity drive, a value of 65,535 can be specified to target all the tracks of any given drive. For example, to change the Adaptive Copy skew value to all tracks of device BCV023 of group prod, enter:
symrdf -g prod set acp_skew 65535 BCV023
For example, to change the Adaptive Copy skew value to 30,000 tracks for device BCV023 of group prod, enter:
symrdf -g prod set acp_skew 30000 BCV023
2-48
Swapping R1 Devices with R2

If you have a Configuration Mgr license, you can swap the RDF personality of the RDF device designations of a specified device group. Soure R1 device(s) become target R2 device(s) and target R2 device(s) become source R1 device(s). Use the following form to do an R1/R2 swap:
symrdf -g DgName [-force] [-bcv|-all] [-v|-noecho] [-bypass] [-i Interval] [-c Count] [-noprompt] swap -refresh R1|R2
where: DgName -force The specified device group for this action. When you need to apply force to the operation even though one or more devices in the group may not be in the normal, expected state or operation. You use -bcv when you need to target just the BCV associated devices for the swap action in the RDF. Use -all when you are targeting both BCV and Standard devices. Use nothing when you are targeting just the standard devices.
-bcv|-all
-v|-noecho -v for verbose mode, or -noecho if you do not want to echo stdout during the RDF action. -bypass To bypass any existing Symmetrix exclusive locks during the SRDF operation. Use the bypass option ONLY if you are SURE that no other SRDF operation is in progress in either the local and/or remote Symmetrix units. -c To specify the number (count) of times to display or to acquire an exclusive lock on the Symmetrix host database, the local Symmetrix, and the remote Symmetrix units. If this option is not specified and an interval (-i) is specified, program will loop continuously to display, or until RDF control or set operation starts.
2-49
2
-i To repeat interval in seconds to display or to acquire an exclusive lock on the Symmetrix host database, the local Symmetrix, and the remote Symmetrix units. The default interval is 10 seconds. The minimum interval is 5 seconds. To disable command prompt for user confirmation. Marks the source R1 device(s) or the target R2 device(s) to refresh from the remote mirror.
-noprompt -refresh
R1/R2 Swap Example
To swap the R1 designation of the BCV associated devices with the R2 designation of the BCV associated devices of device group ProdGrpB, and to also refresh the R1 devices, enter:
symrdf -g ProdGrpB -bcv swap -refresh R1
Refresh Data Concerns
The refresh action identifies which device does not hold a valid copy of the data before the swap operation begins. If you determine that the R1 holds the valid copy, the action of refresh R2 will obtain a count of the tracks that are different on the R2 and will copy (refresh) these tracks from the R1 to the R2 device. The result will be the reverse if you choose to refresh R1 as the action. Swapping the R1/R2 designation of the RDF devices can impact the preservation of your stored data as shown in Table 2-5.
RDF Device Data Preservation for a Swap Data Integrity Preserved Status Not preserved
Data Preservation Concerns

Table 2-5
RDF Side with Data RDF1
Swap Operation, Refresh Target Selection -refresh R1 The R2 device holds the valid copy and the R1 devices invalid tracks will be updated using the R2 data. -refresh R2 The R1 device holds the valid copy and the R2 devices invalid tracks will be updated using the R1 data. -refresh R1 The R2 device holds the valid copy and the R1 devices invalid tracks will be updated using the R2 data. -refresh R2 The R1 device holds the valid copy and the R2 devices invalid tracks will be updated using the R1 data.
RDF1
Preserved
RDF2
Preserved
RDF2
Not preserved
2-50
2
Legal States for Swap Operation The current states of the various devices involved in the SRDF swap must be considered before executing a swap action. Table 2-6 lists which states are legal for this operation.
Table 2-6
RDF Device States for Swap Operation Target R2 Invalids Refresh R1|R2 NA NA
RDF State Suspended with R1 Write Disabled R1 Updated Failed Over
Source R2 Invalids Refresh R1|R2 refresh=R1 refresh=R1
State after Swap Suspended Failed Over Failed Over
Impact on I/O
The following are restrictions/conditions in lieu of impact on I/O activity: When swapping source and target attributes no I/O allowed to the R1 device, but I/O to R2 is OK.
Disable SYMAPI Environment Variable
Environment variable SYMAPI_CTRL_OF_NONVISIBLE_DEVS in the options file must be disabled if the devices are not mapped to the user host. In the options file, set:
SYMAPI_CTRL_OF_NONVISIBLE_DEVS = disable
2-51
symrdf -g Command Line Options

With the symrdf -g command, you can perform RDF control operations on RDF device(s) in a device group. The control operations (arguments) have options which allow flexibility in controlling the RDF pairs. Table 2-7 lists the symrdf control operations type arguments and options available when operating on RDF device(s) of a specified device group.
Table 2-7
symrdf -g Control Arguments and Applicable Options -by pass X X X X X X X X X X X X X X X X -no echo X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X -no prompt X X X X X X X X X X X X X X X X
Argument establish -full establish split restore -full restore failover failback suspend resume merge update ready r1 | r2 not_ready r1 | r2 rw_enable r1 | r2 write_disable r1 | r2 refresh r1 | r2
-force X X X X X X X X X X X X X X X X
-bcv X X X X X X X X X X X X X X X X
-rbcv X X X X X X X X X X X X X X X X
-brbcv -all X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
-i/-c X X X X X X X X X X X X X X X X
-v
2-52
2
Table 2-7
symrdf -g Control Arguments and Applicable Options -by pass X X X X -no echo X X X X X -no prompt X X X
Argument invalidate r1 | r2 set mode|domino|skew swapa
-force X
-bcv X X X
-rbcv X X
-brbcv -all X X X X X
-i/-c X X X
-v
a. Another possible option is -refresh (see Swapping R1 Devices with R2).
Table 2-8 lists the symrdf view action type arguments and options available when viewing RDF device(s) of a specified device group.
Table 2-8
symrdf -g View Arguments and Applicable Options -con sist.. X
Argument lista ping query verifyb
-sid X X
-i/-c X X X X
-offline X
-bcv
-rbcv
-brbcv -all
-rdf
-resv X
-updated -valid
-v X
X X X X X X X X X X X X X
a. Other possible options for list are -nobcv, -RDFG, -R1 and -R2 (see Appendix A). b. Other possible options for verify are -synchronized, -suspended, -enabled, -susp_offline, -split, -failedover, -syncinprog, -updateinprog, and -partitioned (see Appendix A).
The following briefly describes the SRDF control options.
All Option
The all (-all) option targets the SRDF action at all devices in the device group, which includes: standard RDF devices, and any BCV RDF devices that are locally associated with the device group. The BCV (-bcv) option allows the SRDF control operation to target the specified BCV device(s) that are associated with the device group and are configured as RDF BCV devices. By default, only the SRDF standard devices are affected by the SRDF control operations. The no BCV (-nobcv) option allows the SRDF control operation to target specified devices not including BCV devices.
BCV Options
2-53
2
The BCV remote BCV (-brbcv) option allows you to target the SRDF action at the specified remotely-associated RDF (Hop 2) BCV device(s) which can be paired with the remote mirrors of the local BCV devices. The remote BCV (-rbcv) option allows you to target the SRDF action at the specified remotely-associated RDF (Hop 2) BCV device(s) which can be paired with the remote mirrors of the local standard devices.
Bypass Option
The bypass (-bypass) option causes the SRDF control operation to bypass existing Symmetrix exclusive locks.
CAUTION Note: Use the -bypass option ONLY if you are SURE that no other SRDF operation is in progress in either the local and/or remote Symmetrix units.
Count and Interval Options
The interval (-i) option executes a command in repeat intervals to display or to attempt to acquire an exclusive lock on the Symmetrix host database, the local Symmetrix, and the remote Symmetrix units. The default interval is 10 seconds. The minimum interval is 5 seconds. The count (-c) option counts the number of times to display or to attempt acquiring exclusive locks on the Symmetrix host database, the local Symmetrix, and the remote Symmetrix units. If the (-c) option is not specified and an interval (-i) is specified, the program loops continuously to produce infinite re-displays, or until the RDF control or set operation starts. To query device group prod every 10 seconds for 1 minute, enter:
symrdf -g prod -i 10 -c 6 query
Force Option
The force (-force) option allows you to perform control operations on SRDF devices when SRDF device(s) are not in the expected state for the control operation.
2-54
2
Using the -force option, the control operation will be attempted, regardless of the state of the SRDF devices, if it is legal to do so according to the rules in Table 2-4. For example, if one SRDF device in an SRDF pair is in the Suspended state, and the other SRDF device is in the Synchronized state, to split the SRDF pair, DEV007, in the device group prod, enter:
symrdf -g prod -force split DEV007
Help Option
The help (-h) option allows you receive brief online help for the SYMCLI command. The no echo (-noecho) option suppresses the display of information which results from an RDF control operation. The no prompt (-noprompt) option suppresses the message asking you to confirm an RDF control operation. The offline (-offline) option prevents accessing the Symmetrix to update the database. The symrdf command uses information previously gathered from the Symmetrix and held in the Symmetrix host database as opposed to interrogating the Symmetrix directly. The offline option can alternatively be set by assigning the environment variable SYMCLI_OFFLINE to 1. The R1 or R2 (-R1 | -R2) options allows you to list only the devices that are RDF1 types (-R1), or RDF2 types (-R2). The SCSI reservations (-resv) option allows you to list RDF devices that have SCSI reservations. For example, to list all the RDF devices in Symmetrix unit 333 that have SCSI reservations, enter:
symrdf -sid 333 -resv list
No Echo Option
No Prompt Option
Offline Option
R1 or R2 Option
SCSI Reservations Option
Consistency State Option
The consistency state (-consistency) option allows you to list the RDF consistency state when you are listing RDF devices.
2-55
2
For example, to show the consistency state in the list of all the RDF devices in Symmetrix unit 333, enter:
symrdf -sid 333 -consistency list
Symmetrix ID Option
The Symmetrix ID (-sid) option allows you to specify the Symmetrix unit, which the command references. The enabled state option (-enabled) verifies whether the RDF device pair(s) are in the Enabled Consistency state. The failedover state option (-failedover) verifies whether the RDF device pair(s) are in the Failedover state. The partitioned state option (-partitioned) verifies whether the RDF device pair(s) are in the Partitioned state. The split state option (-split) verifies whether the RDF device pair(s) are in the Split state. The suspended state option (-suspended) verifies whether the RDF device pair(s) are in the Suspended state. The suspended offline state option (-susp_offline) verifies whether the RDF device pair(s) are in the Suspended state and the SRDF link is offline. The synchronized state option (-synched) verifies whether the RDF device pair(s) are in the Synchronized state. The updated state (-updated) option verifies whether the RDF pair(s) are in the Updated state. For example, to verify whether the RDF device pair, DEV007, in the device group prod is in the Updated state, enter:
symrdf -g prod -updated verify DEV007
Enabled State Option Failed Over State Option Partitioned State Option Split State Option
Suspended State Option Suspended Offline State Option
Synchronized State Option Updated State Option
2-56
2
Update In Progress State Option
The update in progress state option (-updateinprog) verifies whether the RDF device pair(s) are in the UpdateInProg state.
Valid State Option
The valid state (-valid) option verifies whether the RDF pair(s) are in a valid RDF pair state (all RDF pair states except Invalid). For example, to verify whether all the RDF devices in the device group prod are in one of the valid RDF pair states, enter:
symrdf -g prod -valid verify
Until Option
The until (-until) option with the update argument identifies a number of Invalid tracks that are allowed to build up from the active R2 local I/O before another update (R2 to R1 copy) is re-triggered. This allows continuous R1 updates to occur every time the invalid track threshold is reached on the active R2 side. Note that these continuous update sequences start with an immediate update once this command is started. For example, to update R1 mirror after every 500 track changes on R2, enter:
symrdf -g prod -until 500 -nop update
Verbose Option
The verbose (-v) option displays status and progress information as it executes the desired operation.
2-57
RA Group Topologies in an SRDF

There are two types of topologies for RA groups and connection between Symmetrixes of an SRDF: RA Groups in a Point-to-Point SRDF Link RA Groups in a Switched RDF Link
RA Groups in a Point-to-Point SRDF Link
As shown in Figure 2-12, RA adapters interface to an SRDF link between Symmetrixes at different sites. RA groups represent an established connection and an RDF pair associated link between certain R1 and R2 devices. R1 devices are RDF1 types and R2 are RDF2 types.
Site A Symmetrix 1
DEV001 R1
Point-to-Point SRDF Links RA

Group 1
Site B Symmetrix 2 RA
RDF Pair
Group 1
R2
DEV002
RA
RDF Pair
Group 1
RA
Group 1 R2
R1
Figure 2-12
RA Group Topology in a Point-to-Point SRDF Solution
2-58
2
RA Groups in a Switched SRDF Link
As shown in Figure 2-12, RF adapters interface to an SRDF switched network (link) between Symmetrixes at different sites. RA groups represent an established connection and an SRDF pair associated switched link between certain R1 and R2 devices. R1 devices are RDF1 types and R2 are RDF2 types. In the figure, Groups 3 and 4, R2 device at Site B can be paired with Group 1 or 2, R1 device at Site A or Site B.
Site A Symmetrix 1
DEV001 R1
Site B Symmetrix 3 RF RF
R2
Local RA Group 1 DEV002
Remote RA Group 3
RF
RF
R2
R1
Site A Symmetrix 2
DEV001 R1 Local RA Group 2 DEV002 R1
Switched RDF
RF
R2
RF
Remote RA Group 4
RF
R2
RF
Local Group 1 or 2 can be connected to Remote Group 3 and 4
Figure 2-13
RA Group Topology in a Switched RDF Solution
To view what local and remote Symmetrixes, their RF directors and RA groups are connected via the open RDF switch fabric, enter:
symcfg list -RA ALL -switched
RA Group Topologies in an SRDF
2-59
Various Remote Configurations

Various compounded remote configurations can be managed by your host using both the TimeFinder and SRDF components of SYMCLI. As shown in Figure 2-14, you can have multiple sites (for example, remote Sites B and C) on SRDF links to remotely mirror a local Symmetrix unit at Site A. Remote Site B, functioning as a remote mirror to the standard devices at Site A, is most typical. You then can have a third site on an SRDF link (remote Site C) to remotely mirror just the BCV devices in the Symmetrix at Site A. Multi-Hop SRDF Sites You can also multi-hop to a second level SRDF where Remote Site D functions as a remote mirror to the standard devices of Site A and Remote Site E remotely mirroring Site As BCV. Command symrdf manages the RDF pairs within the SRDF link while symmir manages the BCV pairs within any one site. For example, to split the BCV pair within site A, enter:
symmir -g prod split
To split RDF pairs at Site B from host-connected Site A, enter:

To split the BCV pairs within Site B, enter:

symmir -g prod -rdf split
To split BCV RDF pairs at Site C from host-connected Site A, enter:

symrdf -g prod -bcv split
To split the BCV pairs within Site C, enter:

symmir -g prod -rdf -bcv split
To split BCV RDF pairs at Site D from host standard-associated Site B, enter:
symrdf -g prod -rbcv split
To split the BCV pairs within Site D, enter:

symmir -f dfile -sid 0014 split
2-60
2
To split BCV RDF pairs at Site E from host BCV-associated Site C, enter:
symrdf -g prod -brbcv split
To split the BCV pairs within Site E (hop 2), enter:

symmir -f dfile -sid 0015 split
Other operations for these remote sites such as establish and restore apply and execute in the same manner. For more detail information about symmir, refer to the SYMCLI TimeFinder Component manual.
2-61
2
SITE A
HOST
Standard DEV001 BCV001
Device Group: prod Device Group Type: RDF1
Local
DEV001
SYMMETRIX BCV001
Standard
R1
BCV
(symmir) RA Group: 1 (symrdf) RA Group: 2 (symrdf -bcv)
SRDF HOP1 -
SRDF Links
SYMMETRIX RBCV001
SYMMETRIX BRBCV001
Standard
R2
BCV
Standard
R2
BCV
BCV Pair
SITE B
(symmir -rdf) RA Group: 1 (symrdf -rbcv)
BCV Pair
(symmir -rdf -bcv)
SITE C
RA Group: 2 (symrdf -brbcv)
SRDF HOP2 SRDF Link
SRDF Link
SYMMETRIX 0014
SYMMETRIX 0015
Standard
R2
BCV
Standard
R2
BCV
BCV Pair
SITE D
(symmir -f file -sid 0014)
BCV Pair
(symmir -f file -sid 0015)
SITE E
Figure 2-14
2-62
2
Targeting Commands to Various Multi-Hop Devices and Links
This section describes the command application of targeting the various devices and links in complex multi-hop RDF environments. The following sequence of commands steps through some basic control operations that touch every device and RDF link in a complex multi-hop configuration. This numbered list works with and is illustrated by Figure 2-15. The following numbering of commands directly associates with the bubble numbers shown in the figure.
1 2 3 4 5 6 7 8 9
symrdf -g <> establish symmir -g <> split -rdf symrdf -g <> establish -rbcv symrdf -g <> restore -rbcv symmir -g <> restore -rdf symrdf -g <> restore symmir -g <> split symrdf -g <> establish -bcv symmir -g <> split -rdf -bcv
Creates the standard associated hop 1 copy. Splits the standard associated hop 1 BCV device pair. Creates the standard associated hop 2 copy. Restores the standard associated hop 1 BCV with the hop 2 copy. Restores the standard associated hop 1 copy with the hop 1 BCV. Restores the standard device with the hop 1 copy. Splits the standard/BCV pair. Creates the BCV associated hop 1 remote copy. Splits the BCV associated hop 1 device pair. Creates the BCV associated hop 2 copy. Restores the BCV associated hop 1 BCV with the hop 2 copy. Restores the BCV associated hop 1 copy with the hop 1 BCV. Restores the BCV device with the hop 1 copy. Restores the standard device with the BCV copy. Creates the BCV associated hop 2 BCV copy.
10 symrdf -g <> establish -brbcv 11 symrdf -g <> restore -brbcv 12 symmir -g <> restore -rdf -bcv 13 symrdf -g <> restore -bcv 14 symmir -g <> restore 15 symmir -f <> -sid 056 establish
2-63
2
Hop 1 Hop 2
1
R1 Host
6 7
Standard
R2
14
Standard
3
R1 BCV R1 BCV R2
Symmetrix
Site A
8 13
BCV
Symmetrix
Site B
Symmetrix 042
Site D
R2
BCV
12
BCV
15
X 15 16
10
R1 BCV R2
11
Symmetrix
Site C
Symmetrix 056
Site E
Figure 2-15
Remote Multi-Hop SRDF Configurations
2-64
Relative Symmetrix Manager Functions

If you need to convert existing command scripts generated for previous versions of the Symmetrix Manager (now called EMC ControlCenter to the SYMCLI command set, refer to Table 2-9 that lists the Symmetrix Manager SM-CLI functions with equivalent SYMCLI commands.
Table 2-9
Symmetrix Manager Relationship SM-CLI Functions Target takeover Source takeover Pre-Processing Save source data Save target data Source preparation Copy source to target Copy target to source Suspend links Resume links Equivalent SYMCLI Commands symrdf -g DgName failover symrdf -g DgName failback symrdf -g DgName split symrdf -g DgName establish symrdf -g DgName restore symrdf -g DgName update symrdf -g DgName -full establish symrdf -g DgName -full restore symrdf -g DgName suspend symrdf -g DgName resume
Relative Symmetrix Manager Functions
2-65
Consistency Group Operations

A consistency group is a group of Symmetrix RDF devices specially configured to act in unison to maintain the integrity of a database distributed across multiple SRDF units.
Note: Another way to ensure the integrity of a remote database is to use Domino modes (see Domino Effect On on page 2-46).
Consistency
If one or more source (R1) devices in a consistency group can not propagate data to their corresponding target (R2) devices, the PowerPath connected consistency group devices suspend all the source (R1) propagation from these devices in the consistency group. This ensures that all data flow to the consistency groups target (R2) side is instantly and completely halted (see Figure 2-16), and that a consistent database (up to the point in time of data propagation failure) exists on the remote side of the configuration. This ensures the integrity of the remote database.
2-66
Figure 2-16
All Data Propagation is Suspended upon any Link Failure
I/O to the local consistency group devices automatically resumes when the RDF source (R1) devices in the consistency group are suspended. While these updates are not immediately sent to the target side, they are propagated through normal SRDF operation once SRDF mirroring is resumed. Consistency group operations and their associated RDF PowerPath connected devices can be managed using the symcg command.
2-67
2
Creating a Consistency Group
Initially, you must explicitly create an empty consistency group (that can be populated with devices) using the symcg command. When you create a consistency group, you assign it a group name. For example, to create a consistency group named mycg1, enter:
symcg create mycg1
Once you create the group, you can add RDF devices to the group. These RDF devices can belong to different RA groups within a Symmetrix unit and to different Symmetrix units. Deleting a Consistency Group You can delete a specified consistency group. If there are members in the group, the command is rejected unless you use force (-force). For example, to delete an RDF consistency group (mycg1), regardless if the group has members or not, enter:
symcg delete mycg1 -force
Adding devices to a group
You can add RDF devices to a specified consistency group. For example, to add a physical device (/dev/rhdskpower61) to a consistency group oracg, enter:
symcg -cg oracg add pd /dev/rhdskpower61
To add a Symmetrix device (00C) to a consistency group oracg, enter:

symcg -cg oracg add dev 00C -sid 26033
You can also add all RDF devices that are connected and visible to the host through the PowerPath interface, or all devices on a specified Symmetrix. For example, to add all visible RDF devices of Symmetrix 012000426033, to consistency group oracg, enter:
symcg -cg oracg addall -sid 012000426033
To add all RDF devices (visible and non-visable) of Symmetrix 012000426033, to consistency group oracg, enter:
symcg -cg oracg addall dev -sid 012000426033
2-68
2
Removing Devices You can remove a specific Symmetrix device from a group using the devices physical or Symmetrix device name. For example, to remove Symmetrix device 00C from group oracg of Symmetrix 012000426033, enter:
symcg -g oracg remove dev 00C -sid 012000426033
You can remove all the Symmetrix devices from a consistency group. For example, to remove all Symmetrix devices from group oracg of Symmetrix 012000426033, enter:
symcg -g oracg rmall -sid 012000426033
With the addall and rmall command, you can confine the action to Symmetrix unit, an RA group number, just standard RDF devices, or just BCV RDF devices. For example, to remove all standard devices from group oracg of Symmetrix 012000426033, enter:
symcg -g oracg rmall -nobcv -sid 012000426033
Enable/Disable Consistency Groups
You can enable or disable the consistency state of a device group. For example, to establish (enable) consistency to group oracg, enter:
symcg -g oracg enable
For example, to disable consistency to group oracg, enter:

symcg -g oracg disable
Viewing Consistency Groups
You can view all Symmetrix consistency groups or find specific information about a specified consistency group. For example, to list all consistency groups on this host, enter:
symcg list
To list in verbose mode all the consistency groups, enter:

symcg list -v
To view information about a consistency group oracg, enter:

symcg show oracg
2-69
2
Translating Device Groups to Consistency Groups
From an existing device group, you can import or translate the devices to an existing consistency group or create a new consistency group using the following command format:
symdg [-h] dg2cg DgName CgName [-bcv|-nobcv] [-force]
For example, to translate and add all devices of device group oradg_rdf1 to consistency group named oracg, enter:
symdg dg2cg oradg_rdf1 oracg
To translate and add just the BCV devices of device group oradg_rdf1 to consistency group named oracg, enter:
symdg dg2cg oradg_rdf1 oracg -bcv
Translating RDBMS Devices to Symmetrix Groups
From an existing database, you can import or translate the devices of an RDBMS to an existing consistency group or create a new consistency group using the following command format:
symrdb [-h] [-type DbType][-db DbName][-sid SymmId] \ rdb2cg CgName [-cgtype RDF1|RDF2][-bcv|-nobcv]\ [-force]
For example, to create a consistency group named ProdRcg with the R1 standard and R1 BCV devices from the database named ADB4db, enter:
symrdb -db ADB4db rdb2cg ProdRcg -cgtype RDF1
To create a consistency group named myrdfcg with only the R1 standard devices from the database named Accdb, enter:
symrdb -db Accdb rdb2cg myrdfcg -nobcv -cgtype RDF1
TBS Devices To Device Groups
From a database, you can import or translate the devices of an RDBMS tablespace to an existing consistency group or create a new consistency group using the following command format:
symrdb [-h] [-type DbType][-db DbName][-sid SymmId] \ tbs2cg -tbs TblSpName CgName \ [-cgtype RDF1|RDF2] [-bcv|-nobcv] [-force]
For example, to create a consistency group named ProdRcg with the R1 standard and R1 BCV devices from the tablespace named ADB4tbs, enter:
2-70
2
symrdb -tbs ADB4tbs tbs2cg ProdRcg -cgtype RDF1
To create a consistency group named myrdfcg with only the R1 standard devices from the tablespace named Acctbs, enter:
symrdb -tbs Acctbs tbs2cg myrdfcg -nobcv -cgtype RDF1
Translating Volume Groups to Symmetrix Groups
From a logical volume group, you can import or translate the devices to an existing consistency group or create a new consistency group using the following command format:
symvg [-h] [-type VgType] vg2cg VgName CgName \ [-cgtype RDF1|RDF2] [-bcv|-nobcv] [-force]
LVs To Consistency Groups
For example, to create a consistency group named ProdRcg with the R1 standard and R1 BCV devices from the volume group named LVM4vg, enter:
symvg vg2cg LVM4vg ProdRcg -cgtype RDF1
To create a consistency group named myrdfcg with only the R1 standard devices from the volume group named Accvg, enter:
symvg vg2cg Accvg myrdfcg -nobcv -cgtype RDF1
2-71
symrdf -cg Command Line Options

With the symrdf -cg command, you can perform most of the RDF control operations on RDF devices in a consistency group that you can when directing symrdf to device groups (-g). The control operations (arguments) have similar options which allow flexibility in controlling RDF pairs in consistency groups. Table 2-10 lists the symrdf control operations type arguments and options available when operating on RDF device(s) of a specified consistency group.
Table 2-10
symrdf -cg Control Arguments and Applicable Options -by pass X X X X X X X X X X X X X X X -no echo X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X -no prompt X X X X X X X X X X X X X X X
Argument establish -full establish split restore -full restore failover failback suspend resume merge update ready r1 | r2 not_ready r1 | r2 rw_enable r1 | r2 write_disable r1 | r2
-force X X X X X X X X X X X X X X X
-i/-c X X X X X X X X X X X X X X X
-v
2-72
2
Table 2-10
symrdf -cg Control Arguments and Applicable Options -by pass X X X -no echo X X X X -no prompt X X X
Argument refresh r1 | r2 invalidate r1 | r2 set mode|domino|acp_skew
-force X X X
-i/-c X X
-v
Table 2-11 lists the symrdf view action type arguments and options available when viewing RDF device(s) of a specified consistency group.
Table 2-11
symrdf -cg View Arguments and Applicable Options -synchro nized -suspen ded -susp_ offline -failed over
Argument query verifya
-i/-c X X
-offline X X
-split
-enabled
-updated -valid
a. Other options for the verify argument are -syncinprog, -updateinprog, and -partitioned
For information about the various arguments and options refer to the SRDF control operations previously described in this chapter and Appendix A.
symrdf -cg Command Line Options
2-73
2-74
A
This appendix describes the SYMCLI commands for SRDF specific operations. The commands appear in alphabetic order. symcg ..................................................................................................A-3 symioctl ............................................................................................A-10 symrdf...............................................................................................A-16
A-1
SYMCLI Conventions
Categories of information shown below (similar to UNIX man pages) are listed for each command, where applicable. Command name appears in bold typeface at the top of a page followed by a brief description of what the function does. SYNTAX lists the arguments and options for each command. DESCRIPTION provides a description of the command. ARGUMENTS explains the command arguments. OPTIONS explains the command options. PARAMETERS explains the command parameters. RETURN CODES1 specifies the primary success and failure codes for each command. EXAMPLES provides examples of the syntax and output, if any, of the command.
1. For OpenVMS, use write sys$output $status to view return code. SYMCLI return codes for OpenVMS require a special DCL conversion: [SAMPLE-DCL] $ $ $ $ $ $ $ ! Example: Convert SYMCLI return codes. ! a = ( p1 .and. %x0000ffff) ! Mask off bits 16-31. a = ( a/8 ) ! Shift 3-15 right. write sys$output a ! Print return code minus ! severity level. !
For example, an OpenVMS SYMCLI return code of %X1FFF002B would convert to an error code of 5.
A-2
symcg
Performs operations on a Symmetrix RDF consistency group (cg). SYNTAX
symcg -h symcg create CgName delete CgName export CgName import CgName list show [-v] CgName
[-force][-symforce] [-f FileName] [-rdf] [-f FileName] [-offline] [-offline]
symcg <-g|-cg> CgName add add pd PdevName dev SymDevname
[-sid SymmID]
remove pd PdevName [-force][-symforce] remove dev SymDevname [-sid SymmID] [-force][-symforce] addall [dev][-sid SymmID] [-r1|-r2][-RDFG GrpNum][-nobcv] \ [-range SymdevStart:SymdevEnd] rmall [-sid SymmID] [-r1|-r2][-RDFG GrpNum][-nobcv] \ [-range SymdevStart:SymdevEnd] symcg <-g|-cg> CgName [-force] [-noprompt|-v] enable disable
DESCRIPTION
The symcg command performs operations specific to consistency groups as follows: Creates and deletes consistency groups Adds and removes devices of a consistency group Exports and imports consistency group device lists Lists consistency groups Shows detailed information about a consistency group Enables or disables the consistency mode of a device group
symcg
A-3
A
Consistency groups are only valid for RDF devices that are configured as EMC PowerPath devices. ARGUMENTS add pd Adds an RDF device, using its physical device (host) name to the specified consistency group. add dev Adds an RDF device, using its Symmetrix device name to the specified consistency group. addall [dev] Adds to a specified consistency group all RDF devices that are visible and connected to this host through a PowerPath interface. You can also specify a Symmetrix ID to confine the selection of devices from a specific Symmetrix unit for addition to the group. When dev is used, all devices are added, even if they are not connected to the host. create Creates an empty consistency group to hold RDF devices. delete Deletes the specified consistency group. If there are members in the group, the command is rejected unless you use force (-force). If RDF consistency is enabled and it cannot be disabled, the -symforce option can be used. enable Enables RDF consistency for all devices in the RDF consistency group. export Exports a list of devices in a consistency group to a text file, which can be used import the consistency group at such time when needed.
A-4
A
disable Disables RDF consistency for all devices in the RDF consistency group. import Imports a list of devices in a consistency group from a text file, which was created from a text file. list Lists all the consistency groups that were created for this host. remove pd Removes a Symmetrix device, using its physical device (host) name from the specified consistency group. If RDF consistency is enabled and it cannot be disabled, the -symforce option can be used. remove dev Removes a Symmetrix device, using its Symmetrix device name from the specified consistency group. If RDF consistency is enabled and it cannot be disabled, the -symforce option can be used. rmall Removes all Symmetrix devices from the specified consistency group. show Shows detailed information about the specified consistency group. OPTIONS -cg Applies the command to a consistency group name. -f Specifies the text file (for export or import action) which will or currently contains the device list for a consistency group.
symcg
A-5
A
-force Forces the action to occur that overrides instances where they should be rejected.
Note: Use care when applying this option.
-g Applies the command to a consistency group name. -h Provides brief, online help information. -nobcv Confines the command to standard RDF devices only. -noprompt No prompt flag. The default is to prompt the user between command executions for permission to continue. -offline Makes the Symmetrix data connection offline from the host in-memory database for this action. -range Applies the action to a number of Symmetrix devices within a contiguous range to add, or remove all devices to/from a consistency group. -rdf When exporting a consistency group list, uses the remote Symmetrix ID(s) and their device names. This allows the group to be imported on a host connected to the remote Symeetrix units. -R1 Confines the action to RDF R1 devices only. -R2 Confines the action to RDF R2 devices only.
A-6
A
-RDFG Restricts the command to the specified RDF RA group. -sid Applies a Symmetrix ID to the command, confining the scope of the operation to a specific Symmetrix unit. -symforce Forces the action to occur that overrides instances where they should be rejected. Applied with remove or delete actions when the device is enabled and it cannot be disabled.
Note: Use care when applying this option.
-v Provides a more detailed, verbose listing to the command operation.
PARAMETERS
CgName Defines the consistency group name (user defined and unique to this host). GrpNum Defines the RDF (RA) group number assigned to a set of Symmetrix RDF devices. FileName Defines the name of the text file which is used to export or import the consistency group device list. PdevName Defines the physical device name used by the host. SymdevEnd The Symmetrix device name, ending the contiguous range of selected devices, such as 01C
symcg
A-7
A
SymdevStart The Symmetrix device name, starting the range of selected devices, such as 000 SymDevname Defines the Symmetrix device name. SymmID Defines a 12-character ID for the Symmetrix unit. RETURN CODES The following are possible status or error codes that can be returned by this command (e.g. in a UNIX C shell, returned using echo $status):
Code# 0 1 2 19 Code Symbol and Description CLI_C_SUCCESS Indicates that the command was successful CLI_C_FAIL Indicates that the command failed CLI_C_DB_FILE_IS_LOCKED The database file is locked by another user CLI_C_GK_IS_LOCKED All gatekeepers to the Symmetrix unit are currently locked.
EXAMPLES
To create a Symmetrix consistency group, mycg1, of type RDF1 (R1), enter:

symcg create mycg1
To list all Symmetrix consistency groups in detailed format, enter:

symcg -v list
To show information about consistency group oracg, enter:

symcg show oracg
To delete Symmetrix consistency group oracg, regardless whether the group has members or not, enter:
symcg delete oracg -force
A-8
A
To add a device (/dev/rhdskpower61) to a Symmetrix consistency group oracg, enter:
symcg -g oracg add pd /dev/rhdskpower61
To remove a device (00C) from a Symmetrix consistency group oracg in Symmetrix 55, enter:
symcg -g oracg -sid 55 remove dev 00C
To enable RDF consistency for all devices in consistency group oracg, enter:
symcg -g oracg enable
To disable RDF consistency for all devices in consistency group oracg, enter:
symcg -cg oracg disable
symcg
A-9
symioctl
Sends I/O control commands to a specified database server application. SYNTAX
symioctl -h symioctl -type DbType [-noprompt] begin backup end backup freeze thaw checkpoint archive log <Object> <Object> <Object> <Object> <Object> <Object> <Object> <Object> <Object> <Object> [-checkpoint] [-checkpoint]
DESCRIPTION
The symioctl command performs control operations on a specified database application. This utility is intended to be used in conjunction with a TimeFinder or SRDF split operation. The freeze action will suspend database updates from getting written to disk. Once the split operation completes, a symioctl thaw action must be sent to resume full I/O access to the database.
Note: The user account of the symioctl command must have System Administrator privileges.
For the various symioctl arguments, an object or object list is sometimes not required (see Table A-1).
Table A-1
Specifiying Objects with symioctl Argument freeze thaw RDBMS Oracle SQL Server Informix Objects database server database name database server List Object No Yes No
A-10
A
Table A-1
Specifiying Objects with symioctl Argument checkpoint RDBMS Oracle SQL Server Informix Oracle Objects database server database name database server tablespace List Object No Yes No Yes
begin backup end backup archive log
Oracle
database server
No
For Oracle, hot backup control of a list of table objects must be performed before and after a freeze/thaw command. The steps required to split a group of BCV devices follows: 1. symioctl begin backup 2. symioctl freeze 3. Split standard and BCV pairs. This may involve several steps depending on your environment. 4. symioctl thaw 5. symioctl end backup This command supports the platforms and database applications listed in Table A-2.
Table A-2
Databases and Platforms for symioctl On Platforms Sun Solaris HP-UX IBM AIX Sun Solaris HP-UX IBM AIX Windows NT/2000 (Intel-based) Windows NT/2000 (Intel-based) For Databases INFORMIX Dynamic Server, V7.3
Oracle 8i (all actions supported) Oracle 7 (just backup actions supported)
SQL Server, V7.0
symioctl
A-11
A
Environment Variables You need to define the UNIX environment variables for Oracle and Informix databases in order for any database mapping commands to succeed (see Table A-3).
System DB Environment Variables For Database Oracle Set Variables ORACLE_HOME ORACLE_SID PATH INFORMIXDIR ONCONFIG INFORMIXSERVER PATH
Table A-3
Informix
See your System Administrator for more specific information about setting these variables for your system platform and database. Table A-4 lists the various environment variables that you should set to simplify certain repetition of argument entries or options in your command line sequences. These are particularly useful when you are about to apply multiple database calls.
Table A-4
symioctl DB Environment Variables Description Specifies a user name, password, and remote service name for a users relational database account (user/password@service). Specifies a specific type (DbType) of database. Possible values: Informix Oracle SQLServer Default None. Must be specified by user. NULL
Variable Name SYMCLI_RDB_CONNECT
SYMCLI_RDB_TYPE
Note: SYMCLI_RDB_CONNECT must be set with your user name and password for you to access the specified database with this command.
For any individual command, you can override the variable value of SYMCLI_RDB_TYPE to explicitly specify the option in the command argument.
A-12
A
ARGUMENTS begin backup For Oracle only, this action places the specified tablespace objects into hot backup mode. end backup For Oracle only, this action terminates the hot backup mode of the specified tablespace objects. freeze Freezes all I/O to a specified database application. thaw Resumes full I/O to the specified database. checkpoint Issues a checkpoint to the RDBMS. archive log For Oracle databases, this action archives the current log.
OPTIONS
-checkpoint Request a checkpoint prior to the specified action. -h Provides brief, online help information. -noprompt No Prompt option. The default is to prompt the user for confirmation before executing the indicated control operation. -type Applies the command to a database type of the database. Possible values are: Informix Oracle SQLServer
symioctl
A-13
A
PARAMETERS DbType Defines the database type. Possible values are: Informix Oracle SQLServer Object Database name or tablespace name. If no objects are specified, the action defaults to all objects of the specified type database. RETURN CODES The following are possible status or error codes that can be returned by this command (for example, in a UNIX C shell, returned using echo $status):
Code# 0 1 Code Symbol and Description CLI_C_SUCCESS Indicates that the command was successful CLI_C_FAIL Indicates that the command failed
EXAMPLES
The database access environment variable (SYMCLI_RDB_ CONNECT) must be set before any commands as follows:
setenv SYMCLI_RDB_CONNECT "scott/tiger@acme"
To freeze all I/O to an SQL Server database named pubs, enter:

symioctl freeze -type SQLServer pubs
To thaw all I/O to an Oracle database, enter:

symioctl thaw -type Oracle
To place all tables in an Oracle database into hot backup mode, enter:
symioctl begin backup -type Oracle
With the login parameters set in an environment variable (user=infadm, passwd = pass, and service = infserv), freeze all I/O to an INFORMIX database without prompting for confirmation, enter:
setenv SYMCLI_RDB_CONNECT "infadm/pass@infserv" symioctl freeze -type Informix -noprompt
A-14
A
With the database type preset in the environment variable, archive the current log of the Oracle instance represented by connection information, enter:
setenv SYMCLI_RDB_TYPE oracle symioctl archive log -noprompt
To perform a checkpoint for the Informix database. The database type is preset in the environment variable.
setenv SYMCLI_RDB_TYPE informix symioctl checkpoint
symioctl
A-15
symrdf
Performs Symmetrix SRDF ping, control, or modify operations on a device group, consistency group, or on a device within a device group. The device group must have a type of either RDF1 or RDF2. SYNTAX
symrdf -h symrdf [-sid SymmID] [-i Interval [-c Count]] ping [-rdf] list [dev|pd] [-v] [-R1|-R2][-RDFG GrpNum][-bcv|-nobcv] \ [-resv] [-offline][-consistency] symrdf -g DgName [-v|-noecho][-force][-bcv|-rbcv|-brbcv|-all] \ [-bypass][-noprompt][-i Interval [-c Count]] establish [-full] [LdevName [LdevName]] restore split failover failback suspend resume merge update ready not ready [-full] [LdevName [LdevName]] [LdevName [LdevName]] [LdevName [LdevName]] [LdevName [LdevName]] [LdevName [LdevName]] [LdevName [LdevName]] [LdevName [LdevName]] [-until InvalidTracks][LdevName [LdevName]] [LdevName [LdevName]] r1|r2 [LdevName [LdevName]] r1|r2
rw_enable [LdevName [LdevName]] r1|r2 write_disable [LdevName [LdevName]] r1|r2 refresh invalidate [LdevName [LdevName]] r1|r2 [LdevName [LdevName]] r1|r2
symrdf -g DgName [-force] [-bcv|-all] [-v|-noecho] [-bypass] [-i Interval] [-c Count] [-noprompt] swap -refresh R1|R2 symrdf -g DgName [-bcv|-rbcv|-brbcv|-all] [-offline] \ [-i Interval [-c Count]] query [LdevName [LdevName]] verify <[-synchronized] [-enabled]>|-suspended | -susp_offline |-split |-failedover |-updated | -syncinprog |-updateinprog |-partitioned |-valid
A-16
A
[LdevName [LdevName]] symrdf -g DgName [-v][-bcv|-rbvc|-brbcv|-all][-bypass] [-noprompt] \ [-i Interval [-c Count]] set mode sync|semi|acp_disk|acp_wp|acp_off \ [skew <SkewVal>] [LdevName [LdevName]] set domino on|off [LdevName [LdevName]] set acp_skew <SkewVal> [LdevName [LdevName]]
Consistency Groups
symrdf -cg CgName [-v|-noecho][-noprompt] [-force] \ [-bypass] [-i Interval [-c Count]] establish [-full] restore split failover failback suspend resume merge update [-until InvalidTracks] [-full]
symrdf -cg CgName [-offline] [-i Interval [-c Count]] query verify <[-synchronized] [-enabled]>|-suspended | -susp_offline |-split |-failedover |-updated | -syncinprog |-updateinprog |-partitioned |-valid
symrdf -cg CgName [-noprompt] [-force] [-bypass] set mode sync|semi|acp_disk|acp_wp|acp_off [SkewVal] set domino on|off set acp_skew <SkewVal>
DESCRIPTION
The symrdf command invokes an RDF operation on a group of remotely mirrored standard devices, or on one remotely mirrored standard device. These operations include establishing (data copy from the source side to the target side), splitting the remotely mirrored pair, restoring (data copy from the target side to the source side), and querying the state of the remotely mirrored pair. Both the establish and restore operations can be done fully (entire copy) or incrementally (only changed tracks are synchronized). By default, if the -full option is not specified, an incremental establish or restore is attempted.
symrdf
A-17
A
Note: You cannot perform an establish or restore if the remote pair state is not Split or Suspended.
All these operations can be done on a device group basis, individual device basis, or list basis (for more than one device with one command). For device lists, you can either concatenate the list of device names (LdevNames) within the command, or: on UNIX only, specify a specific import file that contains the device names. For example, to perform a split operation on multiple devices listed in a file, use the form:
symrdf -g DgName split cat LdevListFile
The file, read by this UNIX command, must have logical device names with one LdevName per line. ARGUMENTS establish Resumes remote mirroring and initiates a data copy from source (R1) side to the target (R2) side. Depending on whether the establish operation is full or incremental, all or only the changed tracks are copied to the target (R2) side. Write disables the target device(s) to its/their local hosts. Subsequently, for each RDF pair, invalidates all or the needed tracks for the target (R2) side. Finally, a full data copy is started from the source (R1) side to target (R2) side.
This action can only be executed if the standard RDF device(s) in the group have been RDF split or Suspended.
restore Resumes remote mirroring and initiates a data copy from target (R2) side to the source (R1) side. Depends whether the establish operation is full or incremental, all or only the changed tracks are copied to the source (R1) side. Write disables the target device(s) to its/their local hosts. Subsequently, for each RDF pair, invalidates all or the required tracks for the source (R1) side. Finally, a data copy is started from the target (R2) side to the source (R1) side.
A-18
A
This action can only be executed if the standard RDF device(s) in the group have been RDF split or Suspended.
split Stops remote mirroring for the RDF pair(s) in the group. For each RDF pair, suspends I/O traffic on the RDF links and write enables the target device(s) to its/their local hosts.
Note: This action can only be executed if the remotely mirrored standard device(s) in the group are synchronized.
failover Switches data processing from the source (R1) to the target (R2) side. If the source (R1) is operational, suspends I/O traffic on the RDF links and write disables the device(s) on the source (R1) side to its/their local hosts. Then, it suspends traffic on the RDF links, write enables the device(s) on the target side to its/their local hosts. failback Switches data processing back to the source (R1) side. If the target (R2) is operational, write disables the device(s) on the target side to its/their local hosts, and resumes I/O traffic on the RDF links. Then it write enables the device(s) on the source (R1) side to its/their local hosts. invalidate Invalidates the source (R1) device(s) or the target (R2) device(s) so that a full copy can be initiated from the remote mirror. list dev Lists all RDF devices that are configured on the Symmetrix units attached to this host. dev is the default name type, which lists the devices using Symmetrix device names. list pd Lists all RDF devices that are visible to this host. pd lists the devices using physical device (host) names.
symrdf
A-19
A
merge Merges the device track tables between the source (R1) side and the target (R2) side for one or all devices in a device group. not_ready Set the source (R1) device(s) or the target (R2) device(s) to be RDF not ready to their respective local host(s). ping Ping(s) one or more Symmetrix units. By default, only the remotely connected Symmetrix units are pinged through the RDF links. The ping action returns the following unique return codes if the all or some of the targeted Symmetrix units were was successfully pinged:
Code # 8 9
Code Symbol CLI_C_NOT_ALL_PINGED CLI_C_NONE_PINGED
Refer to RETURN CODES for more information. query Returns information about the state of RDF mirroring of one or all device pairs in a device group. ready Set the source (R1) device(s) or the target (R2) device(s) to be RDF ready to their respective local host(s). refresh Marks the source (R1) device(s) or the target (R2) device(s) to refresh from the remote mirror. resume Resumes I/O traffic on the RDF links for the remotely mirrored pair(s) in the group.
A-20
A
rw_enable Set the source (R1) device(s) or the target (R2) device(s) to be Read and Write enabled to its/their local hosts. set mode Sets the RDF mode for one or more RDF pairs in a device group to be Synchronous (sync), semi-synchronous (semi), Adaptive Copy Disk mode (acp_disk), Adaptive Copy Write Pending mode (acp_disk), Or Turns off the Adaptive copy mode (acp_off). set domino Sets the domino mode of one or more RDF pairs in a device group to be ON or OFF. set acp_skew Modifies the value of the skew factor for the set Adaptive Copy mode. skew Modifies the value of the skew factor for the set adaptive copy mode. suspend Suspends I/O traffic on the RDF links for the remotely mirrored pair(s) in the group. swap Swaps the RDF personality of the RDF device designations of a specified device group. Source R1 device(s) become target R2 device(s) and target R2 device(s) become source R1 device(s). This action requires both an SRDF license and a Configuration Mgr license. update Starts an update of the source (R1) side after a failover and while the target(R2) side may still be operational to its local host(s).
symrdf
A-21
A
verify Verifies whether one RDF device pair or all RDF device pairs in a device group are in the Synchronized state. Optionally it can verify whether the RDF device pair or all device pairs in a device group are in the Updated state, or in any valid RDF pair state. The RDF verify action returns the following unique return codes if the verify criteria was not met:
Code # 4 5 6 7 14 15 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
Code Symbol CLI_C_NOT_ALL_SYNCHRONIZED CLI_C_NONE_SYNCHRONIZED CLI_C_NOT_ALL_UPDATED CLI_C_NONE_UPDATED CLI_C_NOT_ALL_VALID CLI_C_NONE_VALID CLI_C_NOT_ALL_SUSPENDED CLI_C_NONE_SUSPENDED CLI_C_NOT_ALL_FAILED_OVER CLI_C_NONE_FAILED_OVER CLI_C_NOT_ALL_UPDATEINPROG CLI_C_NONE_UPDATEINPROG CLI_C_NOT_ALL_PARTITIONED CLI_C_NONE_PARTITIONED CLI_C_NOT_ALL_ENABLED CLI_C_NONE_ENABLED CLI_C_NOT_ALL_SYNCHRONIZED_AND_ENABLED CLI_C_NONE_SYNCHRONIZED_AND_ENABLED CLI_C_NOT_ALL_SUSP_AND_ENABLED CLI_C_NONE_SUSP_AND_ENABLED CLI_C_NOT_ALL_SUSP_AND_OFFLINE CLI_C_NONE_SUSP_AND_OFFLINE
Refer to RETURN CODES for more information.
A-22
A
write_disable Write disables the source (R1) device(s) or the target (R2) device(s) to its/their local hosts OPTIONS -all Targets the SRDF action to all devices in the device group: standard RDF devices and locally-attached BCV RDF devices. -bcv Target the SRDF action at the specified locally-associated BCV device(s) that are configured as RDF Hop 1 BCV devices. -brbcv Target the SRDF action at the specified remotely-associated RDF (Hop 2) BCV device(s) that can be paired with the remote mirrors of the local BCV devices. -rbcv Target the SRDF action at the specified remotely-associated RDF (Hop 2) BCV device(s) that can be paired with the remote mirrors of the local standard devices. -bypass Bypass any existing Symmetrix exclusive locks during the SRDF operation.
CAUTION Use this option ONLY if you are SURE that no other SRDF operation is in progress in either the local and/or remote Symmetrix units. -c Number (count) of times to display or to acquire an exclusive locks on the Symmetrix host database, the local Symmetrix, and the remote Symmetrix units. If this option is not specified and an interval (-i) is specified, program will loop continuously to display, or until RDF control or set operation starts.
symrdf
A-23
A
-cg Applies a Consistency Group name to the operation. -consistency Display the RDF consistency state when listing RDF devices. -enabled Verifies whether the RDF device pair(s) are in the Enabled Consistency state. -full Requests a full establish or restore operation. If this option is not specified, is an incremental establish or restore is attempted. -force Attempts to force the operation even though one or more devices in the device group may not be in the normal, expected state(s) or the specified operation. -g Applies a device group name to the operation. -h Brief online help information. -i Repeat interval in seconds to display or to acquire an exclusive locks on the Symmetrix host database, the local Symmetrix, and the remote Symmetrix units. The default interval is 10 seconds. The minimum interval is 5 seconds. -nobcv List standard SRDF devices only (excludes RDF BCV devices). -noecho Do not echo to the screen the progress status of the RDF action.
A-24
A
-noprompt No Prompt option. The default is to prompt the user for confirmation. -offline Makes the Symmetrix data connection offline from the host in-memory database for this action. -partitioned Verifies whether the RDF device pair(s) are in the Partitioned state. -R1 List RDF1 (R1) devices only. -R2 List RDF2 (R2) devices only. -rdf Ping the specified Symmetrix unit via the RDF links even though it may be also attached locally to the host. -RDFG Applies a Symmetrix RA group number to the command to restrict the list to just the RDF devices of an RA group. -refresh Marks the source R1 device(s) or the target R2 device(s) to refresh from the remote mirror after a swap operation. -resv List all Symmetrix devices that are visible to this host and that have SCSI reservations. -sid Limits listing of Symmetrix devices visible to this host to ones that belong to the specified Symmetrix unit.
symrdf
A-25
A
-split Verifies whether the RDF device pair(s) are in the Split state. -suspended Verifies whether the RDF device pair(s) are in the Suspended state. -susp_offline Verify whether the RDF device pair(s) are in the Suspended state and the SRDF link is Offline. -synchronized Verifies whether the RDF device pair(s) are in the Synchronized state. -syncinprog Verifies whether the RDF device pair(s) are in the SyncInProg state. -until Used with the update argument to identify a number of Invalid tracks that are allowed to build up from the active R2 local I/O before another update (R2 to R1 copy) is re-triggered. This allows continuous R1 updates to occur every time the invalid track threshold is reached on the active R2 side. Note that these update sequences start with an immediate update once this command is started. -updated Verify whether the RDF device pair(s) are in the R1 Updated state. -updateinprog Verify whether the RDF device pair(s) are in the R1 UpdInProg state. -valid Verify whether the RDF device pair(s) are in a Valid state.
A-26
A
-v Provides a more detailed, verbose listing.
PARAMETERS
DgName Defines the device group name. CgName Defines the consistency group name (user defined and unique to this host). LdevName The logical device name, such as DEV002 PdevName The host name for the physical device, such as /dev/rdsk/c2t0d2s3 SymmID The 12-digit ID of the Symmetrix unit SkewVal The skew factor for the adaptive copy mode. Possible values range from 0 to 65534 tracks. For devices larger than a 2 GB capacity drive, a value of 65,535 can be specified to target all the tracks of any given drive.
RETURN CODES
The following are possible status or error codes that can be returned by this command (for example, in a UNIX C shell, returned using echo $status):
Code# 0 1 2 3 Code Symbol and Description CLI_C_SUCCESS Indicates that the command was successful. CLI_C_FAIL Indicates that the command failed. CLI_C_DB_FILE_IS_LOCKED Indicates that the database file is locked by another user. CLI_C_SYM_IS_LOCKED Returned if the Symmetrix unit is locked by another session or user.
symrdf
A-27
A
Code# 4 Code Symbol and Description CLI_C_NOT_ALL_SYNCHRONIZED Returned if not all standard devices are in the Synchronized or in the Restored states. CLI_C_NONE_SYNCHRONIZED Returned if no standard devices are in the Synchronized or in the Restored states. CLI_C_NOT_ALL_UPDATED Returned if not all requested devices are in the Updated state. CLI_C_NONE_UPDATED Returned if no requested devices are in the Updated state. CLI_C_NOT_ALL_PINGED Returned if not all of the targeted Symmetrix units are successfully pinged. CLI_C_NONE_PINGED Returned if none of the targeted Symmetrix units are successfully pinged. CLI_C_NOT_ALL_VALID Returned if not all requested devices are in a valid RDF state (some devices are in the Invalid RDF state). CLI_C_NONE_VALID Returned if no requested devices are in a valid RDF state (all devices are in the Invalid RDF state). CLI_C_ALREADY_IN_STATE The device or device group is already in the desired RDF state. Applicable only for RDF control and RDF set actions. CLI_C_GK_IS_LOCK All gatekeepers to the Symmetrix unit are currently locked. CLI_C_NEED_MERGE_TO_RESUME You must issue an rdf merge track table before you can resume the RDF links. CLI_C_NOT_ALL_SUSPENDED Not all requested devices in the group are in a valid Suspended RDF state (some are suspended). CLI_C_NONE_SUSPENDED No requested devices in the group are in a Suspended RDF state. CLI_C_NOT_ALL_FAILED_OVER Not all requested devices in the RDF group are in the Failed Over state. CLI_C_NONE_FAILED_OVER None of the requested devices in the RDF group are in the Failed Over state.
6 7 8 9 14
15
18
19 21 31
32 33 34
A-28
A
Code# 35 36 37 38 39 Code Symbol and Description CLI_C_NOT_ALL_UPDATEINPROG Not all requested devices in the RDF group are in the R1 UpdInProg state. CLI_C_NONE_UPDATEINPROG None of the requested devices in the RDF group are in the R1 UpdInProg state. CLI_C_NOT_ALL_PARTITIONED Not all requested devices in the RDF group are in the Partitioned state. CLI_C_NONE_PARTITIONED None of the requested devices in the RDF group are in the Partitioned state. CLI_C_NOT_ALL_ENABLED Not all requested devices in the group are in an Enabled Consistency state (some are Enabled). CLI_C_NONE_ENABLED No requested devices in the group are in an Enabled Consistency state. CLI_C_NOT_ALL_SYNCHRONIZED_AND_ENABLED Not all requested devices in the group are in a Synchronized state and in an Enabled Consistency state. CLI_C_NONE_SYNCHRONIZED_AND_ENABLED None of the requested devices in the group are in a Synchronized state and in an Enabled Consistency state CLI_C_NOT_ALL_SUSP_AND_ENABLED Not all requested devices in the RDF group are in the Suspended state and in the Enabled Consistency state. CLI_C_NONE_SUSP_AND_ENABLED None of the requested devices in the RDF group are in the Suspended state and in the Enabled Consistency state. CLI_C_NOT_ALL_SUSP_AND_OFFLINE Not all requested devices in the group are in an Offline state (some are offline with RDF link suspended). CLI_C_NONE_SUSP_AND_OFFLINE Devices in the request are in the Suspended state and in the Offline Link Suspended state.
40 41
42
43
44
45
46
EXAMPLES
To create an RDF R1 device group called prod:

symdg create prod -type RDF1
To add an RDF R1 device, acct1, to the device group prod:

symld -g prod add dev 006 acct1
symrdf
A-29
A
To fully establish standard device acct1 (fully copy the R1 mirror to the R2 mirror) in group prodDB, enter:
symrdf -g prodDB establish -full acct1
To split all standard RDF devices in group prod, enter:

To perform an incremental restore from the R2 target side to the R1 source side for the RDF pair acct1 in group prodDB, enter:
symrdf -g prodDB restore acct1
To query information about all RDF standard devices in group prodDB, enter:
symrdf -g prodDB query
To invoke a failover operation on multiple logical RDF devices (DEV001, DEV002, DEV010, and DEV011) in group prodDB, enter:
symrdf -g prodDB failover DEV001 \ DEV002 \ DEV010 \ DEV011
For UNIX only, to invoke a failover operation on multiple logical RDF devices in group ProdDB that are listed in a separate file (yourldevlist), enter:
symrdf -g ProdDB failover cat yourldevlist
In this UNIX example, the imported file has the exact same logical device name listing and format as shown in the previous example.
A-30
B
This appendix describes the issues concerned with adapting and/or migrating your current Open Symmetrix Manager SM-CLI scripts to the SYMCLI Solutions Enabler environment. Compatibility Mode for Existing Symmetrix Manager Sites...... B-2 Installing the Compatibility Mode ................................................. B-3 Migrating SM-CLI Scripts to SYMCLI ........................................... B-5
B-1
Compatibility Mode for Existing Symmetrix Manager Sites

EMC no longer supports new versions of the SM-CLI command and script language (part of the Open Symmetrix Manager (OSM) beyond Versions 3.2.x). Also, at V4.0, the Open Symmetrix Manager was replaced by a larger product offering called the EMC ControlCenter. For any new script coding, EMC recommends you use the EMC Solutions Enabler SYMCLI command set, which will provide parallel functionality and more. If immediate conversion of your scripts are not possible at this time, EMC can provide a licensed Compatibility Mode key (for use during the V4.x ECC and Solutions Enabler installation) that will allow you to run a compatibility mode script (instcmpt.*). Once the compatibility mode installation is complete, your existing V3.2.x SM-CLI script commands will work in the V4.x SYMCLI environment. For example with Compatibility Mode, your original Symmetrix Manager commands srdf and bcv (including arguments and options) will still function in the new SYMCLI environment. So, your existing V3.2 Symmetrix Manager command documentation still applies here.
B-2
Installing the Compatibility Mode

Following a SYMCLI installation, if you are running EMCs Open Symmetrix Manager (OSM) Version 3.2.x on your host, you need to run a Compatibility Mode install script. To install the OSM Compatibility Mode, perform the following procedure: 1. Ensure that you are at the SYMCLI documentation directory. On UNIX platforms, the directory is: /usr/symcli/doc On Windows NT, the directory is: C:\Program Files\EMC\SYMCLI\documentation 2. Run the Compatibility Mode install script. On UNIX platforms, enter: instcmpt.csh On Windows NT, ensure that you have the perl scripting language on your system and run: perl instcmpt.pl 3. Choose the desired components of the Compatibility Mode to install. 4. When prompted, enter the location of your symapps (and if required, SYMCLI binary directory). On UNIX platforms, these directories are usually: /usr/symcli/bin /usr/symmapps/bin On Windows NT, these directories are usually: C:\Program Files\EMC\symmapps\bin C:\Program Files\EMC\SYMCLI\binaries These install locations can be accepted as the default by hitting Enter with no input.
Installing the Compatibility Mode
B-3
B
5. If you installed the SRDF component, you must set environment variable SYMCLI_OSM_VERSION to match what the install script reports. The install script reports the version number with the following line:
setenv SYMCLI_OSM_VERSION x.x.x
6. In order to extablish a SYMAPI database, you should now enter the following SM-CLI command:
bcv setup
This command scans all devices on the SCSI bus looking for Symmetrix devices and builds the Symmetrix host (SYMAPI) database, which is necessary for the SYMCLI environment.
B-4
Migrating SM-CLI Scripts to SYMCLI

If you need to convert existing command scripts generated for previous versions of the Symmetrix Manager (now called EMC ControlCenter to the SYMCLI command set, refer to Table B-1 that lists the Symmetrix Manager SM-CLI functions with equivalent SYMCLI commands.
Table B-1
Symmetrix Manager Relationship SM-CLI Functions Target takeover Source takeover Pre-Processing Save source data Save target data Source preparation Copy source to target Copy target to source Suspend links Resume links bcv setup Equivalent SYMCLI Commands symrdf -g DgName failover symrdf -g DgName failback symrdf -g DgName split symrdf -g DgName establish symrdf -g DgName restore symrdf -g DgName update symrdf -g DgName -full establish symrdf -g DgName -full restore symrdf -g DgName suspend symrdf -g DgName resume symcfg discover
Migrating SM-CLI Scripts to SYMCLI
B-5
B-6
Glossary
This glossary contains terms related to disk storage subsystems. Many of these terms are used in this manual.
A
Adaptive Copy - Write Pending mode An SRDF mode of operation that stores new data for a remotely mirrored pair in the cache of the local Symmetrix unit until it can be successfully written to both the source (R1) and target (R2) devices. A skew parameter associated with this mode determines the maximum number of write pendings that can exist for a remotely mirrored pair. (There is a skew value for each remotely mirrored pair configured for the Adaptive Copy mode in Symmetrix units.) This skew parameter is set at the device level and can range from 1 to 65,535 (decimal). An SRDF mode of operation that stores new data for a remotely mirrored pair on the source (R1) device of that pair as invalid tracks. This operation continues until it can be successfully transferred to the target (R2) device. A skew parameter associated with this mode indicates the maximum number of tracks that can be out of synchronization between the two devices at any given time. This skew parameter value set at the device level in Symmetrix units can range from 1 to 65,535 (decimal).
Adaptive Copy - Disk Mode
B
BCV Device A Symmetrix Business Continuance Volume (BCV) that functions as a mirrored media to a standard device for a protected storage environment.
g-1
Glossary
BCV Pair
Consists of a standard device and a BCV device providing a protected storage environment. A protected storage environment solution that has defined specially configured Symmetrix devices as mirrors or Business Continuance Volumes (BCVs) to protect data on standard devices. See BCV Device.
Business Continuance
Business Continuance Volume
C
CA Cache Channel Adapter. See Parallel Channel Director. Random access electronic storage used to retain frequently used data from disk for faster access by the channel. The channel adapter (CA) in the Symmetrix subsystem that interfaces between the host channels and data storage. It transfers data between the channel and cache.
Channel Director
D
DA Destage Disk Adapter. See Disk Director. The asynchronous write of new or updated data from cache to disk device. A general term referring to a storage device. In the Symmetrix subsystem, a device corresponds to a single device visible to the host. The device group name (DgName/dg) is a user-defined name, which specifies a group of associated devices that support a common function, application, or database. System level tests or firmware designed to inspect, detect, and correct failing components. These tests are comprehensive and self-invoking. The splitting of a BCV pair that will only archive changed (differential) data from the first mirror to the remaining mirror set when the BCV split completes. A uniquely addressable part of the Symmetrix subsystem that consists of a set of access arms, the associated disk surfaces, and the electronic circuitry required to locate, read, and write data.
Device
Device Group Name
Diagnostics
Differential Split
Disk
g-2
Glossary
Director
An adapter (such as a DA, RA, SA, EA) in the Symmetrix subsystem that is the interface for control and data transfers between the host channels and disk devices. The disk adapter (DA) in the Symmetrix subsystem that interfaces between cache and the disk devices. An optional feature for RDF1 source (R1) devices. When enabled, this feature causes a master device to become not ready to its host and all I/O activity ceases with that device if the slave device fails or a link failure occurs. When the fault condition is corrected, the user must manually make the master device ready. This feature ensures that a remotely mirrored pair is always synchronized. A Symmetrix feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all non-mirrored devices in the Symmetrix subsystem.
Disk Director
Domino Effect
Dynamic Sparing
E
EA Establish ESCON Adapter. See Serial Channel Director. A BCV or SRDF control operation. For BCV control operations, a BCV establish operation assigns a BCV device to the standard device as the next available mirror of a standard device. The BCV establish operation causes the BCV device to be fully synchronized and functioning as a Symmetrix mirrored media. For SRDF control operations, an SRDF establish operation issues a full copy from the source (R1) device to the target (R2) device. The SRDF establish operation causes the source (R1) device to be fully synchronized with the target (R2) device. See Incremental Establish.
F
Fast-Wide SCSI Channel Director The SCSI adapter (SA) director in the Symmetrix subsystem that interfaces between host SCSI channels and data storage. It transfers data between the channel and cache.
g-3
Glossary
Fast Write
A Symmetrix write operation at cache speed that does not require immediate transfer of data to disk. The data is written directly to cache and is available for later destaging. Fibre Channel. See Fibre Channel Director. The Fibre Channel (FC) director in the Symmetrix subsystem that interfaces between the host fibre channel interface and data storage. It transfers data between the channel and cache.
FC Fibre Channel Director
G
Gatekeeper A Symmetrix device accessible by the host through which the SYMCLI/SYMAPI software communicates with the Symmetrix. A gatekeeper routes the SCSI commands executed by the SYMCLI/SYMAPI to the Symmetrix unit devices. 109 bytes.
Gigabyte (GB)
H
Hit Ratio Percentage of cache hits (reads and writes serviced by cache) out of all I/O requests. The splitting of a physical disk into 2 or more logical volumes (hyper-volumes). The host views hyper-volumes as individual physical devices. The number of possible hyper-volumes per disk depends on disk capacity.
Hyper-Volume
I
Identifier (ID) A sequence of bits or characters that identifies a program, device, controller, or system. A BCV or SRDF control operation. For BCV control operations, an incremental establish causes the BCV device to be incrementally synchronized and functioning as a Symmetrix mirrored media. (The devices must have been previously paired.) This is the same as an establish operation except that an incremental establish is much faster. This is accomplished by copying
Incremental Establish
g-4
Glossary
only the differences or new storage data from the standard device to the BCV device. Any changed tracks on the BCV device are overwritten by the data on the corresponding tracks from the standard device. For SRDF control operations, an incremental establish causes the target (R2) device to be incrementally synchronized and established as a Symmetrix mirrored media. (The devices must have been previously paired.) This is the same as an establish operation except that an incremental establish is much faster. This is accomplished by copying only the differences or new storage data from the source (R1) device to the target (R2) device. Any changed tracks on the device are overwritten by the data on the corresponding tracks from the source (R1) device. Incremental Restore A BCV or SRDF control operation. In BCV control operations, an incremental restore is a control operation that reassigns a BCV device as the next available mirror of the standard device in the pair. However, the standard devices are updated with only the data that was written to the BCV device during the time of the original pair split, and the data that was written to the standard device during the split is overwritten with data from the BCV mirror. In SRDF control operations, an incremental restore is a control operation that reassigns a target (R2) device as the next available mirror of the source (R1) device in the pair. The source (R1) devices are updated with only the data that was written to the target (R2) device during the time of the original pair split, and the data that was written to the source (R1) device during the split is overwritten with data from the target (R2) mirror. Invalid Tracks Number of tracks of data that are not in sync between two or more mirrors (local or remote). Action that makes all tracks invalid for a target or source (R1) device. An addressable input/output unit, such as a disk device.
Invalidate I/O Device
K
Kilobyte (K) 1024 bytes.
g-5
Glossary
L
Local Device A Symmetrix device that has a direct I/O channel connection to your host. The logical device name (LdevName/ld) is assigned to a device when it is added to a device group (for example, DEV003 or BCV001).
Logical Device Name
M
Master Unit In an SRDF configuration, it is the primary data storage subsystem. It initiates many of the SRDF synchronization activities. An SRDF configuration must have at least one master unit and one slave unit. See also Slave Unit. The disk surface on which data is stored. 106 bytes. A concatenated group of adjacent Symmetrix devices that appear as one target on the SCSI bus. The Symmetrix maintains two or more identical copies of a set of data on separate disks. Each copy automatically updates during a write operation. If one disk device fails, the Symmetrix automatically uses one of the other copies from another disk drive. A device comprised of two hyper disks (hyper-volumes) with all data recorded twice, once on each disk drive.
Media Megabyte (MB) Meta Device
Mirroring
Mirrored Pair
P
Parallel Channel Director The parallel channel director (PCD) or channel adapter (CA) in the Symmetrix subsystem that interfaces between mainframe host bus & tag channels and data storage. It transfers data between the channel and cache. The physical device name (PdevName/pd) or host name which is referenced in a command or function argument, or shown in a display (such as /dev/rdsk/c2t0d2s2). The process of moving data from a track on the disk device to cache. See also Stage.
Physical Device Name
Promotion
g-6
Glossary
R
R1 R2 RA RA Groups RAID RDF1/RDF2 See Source Device. See Target Device. RLD Adapter. See Remote Link Director. RA groups in an SRDF. See RDF Groups. Redundant Array of Independent Disks. A type of SRDF device group. Only RDF devices can be assigned to an RDF group. An RDF1 group type contains source (R1) devices and an RDF2 group type contains target (R2) devices. RDF groups (also known as RA groups) are configured and assigned RDF group numbers (1 to 16) by the Symmetrix microcode. An RA or RF director and any one storage device in the SRDF can belong to only one RDF group. Typically there are two or more RA/RF directors per RDF group. Data requested by the read operation is in cache. Percentage of read hits out of all read requests. Data requested by the read operation is not in cache. The Remote Link Director (RLD) is a serial channel director, which is microcode-configured as the link between the two Symmetrix units in a Symmetrix Remote Data Facility (SRDF) configuration. A BCV or SRDF control operation. In BCV control operations, a restore copies a full BCV mirror back to the standard device in the pair and reassigns the BCV device as the next available mirror to the standard device. In SRDF control operations, a restore copies the full target (R2) mirror back to the source (R1) mirror in the pair and reassigns the target (R2) device as the next available mirror to the source (R1) device. See Incremental Restore. RLD Remote Link Director. See Remote Link Director
RDF Groups
Read Hit Read Hit Ratio Read Miss Remote Link Director
Restore
g-7
Glossary
S
SA SCSI Adapter. See Fast-Wide SCSI Channel Director and Ultra SCSI Channel Director. The hexadecimal value that uniquely defines a physical I/O device on a SCSI channel path. A SCSI address consists of a Target ID and a Logical Unit Number (LUN). An SRDF mode of operation that provides an asynchronous mode of operation. Applications are notified that an I/O (or I/O chain) is complete once the data is in the cache of the local Symmetrix unit. Any new data is then written to cache in the remote Symmetrix unit. The remote Symmetrix unit acknowledges receipt of the data once it is secure in its cache. If source tracks are pending transfer to a target (R2) device, and a second write is attempted to the source (R1) device, the Symmetrix will disconnect (non-immediate retry request), and wait for the pending track to transfer to the remote Symmetrix unit. The ESCON adapter (EA) in the Symmetrix subsystem that interfaces between Symmetrix serial channels (ESCON) and data storage. It transfers data between the channel and cache. In an SRDF configuration, this subsystem maintains synchronization with the devices it is paired with in the master unit. It can serve as a master unit during disaster recovery. An SRDF configuration must have at least one master unit and one slave unit. See also Master Unit. A BCV or SRDF control operation. A BCV control operation that removes the BCV mirrored device from the existing device pair and assigns the mirrored device back to its original device address. The split causes the BCV device to provide an additional standard device copy to the host. An SRDF control operation that removes the target (R2) mirrored device from the existing device pair and assigns the target (R2) device back to its original device address. The split causes the target (R2) device to provide an additional copy to the host. Source (R1) Device A Symmetrix source (R1) device that is participating in SRDF operations with a target (R2) device. All writes to this device are mirrored to a target (R2) device in a remote Symmetrix unit. An R1 device must be assigned to an RDF1 group type (see RDF1).
SCSI Address
Semi-synchronous Mode
Serial Channel Director
Slave Unit
Split
g-8
Glossary
SRDF
Symmetrix Remote Data Facility. SRDF consists of the microcode and hardware required to support Symmetrix remote mirroring. ESCON fiber optic connections and channels between the two Symmetrix units. A minimum of two to a maximum of eight links can exist between the two units. A Symmetrix device configured as the normal data storage source within a desired protected environment (such as RAID, SRDF, BCV). The process of writing data from a disk device to cache. See also Promotion, Destage. The component in the Symmetrix subsystem that connects Symmetrix to the host channels. It performs channel commands and communicates with the disk adapters and cache. A user-addressable unit of storage. In the Symmetrix subsystem, the user can define multiple devices (hyper-volumes) on a single physical disk drive. A Symmetrix-assigned hexadecimal number (SymDevName) of a physical device. A unique 12-character Symmetrix ID (SymmID/sid) assigned to each Symmetrix unit (such as AB0010020064). An SRDF mode of operation that ensures 100% synchronized mirroring between the two Symmetrix units. Applications are notified that an I/O (or I/O chain) is complete when the remote Symmetrix unit acknowledges that the data has been secured in its cache.
SRDF Link
Standard Device
Stage
Storage Control
Symmetrix Device
Symmetrix Device Name Symmetrix ID
Synchronous Mode
T
Target (R2) Device A Symmetrix target (R2) device that is participating in SRDF operations with a source (R1) device. It resides in the remote Symmetrix unit. It is paired with a source (R1) device in the local Symmetrix unit and receives all write data from its mirrored pair. This device is not accessed by user applications during normal I/O operations. An R2 device must be assigned to an RDF2 group type (see RDF2). Data transfer rate of a component in the host or Symmetrix complex.
g-9
Throughput
Glossary
TimeFinder
A Business Continuance solution which allows customers to use special devices (BCVs) that contain copies of Symmetrix devices while the standard devices are online for regular host operations.
U
Ultra SCSI Channel Director The component in the Symmetrix subsystem that interfaces between host Ultra SCSI channels and data storage. It transfers data between the channel and cache.
V
Visible Refers to the current context of the host connection to a Symmetrix device. A device is visible to a host when a SCSI bus connection exists and the Symmetrix host database has been updated to include that device (using the SYMCLI discover option of the symcfg command). A general term referring to a storage device. In the Symmetrix subsystem, a volume corresponds to single device visible to the host.
Volume
W
Write Hit Write Miss There is room in cache for the data presented by the write operation. There is no room in cache for the data presented by the write operation. Symmetrix will disconnect from the channel and reconnect when space is available. Percentage of write requests out of all I/Os.
Write Ratio
g-10
Sales and Service Locations
Corporate Headquarters
EMC Corporation Hopkinton, Massachusetts 01748-9103 U.S.A. 508-435-1000 1-800-424-EMC2 EMC Japan K.K. P.O. Box 323 Shinjuku-Mitsui Bldg., 55 1-1, Nishi-Shinjuku 2-chome Shinjuku-ku Tokyo 163-0466 JAPAN Tel: 81-3-3345-3211 Fax: 81-3-3345-3221 Atlanta, GA 404-705-4750 Baltimore, MD 410-850-4324 Bellevue, WA 425-201-6400 Bethesda, MD 301-530-0091 Boston, MA 617-449-8100 Charlotte, NC 704-521-9773 Chicago, IL 708-390-8800 Cincinnati, OH 513-745-0300 Cleveland, OH 216-573-1162 Columbus, OH 614-436-3900 Dallas, TX 972-233-5676 Denver, CO 303-294-9966 Farmington Hills, Ml 313-553-4810 Ft. Lauderdale, FL 305-776-3622 Greensboro, NC 910-665-1077
s-1
Asia Pacific Headquarters
North American Sales and Service Locations
Houston, TX 713-621-9800 Indianapolis, IN 317-577-9766 Inglewood, CA 310-364-1222 Irvine, CA 714-833-1442 Lenexa, KS 913-469-9292 Long Island, NY 516-393-5045 Minneapolis, MN 612-835-1994 Montreal, Quebec 514-856-6166 Nashville, TN 615-781-4394 New York City, NY 212-564-6866 Ottawa, Ontario 613-233-0111 Orlando, FL 407-855-4087 Phoenix, AZ 602-955-0702 Philadelphia, PA 610-834-7740 Pittsburgh, PA 412-922-5222 Portland, OR 503-293-8450 Raleigh, NC 919-420-0405 Rochester, NY 716-387-0970 Salt Lake City, UT 801-532-1454 San Diego, CA 619-576-1880 San Francisco, CA 415-871-1970 Southington, CT 860-620-6730 Springfield, NJ 201-467-7979 St. Louis, MO 314-469-9005 Tampa, FL 813-282-0274 Toronto, Ontario 905-206-1580 Tulsa, OK 918-663-2255 Vancouver, BC 604-270-1657 Vienna, VA 703-893-8400 International Sales Locations Berlin, Germany (49) 30 25 49 31 86 Bologna, Italy (39) 51 522579 Brescia, Italy (39) 30 2421791 Brussels, Belgium (32) 2 725 74 25 Cape Town, South Africa (27) 21 686 1430 Dublin, Ireland (353) 1 475 4172 Durban, South Africa (27) 31 83 6611 Dusseldorf, Germany (49) 2131 9191 0 Frankfurt, Germany (49) 6196 4 72 80 Hamburg, Germany (49) 4069 69 610 Hong Kong, Taikooshing (852) 2839 9600 Johannesburg, South Africa (27) 11 807 5300 Leatherhead, Surrey, UK (44) 1372 36 0000
s-2
Lyon, France (33) 7 860 1330 Marseille, France (33) 4292 2549 Melbourne, Australia (61) 3 653 9519 Milan, Italy (39) 02 409081 Munich, Germany (49) 89 14 31 320 Nagoya, Japan (81) 52 223 1900 Newton Le Willows, Merseyside, UK (44) 1942 275 511 Nieuwegein, Netherlands (31) 03 6055777 Nuernberg, Germany (49) 911 2379260 Osaka, Japan (81) 6 373 8300 Padua, Italy (39) 49 8235853 Paris, France (33) 1 3082 5100 Pretoria, South Africa (27) 12 663 6635 Rome, Italy (39) 06 8552116 Schlieren, Switzerland (411) 743 4949 Seoul, Korea (82) 2 539 4455 Singapore (65) 338 9265 Stuttgart, Germany (49) 7152 979340 Sydney, Australia (61) 2 922 7888 Toulouse, France (33) 6131 6262 Turin, Italy (39) 11 746527 Vienna, Austria (43) 1 599 99 627
s-3
s-4
Index
Symbols
2-63
E
Establishing SRDF pairs 2-11, 2-16
A
Adaptive Copy-Disk 2-47
F
Fabric 2-5, 2-59 Failback 2-24 Failover 2-23 Force option 2-54 Freezing databases 2-15 Front-end director 1-6
B
BCV devices 1-9 remote 2-60 Business Continuance 1-9 Business continuance operations 1-9
G
Gatekeeper devices 1-9
C
Cache memory 1-6 Commands multi-hop operations 2-63 Compatibility Mode B-3 Composite operations 2-10 Consistency groups 2-66 to 2-69 Conventions xiv
H
Hot backup 2-15 Hyper 1-7 Hyper-volume 1-7
I
ICDA 1-5 Invalid tracks threshold 2-47
D
DA 1-7 Databases I/O controls 2-15 Device groups definition of 1-7 Disk director 1-7 Domino Effect 2-46
J
JRNL0 attribute 2-45
L
Listing RDF devices 2-6 Listing RDF groups 2-6
i-1
Index
Logical volume attributes Adaptive Copy 2-47 Domino Effect 2-46 JRNL0 2-45
M
Merging track tables 2-39 Multi-hop control operations 2-63
O
Offline option 2-55 Options to symrdf 2-52, 2-53, 2-72 OSM Compatibility B-3
P
Pinging SRDF devices 2-8
Q
Query SRDF devices 2-8
R
RA groups 2-58 Remote BCV devices 2-60 Remote operations 2-60 Restoring SRDF devices 2-18, 2-20
S
Setting SRDF modes 2-45 Singular control operations 2-29 Skew parameter 2-47 Source (R1) device 1-2, 2-2 Splitting SRDF pairs 2-13 SRDF 2-2 definition of 1-2 operations 2-9 SRDF configurations bi-directional 2-2 uni-directional 2-2
SRDF control operations failback 2-24 failover 2-22 full establish 2-11 full restore 2-18 incremental establish 2-16 incremental restore 2-20 invalidate R1 mirror 2-36 invalidate R2 mirror 2-36 merge track tables 2-39 not ready R1 mirror 2-38 not ready R2 mirror 2-38 read/write enable R1 mirror 2-32 read/write enable target (R2) device 2-32 ready R1 mirror 2-37 ready R2 mirror 2-37 refresh R1 mirror 2-34 refresh R2 mirror 2-35 resume 2-31 split 2-13 suspend 2-30 update R1 mirror 2-26 write disable source (R1) devices 2-33 write disable target (R2) device 2-34 SRDF devices 1-2 listing 2-6 pinging 2-8 querying 2-8 viewing 2-6 SRDF implementations Campus Solution 2-4 Extended Distance Solution 2-4 SRDF modes 2-45 adaptive copy 2-47 adaptive copy change skew 2-48 adaptive copy disk 2-47 domino effect 2-46 semi synchronous 2-45 synchronous 2-45 SRDF states verify 2-8 Switched RDF 2-5 topology 2-59 SYMCLI 1-2
i-2
Index
SYMCLI commands symioctl 2-15, A-10 symrdf 1-3, 2-11, 2-13, 2-16, 2-18, 2-20, 2-22, 2-24, 2-26, 2-30, 2-31, 2-32, 2-34, 2-35, 2-36, 2-37, 2-38, 2-39, 2-42 Symmetrix 1-5 Symmetrix Command Line Interface 1-2 Symmetrix devices major components 1-5 Symmetrix Remote Data Facility 2-2 symrdf command options all 2-53 bcv 2-53 brbcv 2-54 bypass 2-54 consistency state 2-55 count 2-54 enabled consistency state 2-56 failed over state 2-56 force 2-54 help 2-55 interval 2-54 list 2-7 no echo 2-55 no prompt 2-55 offline 2-55 Partitioned state 2-56 R1 2-55 R2 2-55 rbcv 2-54 SCSI reservations 2-55 SID 2-56 split state 2-56 suspended and link offline state 2-56 suspended state 2-56 synched state 2-56 until 2-57 updated state 2-56 UpdateInProg state 2-57 valid state 2-57 verbose 2-57
T
Target (R2) device 1-2, 2-2 Thawing databases 2-15 Track tables 2-39
U
Until option 2-28 Updates continuous 2-28 Updating mirror 2-26
i-3
Index
i-4

SRDF 4.2

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SRDF 4.2

Загружено:

Авторское право:

Доступные форматы

EMC Enterprise Storage

EMC Solutions Enabler SYMCLI SRDF Component

Copyright 2000 EMC Corporation. All rights reserved.

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

Preface........................................................................................................................... xiii Chapter 1 Overview

SRDF Control Operations

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

SYMCLI SRDF Command Reference

OSM Compatibility Mode

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

Conventions Used in this Manual

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

Where to Get Help

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

SYMCLI SRDF Component

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

SYMCLI SRDF Component

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

Symmetrix and SYMCLI Fundamentals

Symmetrix and SYMCLI Fundamentals

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

Symmetrix and SYMCLI Fundamentals

Four Hyper Volumes

Storage Device Names Using SYMCLI

Symmetrix Device Configuration

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

Symmetrix and SYMCLI Fundamentals

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

Consistency Groups Cope with RDF Link Failure

Symmetrix and SYMCLI Fundamentals

All Data Propagation is Suspended upon any Link Failure

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

SRDF Control Operations

SRDF Control Operations

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

SRDF Control Operations

SRDF Control Operations

SRDF Extended Distance Solution

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

SRDF Control Operations

Switched RDF Switched (Fabric) RDF Links Site C Host

Switched (Fabric) RDF Topology

SRDF Control Operations

Finding SRDF Devices

RDF Device Groups

If the type of group is RDF1, or RDF2, the group is an SRDF group.

Listing RDF Devices

EMC Solutions Enabler SYMCLI SRDF Component Product Guide

SRDF Control Operations

Finding SRDF Devices

SRDF Control Operations

Ping SRDF Devices

Verify SRDF States