Anda di halaman 1dari 12

EMC Customer Symmetrix Procedure Generator

Topic
Managing SRDF using Solutions Enabler SYMCLI

Selections
Select a task: Managing SRDF/A
Select task(s): Starting a session

Procedure Generated: 06/09/2013 12:47:01


Tobesuryhavtlcpdgnioewt,alyschYnkdifoutpaehlcrys.
SYMCLI and SYMAPI normally capture significant events and command actions to a daily log file.
UNIX: /var/symapi/log/symapi-yyymmdd.log
Windows: C:\Program Files\EMC\Symapi\log\symapi-yyyymmdd.log

REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
Procedure Generators@emc.com

Copyright 2010 2015 EMC Corporation. All rights reserved.


Publication Date: September, 2013
EMC believes the information in this publication is accurate as of its publication date. The information is subject to
change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories
section on EMC Powerlink.
For the most up-to-date listing of EMC trademarks, see the list of EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.

EMC CONFIDENTIAL

version: 3.2.0

1 of 12

EMC Customer Symmetrix Procedure Generator

Contents

Starting an SRDF/A session.....................................................................................3

EMC CONFIDENTIAL

version: 3.2.0

2 of 12

EMC Customer Symmetrix Procedure Generator

srdfaStart_sym001

Starting an SRDF/A session


This procedure describes the steps necessary to implement and start a single source
SRDF/Asynchronous mode (SRDF/A) session using static (non-dynamic) Symmetrix devices.
The instructions use the Solutions Enabler SYMCLI command line interface to manage
devices by a device group. The user should be familiar with the concepts of SRDF/A, and have
some experience using Solutions Enabler SYMCLI commands before attempting this
procedure.
This procedure is based on content from the following EMC manuals:
EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide
SRDF/A and SRDF/A Multi-Session Consistency on UNIX and Windows EMC
Engineering Solutions Guide
EMC Solutions Enabler Symmetrix Array Management CLI Product Guide.
EMC Solutions Enabler TimeFinder Family CLI Product Guide
These documents can be obtained from the EMC Powerlink website at:
http://Powerlink.EMC.com

SRDF Brief Summary and Overview of This Procedure


In SRDF/A, the Symmetrix array provides a dependent-write consistent point-in-time image on
the target (R2) device, which is a short period of time behind the source (R1) device.
Managed in sessions, SRDF/A transfers data in predefined timed cycles or delta sets to
ensure that data at the remote (R2) site is dependent-write consistent. This mode requires an
SRDF/A license.
The steps outlined in this procedure must be followed in order and are explained in three
separate phases as described below:
Three Phase Implementation
Phase I Initial steps for setting up a single source SRDF/A replication session

Identify potential source and target devices on the Symmetrix arrays


Identify or create a device group to manage the SRDF/A session
Verify device group details

Phase II Transitional steps to perform before session activation

Change the SRDF mode to adaptive copy disk mode


Perform a full establish on the SRDF pairs
Query device group status
Phase III Activate the SRDF/A Configuration
Verify the number of invalid tracks
Change the SRDF mode to asynchronous
Enable and verify consistency protection for SRDF/A mode

1. Identify source (R1) and target (R2) devices on the Symmetrix arrays
In this step all components in the replication environment are identified, and application details
including the number and size of devices are determined.

Using the example provided, determine the Symmetrix device types for the candidate R1
EMC CONFIDENTIAL

version: 3.2.0

3 of 12

EMC Customer Symmetrix Procedure Generator

devices and identify candidate R2 devices on the target Symmetrix.


Devices contain the application data and are used as sources and targets for the SRDF/A
functionality. In circumstances where an application is already on the Symmetrix array but no
device groups have been created, Symmetrix devices need to be identified by using your hostspecific LVM commands instead of SYMCLI commands.
There are several SYMCLI commands that can be used to identify SRDF/A devices, some of
these include: symrdf list, symdev list and sympd list. For extensive information on how
obtain device information, refer to the EMC Solutions Enabler Symmetrix Array Management
CLI Product Guide. A few examples are provided here in brief. It is the users responsibility to
properly identify the devices to be used in the SRDF/A session for this procedure.
To identify candidate source (R1) and target (R2) devices for SRDF/A, you can use the symrdf
list command with the rdfa option as shown below:
symrdflistrdfa
SymmetrixID:000000006163
LocalDeviceView

