Advanced Replication and Disaster Recovery in a Linux on System z Environment

Gail RileyEMC

March 15, 20109165

2

Objectives

After completing this session, you will be able to:• Discuss the basic considerations when implementing

replication • Understand the basic tasks needed to configure Local and

Remote Replication on a Symmetrix• Describe the processes for accessing a Local and Remote

replica in a Linux on System z environment

3

Replication – Business Recovery Tools

• TimeFinder – Local Replication• Provides multiple point-in-time copies of data to distribute business tasks

• This allows for simultaneous action of previously sequential business tasks• An example of this is the ability to backup a point-in-time copy of critical

data while production operations continue on the source data• Forms of Local Replication include stand alone point-in-time

copies and capacity savings point-in-time views• SRDF – Remote Replication

• Allows the movement of data between storage systems in the same room, to different buildings located across town, or thousands of miles apart

• Offers various disaster recovery levels • Enables the following operations:

• Disaster recovery, Disaster restart testing• Recovery from planned outages, Remote backup• Data center migration, Data replication and mobility

Linux Linux

LinuxLinux

4

Disaster Recovery versus Disaster Restart

• Most business critical applications have some level of data interdependencies• Disaster recovery

• Restoring previous copy of data and applying logs to that copy to bring it to a known point of consistency

• Generally implies the use of backup technology• Data copied to tape and then shipped off-site • Requires manual intervention during the restore and recovery processes

• Disaster restart • Process of restarting mirrored consistent copies of data and applications• Allows restart of all participating DBMS to a common point of consistency

utilizing automated application of recovery logs during DBMS initialization• The restart time is comparable to the length of time required for the

application to restart after a power failure

5

Forms of Local Replication

• Full Volume Copy - Clone• Data is copied from the Source Device to a Target Device of equal

size and emulation

• Pointer Based Replication - Snap• The Target Device is a virtual device housing a collection of pointer

between the Source and a reserve area for a point-in-time view

Source Target

Source Target

6

TimeFinder – Local Replication• Clone

• Provides up to 16 concurrent, instant Point-in-Time:

• Copies of a Volume or Dataset• Immediately accessible after activation

• The CLONE is completed in the background in the Symmetrix

• Target device can be larger than Source• Snap

• SNAP’S create logical point-in-time “snapshots”of a source volume

• Requires only a fraction of the source volume’s capacity (based on percentage of writes)

• Multiple Snapshots can be created from a source volume and are available immediately

• Snapshots support read / write processing• Supports mainframe and open systems host

environmentsCache-Based Pointer Map

Production ViewProduction View

Snapshot ViewSnapshot View

SaveArea

MVS OS/390Host

Source

Target

LPAR

LPAR

7

Forms of Remote Replication

• Data Distribution -• Data is copied from one storage system to another without

maintaining a consistent recoverable copy• Source ≠ Target

• Synchronous Replication• Identical copies of data across storage systems where writes are

committed across to remote systems/sites first which increases execution time • Source = Target

• Asynchronous Replication• Data is a point-in-time consistent copy but writes happen locally

and are sent across to remote systems/sites at a predetermined time• Source ≅ Target

8

Symmetrix Remote Data Facility:Two Site solutionsSRDF/Synchronous

No data exposure

Some performance impact

Limited distance

Source

Limited Distance

Target

R1 R2

SRDF/AsynchronousPredictable RPO

No performance impact

Unlimited distance

Only two copies of data required

Source

Unlimited Distance

Target

R1 R2

SRDF/ARData Movement solution

No performance impact

Unlimited distance

Source

Unlimited Distance

Target

R1 R2

9

Creating a TimeFinder Consistent Copy

• Different options depending on application and host requirements• Server

• Pause I/O at the Server Level to provide a Consistent Point-in-Time Copy • Application

• Stop the application and unmount the file system prior to activate or split

• Database hot backup mode• Database freeze/thaw

