SRDF Product Guide (WWW - Mianfeiwendang.com)

文档下载免费文档下载
http://www.mianfeiwendang.com/
　　
本文档下载自文档下载网，内容可能不完整，您可以点击以下网址继续阅读或下载：
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8
srdf product guide
EMC® Symmetrix® Remote

Facility (SRDF®)
/N 300-001-165
A09
Corporation
Headquarters:
, MA 01748-9103
-508-435-1000
://www.mianfeiwendang.com
© 2009 EMC Corporation. All rights reserved.
November, 2009
believes the information in this publication is accurate as of its publication
date. The information is subject to change without notice.
INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN
THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
, copying, and distribution of any EMC software described in this publication
requires an applicable software license.
the most up-to-date regulatory document for your product line, go to the
Techttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8hnical
Documentation and Advisories section on EMC Powerlink.
the most up-to-date listing of EMC product names, see EMC Corporation Trademarks
on http://www.mianfeiwendang.com.
other trademarks used herein are the property of their respective owners.
EMC Symmetrix Remote Data Facility (SRDF) Product Guide

1ContentsSRDF Technical Concepts

.............16 interfamily connectivity
support......................................................... 17
and controlling
SRDF.................................................................. 17
documentation...................................................................
................. 17
SRDF family
products...................http://www.mianfeiwendang.com/doc/fbe03131210633d18de
37bd8................................................................ 18
of SRDF
options.........................................................................
........... 19
SRDF products and options.......................................................
21
/
Synchronous.....................................................................
.................... 21
/
Asynchronous....................................................................
................... 21
/Data
Mobility........................................................................
................ 21
/Automated
Replication.....................................................................
.. 22
/
Star............................................................................
.............................. 22
/Consistency
Groups......................................http://www.mianfeiwendang.com/doc/fb
e03131210633d18de37bd8....................................... 22
/Cluster
Enabler.........................................................................
............ 22
Dispersed Disaster Restart.................................................. 23
Management
tools...........................................................................
............ 24
Host Component for
z/OS................................................................... 24
Enabler SRDF
component.............................................................. 24
types...........................................................................
.................................. 25
devices.........................................................................
....................... 25
devices.........................................................................
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8................... 25
role devices
(R21)...........................................................................
......... 26
SRDF
devices.........................................................................
........... 27
Compatible
Peer............................................................................
......... 28
device
considerations..................................................................
....... 30
states..........................................................................
.................................. 32
device states (Symmetrix
view)........................................................... 32
device states (host
view)....................................................................... 33
to the
host ...........................................................................
.http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8...... 34
and
links...........................................................................
.......................... 36
types...........................................................................
............................ 36
................................................................................
................................... 37
Symmetrix Remote Data Facility (SRDF) Product Guide3
protocols and
topologies......................................................................
. 39
Channel.........................................................................
............................ 39
Ethernet
(GigE)..........................................................................
.......... 41
................................................................................
...................http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8...
.......... 42
of
operation.......................................................................
.......................... 43
modes...........................................................................
....................... 43
modes...........................................................................
................... 46
2SRDF Operations
operations......................................................................
................................ 50
write
I/Os............................................................................
..................... 50
I/Os in an ESCON bidirectional configuration................................. 50
/S concurrent write I/Os (for FBA
devices)....................................... 50
I/Os to R21
devices..................................................http://www.mianfeiwenda
ng.com/doc/fbe03131210633d18de37bd8.............................. 50
I/Os and software
compression........................................................... 51
operations......................................................................
................................. 52
I/Os to the primary
device.................................................................... 52
I/O to the secondary
device.................................................................. 52
I/Os to diskless R21
devices.................................................................. 52
I/Os and software
compression........................................................... 52
operations......................................................................
......................... 53
to the secondary Symmetrix system...............................................
53
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8to the primary
Symmetrix system.................................................. 53
for a large number of invalid
tracks............................................. 53
remote command
support.................................................................... 53
Multi-hop
operations......................................................................
....... 54
Migrations......................................................................
......................... 54
3SRDF Multisite Operations
operations......................................................................
...................... 56
SRDF/S with
SRDF/A................................................................ 56
migration with Concurrent
SRDF...................................................... 57
mirror SRDF
ECA..................http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8.
.................................................................. 57
................................................................................
............................... 57
operations......................................................................
......................... 58
up a Cascaded SRDF
relationship..................................................... 58
SRDF
modes...........................................................................
.......... 59
................................................................................
............................... 59
Distance
Protection......................................................................
......... 60
................................................................................
............................... 60
site
conhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8figurations........
................................................................................
. 61
................................................................................
............................... 62
4SRDF Consistency Groups
groups..........................................................................
....................... 64
write
operations......................................................................
..... 64
data
consistency.....................................................................
.......... 64
5SRDF/Synchronous Operations
/S
overview........................................................................
........................... 68
................................................................................
............................... 68
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nts and
limitations.....................................................................
.... 68

6
7
8
9ContentsSRDF/Asynchronous Operations SRDF/A
overview........................................................................
.......................... 70Single session
mode............................................................................
............. 70Multi-Session Consistency (MSC)
mode....................................................... 70Reserve
Capacity........................................................................
...................... 70Write
Folding.........................................................................
............................ 71Write
Pacing..........................................................................
............................ 71Tolerance
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8mode..................
...............................................................................
72SRDF/A
benefits........................................................................
....................... 72Requirements and
limitations.....................................................................
.... 72Development and
availability....................................................................
.... 72 Single session
mode............................................................................
.................... 75Dependent-write
consistency.....................................................................
.... 75Single session
states..........................................................................
................ 76Single session state
transitions.....................................................................
... 76Delta set
switching........................................................http://www.mian
feiwendang.com/doc/fbe03131210633d18de37bd8...................................
77Session mode
switching.......................................................................
............ 79Recovery
scenarios.......................................................................
.................... 80 Multi-Session Consistency (MSC)
mode............................................................. 83MSC mode
dependent-write consistency.....................................................
83Entering SRDF/A multi-session
consistency............................................... 84Performing an
SRDF/A MSC consistent cycle switch................................ 85Multi-
Session Consistency (MSC) mode delta set switching..................... 86Multi-
Session Consistency (MSC) session cleanup process.......................
91Consistency exempt
option..........................................................................
... 92SRDF/Star Operations SRDF/Star
overview............http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8..
................................................................................
94Benefits......................................................................
.........................................
95Requirements..................................................................
.................................. 95 How SRDF/Star
works...........................................................................
............... 96SRDF/Star control for
mainframe..................................................................
96SRDF/Star control for open
systems............................................................. 97
Concurrent
SRDF/Star.......................................................................
.................... 98Concurrent SRDF/Star with R22
devices..................................................... 98 Cascaded
SRDF/Star.......................................................................
...........http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8..........
100Cascaded SRDF/Star with R22
devices...................................................... 101 SRDF/EDP and
SRDF/Star.......................................................................
.......... 102SRDF/Data Mobility SRDF/DM
overview........................................................................
....................
106Benefits.....................................................................
........................................
106Limitations..................................................................
..................................... 107SRDF/Automated Replication
/AR
overview........................................................................
..................... 110
................................................................................
............................. 110
..............................................................http://www.mianfei
wendang.com/doc/fbe03131210633d18de37bd8........................................
.. 111
/AR with TimeFinder and other SRDF solutions............................. 111
10SRDF Integration
continuance.....................................................................
....................... 114
business
continuance.....................................................................
...... 114
and TimeFinder business
continuance.............................................. 115
TimeFinder BCVs with primary devices..........................................
116
TimeFinder BCVs with secondary devices...................................... 116
clusters........................................................................
................................. 118
/Cluster Enabler
(SRDF/CE).http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8............
................................................. 118
/Star with Veritas Cluster
Server........................................................ 119
AutoSwap........................................................................
....................... 119
MetroCluster and Continental
Cluster.................................................. 120
with Solaris Cluster Campus Topology............................................
120
with Solaris Cluster Geographic
Edition.......................................... 121
Dispersed Disaster
Restart....................................................... 122
................................................................................
..................... 123
................................................................................
...........................http://www.mianfeiwendang.com/doc/fbe03131210633d18de
37bd8.. 123
................................................................................
....................... 123
and virtualization
environments............................................................. 124
and Virtual
Provisioning....................................................................
. 124
and VMware Site Recovery Manager...............................................
124

PageSRhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8DF basic
configuration...................................................................
.................................. 16SRDF family of
products........................................................................
.............................. 18SRDF options
overview........................................................................
................................ 20R22 device with Cascaded
SRDF/Star.......................................................................
........ 26R22 device with Concurrent
SRDF/Star.......................................................................
..... 26Diskless R21 device (DL
Dev)............................................................................
................. 27SRDF device
states..........................................................................
...................................... 32Moving SRDF devices between SRDF
groups..........................http://www.mianfeiwendang.com/doc/fbe03131210633
d18de37bd8........................................ 37Switched SRDF with
multiple primary and secondary devices....................................
39Switched SRDF over Fibre Channel with Enginuity
5x67.............................................. 40Switched and Concurrent
SRDF over Fibre Channel......................................................
41Switched SRDF over
GigE............................................................................
....................... 42Basic metropolitan area network
configuration...............................................................
44Basic wide area network
configuration...................................................................
.......... 44SRDF/A basic
configuration...................................................................
............................ 45Combined basic MAN/WAN
configuration...................................................................
. 45Basichttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 SRDF Multi-
hop
configuration...................................................................
.............. 54Concurrent SRDF
configuration...................................................................
...................... 56Example of two-mirror SRDF
ECA.............................................................................
....... 57Cascaded SRDF
configuration...................................................................
......................... 58Establishing a Cascaded SRDF
configuration...................................................................
58SRDF/EDP basic
configuration...................................................................
....................... 60Four-site disaster recovery (old
configuration)................................................................
61Four-site disaster recovery (new
configuration)..............................................................
62Prhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8imary and
secondary
relationships...................................................................
............. 64Failed links between primary system 2 and secondary
system1................................... 65Primary systems 1, 2, and 3 in a
consistency group.........................................................
65Failed link between primary system 2 and secondary system
1.................................... 65Basic SRDF/S
configuration...................................................................
............................. 68SRDF/A delta sets and their
relationships...................................................................
..... 75Delta set
switching.......................................................................
......................................... 79SRDF/A MSC delta sets and their
relationships..............................................................
84SRDF/A MSC allowed state
trahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nsitions...........
................................................................. 85SRDF/A MSC
capture delta set collects application write
I/O..................................... 86SRDF/A MSC primary Symmetrix system
transmit delta set is emptied.................... 87SRDF/A MSC primary
Symmetrix system halts the SRDF transfer............................. 87SRDF/A
MSC secondary apply delta set restore
complete............................................ 88SRDF/A MSC primary
Symmetrix system cycle switch while I/O is deferred.......... 88SRDF/A MSC I/O
is released and a new capture delta set continues to accept host
/
O .............................................................................
.......................................................... 89
SRDF/A MSC secondary Symmetrix system cycle

switch..................http://www.mianfeiwendang.com/doc/fbe03131210633d18de37b
d8........................... 89
SRDF/A MSC secondary Symmetrix system new receive delta set is

available......... 90
SRDF/A MSC primary Symmetrix systems begin SRDF

transfer................................. 9043SRDF/A MSC secondary Symmetrix
system begins the apply delta set restore
process ........................................................................
............................................................ 91
Concurrent SRDF configured for SRDF/Star

support..................................................... 94
Concurrent SRDF/Star
configuration...................................................................
............. 98
Concurrent R22 SRDF/Star

configuration...................................................................
...... 9947Cascaded SRDF/Star
configuration...................................................................
...........http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8....
10048Cascaded R22 SRDF/Star
configuration...................................................................
....... 10149Cascaded SRDF/Star EDP (diskless) configuration with an R2
site............................ 10250SRDF/DM adaptive copy
mode............................................................................
............ 10651SRDF/AR single-hop data
flow............................................................................
............ 11052SRDF/AR Multi-hop data
flow............................................................................
............. 11053SRDF business
continuance.....................................................................
.......................... 11454Primary-to-secondary
resynchronization...............................................................
......... 11455Secondary-to-primary
resynchronization...............................................................
....http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8..... 11556SRDF
single-hop configuration (BCV functioning as a primary SRDF device).........
11657SRDF/CE two-node two-cluster
configuration..............................................................
11958AutoSwap
processing......................................................................
................................... 12059Three-site Concurrent SRDF/Star with
GDDR............................................................... 12260EMC
SRDF and VMware
SRM.............................................................................
............. 125

PageSymmetrix hardware model

numbers.........................................................................
...... 17Local protection types compatible with SRDF remote
mirroring..................................
25http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Thin SRDF devices
with TimeFinder/Clone and TimeFinder/Snap............................ 31Primary
(R1) device - accessibility to the
host..................................................................
34Secondary (R2) device - accessibility to the
host.............................................................. 34Device
support for
SRDF............................................................................
......................... 36SRDF/A development and availability
summary........................................................... 73
part of an effort to improve and enhance the performance and capabilities of its
product lines, EMC periodically releases revisions of its hardware and software.
Therefore, some functions described in this document
mhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ay not be supported
by all versions of the software or hardware currently in use. For the most up-
to-date information about product features, refer to your product release notes.
If a product does not function properly or does not function as described in
this document, please contact your EMC representative. Audience This guide
provides an overview of SRDF and SRDF family of product offerings for users
requiring a basic knowledge of SRDF concepts and operation. Detailed SRDF
installation and configuration information is available in the documents listed
in the“Related documentation” on page 17. Related documents
include:◆◆◆◆◆◆◆
documentation
Networked Storage Topology Guide EMC SRDF Connectivity Guide EMC Symmetrix
(Model or Series) Product Guide EMC Solutions Enabler Symmetrix SRDF Family CLI
Product Guide EMC SRDF Host Component for z/OS Product Guide EMC SRDF Controls
for TPF Product Guide
Geographhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ically
Dispersed Disaster Restart (GDDR) Product Guide
additional information on all Symmetrix system related publications, contact
your EMC Sales Representative or refer to the EMC Powerlink website
at:http://www.mianfeiwendang.com
used in this guide
uses the following conventions for special notices.Note: A note presents
information that is important, but not hazard related.
!
A caution contains information essential to avoid data loss or damage to the
system or equipment. An important notice contains information essential to
software or hardware operation.
Symmetrix Remote Data Facility (SRDF) Product Guide
[此处图片未下载成功]
Preface
A warning contains information essential to avoid a hazard that can cause severe
personal injury, death, or substantial propert
damage if you ignore the warning. DANGER A danger notice
chttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ontains information
essential to avoid a hazard that will cause severe personal injury, death, or
substantial property damage if you ignore the message. Typographical conventions
EMC uses the following type style conventions in this guide. Normal fontIn
running text: Interface elements (for example, button names, dialog box names)
outside of procedures Items that user selects outside of procedures Java
classes and interface names Names of resources, attributes, pools, Boolean
expressions, buttons, DQL statements, keywords, clauses, environment variables,
filenames, functions, menu names, utilities Pathnames, URLs, filenames,
directory names, computer names, links, groups, service keys, file systems,
environment variables, notifications In procedures: Names of dialog boxes,
buttons, icons, menus, fields Selections from the user interface, including
menu items and field entries Key names Window names In running text:
Cohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8mmand names,
daemons, options, programs, processes, notifications, system calls, man pages,
services, applications, utilities, kernels Used for: Full publications titles
referenced in text Unique word usage in text Used for: System output
Filenames Complete paths Command-line entries URLs Used for: User entry
Options in command-line syntax Used for: Arguments used in examples of command-
line syntax Variables in examples of screen or file output Variables in
pathnames Angle brackets enclose parameter or variable values supplied by the
user Square brackets enclose optional values Vertical bar indicates alternate
selections - the bar means“or” Braces indicate content that you must specify
(that is, x or y or z) Ellipses indicate nonessential information omitted from
the example
, bold
, italic
<>[]| ...
Symmetrix Remhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ote Data

Facility (SRDF) Product Guide
Preface
to get helpEMC support, product, and licensing information can be obtained as
follows.
information —For documentation, release notes, software updates, or for
about EMC products, licensing, and service, go to the EMC Powerlink
(registration required) at:
support —For technical support, go to EMC Powerlink. To open a case,
must be a customer. Information about your site configuration and the
under which the problem occurred is required.
commentsYour suggestions will help us continue to improve the accuracy,
organization, and
quality of the user publications. Please send your opinion of this document to:
@http://www.mianfeiwendang.com
you have issues,
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8comments, or questions
about specific information or procedures,
include the title and, if available, the part number, the revision (for example,
), the page numbers, and any other details that will help us locate the subject
you
addressing.
Preface
1
Technical
chapter introduces SRDF, explains basic concepts, and provides example

. Topics include:
◆Overview......................................................................
.................................................
◆Base SRDF family

products........................................................................
................ 18 16
◆Overview of SRDF
options...................................................http://www.mianfeiwend
ang.com/doc/fbe03131210633d18de37bd8...................................... 19
◆Understanding SRDF products and

options............................................................ 21
◆SRDF Management
tools...........................................................................
.................. 24
◆Device
types...........................................................................
....................................... 25
◆Device
states..........................................................................
........................................ 32
◆Groups and
links...........................................................................
............................... 36
◆Network protocols and

topologies......................................................................
...... 39
◆Modes of
operation.......................................................................
...............................
43://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8parTechnical Concepts15
SRDF Technical Concepts
: The following terms are used synonymously throughout SRDF documentation:

Primary
, R1, or source device; secondary device, R2, or target device; and tertiary or
remote
.
EMC® Symmetrix® Remote Data Facility (SRDF®) software family of
products
remote mirroring and offers various levels of Symmetrix-based business
and disaster recovery solutions. The SRDF products offer the capability
maintain multiple host-independent copies of data. The Symmetrix systems can be
the same room, in different buildings within the same campus, or hundreds to
of kilometers apart. Figure1 on page16 shows an example of an SRDF
.
maintaining copies of data in different physical locations, SRDF enables you
to://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8arthe following
operations with minimal impact on normal business
:
◆
◆Disaster restartDisaster restart testingRecovery from planned outagesRemote
backupData center migrationData replication and mobility.
ASite B
pair
(R1)
/O TransferHost(R2)SRDF pair
(R2)
/O Transfer(R1)Symmetrix
SRDF pair
SRDF basic configuration

interfamily
SRDF solution can use different Symmetrix hardware platforms/models. Details

about SRDF interfamily connectivity support are provided at:
http://www.mianfeiwendang.com
> Support > Technical Documentation and Advisories
&ghttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8t; Software ~ S ~
> SRDF Family > SRDF Interfamily Connectivity Support
on page17 lists Symmetrix hardware platforms that can be used in SRDF
.
Symmetrix hardware model numbers
xxx/5xxxTM Series
/5330 and 3630/5630
/5430, 3830/3832a/5830Symmetrix 8000TM Series82308430, 8530Symmetrix DMXTM

SeriesDMX800DMX800, DMX1000,
950, DMX-4 950
, DMX2000,
950, DMX-4 950
/5700 and 3930/59308730, 8830DMX3000

, DMX-4Symmetrix V-MaxTM SeriesN/AV-Max SEV-Max, V-Max SEV-MaxV-MaxCabinet
description1/2 bay1 bay2 bay3 bayUp to 11 bays
.The Symmetrix 3832 is a 3830 model with a split backplane.
and
SRDFAn EMC representative installs and initially configures SRDF at your site.
After SRDF is enabled, you can monitor and control its
ohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8peration by obtaining
the appropriate
ControlCenter®, Solutions Enabler, Symmetrix Management Console (SMC), or
Host Component software.
additional information on SRDF and all Symmetrix systems-related publications,
your EMC Sales Representative or refer to the EMC Powerlink website at:
◆
◆Related documentationEMC Networked Storage Topology GuideEMC SRDF Connectivity

GuideEMC Symmetrix (Model or Series) Product GuideEMC Solutions Enabler
Symmetrix SRDF Family CLI Product GuideSymmetrix Management Console (SMC) help
file informationEMC SRDF Host Component for z/OS Product GuideEMC SRDF Controls
for TPF Product GuideGeographically Dispersed Disaster Restart (GDDR) Product
GuideEMC Support Matrix
: For detailed information regarding solutions that involve
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8other qualified
vendors'
, consult the appropriate product specification manuals available from each
vendor,
ask your site representative to contact the appropriate EMC partner vendor or
EMC
Support/Engineering.

SRDF family productsThe SRDF family consists of the following base solutions:◆
◆
/Synchronous (SRDF/S)— High-performance, host-independent, real-time
synchronous remote replication from one Symmetrix system to one or more
Symmetrix systems. SRDF/Asynchronous (SRDF/A)— High-performance extended
distance asynchronous replication using a delta set architecture for optimal
bandwidth utilization and minimal host performance impact. SRDF/Data Mobility
(SRDF/DM)— Rapid transfer of data from primary volumes to secondary volumes
anywhere in the world, permitting information to be shared and
contenhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8t to be
distributed, or information consolidated for parallel processing activities.
SRDF/Extended Distance Protection (EDP)— Offers a long distance
recovery (DR) solution.
◆
2 on page 18 summarizes the SRDF family of products.
2
family of products

of SRDF options
are a number of additional options and features that can be added to the base
to solve specific service-level requirements. These include:
◆SRDF/Automated Replication (SRDF/AR) solutions for meeting very specific,

remote replication service-level requirements
/Star for advanced multisite failover with continuous protection
/Consistency Groups (SRDF/CG) for data consistency
/Cluster Enabler
(SRDF/CEhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8) for
integration with host-based clustering products such as SRDF/Star with Veritas
Cluster Server and Windows
Geographically Dispersed Disaster Restart (GDDR) for complete, automated
solutions for restarting mainframe operations after planned or
outages.◆◆◆◆
: For simplicity, this document uses the term SRDF to represent all EMC SRDF-
related
, including: SRDF/S, SRDF/AR (multi-hop and single-hop), SRDF/DM, SRDF/Star,
SRDF/CG, and so on.
SRDF family of products can also be used with the EMC TimeFinder® family of
products,
includes TimeFinder/Clone and TimeFinder/Snap. For simplicity, this document
uses
term TimeFinder to represent all EMC TimeFinder-related products.
on page20 shows and describes SRDF supported options.
of SRDF options19

3
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8RDF options overview

SRDF products and options
/Synchronous
/Asynchronous
/Data MobilityThis section describes the features and benefits of SRDF base
products and options. SRDF options provide additional features, and are added to
the base product to solve specific service-level requirements.Symmetrix Remote
Data Facility/Synchronous (SRDF/S) is a remote replication product that
maintains a real-time (synchronous) mirrored copy of data in physically
separated Symmetrix systems within an SRDF configuration. SRDF/S offers the
following major features and benefits:◆High data availability◆High
performance◆Flexible configurations◆Host and application software
transparency◆Automatic recovery from a failure◆Significantly reduced recovery
time after a
disastehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8r◆Reduced
backup and recovery costs◆Reduced disaster recovery complexity, planning, and
testingThe SRDF/S operation is transparent to the host operating system and host
applications. It does not require additional host software for duplicating data
on the participating Symmetrix units. SRDF/S offers greater flexibility through
additional modes of operation. “Modes of operation” on page43 and
“SRDF/Synchronous Operations” on page67 provide additional details.Beginning
with EMC Enginuity version 5670, Symmetrix systems support the asynchronous
replication product named SRDF/Asynchronous (SRDF/A). SRDF/A is a mode of remote
replication that allows you to asynchronously replicate data while maintaining a
dependent-write consistent copy of the data on the secondary (R2) devices at all
times. The dependent-write consistent point-in-time copy of the data at the
secondary side is typically only seconds behind the primary (R1) side.
SRDhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8F/A session data is
transferred to the secondary Symmetrix system in cycles, or delta sets,
eliminating the redundancy of multiple same-track changes being transferred over
the SRDF links, potentially reducing network bandwidth requirements. SRDF/A
provides a long-distance replication solution. This level of protection is
intended for customers who require minimal host application impact while
maintaining a dependent-write consistent, restartable image of their data at the
secondary site. In the event of a disaster at the primary (R1) site or if SRDF
links are lost during data transfer, a partial delta set of data can be
discarded, preserving dependent-write consistency on the secondary site within
no more than two SRDF/A cycles. “SRDF/Asynchronous Operations” on page69
provides additional details.SRDF/Data Mobility (SRDF/DM) is an SRDF product that
permits operation in
adaptive copy mode only and is designed for
dathttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8a replication or
migration
two or more Symmetrix systems. Adaptive copy mode enables applications
avoid propagation delays while data is transferred to the secondary site.
/DM transfers data from primary volumes to secondary volumes, permitting
to be shared, content to be distributed, and access to be local to
processing environments. SRDF/DM supports all Symmetrix hardware
and all Enginuity versions that support SRDF, and can be used for local or
transfers. “SRDF/Data Mobility” on page105 and “SRDF/Data Mobility” on
provides additional details.
SRDF products and options21

/Automated
/Automated Replication (SRDF/AR) is an automation solution that uses both SRDF
and TimeFinder to provide a periodic asynchronous replication of a
reshttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8tartable
image.
to traditional disaster recovery solutions with their long recovery time,
restart solutions using SRDF/AR provide remote restart with a shorter
time. SRDF/AR offers data protection with dependent-write consistency
a distance.
“SRDF/Automated Replication” on page109 and “SRDF and TimeFinder business