STATUSMODESRDFSTATES
SymRDFR1InvR2Inv
DevRDevTyp:GSARALNKMDATracksTracksDevRDevPair

00F200E6R1:3RWRWRWS..00RWWDSynchronized
00F300E7R1:3RWRWRWS..00RWWDSynchronized
00F400E8R1:3RWRWRWS..00RWWDSynchronized
00F500E9R1:3RWRWRWS..00RWWDSynchronized
00F600EAR1:3RWRWRWS..00RWWDSynchronized
00F700EBR1:3RWRWRWS..00RWWDSynchronized
00F800ECR1:3RWRWRWS..00RWWDSynchronized
00F900EDR1:3RWRWRWS..00RWWDSynchronized
00FA00EER1:3RWRWRWS..00RWWDSynchronized
00FB00EFR1:3RWRWRWS..00RWWDSynchronized
00FC0104R1:3RWRWRWS..00RWWDSynchronized
00FD0105R1:3RWRWRWS..00RWWDSynchronized
00FE0106R1:3RWRWRWS..00RWWDSynchronized
00FF0107R1:3RWRWRWS..00RWWDSynchronized
01000108R1:3RWRWRWS..00RWWDSynchronized
01010109R1:3RWRWRWS..00RWWDSynchronized
Total
Track(s)00
MB(s)0.00.0
LegendforMODES:
M(odeofOperation):A=Async,S=Sync,E=Semisync,C=AdaptiveCopy
D(omino):X=Enabled,.=Disabled
A(daptiveCopy):D=DiskMode,W=WPMode,.=ACpoff

The above output shows that RDF (RA) group 3 has been configured to provide SRDF/A
operations. Devices in this type of RDF group must be either R1 or R2 devices. You can not
mix device types in the same group.
Before creating a device group and adding devices to it, examine the devices on the local
EMC CONFIDENTIAL

version: 3.2.0

4 of 12

EMC Customer Symmetrix Procedure Generator

Symmetrix array to determine which ones are source devices (SymDev), which are remote
target devices (RDev), and whether a device is an R1 or an R2 type device. The symrdf list
command displays this information, as well as other relevant data, such as RDF group (G),
replication method (column M), pair state, invalid tracks, and the state of each device and the
RDF links that connect them. The ellipsis () represents truncated output.
symrdflist
SymmetrixID:000000003264
LocalDeviceView

STATUSMODESRDFSTATES
SymRDFR1InvR2Inv
DevRDevTyp:GSARALNKMDATracksTracksDevRDevPair

00450045R2:2RWWDNRS..049500WDRWSuspended
00460046R2:2??WDNRS..033000WDRWSuspended
00470047R2:2??WDNRS..00WDRWSuspended
009C0054R1:2RWRWRWS..00RWNRSynchronized
009D0055R1:2RWRWRWS..00RWNRSynchronized
009E0056R1:2RWRWRWS..00RWNRSynchronized
009F0057R1:2RWRWRWS..00RWNRSynchronized
00A00058R1:2RWRWRWA.W00RWNRSynchronized
00A10059R1:2RWRWRWA.W00RWNRSynchronized
00A2005AR1:2RWRWRWA.W00RWNRSynchronized
00A3005BR1:2RWRWRWA.W00RWNRSynchronized
...
The symdev list command with the r1 option displays all R1 devices. Those R1 devices that

are not already part of a device group are displayed as N/Grpd, which means they are
available to be added to a new RDF1 device group.
symdevlistr1
SymmetrixID:000000003264
DeviceNameDirectorsDevice

Cap
SymPhysicalSA:PDA:ITConfigAttributeSts(MB)