• Symmetrix based• Enginuity Consistency Assist (ECA) holds IO at the

Symmetrix until all Splits/Activate complete

Linux

Linux

10

SRDF/Consistency Groups Overview

• Preserves dependent-write consistency of devices • Ensures application dependent write consistency of the application data

remotely mirrored by SRDF operations in the event of a rolling disaster• Across multiple Symmetrix systems and/or multiple SRDF groups within a

Symmetrix system• A composite group comprised of SRDF

R1 or R2 devices• Configured to act in unison to maintain the

integrity of a database or application distributed across Symmetrix systems

• Included with SRDF/S and SRDF/A• SRDF/S using Enginuity Consistency Assist (ECA)• SRDF/A using Multi Session Consistency (MSC)

Ensures dependent-write consistency of the data remotely mirrored by SRDF

logicallysuspended

Fault event

11

Linux on System z Replication Devices

• The Symmetrix replicates disk drives• FBA

• SCSI disk drives configured as zfcp devices• CKD

• Dedicated to guest virtual machine

12

SRDF Lab Configuration

Primary Site192601700

Recovery Site 192601715

8F9F

7F10F

V-Max

LPAR z11z/VM

Linux

Fibre Channel or

GigE Switch

7F,10FRemote Director 8F, 9FRemote Director

zL1_rdfcgComposite Group Name

zL1_rdfcgComposite Group Name

4,10Remote RDF Group 4,10RDF Group 1715Symmetrix SID1700Symmetrix SID

Remote SymmetrixSource Symmetrix

R1CKD

R2CKD

Primary Site

Recovery Site LPAR x14

z/VMLinux

V-Max

13

Replication Management

• Open Systems• Solutions Enabler (SE)• Symmetrix Management

Console• z/OS

• Resource Pak• EMC z/OS Storage

Manager (EzSM)

IP Network

Client

z/VM LPAR

z/OS LPAR

Open Systems host over an IP Network – SMC

or SE

Linux as a–guest virtual

machine running SE

z/OS LPAR for Management via

EzSM

Guest Guest

14

EMC Replication Management Options

• Solutions Enabler – 7.1• On Linux – SUSE 10/11 and Red Hat 5.4• Open Systems hosts – Windows, Linux, UNIX

• Mainframe Enabler• z/OS

• Symmetrix Management Console (SMC)• Windows, Linux (x86), UNIX

• EMC z/OS Storage Manager (EzSM)• ISPF like Panel Menu Interface

• EMC products for TPF• TimeFinder Controls for TPF• SRDF Controls for TPF• ResourcePak for TPF

Replication Control for Linux on System zfromWindowsSymmetrix Management Console

16

Replication Management: Web Interface

• Symmetrix Management Console (SMC)• Web interface to interface directly with Storage System• Used for general storage management and Local and

Remote Replication operations• Provides Management at the Storage Subsystem Level

17

Local Replication Operations with SMC

• TimeFinder operations are invoked by selecting a DG or CG and using the Replication option

• TimeFinder• Mirror (DMX-4 and below)• Clone• Snap• SAVE Device Pool Management

TimeFinder Operations in SMC

18

TimeFinder/Clone Associate Pairs

19

TimeFinder/Clone Create Session

• Clone Actions• Create• Activate• Terminate• Establish (Full/Incremental)• Restore (Full/Incremental)• Recreate

20

TimeFinder/Clone Activate Session

21

Building SRDF Configuration with SMC• Use SRDF Replication Wizard

22

Identify Configuration

• Select between two site configurations

23

Identify Source Site

• Select the Source Symmetrix and R1 Devices

24

Select Target Symmetrix and Create Group

25

Verify Symmetrix Device Pairs

• Verify R1 to R2 as the R2 will be overwritten and any data on it lost

26

Automatically Create a Device Group

• Device Group is required to perform SRDF operations

27

Summary of SRDF Process