” on page115 provide additional details.
/StarAvailable at Enginuity version 5x71 and later, SRDF/Star provides advanced
business continuity protection. SRDF/Star offers the ability to differentially
and protect the data amongst surviving sites in a multisite disaster recovery
(DR) implementation.
the event of a primary site failure, SRDF/Star enables the surviving sites to
quickly
establish data, protect it using remote mirroring, and then just as
quhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ickly restore
primary site when conditions permit.
SRDF/Star solution uses different modes of operation (SRDF/A, SRDF/S)
participating sites. SRDF/Star enables enterprises to resynchronize their
/S and SRDF/A copies by replicating only the differences between the
—allowing for much faster resumption of protected services after a primary
failure. SRDF/Star can also be used with Cascaded and Extended Distance
configurations. “SRDF/Star Operations” on page93 provides additional
.
/Consistency
/Consistency Groups (CG) ensure the consistency of data remotely mirrored by the
SRDF operations in the event of a rolling disaster across multiple Symmetrix
or across multiple devices within a Symmetrix system. When SRDF/CG
any write I/O to a volume that cannot communicate with
ithttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8s remote mirror,
/CG suspends the remote mirroring for all volumes defined to the consistency
before completing the intercepted I/O and returning control to the application.
this way, SRDF/CG prevents dependent I/O from reaching its remote mirror in
case where a predecessor I/O only gets as far as the local mirror. “SRDF
Groups” on page63 provides additional details.
/Cluster Enabler (CE) for Microsoft Cluster Service (MSCS) is a software
for MSCS. SRDF/CE allows MSCS to operate across a single pair of
connected Symmetrix arrays in topographically distributed clusters. These
are referred to as SRDF/CE clusters. Using SRDF links, SRDF/CE expands
range of cluster storage and management capabilities while ensuring full
business
protection. “SRDF/Cluster Enabler (SRDF/CE)” on page118
phttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8rovides
details.SRDF/Cluster Enabler
Disaster
Geographically Dispersed Disaster Restart (GDDR) is a mainframe software product
that standardizes and automates the restart of business processing following
planned or unplanned outages including the total loss of a data center. GDDR
restarts remote host systems, applications, and storage.
supports both two-site and three-site SRDF configurations including
/Star and AutoSwap operations. “Geographically Dispersed Disaster Restart”
page122 provides additional details.
SRDF products and options23

Management tools
is managed with the following tools:
◆SRDF Host Component for z/OS

http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8— A z/OS subsystem
for controlling SRDF
and monitoring SRDF status by using commands executed from a host.
Solutions Enabler SYMCLI — A library of commands that are entered from a
command line or from a script.◆
Host
for z/OSEMC SRDF Host Component is a z/OS subsystem for controlling SRDF
processes and monitoring SRDF status by using commands executed from a host.
Users can
SRDF Host Component commands to both local and remote Symmetrix
. Commands destined for remote Symmetrix systems are transmitted through
Symmetrix systems to remote Symmetrix systems through SRDF links.
and status information can be viewed for each device on every
array containing SRDF devices.
interfaces to SRDF Host Component are provided through both the Time
Option (TSO), Interactive System
Produhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ctivity Facility
(ISPF), and batch
, as well as through the system console. An optional interface is provided
TimeFinder commands as well as SRDF commands to centralize commands for
replication products.
Host Component for z/OS is delivered with members of the Mainframe
product family. The Mainframe Enablers is a suite of components designed
monitor and manage your storage. By offering compatible components, this
packaging simplifies installation and maintenance. The Mainframe
suite includes the following components:
◆
◆SRDF Host Component for z/OSEMC ResourcePak® Base for z/OSConsistency

Groups for z/OSTimeFinder/Clone Mainframe Snap FacilityTimeFinder/Mirror for
z/OSTimeFinder Utility
EMC SRDF Host Component for z/OS Product Guide located on the EMC
Powerlhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ink
contains additional information.
Enabler
componentThe Solutions Enabler SYMCLI is a specialized library consisting of
commands that can be invoked from a host command line or within scripts. These
commands
control operations on devices and data objects within your managed storage
. The Solutions Enabler SRDF component extends the basic SYMCLI
set to include SRDF commands for performing control operations on SRDF
. This component provides all the commands to establish, manage and
SRDF operations.
component runs on many open systems servers and on mainframe servers that
Linux-based operating system partitions configured to them.
EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide contains
information.
EMC Symmetrix Remote Data Facility

(SRDFhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8) Product Guide

types
refers to Symmetrix devices (volumes) as primary (R1) and secondary (R2)
. Primary and secondary SRDF devices are basic SRDF device types. In
site configurations, such as Cascaded SRDF and SRDF/EDP, some SRDF
assume dual-roles.
devicesPrimary devices (R1, R11) contain data that is mirrored in a different
Symmetrix
. Updates to a primary device are automatically mirrored to a secondary
(R2, R22) in another Symmetrix system. A primary device also can be paired
a BCV to provide an additional working copy of the data at the same location.
being remotely mirrored in secondary devices, primary devices can also be
locally, using any of the local protection types listed in Table2 on page25.
Local protection types
compatihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ble with SRDF
remote mirroringa
type
(RAID 1) DescriptionProvides the highest level of performance and availability
for all mission-critical and
critical applications by maintaining a duplicate copy of a device on two
internally
disk drives.
a combination of RAID 1 and RAID 0 for open systems environments. Data can be
striped across SRDF logically mirrored pairs, or concatenated across multiple
SRDF
volume pairings (either SRDF pairings locally protected by supported internal
disk
methods)..
a combination of RAID 1 and RAID 0 for mainframe environments.
data and distributes parity blocks across all the disk drives in the RAID group.
Uses
parity and provides support for a single disk drive failure. RAID 5 is
configured in
(3 1) and (7 1)
groups.://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8rRAID 5, RAID 6
stripes data and distributes parity blocks across all the disk drives in the
group. RAID 6 uses both horizontal parity and diagonal parity. It provides
support for
than two disk drive failures. RAID 6 is configured in (6 2) and (14 2) groups.
is a local protection option that invokes a spare drive when a production drive
starts
. A spare drive is a physical drive, invisible to the host until automatically
invoked by the
utility. Depending on the Enginuity level, the sparing utility either:
Invokes a spare drive as an additional local mirror to the faulty drive to

maintain local
level until the faulty drive is replaced (dynamic sparing)
Invokes a spare drive to replace the faulty drive without using an additional
mirror position
(permanent sparing).Symmetrix RAID 1/0Symmetrix RAID 10RAID

http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd85 RAID 6Sparing
.When configuring multiple data protection options, consult your EMC Sales
Representative for configuration rules. Not all data
options are available on all Symmetrix systems or Enginuity versions.
R11 devices are used primarily in Concurrent SRDF operations. The R11 has two
R1 SRDF mirrors, replicating to two different secondary devices. Each SRDF
must be configured to a separate SRDF group. Figure18 on page56 shows an
of a Concurrent SRDF configuration that uses R11 devices.
“Groups and links” on page36 provides more information on SRDF links.

devicesSecondary devices (R2, R22) contain a mirrored copy of data from
associated primary
. Like primary devices, secondary devices can be paired with BCVs and
protected using protection types listed in Table2 on page25. Secondary
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ices used in SRDF/Star
solutions are known as R22 devices.
types25
devices are mainly used in SRDF/Star environments. The R22 is a concurrent R2

device. It has two unique R2 SRDF mirrors t
receive data from different primary devices. Only one of the R2 mirrors can
accept reads or writes from a primary device at a point in time. The other
mirror is marked as blocked to its primary device. Two R2 mirrors allow
businesses to benefit from two SRDF relationships in the event of an SRDF/Star
failover/failback operation by avoiding the need for reconfiguration steps
required during these procedures if R22 devices are not used. The SRDF/Star
failover operations with Enginuity versions prior to 5874 require that any R2
device have the R2 mirror deleted before it is used in a different SRDF
relationship. This is no longer necessary with R22 devices. Figure 4
ohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8n page 26 and Figure
5 on page 26 show an R22 device used with Cascaded and Concurrent
SRDF/Star.“Concurrent SRDF/Star” on page 98 and“Cascaded SRDF/Star” on page
100 provide additional information on these SRDF operations. R22 devices must
reside in a Symmetrix V-Max system running Enginuity 5874 and later. The primary
devices can reside in a Symmetrix DMX system running Enginuity 5773 or Enginuity
5671 (for migration operations only). Both static and dynamic R22 devices are
supported. Both R2 mirrors must be either static or dynamic. They can not be a
mixture of both.“Dynamic SRDF devices” on page 27 provides additional details.
/S
Failover link
/A
4
device with Cascaded SRDF/Star
/A R22 R11
/S R21
linkR22 device with Concurrent SRDF/Star
5
role devices (R21)
devices are duhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8al-role
SRDF devices used in three-site replication solutions such as Cascaded SRDF. The
R21 device simultaneously assumes the roles of a secondary and a primary device.
Data received by an R21 as a secondary device can automatically be transferred
by the same device as a primary device to another secondary device, the third
SRDF mirror in the Cascaded SRDF configuration.“Dynamic SRDF devices” on page
27 contains additional information. Beginning with Enginuity 5874, a special
type of R21 device is supported - diskless R21 (DL R21).
Diskless R21 devices
SRDF
Technical ConceptsDiskless R21 devices (DL Dev) operate as R21 devices but do
not store full copies of data. Diskless R21 devices store only the data
differences coming from the primary site traveling to the tertiary site.
Dihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8skless R21 devices
have two SRDF mirrors. During creation/deletion of this device type or during
automated failover/failback operations, the diskless R21 devices may temporarily
have only one SRDF mirror. Diskless R21 devices are supported on Symmetrix V-Max
hardware platforms running Enginuity 5874 and later and are used in SRDF/EDP
solutions. Figure6 on page27 shows a three-site configuration using diskless R21
devices residing on the secondary site.
PrimarySecondaryTertiaryHostSRDF/SSRDF/AR1DLDevR2Full copyDisklessFull copyR21
device(Not full copy-differences only)SYM-002130Diskless R21 device (DL Dev)The
following guidelines should be considered when using diskless R21
devices:◆Diskless R21 cannot be used with TimeFinder.◆Diskless R21 cannot be
assigned to hosts.◆Diskless R21 cannot be used in adaptive copy disk mode.◆R21
and diskless R21 devices cannot be used in the same SRDF/A session. If the
SRDF/A mode is not used,
diskhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8less R21 can be
configured in the same SRDF group as R21 devices.◆Virtually provisioned (thin)
devices cannot be remotely mirrored to diskless R21 devices.Dynamic SRDF devices
are SRDF devices that allow flexible control over an SRDF configuration. Dynamic
SRDF device attributes can be configured and controlled
EMC host-based SRDF software. Unlike static SRDF devices whose SRDF
are defined and stored in the Symmetrix configuration file, dynamic SRDF
are only enabled in the configuration file while their device attributes are
in, mirrored, and protected by Symmetrix memory vault operations during
power off.. EMC host-based SRDF software can initiate the following actions
modify dynamic SRDF device attributes:
◆Create a new primary/secondary pair relationship from non-SRDF devices
◆Terminate and establish a relationship with a new

sechttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ondary device
◆Swap personality between primary and secondary devices.

: Creating, terminating, and swapping personality functions are not allowed in
ESCON
configurations. “ESCON” on page42 provides more details.
SRDF devices are supported in the following topologies:
◆Fibre Channel SRDF, point-to-point connection

types27
◆
◆
◆Fibre Channel SRDF, switched Fibre Channel GigE SRDF ESCON, point-to-point
connection.
SRDF devices were introduced in Enginuity 5567. The only Dynamic SRDF
delivered in Enginuity 5567 was R1/R2 personality swap. The Dynamic
functionality delivered in Enginuity version 5568 and later enabled users to
, delete, and swap SRDF pairs while the Symmetrix system was in operation. At
level 5x71 and later, SRDF/A
dehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8vices could be
configured as Dynamic
capable devices.
/R2 personality
SRDF provides the capability of swapping the R1/R2 personality of an SRDF device
pair. After a personality swap, the primary R1 devices become
R2 devices and the secondary R2 devices become primary R1 devices. The
swap allows the R2 side to take over operations while retaining a remote
on the R1 side. This feature is especially useful after failing over an
application
the R1 to the R2 side.
remote mirroring must be halted before performing an R1/R2 swap. Once the
operation is complete, the SRDF device pair remains halted. EMC host-based
software then controls and maintains incremental or full resynchronization.
introduced in Enginuity 5x56 and 5x66, the R1/R2 personality swap feature
an online
conhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8figuration change.
With Enginuity 5567 and dynamic SRDF
, users could leverage their flexible SRDF configurations by initiating
performance dynamic R1/R2 swap operations via the EMC host-based SRDF
.
swap is not supported under the following conditions:
◆If one site in the SRDF configuration runs Enginuity 5567 and the other runs
Enginuity 5568.
the R2 device is larger than the R1 device.
the devices to be swapped are participating in an active SRDF/A session.
SRDF/EDP configurations where attempted reconfiguration operations, either
performed manually or via automation, would result in an illegal device device
such as a DL R22 or DL R11.
ESCON FarPoint configurations.◆◆◆◆
SRDF Host Component for z/OS Product Guide and the EMC Solutions Enabler
SRDF Family CLI Product Guide provide more
ihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nformation about
the R1/R2 swap operations and specific host platform requirements.
Compatible
version 5568 and later enables the Symmetrix system to support native IBM Peer-
to-Peer Remote Copy (PPRC) commands through a Symmetrix feature
EMC Compatible Peer. The EMC Compatible Peer mode requires dynamic
devices. This feature is available in mainframe environments for all CKD
types supported by the IBM PPRC feature.
dynamic SRDF device enters PPRC mode when it receives a PPRC CESTPAIR
from the host. Once in PPRC mode, the device cannot be controlled by the
host-based SRDF software; only PPRC commands received from the host can
Symmetrix devices in PRRC mode..
Converting to/from
mode devicesSRDF Technical
Cohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nceptsBeginning with
Enginuity 5568,EMC Compatible Peer implements PPRC version 1, architectural
level 2. Enginuity 5671 adds support for PPRC version 1, architectural levels 3
and 4 Hyperswap support, including failover/failback functionality. More details
about PPRC implementations are available
at:http://www.mianfeiwendang.com/abstracts/sg246374.htmlBecause EMC Compatible
Peer does not support advanced SRDF features such as Concurrent SRDF and SRDF/A,
the following devices cannot be converted to PPRC devices:◆R11, R21, or R22
devices ◆Devices in an active SRDF/A group◆Primary devices (R1) in an active
SRDF/Consistency Groups ◆SRDF devices in an SRDF/Star relationship.This feature
allows businesses to convert their PPRC or SRDF devices with minimal down time
between the primary and secondary devices using differential copy. This
is available in mainframe environments for CKD 3380 and 3390 devices only.
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8C Customer Service
personnel perform the conversion on the primary site by
the appropriate attended online configuration change script. The SRDF links
remain active during this operation.
: “EMC Compatible Peer” on page28 contains additional information on EMC’s
support
PPRC.
the PPRC to SRDF conversion, either the CE or the customer must issue
that resume the relationship between the primary and secondary devices.
the SRDF to PPRC conversion, the customer must run the CESTPAIR and
commands.
to the following guidelines when using the conversion process:
◆Enginuity 5874 must be running on both the primary and secondary side
◆An EMC CE must run the conversion procedure
◆To convert from SRDF to PPRC requires the device be a dynamic SRDF device
◆To convert from PPRC to SRDF or SRDF to

Phttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8PRC the SRDF group
can be either static or dynamic. “Dynamic SRDF devices” on page27 contains
additional
on dynamic SRDF groups
conversion, the following conditions must be true:
◆.Only SRDF devices (R1, R2) with single remote mirrors are allowed. No
R11,R21, or R22 devices are allowed
◆The relationship between R1 and R2 devices must be suspended

◆The R1 device cannot be in an active SRDF/Consistency Group
◆The devices to be converted cannot be in a SRDF/Star relationship
◆The devices to be converted cannot be in an active SRDF/A group
◆Devices to be converted must be in the same SRDF group. Only one SRDF group at
a time can be converted
types29
**With Enginuity 5874, customers can convert their PPRC devices to SRDF devices.
Customer Service personnel perform the conversion by running the
aphttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8propriate
configuration change procedure on the primary site. The SRDF links must
active during the operation. Once the conversion is completed, the
between the primary and secondary devices must be resumed.
to the following guidelines when using the PPRC to SRDF conversion
:
◆Enginuity 5874 must be running on both the primary and secondary side.The SRDF
relationship between R1 and R2 devices must be resumed after the conversion
process.
device
following Symmetrix devices require special consideration when used in an SRDF
environment:
◆
◆Open systems metavolumes (RAID 1/0) RAID 10 mirrored striped CKD devicesThin
devices.
systems
(RAID 1/0)In open systems environments, users can create metavolumes. A

metavolume is a device comprised of
mulhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8tiple Symmetrix
logical devices (volumes) presented to the
as a single addressable device. The metavolume consists of a head device, some
of member devices (optional), and a tail device.
allow users to create devices larger than the current maximum
device size of approximately 256 GB, can contain up to 255 Symmetrix
, and can reach up to 16 TB in size. Metavolumes reduce the number of
visible to the host and can be composed of nonsequential and nonadjacent
devices.
remotely mirrored in an SRDF configuration, metavolumes must be configured
both sides of the SRDF links with the number of the meta members equal on the
and secondary side. Concatenated metavolumes must have equal size
on both sides of the link.
: Additional considerations apply to striped
metavolumehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8s and to
SRDF device pairs with
R2 device larger than the R1. Contact EMC Customer Service for more details.
RAID 10
striped CKD
improve mainframe volume performance, Symmetrix RAID 10 stripes data across
multiple Symmetrix logical devices. Four Symmetrix devices (each one-fourth the
of the host-facing mainframe device) appear as one mainframe device to the host.
four Symmetrix logical devices can be chosen to define a RAID 10 group,
they are the same emulation (for example, IBM 3390) and have the same
protection scheme. Since each member of the stripe group is mirrored (stripe
is one cylinder), the entire set is protected.
Enginuity 5568 or later, RAID 10 striped volumes can be remotely mirrored to
RAID 10 devices (R2). The R2 device size on the secondary site must equal the
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8mainframe device size on
the primary site. With Enginuity 5669 or later, the R2
can be larger than the mainframe device on the primary site.
ProvisioningA virtually provisioned device (thin device) is a device without
space physically
until the first I/O write to the device occurs. Then, the Symmetrix system
storage space for this device from a pool of Virtual Provisioning data
that are real storage devices. Users are granted what appear to be very large

of storage space, while the actual space consumed on physical disk storage is
only that used by the actual data that is written. Virtual Provisioning is
supported in open systems environments with Symmetrix systems running Enginuity
5773 and later. With Enginuity 5874 and later, thin
devhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ices can be
protected by any local protection type. Thin devices can be configured as SRDF
volumes and remotely mirrored with SRDF. The following restrictions apply to
thin SRDF devices:
◆Enginuity 5773 and later is required on both Symmetrix systems.Thin SRDF

devices cannot be used with TimeFinder/Mirror.Thin SRDF devices cannot be used
in multisite configurations such as Cascaded or Concurrent SRDF.
SRDF devices can be used with TimeFinder/Clone and TimeFinder/Snap. Table3 on
page31 lists limitations.
Thin SRDF devices with TimeFinder/Clone and TimeFinder/Snap
Provisioning function
of SRDF/A R1
of SRDF/A R2
of SRDF/S R1
of SRDF/S R2a
of SRDF/A R1
of SRDF/A R2
of SRDF/S R1
of SRDF/S R2
.Requires precopy option.Enginuity
5773NoNoYesYesNoNoYesYesEnginhttp://www.mianfeiwendang.com/doc/fbe03131210633d18
de37bd8uity 5874YesYesYesYesYesNoYesYes
types31

statesOverall state for SRDF device is determined by a combination of
substates.Host interface state Host SRDF state
7
device states
two SRDF substates can be considered as two layers as shown in Figure 7 on page
32.◆◆
internal layer (Symmetrix view)— SRDF state. An external layer (host view)—
Host interface state.
two layers are configured by different sets of internal Symmetrix parameters,
which can be set by either EMC Customer Service or by EMC host-based SRDF
software. The state ultimately seen by the host is determined by the combination
of these two device states. For example, only when a secondary (R2) device is
write-enabled for both the host interface state and the SRDF state, can the host
write to the device. The following sections describe how
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8the various device
substate combinations determine the actual overall device state presented to the
host.Note: The SRDF device states are fundamental to SRDF operations. Users are
required to fully comprehend this section before attempting any SRDF operations.
device states (Symmetrix view)Primary (R1) device states
section lists the substates a primary (R1) or secondary (R2) device can have in
SRDF operations. Unless noted otherwise, all primary and secondary volume states
described in this section apply to each SRDF mirror of an R11, R21, or R22
device. A primary (R1) device can have the following states for SRDF
operations:◆
and Read/Write— In this state, the primary device is available for read/write
operations. This is the default primary device state. Host Not Ready— In this
state, the primary device responds Not Ready to the host for all read and write
operations. Not Ready— SRDF
dehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8vices can be locally
Not Ready or remotely Not Ready remotely on the SRDF link: Locally Not Ready—
If the primary (R1) device fails, the host continues to recognize that device as
available for read/write operations as all reads or writes continue
uninterrupted with the secondary (R2) device in that remotely mirrored pair.
Remotely Not Ready— If R1 devices are Remotely Not Ready, write updates do not
propagate to the secondary devices. Changes to the R1, R11, or R21 devices are
marked invalid as owed to the secondary R2 devices.
Secondary (R2)
states
device states
(host view)
(R1) device
modes and
integritySRDF Technical ConceptsA secondary (R2) device can have one of the
following states for SRDF operations:◆Read Only —
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8In this state, the
secondary (R2) device is available for read only operations. This is the default
secondary (R2) device state.◆Not Ready — In this state, the secondary (R2)
device responds Not Ready to the host for all read and write operations to that
device.◆Read/Write — In this state, the secondary (R2) device is available for
read/write operations.Note: When a secondary device is placed into a Read/Write
state, the corresponding primary device is placed into a Remotely Not Ready
state automatically, if it had not been placed in that state prior to the
secondary device being made read/write capable.◆Link blocked (LnkBlk) — This
state is unique to SRDF mirrors belonging to R22 devices. In this state, the
secondary mirror cannot receive writes from its associated primary (R1) device.
In normal operations, one SRDF mirror of the R22 device is in this state.This
section lists host-visible SRDF device states. These states are
prhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8esented to the host
connected to the Symmetrix system in which these devices reside.A primary (R1)
device can have one of the following states: ◆Write Enabled — In this state,
the primary (R1) device is available for read/write operations. This is the
default primary (R1) device state.◆Read Only — In this state, the primary (R1)
device responds Device Write Protected to the host for all write operations to
that device. ◆Not Ready — In this state, the primary (R1) device responds Not
Ready to the host for all host accesses to that device. Under certain
conditions, the primary devices can be forced into the Not Ready state to the
host. Domino attributes are used to stop all subsequent write operations to
primary and secondary SRDF devices when all mirrors of a primary or
device fail, or if all links in an SRDF group become unavailable. While
a shutdown temporarily halts production
processinhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8g, domino
modes can
data integrity in case of a rolling disaster. Domino modes can be set at the
level (device domino mode) or at the SRDF group level (link domino mode).
domino mode is set for primary devices. When this attribute is set and the
device cannot successfully replicate data to the secondary device, the
volume becomes Not Ready to its host.
domino mode is set at the SRDF group level at either side of the SRDF link. If
attribute is set and the last available link in the SRDF group fails, all
primary
in the SRDF group become Not Ready to their hosts.
the Not Ready to the host condition is set, users must re-enable the primary
using EMC host-based SRDF software. Both domino modes make SRDF R1
Not Ready and cause host applications to stop. This is an extreme measure
of://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8pardata integrity.
Consistency groups implement a more moderate
. “SRDF Consistency Groups” on page63 contains additional information.
states33

(R2)
statesA secondary (R2) device can have one of the following states:◆Read Only
— In this state, the secondary (R2) device responds Device Write Protected to
the host for all write operations to that device. This is the default
(R2) device state.
Enabled— In this state, the secondary (R2) device is available for read/write
operations.
Ready — In this state, the secondary (R2) device responds Not Ready to the host
for all host accesses to that device.◆◆
used with a special device attribute, the invalid tracks attribute, the Not
Ready to
host state on the secondary device provides information about the state of
the://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8device pair. The
invalid tracks attribute can only be set on the secondary
. When the invalid tracks attribute is enabled, SRDF makes the secondary
Not Ready to the host if the secondary device is not synchronized to its
device. The purpose of the invalid tracks attribute is to inform the user that
on the secondary devices may not be suitable for use in disaster recovery
. It is the user’s decision to proceed using data from secondary devices that
made Not Ready by the invalid tracks attribute. The Not Ready condition set by
invalid track attribute can be reset using EMC host-based SRDF software.
Enginuity 5874 and later, the state change time stamp provides users with
about the most recent SRDF mirror transitions on the primary and the
sites. The time stamp data includes the
timhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8e, type, and the
cause of the last
mirror state change to help users determine the state of the SRDF device pair.
to the
The accessibility of a particular SRDF device to the host depends on both the
host and the Symmetrix view of the SRDF device state. Table4 on page34 and
Table5 on
list host accessibility levels of a primary (R1) device and secondary (R2)
. Consult the EMC Solutions Enabler Symmetrix SRDF CLI Product Guide or the
SRDF Host Component for z/OS Product Guide for more information on how
information is presented in these operating environments.
(R1) device - accessibility to the host
interface state
Enabled
Enabled
Disabled
Disabled
Ready
Ready Symmetrix stateRead/WriteNot ReadyRead/Write Not ReadyRead/Write Not
Readyhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8AccessibilityRead
/WriteDepends on the R2 availabilityRead OnlyDepends on the R2
availabilityUnavailableUnavailableTable4
Secondary (R2) device - accessibility to the host
interface state
Enabled
Enabled
Enabled Symmetrix stateNot ReadyRead Only Read/WriteAccessibilityUnavailableRead
OnlyRead/Write