009C/dev/rdsk/emcpower84c16B:101A:C0RDF1N/Grp'dRW516
009D/dev/rdsk/emcpower85c16B:102B:D3RDF1N/Grp'dRW516
009E/dev/rdsk/emcpower90c16B:102A:C0RDF1N/Grp'dRW516
009F/dev/rdsk/emcpower91c16B:101B:D3RDF1N/Grp'dRW516
00A0/dev/rdsk/emcpower92c16B:101B:C0RDF1N/Grp'dRW516
00A1/dev/rdsk/emcpower93c16B:102A:D3RDF1Grp'dRW516
00A2/dev/rdsk/emcpower94c16B:102B:C0RDF1N/Grp'dRW516
...

Using the above SYMCLI examples, identify and create a list of the SRDF devices that will be
added to your device group for the SRDF/A session.
2. Identify or create a device group to manage the SRDF/A session and add the devices

EMC CONFIDENTIAL

version: 3.2.0

5 of 12

EMC Customer Symmetrix Procedure Generator

The symdg list command with the Symmetrix ID number can be used to identify existing
device groups on a particular Symmetrix array.
symdglistsid3264

After identifying SRDF-capable devices and selecting the required number needed, devices
are added into a Symmetrix device group. The SRDF/A session created using this procedure
will be managed by a single device group, rather than individual devices.
For example, to create a device group named pocsun100data using devices 00e1 through
00e4 on Symmetrix 000187461501, enter the following commands:
symdgcreatepocsun100data
symldgpocsun100dataaddalldevrange00e1:00e4sid502

Note: For additional information on how to display and manage device groups using the symdg
command, refer to the EMC Solutions Enabler Symmetrix Array Management CLI Product
Guide.
Using the previous example, identify or create a device group to manage your SRDF/A session
and add the devices you selected in the previous step.
3. Verify device group details
After creating the device group, confirm and verify the device group details by using the symdg
list and show commands.

symdglist
DEVICEGROUPS
Numberof
NameTypeValidSymmetrixIDDevsGKsBCVsVDEVs
pocsun100dataRDF1Yes0001874615024000

You can display detailed information about a device group using the symdg show command.
symdgshowpocsun100data
GroupName:pocsun100data
GroupType:RDF1
DeviceGroupinGNS:Yes
Valid:Yes
SymmetrixID:000187461502
GroupCreationTime:SatMar1821:57:122006
VendorID:EMCCorp
ApplicationID:SMC
NumberofSTDDevicesinGroup:4
NumberofAssociatedGK's:0
NumberofLocallyassociatedBCV's:0
NumberofLocallyassociatedVDEV's:0
NumberofRemotelyassociatedVDEV's(STDRDF):0
NumberofRemotelyassociatedBCV's(STDRDF):0
NumberofRemotelyassociatedBCV's(BCVRDF):0
NumberofRemotelyassoc'dRBCV's(RBCVRDF):0

EMC CONFIDENTIAL

version: 3.2.0

6 of 12

EMC Customer Symmetrix Procedure Generator

Standard(STD)Devices(4):
{
SymCap
LdevNamePdevNameDevAtt.Sts(MB)

DEV001N/A00E1RW4315
DEV002N/A00E2RW4315
DEV003N/A00E3RW4315
DEV004N/A00E4RW4315
}

The previous example identifies devices that are used by the application. Always make sure
this information matches the information provided by your application administrator.
4. Change the SRDF mode to adaptive copy disk mode
Now that you have identified your SRDF pairs and added them to a device group, the SRDF
mode should be changed to adaptive copy disk mode ( acp_disk). This transitional step allows
you to copy the local data across the SRDF link to the remote site as efficiently as possible. If
you allowed the SRDF establish to start in synchronous mode, you could create serious I/O
latency issues for the host application.

In adaptive copy disk mode, the host does not have any I/O performance impact. This is the
added benefit of using acp_disk mode. By specifying acp_disk rather than adaptive copy
write pending (acp_wp), you do not waste valuable cache resources on the local Symmetrix
array during the SRDF establish. This further reduces the risk of performance impact if there is
production occurring on the local Symmetrix array.
To set the SRDF mode to acp_disk, use the symrdf set mode command. For example, set
the mode for the pocsun100data device group as follows:
symrdfgpocsun100datasetmodeacp_disknop
AnRDFSet'ACpDiskModeON'operationexecutionisin
progressfordevicegroup'pocsun100data'.Pleasewait...
TheRDFSet'ACpDiskModeON'operationsuccessfullyexecuted
fordevicegroup'pocsun100data'.

After setting the SRDF mode, run a symrdf query command against the device group to
verify that it is in adaptive copy disk mode.
symrdfgpocsun100dataquery
DeviceGroup(DG)Name:pocsun100data
DG'sType:RDF1
DG'sSymmetrixID:000187461502

Source(R1)ViewTarget(R2)ViewMODES

STLIST
StandardANA
LogicalTR1InvR2InvKTR1InvR2InvRDFPair
DeviceDevETracksTracksSDevETracksTracksMDASTATE

DEV00100E1RW0138090NR00E1WD00C.DSuspended
DEV00200E2RW0138090NR00E2WD00C.DSuspended
DEV00300E3RW0138090NR00E3WD00C.DSuspended
EMC CONFIDENTIAL

version: 3.2.0

7 of 12

EMC Customer Symmetrix Procedure Generator

DEV00400E4RW0138090NR00E4WD00C.DSuspended
Total
Track(s)055236000
MB(s)0.017261.30.00.0
LegendforMODES:
M(odeofOperation):A=Async,S=Sync,E=Semisync,C=AdaptiveCopy
D(omino):X=Enabled,.=Disabled
A(daptiveCopy):D=DiskMode,W=WPMode,.=ACpoff

This example shows the RDF pair state is still suspended. The operation has changed only the
mode from synchronous to acp_disk (C.D). When you set the SRDF mode to adaptive copy
disk, the Symmetrix array acknowledges all writes to source (R1) devices as if they were local
devices. New data accumulates on the source (R1) device and is marked by the source (R1)
side as invalid tracks until it is subsequently transferred to the target (R2) device. The remote
director transfers each write to the target (R2) device whenever link paths become available. In
addition, tracks are read from the physical disk for transfer to the R2.
5. Perform a full establish on the SRDF pairs
Once the device groups are in adaptive copy disk mode, start the initial full SRDF establish for
each device group. The establish operation can take a long time. It is best to launch this during
nonpeak hours to minimize traffic over the RDF link.

symrdfgpocsun100dataestablishfullnop
AnRDF'FullEstablish'operationexecutionis
inprogressfordevicegroup'pocsun100data'.Pleasewait...
SuspendRDFlink(s).......................................Done.
Mergedevicetracktablesbetweensourceandtarget.......Started.
Devices:00E100E4......................................Merged.
Mergedevicetracktablesbetweensourceandtarget.......Done.
ResumeRDFlink(s)........................................Started.
ResumeRDFlink(s)........................................Done.
TheRDF'FullEstablish'operationsuccessfullyinitiatedfor
devicegroup'pocsun100data'.

The establish operation begins by merging the track tables between the R1 and R2 devices. It
then enables the RDF link (makes it enabled for read and write requests) and begins the copy
of data from the source device to the device which was designated as invalid. In this case the
data flow is from the R1 device to the R2 device. Again, this is because the example specified
the invalidate R2 option when it created the pairing. Had it specified invalidate R1, it would
be overwriting the R1 data from the R2.
6. Query device group status
Periodically, query the progress of the initial SRDF establish. Check to make sure the amount
of invalid tracks owed from the R1 to the R2 is decreasing. This value is visible in the R2 Inv
Tracks column.

symrdfgpocsun100dataquery
DeviceGroup(DG)Name:pocsun100data
DG'sType:RDF1
DG'sSymmetrixID:000187461502

EMC CONFIDENTIAL

version: 3.2.0

8 of 12

EMC Customer Symmetrix Procedure Generator

Source(R1)ViewTarget(R2)ViewMODES

STLIST
StandardANA
LogicalTR1InvR2InvKTR1InvR2InvRDFPair
DeviceDevETracksTracksSDevETracksTracksMDASTATE

DEV00100E1RW0113166RW00E1WD00C.DSyncInProg
DEV00200E2RW0110506RW00E2WD00C.DSyncInProg
DEV00300E3RW0114995RW00E3WD00C.DSyncInProg
DEV00400E4RW0114888RW00E4WD00C.DSyncInProg
Total
Track(s)045355500
MB(s)0.014173.60.00.0
Synchronizationrate:33.0MB/S
Estimatedtimetocompletion:00:07:10
LegendforMODES:
M(odeofOperation):A=Async,S=Sync,E=Semisync,C=AdaptiveCopy
D(omino):X=Enabled,.=Disabled
A(daptiveCopy):D=DiskMode,W=WPMode,.=ACpoff

Periodically examine the output from the symrdf query command and verify the following:

The R1 device is now read and write enabled.

The R2 invalid tracks have been calculated and are now being copied. Verify that this
value is greater than zero and that the number of tracks are decreasing as the establish
continues.

The link is now ready (read and write enabled).


The above conditions mean that the SRDF pairs are synchronizing (SyncInProg) as shown in
the above example. Once the invalid R2 tracks go to zero, the RDF pair state changes to
Synchronized.

7. Document the SRDF pairing information in a configuration worksheet


The SRDF pairing information created for this procedure should be documented in a
configuration worksheet. The recorded information may be necessary in the event of a failure
and should be made available to the system administrator to keep on record.

8. Verify that the number of invalid tracks is below 30,000


IMPORTANT
It could be a dangerous situation if SRDF/A mode is activated with a large number of invalid
tracks. It is a best practice to switch into SRDF/A mode once the total amount of invalid tracks
has fallen below 30,000. Activating SRDF/A with a large number of invalid tracks owed to the
R2 side could overload the DA, flood the RDF link, and flood the R1 cache. All of these
scenarios could cause the SRDF/A session to drop again. At a minimum, it will have a
negative effect on cycle time and could cause other active SRDF/A sessions in the Symmetrix

EMC CONFIDENTIAL

version: 3.2.0

9 of 12

EMC Customer Symmetrix Procedure Generator

array to experience elongated cycle times.


Before switching into SRDF/A mode, you should remain in adaptive copy disk mode until the
invalid track count falls below 30,000, or one cycle set of data. This way you greatly minimize
your risk of flooding the cache or your link.
Using the example shown below, enter the symrdf query command for your device group to
determine the invalid track count.
symrdfgpocsun100dataqueryi5
DeviceGroup(DG)Name:pocsun100data
DG'sType:RDF1
DG'sSymmetrixID:000187461502

Source(R1)ViewTarget(R2)ViewMODES

STLIST
StandardANA
LogicalTR1InvR2InvKTR1InvR2InvRDFPair
DeviceDevETracksTracksSDevETracksTracksMDASTATE

DEV00100E1RW025891RW00E1WD00C.DSyncInProg
DEV00200E2RW00RW00E2WD00C.DSynchronized
DEV00300E3RW00RW00E3WD00C.DSynchronized
DEV00400E4RW00RW00E4WD00C.DSynchronized
Total
Track(s)02589100
MB(s)0.0809.10.00.0
LegendforMODES:
M(odeofOperation):A=Async,S=Sync,E=Semisync,C=AdaptiveCopy
D(omino):X=Enabled,.=Disabled
A(daptiveCopy):D=DiskMode,W=WPMode,.=ACpoff

The R2 invalid track columns in this example show that the amount of invalid tracks has fallen
below 30,000. Device group pocsun100data has 25,891 invalid tracks. This means that it
takes just one SRDF/A cycle switch to make the RDF pairs consistent for both device groups.
9. Change the SRDF mode to asynchronous
To change to asynchronous mode, use the symrdf set mode async command.

symrdfgpocsun100datasetmodeasyncnop
AnRDFSet'AsynchronousMode'operationexecutionisin
progressfordevicegroup'pocsun100data'.Pleasewait...
TheRDFSet'AsynchronousMode'operationsuccessfullyexecuted
fordevicegroup'pocsun100data'.