• Confirm SRDF configuration before execution

28

• SRDF Control• Perform Disaster Recover or

Concurrent operations on SRDF Devices

• SRDF Settings• Set the replication operation

mode for SRDF devices• SRDF Configuration

• Manage SRDF Groups• Manipulate SRDF Pairs

SRDF Operations Supported by SMC

SRDF - SMCReplication

29

SRDF Settings - Setting SRDF Mode

30

SRDF Control - Failover, Failback

Replication Control from z/OSMainframe Enabler for z/OS

32

Replication Management: z/OS

• Mainframe Enabler for z/OS• EMC ResourcePak Base for z/OS (Symmetrix Control Facility)• EMC Consistency Groups for z/OS• SRDF Host Component for z/OS• EMC TimeFinder/Clone Mainframe SNAP Facility• EMC TimeFinder/Mirror for z/OS• EMC TimeFinder Utility

• EMC z/OS Storage Manager (EzSM)• EMC products for TPF

• TimeFinder Controls for TPF• SRDF Controls for TPF• ResourcePak for TPF

• Provides Management at the Host and Storage Subsystem Level• Allows for application level control at the z/OS LPAR

33

Mainframe Enabler for z/OS

• The Enabler for EMC’s z/OS TimeFinder and SRDF Business Continuance solutions

• Symmetrix Control Facility (SCF) address space • Persistent EMC Subsystem for

SymmAPI functions:• Gathering and maintaining

device information• Performing automation

functions• Multi LPAR coordination via

Symmetrix• Provides a “Central Point of

Control”

Symmetrix ControlFacility

• EMCSAI• SNAPAPI• Automation• Meta Data

z/OS

Mainframe Enabler Components (e.g. TF SRDF HC)Or ISV Developed Products

IOS

34

SRDF Host Component for z/OS

• Host based utility for monitoring and managing of TimeFinder and SRDF solutions

• Runs as a started task• Multiple user interfaces

• z/OS operator commands • Batch Interface to ease automation• ISPF like interface for ad-hoc usage • REXX support for common procedures• EMCSPE: Stored Procedure Executive, with common

scripts

#SQ GLOBAL#SQ LINK,0100,E#SQ RDFGRP,0100#SQ VOL,SCFG(CE01S02GNS)

Replication Control from Linux for System z

Solutions Enabler for Linux on System z

36

SRDF Lab Configuration

Primary Site192601700

Recovery Site 192601715

8F9F

7F10F

V-Max

LPAR z11

Fibre Channel or

GigE Switch

7F,10FRemote Director 8F, 9FRemote Director

zL1_rdfcgComposite Group Name

zL1_rdfcgComposite Group Name

4,10Remote RDF Group 4,10RDF Group 1715Symmetrix SID1700Symmetrix SID

Remote SymmetrixSource Symmetrix

R1CKD

R2CKD

Primary Site

Recovery Site

LPAR x14

V-Max

37

CKD Lab Environment – Primary Site

LN150148Red Hat 5.x

EMC SolutionsEnabler

LN150150SLESEMC

SolutionsEnabler

z/VM 5.4 LPAR

FICON

CHPID 83CHPID 82

9g:0

6g:0 SYMMserial

number1700

128a-1291

0100

Guest Dev Addr

022A-0231-128a-

12911196-119D

00e700AA214700e7

Remote SLV (R2)

Local Clone SLV

z/VM IODEVICE

Symmetrix Logical

Volumes (R1)

V-Max1700

38

CKD Lab Environment – Recovery Site

DR150148Red Hat 5.x

EMC SolutionsEnabler

DR150150SLESEMC

SolutionsEnabler

z/VM 5.4 LPAR

FICON

CHPID 89CHPID 88

8g:0

7g:0 SYMMserial

number1715

128A-1291

0100

Guest Dev Addr

-0290-0297

26F0-26F7022A - 0231

-00EA23FA00e7

Remote SLV

Local Clone SLV

z/VM IODEVICE

SymmetrixLogical

Volumes (R2)

V-Max1715

39

Replication Management: Linux on System z

• Solutions Enabler – 7.1• Linux on System z SLES 10/11 and Redhat 5.4• Open Systems hosts – Windows, Linux, UNIX

• Provides Management at the Host and Storage Subsystem Level• Allows for application level control at the Linux on System z

Server

40

List Linux Virtual Machines Devices

• Use vmcp to query the virtual machine devices • Make sure virtual addresses are consistent across sites

# vmcp q v all……………………DASD 0100 ON DASD 2147 R/W 0X0100 SUBCHANNEL = 000C…………………DASD 128A ON DASD 128A R/W 0X128A SUBCHANNEL = 000EDASD 128B ON DASD 128B R/W 0X128B SUBCHANNEL = 000FDASD 128C ON DASD 128C R/W 0X128C SUBCHANNEL = 0010DASD 128D ON DASD 128D R/W 0X128D SUBCHANNEL = 0011DASD 128E ON DASD 128E R/W 0X128E SUBCHANNEL = 0013DASD 128F ON DASD 128F R/W 0X128F SUBCHANNEL = 0014DASD 1290 ON DASD 1290 R/W 0X1290 SUBCHANNEL = 0015DASD 1291 ON DASD 1291 R/W 0X1291 SUBCHANNEL = 0016

# vmcp q v all……………………DASD 0100 ON DASD 2147 R/W 0X0100 SUBCHANNEL = 000C…………………DASD 128A ON DASD 128A R/W 0X128A SUBCHANNEL = 000EDASD 128B ON DASD 128B R/W 0X128B SUBCHANNEL = 000FDASD 128C ON DASD 128C R/W 0X128C SUBCHANNEL = 0010DASD 128D ON DASD 128D R/W 0X128D SUBCHANNEL = 0011DASD 128E ON DASD 128E R/W 0X128E SUBCHANNEL = 0013DASD 128F ON DASD 128F R/W 0X128F SUBCHANNEL = 0014DASD 1290 ON DASD 1290 R/W 0X1290 SUBCHANNEL = 0015DASD 1291 ON DASD 1291 R/W 0X1291 SUBCHANNEL = 0016

41

List Symmetrix Devices

• Verify Symmetrix Devices are available on each Symmetrix

# symdev list -range 1196:119d -sid 1700

Symmetrix ID: 000192601700

Device Name Directors Device----------------------- ------------- ------------------------------------CapSym Physical SA :P DA :IT Config Attribute Sts (MB)----------------------- ------------- --------------------------------------1196 Not Visible ***:* 06B:D7 RDF1+Mir Grp'd RW 9021197 Not Visible ***:* 09B:D2 RDF1+Mir Grp'd RW 9021198 Not Visible ***:* 05C:C0 RDF1+Mir Grp'd RW 9021199 Not Visible ***:* 09A:C0 RDF1+Mir Grp'd RW 902119A Not Visible ***:* 06D:C0 RDF1+Mir Grp'd RW 902119B Not Visible ***:* 09D:C1 RDF1+Mir Grp'd RW 902119C Not Visible ***:* 05A:D7 RDF1+Mir Grp'd RW 902119D Not Visible ***:* 10C:C1 RDF1+Mir Grp'd RW 902

# symdev list -range 1196:119d -sid 1700

Symmetrix ID: 000192601700

Device Name Directors Device----------------------- ------------- ------------------------------------CapSym Physical SA :P DA :IT Config Attribute Sts (MB)----------------------- ------------- --------------------------------------1196 Not Visible ***:* 06B:D7 RDF1+Mir Grp'd RW 9021197 Not Visible ***:* 09B:D2 RDF1+Mir Grp'd RW 9021198 Not Visible ***:* 05C:C0 RDF1+Mir Grp'd RW 9021199 Not Visible ***:* 09A:C0 RDF1+Mir Grp'd RW 902119A Not Visible ***:* 06D:C0 RDF1+Mir Grp'd RW 902119B Not Visible ***:* 09D:C1 RDF1+Mir Grp'd RW 902119C Not Visible ***:* 05A:D7 RDF1+Mir Grp'd RW 902119D Not Visible ***:* 10C:C1 RDF1+Mir Grp'd RW 902

