Performing Non-Disruptive Migration Using SRDF/Metro: Abstract

Performing Non-Disruptive Migration
Using SRDF/Metro

ABSTRACT:
This document shows overall steps to perform non-disruptive migration of application from VMAX3 to another using
SRDF/Metro technology
Date: July 7, 2016

Version: 1.0

Prepared for: Prepared by:
Cisco GIS Chirag Patel

170 West Tasman Advisory Solution Architect
San Jose, CA 95134
Table of Contents

Table of Contents ......................................................................................................................................... 2
SRDF/Metro Overview ........................................................................................................................ 3
Bias Option ............................................................................................................................................... 3
Witness Array Option ............................................................................................................................... 3
SRDF/Metro Requirements ....................................................................................................................... 3
Non-Disruptive Migration Using SRDF/Metro ............................................................................ 4
Existing Environment ................................................................................................................................ 4
High-Level SRDF/Metro Storage Migration Steps .................................................................................... 5
Host and Storage Environment Verification Check List ............................................................................ 6
SRDF Group Creation Between Source and Target Frame ........................................................................ 6
Device Creation On Target Frame ............................................................................................................ 7
Perform SRDF/Metro “Createpair” Operation .......................................................................................... 9
Verify Devices in “ActiveBias” Mode ...................................................................................................... 12
Zone and Mask Devices from Target Frame ........................................................................................... 13
Change SRDF/Metro Bias to Target Frame ............................................................................................ 21
Remove Linux Source Frame Devices on the Hosts ................................................................................. 23
Perform Suspend Operation On SRDF/Metro Group .............................................................................. 29
Remove Masking from Source Frame Devices ........................................................................................ 30
Perform “Deletepair” Operation on SRDF/Metro Devices ...................................................................... 31

SRDF/Metro Overview
SRDF/Metro provides High Availability (HA) for an application at the VMAX3 array level. In traditional
SRDF, R1 devices are Read/Write accessible. R2 devices are Read Only/ Write Disabled. Contrary in
SRDF/Metro, R2 devices on VMAX3 arrays are Read/Write accessible to hosts. Furthermore, R2 devices
assume the same external device identity (geometry, device WWN) as their R1. Thus, hosts can write to
both the R1 and R2 side of the device pair.

In the event of link or other failures, SRDF/Metro uses one of two options to determine which side of an
SRDF device pair remains R/W accessible to the host. These two options are following.
• Bias Option
• Witness Array Option
Bias Option
Bias option provides ability to predetermined which side of an SRDF device pair remains R/W accessible
to the host in event of failure. SRDF/Metro bias side can also be changed anytime during SRDF/Metro
operation.

Due to these SRDF/Metro feature sets bias capability, SRDF/Metro bias option can be used for
performing non-disruptive migrations of applications.
Witness Array Option

By default, SRDF/Metro will use a Witness Array to determine the bias device when the link is
Suspended or Partitioned. The Witness array is not the Array that contains the R1 or R2 devices in an
SRDF/Metro configuration but a separate Array. A user must configure Witness RDF group between the
R1 VMAX3 and Witness Array and another Witness RDF group between the R2 VMAX3 and Witness
Array. These Witness RDF groups do not contain any devices. These are empty RDF groups.

Note: Witness array can be VMAX, VMAX2 or VMAX3
• VMAX & VMAX2: Requires microcode 5876 with fix 82877
• VMAX3: Requires HyperMax 5977 Q1 2015 with fix 82878 or Hypermax 5977 Q3 2015
SRDF/Metro Requirements
Following are SRDF/Metro Requirements
• SRDF/Metro is only supported on VMAX3
• Minimum Hypermax Q3 2015. (However, Hypermax Q1 2016 has added more support to
environment)
• SRDF/Metro licenses on participating VMAX3 arrays.
• SRDF Protocol: Fibre Channel or Gigabit Ethernet
• Solution Enabler: 8.1 or above
• Multipath Software: Please use support matrix for detail list.

Non-Disruptive Migration Using

SRDF/Metro
This document demonstrates overall steps to perform non-disruptive migration of application running
on RHEL Linux from one VMAX3 to another VMAX3 using SRDF/Metro technology. Please do not use this
documentation as a procedural runbook to perform migration as infrastructure environments can differ
from described here in this documentation.
Existing Environment
In existing environment, we have four node Oracle RAC clusters running on RHEL 6.6. These nodes are
getting storage from VMAX3 frame HK196801346.

Following table provides information on Oracle RAC node.

OS OS
Server Name Application
Version Level
lnxdb-svl-13 RHEL 6.6 Oracle RAC with ASM

Following table provides zoning configuration that consists between four node clusters and VMAX3 1346
frame.

Server Name HBA WWPN Frame FA Port
vHBA1 200b1200000000be 1D:28
vHBA2 200b1200000000ee 2D:29
lnxdb-svl-13
vHBA3 200b12000000008c 3D:28
vHBA4 200b12000000009c 4D:29
vHBA1 200b12000000003d 1D:28
vHBA2 200b12000000002d 2D:29
lnxdb-svl-14
vHBA3 200b1200000000eb 3D:28
vHBA4 200b1200000000bb HK196801346 4D:29
vHBA1 200b12000000007c 1D:28
vHBA2 200b12000000006c 2D:29
lnxdb-svl-15
vHBA3 200b1200000000cb 3D:28
vHBA4 200b1200000000ab 4D:29
vHBA1 200b12000000001d 1D:28
lnxdb-svl-16 vHBA2 200b12000000000d 2D:29
vHBA3 200b12000000008b 3D:28
vHBA4 200b12000000009b 4D:29

Following table provides masking information fromVMAX3 1346 to four nodes cluster servers. It is
essential to gather this information as it helps in migration planning.

Port
Type Of Purpose Of Masking Initiator Group
Initiator Group Port Group Group Storage Group Storage Group Member SYMDEV IDs
Storage Storage View Member
Member
IG_LNXDB_SVL-
13,
1D:28,
Shared DB File, MV_lnxdb- IG_LNXDB_SVL- PG_LNXDB-
IG_LNXDB_SVL- 2D:29, SG_lnxdb-svl- SG_DBBS2DM1_DB_PAR_ARCH_New, 003B9:003C4,
With In ARCH, Redo, svl-13- 14, SVL-
13_14_15_16 3D:28, 13-16_Shared SG_DBBS2DM1_REDO_New 003D1:003D8
Four Nodes etc… 16_Shared IG_LNXDB_SVL- 13_14_15_16
4D:29
15,
IG_LNXDB_SVL-16
1D:28,
Dedicated Oracle PG_LNXDB-
MV_lnxdb- IG_LNXDB_SVL- vHBAs of lnxdb- 2D:29, SG_lnxdb-svl-
to lnxdb- Binary File SVL- No Child Storage Groups 003C5:003C7
svl-13_Local 13 svl-13 3D:28, 13_local_new
svl-13 Systems 13_14_15_16
4D:29
1D:28,
to lnxdb- Binary File SVL- No Child Storage Groups 003C8:003CA
svl-14 Systems 13_14_15_16
4D:30
1D:28,
to lnxdb- Binary File SVL- No Child Storage Groups 003CB:003CD
svl-15 Systems 13_14_15_16
4D:30
1D:28,
to lnxdb- Binary File SVL- No Child Storage Groups 003CE:003D0
svl-16 Systems 13_14_15_16
4D:30
1D:28,
Dedicated PG_LNXDB-
Gatekeeper MV_lnxdb- IG_LNXDB_SVL- vHBAs of lnxdb- 2D:29, SG_lnxdb-svl-
to lnxdb- SVL- No Child Storage Groups 001B0:001B1
devices svl-13_GK 13 svl-13 3D:28, 13_gk
svl-13 13_14_15_16
4D:29
1D:28,
Dedicated PG_LNXDB-
svl-14 13_14_15_16
4D:30
1D:28,
Dedicated PG_LNXDB-
svl-15 13_14_15_16
4D:30
1D:28,
Dedicated PG_LNXDB-
svl-16 13_14_15_16
4D:30
High-Level SRDF/Metro Storage Migration Steps

We will be demonstrating non-disruptive storage migration of above Oracle RAC database from VMAX3
frame HK196801346 (Symdev IDs 03B9:03D8) to new VMAX3 frame HK196801695. This will include
devices that hosts shared Oracle RAC database as well as dedicated Oracle binary filesystems.

We will occasionally refer frame HK196801346 as source frame and frame HK196801695 as target
frame.

Following are the high-level steps needed to perform this migration.
• Host and Storage Environment Verification Check List
• SRDF Group Creation Between Source and Target Frame
• Device Creation On Target Frame

• Perform SRDF/Metro “Createpair” Operation
• Verify Devices in “ActiveBias” Mode
• Zone and Mask Devices from Target Frame
• Change SRDF/Metro Bias to Target Frame
• Remove Linux Source Frame Devices on Hosts
• Perform Suspend Operation On SRDF/Metro Group
• Remove Masking from Source Frame Devices
• Perform “Deletepair” Operation on SRDF/Metro Devices
Host and Storage Environment Verification Check List

Before moving forward with storage migration, host and storage environment need to be verified
against EMC support matrix. Following check lists will help identify and verify environment information.
If any of the check list fails, please remediate before moving forward with migration.

Check List Information Pass / Fail?
Is host OS supported in EMC Support Matrix? þ ý
Is host's multipath software supported in EMC Support Matrix? þ ý
Is host's cluster software supported in EMC Support Matrix? þ ý
Is Solution Enabler installed on host? þ ý
Are SRDF/Metro licenses installed on source and target VMAX3 frames? þ ý
Is SRDF configured on source and target frame? þ ý
Are hosts, source and target frames reside in same data center and SAN Fabrics? þ ý
Will target frame able to handle workload after storage migration? þ ý
Gathered source device (/dev/sd) list from host? þ ý
Gathered source device wwn presented host that are participating in migration? þ ý
Is host change rate through put below planned SRDF RA ports’ aggregate link? þ ý