Secondary (R2) device - accessibility to the host
interface state
Disabled
Disabled
Disabled
Ready
Ready
ReadySymmetrix stateNot ReadyRead OnlyRead/WriteNot ReadyRead Only Read/Write
AccessibilityUnavailableRead Only Read OnlyUnavailableUnavailableUnavailable
states35

and links
groups define relationships
betwhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8een Symmetrix
systems. An SRDF group is
as a set of SRDF ports and devices configured to communicate with another
of SRDF ports and devices in another Symmetrix system. SRDF groups cannot
topologies and therefore cannot have both GigE and Fibre Channel ports
in the same SRDF group.
typesSRDF groups can be defined as:
◆Static groups - created and saved in the Symmetrix configuration file

: EMC recommends that static SRDF groups be used with EMC Compatible Peer.
◆Dynamic groups - created and controlled through EMC host-based SRDF software
on page36 summarizes SRDF device and SRDF device group support in Symmetrix DMX
and Symmetrix V-Max series systems◆
Device support for SRDF
platform
level
support for SRDF
limit per SRDF
grouphttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8s per system

groups per portSymmetrix DMX seriesa
567016K8K328567132K16K648577164K32K648577264K32K12832577364K64K12832Symmetrix V-
Max seriesa587464K64K25064
.65K devices require a minimum of two SRDF groups.
Enginuity 5669 and later, users can create empty SRDF groups and associate these
with Fibre Channel or GigE SRDF ports. Users can also remove these dynamic
groups by using EMC host-based SRDF software.
dynamic SRDF devices are added to the SRDF groups, these dynamic groups
users to exercise complete control over their SRDF configuration.
dynamic SRDF
between
groupsWith Enginuity 5773 and later, dynamic SRDF devices can be moved between
SRDF groups without having to execute a full synchronization. The move operation
that the remote device be Not Ready (split, suspended) on the SRDF link
at://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8parprimary side at the
time of the move. EMC host-based SRDF software supports
capability in SRDF/S or SRDF/A modes of operation. Figure8 on page37 shows
example.

/S
/S
8
SRDF devices between SRDF groups
Dynamic SRDF move operation can be either a full or a half move; the former
moves the SRDF device pair, the latter a single device in the SRDF device pair.
After half move operations, a merge operation is required to make the remote
device Ready on the SRDF link. In Cascaded SRDF solutions, only a full move is
allowed for R21 devices. The key benefits of moving SRDF devices between dynamic
SRDF groups are:◆◆
and fast transition to a different SRDF topology Minimal RPO exposure on device
move operations.
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8te: An improved mechanism
is available for moving SRDF devices in Consistency exempt solution that are
participating in an SRDF/A session.“Consistency exempt option” on page 92
provides more details.
link is a physical connection between the Symmetrix SRDF ports and includes the
SRDF ports, wire, routers and switches. The links between a given pair of
Symmetrix systems in an SRDF configuration can use one of the following methods
to transmit data:◆◆◆
Bidirectional Dual-directional.
link configuration
all primary devices (R1
) reside in one Symmetrix system and all secondary devices (R2) reside in
another Symmetrix system, write operations move in one direction, from primary
to secondary. This is a unidirectional configuration as data moves in the same
direction over every link in the SRDF group. If an SRDF group contains both
primary and secondarhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8y
devices, write operations move data in both directions over the SRDF links for
that group. This is a bidirectional SRDF configuration. If multiple SRDF groups
are used, some sending data in one direction, the other in the opposite
direction, the link configuration is dual-directional. Dual-directional
configurations are often used in extended-distance SRDF configurations that
require data to move in two directions. SRDF links can be in two possible
states: online or offline. The SRDF link is online when the following occurs:◆
link configuration
directional link configuration
states
Symmetrix SRDF ports are operational and enabled on both sides of the SRDF
configuration
and links
◆The Symmetrix systems are configured properly on both sides of the SRDF
configuration
external link
infrastrhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ucture
components are operational.
Symmetrix directors are offline
Symmetrix directors are online but the link is offline (damaged or disconnected
cable or other external network damaged hardware)
configuration of SRDF relationships between Symmetrix systems, or devices
participating in the SRDF relationship, are not configured properly.◆The SRDF
link is offline if one or more of the following occurs:◆◆◆
and device
that affect
operationsIf all SRDF links fail, the Symmetrix system remembers the last known
logical state of the affected devices. This behavior is known as pure Ready
state. If a device is in a
state before all links fail, it is restored to a Ready state when any link
becomes
again. If a device is in a Not Ready state before all links fail, it is restored
a Not Ready state after any link is again
operahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8tional. Automatic
recovery can be
in the Symmetrix configuration file.
: The device level pure ready state behavior does not apply the SRDF/A mode of
. Chapter6, “SRDF/Asynchronous Operations” provides details.
following settings in the Symmetrix configuration file affect link states:
◆If the Prevent Automatic Recovery After All Links Fail setting is set in the
Symmetrix configuration file, all devices in the corresponding SRDF group
Not Ready on the SRDF links after all links fail.
the Force RAs Offline After Power Up configuration setting is set, the SRDF
links remain offline following a Symmetrix power cycle. When set, this attribute
SRDF ports offline after a power outage event and is used to protect data in
rolling disaster scenario that can follow a power outage.◆
to Enginuity 5669, these configuration
sehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ttings were applied
at the Symmetrix
level. At Enginuity version 5669 and later, these configuration settings are
at the SRDF group level.

protocols and topologiesSRDF supports the following network protocols to move
data across the SRDF links: Fibre Channel, Gigabit Ethernet, and ESCON. These
protocols and the corresponding network topologies used in SRDF configurations
are introduced in the following sections. The EMC SRDF Connectivity Guide
provides more detailed information about the SRDF connectivity options.
Channel
the following when deploying SRDF over Fibre Channel:◆
— Round trip time between the primary and the secondary Symmetrix systems.
Increased latency can be caused by host bus adapters (HBAs), switches, optics
(multimode, singlhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8e-
mode), distance extension devices, and Fibre Channel cables. Bandwidth—Allow
for the necessary amount of bandwidth to handle both present and future
requirements. Flow control— Hardware-based flow control mechanisms affect
distances between links. SRDF flow control allocates the number of I/Os that can
be sent from the SRDF layer. Fast write/write acceleration— Products that can
increase SRDF throughput over extended distances. These products decrease
response time for SRDF/S and improve performance over long distances for
adaptive copy and SRDF/AR and some SRDF/A configurations. Compression— Software
compression is available with Enginuity 5874 and may increase data throughput
over the SRDF links. FCIP and IFCP— Tunneling protocols for transporting Fibre
Channel ISL traffic.
◆
Fibre Channel
5x67 and later support fully switched open SRDF (Fibre
Channehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8l) connections.
Switched SRDF topologies allow greater connectivity and configuration
flexibility with a given number of Symmetrix Fibre Channel ports and are often
used in Concurrent SRDF and SRDF/Star solutions. Switched SRDF topologies
require non-blocking switching devices that interconnect two or more Fibre
Channel ports. Figure 9 on page 39 shows a switched SRDF configuration using
Fibre Channel switches connected through E_Ports. In this configuration,
multiple primary devices are remotely connected using a storage area network
(SAN) to multiple secondary devices.
Switch E_Port Switch E_Port
Switch E_Port
_Port
R11
R1= Primary devices R2= Secondary devices
9
SRDF with multiple primary and secondary devices
protocols and topologies
10 on page 40 illustrates
Symmetrhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ix A
simultaneously communicating with Symmetrix B and Symmetrix C through a Fibre
Channel switch, using point-to-point and point-to-multipoint Fibre Channel
connectivity with Symmetrix B and Symmetrix C, respectively. In this example,
primary (R1) devices reside in all Symmetrix systems, indicating a bidirectional
dual-directional SRDF link configuration.Symmetrix A DMX, 5669 R2 volumesRF
to-point FC switch
B 3XXX/5XXX, 5267
RF
volumes R2 volumes
volumes
C 8000, 5568
tomultipoint
RF
volumes R1 volumes
10
SRDF over Fibre Channel with Enginuity 5x67
11 on page 41 illustrates Symmetrix A communicating with Symmetrix B and
Symmetrix C simultaneously through a Fibre Channel switch using point-to-point
and point-to-multipoint connectivity. Symmetrix A also
useshttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 Concurrent SRDF
to mirror its primary devices (R1s) to a second set of secondary devices (R2s)
in Symmetrix D. To support Concurrent SRDF, each SRDF Fibre Channel port in
Symmetrix A is configured to support two SRDF groups. A separate ESCON SRDF
group in Symmetrix A is configured for Concurrent SRDF to Symmetrix D.Note: The
ability to support point-to-multipoint connectivity is not related to primary
(R1) or secondary (R2) device relationships.


A DMX, 5669 Symmetrix devicesRF
B 3XXX/5XXX, 5267 FC switchRF RF
-0F 10-1F R11 volumes

RA1 RA1
volumes
C 8000, 5568
supported link
RF
volumes
RA2
D 3XXX/5XXX or 8000, 5x67
devices 00-1F R2 volumes (second
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8remote copy of all
SRDF devices in Symmetrix A)
11
and Concurrent SRDF over Fibre Channel
Ethernet (GigE)
implementing SRDF over GigE network protocol, consider the following:◆
— Round trip time between the primary and the secondary Symmetrix systems.
Latency should be as low as possible at given distances separating the sites.
Network quality— Affects packet loss. Packets should not be sent or delivered
out of order to avoid performance degradation and SRDF links bounces. Link speed
— Affects the amount of traffic that a Symmetrix director sends from each port.
Speed limits are set in the Symmetrix configuration file. Flow control—
Hardware-based flow control mechanisms affect distances between links. MTU size
— Maximum transmission unit (MTU) should not be exceeded or packet
fragmentation will occur. Compression— Hardware compression may increase the
throughpuhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8t of the data
over the links. Encryption devices— Can be used to ensure the secrecy of data
transmitted between two points. Contact your EMC Sales Representative for the
list of qualified encryption devices. Security— SRDF GigE implementations
support IPv4 and IPv6. IPv6 is available on the GigE/IPsec implementations
beginning with Enginuity 5773. IPSec is available with Enginuity 5773 and later.
◆
configurations with native GigE
DMX and Symmetrix V-Max series systems provide support for native IP that
enables direct Symmetrix system-to-IP-network attachment. With GigE, SRDF
solutions can use connectivity provided by an existing Ethe
infrastructure and directly access high-speed data transmission conduits using
IP. Figure 12 on page 42 illustrates a switched GigE SRDF solution. Each GigE
port in a primary site establishes a
logihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8cal TCP connection
to each GigE port in the remote Symmetrix system. The EMC Network Storage
Topology Guide and the EMC SRDF Connectivity Guide contain more details.Network
protocols and topologies41
.Symmetrix A GigE switch/routerRE RE

B GigE switch/router WAN
RE
network
12
SRDF over GigE
is available as an SRDF network protocol on DMX hardware platforms running

Enginuity 5773 or earlier. Consider the following when deploying SRDF over
ESCON:◆
distances can be increased by using ESCON extender/repeater units or the ESCON
director XDF feature. FarPoint is an SRDF feature used only with ESCON extended
distance solutions and certain ESCON campus solutions to optimize the
performance of the SRDF links. For SRDF distances beyond 15 km, or connections
through channhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8el
extenders, use FarPoint to eliminate distance limitations and minimize
performance penalties. If ESCON directors are used in SRDF configurations, the
ESCON director ports must be configured as static and dedicated.

of operation
modes
modeTo accommodate different data protection and performance requirements while
processing various levels of host I/O activities, the SRDF solutions can operate
in different modes. SRDF modes of operation fall into two categories; primary
and secondary modes of operation. Once set, the primary mode is the default mode
of operation in a given SRDF solution and is associated with the corresponding
SRDF product offering. To address specific situations, the SRDF solution can
also operate in secondary modes.
Whenhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 secondary modes
of operation are reverted, the SRDF devices default to their primary modes of
operation. Primary and secondary modes are set at the device level and are
managed at the SRDF group level. SRDF supports synchronous, asynchronous, and
semi-synchronous modes as primary modes of operation. If synchronous or semi-
synchronous mode is used, the user must set the same SRDF mode of operation on
the remote mirrors.Available with the SRDF/S product offering, the synchronous
mode maintains a
time mirror image of data between the primary and secondary devices. Data
be successfully stored in both the primary and the secondary site before an
is sent to the primary site host. Synchronous mode I/O is
in the following steps:
.The Symmetrix system containing the primary device receives a write operation
the host and places the write data into global
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8memory.
.The primary Symmetrix system propagates the write I/O operation to the remote
system containing the secondary device. The primary Symmetrix
does not accept additional write operations to the primary device.
: SRDF/S supports multiple concurrent I/Os at the volume level if PAV/MA or FBA
are used at the host interface level, and the host write command is sent to a
data region on the Symmetrix device.
.The secondary Symmetrix system sends an acknowledgement to the primary

system after the write has been received in global memory.
.The primary Symmetrix system sends a completion message to the host and can
accept additional host write operations to the primary device.
synchronous mode of operation is suited for most metropolitan area network
(MAN) implementations where distances
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8between Symmetrix
systems participating
SRDF operations are short. Figure13 on page44 shows an example. If SRDF/S is
in conjunction with other modes of operation, such as SRDF/A,
/S is used for distances shorter than 200 km (125 miles) and SRDF/A is used for
greater than 200 km (125 miles).
of operation43

site Host Metro secondary site SRDF/SSAN
R1
SAN R2
Figure 13
metropolitan area network configuration

14 on page 44 illustrates an example where SRDF/S is used within a metro region
and the SRDF adaptive copy mode over the wide area network (WAN).Primary site
Host
secondary site SRDF/S (Hop 1) FC SANR1
SANR2 BCV R1
Adaptive Copy (Hop 2) SAN SAN
of region site
R2
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8trix
SYM-002125
14
wide area network configuration
mode
mode (SRDF/A) is a remote copy solution, designed to support greater distances
between the primary and the secondary site, without the response time impact
associated with a synchronous solution as shown in Figure 15 on page 45. In an
SRDF/A implementation, data is asynchronously replicated while maintaining a
dependent-write consistent copy of the data on the secondary (R2) site at all
times. The point-in-time copy of the data at the secondary site is only slightly
behind that on the primary (workload) site. SRDF/A session data is transferred
from the primary to asynchronous secondary site in cycles, using delta sets.
SRDF/A has little or no impact on the production on the primary site as long as
the links and secondary system are fast enough to move data across the SRDF
lihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nks. If the remote
copy process is unable to keep pace with I/O activity on the primary site,
SRDF/A can throttle host I/Os to catch up.

volume
volume
15
/A basic configuration
/A is used in wide area network implementations where longer distances are
required. If disaster recovery solutions are required, the Concurrent SRDF
architecture is deployed with synchronous mode over the MAN distance and
metropolitan area and with asynchro
mode over the WAN distance as shown in Figure 16 on page 45.Metro secondary site
site
/S FC
SAN SRDF/A FC
of region siteSYM-002126
16
basic MAN/WAN configuration
/S–SRDF/A mode change
SRDhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8F configurations
can use the SRDF/S in conjunction with SRDF/A to switch between asynchronous
mode and synchronous mode while maintaining dependent-write consistency on the
R2 (secondary) site throughout the process. This feature can be used when a
transaction load causes latencies that applications may not be able to handle
while in synchronous mode. With the mode change capability, users can switch
from SRDF/S to SRDF/A mode during high workload periods to minimize performance
impact on applications. Once a peak workload situation has passed, the users can
revert to SRDF/S mode. Semi-synchronous mode Semi-synchronous mode is supported
prior to Enginuity 5773. Previously used mainly for the extended distance
solution, semi-synchronous mode allows the primary and secondary devices to be
out of synchronization by one write I/O operation. Data must be successfully
stored in the Symmetrix system containing the primary device
beforehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 an
acknowledgement is sent to the local host. Semi-synchronous mode will not allow
another write I/O to the primary device until a positive acknowledgement is
received from the secondary Symmetrix system that the first write operation was
received in the secondary Symmetrix system’s global memory. However, any number
of read operations can be performed to the primary device while awaiting
acknowledgement of the first write operation.Modes of operation45

synchronous mode writes data to the primary device, completes the I/O, and
synchronizes the data with the secondary device in the secondary Symmetrix
as follows:
.The Symmetrix system containing the primary device receives a write operation
the host.
.The primary Symmetrix system writes data to the primary device and a sends
message to the lhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ocal
host. The host now considers the I/O complete.
operations to the primary device continue normally while a second write
/O to that device is not immediately accepted.
.The primary Symmetrix system propagates data from the first write operation to
Symmetrix system containing the secondary device.
.When write data is received in its global memory, the secondary Symmetrix
sends an acknowledgement from the first write operation to the primary
system. When the acknowledgement is received, another write I/O
the host can be accepted to this primary device.
: In the mainframe environment, semi-synchronous mode is not supported when the
uses FICON host connectivity. In the mainframe PAV/MA environment,
synchronous mode is not recommended because it provides no performance benefit.
users seekinghttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 the
increased parallelism offered by PAVs should run SRDF in
mode.
modesAll SRDF primary modes can be used in conjunction with secondary modes of
. Like the primary modes, secondary modes of operation are defined at the
level and managed at the SRDF group level. If adaptive copy is used, it can be
for either one or both remote mirrors. SRDF supports adaptive copy modes
secondary modes of operation.
copy modes allow the primary and secondary devices to be more than one
/O out of synchronization. The maximum number of I/Os that can be out of
is known as the maximum skew value.
maximum skew value for an SRDF can be set using EMC host-based SRDF
. There are two adaptive copying modes: adaptive copy write-pending mode
adaptive copy disk mode. Both modes allow
whttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8rite tasks to
accumulate on the
system before being sent to the secondary system.
copy write
SRDF adaptive copy write pending mode, write tasks accumulate in the global
memory of the primary Symmetrix system. A background process writes data to the
device and the corresponding secondary device on the other side of the
links. When the maximum skew value is reached, the primary device reverts to
primary mode of operation, for example, synchronous or semi-synchronous to
the I/O backlog on the primary site. The device remains in the primary mode
the number of I/Os out of synchronization is lower than the maximum skew
.
: Adaptive copy write-pending mode reverts to the specified primary mode if 75
percent
the write-pending limit for the Symmetrix system is reached, regardless of
whether thehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8
skew value specified for each device is reached.
copy disk
copy disk mode is similar to adaptive copy write pending mode, except that write
tasks accumulate on the primary volume rather than in global memory. A
process destages the write tasks to the corresponding secondary volume.

the skew value is reached, the primary volume reverts to its primary mode of
.
Enginuity 5773 or later, the background copy tasks scheduled to send I/Os from
primary to the secondary devices can be deferred if:
◆The copy tasks exceed the maximum device write pending limits that the
secondary devices can afford.
copy tasks exceed 50% of the secondary system write pending space.◆
SRDF devices that operate
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8in the adaptive copy
disk mode should be locally
. Diskless devices cannot operate in adaptive copy disk mode.
of operation47

2
Operations
chapter describes the following SRDF operations. Topics include:
◆Write
operations......................................................................
..................................... 50
◆Read
operations......................................................................
...................................... 52
◆Recovery
operations......................................................................
.............................. 53
Operations49
SRDF Operations
operations
write task is the most common SRDF operation. This section describes the write
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ions for unidirectional,
dual-directional, and bidirectional link configurations.
write I/Os The basic write operation applies to SRDF write I/Os over
unidirectional or
directional SRDF links. In synchronous or semi-synchronous SRDF mode, the
host sends a write I/O. The I/O then moves across the SRDF links to the remote
system. When it receives the I/O, the remote Symmetrix system returns
acknowledgement to the local Symmetrix system.
: If a primary device becomes unavailable due to a CRC error, an invalid track,
or a RAID
and data is kept in the global memory of the primary Symmetrix system, data can
be
to disks in the primary Symmetrix system. This process can eliminate the need to
data from the secondary Symmetrix system.
I/Os in an
bidirectional
ESCOhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8N is used over
bidirectional links, the secondary site, normally the receiving end of the SRDF
link, also sends write data to its corresponding primary site, normally the
sending end of the SRDF link. In this case, the ESCON director on
secondary site cannot simply transmit the data over the SRDF link to the primary
due to the nature of ESCON protocol and the host-to-storage control unit
of ESCON-based SRDF.
, the ESCON director on the secondary site requests that the director on the
site read the data from the primary device. When the primary site reads data
the primary device, the write I/O from the secondary site to the primary site is
.
/S concurrent
I/Os (for FBA
)With Enginuity 5773, multiple hosts issuing write I/O to different blocks on
the same SRDF R1 device are processed
concurrentlhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8y if the
following occurs:◆
◆Subsequent writes are within two tracks (256 blocks)Maximum number of

concurrent writes to the device is less than eightSubsequent writes do not span
metadevice members.
I/Os to R21
SRDF configurations that use dual-role R21 devices the write operations require
additional capability because the R21 devices are not locally protected. If a
write
is issued from the primary to the secondary device, but the secondary site
perform the write, the dual-role R21 device will obtain the necessary data
the tertiary device, allowing the primary device to execute the write I/O and
send the update write to the tertiary R2 device.
: If the R21 devices are diskless (DL Dev), by default, no direct host-write is
allowed to
devices.
EMC Symmetrix Remote Data Facility (SRDF) Product

http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Guide
SRDF Operations
I/Os and
compression for SRDF over Fibre Channel and GigE is available with Enginuity
5874 and later. Both sides of the SRDF link must be able to support compression.
the case of write I/Os, the decision to compress is made locally, as the same
engine
compression and the write operation.When compression is enabled, data is
, then sent across the link.
GigE SRDF implementations, both software and hardware compression can be
simultaneously. Data would first be compressed by the software and further
by the hardware.
operations51
SRDF Operations
operations
section describes the types of read operations with SRDF.
I/Os to the
device Read operations from a primary device behave as normal read
ohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8perations and are not
impacted in any way by SRDF. The Symmetrix system always performs a full-track
for count-key-data (CKD) and at least a contiguous-block read for fixed block
(FBA) data.
operations from a secondary device can be initiated in response to read I/Os
by the host attached to the primary Symmetrix system or by the host attached
the secondary Symmetrix system.
a read operation is issued from a primary host to the secondary Symmetrix
, the secondary Symmetrix system reads data from the secondary device and
the data across the SRDF link to the primary Symmetrix system. Read
, in which the primary host reads data from a secondary device in the
Symmetrix system, are performed only if data on the primary site is
. Several events can trigger such a read
operation:://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ar
◆
◆Read I/O to the secondary device Read I/O from theprimary host to thesecondary
deviceIf data is not in global memory and all primary devices are in a Not Ready
state.If a primary device is in a Ready state but the requested track is invalid
on the local device.
the back-end director cannot access the primary device, for example, if a drive
timeout or cyclic redundancy check (CRC) errors occur.
data on the primary device is available only through a RAID rebuild. The primary
Symmetrix system then requests data from the secondary site because
operation is faster than the RAID rebuild. ◆◆
I/Os from the
host to the
deviceSRDF secondary devices are by default in the Read-Only state while SRDF is
in operation. A host attached to the secondary Symmetrix system may read data
from
secondary devices provided its operating system
supporthttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8s reading data
from
that are hardware write-protected.
the secondary host has read-only access to the secondary device, it does not
with SRDF operations. SRDF ensures that the most current image of data is
available to the secondary host.
I/Os to
R21 devicesNo direct host read operations are allowed to diskless R21 devices
because these devices are by default not visible to the host.
R21 devices can be made read/write capable to the host through the EMC
based SRDF control software. As soon as the diskless R21 devices are made read
write capable, the primary (R1) devices automatically become Not Ready on the
links. Before making diskless R21 devices read/write capable to the host, it is
that the primary devices be made Not Ready on the SRDF links.
I/Os and
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8re
If software compression is enabled, the compression policy has to be sent with
the I/O command. This eliminates the need for the remote side to look up the
compression policy and makes the policy consistent across the SRDF link.52EMC
SRDF Operations
operations
to the
system
to the
Symmetrix
for a large
of invalid
remote
supportIf the host or primary Symmetrix system fails, and the primary devices
are operating in synchronous mode, the secondary Symmetrix system can be ready
for operations in minutes. When the failure occurs, the primary and secondary
devices are synchronized within one I/O and there are no tracks owed to either
the primary or secondary side.If a
secondhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ary host is
activated to continue production processing, users must initiate a failover
process using the EMC host-based SRDF control software.The failover process
involves changing the states of the secondary devices to Ready and transferring
production processing to the secondary host. After the failover has been
initiated, updates made to the secondary devices appear as invalid tracks owed
to the primary devices. Processing continues on the secondary host until the
primary host and Symmetrix system are operational again and a failback operation
is performed.After the primary host and the Symmetrix system containing the
primary devices are again operational, production processing can resume on the
primary host. The following steps are required to transfer processing from the
secondary host back to the primary host:1.Halt processing on the secondary host
and change the state of the secondary devices to Read Only or host Not
Reahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8dy.2.If a power on
or IML is required of the primary Symmetrix system, the SRDF links must be
physically disabled to prevent invalid track metadata from moving across the
SRDF links. 3.Bring the primary devices to a Ready state.4.If the SRDF links
were physically disabled, re-enable the http://www.mianfeiwendang.come EMC host-
based SRDF control software to send invalid track metadata information from the
secondary devices to the primary devices.6.Bring the SRDF links online and
restart the primary host. The primary devices automatically receive the
appropriate data from the secondary devices, effectively resynchronizing the
primary and secondary devices.If the secondary site (the secondary host and the
Symmetrix system containing the secondary devices) has handled production
processing for a long period of time, there might be a large number of invalid
tracks (TBs in size) owed to the primary devices. Users can resynchronize
thehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 primary and
secondary devices while the secondary host continues production processing. This
operation can be carried out using EMC host-based SRDF control software.Once
there is a relatively small number of invalid tracks on the primary devices (for
example, 50 GB), users can shut down the secondary host and restart the primary
host.A primary host can issue SRDF and BCV control commands and have those
commands transmitted across the SRDF links. Therefore, a secondary host located
at
secondary site is not required to, for example, create a dependent-write
consistent
in-time copy of your data at the secondary site.
operations53
SRDF Operations
Multi-hop operations
’s Multi-hop capability provides disaster recovery protection at great
distances. A middle or bunker site transitions the synchronous replication
solution by using TimeFinder in conjunction with
SRhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8DF. SRDF Multi-hop
uses a BCV R1 on the secondary side of an SRDF synchronous configuration to
perform an incremental synchronization with a secondary device on a third
Symmetrix system as shown in Figure 17 on page 54. When split, the BCV R1 copies
only changes to the secondary device located in the third Symmetrix system. This
process provides two benefits. It eliminates the additional performance impact
on synchronous operations across great distances and dramatically reduces
network bandwidth requirements.
Site Host Secondary site SRDF/S (Hop 1)FC R1 SAN FC SAN R2 BCV R1 SAN SAN
Adaptive Copy (Hop 2)
site
R2
GEN-000803
17
SRDF Multi-hop configuration Note: Although the first hop of a SRDF Multi-hop
configuration requires an SRDF license with the ability to do synchronous or
semi-synchronous
operathttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ions, you can
use SRDF - Data Mobility in adaptive copy mode on Symmetrix systems connected to
the SRDF extended distance configuration. This requires an initial full
synchronization to establish the relationship.
Migrations
can be used to migrate data between two or more physically separated Symmetrix
systems. Enginuity 5669 and later provide a temporary method for migrating data
from a primary (R1) device to a larger secondary (R2) device. When a primary
SRDF device is remotely paired with a larger secondary device, the device format
information is copied from the primary to the secondary device. When the
secondary device is initially mounted to a host, the host assumes that this
secondary device had the same characteristics as its corresponding primary
device. Until the device format information is updated, the secondary device can
be used as a remote mirror to the primary device. However, once this
inhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8formation is updated
to reflect the larger size of the secondary device, this
can no longer be remotely paired with its original, smaller primary device. The
process used to update the device format information is specific to host
operating system and data management systems employed. Certain limitations apply
when the R2 device is larger than the R1 device:◆◆
operations are not allowed Data migrated to a larger secondary device, once the
host has recognized the additional capacity, cannot be restored back to the
primary device Striped FBA metadevices are supported with restrictions
Concatenated FBA metadevices are not supported.
◆◆
3
Multisite
chapter describes the SRDF multisite operations. Topics include:
◆Concurrent
operations................http://www.mianfeiwendang.com/doc/fbe03131210633d18de3
7bd8............................................................................
......◆Cascaded
operations......................................................................
............................... 56◆Extended Distance Protection
◆Four-site
configurations..................................................................
................................................................................
.................................. 58 60 61
Multisite Operations55
SRDF Multisite Operations

operationsEnginuity version 5567 and later supports the ability for a single
primary device to be remotely mirrored to two secondary devices concurrently.
This feature is called Concurrent SRDF and is supported on Fibre Channel,
Gigabit Ethernet (GigE), and ESCON SRDF topologies. In Concurrent SRDF, the
primary (R11) devices must be assigned to two different SRDF groups. This is
because each http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8remote
mirror can be assigned to only one SRDF group, even if the two secondary devices
reside in the same Symmetrix system. Concurrent SRDF requires that each remote
mirror operate in the same primary mode, either both synchronous or both semi-
synchronous, but allows either or both devices to be placed into one of the
adaptive copy modes. Figure 18 on page 56 shows a Concurrent SRDF configuration
in which the primary device is communicating with one secondary device in
synchronous mode. Concurrently, the same primary device is communicating with
its other secondary device in one of the adaptive copy modes. Any combination of
synchronous/semi-synchronous and adaptive copy mode is allowed except for one
remote mirror operating in synchronous mode and the other remote mirror
operating in semi-synchronous mode.Symmetrix
SymmetrixAdaptive Copyhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8
18
SRDF configuration
I/O operational rules for SRDF also apply to Concurrent SRDF configurations.
When operating in synchronous mode, ending status for an I/O is not presented to
the host until the remote Symmetrix system acknowledges receipt of the I/O to
the primary Symmetrix system. If both secondary devices are operatin
in synchronous mode, ending status is not presented to the host until both
devices acknowledge receipt of the I/O. If one remote mirror is in synchronous
mode and one remote mirror is in adaptive copy mode, ending status is presented
to the host when the synchronous device acknowledges receipt of the I/O.Note:
Concurrent SRDF can also be implemented with SRDF/Star.“Concurrent SRDF/Star”
on page 98 contains additional information.
SRDF/S with SRDF/A
SRDF/S with SRDF/A provides the ability
tohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 remotely mirror a
group of devices in synchronous mode to one secondary site and in asynchronous
mode to a different secondary site which may be an extended distance site. In
this

, each primary device is remotely mirrored synchronously using SRDF/S on one set
of SRDF links and asynchronously using SRDF/A on another set of SRDF links.
migration with Concurrent SRDF
migration with Concurrent SRDF provides the ability to replace an existing
primary or secondary device with a new device in an SRDF pair. During migration,
a Concurrent SRDF relationship is established to transfer data from an existing
device to a new device in adaptive copy disk mode. After this data transfer, the
existing device is replaced with the newly populated device in the SRDF pair.
Ehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8MC Solutions Enabler
Symmetrix SRDF Family CLI Product Guide contains additional information on
device migration.
mirror SRDF ECA
a Concurrent SRDF/S with an SRDF/S configuration (SRDF/S/S), the two-mirror SRDF
ECA (Enginuity Consistency Assist) feature provides allows for independent
consistency group protection. If the user decides to disarm the protection on
one SRDF group, the other synchronous SRDF group can remain active and continue
protecting the primary site as shown in Figure 19 on page 57. SRDF ECA is
available with Enginuity version 5874 or later.
remains protected SRDF/S
BCV Secondary site (Enginuity/5874, 5773)
R11
Primary Site (Enginuity/5874) SRDF/S
/split Incrementally establish/resume Re-establish split
BCV Test OFF Split BCV or R2
site (Enginuity/5874, 5773)
19
of two-mirrhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8or SRDF ECA
have two options for managing consistency groups in a Concurrent SRDF/S/S
configuration:◆◆
consistency group protection Joint consistency group protection.
“SRDF Consistency Groups” on page 63 provides additional information.
following are the benefits of Concurrent SRDF:◆◆◆

distance solution using SRDF/A Support for device migration Integration with
ECA.
operations

operationsCascaded SRDF is a three-site disaster recovery solution where data
from a primary site is synchronously replicated to a secondary site, and then
asynchronously replicated from the secondary site to
tertiary site. The core benefit behind a cascaded configuration is its inherent
capability to continue replicating, with minimal user intervention, from the
secondahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ry site to the
tertiary site in the event that the primary site fails. This enables a faster
recovery at the tertiary site, provided that the tertiary site is where the
customer wishes to restart production operations. Cascaded SRDF uses dual-role
SRDF devices (R21 devices) on the secondary site which acts as both an R2 to the
primary site and an R1 to the tertiary site as shown in Figure 20 on page
58.Host Primary Secondary Tertiary
R1
SRDF/S
/A
20
SRDF configuration
the dual-role R21 devices require Enginuity 5773 and later, the secondary site
Symmetrix system has to be at this level. The primary or tertiary Symmetrix
systems may run other Enginuity levels compatible with Enginuity 5773. The
Cascaded SRDF solution complements the existing EMC’s three-site
configurations, Concurrent SRDF and SRDF/Star.
up a Caschttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8aded SRDF
relationship
up a Cascaded SRDF relationship is a two-step process: 1. Create the initial
R1–> R2 pair between primary site A and secondary site B for the first hop.
2. Set up the R1–> R2 pair between secondary site B and tertiary site C for
the second hop.Note: The above referenced steps are reversed for diskless R21
devices used in SRDF/EDP solutions.
21 on page 58 shows a Cascaded SRDF configuration.Primary Host SRDF/S R1 R21
SRDF/A R2 Secondary Tertiary
copy
copySYM-002129
2158
a Cascaded SRDF configuration
Cascaded SRDF
SRDF Multisite OperationsNote: Cascaded SRDF can also be implemented with

SRDF/Star. “Cascaded SRDF/Star” on page100 contains additional information.The
following SRDF modes are
allohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8wed in Cascaded
SRDF:◆R1 –> R2: SRDF/S, SRDF/A, Adaptive copy disk mode, Adaptive copy
write- pending mode◆R21 –> R2: SRDF/A, Adaptive copy disk mode.Note:
Adaptive copy disk mode is not allowed with diskless devices. “Diskless R21
devices” on page27 contains more information.The most common implementation is
for the first hop to be in SRDF/S mode, and the second hop to be in SRDF/A
mode.The benefits of Cascaded SRDF are:
◆Faster recovery times at the tertiary site enabled by the continuous

replication from the secondary site to the tertiary site in the event that the
primary site
.
: Single-session implementations continue replicating data from the secondary to
the tertiary site. User intervention is required in Multi-Session Consistency
environments. ◆Tight-integration with TimeFinder product family
◆Reduced RTOs
◆Cost savings — Only requires three full copies for operation

chttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ompared to four with
SRDF/AR. With SRDF/AR, secondary site and tertiary sites require BCV
◆Management capability using the current storage management portfolio of
software products.
◆Geographically dispersed secondary and tertiary sites.

following limitations apply to Cascaded SRDF:
◆Only one hop (R1 –> R21, or (R21 –> R2) can be Asynchronous at a
time◆Like Concurrent SRDF, the two SRDF mirrors of a R21 cannot be configured
using the same SRDF group.
operations59

Distance Protection
SRDF/Extended Distance Protection (EDP) functionality offers a long distance
disaster recovery (DR) solution. The SRDF/EDP is a three-site configuration that
requires Enginuity 5874 and later running on the secondary Symmetrix system and
Enginuity 5773 or 5874 and later running on the primary and tertiary systems.
Figure22http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 on page60
shows an SEDF/EDP configuration.
/EDP is achieved through a Cascaded SRDF setup, where a Symmetrix V-Max system
at a secondary site uses diskless R21 devices to capture only the differential
data that would be owed to the tertiary site in the event of a primary site
failure.
is the data on the diskless R21 devices that helps these configurations achieve
a zero Recovery Point Objective (RPO).
: SRDF/EDP is a licensed feature. Contact your EMC Sales Representative for
additional information on this feature.
/S
SecondaryTertiarySRDF/ADL
copyDiskless
device
(Not full copy-

only)Full copySYM-002130
SRDF/EDP basic configuration
: SRDF/EDP can also be implemented with SRDF /Star. “SRDF/EDP and SRDF/Star”
on page102 contains additional information.
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ts SRDF/EDP benefits
include:
◆A long distance replication solution with the ability to achieve zero RPO at
the tertiary site
lower cost solution when compared to three-site solutions such as Concurrent and
Cascaded SRDF
/Star differential relationship support between a primary site and the tertiary
site for failover operations.◆◆

site configurations
SRDF four-site configurations can be created during the process of migrating an
existing two-site disaster recovery solution to a new two-site data disaster
recovery solution, for example, to migrate from a DMX-based solution to a V-Max-
based solution. Four-site configurations allow disaster recovery support while
this migration is occuring.Previously, customers would use Concurrent SRDF to
migrate an existing two-site SRDF
configuhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ration to
replicate (migrate) from the existing primary array to the new primary array (A)
and then fully replicate between the new primary and new secondary array
(B).During the latter cycle, the production data would either be unprotected, or
production applications would need to remain down until the new primary and
secondary arrays were fully synchronized, providing full remote protection as
shown in Figure23 on page61.Primary site (R1)Secondary site
(R2)R11SRDF/SR2SRDF/AAR2Secondary site (R2)BPrimary site (R1)Secondary site
(R2)R1R2Full synchronizationSYM-002131Four-site disaster recovery (old
configuration)
site configurations61

four-site SRDF data migration, replicating from the existing primary array to
both the new primary array and new secondary array is performed simultaneously.
This enables a move to the new two-site configuration with minimal application
dowhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ntime, and with no
production data exposure as shown in Figure24 on page62.
site (R1)
/SNew Primary site (R1)R21

/ASRDF/A
R2
site (R2)Secondary site (R2)
Four-site disaster recovery (new configuration)

following are benefits of four-site solutions:
◆Fully protected migration of disaster recovery solutionsMinimal application

downtime.
4
Consistency
chapter describes the SRDF Consistency Group operations. Topics

include:◆Consistency
groups..........................................................................
............................. 64
Consistency Groups63
SRDF Consistency Groups

groupsSRDF/Consistency Group (SRDF/CG) is an SRDF
prodhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8uct offering
designed to ensure the dependent-write consistency of the data remotely mirrored
by SRDF/S operations in the event of a rolling disaster. Most applications, and
in particular database management systems (DBMSs), have dependent-write logic
embedded in them to ensure data integrity if a failure occurs either hardware of
software.
write operations
/CG is based on dependent-write operations. A dependent-write is a write, not
issued by an application until a prior, related write I/O operation is
completed. An example of dependent-write is a database update: 1. The DBMS
writes to the disk containing the transaction log. 2. The DBMS writes the data
to the actual database. 3. The DBMS writes again to the log volume to indicate
that the database update was made. In a remotely mirrored environment, data
consistency cannot be ensured if one of the writes is remotely mirrored, but its
predecessor washttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 not.
This could occur, for example, in a rolling disaster where a communication loss
occurs and affects only a subset of the devices involved in the remote copy
function. SRDF/CG prevents a rolling disaster from affecting data integrity at
the secondary site. When SRDF/CG detects any write I/O to a volume that cannot
communicate with its R2 (secondary) mirror, SRDF/CG suspends the remote
mirroring for all volumes defined to the consistency group before completing the
intercepted I/O and returning control to the application. In this way, SRDF/CG
prevents a dependent-write I/O from reaching the secondary site if the previous
I/O only gets as far as the primary mirror. I/O to the primary devices in the
consistency group can
occur even when the devices are Not Ready on the SRDF links. Such updates are
not immediately sent to the secondary site. However, they are propagated after
the affected links are again
operationalhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8, and data
transfer from the primary devices to the secondary devices resumes.
data consistency
an SRDF configuration consists of three Symmetrix systems with primary devices,
and two additional Symmetrix systems with secondary devices. The systems with
primary devices send data to the systems with secondary devices as shown in
Figure 25 on page 64.
1
2
3
1
2
25
and secondary relationships

, assume that the links between primary system 2 and secondary system 1 fail.
Without a consistency group, primary systems 1 and 3 continue to write data to
the secondary site systems 1 and 2 while primary system 2 does not as shown in
Figure 26 on page 65. The copy of
thehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 data spread across
secondary systems 1 and 2 becomes inconsistent.
1
2
3
1
2
26
links between primary system 2 and secondary system1
, if primary system 1, 2, and 3, belong to a consistency group, as shown in
Figure 27 on page 65, and the links between primary system 2 and secondary
system 1 fail, the consistency group automatically stops primary systems 1 and 3
from sending data to secondary systems 1 and 2, as shown in Figure 28 on page
65. Thus, the dependent-write consistency of the data spanning secondary systems
1 and 2 remains intact.Consistency group
1
2
3
1
2
27
systems 1, 2, and 3 in a consistency group
group
1
2
3
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ry 1
2
28
link between primary system 2 and secondary system 1Consistency groups65

SRDF/CG product requires specially configured Symmetrix devices to act in
and maintain data integrity. EMC host -based SRDF software provides the
used to configure and manage these devices.
more information about consistency groups and consistency group utilities, refer
:
◆EMC Consistency Groups for z/OS Product GuideEMC Solutions Enabler Symmetrix
SRDF Family CLI Product Guide.
5
/Synchronous
chapter introduces SRDF/Synchronous (SRDF/S). Topics include:
◆SRDF/S
overview........................................................................
...............http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8.......
........... 68
/Synchronous Operations67
29
6
/Asynchronous
chapter provides a technical overview of SRDF/Asynchronous (SRDF/A).

include:
◆SRDF/A
overview........................................................................
............................... 70
◆Development and
availability....................................................................
................ 72
◆Single session
mode............................................................................
......................... 75
◆Multi-Session Consistency (MSC)

mode................................................................... 83
/Asynchronous Operations69
SRDF/Asynchronous Operations
/A overview
/A provides a long distance disaster restart solution with minimal impact on
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8parperformance. This
solution is intended for customers requiring the ability to preserve
write consistency within and across the database and application
at an extended distance secondary site with minimal host application
. To achieve such high levels of data consistency, disaster-restart protection,
to maintain performance, SRDF/A provides functionality described in the
sections.
“Base SRDF family products” on page18 provides additional information.

: When using either TimeFinder/Clone BCVs or TimeFinder/Snap BCVs, special
must be followed.
/A is supported for open systems and mainframe hosts through EMC
based SRDF software. Consult the EMC Solution Enabler Symmetrix SRDF Family
Product Guide or the EMC SRDF Host Component for z/OS Product Guide for specific
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8imposed by host
platforms.
session modeSRDF/A single session mode refers to implementations where
individual SRDF/A
, whether in the same or multiple Symmetrix systems, have their cycle switch
independently by Enginuity rather than by EMC host-based SRDF control
.
“Single session mode” on page75 provides additional details.

Session
(MSC)
/A Multi-Session Consistency (MSC) mode is provided for installations where
multiple primary SRDF groups and multiple secondary SRDF groups require
consistency, thereby included in the same SRDF/A MSC session. In this
environment,
SRDF/A cycle switch is driven by EMC host-based SRDF software, to maintain
between multiple SRDF/A sessions operating in the SRDF/A single
mode.
“Multi-Session Consistency (MSC) mode” on page83 provides

http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8additional details.
CapacityWith Enginuity 5772, SRDF/A Reserve Capacity enhanced SRDF/A's ability
to
an operational state when encountering temporary network resource
that would have previously suspended SRDF/A operations. The two
that implement SRDF/A Reserve Capacity are Transmit Idle and Delta Set
(DSE).
Idle maintains SRDF/A in an active state after all SRDF network links have
. It allows SRDF/A to remain fully active during longer network outages that
All Links Lost conditions. When links return, SRDF/A resumes data transfer
it left off. Transmit Idle requires the following:
The Symmetrix systems on both sides of the SRDF links must be running at
Enginuity 5671
SRDF/A Transmit Idle must be enabled at both the primary and secondary
. Transmit Idle http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8is
enabled by default with Enginuity 5772 and later.
SRDF/A Transmit idle is not supported on ESCON SRDF directors.Transmit Idle
Delta Set Extension

Folding
PacingSRDF/Asynchronous OperationsFor EMC host-based SRDF software requirements,
consult the EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide or the
EMC SRDF Host Component for z/OS Product Guide.SRDF/A Delta Set Extension (DSE)
enables asynchronous replication operations to remain active if the Symmetrix
system approaches the system write-pending or SRDF/A maximum cache limits. This
functionality is achieved by offloading some or all of the active delta set data
into preconfigured storage pools known as DSE pools.Note: If DSE is enabled, EMC
strongly recommends that it be enabled at both sides of the SRDF/A
configuration. DSE pools are associated with
SRDhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8F groups. It is
necessary to have as many DSE pools associated with an SRDF group as there are
different device emulation types in the SRDF group. To support one DSE pool for
each emulation type, at most four DSE pools need be created (for FBA, IBMi,
CKD3380, and CKD3390).It is also possible to create multiple DSE pools for
different SRDF/A groups, according to user requirements or design objectives.
Consult your EMC Business Continuance Specialist for advice on how to best
implement DSE pools in your environment. Write Folding improves the efficiency
of the SRDF network links. If there are multiple data updates in the same cycle,
the systems send the most current data across the SRDF links. This is a major
advantage over competitive asynchronous replication solutions as it decreases
network bandwidth consumption and the number of I/Os the SRDF director
processes, thereby reducing the system overhead per host I/O.Write Pacing
ishttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 an Enginuity 5874
feature that provides the user a method of
conditions that result in cache overflow. This feature maintains SRDF/A’s
balance and avoids Symmetrix systems from reaching system write
limits. Write Pacing extends host I/O response times in order to balance the
host write I/O rate with the SRDF link bandwidth throughput capabilities.
Write Pacing algorithm provides a pacing mechanism to reduce the likelihood of
/A operational interruptions if the following configuration imbalance
occur:
◆The host I/O rate exceeds the SRDF throughput
◆The SRDF link transfer rate has become less than the incoming host write I/O
rate
◆The secondary side service rate has gone below the host I/O rate.
the primary and the secondary site must be running Enginuity 5874 or later.
/A must behttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 in the
active state for Write Pacing to function.
: Write Pacing does not require a separate license.
/A Write Pacing works concurrently with other SRDF/A features including
Set Extension (DSE), SRDF/A host throttling, Multi Session Consistency (MSC),
Transmit Idle.
SRDF/A Write Pacing is active when all SRDF links are lost and Transmit Idle is
, host write I/O continue to be paced at the same rate as it was all SRDF links
lost and Transmit Idle was invoked. If Transmit Idle is invoked prior to
reaching
/A overview71
/A Write Pacing cache usage levels, then SRDF/A Write Pacing prepare for
recovery, but host write I/O will not be paced until some or all of the SRDF
recover.
modeTolerance mode allows certain conditions to occur that would normally
chttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ause
in SRDF/A operation, for example, if the secondary devices become
/Write-capable. When tolerance mode is set to on, dependent-write consistency
not guaranteed. Tolerance mode is an SRDF/A feature that allows customers to
their performance and data consistency requirements.
default, SRDF control software does not allow an SRDF/A session participating in
Session Consistency (MSC) operations to have tolerance mode set to on.
mode can still be set in SRDF/A MSC environments. If it is set for any
/A group within the MSC configuration, it could lead to inconsistencies for the
MSC group.
host software implementations of tolerance mode are different for mainframe
open systems. The mainframe software exports the use of tolerance mode
, where the open systems software
externalihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8zes it
through consistency
/disabling options.
: The EMC Symmetrix SRDF Host Component for z/OS Product Guide and the EMC
Solutions
Symmetrix SRDF Family CLI Product Guide provide more details.
/A benefitsSRDF/A provides the following features and benefits:
◆Supports extended data replication with database and application

consistencyPromotes efficient link utilization resulting in lower link bandwidth
requirementsMaintains a dependent-write consistent point-in-time image on the
secondary (R2) devices
all current SRDF topologies (ESCON, FarPoint, point-to-point and switched fabric
Fibre Channel, and GigE)
no additional external storage devices
hosts listed in the EMC Support Matrix for CKD and FBA data emulation types
: For more information on supported host platforms, go to the EMC Support
Matrihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8x at
://www.mianfeiwendang.com or http://www.mianfeiwendang.com, or contact your EMC
Sales
.◆◆◆
◆Provides a performance response time similar to writing to non-SRDF

devicesAllows failover and failback capability between the primary and the
secondary sites.
and
and
Enginuity 5874, the following requirements and limitations apply to
SRDF/A:◆SRDF/A cannot be used in SRDF/AR solutions.Table7 describes the
highlights of SRDF/A development and availability.
SRDF/A development and availability summary (page 1 of 2)
/A feature or enhancement
/AFeature/enhancement descriptionAllowed a single static SRDF group to
participate in asynchronous
within a single
Symmetrixhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 system. This
SRDF/A group could
use Dynamic SRDF or participate in Concurrent SRDF
.
of SRDF/A Multi-Session Consistency (MSC) for
. The initial support was limited to a single static SRDF/A
per Symmetrix system, but multiple Symmetrix systems could
participate in an SRDF/A MSC configuration.
SRDF/A groups (up to 64, depending upon the configuration)
per Symmetrix system. Implicit in this feature was the ability
define a primary and secondary SRDF/A group within the same
system and therefore the ability to use SRDF/A with
operationsa.Enginuity version56705670.50Multi-Session Consistency
(MSC)5671Multiple SRDF/A SRDF groups per Symmetrix
SRDF/A Multi-Session Consistency, SRDF/A Multi-Session Consistency (MSC), for

mainframe and open
suphttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ported multiple
Symmetrix systems with no restrictions to
number of SRDF/A groups per Symmetrix operating in SRDF/A
mode. The SRDF/MSC feature now included the addition of
systems support and eased the existing restrictions
in Enginuity 5670.50 and later for Symmetrix SRDF
systems.
SRDF supportThis enhancement provided the ability to remotely mirror a group of
devices in SRDF/S mode to one secondary site and to another
extended distance site in SRDF/A mode. The same
device can be replicated synchronously using SRDF/S mode
one SRDF group and asynchronously using SRDF/A mode
another SRDF group.
feature enabled SRDF/A on SRDF groups that were created by
SRDF.
feature allowed the individual SRDF/A processes, single session
MSC, thttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8o set a maximum
cache usage limit to a percentage of the
write pending limit. In so doing, the user can effectively assign
priority to sessions, keeping SRDF/A active upon for as long as
resources allow.567156715671Dynamic SRDF supportTunable cache utilization
/A overview73
SRDF/A development and availability summary (page 2 of 2)
/A feature or enhancement
CapacityFeature/enhancement descriptionReserve Capacity enhanced SRDF/A's
ability to maintain an
state when encountering temporary network resource
that would have previously suspended SRDF/A operations.
SRDF/A Reserve Capacity functions enabled, additional
allocation could be applied to address temporary workload
, periods of network congestion, or even temporary network
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8outagesb. Reserve Capacity
includes the following key features:
Transmit Idle (available in 5771, but not with DSE)

Idle enables asynchronous replication operations to
active in the event all links are lost temporarily due to
outagesc.
Delta Set Extension

Set Extension (DSE) enables asynchronous replication
to remain active in the event system cache resources
approaching the system write pending or SRDF/A maximum
limit d.
Enginuity enhancement simplifies and reduces the time needed
perform existing software initiated recovery operations after an
/A drop.e
Pacing provides the user an additional method of extending the
of SRDF/A by taking corrective action to slow down host
I/O rates to match the slower service rate. This prevents
caches://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8parbeing overrun on
both R1 and R2 sidesEnginuity version57725773Transfer Log5874Write Pacingf
.Bidirectional operation within a single SRDF/A group is not supported. All
primary to secondary device operations within a single SRDF/A group
remained unidirectional. (“Bidirectional link configuration” on page37
contains additional information.)
.“Reserve Capacity” on page70 contains additional information.
.“Transmit Idle” on page70 contains additional information.
.“Delta Set Extension” on page71 contains additional information.
.“Transfer Log” on page81 contains additional information.
.“Single session mode” on page75 contains additional information.
session modeDifferent from traditional ordered write asynchronous approaches,
Symmetrix systems
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8implement asynchronous
mode host writes from the primary Symmetrix to the secondary Symmetrix system
using dependent-write consistent delta sets transferred in cycles:◆
delta set contains groups of write I/Os for processing, which are managed for
dependent-write consistency by the Enginuity operating environment. SRDF/A
transfers these sets of data using cycles of operation, one cycle at a time,
between the primary Symmetrix system and the secondary Symmetrix system.
◆
Enginuity 5x71 and later, multiple SRDF groups can be enabled for SRDF/A
operations within the same Symmetrix system. However, if multiple groups within
the same Symmetrix system are enabled for SRDF/A, these sessions operate without
knowledge of each other, or of SRDF/A sessions in other Symmetrix systems. To
manage multiple SRDF/A sessions that need to be consistent, a multisession mode
is required and EMC host-based SRDF
softwarehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 to performs
this multi-session management.“Multi-Session Consistency (MSC) mode” on page
83 provides additional details.
write consistency
write consistency is achieved through the processing of ordered SRDF/A delta
sets (cycles) between the primary Symmetrix system and the secondary Symmetrix
system: 1. The active cycle on the primary Symmetrix system contains the current
host writes or N data updates in the capture delta set. 2. The inactive cycle
contains the N-1 data set that is transferred from the primary Symmetrix system
to the secondary Symmetrix system. 3. The primary inactive cycle is the transmit
delta set and the secondary Symmetrix system inactive cycle is the receive delta
set. 4. The active cycle on the secondary Symmetrix system contains the N-2 data
update in the apply delta set. This is the guaranteed dependent-write consistent
image in the event of a disaster or failure.
Figuhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8re 30 on page 75
illustrates the delta sets and their relationships.Primary Symmetrix Secondary
Symmetrix
N Transmit N-1
N-2 Receive N-1
“active” cycle
“inactive” cycle
“active” cycle
30
/A delta sets and their relationships
session mode
Symmetrix SRDF director ensures dependent-write consistency within SRDF/A
obtaining the active cycle number from a single location in global memory and
it to each I/O. The director retains that cycle number even if a cycle switch
during the life of that I/O. This results in an atomic cycle switch process for
write sequences, even though it is not physically an atomic event
achttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ross a
of volumes. As a result, two I/Os with a dependent relationship between them
be in the same cycle, or the dependent I/O can be in a subsequent cycle.
session states
Ready stateSRDF/A single session mode can have the following states: Not Ready,
Inactive, and Active.When the SRDF environment is configured, and the SRDF links
become active and
, by default all SRDF volumes are in a Not Ready state. This means that all the
devices on the primary Symmetrix system are Not Ready on the SRDF links.
devices can be made Ready on the links by issuing the commands from the
host-based SRDF software. Once devices are Ready on the links, the session
to an Inactive state.
devices are Ready on the SRDF link while the SRDF/A session is Inactive. Host
are required to transition SRDF/A into an
Achttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8tive state. In order
to
SRDF/A to an inactive state, specific host control software command must
entered. Most of these commands maintain a dependent-write consistent copy on
secondary Symmetrix system and one of them (deactivate) does not. Enginuity
also place SRDF single sessions into the inactive state, depending upon certain
being met or error conditions being encountered.
active state is the normal running state of SRDF/A. The secondary Symmetrix
is either consistent or inconsistent.
secondary Symmetrix system is consistent once all of the previously owed tracks
the primary devices have been transferred to the secondary devices.
Specifically,
the last cycle containing this data is fully copied to global memory and in the
cycle (apply delta set) on the secondary Symmetrix system has
succehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ssfully been
. The consistent active state always represents a dependent-write consistent
of the data.
inconsistent active state represents previously owed tracks that have not yet
been
to the secondary Symmetrix system. Inactive stateActive state
session state
the state transition sequence from Not Ready, Inactive, to an Active state is
common when setting up SRDF/A, transitions from an Active state to a Not Ready
or
Inactive state can happen in response to certain conditions or host software
. The following sections provide same examples of these state transitions.
: If the session is in an Active state with an inconsistent secondary Symmetrix
system and
transferring accumulated updates, it is impossible to create a dependent-write
consistent
on the secondary Symmetrix
syshttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8tem with any method
of transitioning out of SRDF/A
.
an SRDF/A session is dropped, the devices participating in the SRDF/A
are placed in a Not Ready state on the SRDF links. The SRDF/A session
from the Active to the Not Ready state. This transition can be triggered by
if either error or system resource limit conditions are met, or if resource
conditions that are detected by Enginuity exceeding user set operating
are met, or by host software command.
Pend-drop
set switchingSRDF/Asynchronous OperationsData not yet sent from the capture and
transfer delta sets is marked as owed to the secondary Symmetrix. Also, if only
a partially completed receive delta set is detected on the secondary Symmetrix,
the data so far
rechttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8eived is marked as
owed to the primary Symmetrix (at Enginuity versions below 5773). This allows
for a consistent image of data to be re-synchronized from either system, in
either direction, according to user requirements. On Symmetrix systems are
running Enginuity 5773 or higher, the Transfer Log function changes this
behavior. “Transfer Log” on page81 contains further information.EMC recommends
to capture the resulting dependent-write consistent data with either a set of
BCVs or Clones prior to any resynchronization. During the resynchronization
activity the dependent-write consistent image at the secondary Symmetrix system
is compromised.Note: With Enginuity 5773 and later, the Transfer Log mechanism
improves operations in relation to recovery after an SRDF/A drop. “Transfer
Log” on page81 contains further information.Enginuity may drop an SRDF/A single
session mode if:◆The primary Symmetrix system write pending limit is
reahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ched or the SRDF/A
maximum cache value is exceeded◆Any secondary device is made not ready on the
SRDF links◆All links are lostand the Transmit Idle function is not enabledNote:
Tolerance mode may change the operating behaviors described above. “Tolerance
mode” on page72 provides additional information.These all result in a
dependent-write consistent image being preserved on the secondary Symmetrix
system.Another way of dropping an Active session and moving it into a Not Ready
state is to place the devices in a Not Ready state only at the end of the
current cycle. This transition can be triggered by Enginuity or host software.
Write pending tracks in the active cycle are converted to tracks owed on the
primary Symmetrix system only. By dropping SRDF/A on the cycle boundary using
the pend-drop mechanism, there are no owed tracks to be resolved from secondary
to primary Symmetrix systems upon resuming SRDF/A. “Transfer Log” on
pagehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd881 contains
additional information. Note: In multi-session environments, a single session
drop most often results in the corresponding MSC session drop.SRDF/A allows an
immediate session transition from Active to Inactive while leaving the SRDF
devices Ready on the links. Because the devices are left ready on the SRDF
links, data continues to flow and the dependent-write consistency of the data at
the secondary Symmetrix system is compromised. The capture and transmit delta
sets data are marked as owed tracks to the secondary Symmetrix system similar to
a resynchronization operation. These owed tracks are not dependent-write
consistent. Delta set switching is at the core of the SRDF/A active session
operation. This section
the process of delta set switching. The following is required before a
Symmetrix system cycle switch can occur:
session mode77
SRDF/Asynchronous
Operationshttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8
◆The transmit delta set must have completed data transfer to the secondary
Symmetrix system
minimum cycle time (single session mode) or minimum cycle target time (MSC mode)
must be reached
previous Apply delta set must have been completed.◆◆
the delta-set switching process:
.Write I/Os are collected in the capture delta set on the primary Symmetrix
. The previous cycle’s transmit delta set is completing the SRDF transfer to
receive delta set, which is the N-1 copy. The secondary Symmetrix system
delta set (N-2) is written to global memory, so that data is marked write
to the secondary devices.
.The primary Symmetrix system waits for the minimum cycle time to elapse and
transmit delta set to empty, meaning that all data has been transferred to the
Symmetrix system.
.Once these conditihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ons

are satisfied, the primary Symmetrix system sends a
message to the secondary Symmetrix system to begin the secondary
system cycle switch.
: The SRDF transfer is halted prior to the primary Symmetrix system cycle
switch. The
Symmetrix system cycle switch between the capture and transmit delta set is done
through Enginuity. This happens in unison with the secondary cycle switch.
.On the primary system, the new capture delta set is available to collect new
host
/Os. Before the secondary Symmetrix system cycle switch can occur, the
must be true:
The secondary Symmetrix system receives the commit message from the
Symmetrix system.
Apply delta set (N-2 copy) completes its write process marking the data write
to the secondary devices.
.Once the secondary Symmetrix

systehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8m receives the
commit message from the
Symmetrix system, the secondary Symmetrix system verifies the apply
set has been written. This occurs while the primary Symmetrix system is
the cycle switch between the capture and transmit delta sets.
.The next step is a delta set cycle switch on the secondary Symmetrix system
the receive (inactive) and apply (active) delta sets. This preserves the
write consistent copy at the secondary Symmetrix system prior to
the next dependent-write consistent copy.
.The secondary Symmetrix system sends an acknowledgement to the primary

system. The data in the apply delta set is written to cache. Figure31 on
shows the process.
Figure31
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8n mode
/S to SRDF/A
/A to SRDF/SSRDF/Asynchronous OperationsHost13a1.Capture delta set (DS)
collectsR133eapplication write I/ONCaptureApply2.Primary waits for the minimum
cycle 2dN2c3bN-2time, and for the Transmit DS to emptyTransmitReceiveN-
2R2a)Primary tells Secondary to commit the Receive N-1DS (begins Secondarystep 3
in unison)R122b, 4aN-1Nb)SRDF transfer halted2d42a3c3dN-2R2c)Primary cycle
switch occurs – Capture DS becomes the Transmit DSPrimary SymmetrixSecondary
Symmetrixd)New Capture DS available for Host I/O3.Secondary receives commit from
Primarya)Check if the data in Apply DS is restored (data marked write pending to
the R2 devices)b)Secondary cycle switch – Receive DS becomes Apply DS c)New
Receive DS available for SRDF transferd)Secondary sends Primary
acknowledgemente)Begin restore of Apply DS4.Primary receives acknowledgement of
Secondarycycle switcha)SRDF transfer
beginsSYhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8M-001274Delta
set switchingAn active SRDF/A session can transition to different modes of
operation, provided that the device group configuration settings allow such
transitions. An active SRDF/A session can switch to a a sync ho neurosis mode
(SDRF/S), Adaptive copy disk mode, or Adaptive copy write-pending mode. Session
mode switching can be triggered by Enginuity or EMC host-based SRDF
software.Note: It is recommended to capture a dependent-write consistent copy
(locally or remotely) on a set of BCVs or clones prior to switching session
modes.When switching from SRDF/S to SRDF/A operation verifies that all the
devices are Ready, and then moves the SRDF group to the SRDF/A Active state on
both the primary and secondary Symmetrix systems. As a result, the delta sets
are established on the primary and secondary Symmetrix systems and the SRDF/A
mechanism is enabled.If all devices are synchronized when switching from SRDF/S
to SRDFhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8/A mode and,
the secondary Symmetrix system shows a consistent state and the data is
dependent-write consistent.If some data is still owed to the secondary site,
there is no dependent-write consistency at the secondary Symmetrix system until
the last owed track is in the N-2 cycle (apply delta set). Note: SRDF/A is an
SRDF group-level feature; all devices assigned to an SRDF group set to operate
in asynchronous mode will operate in asynchronous mode when the SRDF/A state
becomes Active.With Enginuity 5x71 and above, it is possible to transition to
the SRDF/S mode from
/A without losing dependent-write consistency with Enginuity 5x71 and
. This is only allowed for SRDF/A single session mode. The following caveats
:
◆The transition is not immediate. Once a transition is requested, it may take

some time for SRDF/A mode to transition to SRDF/S mode
session mode79
SRDF/http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Asynchronous
Operati
◆
performance degradation occurs with synchronous mode while the transition takes
place The transition requires both Symmetrix systems to be running Enginuity
5x71 and later.
◆
: It is recommended to capture a dependent-write consistent copy (locally or
remotely) on a set of BCVs or Clones prior to performing this process.
copy write -pending to SRDF/A
the mode is set to SRDF/A from Adaptive copy write pending mode, all devices are
moved into the Adaptive Copy Pending Off mode. An SRDF/A session is activated
and the back-end directors scan devices for write-pending tracks and add them to
the active cycle (capture delta set). Once all write-pending data to the
secondary device has been written to cache in the secondary system, the primary
device can transition out of the Adaptive Copy Pending Off mode. When all
devices transition out
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8of the Adaptive Copy
Pending Off mode, wo cycle switches are required for the secondary Symmetrix
system to report a consistent state and to have its data dependent-write
consistent. When a host or Enginuity request mode switch from Adaptive copy disk
mode to SRDF/A mode, the transition is immediate. Tracks owed to the secondary
Symmetrix system as a result of Adaptive copy disk skew are scheduled as
resynchronization operations. These are copy I/Os scheduled by the back-end
director to be serviced by SRDF/A. Each cycle switch (new capture delta set)
limits the copy I/Os to 30,000 tracks to avoid using all of the cache in the
primary Symmetrix system. Host I/Os continue to be serviced in the current
SRDF/A cycles (capture delta set). The length of time to send the tracks owed
with asynchronous mode depends on the number of outstanding tracks owed prior to
switching to asynchronous mode. For example, 90,000 tracks owed take a
minhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8imum of three
SRDF/A cycle switches to transmit the data. There are another two cycle switches
required to ensure the data is in the apply delta set cycle, or the N-2 copy of
data. SRDF/A produces a consistent state on the secondary Symmetrix system and a
dependent-write consistent copy of data after all resynchronization operations
are complete and the two additional cycle switches have occurred. This section
briefly discusses the different recovery scenarios associated with SRDF/A single
session mode.“Transfer Log” on page 81 contains additional information. If
SRDF/A suffers a temporary loss (< 10 seconds by default) of all SRDF links,
the SRDF/A state remains active and data continues to accumulate in global
memory. This may result in an elongated cycle, but the secondary Symmetrix
system dependent-write consistency is not compromised and the primary and
secondary Symmetrix system device relationships are not suspended.
Ihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8f a customer wishes
to keep SRDF/A in an active state during all links lost conditions, SRDF/A
Transmit Idle should be used. See“Transmit Idle” on page 70. CAUTION Customers
switching to SRDF/S mode with the link limbo paramete
configured for more than 10 seconds could experience an application, database,
or host failure if SRDF is restarted in synchronous or semi-synchronous mode.
copy disk mode to SRDF/A
scenarios
all links lost
!
all links lost
SRDF/A experiences a permanent all SRDF links lost condition, it transitions all
of the devices configured to the SRDF group(s) where the devices were configured
to a
Session cleanup
LogSRDF/Asynchronous OperationsNot Ready state. This results in all data in the

ahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ctive and inactive
primary Symmetrix system cycles (capture and transmit delta sets) being changed
from write pending for the remote mirror to owed to the remote mirror. In
addition, any new write I/Os on the primary Symmetrix system result in tracks
being marked owed to the remote mirror. All of these tracks are owed to the
secondary Symmetrix system once the links are restored.The secondary Symmetrix
system inactive cycle (receive delta set) data is also marked owed to the remote
mirror. These are owed to the primary Symmetrix system. The active cycle (apply
delta set) data completes its commit to the secondary Symmetrix system
devices.Note: Enginuity 5773 Transfer Log changes this behavior somewhat.
“Transfer Log” on page81 contains additional information.When the links are
restored, normal SRDF recovery procedures are followed. The metadata
representing the data owed is compared and merged based on normal host recovery
procehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8dures used by EMC
host-based SRDF software. The data is then resynchronized by sending the owed
tracks as part of the SRDF/A cycles. Note: The data on non-consistency exempt
volumes, on the secondary Symmetrix system, is always dependent-write consistent
in SRDF/A active/consistent state, even when all SRDF links have failed.
However, the act of starting a resynchronization process compromises the
dependent-write consistency until the resynchronization is fully complete and
two cycle switches have occurred. For this reason, it is recommended a gold copy
of the dependent-write consistent image be saved using either a set of BCVs or
Clones on the secondary Symmetrix system.Once SRDF/A single session mode is
dropped, a cleanup process occurs automatically within Enginuity. The primary
Symmetrix system marks new incoming writes as being owed to the secondary
Symmetrix system. The primary Symmetrix system does a cleanup of the delta
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8sets; capture and
transmit. The capture and transmit delta sets are discarded, but the data is
marked as being owed to the secondary Symmetrix system. All of these owed tracks
are sent to the secondary Symmetrix system once SRDF is resumed if the copy
direction remains primary to secondary.The secondary Symmetrix system marks and
discards the receive delta set only. This data is marked as tracks owed to the
primary Symmetrix system. Once SRDF is resumed, these tracks are scheduled to be
sent from the primary Symmetrix system if the copy direction has not changed.
Note: The SRDF/A Transfer Log improves this cleanup operation. The following
sections contain information related to the SRDF/A Transfer Log.The secondary
Symmetrix system makes sure the apply (N-2) delta set is safely applied to disk;
this is the dependent-write consistent image. Note: It is very important to
capture a gold copy of the dependent-write consistent data
ohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8n the secondary
Symmetrix system R2 devices prior to any resynchronization. Any resync process
compromises the dependent-write consistent image. The gold copy can be stored on
a remote set of BCVs or Clones. The SRDF/A Transfer Log is available with
Enginuity 5773 or later. It allows SRDF/A
know which tracks in the transmit delta set has been successfully transferred to
the
delta set. The overall effect of this function is a significant increase in the
session mode81
of the SRDF/A recovery operations. It shortens the time required to recover from
an unplanned SRDF/A drop.
function requires Enginuity 5773 or later at both the primary and secondary
sites. The Transfer Log removes the need to manage invalid track information on
the secondary side marked as owed to the primary side after an SRDF/A unplanned
drop. Using the Transfer
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Log recovery involves
only two operations:
◆Make primary side remote devices ReadyActivate SRDF/A.

system global
full conditionIt is possible that an imbalance may occur with SRDF/A between the
incoming write I/O workload and the outgoing SRDF/A bandwidth, or the inability
to de-stage data
enough at the secondary Symmetrix system, such that the global memory in the
primary Symmetrix system becomes full.
inactive and active cycles (capture and transmit delta sets) on the primary
system consume all the available write memory in the Symmetrix system.In this
situation, SRDF/A behaves based on customer-configurable settings:◆The primary
Symmetrix system can throttle the host at the speed of the links, and keep
SRDF/A running. In this case the host performance is equivalent to
mode.
primary Symmetrix system throttles
thttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8he host for a
customer-defined specified period of time, and if the condition has not resolved
itself at the expiration of this time, then SRDF/A is dropped. The default
behavior is to drop SRDF/A
when this condition occurs.◆
: To avoid a memory full condition, the SRDF/A environment must be properly
designed and configured. Factors and variables that may cause an imbalance in
the SRDF/A
may include bandwidth, global memory, unbalanced primary and secondary Symmetrix
system configurations, and workload allocation for specific implementations.
your EMC Customer Service Representative to initiate a study of your environment
to avoid such an imbalance.
an effort to assist customers to better manage global memory full conditions,
Enginuity 5x71 introduced Tunable Cache Utilization. Reserve Capacity DSE helps
when global memory approaches capacity. “Reserve
Caphttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8acity” on page70
from
devicesIn the event that a disaster occurs on the primary Symmetrix system, the
data on the secondary Symmetrix system devices represents a dependent-write
consistent image
data that can be used to restart an environment. Once the primary Symmetrix
system has been repaired, the process for returning production operations to the
primary Symmetrix system uses exactly the same methods as those used for
synchronous SRDF failback operations.
the workload has been transferred back to the primary Symmetrix system hosts,
SRDF/A can be activated and normal asynchronous mode protection can be resumed.
the event of an extended failover event, the SRDF/A configuration can be
reversed using either Dynamic SRDF or a configuration change. SRDF/A can
continue
until a planned reversal of direction can be
perfohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8rmed in order to
restore the original SRDF/A primary/secondary relationship.
Session Consistency (MSC) mode
mode
write
software and Enginuity version 5670.50 and later support SRDF/A control for
multiple Symmetrix systems provided there is a single SRDF group per Symmetrix
system. Beginning with Enginuity 5x71 for mainframe and open systems, SRDF/A is
supported in configurations where there are multiple primary Symmetrix systems
or multiple primary Symmetrix system SRDF groups connected to multiple secondary
Symmetrix systems or multiple secondary Symmetrix systems SRDF groups. This is
referred to as SRDF/A Multi-Session Consistency (MSC). SRDF/A MSC configurations
can also support mixed open systems and mainframe data controlled within the
same SRDF/A MSC
seshttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8sion. Achieving
data consistency across multiple SRDF/A groups requires that the cycle switch
process described earlier in this chapter be coordinated among the participating
Symmetrix system SRDF groups or systems, and that the switch occur during a very
brief time period when no host writes are being serviced by any participating
Symmetrix system.Achieving this requires a single coordination point to drive
the cycle switch process in all participating Symmetrix systems. This function
is provided by the SRDF control software running on the host. I/Os are processed
exactly the same way in SRDF/A MSC mode as they are in single session mode:1.The
active cycle on the primary Symmetrix system contains the current host
or N data version in the capture delta set.
.The inactive cycle contains the N-1 data version that is transferred using
SRDF/A
the primary Symmetrix system to the secondary Symmetrix
shttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ystem. The primary
inactive delta set is the transmit delta set and the secondary Symmetrix
system’s inactive delta set is the receive delta set.
.The active cycle on the secondary Symmetrix system contains the N-2 data
on the apply delta set. This is the guaranteed dependent-write consistent image
in the event of a disaster or failure.
on page84 illustrates the delta sets and their relationships.
Session Consistency (MSC) mode83
Symmetrix
Symmetrix
Host
N Transmit N-1
N-2 Receive N-1
N Transmit N-1 Capture N Transmit N-1

N-2 Receive N-1 Apply N-2 Receive N-1
“active” cycle
“active” cyclehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8
32
/A MSC delta sets and their relationships
SRDF/A multi-session consistency
the host to control the cycle switch process, the Symmetrix systems must be
aware that they are running in multi-session consistency mode. This is done
using the SRDF control software running on the host. The host software:◆
the cycle switching for all SRDF/A sessions comprising the SRDF/A MSC
configuration Monitors for any failure to propagate data to the secondary
Symmetrix system devices and drops all SRDF/A sessions together to maintain
dependent-write consistency Performs MSC cleanup if able.
◆
: Simply activating SRDF/A does not place a session in multi-session mode.
Conversely, exiting multi-session mode does not drop or deactivate SRDF/A, it
merely places SRDF/A in single-session mode. However, if SRDF/A is dropped or
deactivatehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8d, then
multi-session mode (along with all SRDF/A single session modes comprising the
MSC session) is necessarily terminated and would need to be reentered once
SRDF/A was made active again.
part of the process to enter MSC mode, and with each cycle switch issued
thereafter, Enginuity assigns a cycle tag to each new capture cycle. That cycle
tag is retained throughout that cycle’s life. This cycle tag is a value that is
common across all participating SRDF/A sessions and eliminates the need to
synchronize the cycle numbers across them. The cycle tag is the mechanism by
which dependent-write consistency is assured. Figure 33 on page 85 updates the
SRDF/A state diagram from single session mode to incorporate multi-session mode
for SRDF/A.
session consistencyHost command or
Engihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nuity Remote site
consistent or inconsistent Host command Host command
ready (NR)All devices are Not Ready on the links
Host command or Enginuity Remote site consistent or inconsistent Host command
command
Synchronous or adaptive copy modesSYM-001279
33
/A MSC allowed state transitions
an SRDF/A MSC consistent cycle switch
/A MSC mode performs a coordinated cycle switch during a very short window of
time when th
are no host writes being completed. This time period is referred to as an SRDF/A
window, which is actually a flag (open/closed). The SRDF/A window is an
attribute of the SRDF/A group and is checked at the start of each I/O, at no
additional overhead, because the front-end director is already obtaining the
cycle number from global memory as part of the existing overhead incurred by
SRDF/A operations.
Whehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8n the host software
discovers that all the SRDF groups and Symmetrix systems are ready for a cycle
switch, it issues a single command to each SRDF group that performs a cycle
switch and opens the SRDF/A window. The front-end director to obtains the cycle
number at the start of each write in single session mode. In multi-session mode,
the front-end director also checks the SRDF/A window flag, and if it is on (an
open window); it disconnects upon receiving host write I/O and begins polling to
determine when the SRDF control host software has closed the window. While the
window is open, any write I/Os that start are disconnected and as a result no
dependent-write I/Os are issued by any host to any devices in the SRDF/A MSC
session. The SRDF/A window remains open on each SRDF group and Symmetrix system
until the last SRDF group and Symmetrix system in the multi-session group
acknowledges to the host software that the open and
switchhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 command has
been processed. At this point the host software issues a close command for each
SRDF/A group under MSC control. As a result, dependent-write consistency across
the SRDF/A MSC session is ensured.Note: Enginuity does provide a fail-safe
mechanism to ensure that the SRDF/A MSC window does not remain open permanently
due to a host software failure. Enginuity closes the SRDF/A MSC window itself if
the host software has not closed it within 15 seconds.
Session Consistency (MSC) mode delta set switching
section describes how the delta set switching works for SRDF/A MSC mode. This
next series of figures represent three SRDF/A single sessions combined together
to create a single SRDF/A MSC group. There are two primary Symmetrix systems,
one with a single SRDF/A group and the other with two SRDF/A
ghttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8roups. The secondary
Symmetrix systems are the same configuration as the primary, which is a balanced
configuration. Figures 34 through 43 assume SRDF/A MSC has been activated and
two cycle switches have previously occurred. Before a primary Symmetrix system
cycle switch can occur, two things must be achieved:◆◆
primary Symmetrix system’s transmit delta set must be empty The secondary
Symmetrix system’s apply delta set must have completed marking the R2 devices
write pending for the N-2 data.
34 on page 86 displays the current host I/O being collected by the capture delta
set on the primary Symmetrix system. The primary Symmetrix system transmit delta
set is continuing to send the data to the secondary Symmetrix sys
receive delta set. The apply delta set is continuing to restore, or mark the
data write pending to the secondary Symmetrix system R2 devices.1R1 N Host R1
NApply N-2 Receive N-http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd81
N Transmit N-1
N-2R2 N-2
. Capture delta set (DS) collects application write I/Os
R1 NCapture N Transmit N-1 Capture N Transmit N-1 Apply N-2 Receive N-1 Apply N-
2 Receive N-1
N-2
N
N-2
Symmetrix
Symmetrix
34
/A MSC capture delta set collects application write I/O

35 on page 87 shows that SRDF transfer between the primary Symmetrix system
transmit delta set and the secondary Symmetrix system receive delta set is
complete (step 2a).1R1 NApply N-2 Receive N-1
. Capture DS collects application write I/O R2 N-2 2. Primary Transmit DS

complete a) Primary sends Secondary‘ Transmit complete’ message
N Transmit
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8aR2 N-2
N
R1 NCapture N Transmit Apply N-2 Receive N-1 Apply N-2 Receive N-1
N-2
R1 NCapture N Transmit
aR2 N-2
Primary Symmetrix
Symmetrix
35
/A MSC primary Symmetrix system transmit delta set is emptied
primary Symmetrix system halts the SRDF transfer and sends a transmit complete
message to the secondary Symmetrix system as shown in Figure 36 on page 87. The
secondary Symmetrix system stores the information, which is used during cleanup
(if SRDF/A drops), and sends an acknowledgement back to the primary Symmetrix
system (step 2b).1R1 N 2b R1 NApply N-2 Receive N-1
. Capture DS collects application write I/O R2 N-2 2a R2 N-2 2. Primary Transmit

DS complete a) Primary sends Secondary‘ Transmit complete’ message b) Primary
waits for acknowledgement from Secondary c) SRDF transfer
hhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8alted
N Transmit
R1 N 2b R1 NCapture N Transmit
c
N-2 Receive N-1
N-2 2a R2 N-2
Capture N Transmit
c
N-2 Receive N-1
Primary Symmetrix
Symmetrix
36
/A MSC primary Symmetrix system halts the SRDF transfer
secondary Symmetrix system apply delta set completes the restore process by
marking the data write pending to the R2 devices (step 3) as shown in Figure37
on page88. When completed, the secondary Symmetrix system sends a restore
complete message to the primary Symmetrix system (step 3a).
b
NCaptureN31.Capture DS collects
applichttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ation write
I/O2a2cApplyReceiveN-1R2N-222.Primary Transmit DS completea)Primary sends
Secondary ‘Transmit complete’messageb)Primary waits for acknowledgement
Secondary
)SRDF transfer halted
.Secondary completes Apply DS (N-2)

(data marked write pending to
R2 devices)
)Secondary sends Primary “restore
”message3aR2N-21R1N2b
NCaptureN32a2c2a
cApplyReceiveN-1ApplyReceiveN-13aTransmit2CaptureNR2N-2R2N-2
SymmetrixSecondary SymmetrixSYM-001258
SRDF/A MSC secondary apply delta set restore complete
the primary Symmetrix system receives the restore complete message from the
secondary Symmetrix system (step 3a), the primary Symmetrix system responds to
polls from the SRDF/A MSC host software with a ready to switch condition. Again
this is because the primary Symmetrix system transmit delta set is
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8empty and the
secondary Symmetrix system apply delta set has completed the restore process
(step
). The SRDF/A MSC host software initiates a primary Symmetrix system cycle
once all of the participating SRDF groups in the SRDF/A MSC configuration report
a ready to switch state.
on page88 displays this primary Symmetrix system cycle switch between the
capture and transmit delta set. The SRDF/A MSC host software that is
the cycle switch and the process is explained in detail in “Performing an
SRDF/A MSC consistent cycle switch” on page85. The write I/O is deferred long
enough for the host software to coordinate the cycle switch across all SRDF
groups and the primary Symmetrix system (step 5a).
N3aCapture
.Capture DS collects application write I/O2.Primary Transmit DS

completea)Primary sends Secondary ‘Transmit
complehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8te’messageb)Pri
mary waits for acknowledgement from Secondary
)SRDF transfer halted
.Secondary completes Apply DS (N-2)

(data marked write pending to
R2 devices)
)Secondary sends Primary “restore
”message
.At next host poll, Primary will respond
“ready to switch”(Transmit complete

Apply restore complete both true)
.“Switch/Open”receive from host

)Primary cycle switch occurs while I/O
–Capture DS becomes the
DSSYM-00125954R1N5a2c2aR2N-2R2N-22TransmitN2b1R1N2bCaptureN33a2cApplyReceiveN-
15a4R1N2NCaptureNR2N-22a2cApplyReceiveN-15a2TransmitNR2N-2Primary
SymmetrixSecondary Symmetrix
SRDF/A MSC primary Symmetrix system cycle switch while I/O is deferredEMC
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8r[此处图片未下载成功]
Figure39
SRDF/Asynchronous OperationsThe primary Symmetrix system allows the deferred
I/O, and a new capture delta set accepts the host I/O (step 5b) as shown in
Figure39 on page89. The transmit delta set contains the N-1 copy of dependent-
write consistent data. 131.Capture DS collects application write
I/OR13a2.Primary Transmit DS completeNCapturea)Primary sends Secondary
‘Transmit 55b4NApply5aR2complete’messageTransmitReceiveb)Primary waits for
acknowledgement N-2from SecondaryR12N-12cNc)SRDF transfer
halted2b2aR25b3.Secondary completes Apply DS (N-2) 13restore (data marked write
pending to the R2 devices)Capture3aR1Na)Secondary sends Primary “restore
N45a2cApplycomplete”message5b2TransmitReceiveN-1R22aN-24.At next host poll,
Primary will respond “ready to switch”(Transmit complete R1CaptureApplyNNand
Apply restore complete both true)2b5a5bTransmit2cR25.“Switch/Open”receive from
host2N-1Rhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8eceiveN-
2a)Primary cycle switch occurs while I/O deferred –Capture DS becomes the
Primary SymmetrixSecondary SymmetrixTransmit DSb)I/O released -New Capture DS
available for Host I/OSYM-001260SRDF/A MSC I/O is released and a new capture
delta set continues to accept host I/OThe primary Symmetrix system sends a
commit message to the secondary Symmetrix system (step 6) once the primary
Symmetrix systems cycle switch occurs (step 5a). After receiving the commit
message the secondary Symmetrix systems perform a cycle switch between the
receive and apply delta sets (step 6a), as shown in Figure40 on
page89.131.Capture DS collects application write I/O3aR12.Primary Transmit DS
completeNCaptureApplya)Primary sends Secondary ‘Transmit 5bN5a6aN-
2R2complete’message54TransmitReceiveb)Primary waits for acknowledgement 2N-1N-
2from SecondaryR12cN2bR2c)SRDF transfer halted2a5b63.Secondary completes Apply
DS (N-2) 13restore (data marked write
phttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ending to the R2
devices)Capture3aR1Na)Secondary sends Primary “restore N5a6aN-
2complete”message5bTransmit2cReceiveN-12aN-2R24.At next host poll, Primary will
respond 42CaptureApply“ready to switch”(Transmit complete R1N5a6aN-2and Apply
restore complete both true)N2b5bTransmit2cReceiveR25.“Switch/Open”receive from
host2N-16N-2a)Primary cycle switch occurs while I/O deferred –Capture DS
becomes the Primary SymmetrixSecondary SymmetrixTransmit DSb)I/O released –
New Capture DS available for Host I/O6.Secondary receives commit message from
Primarya)Secondary cycle switch –Receive DS becomes Apply DS SYM-001261SRDF/A
MSC secondary Symmetrix system cycle switch
secondary Symmetrix system now has a new receive delta set available (step 6b)
as shown in Fihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8gure41
on page90.
N3aCapture
.2.Capture DS collects application write I/OPrimary Transmit DS
completea)Primary sends Secondary ‘Transmit complete’message
)Primary waits for acknowledgement
Secondary
)SRDF transfer halted55b4R1N5a2TransmitN-12c2a6aR2Receive6b2bR2
.5b
N2b63CaptureN3a
a5a6aN-2Secondary completes Apply DS (N-2) restore (data marked write pending to

the R2 devices)a)Secondary sends Primary “restore complete”message“ready to
switch”(Transmit complete
Apply restore complete both true)5b4R1N2TransmitN-1CaptureNReceiveR26bApplyN-
24.At next host poll, Primary will respond 5a
b2TransmitN-12c6aReceiveR2
b
SymmetrixPrimary Symmetrix5.“Switch/Open”receive from hosta)Primary cycle
switch occurs while I/O deferred –Capture DS becomes the Transmit DS
–b)I/O released Newhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8

Capture DS available
Host I/O
.Secondary receives commit message

Primary
)Secondary cycle switch –Receive DS
Apply DS
)New Receive DS available for SRDF transfer
SRDF/A MSC secondary Symmetrix system new receive delta set is available
Figure42 on page90, the SRDF transfer process begins from the primary
systems to the secondary Symmetrix systems (step 6c).
a
NCapture
.2.Capture DS collects application write I/OPrimary Transmit DS
completea)Primary sends Secondary ‘Transmit complete’message
)Primary waits for acknowledgement
Secondary
)SRDF transfer halted55b4R1N5a6aR22TransmitN-12a, 2c, 6cReceiveN-16b2bR2
.5b
N63CaptureN3a5a6aN-2Secondary completes Apply DS (N-2) restore (data marked

write pending to the R2
devihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ces)a)Secondary
sends Primary “restore
”message
“ready to switch”(Transmit complete

Apply restore complete both true)5b242bR1NTransmitN-16Capture2a, 2c,
6cNReceiveN-1ApplyN-2R26bR24.At next host poll, Primary will respond 5a6a
b2TransmitN-12a, 2c, 6cReceiveN-16b

SymmetrixSecondary Symmetrix5.“Switch/Open”receive from hosta)Primary cycle
switch occurs while I/O deferred –Capture DS becomes the Transmit DS
)I/O released – New Capture DS available
Host I/O
.Secondary receives commit message

Primary
)Secondary cycle switch –Receive DS
Apply DS
)New Receive DS available for SRDF transfer
)SRDF transfer begins
SRDF/A MSC primary Symmetrix systems begin SRDF transfer
[此处图片未 http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 下载成功]
Figure43
Session
(MSC)
cleanup
SRDF/Asynchronous OperationsThe secondary Symmetrix systems also begin the apply
delta set restore process (step 6d) and the process begins again as shown in
Figure43 on page91. 16d1.Capture DS collects application write I/O3aR132.Primary
Transmit DS completeNCaptureApplyN6aN-2R2a)Primary sends Secondary ‘Transmit
5b5aN-2complete’message54TransmitReceiveb)Primary waits for acknowledgement N-
16bfrom SecondaryR12N-1NR2c)SRDF transfer halted5b2a, 2c, 6cN-263.Secondary
completes Apply DS (N-2) 136drestore (data marked write pending to the R2
devices)Capture3aR1Na)Secondary sends Primary “restore N5a6aN-
2ReceiveR2complete”message5bTransmitN-2At next host poll, Primary will respond
42N-16N-16b4.CaptureApply“ready to switch”(Transmit complete R1N2a, 2c,
6c5a6aN-2R2and Apply restore complete both true)NN-25.“Switch/Open”receive
frhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8om
host5bTransmitReceive2N-12a, 2c, 6cN-16ba)Primary cycle switch occurs while I/O
deferred –Capture DS becomes the Primary SymmetrixSecondary SymmetrixTransmit
DSb)I/O released –New Capture DS available for Host I/O6.Secondary receives
commit message from Primarya)Secondary cycle switch –Receive DS becomes Apply
DS b)New Receive DS available for SRDF transferc)SRDF transfer beginsd)Begin
Secondary Apply DS restoreSYM-001264SRDF/A MSC secondary Symmetrix system begins
the apply delta set restore processWhen SRDF/A is deactivated or dropped while
in multi-session consistency mode, each R1 Symmetrix system starts the same
cleanup process as in single session mode: it discards all I/O from both the
transmit and capture delta sets and marks the corresponding tracks owed to the
secondary Symmetrix system. “Transfer Log” on
host software does not need to perform any special
rechttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8overy on the
primary Symmetrix system.
at the secondary Symmetrix system completes the restore of its apply delta set
automatically. For each SRDF group, Enginuity discards any receive delta sets
that are not complete. If the receive delta set is a complete delta set for each
SRDF group Enginuity marks it as “needing cleanup” in cache, awaiting a
decision from the host software.
is where SRDF/A MSC uses the host cycle tags. The host software must use its
cycle tags during recovery of the receive delta sets on the secondary Symmetrix
. There are three different scenarios to be considered when SRDF/A has been
terminated with respect to the receive delta sets on the secondary Symmetrix
system. This is determined by the following rules.
the first case, all receive delta sets on all secondary Symmetrix systems and
SRDF groups have the same tag and are marked as needing cleanup.This
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8is the result of the
secondary Symmetrix system receiving and acknowledging the transmit complete
message in step 2 of the SRDF/A MSC cycle switch process.
this case, the host software may choose to either commit all of the receive
delta sets or discard all of the receive delta sets. The default behavior
commits all of the receive delta sets to deliver the most current dependent-
write consistent data to the secondary Symmetrix system devices.
the second case, all receive delta sets on all Symmetrix systems have the same
tag number, but at least one Symmetrix systems or SRDF/A group does not have a
receive delta set marked needing cleanup. This means Enginuity discarded an
incomplete receive delta set.
host software must discard all receive delta sets for this tag number in this
case. The most current data is
alreadyhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 on the
secondary Symmetrix system devices using the apply delta set. The data that was
in the discarded receive delta sets are marked as tracks owed to the primary
Symmetrix system devices. “Transfer Log” on page81 contains additional
information.
third case occurs where there are different cycle tags within the apply and
receive delta sets. In this case, the secondary Symmetrix system SRDF/A sessions
can be divided into two groups. The first group has Symmetrix systems with apply
delta set cycle tags that match the receive delta set cycle tags of the
Symmetrix systems from the second group. In other words, Symmetrix systems from
the first group have received the commit message for a certain host cycle, while
the Symmetrix systems from the second group have not. In this case, the receive
cycles of the Symmetrix systems from the second group are necessarily complete
and the host software must force their restore. At
thttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8he same time, host
software must discard the receive delta sets of the Symmetrix systems from the
first group regardless of their completeness.
optionThe consistency exempt option is provided for an SRDF/A environment to

indicate that the volume should be considered exempt from the consistency
requirements for
session. This allows dynamic expansion of devices participating in an SRDF/A
session without taking the SRDF/A group offline or declaring the entire SRDF/A
group inconsistent (or setting Tolerance mode on), while maintaining
consistency.In normal operation, SRDF/A provides a consistent copy of the data
on the R2 side. However, if there are tracks that need to be copied as part of
an initial
operation, the data is not consistent until those tracks have been copied to the
remote Symmetrix system. Also, when new SRDF device pairs are created, a full
synchronizhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ation is
required. As a result, adding new SRDF devices to an existing SRDF/A group
causes the group to appear inconsistent.
solve this problem, the consistency exempt option is available to allow a new
to be excluded from the consistency check until the tracks have been copied to
the remote Symmetrix system. When the devices are added to the SRDF/A group in
consistency exempt mode, the CEXMPT indication has to clear before those devices
can be used or considered part of the consistent image.
7
/Star Operations
chapter provides an overview of SRDF/Star. Topics include:
◆SRDF/Star
overview........................................................................
............................ 94◆How SRDF/Star
works...........................................................................
....................
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd896◆Concurrent
SRDF/Star.......................................................................
......................... 98◆Cascaded
SRDF/Star.......................................................................
.......................... 100◆SRDF/EDP and
SRDF/Star.......................................................................
............... 102
/Star Operations93
SRDF/Star Operations
/Star overview
/Star is a three-site disaster recovery solution that consists of a primary
system and two remote Symmetrix systems. In the event of a primary site outage,
EMC's SRDF/Star solution allows customers to quickly move operations and re-
establish protection between the remaining sites. Once conditions permit,
customers can quickly rejoin the primary site to the configuration, resuming
SRDF/Star.
/Star can operate in concurrent or cascaded environments,
providinghttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 the
appropriate differential synchronization. These environments address different
recovery and availability objectives:
◆Concurrent SRDF/Star positions the secondary site or the remote site as

potential recovery sites, and provides differential resynchronization between
the secondary
remote sites. To achieve this positioning, some level of reconfiguration
is required to access point-of-disaster data. “Concurrent SRDF/Star” on page98
SRDF/Star positions only the remote site as the recovery site with minimal
intervention to access point-of-disaster data. This solution differentially
synchronizes data between the primary site and the remote site. “Cascaded
SRDF/Star” on page100 contains additional information.◆
/EDP can also be used in SRDF/Star configuration. “SRDF/EDP and SRDF/Star” on
page102 contains additional information.
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8parSRDF/Star provides for
rapid reestablishment of cross-site protection in the event of the primary site
failure. Rather than a full resynchronization between the remote sites,
SRDF/Star provides differential synchronization between the remote sites, and
dramatically reduces the time it takes to remotely protect the new production
site. SRDF/Star also provides a mechanism to determine which remote site has the
most current data in the event of a rolling disaster that affects the primary
site.
all cases, users maintain the ability to choose which site to operate from and
which site’s data to use when recovering from a primary site failure. Figure44
on page94 shows an SRDF/Star configuration.
site A
/SynchronousSecondary site BR2

/AynchronRecoverylinksous
site C
Legend:
Concurhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8rent SRDF
configured for SRDF/Star supportEMC Symmetrix Remote Data Facility (SRDF)
Product Guide
Benefits
/Star OperationsIn a Concurrent SRDF/A configuration without the SRDF/Star
functionality, the loss of the primary site would normally cause the long
distance replication to stop and data would no longer propagate to the remote
site. Data at the remote site would continue to age as production would be
resumed at the other remote site. Setting up the SRDF/A operations between the
remote sites requires a full resynchronization to achieve disaster recovery
protection. The SRDF/Star solution offers avoids this full resynchronization by
allowing the customers to differentially synchronize the remote sites. SRDF/Star
supports the SRDF personality swap between the primary site and the synchronous
remote site. In addition, SRDF/Star allows the SRDF/A relationships to be
transferred to remote sites
durhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ing planned
outages. These SRDF/A relationship transfers require no data movement.SRDF/Star
provides the following features and benefits:◆The ability to maintain
protection and business continuance despite the loss of any site in a three-site
configuration.◆The ability to resume asynchronous protection between the two
secondary sites, with minimal data movement, in the event of a primary site
failure.◆EMC host-based SRDF software support for control functions. Note: The
EMC Solutions Enabler Symmetrix SRDF CLI Product Guide and the EMC Symmetrix
SRDF Host Component for z/OS Product Guide contain additional information.It is
strongly recommended that all SRDF devices be locally protected and that there
capacity allocated for one replica (BCV, Snap, or Clone) at the primary
(production) site and remote sites in the configuration.
Enginuity 5874, the following requirements apply to SRDF/Star:
◆All SRDF/Sthttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ar device

pairs must be of the same geometry and size
◆All SRDF groups including inactive ones must be defined and operational prior
to entering SRDF/Star mode.
/Star overview95
SRDF/Star works
: Descriptions of states and events in this chapter are from the primary (R1)
point of view unless otherwise noted.
SRDF/Star is a three-site disaster-restart solution (A, B, C) that provides
differential resynchronization between sites B and C and a restart at either
site. SRDF/Star supports the following scenarios:
◆Normal operation — This refers to session management and differential B-to-C

or C-to-B resynchronization in SRDF/Star configurations.
switchovers — This refers to host-based automation executed at the synchronous
remote site to reconfigure SRDF/Star in support of planned site switchovers
between the synchronous SRDF
sites.://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8parfailovers — This
refers to host-based automation executed at the remote site to perform SRDF/Star
reconfiguration.
normal operation, devices at site A are in SRDF/S relationship with devices at
site B and in Concurrent SRDF/A relationship with devices at site C. SRDF
Consistency Group is required between site A and site B and an active host is
required at site A. A host is also required at either site B or site C for
recovery processing if site A fails. Host automation is required to reconfigure
SRDF/Star after a switchover of a disaster restart event.
planned switchovers are performed, BCVs are required at all three sites to
retain any consistency images created either during a planned or unplanned
event.◆◆The following is required in SRDF/Star configurations:◆◆
/Star control for
host-based Multi-Session Consistency (MSC) task at the primary (R1) site
controls http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8normal
SRDF/Star operation. MSC performs session management at the
/S site B and when necessary at the SRDF/A site C. The MSC session management
task maintains the information needed to perform differential synchronization
between site B and site C.
Host Component, Consistency Group, support utilities, and documented procedures
are also available to customers to resynchronize sites and manage
reconfigurations.
: Automation for SRDF/Star mainframe configurations is provided by EMC GDDR.
“Geographically Dispersed Disaster Restart” on page122 contains additional
information.
/Star control for
systemsSolutions Enabler software controls, manages, and automates the SRDF/Star
processes at site A through its symstar command. Session management is required
at
A and when necesshttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ary
at site B. The host software and Enginuity maintain the
needed to perform the differential synchronization between site B and
C.
based automation is provided for normal, transient fault, unplanned switch,
planned switch operations. This automation is delivered in Solutions Enabler
the SRDF/Star license. Detailed descriptions and implementation guidelines can
found in the EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide.
SRDF/Star works97
SRDF/StarIn Concurrent SRDF/Star operations, site B serves as the secondary site
and the target of the SRDF/S links from site A. Site C serves as the tertiary
site and the secondary site of the SRDF/A links from site A. The recovery links
are the SRDF/A links between site C and site B. Figure 45 on page 98 shows a
Concurrent SRDF/Star
configurathttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ion.Primary
site (A) Secondary site (B)
/Synchronous
/Asynchronous
/A (recovery links)
Inactive
of region site C
45
SRDF/Star configuration Note: The Concurrent SRDF/Star configuration requires
Enginuity version 5671 and later at the three sites and a current SRDF/Star
license.
SRDF/Star with R22 devices
5874 supports Concurrent SRDF/Star configurations using concurrent R22 devices.
Figure 46 on page 99 shows an R22 device at the asynchronous target site that
has two remote mirrors, only one of which is allowed to be active on the links
at a given time. R22 devices simplify failover situations in SRDF/Star
configurations, improve the resiliency of the SRDF/Star application, and reduce
the number of steps involved in failover procedures, thus enabling the command
sequences to http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8finish
quicker. R22 devices can also be used in Cascaded SRDF/Star
operations.“Cascaded SRDF/Star” on page 100 provides additional
information.Note:“R22” on page 26 provides more information abou
the R22 device type.
site (A)
target site (B)
/Synchronous
/Asynchronous Active Inactive

/A (recovery links)
taget site (C)
46
R22 SRDF/Star configuration
SRDF/Star
SRDF/StarA base Cascaded SRDF configuration can be enhanced using SRDF/Star
differential resynchronization functionality. SRDF/Star in a Cascaded SRDF
configuration offers the ability to differentially
synchrohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nize and
protect the Symmetrix systems at the primary site and the out of region site
(the long-distance asynchronous site) in the event the secondary site (the
synchronous site) fails. Cascaded SRDF/Star has the ability to incrementally
establish an SRDF/A session between the primary and the asynchronous site in the
event the synchronous site fails. With Cascaded SRDF/Star, the synchronous
secondary site is always more current than the asynchronous secondary site.
Figure 47 on page 100 shows a basic Cascaded SRDF/Star configuration. Site B
serves as the secondary site and the target of the SRDF/S links from site A.
Site C serves as the out of region site and the secondary of the SRDF/A links
from site B. The recovery SRDF/A links are between site C and site A.Primary
site (A) Secondary site (B)
/Synchronous
Inactive SRDF/A (recovery links) SRDF/Asynchronous

of region sithttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8e C
47
SRDF/Star configuration
SRDF/Star uses dual-role SRDF R21 devices at site B that act as both secondary
devices to site A devices and as primary devices to site C devices. Cascaded
SRDF/Star provides a mechanism to determine when current active R1 cycle
(capture) contents reach the active R2 cycle (apply) over the long-distance
SRDF/A links. This minimizes the amount of data that must be moved between sites
B and C to fully synchronize them.Note: The Cascaded SRDF/Star configuration
requires Enginuity version 5773 and later at site A and site B.
SRDF/Star with R22 devices
48 on page 101 shows Cascaded SRDF R22 mode operation. This mode has the same
configuration as the basic Cascaded SRDF/Star but uses R22 devices
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8at the asynchronous
site C. The site A to site C relationship is passive and is referred to as the
recovery path.Note:“R22” on page 26 provides more information about the R22
device type.
site (A)
secondary site (B)
/Synchronous
Inactive
/A (recovery links)
/Asynchronous
secondary site (C)
48
R22 SRDF/Star configuration
the following when creating a Cascaded SRDF/Star configuration with R22
devices:◆
devices at the primary site must be configured as concurrent (R11) devices with
one mirror paired with the
R21 device (synchronous secondary site) and the other mirror paired with the
remote mirror at the asynchronous secondary site. All devices at the synchronous
site must be configured as R21 devices paired with a remote
partnehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8r at the primary
site and a remote partner at the asynchronous site. All devices at the
asynchronous site must be configured as R22 devices paired with an R21 remote
partner at the synchronous site and an R11 remote partner at the primary site.
◆
SRDF/Star
/EDP and SRDF/StarEnginuity 5874 supports SRDF/Extended Distance Protection
(EDP) configurations in SRDF/Star environments.Note:“Extended Distance
Protection” on page 60 provides detailed information on the use of diskless R21
devices for SRDF/EDP functionality.
/EDP is mainly used with Cascaded SRDF/Star. Figure 49 on page 102 illustrates a
Cascaded SRDF/Star EDP diskless environment with the remote devices at the
asynchronous secondary site. The diskless R21 device streamlines the link
connections to the asynchronous site in cascaded mode. No data copies are
available ahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8t the
synchronous site B that uses diskless devices.Primary site (A) Synchronous
secondary site (B) (diskless DL Dev)
/Synchronous
Inactive
/A (recovery links)
/Asynchronous
secondary site (C)
49
SRDF/Star EDP (diskless) configuration with an R2 site
for diskless SRDF/EDP with SRDF/Star
following requirements apply to diskless SRDF/EDP implementations with
SRDF/Star:◆
minimum of Enginuity 5874 is required at the synchronous secondary site
containing the diskless devices, and Enginuity 5773 or later is required at the
other sites. All devices at the primary site must be configured as R1 devices
paired with the R2 mirror of the diskless R21 device at the synchronous
secondary site. All devices at the asynchronous secondary site must be
configured as R2 devices
pahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ired with the R1
mirror of the diskless R21 device at the synchronous secondary site.
◆All devices at the synchronous secondary site in diskless SRDF/EDP

implementations with SRDF/Star must be diskless R21 devices. R21 devices and
R21 devices cannot be mixed within the same SRDF group in SRDF/Star
.
R22 devices are used at the asynchronous site and diskless devices at the
synchronous site in SRDF/EDP implementations with SRDF/Star, all
listed requirements except the first apply. In this case, Enginuity version ◆
is required at all three sites.

/EDP and SRDF/Star103
8
/Data Mobility
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8rThis chapter describes
SRDF/Data Mobility (SRDF/DM). Topics include:
◆SRDF/DM
overview........................................................................
........................... 106
/Data Mobility105
SRDF/Data Mobility
/DM overviewSRDF/Data Mobility (SRDF/DM) operates in the SRDF adaptive copy mode
only and is designed for data replication or migration between two or more
Symmetrix systems. SRDF/DM transfers data from primary devices to secondary
devices, permitting information to be shared and content to be distributed.
Figure 50 on page 106 shows an SRDF/Data Mobility (SRDF/DM) configuration.
Adaptive copy mode enables applications to avoid propagation delays while data
is transferred to the secondary site. SRDF/DM supports all Symmetrix hardware
platforms systems and all Enginuity versions that support SRDF.“Adaptive copy
write pending” on page 46 and“Adaptive copy disk mode”
onhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 page 46 contain
additional information.Note: SRDF/Data Mobility is not available in synchronous
or semi-synchronous modes, but is supported in adaptive copy mode only.
SRDF links 4
(R1)
(R2)
I/O write received from host/ server into primary cache 2 Ending status is
presented to host/ server
Write Pending (WP) mode: Data stays in cache until DA finds WP track and
schedules destage to local disk and SRDF copy task to R2 If Disk mode: Track
marked Invalid R2 until DA schedules SRDF copy task to R2. Data in cache slot is
freed.3 I/O is transmitted across the SRDF links to the secondary Symmetrix
system’s cache 4 Reciept acknowledgment from secondary RA removes WP R2 or
Invalid
state for primary system’s cache slotGEN-000802
50
/DM adaptive copy mode
/DM has the following benefits:◆◆

://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Supports all Symmetrix
systems and all Enginuity versions that support SRDF Using adaptive copy write-
pending mode is faster to read data from cache than from disk The unit of
transfer (data) across the SRDF link is the updated block rather than the entire
track, resulting in a more efficient bandwidth Using adaptive copy disk mode,
less cache is consumed.
SRDF/Data Mobility
/DM has the following limitations:
◆Not available in synchronous or semi-synchronous modes; supports adaptive copy

mode only
for data replication or migration only between two or more Symmetrix systems
adaptive copy write-pending mode, cache is temporarily consumed by the data
until it is transferred across the link
adaptive copy disk mode, more bandwidth is used because
thttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8he unit of transfer
is the entire block
adaptive copy disk mode, reading data is slower from disk than cache, increasing
device resynchronization time.◆◆◆◆
/DM overview107
SRDF/Data Mobility
9
/Automated
chapter describes SRDF/Automated Replication (SRDF/AR). Topics include:
◆SRDF/AR
overview........................................................................
............................. 110
/Automated Replication109
SRDF/Automated Replication
/AR overviewThe SRDF/Automated Replication (SRDF/AR) option enables a rapid
disaster restart over any distance with a two-site single-hop option using
SRDF/DM in combination with TimeFinder, or a three-site multi-hop option using a
combination of SRDF/S, SRDF/DM, and TimeFinder. SRDF/AR single-hop
ashttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 shown in Figure 51
on page 110 provides remote disaster restart at the secondary site with low
data-loss exposure (minutes to tens of minutes).Primary Secondary
distance
IMG-000429
51
/AR single-hop data flow
/AR Multi-hop as shown in Figure 52 on page 110 provides long-distance remote
disaster restart at the secondary site.Primary site Secondary site Out of region
Secondary site
IMG-000430
52
/AR Multi-hop data flow Note:“SRDF Multi-hop operations” on page 54 contains
additional information.
/AR provides the following benefits:◆◆

be used in both mainframe and open systems environments A SRDF/AR Multi-hop
configuration as shown in Figure 52 on page 110, provides long distance disaster
restart at a middle or bunker site Compared to traditional disaster
rechttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8overy solutions
with their long recovery time, using SRDF/AR provides remote restart with a
short time Offers data protection with dependent-write consistency across a
distance. Provides a lower cost solution for remote data protection by utilizing
lower-cost communication links.
◆◆
Limitations
/AR with
and
SRDF solutionsSRDF/Automated ReplicationThe following are the limitations of
SRDF/AR:◆In a three-site SRDF/AR Multi-hop option as shown in Figure52 on
page110, SRDF/S host I/O to the Symmetrix system is not acknowledged until the
remote secondary Symmetrix system has acknowledged it. Therefore SRDF/S has some
impact on the production application.◆If using SRDF/S on the primary to
intermediate site, the distance should not exceed 200 km.SRDF/AR can be used in
combinathttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ion with the
following EMC products:◆The two-site single-hop option uses SRDF/DM in
combination with TimeFinder as shown in Figure51 on page110. TimeFinder is used
to create a local
in-time copy which is used as a staged copy for migration to a remote array.
SRDF/AR process can be implemented with TimeFinder/Mirror in a
z/OS environment, or through UNIX and Windows environments
Solutions Enabler’s symreplicate command line interface.
: The EMC SRDF Host Component for z/OS Product Guide and the EMC Solutions
Enabler
SRDF Family CLI Product Guide contain additional information.
◆The three-site SRDF/AR Multi-hop solution as shown in Figure52 on page110 uses

a combination of SRDF/S, SRDF/DM, and TimeFinder.
/AR overview111
SRDF/Automated Replication
10http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8
Integration
chapter describes SRDF and its integration with other EMC products. Topics
:
◆Business
continuance.....................................................................
.............................. 114
◆SRDF and TimeFinder business

continuance........................................................... 115
◆SRDF
clusters........................................................................
........................................ 118
◆Geographically Dispersed Disaster
Restart.............................................................
◆SRDF and virtualization

environments...................................................................
122 124
Integration113
SRDF Integration
continuanceBusiness continuance refers to practices that enable you to achieve
nearly nonstop, 24x7 business operations.
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8F business continuance
enables business continuance by allowing users to split/suspend remote mirroring
and temporarily enabling the secondary volumes for read/write activity,
effectively creating two separate host/storage systems as shown in Figure 53 on
page 114.Symmetrix 1 Symmetrix 2
host
lInks
continuance host
mirroring temporarily halted and secondary (R2) volumes enabled for read/write
activities
53
business continuance
following business continuance operations are possible with SRDF:◆◆
— Avoid taking the system offline while backups run Remote processing— For
example, some systems must produce daily billing statements. These statements
can be produced at a remote site without affecting normal processing at the
production site Decision Support System (DSS) operations Application
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8testing.
◆◆
operations
can temporarily split/suspend the SRDF relationship to read and write data on
both the primary and secondary volumes concurrently. This enables them, for
example, to run backups on the secondary devices while production processing
continues on the primary devices (business continuance practice). Once the
backup operation completes, users can resume the SRDF links and copy data from
the primary volumes to the secondary volumes. Any updates made to the primary
volumes while the links were suspended propagate and overwrite any changed data
on the secondary volumes, bringing both volumes into a synchronized state as
shown in Figure 54 on page 114.
primary data After completion of concurrent operations, the remote mirroring
between primary and secondary are restarted, and updates are propagated from the
primary volumes to the secondary volumes.
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8parR2 secondary data

54114
to-secondary resynchronization
SRDF Integration
, you can resynchronize data in the opposite direction, from secondary to
primary as shown in Figure 55 on page 115
. This operation is useful if, for example, you performed application testing on
the secondary volumes, production processing was halted on the primary volumes,
the testing was successful, and you want to keep the updates.
primary data During an R2-to-R1 resynchronizing operation, data is copied from
the secondary volumes to the primary volumes.
secondary data
55
to-primary resynchronization
and TimeFinder business continuance
EMC TimeFinder product offering uses one or more software-controllable,
dynamicalhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ly assignable
mirror volumes called business continuance volumes (BCVs). SRDF, when used with
EMC TimeFinder software, allows you to perform business continuance operations
without temporarily suspending remote mirroring. TimeFinder BCVs can be locally
mirrored or remotely mirrored using SRDF. The sections that follow describe how
SRDF can be used with TimeFinder for business continuance operations. TimeFinder
with SRDF allows the creation of replicas on a remote secondary without
interrupting the synchronous or asynchronous replication. If a restore from a
remote replica is needed, TimeFinder and SRDF will restore data incrementally
and in parallel, to achieve the maximum level of availability and protection.
The TimeFinder product family supports the creation of dependent-write
consistent replicas using EMC consistency technology, and replicas that are
valid for backup/recovery operations. EMC recommends using SRDF in
conjuncthttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ion with
TimeFinder, to allow remote copies utilizing the secondary system’s hardware
resources without interrupting the SRDF replications. Also, the remote copies
can serve as a gold copy whenever a secondary SRDF device needs to be refreshed.
For example, a remote TimeFinder/Clone can be created from the SRDF R2 devices,
and many additional snaps can be created out of that clone for test,
development, and reporting instances. When SRDF/A is used, any remote TimeFinder
operation should use the consistent split feature to coordinate the replicas
with SRDF/A cycle switching. The SRDF/AR option enables rapid disaster restart
over any distance with a two-site single-hop option using SRDF/DM in combination
with TimeFinder as shown in Figure 51 on page 110), or a three-site SRDF/AR
Multi-hop option using a combination of SRDF/S, SRDF/DM, and TimeFinder as shown
in Figure 52 on page 110.Note: Table 3 on page 31 contains additional
SRhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8DF/TimeFinder
information.
continuance
SRDF Integration
TimeFinder BCVs with primary devices
operations (establish, split, restore) are allowed between a BCV and a primary
device. Restore operations to a primary device (R1) result in the restored data
being propagated across the SRDF links if the remote mirroring has not been
halted. If the remote mirroring has been halted, restored data will be marked as
invalid (owed) to the secondary device. A BCV device may also function as an
SRDF primary device. Such a devic
is called a BCV R1 device. A BCV R1 device may optionally be locally mirrored or
protected using any data protection scheme except Parity RAID. Contact your EMC
Sales Representative for additional information. When a BCV R1 is attached to a
standard device, the corresponding secondary device is split/suspended. When the
BCV is split, http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8the
default behavior is to propagate the changed data to the secondary device.
Optionally, data transmission can be suppressed and the BCV R1 device marks the
changed data as invalid (owed) to the secondary device, pending the resumption
of the BCV R1 to R2 device relationship as shown in Figure 56 on page 116.
Concurrent SRDF is not supported for BCV R1 devices because a BCV R1 device is
not allowed to have two remote mirrors.
a BCV as a primary device
device Host
links
2 3R2
BCV
site A 1. The BCV device is split.
site B
. The R2 on the Symmetrix system at site B is resynchronized with the R1 BCV at

site A. 3. Data is mirrored to the R2 device on the Symmetrix system at site B.
56
single-hop configuration (BCV functioning as a primary SRDF device)
BCV device may later be
separated,http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 or split,
from the standard device with which it was previously paired. After a split, the
BCV device has valid data and is available for backup or other host processes
through its original device address. Once host processes on the BCV device are
complete, the BCV may again be mirrored to a standard device (either the same
device to which it was previously attached or a different device). It can then
acquire new data for other business continuance processes or update the standard
device with any new data from the completed business continuance processes.
TimeFinder BCVs with secondary devices
operations (establish, split, restore) are allowed between a BCV and a secondary
device. By default, restore operations will not result in data propagating back
to the primary device. Changed data is marked as invalid (owed) to the primary
device following a restore operation. If data has to be propagated
bahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ck to the primary
device, TimeFinder software options are available to enable this function.

SRDF Integration
a BCV as a
deviceA BCV device may also function as an SRDF secondary device. Such a device
is called a BCV R2 device. A BCV R2 device may optionally be locally mirrored or
protected
any data protection scheme except Parity RAID. Contact your EMC Sales
for additional information. When a BCV R2 is attached to a standard
, the corresponding primary device is suspended. When the BCV R2 is split, it
again available for SRDF operations.
software may restrict functionality of BCV R2 devices. Refer to the SRDF Host
or Solutions Enabler documentation for information on using BCV R2
.
: For ihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8nformation
about EMC TimeFinder, go to the documentation (available on the EMC
http://www.mianfeiwendang.com, or contact your EMC representative.
continuance117
SRDF Integration
clusters
section describes how SRDF is integrated with EMC and other industry-related
products.
following cluster products are described in this section:
◆“SRDF/Cluster Enabler (SRDF/CE)” on page118“SRDF/Star with Veritas Cluster

Server” on page119“EMC AutoSwap” on page119“HP MetroCluster and Continental
Cluster” on page120“SRDF with Solaris Cluster Campus Topology” on
page120“SRDF with Solaris Cluster Geographic Edition” on page121
/Cluster
(SRDF/CE)SRDF/CE enables automated or semi-automated site failover using SRDF/S
or SRDF/A with Microsoft Failover Clusters MSCS). SRDF/CE allows
Windohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ws Server
and Windows Server 2008 Enterprise and Datacenter editions running Microsoft
Clusters to operate across a single pair of SRDF-connected arrays as
distributed clusters.
SRDF/CE clusters can share the same SRDF pair. SRDF/CE software can
the Symmetrix system to support up to 64 MSCS clusters per Symmetrix pair.
an SRDF link, SRDF/CE expands the range of cluster storage and management
while ensuring full business continuance protection. A SCSI or Fibre
connection from each cluster node is made to its own Symmetrix array. Two
arrays are connected through SRDF to provide automatic failover of
mirrored volumes during MSCS node failover.
on page119 shows an example of a two-node two-cluster SRDF/CE
.
EMC Symmetrix Remote Data

http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Facility (SRDF)
Product Guide
SRDF Integration
Switch Extended IP Subnet
Switch
1/Host 1
Channel Hub/Switch
Channel Hub/Switch
1/Host 2
/Synchronous Links Cluster 2/Host 1
2/Host 2
A
BICO-IMG-000761
57
/CE two-node two-cluster configuration
/Star with Veritas Cluster Server
/Star with Veritas Cluster Server provides high availability and automated
failover through storage-based replication and server clustering through SRDF/S
and SRDF/Star with Veritas Cluster Server. Chapter 7,“SRDF/Star Operations”
contains additional information. EMC AutoSwapTM (mainframe only) provides
transparent switching between Symmetrix DASD subsystems containing SRDF remote
mirroring, extending Parallel Sysplex redundancy to the disk systems. AutoSwap
allows http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8you to totally
shutdown your primary computer center and continue operations using remote
Symmetrix systems without disturbing your users. AutoSwap swaps all your z/OS
servers to the remote mirrored Symmetrix systems, allowing you to power down the
entire DASD center, or perform required maintenance in the center. Figure 58 on
page 120 shows an example of EMC AutoSwap processing. The EMC AutoSwap Product
Guide contains addi
information.
AutoSwap
clusters
SRDF Integration
/S R1 SRDF/CG R2 R1
/S SRDF/CG R2
IMG-000107
58
processing
requirements
has the following requirements:◆◆◆
current release of z/OS AutoSwap volumes must be protected by SRDF/S Sufficient
User Control Blocks (UCBs) must be available for all primary and secondary
volumhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8es
SRDF/Consistency Groups ResourcePak Base for z/OS.
◆◆
MetroCluster and Continental Cluster
Packard MC/ServiceGuard with MetroCluster software and EMC SRDF is an
integrated, open systems disaster-tolerant solution enabling geographically
dispersed HP-UX clusters to be combined into a single, manageable system with
automatic failover of applications. When a site becomes inoperable due to a
system failure or a disaster event, application package switching occurs. This
action automatically transfers control of the affected application to another HP
9000 system located in a secondary site, while also automatically read/write-
enabling remotely mirrored EMC disk devices associated with the transferred
application. HP MetroCluster for EMC SRDF allows cluster support between sites
up to 40 kilometers apart with an intersite link, which is used to provide
heartbeat communication between cluster nodes.
HPhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 Continental
Clusters extend the distance limits while operating in a similar manner.
with Solaris Cluster Campus Topology
Solaris Cluster campus topology provides rapid application resumption with
automated failover resulting from a primary site outage with up to 200
kilometers in distance between sites with SRDF/S. When using Solaris Cluster
campus topology, if a customer’s site becomes inoperable in the event of a data
center failure, fault, or disaster event, the resource groups associated with
the Solaris Cluster systems automatically fail over to the Solaris systems in
the secondary site.
SRDF Integration
with Solaris
Geographic
Solaris Cluster Geographic Edition enables independent geographically dispersed
Solaris Clusters to provide automatic failure
dhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8etection with semi-
automated failover of applications up to 200kilometers in distance between sites
SRDF/S, and unlimited distance between sites with SRDF/A.
using Solaris Cluster Geographic Edition, if a customer’s primary site becomes
due to a system failure or disaster event, the secondary cluster detects the
and notifies the system administrator who can then request a takeover with a
command. This performs SRDF state validations, then proceeds to bring the
online in the secondary cluster.
clusters121
SRDF Integration
Dispersed Disaster RestartEMC Geographically Dispersed Disaster Restart (GDDR)
is a mainframe software product that automates business recovery following both
planned outag
and disaster situations, including the total loss of a data center. EMC GDDR
achieves this goal bhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8y
providing monitoring, automation and quality controls to the functionality of
many EMC and third-party hardware and software products required for business
restart. Because EMC GDDR restarts production systems following disasters, it
does not reside on the same servers that it is seeking to protect. EMC GDDR
resides on separate logical partitions (LPARs) from the host servers that run
your application workloads. EMC GDDR is installed on a control LPAR at each
site. Each EMC GDDR node is aware of the other EMC GDDR nodes through network
connections between each site. This awareness allows EMC GDDR to:◆◆◆◆
disasters Identify survivors Nominate the leader Recover business at one of the
surviving sites.
59 on page 122 shows a three-site GDDR configuration, the Concurrent SRDF/Star
with AutoSwap.
59
site Concurrent SRDF/Star with GDDR
is implemented with SRDF/A,
SRhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8DF/S, AutoSwap,
TimeFinder, and other EMC-related products to achieve the optimum disaster
restart capability.Note: The EMC GDDR Product Guide provides details on GDDR use
and operation.
Prerequisites
IntegrationThe minimum software prerequisites needed to run EMC GDDR are:

◆Any version of z/OS currently supported by IBM
◆IBM hardware Management Console (HMC) API
◆CA-OPS/MVS
◆EMC SRDF/Host Component for z/OS
◆EMC ResourcePak Base for z/OS
◆EMC Consistency Group for z/OS
◆EMC TimeFinder/Mirror for z/OS
◆EMC AutoSwap for z/OS
◆EMC TimeFinder/Clone Mainframe SNAP Facility (optional)Note: The EMC Powerlink
website contains the minimum required levels for these software prerequisites.
Also, check Powerlink for any additional required maintenance.GDDR has the
following benefits:
◆Automatically restarts
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8your remote host
systems, applications, and storage in the event of a disaster
◆Mitigates against human error in scripts and operations
◆Provides options for disaster recovery testing that allows business operations
to continue and maintain three-site recovery capability while testingEMC GDDR
has no limitations on the number of EMC Symmetrix /devices that can be managed.
Any limitations are subject to restrictions in hardware and software.
is used on mainframe systems only.
Dispersed Disaster Restart123
SRDF Integration and virtualization environments automated datacenter built on a