42

# symdg create -type rdf1 zL_cl_dg1# symld -g zL_cl_dg1 add dev 00e7# symld -g zL_cl_dg1 add dev 00aa -tgt# symdg show zL_cl_dg1

Group Name: zL_cl_dg1

Group Type : RDF1 (RDFA)Standard (STD) Devices (1):

{--------------------------------------------------------------------

Sym CapLdevName PdevName Dev Att. Sts (MB)--------------------------------------------------------------------DEV001 N/A 00E7 RW 8120}

TGT Devices Locally-associated (1):{--------------------------------------------------------------------

Sym CapLdevName PdevName Dev Att. Sts (MB)--------------------------------------------------------------------TGT001 N/A 00AA RW 8120

# symdg create -type rdf1 zL_cl_dg1# symld -g zL_cl_dg1 add dev 00e7# symld -g zL_cl_dg1 add dev 00aa -tgt# symdg show zL_cl_dg1

Group Name: zL_cl_dg1

Group Type : RDF1 (RDFA)Standard (STD) Devices (1):

{--------------------------------------------------------------------

Sym CapLdevName PdevName Dev Att. Sts (MB)--------------------------------------------------------------------DEV001 N/A 00E7 RW 8120}

TGT Devices Locally-associated (1):{--------------------------------------------------------------------

Sym CapLdevName PdevName Dev Att. Sts (MB)--------------------------------------------------------------------TGT001 N/A 00AA RW 8120

TimeFinder/Clone Operations• Create device group

• Add source device and associate target to device group

43

# symclone -g zL_cl_dg1 create -tgt -precopy -differential

Execute 'Create' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Create' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Create' operation successfully executed for device group'zL_cl_dg1'.

# symclone -g zL_cl_dg1 create -tgt -precopy -differential

Execute 'Create' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Create' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Create' operation successfully executed for device group'zL_cl_dg1'.

TimeFinder/Clone Operations

• Creating a session builds relationship between the source and target• No data is immediately copied unless the –precopy flag is specified• Use the –differential

• If the Clone will be repeatedly refreshed (recreate)• If Clone might be used for incremental restore back to the source

44

# symclone -g zL_cl_dg1 query

Device Group (DG) Name: zL_cl_dg1DG's Type : RDF1DG's Symmetrix ID : 000192601700

Source Device Target Device State Copy--------------------------------- ---------------------------- ------------ ----

Protected Modified ModifiedLogical Sym Tracks Tracks Logical Sym Tracks CGDP SRC <=> TGT (%)--------------------------------- ---------------------------- ------------ ----DEV001 00E7 102936 0 TGT001 00AA 0 XXX. PreCopy 31

Total -------- -------- --------Track(s) 102936 0 0MB(s) 5562.6 0.0 0.0

Legend:(C): X = The background copy setting is active for this pair.

. = The background copy setting is not active for this pair.(G): X = The Target device is associated with this group.

. = The Target device is not associated with this group.……………………………………….

# symclone -g zL_cl_dg1 query

Device Group (DG) Name: zL_cl_dg1DG's Type : RDF1DG's Symmetrix ID : 000192601700

Source Device Target Device State Copy--------------------------------- ---------------------------- ------------ ----

Protected Modified ModifiedLogical Sym Tracks Tracks Logical Sym Tracks CGDP SRC <=> TGT (%)--------------------------------- ---------------------------- ------------ ----DEV001 00E7 102936 0 TGT001 00AA 0 XXX. PreCopy 31

Total -------- -------- --------Track(s) 102936 0 0MB(s) 5562.6 0.0 0.0

Legend:(C): X = The background copy setting is active for this pair.

. = The background copy setting is not active for this pair.(G): X = The Target device is associated with this group.

. = The Target device is not associated with this group.……………………………………….

TimeFinder/Clone Operations• Session created

• Review PreCopy status

45

# symclone -g zL_cl_dg1 activate -tgt

Execute 'Activate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Activate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Activate' operation successfully executed for device group'zL_cl_dg1'.

# symclone -g zL_cl_dg1 activate -tgt

Execute 'Activate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Activate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Activate' operation successfully executed for device group'zL_cl_dg1'.

TimeFinder/Clone Operations• activate a session makes a Target R/W accessible to host

• Establishes point-in-time copy• Three copy options:

• Copy on Access (default)• Copy on Write (-nocopy when session created)• Full background copy (-copy)

46

# symclone -g zL_cl_dg1 create -tgtExecute 'Create' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Create' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Create' operation successfully executed for device group'zL_cl_dg1'.# symclone -g zL_cl_dg1 query

Device Group (DG) Name: zL_cl_dg1DG's Type : RDF1DG's Symmetrix ID : 000192601700

Source Device Target Device State Copy--------------------------------- ---------------------------- ------------ ----

Protected Modified ModifiedLogical Sym Tracks Tracks Logical Sym Tracks CGDP SRC <=> TGT (%)--------------------------------- ---------------------------- ------------ ----DEV001 00E7 150255 0 TGT001 00AA 0 XXX. Created 0

Total -------- -------- --------Track(s) 150255 0 0MB(s) 8119.6 0.0 0.0

# symclone -g zL_cl_dg1 create -tgtExecute 'Create' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Create' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Create' operation successfully executed for device group'zL_cl_dg1'.# symclone -g zL_cl_dg1 query

Device Group (DG) Name: zL_cl_dg1DG's Type : RDF1DG's Symmetrix ID : 000192601700

Source Device Target Device State Copy--------------------------------- ---------------------------- ------------ ----

Protected Modified ModifiedLogical Sym Tracks Tracks Logical Sym Tracks CGDP SRC <=> TGT (%)--------------------------------- ---------------------------- ------------ ----DEV001 00E7 150255 0 TGT001 00AA 0 XXX. Created 0

Total -------- -------- --------Track(s) 150255 0 0MB(s) 8119.6 0.0 0.0

TimeFinder/Clone Create – Protected Tracks• All tracks marked as protected

47

TimeFinder/Clone Operations• Recreate Clone session

• Establishes new point-in-time copy after activation• Only the changed tracks since last activation are copied

• Session must have been created with –copy or –precopy and –differential option

# symclone -g zL_cl_dg1 recreate -tgt

Execute 'Recreate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Recreate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Recreate' operation successfully initiated for device group'zL_cl_dg1'.

[root@ln150148 ~]# symclone -g zL_cl_dg1 activate -tgt

Execute 'Activate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Activate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Activate' operation successfully executed for device group

# symclone -g zL_cl_dg1 recreate -tgt

Execute 'Recreate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Recreate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Recreate' operation successfully initiated for device group'zL_cl_dg1'.

[root@ln150148 ~]# symclone -g zL_cl_dg1 activate -tgt

Execute 'Activate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Activate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Activate' operation successfully executed for device group

48

TimeFinder/Clone Operations• Terminate deletes the pairing information• If not in a COPIED state, target will not be a

complete copy and thus unusable

# symclone -g zL_cl_dg1 terminate -tgt

Execute 'Terminate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Terminate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Terminate' operation successfully executed for device group'zL_cl_dg1'.

# symclone -g zL_cl_dg1 terminate -tgt

Execute 'Terminate' operation for device group'zL_cl_dg1' (y/[n]) ? y

'Terminate' operation execution is in progress fordevice group 'zL_cl_dg1'. Please wait...

'Terminate' operation successfully executed for device group'zL_cl_dg1'.

49

Creating Dynamic SRDF Groups

# symrdf -v addgrp -label rdf-10 -rdfg 10 -sid 1700 -dir 8F -remote_rdfg10 -remote_sid 1715 -remote_dir 7F –noprompt

# symcfg list -ra 8f -sid 1700

Symmetrix ID: 000192601700

S Y M M E T R I X R D F D I R E C T O R S

Remote Local RemoteIdent Symb Num Slot Type Attr SymmID RA Grp RA Grp Status

RF-8F 08F 88 8 RDF-R1 - 000192601715 4 (03) 4 (03) Online- 000192601715 10 (09) 10 (09)- 000192601715 11 (0A) 11 (0A)

# symrdf -v addgrp -label rdf-10 -rdfg 10 -sid 1700 -dir 8F -remote_rdfg10 -remote_sid 1715 -remote_dir 7F –noprompt

# symcfg list -ra 8f -sid 1700

Symmetrix ID: 000192601700

S Y M M E T R I X R D F D I R E C T O R S

Remote Local RemoteIdent Symb Num Slot Type Attr SymmID RA Grp RA Grp Status

RF-8F 08F 88 8 RDF-R1 - 000192601715 4 (03) 4 (03) Online- 000192601715 10 (09) 10 (09)- 000192601715 11 (0A) 11 (0A)

50

RDF Group Details# symcfg -rdfg all list -sid 1700

Symmetrix ID : 000192601700

S Y M M E T R I X R D F G R O U P S

Local Remote Group RDFA Info-------------- --------------------- ----------------------- -----------------

LL Flags Dir Flags CycleRA-Grp (sec) RA-Grp SymmID T Name LPDS Cfg CSRM time Pri

-------------- --------------------- ----------------------- ----- ----- ---4 ( 3) 10 4 ( 3) 000192601715 D RDF-4 XX.. F-S -IS- 30 33

10 ( 9) 10 10 ( 9) 000192601715 D RDF-10 .X.. F-S -IS- 30 3311 ( A) 10 11 ( A) 000192601715 D RDFG_11 .X.. F-S .AS- 30 33

Legend:? : UnknownGroup (T)ype : S = Static, D = DynamicDirector (C)onfig : F-S = Fibre-Switched, F-H = Fibre-Hub

G = GIGE, E = ESCON, T = T3, - = N/AGroup Flags :

Prevent Auto (L)ink Recovery : X = Enabled, . = DisabledPrevent RAs Online Upon (P)ower On: X = Enabled, . = DisabledLink (D)omino : X = Enabled, . = Disabled(S)TAR mode : N = Normal, R = Recovery, . = OFF

RDFA Flags :(C)onsistency : X = Enabled, . = Disabled, - = N/A…………………………………….

# symcfg -rdfg all list -sid 1700

Symmetrix ID : 000192601700

S Y M M E T R I X R D F G R O U P S

Local Remote Group RDFA Info-------------- --------------------- ----------------------- -----------------

LL Flags Dir Flags CycleRA-Grp (sec) RA-Grp SymmID T Name LPDS Cfg CSRM time Pri

-------------- --------------------- ----------------------- ----- ----- ---4 ( 3) 10 4 ( 3) 000192601715 D RDF-4 XX.. F-S -IS- 30 33

10 ( 9) 10 10 ( 9) 000192601715 D RDF-10 .X.. F-S -IS- 30 3311 ( A) 10 11 ( A) 000192601715 D RDFG_11 .X.. F-S .AS- 30 33

Legend:? : UnknownGroup (T)ype : S = Static, D = DynamicDirector (C)onfig : F-S = Fibre-Switched, F-H = Fibre-Hub

G = GIGE, E = ESCON, T = T3, - = N/AGroup Flags :

Prevent Auto (L)ink Recovery : X = Enabled, . = DisabledPrevent RAs Online Upon (P)ower On: X = Enabled, . = DisabledLink (D)omino : X = Enabled, . = Disabled(S)TAR mode : N = Normal, R = Recovery, . = OFF

RDFA Flags :(C)onsistency : X = Enabled, . = Disabled, - = N/A…………………………………….

51

Create SRDF Pair Example

# symrdf –file pair.txt –sid 1700 –rdfg 4 –type r1 –establish createpair

An RDF 'Create Pair' operation execution is in progress for devicefile 'pairf'. Please wait...

Create RDF Pair in (0398,04)....................................Done.Mark target device(s) in (0398,04) for full copy from source....Started.Device: 0330 .................................................. Marked.Mark target device(s) in (0398,04) for full copy from source....Done.Merge track tables between source and target in (0398,01).......Started.Device: 01D0 .................................................. Merged.Merge track tables between source and target in (0398,01).......Done.Resume RDF link(s) for device(s) in (0398,04)...................Started.Resume RDF link(s) for device(s) in (0398,04)...................Done.

The RDF 'Create Pair' operation successfully executed for devicefile ‘pair'.

# symrdf –file pair.txt –sid 1700 –rdfg 4 –type r1 –establish createpair

An RDF 'Create Pair' operation execution is in progress for devicefile 'pairf'. Please wait...

Create RDF Pair in (0398,04)....................................Done.Mark target device(s) in (0398,04) for full copy from source....Started.Device: 0330 .................................................. Marked.Mark target device(s) in (0398,04) for full copy from source....Done.Merge track tables between source and target in (0398,01).......Started.Device: 01D0 .................................................. Merged.Merge track tables between source and target in (0398,01).......Done.Resume RDF link(s) for device(s) in (0398,04)...................Started.Resume RDF link(s) for device(s) in (0398,04)...................Done.

The RDF 'Create Pair' operation successfully executed for devicefile ‘pair'.

52

Linux Replica Device Considerations

• Both Local and Remote Replication have device access considerations• Dedicated CKD or FCP/FBA devices are supported• Use device-by-path, not device-id for device setup• Replicated devices have the same virtual addresses at both sites• SCSI LUN mapping is the same at both sites for both Symmetrix

• Other considerations• Identify/minimize hardcoded application dependencies

• Network – IP, hostname, etc.• Update network, DNS as appropriate• Automate the process wherever possible

53

Solutions Enabler Considerations

• Gatekeeper devices are required for Solutions Enabler communication to the Symmetrix

• Use Group Name Services (GNS)• If booting off a Symmetrix device, at backup site, run symcfg discover to

refresh Symmetrix connectivity

• If Linux is running under z/VM with CKD• Solutions Enabler with only CKD devices requires gatekeeper devices be

setup as rdev unsupported devclass DASD because CP prevents certain calls

• These devices will be seen as CGK from Solutions Enabler• Devices must be referenced by Symmetrix Device Name• Create special CKD gatekeeper devices at backup site also• PAV is not supported with rdev unsupported devices so ensure gatekeeper

devices are across multiple paths

54

Solutions Enabler Considerations

• If Linux is running under z/VM – FCP/FBA• Assign SCSI gatekeeper devices• Devices can be referenced by Symmetrix Logical Device

name• Create gatekeeper devices accessible on backup site virtual

machine• If booting off Symmetrix, at backup site, run symcfg discover

to refresh Symmetrix connectivity

• If Linux is running native in a LPAR• There are no special considerations for Solutions Enabler

55

Summary

• Planning is key to successful replication• Local replication is very flexible

• SNAP• CLONE

• Remote Replication has several options depending on RPO/RTO• Sync• Async• Data Mobility

• Management of the Symmetrix and replication can by done by• Linux on System z• z/OS• Open Systems – Linux, Unix, Windows