SRDF Group Creation Between Source and Target Frame

In order to establish any SRDF relationship between source and target frame, SRDF group needs to be
created. We are using SRDF fiber channel protocol in our example. Thus, first we need to zone source
and target RA ports participating in SRDF and following it by SRDF “addgrp” command.

Note: Existing RDF group can be used given that it does not have any SRDF devices. This is one of the
requirement in SRDF/Metro setup since SRDF operation command changes states on all the devices
participating in SRDF group.

Following table provides zoning configuration between source and target RA ports.

Source Frame Source RA Port Target Frame Target RA Port
1E:05 1E:05
HK196801346 HK196801695
2E:06 2E:06

Following section provides SRDF group creation and verification CLI output.

$sudo symrdf addgrp -label rdfgrp40 -rdfg 40 -sid 000196801346 -dir 1E:5,2E:6 -remote_rdfg 40 -remote_sid
000196801695 -remote_dir 1E:5,2E:6
Execute a Dynamic RDF Addgrp operation for group

'rdfgrp40' on Symm: 000196801346 (y/[n]) ? y
Successfully Added Dynamic RDF Group 'rdfgrp40' for Symm: 000196801346
$sudo symcfg -sid 1346 -rdfg 40 -ra all -switched list
Symmetrix ID: 000196801346 (Local)
S Y M M E T R I X R D F D I R E C T O R S
Local Group Link Remote

--------------------- -------------- ---- -------------------------------
Po Po
r FLGS FLGS r
Ident t RA Grp T Name SH SH SymmID Ident t RA Grp
------ -- -------- - -------------- ---- ------------ ------ -- --------
RF-1E 4 - - - -- -- - - - -
5 40 (27) D rdfgrp40 .. X. 000196801695 RF-1E 5 40 (27)
7 - - - -- -- - - - -
RF-2E 4 - - - -- -- - - - -
5 - - - -- -- - - - -
6 40 (27) D rdfgrp40 .. X. 000196801695 RF-2E 6 40 (27)
RF-3E 4 - - - -- -- - - - -
5 - - - -- -- - - - -
6 - - - -- -- - - - -
7 - - - -- -- - - - -
RF-4E 4 - - - -- -- - - - -
5 - - - -- -- - - - -
6 - - - -- -- - - - -
7 - - - -- -- - - - -
Legend:
Group (T)ype : D = Dynamic, S = Static, - = Unknown
Group Flags :
RDF (S)oftware Compression : X = Enabled, . = Disabled, - = N/A
RDF (H)ardware Compression : X = Enabled, . = Disabled, - = N/A
Link Flags :
RDF (S)oftware Compression : X = Supported, . = Not supported, - = N/A
RDF (H)ardware Compression : X = Supported, . = Not supported, - = N/A
Device Creation On Target Frame

We will create new target devices on target frame with exact same number and cylinder count of source
devices.

Following section provides new target devices creation output.

$sudo symconfigure -sid $sid -cmd "create dev count=24, config=TDEV, emulation=FBA, size=143087 cyl;" commit -v -nop
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.