10.Enable and verify consistency protection for SRDF/A mode


Enable SRDF/A consistency protection by disabling tolerance mode. Tolerance mode allows a
device that is not ready on the link to be added to an active SRDF/A group without dropping
the session. When tolerance mode is on, if a device that is already part of the SRDF/A group
EMC CONFIDENTIAL

version: 3.2.0

10 of 12

EMC Customer Symmetrix Procedure Generator

becomes NR on the link, the SRDF/A group will not drop. This breaks the guarantee of R2
consistency until tolerance mode is turned off again.
To enable SRDF/A consistency protection, use the symrdf enable command.
symrdfgpocsun100dataenablenop
AnRDF'Enable'operationexecutionis
inprogressfordevicegroup'pocsun100data'.Pleasewait...
TheRDF'Enable'operationsuccessfullyexecutedfor
devicegroup'pocsun100data'.

Consistency mode takes one full RDFA cycle to activate.


To verify that consistency protection is enabled and the RDF status is consistent, query the
status by issuing the symrdf query command with rdfa option (which provides specific
details about the SRDF/A session for the device group).
symrdfgpocsun100dataqueryrdfa
DeviceGroup(DG)Name:pocsun100data
DG'sType:RDF1
DG'sSymmetrixID:000187461502
RDFASessionNumber:34
RDFACycleNumber:4
RDFASessionStatus:Active
RDFAMinimumCycleTime:00:00:30
RDFAAvgCycleTime:00:00:29
DurationofLastcycle:00:00:29
RDFASessionPriority:33
TracksnotCommittedtotheR2Side:0
TimethatR2isbehindR1:00:00:47
RDFAR1SidePercentCacheInUse:0
RDFAR2SidePercentCacheInUse:0

Source(R1)ViewTarget(R2)ViewMODES

STLIST
StandardANA
LogicalTR1InvR2InvKTR1InvR2InvRDFPair
DeviceDevETracksTracksSDevETracksTracksMDACSTATE

DEV00100E1RW00RW00E1WD00A..XConsistent
DEV00200E2RW00RW00E2WD00A..XConsistent
DEV00300E3RW00RW00E3WD00A..XConsistent
DEV00400E4RW00RW00E4WD00A..XConsistent
Total
Track(s)0000
MB(s)0.00.00.00.0
LegendforMODES:
M(odeofOperation):A=Async,S=Sync,E=Semisync,C=AdaptiveCopy
D(omino):X=Enabled,.=Disabled

EMC CONFIDENTIAL

version: 3.2.0

11 of 12

EMC Customer Symmetrix Procedure Generator

A(daptiveCopy):D=DiskMode,W=WPMode,.=ACpoff
C(onsistencyState):X=Enabled,.=Disabled,=N/A

This example represents a device group running in normal SRDF/A operations. In the
example, the Symmetrix has assigned an SRDF/A session number of 34 with a session priority
of 33. The SRDF/A session status for device group pocsun100data is active. If you performed
the same query on a device group that was in an RDF mode other than asynchronous, this
value would say inactive because there would be no running SRDF/A session associated with
it.
Other values to examine in your output are the cycle time statistics. Here you can get the
configurable parameter minimum cycle time, average cycle time, and the actual duration time
of the last cycle. The example device group shown is using a minimum cycle time of 30
seconds. This is the default value for SRDF/A. Recalling that the R2 devices are two cycle sets
behind the R1, you would assume that the R2 devices should be approximately behind the R1
device by 60 seconds. The output can verify this in the Time that R2 is behind R1 value.
These values are snapshots and should be considered approximate numbers.
If you look at the current SRDF modes, you can see that the example session is operating in
asynchronous mode (A) and that RDFA consistency protection is enabled (X) by the output of
A..X. You can also see that the RDF pair state is consistent. The consistent state signifies the
normal state of operation for device pairs operating in asynchronous mode.
Table of Contents

EMC CONFIDENTIAL

version: 3.2.0

12 of 12