virtualization platform allows users to respond dynamic conditions faster and
more efficiently than ever before. Users can run engines on a single physical
machine and share the resources of that single across
multiplhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8e environments.
Different virtual machines can run different
systems and multiple applications on the same physical computer.
and Virtual
Provisioning supports local and remote replication, including “thin to thin”
replication with SRDF. All replication products are Virtual Provisioning aware.
Both
and remote replication are supported with thin devices.
: “Virtual Provisioning” on page30 contains additional information about SRDF
and VP
and restrictions.
and VMware
Recovery
VMware Site Recovery Manager with EMC replication solutions such as SRDF is the
continuation of a trend that has simplified disaster recovery and increased cost
efficiency by streamlining and automating recovery plans as shown in
on page125.
VMware-defined specifications are implemented by the
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Symmetrix storage
array
an application referred to as the storage replication adapter (SRA). The EMC
SRDF
is an SRA that enables VMware Site Recovery Manager to interact with an
Symmetrix system. It allows VMware Site Recovery Manager to automate
based disaster restart operations on Symmetrix arrays in a Symmetrix SRDF
. The EMC SRA for VMware Site Recovery Manager supports SRDF/S
SRDF/A in Enginuity 5874 and later.
EMC adapter for VMware Site Recovery Manager supports Symmetrix systems
Enginuity 5x71 and later. In addition, the EMC adapter requires Solutions
6.5 and later.
adapter for VMware Site Recovery Manager can also address configurations in
a datastore is spread across multiple storage arrays or SRDF groups. The
must be installed on both the primary and
secondarhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8y sites. The
SRA
discovery of arrays and replicated LUNs, and initiates test and failover.
makes it much easier to ensure that the storage replication and virtual machine
established properly.
Site Recovery Manager on http://www.mianfeiwendang.com contains related
.
SRDF Integration
side vCenter and SRM Server Solutions Enabler software
side vCenter and SRM Server Solutions Enabler software
Network
Network
Server Solutions Enabler software configured as a SYMAPI server
Fabric
Fabric
Fabric
Fabric
Replication
side Symmetrix array
side Symmetrix arraySYM-002127
60
SRDF and VMware SRM
and virtualhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ization
environments
SRDF Integration
adaptive copy disk
copy mode
copy write
mode
SRDF
glossary contains terms related to Symmetrix Remote Data Facility (SRDF). Many
of these terms are used in this manual. Other terms are related to Symmetrix
systems.ASymmetrix SRDF Adaptive copy disk mode is designed for bulk data
transfer. Host write tasks accumulate on the primary volume rather than in
global memory. A background process destages the write tasks to the
corresponding secondary volume. When a skew value is reached, the primary volume
reverts to its primary mode of operation, either synchronous or semi-
synchronous, whichever is currently specified. Symmetrix SRDF Adaptive copy
modes facilitate data
shttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8haring and migration.
These modes allow the primary and secondary volumes to be more than one I/O out
of synchronization. The maximum number of I/Os that can be out of
synchronization is known as the maximum skew value. The default value is equal
to the entire logical volume. The maximum skew value for a volume can be set
using the SRDF monitoring and control software. With Symmetrix SRDF adaptive
copy write pending mode, write tasks accumulate in global memory. A background
process moves, or destages, the write-pending tasks to the primary volume and
its corresponding secondary volume on the other side of the SRDF links.When the
maximum skew value is reached, the primary volume reverts to its primary mode of
operation, either synchronous or semi-synchronous, whichever is currently
specified. The device remains in the primary mode until the number of tracks to
remotely copy becomes less than the maximum skew value. This mode is
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8not supported for
FICON or Enginuity 5772 and later.SRDF/Asynchronous (SRDF/A) mode for SRDF
secondary devices provides a dependent-write consistent copy on the R2 device,
which is only slightly behind the currency of the primary R1 device. SRDF/A
session data is transferred to the remote Symmetrix system in cycles or delta
sets, which minimizes the redundancy of same-track changes being transferred
over the SRDF links.SRDF/Automated Replication (SRDF/AR) performs automated
consistent replication of data from standard devices and from BCV R1 devices
over SRDF links
the remote SRDF pair.
Glossary
up
deviceThe process of creating a copy of data to ensure against accidental loss.A
Business Continuance Volume (BCV) is Symmetrix storage device that holds a
copy of the primary data on the Standard device.
http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8A BCV Device contains
a
of data from a standard Symmetrix device that is online for regular I/O
from its host(s). The Standard device and its assigned and mirroring BCV
are known as a BCV pair.
Standard device and its assigned and mirroring BCV device are known as a BCV
.
an SRDF group contains both primary and secondary volumes, write operations
data in both directions over the SRDF links for that group. This is called an
bidirectional configuration.
smallest unit of computer memory. A bit can hold a value of zero or one.
that maintain mirror images of data at the device level in Symmetrix
located locally and in physically separate sites. Both TimeFinder and SRDF
provide a recovery solution for component site failures between locally
remotely located storage
dhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8evices.
standard Symmetrix device with special attributes that allow it to independently
applications and processes, such as backup operations, restore operations,
Support operations, and application testing. BCV devices are available
the EMC TimeFinder software.
8-bit unit of data storage. For SRDF applications with Fibre Channel, GigE, and
, a byte is 10 bits.BCV pairbidirectional SRDF linkbitbusiness
continuancebusiness continuancevolumes (BCVs)byte
slot
SRDF
trackerSee global memory.Unit of cache equivalent to one track.A three-site SRDF
replication configuration that provides a data recovery solution. This uses a
device (R21) that is both and R2 to an R1 mirror and an R1 to an R2 mirror.A
tool available to EMC field engineers to aid in the estimation of bandwidth
in ahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8n SRDF
configuration. Change Tracker allows a user to monitor the
activity on Symmetrix devices, and is especially useful for sizing SRDF in a
configuration.
Tracker consists of two programs: a collector program that gathers the update
statistics, and a reporter program that analyzes the data and formats it into
reports.
director
component in the Symmetrix subsystem that interfaces between the host and data
storage. It transfers data between the host and global memory.TimeFinder/Clone
operations allow you to create point-in-time copies of a source
(prime or backup) device on multiple secondary devices.
compatible peer
SRDF
group
Key-Data
(CKD)
time
availability://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8Sets
Enginuity version 5568 (and later) enables the Symmetrix system to support
native IBM Peer-to-Peer Remote Copy (PPRC) commands through a Symmetrix feature
called EMC Compatible Peer.Supports the ability for a single primary volume to
be remotely mirrored to two secondary volumes concurrently. This feature is
called Concurrent SRDF and is supported in ESCON, Fibre Channel, and Gigabit
Ethernet SRDF configurations. In Concurrent SRDF, R11 volumes must be assigned
to two different SRDF groups. This is because each remote mirror can only be
assigned to one SRDF group, even if the two secondary volumes reside in the same
Symmetrix system.A consistency group (CG), known as SRDF/CG) is a group
comprised of primary SRDF devices, which have been enabled for remote point-in-
time consistency. These SRDF consistency groups operate in
unhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ison to preserve the
integrity and dependent-write consistency of a database distributed across
multiple Symmetrix systems.A data recording format employing self-defining
record formats, used in mainframe hosts, in which each record is represented by
a count area that identifies the record and specifies its format, an optional
key area that may be used to identify the data area contents, and a data area
that contains the user data for the record. CKD can also refer to a set of
channel commands that are accepted by a device that employs the CKD recording
format.Time elapsed between SRDF/A cycle switch operations.DAccess to user data
at all times by user applications.SRDF/A cycles.SRDF/A Delta Set Extension (DSE)
(Enginuity 5772 and later) enables asynchronous replication operations to remain
active in the event system cache resources are becoming in danger of reaching
the system write pending or SRDF/A max cache limit. This
functhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ionality is
achieved by offloading some or all of the active Delta Set data into
preconfigured storage pools. DSE can be enabled on both primary and secondary
sites (EMC recommended). The asynchronous write of new or updated data from
global memory to disk drive.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. See also
volume.Destage is the process of writing data from cache to a disk. Performed by
back-end code or just Enginuity.A program used to initialize the Symmetrix
system at installation and provide media maintenance.System-level tests or
firmware designed to inspect, detect, and correct failing
. These tests are comprehensive and self-invoking.
Glossary
end directorshttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 in the
Symmetrix system provide (through adapters) the
between the host and data storage. SRDF directors are front-end directors
(GigE, Fibre Channel, or ESCON) that are configured for SRDF. See also channel
or disk director.
component in the Symmetrix subsystem that interfaces between global memory
the disk drives.
SRDF domino modes effectively stop all write operations to both primary
secondary volumes if all mirrors of a primary or secondary device fail, or if
any
I/O cannot be delivered to a secondary volume, or if all SRDF links in a link
become unavailable. While such a shutdown temporarily halts production
, domino modes can prevent data integrity exposure caused by rolling
.
an ESCON-based extended-distance SRDF configuration (for example, using E1,
, http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8T1, T3, and ATM
links and/or IP network connections) that require data to move
two directions, a dual-directional link configuration may be required. For more
, consult the current EMC Symmetrix Remote Data Facility (SRDF)
Guide. With a dual-directional configuration, multiple SRDF groups are
; some groups send data in one direction, while other groups send data in the
direction.
QoS feature, dynamic cache partitioning allows the Administrator the means to
control the cache area size, servicing a given device group I/O, by
flexible partitions through cache memory.
Dynamic SRDF functionality introduced Enginuity version 5568, and enables the
to create, delete, and swap SRDF pairs, using EMC host-based SRDF control
, while the Symmetrix system is in operation. Dynamic SRDF
allhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ows the user
create SRDF device pairs from non-SRDF devices, and then synchronize and
them in the same way as static SRDF pairs.
Enginuity version 5669 and later, a user can dynamically create empty SRDF
and dynamically associate the groups with Fibre Channel or GigE SRDF
. Removing dynamic SRDF groups is also possible. Both of these operations
accomplished using EMC host-based SRDF control software. Dynamic SRDF
created through this method are persistent through Symmetrix power on or
.
Symmetrix feature that automatically transfers data from a failing disk device
to an
spare disk device without affecting data availability. This feature supports
non-mirrored devices in the Symmetrix subsystem.disk directordomino modesdual-
directional SRDFlinkdynamic cachepartitioningdynamic SRDFdevicesdynamic
Shttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8RDF groupdynamic
sparing
Consistency Assist (ECA) provides consistent split operations across

, heterogeneous hosts. Used in consistency groups, TimeFinder, and
/AR split operations for consistent and restartable copy of a database
system.
is the operating environment for the EMC Symmetrix Enterprise Storage
. Enginuity provides functional services for both its host Symmetrix
as well as for a large suite of EMC Storage Application software.
Systems Connection.EnginuityESCON
ESCON director
write
Channel
(GB)GlossaryDevice that provides a dynamic switching function and

extendehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8d link path
lengths (with XDF capability) when attaching a mainframe ESCON channel or SRDF
director (RA1, RA2).Enterprise Storage Platform. Symmetrix ESP is a functional
enhancement that allows simultaneous storage and access of mainframe data and
open systems data on the same Symmetrix system.FSymmetrix Fibre Channel
director. When this director is configured for SRDF, it becomes an RF.Fibre
Channel employs a fabric to connect devices. A fabric can be as simple as a
single cable connecting two devices. The term is often used to describe a more
complex network utilizing hubs, switches, and gateways.FarPoint is an SRDF
feature used only with ESCON extended distance solutions (and certain ESCON
campus solutions) to optimize the performance of the SRDF links. This feature
works by allowing each SRDF director to transmit multiple I/Os, in series, over
each SRDF link. In the Symmetrix system, a write operation at global memory
speed http://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8that does not
require immediate transfer of data to disk. The data is written directly to
global memory and is available for later destaging.Fixed Block Architecture.
Disk drive data storage format using fixed-size data blocks.A nominally 2 Gb/s
serial data transfer interface technology, although the specification allows
data transfer rates from 133 Mb/s up to 10.0 Gb/s. Data can be transmitted and
received simultaneously. Common transport protocols, such as Internet Protocol
(IP) and Small Computer Systems Interface (SCSI), run over Fibre Channel.
Consequently, a single connectivity technology can support high-speed I/O and
networking.An I/O interface based on the Fibre Channel architecture. In this new
interface, the ESCON protocols have been mapped to the FC-4 layer, that is, the
Upper Level Protocol layer, of the Fibre Channel Protocol. It is used in the
S/390 and z/Series environments.Data packet format in an ESCON, Fibre
Chttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8hannel, or GigE
environment.GOne of the disk storage devices, otherwise part of the storage
capability, becomes designated as the Gatekeeper to handle all feature command
I/O between host and the Symmetrix system. Typically, multiple gatekeepers are
assigned to a Symmetrix system.109 bytes. The GB2 value is based on the
convention:
GB = 1024 * 1024 * 1024 bytes.

GB10 value is based on the convention:
GB = 1000 * 1000 * 1000 bytes.

these values are expressed differently, their values are equivalent.
Glossary
memory
access electronic system storage used to retain frequently used data for faster
access.The physical disks related to each other for common parity protection
when
the RAID 5 option.
ability to define mohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8re

than one logical volume on a single physical disk drive making use of its full
formatted capacity. These logical volumes are user-selectable in
. The minimum volume size is one cylinder and the maximum size depends on
disk drive capacity and the emulation mode selected.
/O device
An addressable input/output unit such as a disk drive.Initial Program

Loading.IPv6 is the latest version of the Internet Protocol (IP), sometimes
called IPng (Next
). IPv6 is designed to solve the challenges of the current IP version, IPv4,
providing support for more addresses, better security, reduced administrative
, and enhanced support for mobile devices.
(Internet Protocol Security) is a framework for security of network
. IPsec allows two computers to trust each other's identity and share a
key fhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8or each
communications session. Based on this session key, the
establish an encrypted communications channel and can verify that data
receive is what was originally sent.IPsec
(KB)The KB2 value is based on the convention:
KB = 1024 bytes.
KB10 value is based on the convention:
KB = 1000 bytes.
these values are expressed differently, their values are equivalent.
volumes
Not ReadyVolumes that reside on an Symmetrix system but do not participate in
SRDF activity.If the local primary SRDF volume fails, the host continues to
recognize that volume as
for read/write operations as all reads and/or writes continue uninterrupted
the secondary (target, R2) volume in that remotely mirrored pair.
user-defined storage device. In the Symmetrix subsystem, for example, the
uhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ser can
a physical disk drive as one to eight logical volumes.
state when requested data is not in global memory and is not in the process of
fetched.
Partition or Logical Partitioning Mode. Mainframe system function that
different operating systems to run concurrently in separate logical partitions.
logical volume (LV)long missLPAR
LUN
(MB)
and
pair
hop SRDF
(MSC)
logical unit number (LUN) is a unique identifier used on a SCSI bus that enables
it to differentiate between up to eight separate storage devices (each of which
is a logical unit).MMultiple Allegiance is an IBM feature, supported by the
Symmehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8trix system, that
improves throughput across a shared storage environment. MA allows more than one
I/O from different hosts to access the same device as long as the I/Os do not
conflict with each other.The disk surface on which data is stored.The MB2 value
is based on the convention: 1 MB = 1024 * 1024 bytes.The MB1 MB = 1000 * 1000
bytes.10 value is based on the convention: Although these values are expressed
differently, their values are equivalent.Metadevices allow for the designation
of individual devices to be concatenated together, creating larger storage
devices. When the Metahead (first device in the member chain) is addressed with
a command, the Enginuity process determines which metadevice is the target for
the command execution. Metadevice addressing, by striping, divides each
Metamember device into a series of stripes, then addresses a stripe from each
device before finally advancing to the next stripe on the first
dhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8evice. The striping
of data across multiple drives effectively creates definable cylinder
stripes.The Symmetrix option that maintains two identical copies of a designated
volume on separate disks. Each volume automatically updates during a write
operation. If one disk drive fails, the Symmetrix system automatically uses the
other disk drive.A logical volume with all data recorded twice, once on each of
two different physical devices.An SRDF multi-hop topology allows you to daisy-
chain three Symmetrix sites where a third site is providing business continuance
backup to the remote SRDF site. In a multi-hop scheme, the last site in the
chain is two hops (SRDF links) away from the local or primary site.Beginning
with Enginuity 5x71 for mainframe and open systems, SRDF/A is supported in
configurations where there are multiple primary Symmetrix systems and/or
multiple primary Symmetrix SRDF groups connected to multiple secondary
Symmehttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8trix systems
and/or multiple secondary Symmetrix SRDF groups. This is referred to as SRDF/A
Multi-Session Consistency or SRDF/A MSC. SRDF/A MSC configurations can also
support mixed open systems and mainframe data controlled within the same SRDF/A
MSC session. Multiple Virtual Storage (mainframe systems only).
Glossary
attached
topologyA NAS device is attached to a TCP/IP-based network (LAN or WAN), and

accessed using CIFS and NFS-specialized I/O protocols for file access and file
sharing.A physical arrangement of nodes and interconnecting communication links
in
based on application requirements and geographical distribution of users.
SRDF linkPertaining to equipment or devices not under control of the

processor.An SRDF link is offline if one or
mohttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8re of the following
occurs: The remote adapter is
- link disabled. The remote adapter is online but the link is offline (damaged
or
cable or other damaged hardware) - link disabled.
to equipment or devices under control of the processor.
SRDF link is online when the following occurs: The remote adapter is operational
enabled on both sides of the SRDF configuration. The Symmetrix systems are
properly on both sides of the SRDF configuration. The external link
components are operational.
system whose characteristics comply with standards made available throughout
industry, and therefore can be connected to other systems that comply with the
standards.onlineonline SRDF linkopen system
to-peer remote
(PPRC)
link lossA hardware-based remote
chttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8opy option that
provides a synchronous volume copy across storage subsystems for disaster
recovery, device migration, and workload migration.If SRDF/A experiences a
permanent link loss, it drops all of the devices on the link to
Ready state. This results in all data in the active and inactive primary
Symmetrix
(capture and transmit delta sets) being changed from write pending for the
mirror to owed to the remote mirror. In addition, any new write I/Os on the
Symmetrix system result in tracks being marked owed to the remote mirror.
of these tracks are owed to the secondary Symmetrix once the links are restored.
known as source volume. A Symmetrix logical volume that is participating in
operations. It resides in the “local” Symmetrix storage subsystem. All CPUs
to the Symmetrix may access a primary volume for read/write
operatihttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ons.
writes to this volume are mirrored to a “remote” Symmetrix storage subsystem.
A
volume is not available for local mirroring operations.primary volume (R1)
of Service (QoS) is a Symmetrix management area that provides the

performance tuning tools to optimize the storage system’s dynamic
/O handling paths. QoS features allow you to adjust data transfer rates and
caching
to meet your current storage environment.
RAID 5
1/0
10
6
hit
miss
Capacity
disaster
device
5 data protection implements data striping and rotating parity across all
hypervolumes of a RAID 5 device.
RAIhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8D 5 (3 1)
configurations consists of four Symmetrix devices with parity and data striped
across each device. RAID 5 (7 1) configurations consists of eight Symmetrix
devices with data and parity striped across each device. A protection method
that combines RAID 1 and RAID 0; used in open systems environments. A protection
method that combines RAID 1 and RAID 0; used in mainframe environments. A
protection method that supports the ability to rebuild data in the event that
two drives within the RAID group fail. RAID 6(6 2) configurations consists of
eight Symmetrix devices with parity and data striped across each device. RAID 5
(14 2) configurations consists of sixteen Symmetrix devices with data and parity
striped across each device. The name of the action taken when data requested by
the read operation is in global memory.The name of the action taken when data
requested by the read operation is not in global memory.The function
thttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8hat occurs when a
target selects an initiator to continue an operation after a disconnect.A
reconnection exists from the assertion of the BSY signal in a RESELECTION phase
until the next BUS FREE phase occurs. A reconnection can only occur between a
target and an initiator.SRDF/A Reserve Capacity enhances SRDF/A's ability to
maintain an operational state when encountering network resource constraints
that would have previously suspended SRDF/A operations. With SRDF/A Reserve
Capacity functions enabled, additional resource allocation can be applied to
address temporary workload peaks, periods of network congestion, or even
transient network outages. See Transmit Idle and DSE.A track image copy from the
primary volume to the secondary volume of only the tracks which have changed.
Resynchronization is the process of copying data from primary to secondary or
secondary to primary sites since the data was last synchronized.A rolling
dhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8isaster is a series
of events that lead up to a complete disaster. For example, the loss of a
communication link occurs prior to a site failure. Most disasters are rolling
disasters; their duration may be only milliseconds or up to hours.SA Save device
is a device member of a SAVE pool. There are two types of Save device pools:
Snap pools and SRDF/A DSE pools.Small Computer System Interface.
Glossary
volume
(R2)A Symmetrix logical volume that is participating in SRDF operations. It

resides in the secondary Symmetrix storage subsystem. It is paired with a
primary volume in the
Symmetrix storage subsystem and receives all write data from its mirrored
. This volume is not accessed by user applications during normal I/O operations.
mainly for an extended distance SRDF solution, semi-synchronous
modhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8e allows
primary and secondary volumes to be out of synchronization by one write I/O
. Data must be successfully stored in the Symmetrix system containing the
volume before an acknowledgement is sent to the local host. This mode is
supported for FICON or at Enginuity 5772 and later.
I/O.
Remote Data Facility. SRDF consists of the microcode and hardware
to support Symmetrix remote mirroring.
groups define relationships between Symmetrix systems. An SRDF group is a
of SRDF director port connections configured to communicate with another set of
director ports in another Symmetrix system. Logical volumes (devices) are
to SRDF groups.
end-to-end SRDF connection between a given pair of Symmetrix systems.
mode of remote replication that allows customers to
asynchronoushttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ly
replicate data
maintaining a dependent-write consistent copy of the data on the secondary
(R2) device sat all times. The dependent-write consistent point-in-time copy of
the
at the remote site is typically only seconds behind the primary (R1) site.
SRDF/A
data is transferred to the secondary Symmetrix system in cycles (or delta sets),
the redundancy of multiple same-track changes being transferred over
SRDF links, potentially reducing the required bandwidth.
automation solution that uses both SRDF and TimeFinder to provide a periodic
replication of a restartable data image. For protection over greater
, a multi-hop SRDF/AR configuration can provide long distance disaster
at a middle or bunker site.
SRDF product offering designed to ensure the dependent-write consistency of
://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8data remotely mirrored by
the SRDF operations in the event of a rolling disaster.
SRDF product offering that permits operation in SRDF adaptive copy mode only
is designed for data replication and/or migration between two or more
systems. SRDF/DM transfers data from primary volumes to secondary
, permitting information to be shared, content to be distributed, and access to
local to additional processing environments. Adaptive copy mode enables
using that volume to avoid propagation delays while data is transferred
the remote site.
/DM supports all Symmetrix systems and all Enginuity versions that support
, and can be used for local or remote transfers. See adaptive copy mode.semi-
synchronousmodeSIOSRDFSRDF groupSRDF
linkSRDF/Asynchronous(SRDF/A)SRDF/AutomatedReplication
(SRDF/AR)SRDF/ConsistencyGroups
(SRDF/CG)SRDF/Dahttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ta
Mobility(SRDF/DM)
/StarSRDF/Star is a data protection and failure recovery solution that covers
three
dispersed data centers in a triangular topology. The primary site, by
of SRDF links, uses concurrent or Cascading SRDF capabilities to mirror the
production data synchronously to one secondary site and asynchronously to
secondary site for a total business continuance solution.
SRDF/Synchronous
(SRDF/S)
device
mode
link loss
(TB)
device
pool
Idle
SRDF
business continuance solution that maintains a real-time (synchronous) copy of
data at the logical volume level.The process of writing data from a
diskhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8 drive to global
memory. See also destage.A standard device is a Symmetrix volume that could be
participating in SRDF operations, but is being used for Timefinder/Clone/Snap
operations.The process of segmenting logically sequential data and writing the
segments to multiple physical drives.Available with the SRDF/S product offering,
synchronous mode maintains a real-time mirror image of data between the primary
and secondary volumes. Data must be successfully stored in both the local and
remote Symmetrix systems before an acknowledgement is sent to the primary site
host. TIf SRDF/A suffers a temporary loss (<10 seconds by default) on all of
the SRDF links, the SRDF/A state remains active and data continues to accumulate
in global memory. This may result in an elongated cycle, but the secondary
Symmetrix dependent-write consistency is not compromised and the primary and
secondary Symmetrix device relationships are not
suspendedhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8.The TB2
value is based on the convention: 1 TB = 1024 * 1024 * 1024 * 1024 bytes. The
TB1 TB = 1000 * 1000 * 1000 * 1000 bytes. 10 value is based on the convention:
Although these values are expressed differently, their values are equivalent.A
host-accessible device that has no storage directly associated with it.A
collection of data devices that provide the storage capacity for thin devices.A
Reserve Capacity enhancement to EMC's SRDF/A feature that provides the
capability of dynamically and transparently extending the Capture, Transmit, and
Receive phases of the SRDF/A cycle while masking the effects of an “all SRDF
links lost” event. Without the SRDF/A Transmit Idle enhancement, an “all SRDF
links lost” event would normally result in the abnormal termination of SRDF/A.
The SRDF/A Transmit Idle enhancement has been specifically designed to prevent
this event from occurring. See also Reserve Capacity.UIf all primary (R1)
volumhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8es reside in one
Symmetrix system and all secondary (R2) volumes reside in another Symmetrix
system, write operations move in one direction,
primary to secondary. In a unidirectional configuration, data moves in the same
between all devices in the SRDF group.
Glossary
general term referring to a storage device. In the Symmetrix subsystem, a volume

to a part of a physical disk drive that emulates a single disk drive to the
.
FoldingWrite Folding in SRDF/A environments improves the efficiency of the SRDF

network
. Even if there are multiple data updates, (i.e. repeated writes) in the same
cycle,
systems send the data across the SRDF links only once.
is room in global memory for the data presented by the write
operationhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8.
is no room in global memory for the data presented by the write operation.write
hitwrite miss
/OSA widely-used operating system for the IBM zSeries mainframe computers that
uses
-bit real storage.
文档下载网是专业的免费文档搜索与下载网站，提供行业资料，考试资料，教
学课件，学术论文，技术资料，研究报告，工作范文，资格考试， word 文档，
专业文献，应用文书，行业论文等文档搜索与文档下载，是您文档写作和查找
参考资料的必备网站。
文档下载 http://www.mianfeiwendang.com/
亿万文档资料，等你来发现

SRDF Product Guide (WWW - Mianfeiwendang.com)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRDF Product Guide (WWW - Mianfeiwendang.com)

Uploaded by

Copyright:

Available Formats

文档下载 免费文档下载

srdf product guide

EMC&#174; Symmetrix&#174; Remote

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

1ContentsSRDF Technical Concepts

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

SRDF/A MSC secondary Symmetrix system cycle

SRDF/A MSC secondary Symmetrix system new receive delta set is

SRDF/A MSC primary Symmetrix systems begin SRDF

Concurrent SRDF configured for SRDF/Star

Concurrent R22 SRDF/Star

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

PageSymmetrix hardware model

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

Symmetrix Remhttp://www.mianfeiwendang.com/doc/fbe03131210633d18de37bd8ote Data

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

chapter introduces SRDF, explains basic concepts, and provides example

◆Base SRDF family

◆Understanding SRDF products and

◆Network protocols and

SRDF Technical Concepts

: The following terms are used synonymously throughout SRDF documentation:

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

SRDF Technical Concepts

SRDF solution can use different Symmetrix hardware platforms/models. Details

/5330 and 3630/5630

/5430, 3830/3832a/5830Symmetrix 8000TM Series82308430, 8530Symmetrix DMXTM

/5700 and 3930/59308730, 8830DMX3000

◆Related documentationEMC Networked Storage Topology GuideEMC SRDF Connectivity

SRDF Technical Concepts

Symmetrix Remote Data Facility (SRDF) Product Guide

SRDF Technical Concepts

◆SRDF/Automated Replication (SRDF/AR) solutions for meeting very specific,

SRDF Technical Concepts

Symmetrix Remote Data Facility (SRDF) Product Guide

SRDF Technical Concepts

SRDF Technical Concepts

“SRDF/Automated Replication” on page109 and “SRDF and TimeFinder business

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

SRDF Technical Concepts

SRDF Technical Concepts

◆SRDF Host Component for z/OS

◆SRDF Host Component for z/OSEMC ResourcePak&#174; Base for z/OSConsistency

EMC Symmetrix Remote Data Facility

SRDF Technical Concepts

Invokes a spare drive as an additional local mirror to the faulty drive to

(permanent sparing).Symmetrix RAID 1/0Symmetrix RAID 10RAID

“Groups and links” on page36 provides more information on SRDF links.

SRDF Technical Concepts

devices are mainly used in SRDF/Star environments. The R22 is a concurrent R2

Symmetrix Remote Data Facility (SRDF) Product Guide

Diskless R21 devices

◆Create a new primary/secondary pair relationship from non-SRDF devices

◆Terminate and establish a relationship with a new

◆Swap personality between primary and secondary devices.

◆Fibre Channel SRDF, point-to-point connection

SRDF Technical Concepts

EMC Symmetrix Remote Data Facility (SRDF) Product Guide

◆An EMC CE must run the conversion procedure

◆To convert from PPRC to SRDF or SRDF to

◆The relationship between R1 and R2 devices must be suspended

◆The R1 device cannot be in an active SRDF/Consistency Group

文档下载免费文档下载

EMC® Symmetrix® Remote

◆SRDF Host Component for z/OSEMC ResourcePak® Base for z/OSConsistency