Processing symmetrix 000196801695
{
create dev count=4, size=3 cyl, emulation=FBA, config=TDEV,
mvs_ssid=0;
Performing Access checks..................................Allowed.

Checking Device Reservations..............................Allowed.
Initiating COMMIT of configuration changes................Queued.
COMMIT requesting required resources......................Obtained.
Step 007 of 011 steps.....................................Executing.
Local: COMMIT............................................Done.
New symdevs: 00282:00299 [TDEVs]

Terminating the configuration change session..............Done.
The configuration change session has successfully completed.
$sudo symconfigure -sid $sid -cmd "create dev count=8, config=TDEV, emulation=FBA, size=4370 cyl;" commit -v -nop
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.

Processing symmetrix 000196801695
{
create dev count=4, size=3 cyl, emulation=FBA, config=TDEV,
mvs_ssid=0;
}
Performing Access checks..................................Allowed.

Checking Device Reservations..............................Allowed.
Initiating COMMIT of configuration changes................Queued.
COMMIT requesting required resources......................Obtained.
Step 007 of 011 steps.....................................Executing.
Local: COMMIT............................................Done.
New symdevs: 0029A:002A1 [TDEVs]

Terminating the configuration change session..............Done.
The configuration change session has successfully completed.
$sudo symdev -sid 1695 -dev 00282:02A1 list
Symmetrix ID: 000196801695
Device Name Dir Device

---------------------------- ------- -------------------------------------
Cap
Sym Physical SA :P Config Attribute Sts (MB)
---------------------------- ------- -------------------------------------
00282 Not Visible ???:??? TDEV N/Grp'd RW 268288
0028A Not Visible ???:??? TDEV N/Grp'd RW 268288
0028B Not Visible ???:??? TDEV N/Grp'd RW 268288
0028C Not Visible ???:??? TDEV N/Grp'd RW 268288
0028D Not Visible ???:??? TDEV N/Grp'd RW 268288
0028E Not Visible ???:??? TDEV N/Grp'd RW 268288
0028F Not Visible ???:??? TDEV N/Grp'd RW 268288
0029A Not Visible ???:??? TDEV N/Grp'd RW 8194
0029B Not Visible ???:??? TDEV N/Grp'd RW 8194
0029C Not Visible ???:??? TDEV N/Grp'd RW 8194
0029D Not Visible ???:??? TDEV N/Grp'd RW 8194

0029E Not Visible ???:??? TDEV N/Grp'd RW 8194
0029F Not Visible ???:??? TDEV N/Grp'd RW 8194
002A0 Not Visible ???:??? TDEV N/Grp'd RW 8194
002A1 Not Visible ???:??? TDEV N/Grp'd RW 8194
Perform SRDF/Metro “Createpair” Operation

Once new target devices are created on target frame, we will need to perform SRDF createpair
operation for source and target devices. This will put source and target devices in mirrored like state.

One of the method of performing this operation is via pairing file. We will be using this method
throughout this documentation.

Following section provide CLI output for SRDF createpair operations.

$cat srdf_metro_1346-1695.pair
#1346 1695
003B9 00282 #272G_DBFiles
003BA 00283 #272G_DBFiles
003BB 00284 #272G_DBFiles
003BC 00285 #272G_DBFiles
003BD 00286 #272G_DBFiles
003BE 00287 #272G_DBFiles
003BF 00288 #272G_DBFiles
003C0 00289 #272G_DBFiles
003C1 0028A #272G_DBFiles
003C2 0028B #272G_DBFiles
003C3 0028C #272G_DBFiles
003C4 0028D #272G_DBFiles
003D1 0029A #8G_Redo
003D2 0029B #8G_Redo
003D3 0029C #8G_Redo
003D4 0029D #8G_Redo
003D5 0029E #8G_Redo
003D6 0029F #8G_Redo
003D7 002A0 #8G_Redo
003D8 002A1 #8G_Redo
003C5 0028E #lnxdb-svl-13
003C6 0028F #lnxdb-svl-13
003C7 00290 #lnxdb-svl-13
003C8 00291 #lnxdb-svl-14
003C9 00292 #lnxdb-svl-14
003CA 00293 #lnxdb-svl-14
003CB 00294 #lnxdb-svl-15
003CC 00295 #lnxdb-svl-15
003CD 00296 #lnxdb-svl-15
003CE 00297 #lnxdb-svl-16
003CF 00298 #lnxdb-svl-16
003D0 00299 #lnxdb-svl-16
$sudo symrdf -sid 1346 createpair -file srdf_metro_1346-1695.pair -rdfg 40 -type r1 -rdf_metro -invalidate r2
Execute an RDF 'Create Pair' operation for device file

'srdf_metro_1695-1346_lvm.pair' (y/[n]) ? y
An RDF 'Create Pair' operation execution is in progress for device

file 'srdf_metro_1695-1346_lvm.pair'. Please wait...
Create RDF Pair in (1346,040)....................................Started.

Create RDF Pair in (1346,040)....................................Done.
Mark target device(s) in (1346,040) for full copy from source....Started.
Devices: 03B9-03D0 in (1346,040).................................Marked.
Mark target device(s) in (1346,040) for full copy from source....Done.
Merge track tables between source and target in (1346,040).......Started.

Devices: 03B9-03D0 in (1346,040).................................In Progress.
Devices: 03B9-03D0 in (1346,040).................................Merged.
Merge track tables between source and target in (1346,040).......Done.
Resume RDF link(s) for device(s) in (1346,040)...................Started.
Resume RDF link(s) for device(s) in (1346,040)...................Done.
The RDF 'Create Pair' operation successfully executed for device

file 'srdf_metro_1695-1346_lvm.pair'.
$sudo symrdf -sid 1346 -file srdf_metro_1346-1695.pair -rdfg 40 query
Symmetrix ID : 000196801346 (Microcode Version: 5977)

Remote Symmetrix ID : 000196801695 (Microcode Version: 5977)
RDF (RA) Group Number : 40 (27)
Source (R1) View Target (R2) View MODE

--------------------------------- ------------------------ ---- ------------
ST LI ST
Standard A N A
Logical Sym T R1 Inv R2 Inv K Sym T R1 Inv R2 Inv RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MACE STATE
--------------------------------- -- ------------------------ ---- ------------
N/A 003B9 RW 0 2146305 NR 00282 WD 0 0 T.X. Suspended

N/A 003BA RW 0 2146305 NR 00283 WD 0 0 T.X. Suspended
N/A 003BB RW 0 2146305 NR 00284 WD 0 0 T.X. Suspended
N/A 003BC RW 0 2146305 NR 00285 WD 0 0 T.X. Suspended
N/A 003BD RW 0 2146305 NR 00286 WD 0 0 T.X. Suspended
N/A 003BE RW 0 2146305 NR 00287 WD 0 0 T.X. Suspended
N/A 003BF RW 0 2146305 NR 00288 WD 0 0 T.X. Suspended
N/A 003C0 RW 0 2146305 NR 00289 WD 0 0 T.X. Suspended
N/A 003C1 RW 0 2146305 NR 0028A WD 0 0 T.X. Suspended
N/A 003C2 RW 0 2146305 NR 0028B WD 0 0 T.X. Suspended
N/A 003C3 RW 0 2146305 NR 0028C WD 0 0 T.X. Suspended
N/A 003C4 RW 0 2146305 NR 0028D WD 0 0 T.X. Suspended
N/A 003D1 RW 0 65550 NR 0029A WD 0 0 T.X. Suspended
N/A 003D2 RW 0 65550 NR 0029B WD 0 0 T.X. Suspended
N/A 003D3 RW 0 65550 NR 0029C WD 0 0 T.X. Suspended
N/A 003D4 RW 0 65550 NR 0029D WD 0 0 T.X. Suspended
N/A 003D5 RW 0 65550 NR 0029E WD 0 0 T.X. Suspended
N/A 003D6 RW 0 65550 NR 0029F WD 0 0 T.X. Suspended
N/A 003D7 RW 0 65550 NR 002A0 WD 0 0 T.X. Suspended
N/A 003D8 RW 0 65550 NR 002A1 WD 0 0 T.X. Suspended
N/A 003C5 RW 0 2146305 NR 0028E WD 0 0 T.X. Suspended
N/A 003C6 RW 0 2146305 NR 0028F WD 0 0 T.X. Suspended
N/A 003CA RW 0 2146305 NR 00293 WD 0 0 T.X. Suspended
N/A 003CB RW 0 2146305 NR 00294 WD 0 0 T.X. Suspended
N/A 003CC RW 0 2146305 NR 00295 WD 0 0 T.X. Suspended
N/A 003CD RW 0 2146305 NR 00296 WD 0 0 T.X. Suspended
N/A 003CE RW 0 2146305 NR 00297 WD 0 0 T.X. Suspended
N/A 003CF RW 0 2146305 NR 00298 WD 0 0 T.X. Suspended
N/A 003D0 RW 0 2146305 NR 00299 WD 0 0 T.X. Suspended
Total ------- ------- ------- -------

Track(s) 0 52035720 0 0
MB(s) 0 6504463 0 0
Legend for MODE:
M(ode of Operation) : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

: M = Mixed, T = Active
A(daptive Copy) : D = Disk Mode, W = WP Mode, . = ACp off
C(onsistency State) : X = Enabled, . = Disabled, M = Mixed, - = N/A
(Consistency) E(xempt): X = Enabled, . = Disabled, M = Mixed, - = N/A
$sudo symrdf -sid 1346 -file srdf_metro_1346-1695.pair -rdfg 40 -type r1 establish -use_bias
Execute an RDF 'Incremental Establish' operation for device file

'srdf_metro_1346-1695.pair' (y/[n]) ? y
An RDF 'Incremental Establish' operation execution is in progress for device

file 'srdf_metro_1346-1695.pair'. Please wait...
Suspend RDF link(s) for device(s) in (1346,040)..................Done.

Resume RDF link(s) for device(s) in (1346,040)...................Started.
Resume RDF link(s) for device(s) in (1346,040)...................Done.
The RDF 'Incremental Establish' operation successfully initiated for device

file 'srdf_metro_1346-1695.pair'.
$sudo symrdf -sid 1346 -file srdf_metro_1346-1695.pair -rdfg 40 query


--------------------------------- ------------------------ ---- ------------
ST LI ST
Standard A N A
--------------------------------- -- ------------------------ ---- ------------
N/A 003B9 RW 0 2143259 RW 00282 WD 0 0 T.X. SyncInProg

N/A 003BA RW 0 2143413 RW 00283 WD 0 0 T.X. SyncInProg
N/A 003BB RW 0 2146305 RW 00284 WD 0 0 T.X. SyncInProg
N/A 003BC RW 0 2146305 RW 00285 WD 0 0 T.X. SyncInProg
N/A 003BD RW 0 2142900 RW 00286 WD 0 0 T.X. SyncInProg
N/A 003BE RW 0 2142789 RW 00287 WD 0 0 T.X. SyncInProg
N/A 003BF RW 0 2146305 RW 00288 WD 0 0 T.X. SyncInProg
N/A 003C0 RW 0 2146305 RW 00289 WD 0 0 T.X. SyncInProg
N/A 003C1 RW 0 2145001 RW 0028A WD 0 0 T.X. SyncInProg
N/A 003C2 RW 0 2145466 RW 0028B WD 0 0 T.X. SyncInProg
N/A 003C3 RW 0 2146305 RW 0028C WD 0 0 T.X. SyncInProg
N/A 003C4 RW 0 2146305 RW 0028D WD 0 0 T.X. SyncInProg
N/A 003D1 RW 0 64622 RW 0029A WD 0 0 T.X. SyncInProg
N/A 003D2 RW 0 64721 RW 0029B WD 0 0 T.X. SyncInProg
N/A 003D3 RW 0 65550 RW 0029C WD 0 0 T.X. SyncInProg
N/A 003D4 RW 0 65550 RW 0029D WD 0 0 T.X. SyncInProg
N/A 003D5 RW 0 64860 RW 0029E WD 0 0 T.X. SyncInProg
N/A 003D6 RW 0 64937 RW 0029F WD 0 0 T.X. SyncInProg
N/A 003D7 RW 0 65550 RW 002A0 WD 0 0 T.X. SyncInProg
N/A 003D8 RW 0 65550 RW 002A1 WD 0 0 T.X. SyncInProg
N/A 003C5 RW 0 2144727 RW 0028E WD 0 0 T.X. SyncInProg
N/A 003C6 RW 0 2145507 RW 0028F WD 0 0 T.X. SyncInProg
N/A 003CA RW 0 2144918 RW 00293 WD 0 0 T.X. SyncInProg
N/A 003CB RW 0 2146305 RW 00294 WD 0 0 T.X. SyncInProg
N/A 003CC RW 0 2146305 RW 00295 WD 0 0 T.X. SyncInProg
N/A 003CD RW 0 2144325 RW 00296 WD 0 0 T.X. SyncInProg
N/A 003CE RW 0 2145108 RW 00297 WD 0 0 T.X. SyncInProg
N/A 003CF RW 0 2146305 RW 00298 WD 0 0 T.X. SyncInProg
N/A 003D0 RW 0 2146305 RW 00299 WD 0 0 T.X. SyncInProg
Total ------- ------- ------- -------

Track(s) 0 52009501 0 0
MB(s) 0 6501187 0 0
Legend for MODE:

Verify Devices in “ActiveBias” Mode

SRDF createpair will start synchronization from source devices (R1) to target devices (R2). During this
time, devices pair state will be in “SyncInProg”. Target devices (R2) will still be in write disable (WD)
state and external device WWN spoofing is not applied. Only after source and target devices are fully
synchronized and in “ActiveBias” state, target devices (R2) are read write enabled and external device
WWN spoofing is applied. During this WWN spoofing, target device (R2) external device WWN will be
exactly like external device WWN of source device (R1).

Following section provides CLI output for verification of SRDF devices’ ActiveBias state.

$sudo symrdf -sid 1346 -rdfg 40 -file srdf_metro_1346-1695.pair query


--------------------------------- ------------------------ ---- ------------
ST LI ST
Standard A N A
--------------------------------- -- ------------------------ ---- ------------
N/A 003B9 RW 0 0 RW 00282 RW 0 0 T.X. ActiveBias

N/A 003BA RW 0 0 RW 00283 RW 0 0 T.X. ActiveBias
N/A 003BB RW 0 0 RW 00284 RW 0 0 T.X. ActiveBias
N/A 003BC RW 0 0 RW 00285 RW 0 0 T.X. ActiveBias
N/A 003BD RW 0 0 RW 00286 RW 0 0 T.X. ActiveBias
N/A 003BE RW 0 0 RW 00287 RW 0 0 T.X. ActiveBias
N/A 003BF RW 0 0 RW 00288 RW 0 0 T.X. ActiveBias
N/A 003C0 RW 0 0 RW 00289 RW 0 0 T.X. ActiveBias
N/A 003C1 RW 0 0 RW 0028A RW 0 0 T.X. ActiveBias
N/A 003C2 RW 0 0 RW 0028B RW 0 0 T.X. ActiveBias
N/A 003C3 RW 0 0 RW 0028C RW 0 0 T.X. ActiveBias
N/A 003C4 RW 0 0 RW 0028D RW 0 0 T.X. ActiveBias
N/A 003D1 RW 0 0 RW 0029A RW 0 0 T.X. ActiveBias
N/A 003D2 RW 0 0 RW 0029B RW 0 0 T.X. ActiveBias
N/A 003D3 RW 0 0 RW 0029C RW 0 0 T.X. ActiveBias
N/A 003D4 RW 0 0 RW 0029D RW 0 0 T.X. ActiveBias
N/A 003D5 RW 0 0 RW 0029E RW 0 0 T.X. ActiveBias
N/A 003D6 RW 0 0 RW 0029F RW 0 0 T.X. ActiveBias
N/A 003D7 RW 0 0 RW 002A0 RW 0 0 T.X. ActiveBias
N/A 003C5 RW 0 0 RW 0028E RW 0 0 T.X. ActiveBias
N/A 003C6 RW 0 0 RW 0028F RW 0 0 T.X. ActiveBias
N/A 003CA RW 0 0 RW 00293 RW 0 0 T.X. ActiveBias
N/A 003CB RW 0 0 RW 00294 RW 0 0 T.X. ActiveBias
N/A 003CC RW 0 0 RW 00295 RW 0 0 T.X. ActiveBias
N/A 003CD RW 0 0 RW 00296 RW 0 0 T.X. ActiveBias
N/A 003CE RW 0 0 RW 00297 RW 0 0 T.X. ActiveBias
N/A 003CF RW 0 0 RW 00298 RW 0 0 T.X. ActiveBias
N/A 003D0 RW 0 0 RW 00299 RW 0 0 T.X. ActiveBias
Total ------- ------- ------- -------

Track(s) 0 0 0 0
MB(s) 0.0 0.0 0.0 0.0
Legend for MODE:


$sudo symrdf -sid 1346 -rdfg 40 -file srdf_metro_1346-1695.pair verify -activebias
All device(s) in the list are in 'ActiveBias' state.
Zone and Mask Devices from Target Frame

Once SRDF devices are in “ActiveBias” mode, it is safe to present target devices to the hosts. We will
perform zoning and masking of target devices to the hosts.

Following table provides zoning configuration between all four hosts and target frame.

Server Name HBA WWPN Frame FA Port Frame FA Port
vHBA1 200b1200000000be 1D:28 1D:24
vHBA2 200b1200000000ee 2D:29 2D:24
lnxdb-svl-13
vHBA3 200b12000000008c 3D:28 2D:24
vHBA4 200b12000000009c 4D:29 2D:25
vHBA1 200b12000000003d 1D:28 1D:24
vHBA2 200b12000000002d 2D:29 2D:24
lnxdb-svl-14
vHBA3 200b1200000000eb 3D:28 2D:24
vHBA4 200b1200000000bb 4D:29 2D:25
HK196801346 HK196801695
vHBA1 200b12000000007c 1D:28 1D:24
vHBA2 200b12000000006c 2D:29 2D:24
lnxdb-svl-15
vHBA3 200b1200000000cb 3D:28 2D:24
vHBA4 200b1200000000ab 4D:29 2D:25
vHBA1 200b12000000001d 1D:28 1D:24
vHBA2 200b12000000000d 2D:29 2D:24
lnxdb-svl-16
vHBA3 200b12000000008b 3D:28 2D:24
vHBA4 200b12000000009b 4D:29 2D:25

Following table provides masking configuration from VMAX3 HK196801695to all four hosts.

Type Of Purpose Of Initiator Group Port Group
Masking View Initiator Group Port Group Storage Group Storage Group Member SYMDEV IDs
Storage Storage Member Member
IG_lnxdb-svl-13, 1D:24,
DB File,
Shared With MV_lnxdb-svl- IG_lnxdb-svl-13- IG_lnxdb-svl-14, PG_lnxdb- 2D:24, SG_lnxdb-svl- SG_DBBS2DM1_DB_PAR_ARCH, 00282:0028D,
ARCH, Redo,
In Four Nodes 13-16_Shared 16 IG_lnxdb-svl-15, svl-13-16 1D:25, 13-16_Shared SG_DBBS2DM1_REDO 0029A:002A1
etc…
IG_lnxdb-svl-16 2D:25
Oracle Binary 1D:24,

Dedicated to File Systems MV_lnxdb-svl- vHBAs of lnxdb-svl- PG_lnxdb- 2D:24, SG_lnxdb-svl- SG_LNXDB-SVL-13_OraBin 00131:00133,
IG_lnxdb-svl-13
lnxdb-svl-13 & 13_Local 13 svl-13-16 1D:25, 13_Local SG_LNXDB-SVL-13_GK 0028E:00290
Gatekeepers 2D:25

IG_lnxdb-svl-14
lnxdb-svl-14 & 14_Local 14 svl-13-16 1D:25, 14_Local SG_LNXDB-SVL-14_GK 00291:00293
Gatekeepers 2D:25

IG_lnxdb-svl-15
Gatekeepers 2D:25

Dedicated to File Systems MV_lnxdb-svl- vHBAs of lnxdb-svl- PG_lnxdb- 2D:24, SG_lnxdb-svl- SG_LNXDB-SVL-16_OraBin 0013A:0013C,
IG_lnxdb-svl-16
Gatekeepers 2D:25

Following section provides CLI output for masking operation from VMAX3 HK196801695.

# Following commands will create storage groups, port groups and initiator groups.
$sudo symaccess -sid 1695 create -name IG_lnxdb-svl-13 -type init -wwn 200b1200000000be
$sudo symaccess -sid 1695 create -name IG_lnxdb-svl-14 -type init -wwn 200b12000000003d
$sudo symaccess -sid 1695 create -name IG_lnxdb-svl-15 -type init -wwn 200b12000000007c
$sudo symaccess -sid 1695 create -name IG_lnxdb-svl-16 -type init -wwn 200b12000000001d
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-13 -type init add -wwn 200b1200000000ee
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-13 -type init add -wwn 200b12000000008c
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-14 -type init add -wwn 200b12000000002d
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-14 -type init add -wwn 200b1200000000eb
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-14 -type init add -wwn 200b1200000000bb
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-15 -type init add -wwn 200b1200000000cb
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-15 -type init add -wwn 200b1200000000ab
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-16 -type init add -wwn 200b12000000000d
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-16 -type init add -wwn 200b12000000008b
$sudo symaccess -sid 1695 -name IG_lnxdb-svl-16 -type init add -wwn 200b12000000009b
$sudo symaccess -sid 1695 create -name IG_lnxdb-svl-13-16 -type init -sg IG_lnxdb-svl-13,IG_lnxdb-svl-14,IG_lnxdb-
svl-15,IG_lnxdb-svl-16
$sudo symaccess -sid 1695 create -name PG_lnxdb-svl-13-16 -type port -dirport 1d:24,2d:24,1d:25,2d:25
$sudo symsg -sid 1695 create SG_DBBS2DM1_DB_PAR_ARCH_New
$sudo symsg -sid 1695 create SG_DBBS2DM1_REDO_New
$sudo symsg -sid 1695 -sg SG_DBBS2DM1_DB_PAR_ARCH_New addall -devs 00282:0028D
$sudo symsg -sid 1695 -sg SG_DBBS2DM1_REDO_New addall -devs 0029A:002A1
$sudo symsg -sid 1695 -sg SG_lnxdb-svl-13-16_Shared add sg SG_DBBS2DM1_DB_PAR_ARCH_New,SG_DBBS2DM1_REDO_New
$sudo symsg -sid 1695 -sg SG_lnxdb-svl-13-16_Shared remove sg SG_DBBS2DM1_DB_PAR_ARCH_First-Migration-
TST,SG_DBBS2DM1_REDO_First-Migration-TST
$sudo symsg -sid 1695 -sg SG_LNXDB-SVL-13_OraBin addall -devs 0028E:00290
$sudo symsg -sid 1695 -sg SG_LNXDB-SVL-14_OraBin addall -devs 00291:00293
$sudo symsg -sid 1695 create SG_LNXDB-SVL-13_GK
$sudo symsg -sid 1695 -sg SG_LNXDB-SVL-13_GK addall -devs 0131:0133
$sudo symsg -sid 1695 -sg SG_LNXDB-SVL-16_GK addall -devs 013A:013C
$sudo symsg -sid 1695 create SG_lnxdb-svl-13_Local
$sudo symsg -sid 1695 -sg SG_lnxdb-svl-13_Local add sg SG_LNXDB-SVL-13_OraBin,SG_LNXDB-SVL-13_GK
# Run Following CMDS after Devices are in ActiveBias Mode.

# Following Masking CMDS will create Local Views
$sudo symaccess -sid 1695 create view -name MV_lnxdb-svl-13_Local -ig IG_lnxdb-svl-13 -pg PG_lnxdb-svl-13-16 -sg
SG_lnxdb-svl-13_Local
$sudo
# Following Masking CMDS will create Shared View
$sudo symaccess -sid 1695 create view -name MV_lnxdb-svl-13-16_Shared -ig IG_lnxdb-svl-13-16 -pg PG_lnxdb-svl-13-16 -
sg SG_lnxdb-svl-13-16_Shared

Once zoning and masking operations are performed, we need to scan all four hosts to discover new
devices. We will also verify that now all four hosts will see 8 paths for storage migration participating
devices.
Following section provide scanning and multipath device verification output from one of the four hosts
(lnxdb-svl-13).

# Following is multipath output before HBA scanning.
$ multipath -ll
mpathbc (360000970000196801346533030334432) dm-23 EMC,SYMMETRIX
size=8.0G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:1:49 sdt 65:48 active ready running
|- 2:0:2:49 sdau 66:224 active ready running
|- 3:0:1:49 sdbt 68:112 active ready running
`- 4:0:2:49 sdcs 70:0 active ready running
mpathaw (360000970000196801346533030334245) dm-17 EMC,SYMMETRIX
size=262G features='1 queue_if_no_path' hwhandler='0' wp=rw
|- 1:0:1:41 sdl 8:176 active ready running
|- 2:0:2:41 sdam 66:96 active ready running
|- 3:0:1:41 sdbl 67:240 active ready running
`- 4:0:2:41 sdck 69:128 active ready running
mpathbb (360000970000196801346533030334434) dm-15 EMC,SYMMETRIX
|- 1:0:1:51 sdv 65:80 active ready running
|- 2:0:2:51 sdaw 67:0 active ready running
|- 3:0:1:51 sdbv 68:144 active ready running
`- 4:0:2:51 sdcu 70:32 active ready running
mpathav (360000970000196801346533030334331) dm-19 EMC,SYMMETRIX
|- 1:0:1:44 sdo 8:224 active ready running
|- 2:0:2:44 sdap 66:144 active ready running
|- 4:0:2:44 sdcn 69:176 active ready running
`- 3:0:1:44 sdbo 68:32 active ready running
mpathbn (360000970000196801346533030334335) dm-0 EMC,SYMMETRIX
|- 1:0:1:1 sdb 8:16 active ready running
|- 2:0:2:1 sdac 65:192 active ready running
|- 3:0:1:1 sdaz 67:48 active ready running
`- 4:0:2:1 sdby 68:192 active ready running
mpathba (360000970000196801346533030334246) dm-38 EMC,SYMMETRIX
|- 1:0:1:42 sdm 8:192 active ready running
|- 2:0:2:42 sdan 66:112 active ready running
|- 3:0:1:42 sdbm 68:0 active ready running
`- 4:0:2:42 sdcl 69:144 active ready running
mpathau (360000970000196801346533030334244) dm-9 EMC,SYMMETRIX
|- 1:0:1:40 sdk 8:160 active ready running
|- 2:0:2:40 sdal 66:80 active ready running
|- 3:0:1:40 sdbk 67:224 active ready running

`- 4:0:2:40 sdch 69:80 active ready running
mpathbm (360000970000196801346533030334336) dm-13 EMC,SYMMETRIX
|- 1:0:1:2 sdc 8:32 active ready running
|- 2:0:2:2 sdad 65:208 active ready running
|- 3:0:1:2 sdbc 67:96 active ready running
`- 4:0:2:2 sdbz 68:208 active ready running
mpathat (360000970000196801346533030334243) dm-14 EMC,SYMMETRIX
|- 1:0:1:39 sdj 8:144 active ready running
|- 2:0:2:39 sdak 66:64 active ready running
|- 3:0:1:39 sdbj 67:208 active ready running
`- 4:0:2:39 sdcg 69:64 active ready running
mpathbl (360000970000196801346533030334337) dm-11 EMC,SYMMETRIX
|- 1:0:1:3 sdd 8:48 active ready running
|- 2:0:2:3 sdae 65:224 active ready running
|- 3:0:1:3 sdbd 67:112 active ready running
`- 4:0:2:3 sdca 68:224 active ready running
mpathas (360000970000196801346533030334241) dm-1 EMC,SYMMETRIX
|- 1:0:1:37 sdh 8:112 active ready running
|- 2:0:2:37 sdai 66:32 active ready running
|- 3:0:1:37 sdbh 67:176 active ready running
`- 4:0:2:37 sdce 69:32 active ready running
mpathbk (360000970000196801346533030334436) dm-28 EMC,SYMMETRIX
|- 1:0:1:53 sdx 65:112 active ready running
|- 2:0:2:53 sday 67:32 active ready running
|- 3:0:1:53 sdbx 68:176 active ready running
`- 4:0:2:53 sdcw 70:64 active ready running
mpathar (360000970000196801346533030334242) dm-34 EMC,SYMMETRIX
|- 1:0:1:38 sdi 8:128 active ready running
|- 2:0:2:38 sdaj 66:48 active ready running
|- 3:0:1:38 sdbi 67:192 active ready running
`- 4:0:2:38 sdcf 69:48 active ready running
mpathbj (360000970000196801346533030334433) dm-4 EMC,SYMMETRIX
|- 1:0:1:50 sdu 65:64 active ready running
|- 2:0:2:50 sdav 66:240 active ready running
|- 3:0:1:50 sdbu 68:128 active ready running
`- 4:0:2:50 sdct 70:16 active ready running
mpathbi (360000970000196801346533030334431) dm-21 EMC,SYMMETRIX
|- 1:0:1:48 sds 65:32 active ready running
|- 2:0:2:48 sdat 66:208 active ready running
|- 3:0:1:48 sdbs 68:96 active ready running
`- 4:0:2:48 sdcr 69:240 active ready running
mpathbh (360000970000196801346533030334333) dm-30 EMC,SYMMETRIX
|- 1:0:1:46 sdq 65:0 active ready running
|- 2:0:2:46 sdar 66:176 active ready running
|- 3:0:1:46 sdbq 68:64 active ready running
`- 4:0:2:46 sdcp 69:208 active ready running
mpathbg (360000970000196801346533030334437) dm-32 EMC,SYMMETRIX
|- 1:0:1:54 sdy 65:128 active ready running
|- 2:0:2:54 sdba 67:64 active ready running
|- 3:0:1:54 sdci 69:96 active ready running
`- 4:0:2:54 sdcx 70:80 active ready running
mpathbf (360000970000196801346533030334438) dm-36 EMC,SYMMETRIX

|- 1:0:1:55 sdz 65:144 active ready running
|- 2:0:2:55 sdbb 67:80 active ready running
|- 3:0:1:55 sdcj 69:112 active ready running
`- 4:0:2:55 sdcy 70:96 active ready running
mpathaz (360000970000196801346533030334239) dm-7 EMC,SYMMETRIX
|- 1:0:1:36 sdg 8:96 active ready running
|- 2:0:2:36 sdah 66:16 active ready running
|- 3:0:1:36 sdbg 67:160 active ready running
`- 4:0:2:36 sdcd 69:16 active ready running
mpathbe (360000970000196801346533030334332) dm-42 EMC,SYMMETRIX
|- 1:0:1:45 sdp 8:240 active ready running
|- 2:0:2:45 sdaq 66:160 active ready running
|- 3:0:1:45 sdbp 68:48 active ready running
`- 4:0:2:45 sdco 69:192 active ready running
mpathay (360000970000196801346533030334330) dm-5 EMC,SYMMETRIX
|- 1:0:1:43 sdn 8:208 active ready running
|- 2:0:2:43 sdao 66:128 active ready running
|- 3:0:1:43 sdbn 68:16 active ready running
`- 4:0:2:43 sdcm 69:160 active ready running
mpathbd (360000970000196801346533030334334) dm-27 EMC,SYMMETRIX
|- 1:0:1:47 sdr 65:16 active ready running
|- 2:0:2:47 sdas 66:192 active ready running
|- 3:0:1:47 sdbr 68:80 active ready running
`- 4:0:2:47 sdcq 69:224 active ready running
mpathax (360000970000196801346533030334435) dm-40 EMC,SYMMETRIX
|- 1:0:1:52 sdw 65:96 active ready running
|- 2:0:2:52 sdax 67:16 active ready running
|- 3:0:1:52 sdbw 68:160 active ready running
`- 4:0:2:52 sdcv 70:48 active ready running
# Following will perform HBA scan, discover new sd and mulitpath devices.
for hba in `echo host1 host2 host3 host4`
do
echo "- - -" > /sys/class/scsi_host/$hba/scan
sleep 2
done
# Following is multipath output after HBA scanning.

$ multipath -ll
|- 1:0:0:19 sdds 71:160 active ready running
|- 2:0:1:19 sdes 129:64 active ready running
|- 3:0:0:19 sdfs 130:224 active ready running
|- 4:0:1:19 sdgs 132:128 active ready running
|- 1:0:1:49 sdt 65:48 active ready running
|- 2:0:2:49 sdau 66:224 active ready running
|- 3:0:1:49 sdbt 68:112 active ready running
`- 4:0:2:49 sdcs 70:0 active ready running
|- 1:0:0:11 sddk 71:32 active ready running
|- 2:0:1:11 sdek 128:192 active ready running
|- 3:0:0:11 sdfk 130:96 active ready running
|- 4:0:1:11 sdgk 132:0 active ready running
|- 1:0:1:41 sdl 8:176 active ready running
|- 2:0:2:41 sdam 66:96 active ready running
|- 3:0:1:41 sdbl 67:240 active ready running
`- 4:0:2:41 sdck 69:128 active ready running

|- 1:0:0:21 sddu 71:192 active ready running
|- 2:0:1:21 sdeu 129:96 active ready running
|- 3:0:0:21 sdfu 131:0 active ready running
|- 4:0:1:21 sdgu 132:160 active ready running
|- 1:0:1:51 sdv 65:80 active ready running
|- 2:0:2:51 sdaw 67:0 active ready running
|- 3:0:1:51 sdbv 68:144 active ready running
`- 4:0:2:51 sdcu 70:32 active ready running
|- 1:0:0:14 sddn 71:80 active ready running
|- 2:0:1:14 sden 128:240 active ready running
|- 4:0:1:14 sdgn 132:48 active ready running
|- 3:0:0:14 sdfn 130:144 active ready running
|- 1:0:1:44 sdo 8:224 active ready running
|- 2:0:2:44 sdap 66:144 active ready running
|- 4:0:2:44 sdcn 69:176 active ready running
`- 3:0:1:44 sdbo 68:32 active ready running
|- 1:0:0:3 sddc 70:160 active ready running
|- 2:0:1:3 sdec 128:64 active ready running
|- 3:0:0:3 sdfc 129:224 active ready running
|- 4:0:1:3 sdgc 131:128 active ready running
|- 1:0:1:1 sdb 8:16 active ready running
|- 2:0:2:1 sdac 65:192 active ready running
|- 3:0:1:1 sdbb 67:80 active ready running
`- 4:0:2:1 sdca 68:224 active ready running
|- 1:0:0:12 sddl 71:48 active ready running
|- 2:0:1:12 sdel 128:208 active ready running
|- 3:0:0:12 sdfl 130:112 active ready running
|- 4:0:1:12 sdgl 132:16 active ready running
|- 1:0:1:42 sdm 8:192 active ready running
|- 2:0:2:42 sdan 66:112 active ready running
|- 3:0:1:42 sdbm 68:0 active ready running
`- 4:0:2:42 sdcl 69:144 active ready running
|- 1:0:0:10 sddj 71:16 active ready running
|- 2:0:1:10 sdej 128:176 active ready running
|- 3:0:0:10 sdfj 130:80 active ready running
|- 4:0:1:10 sdgj 131:240 active ready running
|- 1:0:1:40 sdk 8:160 active ready running
|- 2:0:2:40 sdal 66:80 active ready running
|- 3:0:1:40 sdbk 67:224 active ready running
`- 4:0:2:40 sdcj 69:112 active ready running
|- 1:0:0:4 sddd 70:176 active ready running
|- 2:0:1:4 sded 128:80 active ready running
|- 3:0:0:4 sdfd 129:240 active ready running
|- 4:0:1:4 sdgd 131:144 active ready running
|- 1:0:1:2 sdc 8:32 active ready running
|- 2:0:2:2 sdad 65:208 active ready running
|- 3:0:1:2 sdbc 67:96 active ready running
`- 4:0:2:2 sdcd 69:16 active ready running
|- 1:0:0:9 sddi 71:0 active ready running
|- 2:0:1:9 sdei 128:160 active ready running
|- 3:0:0:9 sdfi 130:64 active ready running
|- 4:0:1:9 sdgi 131:224 active ready running

|- 1:0:1:39 sdj 8:144 active ready running
|- 2:0:2:39 sdak 66:64 active ready running
|- 3:0:1:39 sdbj 67:208 active ready running
`- 4:0:2:39 sdci 69:96 active ready running
|- 1:0:0:5 sdde 70:192 active ready running
|- 2:0:1:5 sdee 128:96 active ready running
|- 3:0:0:5 sdfe 130:0 active ready running
|- 4:0:1:5 sdge 131:160 active ready running
|- 1:0:1:3 sdd 8:48 active ready running
|- 2:0:2:3 sdae 65:224 active ready running
|- 3:0:1:3 sdbd 67:112 active ready running
`- 4:0:2:3 sdce 69:32 active ready running
|- 1:0:0:7 sddg 70:224 active ready running
|- 2:0:1:7 sdeg 128:128 active ready running
|- 3:0:0:7 sdfg 130:32 active ready running
|- 4:0:1:7 sdgg 131:192 active ready running
|- 1:0:1:37 sdh 8:112 active ready running
|- 2:0:2:37 sdai 66:32 active ready running
|- 3:0:1:37 sdbh 67:176 active ready running
`- 4:0:2:37 sdcg 69:64 active ready running
|- 1:0:0:23 sddw 71:224 active ready running
|- 2:0:1:23 sdew 129:128 active ready running
|- 3:0:0:23 sdfw 131:32 active ready running
|- 4:0:1:23 sdgw 132:192 active ready running
|- 1:0:1:53 sdx 65:112 active ready running
|- 2:0:2:53 sday 67:32 active ready running
|- 3:0:1:53 sdbx 68:176 active ready running
`- 4:0:2:53 sdcw 70:64 active ready running
|- 1:0:0:8 sddh 70:240 active ready running
|- 2:0:1:8 sdeh 128:144 active ready running
|- 3:0:0:8 sdfh 130:48 active ready running
|- 4:0:1:8 sdgh 131:208 active ready running
|- 1:0:1:38 sdi 8:128 active ready running
|- 2:0:2:38 sdaj 66:48 active ready running
|- 3:0:1:38 sdbi 67:192 active ready running
`- 4:0:2:38 sdch 69:80 active ready running
|- 1:0:0:20 sddt 71:176 active ready running
|- 2:0:1:20 sdet 129:80 active ready running
|- 3:0:0:20 sdft 130:240 active ready running
|- 4:0:1:20 sdgt 132:144 active ready running
|- 1:0:1:50 sdu 65:64 active ready running
|- 2:0:2:50 sdav 66:240 active ready running
|- 3:0:1:50 sdbu 68:128 active ready running
`- 4:0:2:50 sdct 70:16 active ready running
|- 1:0:0:18 sddr 71:144 active ready running
|- 2:0:1:18 sder 129:48 active ready running
|- 3:0:0:18 sdfr 130:208 active ready running
|- 4:0:1:18 sdgr 132:112 active ready running
|- 1:0:1:48 sds 65:32 active ready running
|- 2:0:2:48 sdat 66:208 active ready running
|- 3:0:1:48 sdbs 68:96 active ready running
`- 4:0:2:48 sdcr 69:240 active ready running

|- 1:0:0:16 sddp 71:112 active ready running
|- 2:0:1:16 sdep 129:16 active ready running
|- 3:0:0:16 sdfp 130:176 active ready running
|- 4:0:1:16 sdgp 132:80 active ready running
|- 1:0:1:46 sdq 65:0 active ready running
|- 2:0:2:46 sdar 66:176 active ready running
|- 3:0:1:46 sdbq 68:64 active ready running
`- 4:0:2:46 sdcp 69:208 active ready running
|- 1:0:0:24 sddx 71:240 active ready running
|- 2:0:1:24 sdex 129:144 active ready running
|- 3:0:0:24 sdfx 131:48 active ready running
|- 4:0:1:24 sdgx 132:208 active ready running
|- 1:0:1:54 sdy 65:128 active ready running
|- 2:0:2:54 sdaz 67:48 active ready running
|- 3:0:1:54 sdby 68:192 active ready running
`- 4:0:2:54 sdcx 70:80 active ready running
|- 1:0:0:25 sddy 128:0 active ready running
|- 2:0:1:25 sdey 129:160 active ready running
|- 3:0:0:25 sdfy 131:64 active ready running
|- 4:0:1:25 sdgy 132:224 active ready running
|- 1:0:1:55 sdz 65:144 active ready running
|- 2:0:2:55 sdba 67:64 active ready running
|- 3:0:1:55 sdbz 68:208 active ready running
`- 4:0:2:55 sdcy 70:96 active ready running
|- 1:0:0:6 sddf 70:208 active ready running
|- 2:0:1:6 sdef 128:112 active ready running
|- 3:0:0:6 sdff 130:16 active ready running
|- 4:0:1:6 sdgf 131:176 active ready running
|- 1:0:1:36 sdg 8:96 active ready running
|- 2:0:2:36 sdah 66:16 active ready running
|- 3:0:1:36 sdbg 67:160 active ready running
`- 4:0:2:36 sdcf 69:48 active ready running
|- 1:0:0:15 sddo 71:96 active ready running
|- 2:0:1:15 sdeo 129:0 active ready running
|- 3:0:0:15 sdfo 130:160 active ready running
|- 4:0:1:15 sdgo 132:64 active ready running
|- 1:0:1:45 sdp 8:240 active ready running
|- 2:0:2:45 sdaq 66:160 active ready running
|- 3:0:1:45 sdbp 68:48 active ready running
`- 4:0:2:45 sdco 69:192 active ready running
|- 1:0:0:13 sddm 71:64 active ready running
|- 2:0:1:13 sdem 128:224 active ready running
|- 3:0:0:13 sdfm 130:128 active ready running
|- 4:0:1:13 sdgm 132:32 active ready running
|- 1:0:1:43 sdn 8:208 active ready running
|- 2:0:2:43 sdao 66:128 active ready running
|- 3:0:1:43 sdbn 68:16 active ready running
`- 4:0:2:43 sdcm 69:160 active ready running
|- 1:0:0:17 sddq 71:128 active ready running
|- 2:0:1:17 sdeq 129:32 active ready running
|- 3:0:0:17 sdfq 130:192 active ready running
|- 4:0:1:17 sdgq 132:96 active ready running
|- 1:0:1:47 sdr 65:16 active ready running
|- 2:0:2:47 sdas 66:192 active ready running
|- 3:0:1:47 sdbr 68:80 active ready running

`- 4:0:2:47 sdcq 69:224 active ready running
|- 1:0:0:22 sddv 71:208 active ready running
|- 2:0:1:22 sdev 129:112 active ready running
|- 3:0:0:22 sdfv 131:16 active ready running
|- 4:0:1:22 sdgv 132:176 active ready running
|- 1:0:1:52 sdw 65:96 active ready running
|- 2:0:2:52 sdax 67:16 active ready running
|- 3:0:1:52 sdbw 68:160 active ready running
`- 4:0:2:52 sdcv 70:48 active ready running
Change SRDF/Metro Bias to Target Frame

Once target devices are scanned on all four hosts and multipath also recognized them in existing paths,
we can change the bias to target frame. This will enable target devices to become RW enable in event of
any failures.

In few steps from now, we are going to perform SRDF suspend operation on all participating
SRDF/Metro devices. Thus, this step will ensure that application I/O will flow thru new target devices.

Following section provide CLI output for this operation.



--------------------------------- ------------------------ ---- ------------
ST LI ST
Standard A N A
--------------------------------- -- ------------------------ ---- ------------


Total ------- ------- ------- -------

Track(s) 0 0 0 0
MB(s) 0.0 0.0 0.0 0.0
Legend for MODE:

$sudo symrdf -sid 1346 -rdfg 40 -file srdf_metro_1346-1695.pair set bias R2
Execute an RDF Set 'Bias R2' operation for device

file 'srdf_metro_1346-1695.pair' (y/[n]) ? y
An RDF Set 'Bias R2' operation execution is

in progress for device file 'srdf_metro_1346-1695.pair'. Please wait...
The RDF 'Bias R2' operation successfully executed

for device file 'srdf_metro_1346-1695.pair'.

Target (R2) View Source (R1) View MODE

--------------------------------- ------------------------ ---- ------------
ST LI ST
Standard A N A
--------------------------------- -- ------------------------ ---- ------------


Total ------- ------- ------- -------

Track(s) 0 0 0 0
MB(s) 0.0 0.0 0.0 0.0
Legend for MODE:

Remove Linux Source Frame Devices on the Hosts

As part of check list, we have gathered Linux source device (/dev/sd) lists. We will use this list to first
offline and then delete these scsi devices from host. We may also generate new list with “symcfg
discover; sympd –sid SRCSID list” CLI output.

Note: We recommend to generate new list using CLI output since host can reboot. If persistent LUN
binding is not setup on these Linux hosts, there is a possibility that source devices (/dev/sd) might
change.

Following section provide output of performing offline and remove operation of Linux source SCSI devices
from one of the host (lnxdb-svl-13).

# File "source_sd_frame_1346.txt" has all of original source scsi devices (from frame 1346) /dev/sd list
# Following is the procedure to perform offline operation on these devices.
file="source_sd_frame_1346.txt"
for sd in `cat $file`
do
echo "offline" > /sys/block/$sd/device/state
sleep 2
done
# Following is multipath output after performing scsi devices offline operation.
$ multipath -ll
|- 4:0:1:19 sdgs 132:128 active ready running
|- 1:0:1:49 sdt 65:48 failed faulty running
|- 2:0:2:49 sdau 66:224 failed faulty running
|- 3:0:1:49 sdbt 68:112 failed faulty running
`- 4:0:2:49 sdcs 70:0 failed faulty running
|- 4:0:1:11 sdgk 132:0 active ready running
|- 1:0:1:41 sdl 8:176 failed faulty running
|- 2:0:2:41 sdam 66:96 failed faulty running

|- 3:0:1:41 sdbl 67:240 failed faulty running
`- 4:0:2:41 sdck 69:128 failed faulty running
|- 4:0:1:21 sdgu 132:160 active ready running
|- 1:0:1:51 sdv 65:80 failed faulty running
|- 2:0:2:51 sdaw 67:0 failed faulty running
|- 3:0:1:51 sdbv 68:144 failed faulty running
`- 4:0:2:51 sdcu 70:32 failed faulty running
|- 3:0:0:14 sdfn 130:144 active ready running
|- 1:0:1:44 sdo 8:224 failed faulty running
|- 2:0:2:44 sdap 66:144 failed faulty running
|- 4:0:2:44 sdcn 69:176 failed faulty running
`- 3:0:1:44 sdbo 68:32 failed faulty running
|- 4:0:1:3 sdgc 131:128 active ready running
|- 1:0:1:1 sdb 8:16 failed faulty running
|- 2:0:2:1 sdac 65:192 failed faulty running
|- 3:0:1:1 sdbb 67:80 failed faulty running
`- 4:0:2:1 sdca 68:224 failed faulty running
|- 4:0:1:12 sdgl 132:16 active ready running
|- 1:0:1:42 sdm 8:192 failed faulty running
|- 2:0:2:42 sdan 66:112 failed faulty running
|- 3:0:1:42 sdbm 68:0 failed faulty running
`- 4:0:2:42 sdcl 69:144 failed faulty running
|- 4:0:1:10 sdgj 131:240 active ready running
|- 1:0:1:40 sdk 8:160 failed faulty running
|- 2:0:2:40 sdal 66:80 failed faulty running
|- 3:0:1:40 sdbk 67:224 failed faulty running
`- 4:0:2:40 sdcj 69:112 failed faulty running
|- 4:0:1:4 sdgd 131:144 active ready running
|- 1:0:1:2 sdc 8:32 failed faulty running
|- 2:0:2:2 sdad 65:208 failed faulty running
|- 3:0:1:2 sdbc 67:96 failed faulty running
`- 4:0:2:2 sdcd 69:16 failed faulty running

|- 4:0:1:9 sdgi 131:224 active ready running
|- 1:0:1:39 sdj 8:144 failed faulty running
|- 2:0:2:39 sdak 66:64 failed faulty running
|- 3:0:1:39 sdbj 67:208 failed faulty running
`- 4:0:2:39 sdci 69:96 failed faulty running
|- 4:0:1:5 sdge 131:160 active ready running
|- 1:0:1:3 sdd 8:48 failed faulty running
|- 2:0:2:3 sdae 65:224 failed faulty running
|- 3:0:1:3 sdbd 67:112 failed faulty running
`- 4:0:2:3 sdce 69:32 failed faulty running
|- 4:0:1:7 sdgg 131:192 active ready running
|- 1:0:1:37 sdh 8:112 failed faulty running
|- 2:0:2:37 sdai 66:32 failed faulty running
|- 3:0:1:37 sdbh 67:176 failed faulty running
`- 4:0:2:37 sdcg 69:64 failed faulty running
|- 4:0:1:23 sdgw 132:192 active ready running
|- 1:0:1:53 sdx 65:112 failed faulty running
|- 2:0:2:53 sday 67:32 failed faulty running
|- 3:0:1:53 sdbx 68:176 failed faulty running
`- 4:0:2:53 sdcw 70:64 failed faulty running
|- 4:0:1:8 sdgh 131:208 active ready running
|- 1:0:1:38 sdi 8:128 failed faulty running
|- 2:0:2:38 sdaj 66:48 failed faulty running
|- 3:0:1:38 sdbi 67:192 failed faulty running
`- 4:0:2:38 sdch 69:80 failed faulty running
|- 4:0:1:20 sdgt 132:144 active ready running
|- 1:0:1:50 sdu 65:64 failed faulty running
|- 2:0:2:50 sdav 66:240 failed faulty running
|- 3:0:1:50 sdbu 68:128 failed faulty running
`- 4:0:2:50 sdct 70:16 failed faulty running
|- 4:0:1:18 sdgr 132:112 active ready running
|- 1:0:1:48 sds 65:32 failed faulty running
|- 2:0:2:48 sdat 66:208 failed faulty running
|- 3:0:1:48 sdbs 68:96 failed faulty running
`- 4:0:2:48 sdcr 69:240 failed faulty running

|- 4:0:1:16 sdgp 132:80 active ready running
|- 1:0:1:46 sdq 65:0 failed faulty running
|- 2:0:2:46 sdar 66:176 failed faulty running
|- 3:0:1:46 sdbq 68:64 failed faulty running
`- 4:0:2:46 sdcp 69:208 failed faulty running
|- 4:0:1:24 sdgx 132:208 active ready running
|- 1:0:1:54 sdy 65:128 failed faulty running
|- 2:0:2:54 sdaz 67:48 failed faulty running
|- 3:0:1:54 sdby 68:192 failed faulty running
`- 4:0:2:54 sdcx 70:80 failed faulty running
|- 4:0:1:25 sdgy 132:224 active ready running
|- 1:0:1:55 sdz 65:144 failed faulty running
|- 2:0:2:55 sdba 67:64 failed faulty running
|- 3:0:1:55 sdbz 68:208 failed faulty running
`- 4:0:2:55 sdcy 70:96 failed faulty running
|- 4:0:1:6 sdgf 131:176 active ready running
|- 1:0:1:36 sdg 8:96 failed faulty running
|- 2:0:2:36 sdah 66:16 failed faulty running
|- 3:0:1:36 sdbg 67:160 failed faulty running
`- 4:0:2:36 sdcf 69:48 failed faulty running
|- 4:0:1:15 sdgo 132:64 active ready running
|- 1:0:1:45 sdp 8:240 failed faulty running
|- 2:0:2:45 sdaq 66:160 failed faulty running
|- 3:0:1:45 sdbp 68:48 failed faulty running
`- 4:0:2:45 sdco 69:192 failed faulty running
|- 4:0:1:13 sdgm 132:32 active ready running
|- 1:0:1:43 sdn 8:208 failed faulty running
|- 2:0:2:43 sdao 66:128 failed faulty running
|- 3:0:1:43 sdbn 68:16 failed faulty running
`- 4:0:2:43 sdcm 69:160 failed faulty running
|- 4:0:1:17 sdgq 132:96 active ready running
|- 1:0:1:47 sdr 65:16 failed faulty running

|- 2:0:2:47 sdas 66:192 failed faulty running
|- 3:0:1:47 sdbr 68:80 failed faulty running
`- 4:0:2:47 sdcq 69:224 failed faulty running
|- 4:0:1:22 sdgv 132:176 active ready running
|- 1:0:1:52 sdw 65:96 failed faulty running
|- 2:0:2:52 sdax 67:16 failed faulty running
|- 3:0:1:52 sdbw 68:160 failed faulty running
`- 4:0:2:52 sdcv 70:48 failed faulty running
# Following is the procedure to perform delete operation on these devices.
for sd in `cat $file`

do
echo $sd
echo 1 > /sys/block/$sd/device/delete
sleep 2
done
# Following is multipath output after performing scsi devices delete operation.
$ multipath -ll
`- 4:0:1:19 sdgs 132:128 active ready running
`- 4:0:1:11 sdgk 132:0 active ready running
`- 4:0:1:21 sdgu 132:160 active ready running
`- 3:0:0:14 sdfn 130:144 active ready running
`- 4:0:1:3 sdgc 131:128 active ready running
`- 4:0:1:12 sdgl 132:16 active ready running

`- 4:0:1:10 sdgj 131:240 active ready running
`- 4:0:1:4 sdgd 131:144 active ready running
`- 4:0:1:9 sdgi 131:224 active ready running
`- 4:0:1:5 sdge 131:160 active ready running
`- 4:0:1:7 sdgg 131:192 active ready running
`- 4:0:1:23 sdgw 132:192 active ready running
`- 4:0:1:8 sdgh 131:208 active ready running
`- 4:0:1:20 sdgt 132:144 active ready running
`- 4:0:1:18 sdgr 132:112 active ready running
`- 4:0:1:16 sdgp 132:80 active ready running
`- 4:0:1:24 sdgx 132:208 active ready running

`- 4:0:1:25 sdgy 132:224 active ready running
`- 4:0:1:6 sdgf 131:176 active ready running
`- 4:0:1:15 sdgo 132:64 active ready running
`- 4:0:1:13 sdgm 132:32 active ready running
`- 4:0:1:17 sdgq 132:96 active ready running
`- 4:0:1:22 sdgv 132:176 active ready running
Perform Suspend Operation On SRDF/Metro Group

Once source devices are removed from all four hosts, we can suspend SRDF/Metro devices. This is will
source devices in write disable (WD) mode.

Following section provides output to perform SRDF suspend operation.

$sudo symrdf -sid 1346 -rdfg 40 -file srdf_metro_1346-1695.pair suspend -force
Execute an RDF 'Suspend' operation for device file

An RDF 'Suspend' operation execution is in progress for device

Suspend RDF link(s) for device(s) in (1346,040)..................Done.
The RDF 'Suspend' operation successfully executed for device


Target (R2) View Source (R1) View MODE

--------------------------------- ------------------------ ---- ------------
ST LI ST
Standard A N A
--------------------------------- -- ------------------------ ---- ------------
N/A 003B9 WD 0 0 NR 00282 RW 0 3625 T.X. Suspended

N/A 003BA WD 0 0 NR 00283 RW 0 3931 T.X. Suspended
N/A 003BB WD 0 0 NR 00284 RW 0 3988 T.X. Suspended
N/A 003BC WD 0 0 NR 00285 RW 0 2620 T.X. Suspended
N/A 003BD WD 0 0 NR 00286 RW 0 2619 T.X. Suspended
N/A 003BE WD 0 0 NR 00287 RW 0 2391 T.X. Suspended
N/A 003BF WD 0 0 NR 00288 RW 0 14 T.X. Suspended
N/A 003C0 WD 0 0 NR 00289 RW 0 27 T.X. Suspended
N/A 003C1 WD 0 0 NR 0028A RW 0 23 T.X. Suspended
N/A 003C2 WD 0 0 NR 0028B RW 0 2695 T.X. Suspended
N/A 003C3 WD 0 0 NR 0028C RW 0 2661 T.X. Suspended
N/A 003C4 WD 0 0 NR 0028D RW 0 2660 T.X. Suspended
N/A 003D1 WD 0 0 NR 0029A RW 0 1765 T.X. Suspended
N/A 003D2 WD 0 0 NR 0029B RW 0 1738 T.X. Suspended
N/A 003D3 WD 0 0 NR 0029C RW 0 1775 T.X. Suspended
N/A 003D4 WD 0 0 NR 0029D RW 0 1850 T.X. Suspended
N/A 003D5 WD 0 0 NR 0029E RW 0 1804 T.X. Suspended
N/A 003D6 WD 0 0 NR 0029F RW 0 1752 T.X. Suspended
N/A 003D7 WD 0 0 NR 002A0 RW 0 1759 T.X. Suspended
N/A 003D8 WD 0 0 NR 002A1 RW 0 1817 T.X. Suspended
N/A 003C5 WD 0 0 NR 0028E RW 0 15 T.X. Suspended
N/A 003C6 WD 0 0 NR 0028F RW 0 5 T.X. Suspended
N/A 003CA WD 0 0 NR 00293 RW 0 12 T.X. Suspended
N/A 003CB WD 0 0 NR 00294 RW 0 12 T.X. Suspended
N/A 003CC WD 0 0 NR 00295 RW 0 11 T.X. Suspended
N/A 003CD WD 0 0 NR 00296 RW 0 9 T.X. Suspended
N/A 003CE WD 0 0 NR 00297 RW 0 4 T.X. Suspended
N/A 003CF WD 0 0 NR 00298 RW 0 1 T.X. Suspended
N/A 003D0 WD 0 0 NR 00299 RW 0 8 T.X. Suspended
Total ------- ------- ------- -------

Track(s) 0 0 0 41621
MB(s) 0.0 0.0 0.0 5202.6
Legend for MODE:

Remove Masking from Source Frame Devices

We can now remove masking of all participating source devices to all four hosts.

Note: In scenario where some devices from source frame are still going to be presented on host, you
may just remove participating source migration devices from active masking view’s storage group. This
will ensure that only participating source migration devices will be removed from masking while
remaining devices are still visible to host.

Following section provides output to removing masking of source devices.

$ sudo symaccess -sid 1346 delete view -name MV_lnxdb-svl-13-16_Shared -nop
$ sudo symaccess -sid 1346 delete view -name MV_lnxdb-svl-13_Local -nop
Perform “Deletepair” Operation on SRDF/Metro Devices

Finally, we are ready to perform SRDF deletepair operation. This operation will delete relationship
between source and target devices.

Note: Once the delete pair operation is performed, source devices WWN will be spoofed. It will take
external device WWN identity of target device.

Following section provides CLI output of performing “deletepair” operation.

$ sudo symrdf -sid 1346 -f srdf_metro_1346-1695.pair -rdfg 40 deletepair -force -v
Execute an RDF 'Delete Pair' operation for device file

An RDF 'Delete Pair' operation execution is in progress for device

RDF Device List group 'NA'
STARTING an RDF 'DELETEPAIR' operation.
Scanning device(s) for a 'INT_CTRL_DELETEPAIR' operation (SOURCE).
Device: 003B9 (Remote Device: 00282) [SELECTED]

Device: 003BA (Remote Device: 00283) [SELECTED]
Device: 003BB (Remote Device: 00284) [SELECTED]
Device: 003BC (Remote Device: 00285) [SELECTED]
Device: 003BD (Remote Device: 00286) [SELECTED]
Device: 003BE (Remote Device: 00287) [SELECTED]
Device: 003BF (Remote Device: 00288) [SELECTED]
Device: 003C0 (Remote Device: 00289) [SELECTED]
Device: 003C1 (Remote Device: 0028A) [SELECTED]
Device: 003C2 (Remote Device: 0028B) [SELECTED]
Device: 003C3 (Remote Device: 0028C) [SELECTED]
Device: 003C4 (Remote Device: 0028D) [SELECTED]
Device: 003D1 (Remote Device: 0029A) [SELECTED]
Device: 003D2 (Remote Device: 0029B) [SELECTED]
Device: 003D3 (Remote Device: 0029C) [SELECTED]
Device: 003D4 (Remote Device: 0029D) [SELECTED]
Device: 003D5 (Remote Device: 0029E) [SELECTED]
Device: 003D6 (Remote Device: 0029F) [SELECTED]
Device: 003D7 (Remote Device: 002A0) [SELECTED]
Device: 003D8 (Remote Device: 002A1) [SELECTED]
Device: 003C5 (Remote Device: 0028E) [SELECTED]
Device: 003C6 (Remote Device: 0028F) [SELECTED]
Device: 003CA (Remote Device: 00293) [SELECTED]
Device: 003CB (Remote Device: 00294) [SELECTED]
Device: 003CC (Remote Device: 00295) [SELECTED]
Device: 003CD (Remote Device: 00296) [SELECTED]
Device: 003CE (Remote Device: 00297) [SELECTED]
Device: 003CF (Remote Device: 00298) [SELECTED]

Device: 003D0 (Remote Device: 00299) [SELECTED]
Started.
Delete RDF Pair in (1346,040)....................................Done.
The RDF 'DELETEPAIR' operation SUCCEEDED.
The RDF 'Delete Pair' operation successfully executed for device


Performing Non-Disruptive Migration Using SRDF/Metro: Abstract

Uploaded by

Document Information

Original Description:

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

Performing Non-Disruptive Migration Using SRDF/Metro: Abstract

Uploaded by

Copyright:

Available Formats

Performing Non-Disruptive Migration

Date: July 7, 2016

Prepared for: Prepared by:

Cisco GIS Chirag Patel

Witness Array Option

Non-Disruptive Migration Using

vHBA4 200b12000000009b 4D:29

High-Level SRDF/Metro Storage Migration Steps

• Device Creation On Target Frame

Host and Storage Environment Verification Check List

SRDF Group Creation Between Source and Target Frame

Execute a Dynamic RDF Addgrp operation for group

Successfully Added Dynamic RDF Group 'rdfgrp40' for Symm: 000196801346

$sudo symcfg -sid 1346 -rdfg 40 -ra all -switched list

Symmetrix ID: 000196801346 (Local)

Local Group Link Remote

Device Creation On Target Frame

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Performing Access checks..................................Allowed.

New symdevs: 00282:00299 [TDEVs]

The configuration change session has successfully completed.

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Performing Access checks..................................Allowed.

New symdevs: 0029A:002A1 [TDEVs]

The configuration change session has successfully completed.

$sudo symdev -sid 1695 -dev 00282:02A1 list

Symmetrix ID: 000196801695

Device Name Dir Device

0029D Not Visible ???:??? TDEV N/Grp'd RW 8194

Perform SRDF/Metro “Createpair” Operation

Execute an RDF 'Create Pair' operation for device file

An RDF 'Create Pair' operation execution is in progress for device

Create RDF Pair in (1346,040)....................................Started.

Merge track tables between source and target in (1346,040).......Started.

The RDF 'Create Pair' operation successfully executed for device

$sudo symrdf -sid 1346 -file srdf_metro_1346-1695.pair -rdfg 40 query

Symmetrix ID : 000196801346 (Microcode Version: 5977)

Source (R1) View Target (R2) View MODE

N/A 003B9 RW 0 2146305 NR 00282 WD 0 0 T.X. Suspended

Total ------- ------- ------- -------

Legend for MODE:

M(ode of Operation) : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

Execute an RDF 'Incremental Establish' operation for device file

An RDF 'Incremental Establish' operation execution is in progress for device

Suspend RDF link(s) for device(s) in (1346,040)..................Done.

The RDF 'Incremental Establish' operation successfully initiated for device

$sudo symrdf -sid 1346 -file srdf_metro_1346-1695.pair -rdfg 40 query

Symmetrix ID : 000196801346 (Microcode Version: 5977)

Source (R1) View Target (R2) View MODE

N/A 003B9 RW 0 2143259 RW 00282 WD 0 0 T.X. SyncInProg

Total ------- ------- ------- -------

Legend for MODE:

M(ode of Operation) : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

Verify Devices in “ActiveBias” Mode

Symmetrix ID : 000196801346 (Microcode Version: 5977)

Source (R1) View Target (R2) View MODE

N/A 003B9 RW 0 0 RW 00282 RW 0 0 T.X. ActiveBias

Total ------- ------- ------- -------

Legend for MODE:

M(ode of Operation) : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy