SRDF A

EMC VNX Series
Release 7.0
Using SRDF/A with VNX

P/N 300-011-847
REV A01
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
" 1998 - 2009 $," ".
/ % 2011
$," . 3
.
3'$ (-%.1, 3(.- (- 3'(2 /4!+(" 3(.- (2 /1.5(#$# " 2 (2." $," ".1/.1 3(., *$2 -. 1$/1$2$-3 3(.-2 .1 6 11 -3($2 .% -8 *(-# 6(3' 1$2/$"3 3.
3'$ (-%.1, 3(.- (- 3'(2 /4!+(" 3(.-, -# 2/$"(%(" ++8 #(2"+ (,2 (,/+($#
6 11 -3($2 .% ,$1"' -3 !(+(38 .1 %(3-$22 %.1 / 13("4+ 1 /41/.2$.
4, , $,"
.
% -- , 3
# $," /.
% -- $," , $," " 3
$,"..
.
" ': ', ,
Using SRDF/A with VNX 7.0
01748-9103
Contents
Preface.....................................................................................................5
Chapter 1: Introduction...........................................................................9
2 .............................................................................................10
1.............................................................................................................10
4 ...........................................................................................12
1 ..............................................................................................13
Chapter 2: Concepts.............................................................................15
21#%........................................................................................................................17
" " 2..............................................17
21#% .........................................................................18
21#%/ ...................................................................................................................20
21#%/ ..................................................................................................21
( ...........................................................22
# 21#%/ 21#%/2........................................................23
" 5-7 -
............................................................................................................24
/ .......................................................................................26
2 ..............................................................27
2
..........................................................................................27
5-7 # , ().............................28
5-7 # , ................................................29
4 5-7 21#% .................................................30
21#%/ ..........................................................................................31
. ...............................................................35
Contents
Chapter 3: Configuring.........................................................................37
/ .............................................................................38
/ () 5-7.................................................39
/ () 5-7....................................39
5 .........................................................................40
( (/)......................................................41
( 5-7...........................................................................41
( 5-7...................................................................45
5 21#%/ 5-7 (/)...............................49
(/).....................................................................52
/ ...................................................................53
5-7.........................................55
5 21#%/ ....................................................59
$ ........................................................................65
1 5-7........................................................................................65
/ ................................................................................66
1 ......................................................................66
Chapter 4: Troubleshooting..................................................................73
$," $-+ ( -..............................................................74
* .......................................................................74
1 ...........................................................74
1 ....................................................................75
1 ..........................................................................80
1 ...............................................................................83
1 # , ..............................91
' ...........................................................94
$ .......................................................................................................94
$," 3 / 2...........................................................95
Appendix A: Portfolio of High-Availability Options.............................97

Glossary................................................................................................103
Index.....................................................................................................107
Preface
,
$," . 3,
.
% -- , .
( ,
$," .
Preface
Special notice conventions

$," :
CAUTION:
.
Important:
Note:
, -.
Hint: , -
.
Where to get help

$," , , :
/ % , , ,
$," , , , $," . 2
( ) ://2.$,"..
3 & $," . 2 .
2 / .
3 % , $," "
2 $," . 2 . ,
2 / , Live Chat Create a service request. 3
$," . 2,
. " $,"
.
Note: #
.
Your comments
8 , ,
.
/ :
Preface
techpubcomments@EMC.com
Preface
1
Introduction
$," 2 1 # %/ (21#%/ )
- . 21#%/
5-7/2
#,7 5-7/2 #,7
( ) ,
-- . " 2 .
3 5-7

- . 8 $," " 2
1 2
, 2 #,7
21#% 21#%/ ,
21#%/ .
3 :
2 10
1 10
4 12
1 13
Introduction
System requirements
3 1 10 $," 5-7 , , ,
.
Table 1. System requirements
Software
Hardware
EMC Symmetrix Enginuity version 5670 or later microcode on the source and destination Symmetrix
DMX systems with SRDF/A.
VNX version 7.0 on the source and destination servers.
Remote adapter (RA) for interconnecting the Symmetrix DMX systems. The connection can be over
wide area channels using Fibre Channel (FC), Dense Wavelength Division Multiplexing (DWDM), or
IP.
Production and standby Data Movers on the VNX systems to support the EMC SRDF /A active/passive
configuration. The Control Station 0 (CS0) volume requires a separate RA and remote data facility
(RDF) group.
Similar source and destination VNX models.
Network
IP data network (required for multi-hop configurations) or dedicated SRDF/A channel (link) for communication between Control Stations of source and destination VNX systems.
Storage
Two attached VNX/Symmetrix DMX system pairs.
Restrictions
21#%/
2 21#%/
21#%/ 2 3, 5, 8 . . 2
#,7 (5670 ) .
Note: 3 2 $ 2 21#% , $,"
2 1 # % (21#%) / &,
21#%/ 2 #,7. 3
://2.$,"., $," . 2 .
10
3 2 $ 5670 21#%/ ,
5-7, . 3 5671
.
21#%/
21#%/ . 6 ,
21#%- # , . 3 ,
5-7/2 .
Introduction
21#%- # , 21#%
. + (23#)
(!"5) , # , 21#%
, 21#%- # ,. " 4
.
Management restrictions
21#%/ $," 4 . 21#%/

"+( ///_/_ .
% " 2, 21#% ,
///_/_ , ,
, "20. " 2 1 ("21)
.
% "-2-14 , "20 + 21#%

, 21#%/ .
2 $ 2 28,"+( 5-7
" 2 , ,
$," ( "". ', 28,"+(
21#%/ .
6 _ ,
///500 . - 2
///500 . ( ///500 ,
.
SnapSure checkpoints restrictions
$," 22 25
(/%2) # , . (
/%2 21#% +4-,
22 25 21#% +4-
/%2. ( 25
21#% +4-, ,
. $ .
21#%/ ,
.
( 22 , 25
___ . ( 25
, /%2 , .
Restrictions
11
Introduction
VNX feature-specific restrictions
% 2 $
21#% , , # , 1#%
. 3 $," 3%/%2 -" %" .
3, _ -_
21#%. # : $
13421842457: 21#%."
21#%/ 3%/%2 -"

%". -" 21#%/
3%/%2 -" . (
%", -
21#%/ .
$," 5-7 1
21#%/2 (21#%/2) 21#%/ (21#%/ ) $,"
,5/2 (,5/2). 8 21#% ,5/2
5-7 1 . ', 21#%
,5/2 , 1 21#%
,5/2 . $ 1
# , . . ,
21#% ,5/2 .
, 21#% $," ,5/2 .

( , 2 ,
,5/2. ,5/2 5-7
.
21#%/
21#%/ 1 (21#%/ 1) 21#%/
21#%/ (22#) . (
22# 21#%/ , 5-7
.
21#% 5-7 %,. 4 5-7 %,

.
21#% ,/%2. " $,"

,/%2 21#%.
" 21#% # 21#%.

.
$," $-+ ( - 74
. 2 10
.
User interface choices

3 21#%/
("+(). 8 5-7 21#%/ .
12
Introduction
Related information
5-7 21#%/
:
, ,
5-7 " + ( 1 %
" - 2 $ , &
. 5-7 %
/ 1 1 5-7
4 5-7 %,
4 ,5/2 5-7 % # 1
4 3%/%2, -", %" 5-7
4 21#%/2 5-7 # 1
. $," , :
2 $ 2 21#% % "+( / &
2 1 # % (21#%) / &
EMC VNX documentation on the EMC Online Support website

3 $," 5-7 $,"
. 2 . 3 ,
://2.$,".. , 5-7 2
/ .
VNX wizards
4 . 3
4 .
Related information
13
Introduction
14
2
Concepts
21#%/
- .
21#%/ -
,
. (
- -

.
! 21#%/
$-
2 1 # %/2 (21#%/2).
/ 21#%/2
.
$ -

. !
,
21#%/ ,

. 3
.
,
. #
, ,
.
%
. # .
% .
21#%/ 2 1 # % (21#%)
$," 2 21#%
15
Concepts
- . 21#%/
21#% .
3 :
16
21#% 17
21#%/ 20
21#%/ 21
# 21#%/ 21#%/2 23
" 5-7 -
24
/ 26
21#%/ 31
. 35
Concepts
SRDF
21#% 2
, .
21#% :
/ ! ,
. $ 5-7 # ,. (
, .
/ 4 5-7 ,
, () 5-7 ,
, (). 3
.
Communication between Control Stations

( 21#% , " 2
5-7 :
(/ ()
21#% (
21#%)
SRDF
17
Concepts
% 1 18 5-7--21#%
.
PS2
PS3
PS4
SB15
SB13
SB11
SB7
SB5
SB3
PS0
Dedicated link for SRDF
Symmetrix
VNX
host
SB1
SB2
SB0
SMB0 SMB1
Source
R1
SB9
SB12
SB10
SB8
SB3
SB4
SB7
PS1
SB1
SB5
PS0
SB6
SB13
SB11
SB15
Optional IP
data network
connection
SB14
Site B target
SB9
SB12
SB8
SB6
SB0
SB2
SB4
VNX
host
SB10
SB14
Site A source
PS1
PS2
PS3
PS4
SMB0 SMB1
Target
R2
Symmetrix
VNX-000033
Figure 1. Basic VNX-with-SRDF configuration
SRDF and logical volumes

3 5-7 21#% , 5-7
.
$ 5-7 :
2 2 . % ,
2 , 001, 001-11 ( , ,
) 001-12 ( , , ).
3 12 11 21#%. 3 12
5-7 -
. ', (11)
, 21#% 12 11
.
18
Concepts
% 2 19 .
- 2 (# ( 001 001
).
SB15
SB13
PS2
PS3
PS4
SB7
SB5
SB3
SB2
SB0
PS0
Logical volume 001
VNX
host
SB1
SB3
SMB0 SMB1
Source
R1
001-R1
SB9
SB11
SB14
SB12
PS1
SB4
SB6
SB8
SB10
SB15
SB13
SB11
PS0
SB1
SB5
SB7
SB9
SB12
SB8
SB6
SB0
SB2
SB4
VNX
host
Site B target
SB10
SB14
Site A source
PS1
PS2
PS3
PS4
SMB0 SMB1
Target
R2
001-R2
Dedicated SRDF link
Symmetrix
Symmetrix
VNX-000034
Figure 2. VNX with SRDF logical volume
Note: ( 5-7 , $," 2

1 2 ()
2 (). ( , 21#% $,"
2 . + $,"
21#% .
5-7 21#% :
" 3 5-7 21#%/2,

21#% . 21#%/2 -
5-7/2
. 21#%/2 ,
.
3
2 ,
21#%/2 3%/%2 -" . 3%/%2 -"
5-7
SRDF
19
Concepts
2 !"5. 3 -" ,
(12) , 21#%/2 . 4 21#%/2 5-7 # 1
4 3%/%2, -", %" 5-7 .
$- 3 5-7 21#%/ , 21#%

. 21#%/ -
5-7 /2 #,7
. 21#%/ , --
.
5-7 3%/%2 %" 21#%
- , %" 12
.
" $,"
.
SRDF/A
21#%/ 5-7/2 #,7
5-7/2 #,7 . 3
21#%/2 (21#%/2) . 5-7 ,
21#%- 5-7 () 5-7, 2
#,7 , .
3 21#%/ 5-7 / .
( / , 2 #,7
21#%/ . - 2 #,7
, () 5-7 . 6
, 5-7 " 2
. 3 5-7
5-7.
Note:
% 21#%/ , 21#%-
, # ,. 3 , 21#%- #
, 21#% , (23#, !"5) . ,
.
3 5-7 , ,
"' $," .
20
Concepts
SRDF/A delta sets

21#%/ - (11)
(12) .
#- , , , ,
. #
,
() .
3 :
1. " -: 21#%/ ( -) (11)
, 21#%/ .
3 , 30
. 8 $," " 2 1
2 #,7 .
2. 3 --1: , -
--1, -
(12) 2 #,7 . 3
--1 . -
- .
3. 1 --1: # --1 , -
(12) 2 #,7 . 6 --1
, , , -
.
4. 1 --2: # , 12 (
). 6
--2 12 , 11 12
- . .
% 3 22 .
:
1. 3 .
2. 3 --1 ,
.
3. 3 --2 .
SRDF/A delta sets
21
Concepts
Note: 3 .
. ( ,
, 20 , .
PS2
PS3
PS4
SB15
SB3
SB1
SB2
SB0
SMB0 SMB1
SB5
SB7
SB9
SB11
SB13
SB14
SB12
SB10
SB3
SB4
SB7
PS1
SB1
SB5
PS0
SB8
VNX
host
SB6
SB13
SB11
SB15
Site B target
SB9
SB12
SB8
SB6
SB0
SB2
SB4
VNX
host
SB10
SB14
Site A source
PS0
PS1
PS2
PS3
PS4
SMB0 SMB1
I/O
Source
R1
device
1. Capture writes
using default
cycle time of 30
sec (active)
2. Transmit writes
to R2 (inactive)
SRDF/A device pair

active sessions
Target
R2
device
SRDF/A delta set begins

Cycle
N
Cycle
N-1
Cycle
N-2
Dedicated SRDF link
Symmetrix
Cycle
N-1
Symmetrix
4. Writes restored
to R2 target device
(active)
3. Receive writes
on R2 (inactive)
VNX-000032
Figure 3. SRDF/A active/passive configuration featuring delta sets (cycles) to transfer data
Important resource considerations
22
. , 21#%/
.
.
# , -
20 , .
# - ( ),
. + $,"
. 8
21#%/ 12 11 28,"+(
21#%/ ( , //// -
<_> -. 111_3).
Concepts
Differences between SRDF/A and SRDF/S

3 2 23 21#%/
2 .
21#%/2 5-7
Table 2. Summary of differences between SRDF/A and SRDF/S

SRDF/A
SRDF/S
Requires Symmetrix DMX systems or later versions. Works with Symmetrix 3xxx, 5xxx, 8xxx, or DMX
systems.
Extended-distance replication facility.
Complete disaster recovery configuration for systems

within relatively short distances.
Provides manual failover and failback of backend

Provides a complete disaster recovery configuration
storage systems and servers with minimal data loss. without data loss.
Provides system-wide points of consistency.
Provides I/O-level consistency.
Each write I/O to the source is immediately committed on the source image only and sent to the destination in predefined timed cycles (delta sets). The
host is acknowledged of the write before the destination Symmetrix system receives the write.
Each write I/O to the source is synchronously replicated to the destination Symmetrix system.The host
is acknowledged of the write after the destination
Symmetrix system receives and CRC-checks the
data.
Locality of reference provides more efficient use of Each I/O is sent to the destination Symmetrix system
network bandwidth. With data sent as cycles of de- before an acknowledgment is sent to the host.
pendent write-consistent data, less data needs to
transfer to the destination. If the same track is written
to more than once within an active set, SRDF/A
sends the update over the link once.
Currently supports active/passive configurations only. Supports active/passive and active/active configurations.
Can be implemented with TimeFinder/FS NearCopy
Not implemented with configurations employing
TimeFinder/FS NearCopy or FarCopy. NearCopy is and FarCopy (adaptive copy disk or disk-pending
not applicable because SRDF/A volumes cannot be mode).
source volumes for TimeFinder/FS NearCopy file
system snapshots. In a configuration employing
FarCopy, adaptive copy disk mode or disk-pending
mode can be used instead of SRDF/A.
-
$," 5-7. 4 21#%/2 5-7 # 1
21#%/2, 21#%.
Differences between SRDF/A and SRDF/S
23
Concepts
Comparison of VNX for file high-availability and replication products

3 3 24 5-7
, , . 3 $,"
.
Note: $," 5-7
.
. , 5 % 2 5-7
5 , , 5 % 2 5-7 , .
Table 3. Comparison of VNX for file high-availability and replication products
Product
Storage platform
Description
MirrorView/Synchronous
VNX for block only, CX series Using attached VNX for file
(CX700/600/500/400, CX3- and VNX for block backend
40, or CX3-80)
pairs, performs synchronized,
Note: This product is currentremote mirroring to provide
ly available through the RPQ
full disaster recovery without
process. Contact your local
data loss at a limited disEMC Sales Representative
tance. Using MirrorView/Synor EMC Service Provider for
chronous with VNX for File
more information.
for Disaster Recovery provides more information about
MirrorView/S. RPQ process
controls the access to this
document.
Restrictions
Cannot be used in the same
VNX for file configuration as
SRDF. Cannot be used with
Symmetrix-based products
such as TimeFinder/FS.
Cannot be used with the Automatic File System Extension feature.
Performs LUN (volume)
cloning, not file system
cloning; remote volumes are
accessible only after a
failover.
With MirrorView/S, the VNX
for file does not see the mirrored LUNs at the destination
site until a failover is activated. This is different from
SRDF, in which the remote
mirrors (R2 volumes) of the
Control Station LUNs are
visible to the Data Movers.
SRDF/Synchronous
24
Symmetrix only (3xxx, 5xxx, Using attached VNX for file

and Symmetrix pairs, per8xxx, or DMX series)
forms synchronized, remote
replication to provide full disaster recovery without data
loss at a limited distance.
Using SRDF/S with VNX for
Disaster Recoveryprovides
more information about
SRDF/S.

MirrorView/S. Cannot be
used with the Automatic File
System Extension feature.
Performs volume cloning, not
file system cloning; remote
volumes are only accessible
after a failover.
Concepts
Table 3. Comparison of VNX for file high-availability and replication

products (continued)
Product
Storage platform
Description
Restrictions
SRDF/Asynchronous
Symmetrix only, DMX series Using attached VNX for file

and Symmetrix pairs, performs asynchronous, pointin-time replication at an extended distance. This technical module provides more information about SRDF/A.

MirrorView/S. Cannot be
used with the Automatic File
System Extension feature.
TimeFinder/FS
Symmetrix only
Using a business continuance configuration with Symmetrix business continuance

volumes (BCVs), provides
local file system cloning.
A single file system should

occupy an entire STD volume. TimeFinder/FS does
not perform volume cloning.
TimeFinder/FS NearCopy
and FarCopy
Symmetrix only
Using a business continuance configuration with Symmetrix BCVs, provides remote file system cloning,
creating a point-in-time copy
(snapshot) of a VNX production file system.
These products do not perform volume cloning.

NearCopy is limited to 200
km. FarCopy supports extended distances.
Performs volume cloning, not

file system cloning; remote
volumes are only accessible
after a failover.
NearCopy relies on SRDF/S

and FarCopy relies on SRDF
A remote file system can be adaptive copy disk or diskmounted and used during
pending mode to manage file
normal operation (that is, it is system snapshots.
generally accessible).
Using TimeFinder/FS,
and FarCopy do not work
NearCopy, and FarCopy on with Automatic File System
VNX provides more informa- Extension.
tion about TimeFinder/FS
products.
Comparison of VNX for file high-availability and replication products
25
Concepts
Table 3. Comparison of VNX for file high-availability and replication

products (continued)
Product
Storage platform
VNX Replicator
VNX for file-supported stor- Produces a read-only, pointage (one Symmetrix or VNX in-time copy of a source file
for block pair)
system and periodically updates this copy, making it
consistent with the source file
system. The read-only copy
can be used by a Data Mover
in the same VNX cabinet, or
by a Data Mover at a remote
site for content distribution,
backup, and application testing. Using VNX Replicator
provides more information.
For TimeFinder/FS,
NearCopy, or FarCopy, a
business continuance volume
(BCV) cannot be a source or
a destination file system for
replication. You can replicate
the underlying source file
system, but you cannot replicate the BCV.
VNX-supported storage
Not intended to be a mirror,

disaster recovery, or highavailability tool. Because it is
partially derived from realtime
PFS data, a checkpoint could
become inaccessible (not
readable) if the PFS becomes inaccessible. Only
checkpoints and a PFS
saved to a tape or to an alternate storage location can be
used to provide disaster recovery.
SnapSure
Description
On a VNX system, provides

read-only, point-in-time logical copies, also known as
checkpoints, of a production
file system.
Restrictions
You cannot use the

TimeFinder/FS -Restore option for a replicated source
file system. Replication is
unaware of any changes because these changes occur
at the volume level.
In version 5.6, SnapSure

supports 112 checkpoints, 96
in 5.5, 64 in 5.4, and 32 prior
to 5.4.
Planning considerations
! 21#%/
2 27
5-7 # , () 28
5-7 # , 29
26
5-7, :
Concepts
4 5-7 21#% 30
Note: $ 21#%-
. $ 23# !"5, . ! 21#%/
, 21#%- # ,
, # , 21#% .
# ,, 21#%
21#%- # ,. 3 21#% ,
# , 21#% . " 4
21#%/ .
Symmetrix system configuration

3 21#%/ 2 #,7
21#% , 21#% ,
. 8 $," " 2 1
2 , 21#%
2
.
3 2 $ 2 21#% $," . 2
, 2 1 # % (21#%) / &,
21#% 2 .
Adding Symmetrix storage devices to the existing system configuration

, 2
, :
1. 1 _ - - - 2
.
2. # 21#% , ///_ -
" 2 :
( 21#% /, ///_ -
.
( 21#% /, ///_ -

" 2, " 2
" 2.
( / , 2
. 3 ,
2 . ! ,
///_ - " 2 ,
11 ,
27
Concepts
12 .
6 ///_ - " 2,
. 3 12
. 3 12
2
///_ - .
VNX volume and Data Mover decisions (flexibility)

21#%/ 5-7 /
, # , # ,. ', # ,
. % ,
# , . 8
# ,.
6 # , :
% () # ,
21#%/ # ,, # ,
. 3 -- # ,
, # ,
.
( # , 21#%/ # ,
# ,, 21#%/ #
, . 3 .
21#%/ # ,
# ,.
3 21#%/ # ,
# ,.
3 21#%/ # ,
12 # ,.
+ # , # ,,
21#%- # ,.
# , /
21#%/ :
28
. 5-7:
+ # , 21#%/
+ # , 21#%/
+ # , (-21#%/ )
+ # , (-21#%/ )
# ,
# ,
Concepts
. () 5-7:
21#%/
# ,
+ # , (-21#%/ )
+ # , (-21#%/ )
VNX Data Mover configuration checklist

! 5-7 21#%/ , # ,
:
+ # , 21#%/ 21#%/ #
,. 3 -- . # , 21#%/
# ,, 21#%/ # ,
21#%/ . ( ,
. - , # ,
_, _2.
# # , 21#%/ # ,
. % -2 /
# , ,
5-7 # , ( ,
_3) # , 21#%/ . " #
, 21#%/ 5-7
, :
server_standby server_2 -delete mover=server_3
server_setup server_3 -type nas
( "-2-14 (14-# ,) ,
, 21#%/
. ( 5-7 45
:
$ # , 5-7
, , 21#%/ # ,
# , . ( ,
. % ,
-2 "-2-14 , -2
"-2-14 .
" (/ - # ,
.
$ 21#%/ 21#%/ #
, , 21#%/
21#%/ # ,.
29
Concepts
$ # ,,
21#%- # ,, 21#%/ . 3
/ .
$ : 2
-(2/#-2 4-(7 , 6(-2//#"/!#"/#"
6 , -3 . 3 "(%2
21#% ,
-%2 . % ,
.2. % "(%2 ,
/ 4(#/&(#.
Note: ( 5-7 21#% ,

21#% , 22
( 25, ) 21#%
. ., 25 (23#)
21#% ,
21#%- .
Upgrading the VNX SRDF environment

+ $,"
, 5-7 21#%
5.6 21#%/ .
! ,
, .
3 21#%/
30
( 21#%/2):
Step
Action
1.
Halt all source Data Movers and shut down the Control Station.
2.
Ensure that the source and destination Symmetrix DMX VNX volumes are synchronized.
3.
Halt the SRDF links to ensure that the appropriate device groups are suspended.
4.
Restart the source Control Station and Data Movers.
5.
Perform the upgrade on the source site.
6.
Test or verify the upgrade.
7.
Resume the SRDF links. For SRDF/A, ensure that the devices in the appropriate device groups are in a Consistent state.
Concepts
8 1 7. 8
5-7 5-7.
Note: 3 21#%/ ". ( , $,"
$," 2 / 21#%/
" .
SRDF/A task overview

3 4 31 21#%/ /
21#%/ 5-7 . 6
, , 21#%
5-7 , .

. % :
# /nas/sbin/nas_rdf activate nocheck
# /nas/sbin/nas_rdf restore -nocheck
3 5 35 . /
, 2
27 2 #,7 5-7 # ,
. ( , $," " 2 1
21#%/ . " 4
21#%/ .
Table 4. SRDF/A task overview
Task
Command used
Preinitialize the relationship be- From each VNX, using nasadmin, log in
tween the source and destination as root:
VNX.
nas_cel-create<cel_name>
Description
Establishes trusted communication between source and destination VNX systems as a prerequisite to SRDF/A initialization. Must be performed on both VNX
systems, using the same passphrase
(615 characters).
The nas_cel command replaces one of

the nas_rdf -init commands from the
previous versions.
-ip<ip>-passphrase
<passphrase>
31
Concepts
Table 4. SRDF/A task overview (continued)

Task
Command used
Initialize an SRDF/A relationship From source and destination, as root:

between attached VNX/Sym/nas/sbin/nas_rdf
metrix pairs.
-init
32
Description
If all SRDF volumes are in a Consistent

state, enables the designated destination
VNX to provide full file system access
and functionality if a site failure occurs.
Configures the Control Station to use

SRDF/A.
Identifies the remote destination VNX

paired with the source VNX.
Identifies the volume mapping on the

Symmetrix DMX system, which maps R1
volumes to their R2 counterparts.
Establishes the Data Mover relationships

from the production Data Mover to the
standby.
Runs the SRDF session state check before initialization.
Runs the SRDF standby Data Mover

configuration check and the Symmetrix
device state check after initialization.
Runs the device group configuration

check and the Data Mover mirrored device accessibility check for both R1 and
R2 device groups after initialization.
Concepts

Task
Command used
Activate an SRDF/A failover from From destination, as root:

a source VNX to a destination
/nas/sbin/nas_rdf
VNX.
-activate
Description
Performs a test failover or manual

failover. For example, a source VNX attached to a source Symmetrix system
becomes unavailable. After the failover,
users have access to the same file systems using the same network addresses
as they did on the source, provided they
have network access to the remote VNX
site.
Sets each R1 volume on the source VNX

(the one failing over) as read-only. This
only occurs if the source Symmetrix system is available.
Sets each R2 volume on the remote

Symmetrix as read/write.
Enables each SRDF/A standby Data

Mover on the remote Symmetrix to acquire the following characteristics of its
source counterpart:
Network identity: IP and MAC addresses of all network interface

cards (NICs) in the failed Data
Mover.
Service identity: Network File System/ Common Internet File Service

(NFS/CIFS) characteristics of the
exported file system controlled by
the failed Data Mover.
Runs the SRDF standby Data Mover

configuration check, the SRDF session
state check, and the Symmetrix device
state check before activating a failover.

check and the Data Mover mirrored device accessibility check for R2 device
groups before activating a failover.
33
Concepts

Task
Command used
Description
Restore a source VNX after a

failover.
From destination, as root:
Typically scheduled by and performed

under the guidance of your local EMC
Customer Support Representative to
ensure continuity between the Symmetrix
systems. Restoration of a source VNX
involves a complete check of the Symmetrix system and SRDF/A and verification of full connectivity to the restored file
systems on the source VNX.
Copies data from R2 volumes to the

corresponding R1 volume on the source
Symmetrix system.
Restarts SRDF standby Data Movers into

standby mode.
Write-disables R2 volumes from the Data

Movers.
Synchronizes R2 to R1.
Resumes mirroring of the R1 devices.
Restarts each Data Mover on the source

VNX and reacquires the IP addresses
and file system control from the SRDF
standby Data Movers.
Runs the SRDF session state check, the

Symmetrix device state check, and the
SRDF restored state check before
restoring a destination VNX.

groups before restoring a destination
VNX.
Runs the Symmetrix device state check

before restoring a source VNX.

groups before restoring a source VNX.
/nas/sbin/nas_rdf
-restore
34
Concepts
Table 5. Health check details

Health check
Description
SRDF standby Data Mover Lists all slot IDs of SRDF source Data Movers on the source
configuration check
side, and compares the list with the list of all slot IDs of SRDF
standby Data Movers on the destination side. If a slot from the
source side is not an RDF standby Data Mover on the destination side, a warning message with the slot ID is displayed.
SRDF session state check
Checks if all devices are synchronized. If they are not synchronized, and if they are in various states, a warning message is
displayed. If none of them is synchronized, but all of them are
in the same state, for example, all of them are consistent or
partitioned, and so on, no warning message is displayed.When
the nas_rdf init command is run, if all the devices are partitioned, a warning message is displayed.
Device group configuration Lists all mirrored devices of an RDF group on backend (symrdf
check
list) and compares the list with the list of devices in a device
group created by using the symdg (symrdf g <device group>
query) command. If there is a missing device in the device
group, a warning message is displayed.
Data Mover mirrored device Lists all devices in a device group, and compares the list with
accessibility check
the list of devices obtained by using the server_devconfig
probe scsi all command. If there is a device in the device
group that is not present in the output of the probe command,
a warning message is displayed. Some of control volumes do
not have TID/LUN depending on their configuration, and these
are ignored in the check.
Symmetrix device state
check
Checks if there is a degraded or failed state device on the back

end by using the symdev list service_state notnormal command. If there is a degraded or failed state device, a warning
message is displayed. All degraded or failed devices on the
Symmetrix, including the devices that are not used for VNX,
are listed in the message.
SRDF restored state check Checks and displays an error message if the source volumes
are R1 and ReadWrite, and if the destination volumes are R2
and ReadOnly. It does this by using the symdg show command.
Overview of the sample configuration

3 , 5-7
:
100_ 5-7. ( .
Overview of the sample configuration
35
Concepts
110_ 5-7. ( -
.
Note: ( , 100_ 5-7

, 110_ 5-7
- .
36
3
Configuring
3 21#%/
/ 38
( (/) 41
(/) 52
1 5-7 65
37
Configuring
Preinitialize the configuration

21#%/ , $," 2 /
5-7 . /
5-7 .
Prerequisites
/ 5-7 .
3 " 2 10
.
/ 615
5-7 . .
3 , 5-7 .
3 _ -
5-7 . 2 -5.6 _ -
. 5 5.6 _ - .
3 ,
21#%/ .
3 5-7 .
/ 21#%/
8 21#%/ (/4 (/6 (/ . 6

, " 2
(/4/(/6 " 2. (/4 " 2
(/6 " 2. 2, (/6 " 2
(/4 " 2. 3 " 2
.
5
.
Note: ! ,
/ 26 2 5-7 # ,
. ( , $," " 2 1
21#%/ .
3 :
1. / () 5-7 39
2. / () 5-7 39
3. 5 40
38
Configuring
Preinitialize from the source (first) VNX

Step
Action
1.
Log in to the source VNX (cs100_src) as nasadmin.
2.
Preinitialize the connection from the source (first) VNX to the destination (second) VNX in a VNX/Symmetrix
configuration for SRDF/A by using this command syntax:
$ nas_cel -create <cel_name> -ip <ip> -passphrase <passphrase>
where:
<cel_name> = name of the destination VNX
<ip> = IP address of the destination Control Station in slot 0
<passphrase> = 615 character password
Example:
To preinitialize the connection from cs100_src to cs110_dst with IP address 192.168.97.141 and passphrase
nasadmin, type:
$ nas_cel -create cs110_dst -ip 192.168.97.141 -passphrase nasadmin
Output:
operation in progress (not interruptible)...
id = 1
name = cs110_dst
owner = 0
device =
channel =
net_path = 192.168.97.141
celerra_id = 0001901005570354
passphrase = nasadmin
3.
Exit by typing:
$ exit
Output:
exit
Preinitialize from the destination (second) VNX

Step
Action
1.
Log in to the destination VNX (cs100_dst) as nasadmin.
Preinitialize the configuration
39
Configuring
Step
Action
2.
Preinitialize the connection from the destination (second) VNX to the source (first) VNX in a VNX/Symmetrix
configuration for SRDF/A by using this command syntax:
$ nas_cel -create <cel_name> -ip <ip> -passphrase <passphrase>
where:
<cel_name> = name of the source VNX
<ip> = IP address of the remote Control Station in slot 0
<passphrase> = 615 character password
Example:
To preinitialize the connection from cs110_dst to cs100_src with IP address 192.168.97.140 and passphrase
nasadmin, type:
$ nas_cel -create cs100_src -ip 192.168.97.140 -passphrase nasadmin
id = 0
name = cs100_src
owner = 0
device =
channel =
net_path = 192.168.97.140
celerra_id = 000190100582034D
passphrase = nasadmin
3.
Exit by typing:
$ exit
Output:
exit
Verify the preinitialization

Step
Action
1.
2.
Verify preinitialization of cs100_src and cs110_dst by typing:

$ nas_cel -list
Output:
id name
owner mount_dev channel net_path
CMU
0 cs100_src 0
192.168.97.140 000190100582034D
1 cs110_dst 0
192.168.97.141 0001901005570354
40
Configuring
Note:
3 0 .
8 _ - ( _ -). 8 _
, , , .
Initialize the configuration (active/passive)

( / 5-7
() .
Prerequisites
5-7 5-7 .
21#%/
3 2 27
2 5-7 # ,
.
21#%/ . 8 $," " 2

1 .
5-7 .
3 / :
( 5-7 41
( 5-7 45
5 21#%/
5-7 (/) 49
Initialize the source VNX

( / , 5-7 ( ) .
Step
Action
1.
41
Configuring
Step
Action
2.
Verify the slots on the source VNX by typing:

# /nas/sbin/getreason
Output:
10
5
5
5
5
3.
slot_0
slot_2
slot_3
slot_4
slot_5
primary control station

contacted
contacted
contacted
contacted
List the Data Movers (servers) on the source VNX by typing:

# /nas/bin/nas_server -list
Output:
id
1
2
3
4
4.
type
1
4
1
4
acl
1000
1000
1000
1000
slot groupID state

2
0
3
0
4
0
5
0
name
server_2
server_3
server_4
server_5
Get detailed information about the Data Movers on the source VNX by typing:
# nas_server -info -all
Output:
id
= 1
name
= server_2
acl
= 1000, owner=nasadmin, ID=201
type
= nas
slot
= 2
member_of =
standby
= server_3, policy=auto
status
:
defined = enabled
actual
= online, active
id
=
name
=
acl
=
type
=
slot
=
member_of =
standbyfor=
status
:
defined =
actual
=
42
2
server_3
1000, owner=nasadmin, ID=201
standby
3
server_2
enabled
online, ready
Configuring
Step
Action
id
name
acl
type
slot
member_of
standby
status
defined
actual
=
=
=
=
=
=
=
:
=
=
id
=
name
=
acl
=
type
=
slot
=
member_of =
standbyfor=
status
:
defined =
actual
=
5.
3
server_4
nas
4
server_5, policy=auto
enabled
online, ready
4
server_5
standby
5
server_4
enabled
online, ready
Switch (su) to root by typing:

$ su
Output:
Password:
6.
Start the active/passive SRDF/A initialization process on the source VNX by typing:
# /nas/sbin/nas_rdf -init
Output:
Discover local storage devices ...
Discovering storage (may take several minutes)
done
Start R2 dos client...
done
Start R2 nas client...
done
Contact cs110_dst... is alive
43
Configuring
Step
Action
7.
At the prompt, assign the remote standby Data Mover on the destination VNX for each source (primary) Data
Mover on the source VNX. For each source Data Mover on cs100_src, type the slot number of its corresponding
standby on cs110_dst.
Note: The actual standby designation occurs later in the procedure.To determine which Data Movers to designate
as standbys, see VNX Data Mover configuration checklist on page 29. Data Movers are referred to as servers,
and named server_n, starting with server_2. In the example, server_2 (source Data Mover) and server_3 (local
standby Data Mover) have remote SRDF/A standby Data Movers, that is, local server_2, slot 2, fails over to the
remote server in slot 2, and local server_3, slot 3, fails over to the remote server in slot 3. Also, server_4 and
server_5 are local Data Movers not protected by SRDF (not configured with SRDF/A standby Data Movers).
Example:
Please create an rdf standby for each server listed
server server_2 in slot 2, remote standby in slot [2] (or none): 2
server_2 : done
id
= 1
name
= server_2
acl
type
= nas
slot
= 2
member_of =
standby
RDFstandby= slot=2
status
:
defined = enabled
actual
= online, active
server_3 : done
id
= 2
name
= server_3
acl
type
= standby
slot
= 3
member_of =
standbyfor= server_2
RDFstandby= slot=3
status
:
defined = enabled
actual
= online, ready
server server_4 in slot 4, remote standby in slot [4] (or none):
none
none
The slot [ 2 3 ] on the remote cs110_dst system must be an rdf
standby Data Mover(s). Currently, the slot [ 2 3 ] is not configured
as an rdf standby Data Mover(s). Please run the nas_rdf -init
command on the remote cs110_dst system.
44
Configuring
Initialize the destination VNX

Step
Action
1.
2.
Verify the slots on the destination VNX by typing:

# /nas/sbin/getreason
Output:
10 - slot_0 primary control station
5 - slot_2 contacted
3.
List the Data Movers (servers) on the destination VNX by typing:

# /nas/bin/nas_server -list
Output:
id
1
2
3
4
type acl
1 1000 2
1 1000 3
1 1000 4
4 1000 5
slot groupID state

0
0
0
0
name
server_2
server_3
server_4
server_5
Note: The output indicates that server_2 and server_3 are free to be configured as SRDF/A standbys for the
source VNX (cs100_src), because they are not local standbys.
4.
Get detailed information about the destination Data Movers on the destination VNX by typing:
# nas_server -info -all
Output:
id
name
acl
type
slot
member_of
standby
status
defined
actual
=
=
=
=
=
=
=
:
=
=
1
server_2
nas
2
enabled
online, ready
45
Configuring
Step
Action
id
name
acl
type
slot
member_of
standby
status
defined
actual
=
=
=
=
=
=
=
:
=
=
id
name
acl
type
slot
member_of
standby
status
defined
actual
=
=
=
=
=
=
=
:
=
=
id
=
name
=
acl
=
type
=
slot
=
member_of =
standbyfor=
status
:
defined =
actual =
5.
2
server_3
nas
3
enabled
online, ready
3
server_4
nas
4
enabled
online, ready
4
server_5
standby
5
server_4
enabled
online, ready

$ su
Output:
Password:
6.
Initialize the destination VNX for active/passive SRDF/A by typing:

# /nas/sbin/nas_rdf -init
Output:
done
Start R2 dos client...
done
Start R2 nas client...
done
Contact cs100_src ... is alive
46
Configuring
Step
Action
7.
At the prompt, create the RDF administrative account (rdfadmin) on the Control Station.
Note: Use the rdfadmin account to manage the destination SRDF/A standby Data Movers on cs110_dst that
provide the failover capability for cs100_src. The RDF site passphrase must consist of 615 characters, and
be the same for the source and destination VNX systems.
Example:
Please create a new login account to manage RDF site cs100_src
New login: rdfadmin
New password:
BAD PASSWORD: it is based on a dictionary word
Retype new password:
Changing password for user rdfadmin
passwd: all authentication tokens updated successfully
done
id = 1
name = cs100_src
owner = 500
device = /dev/ndj1
channel = rdev=/dev/ndg, off_MB=391; wdev=/dev/nda, off_MB=391
net_path = 192.168.97.140
celerra_id = 000190100582034D
passphrase = rdfadmin
Discover remote storage devices ...done
The following servers have been detected on the system:
id type acl slot groupID state name
1 1
1000 2
0
server_2
2 1
1000 3
0
server_3
3 1
1000 4
0
server_4
4 4
1000 5
0
server_5
Note: The IDs of the Data Movers in the id column are used in the next step.
47
Configuring
Step
Action
8.
At the prompt, designate the Data Movers on the destination VNX as SRDF/A standby Data Movers for the
source VNX. To designate the standby Data Movers, type the ID number (not the slot number) of a single Data
Mover or ID numbers for multiple servers, separated by spaces.
Note: For failover capability, each standby Data Mover previously assigned to a source (primary) Data Mover
on cs100_src must be designated as a standby on cs110_dst. Review the Data Mover list created in VNX Data
Mover configuration checklist on page 29 to determine which servers to designate as standbys. Ensure that
you review the checklist if you have an NS series gateway configuration with two Data Movers, and a default
local standby Data Mover. During the source VNX initialization process, the term "slots" identifies the remote
SRDF/A standby Data Mover. During the destination VNX initialization process, the term "server_ids" identifies
the SRDF/A standby Data Mover.
CAUTION: Before you set up an SRDF standby Data Mover at the destination site, check the Data
Mover configurations at the source and destination sites. Verify that the SRDF standby Data Mover is
in the appropriate slot. Verify that the hardware, including network interface adapters, is the same for
the source and SRDF standby Data Movers for failover purposes. Also, ensure that the destination
Data Movers do not have any local standbys defined, as provided in the default installation, for example,
server_5 is, by default, a standby for server_2, server_3, and server_4.
Example:
Please enter the id(s) of the server(s) you wish to reserve
(separated by spaces) or "none" for no servers.
Select server(s) to use as standby: 1 2
id = 1
name = server_2
acl = 2000, owner=rdfadmin, ID=500
type = standby
slot = 2
member_of =
standbyfor=
status :
defined = enabled
actual = boot_level=0
id = 2
name = server_3
acl = 2000, owner=rdfadmin, ID=500
type = standby
slot = 3
member_of =
standbyfor=
status :
defined = enabled
actual = boot_level=0
48
Configuring
Step
Action
id = 1
name = cs100_src
owner = 500
device = /dev/ndj1
channel = rdev=/dev/ndg, off_MB=391; wdev=/dev/nda, off_MB=391
net_path = 192.168.97.140
celerra_id = 000190100582034D
Please create a rdf standby for each server listed
none
none
Note: If you use the nas_server -list command to list the available Data Movers on the destination VNX
(cs110_dst), only server_4 and server_5 appear. Data Movers server_2 and server_3 are unavailable to the
nasadmin account because they are now managed by the rdfadmin account.
9.
Exit root by typing:

# exit
Output:
exit
Note: The initialization process is complete and the active/passive configuration is established. The destination
VNX is ready to provide full file system access and functionality if a source site failure occurs.
Important: ( (/ " 2 ,
///_ - . ( (/
,
// .
Verify SRDF/A on the source VNX (active/passive)

, 5-7 "+( , 2 $ 2
"+( (28,"+() , 21#%/ 5-7.
Step
Action
1.
49
Configuring
Step
Action
2.
List the file systems on the source VNX by typing:

$ nas_fs -list
Output
id
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
31
32
35
50
inuse
n
y
y
y
y
n
n
n
n
n
n
n
n
n
n
y
n
n
n
n
n
n
y
n
n
n
n
n
n
y
y
y
type
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
5
5
5
5
5
1
1
1
1
1
1
5
1
1
1
1
acl
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
volume
74
76
78
80
82
84
86
88
90
92
94
96
98
100
102
104
137
140
141
142
143
156
157
161
162
163
164
165
229
233
234
292
name
root_fs_1
root_fs_2
root_fs_3
root_fs_4
root_fs_5
root_fs_6
root_fs_7
root_fs_8
root_fs_9
root_fs_10
root_fs_11
root_fs_12
root_fs_13
root_fs_14
root_fs_15
root_fs_common
root_fs_ufslog
root_fs_d3
root_fs_d4
root_fs_d5
root_fs_d6
fs1
fs2
fs8k
fs32k
fs64k
ufs1
root_panic_reserve
ufs1_snap1
fs1a
fst1
fs5
server
1
2
3
4
2,1,3
1
1
3
Configuring
Step
Action
3.
List the device groups on the source VNX by typing:

$
/nas/symcli/bin/symdg list
Output
D E V I C E G R O U P S
Name
1R1_3
1REG
Number of
Type
Valid Symmetrix ID Devs GKs BCVs VDEVs TGTs
RDF1
Yes
000190100582 70
0
0
0
0
REGULAR Yes
000190100582 48
0
64
0
0
Note:
( , : 111_3
21#%/ - 11 11$& (-21#%/ )
. 3 .
4 2 $ 2 28,"+( 5-7
; 2 $ 2 28,"+(
" 2 , , $," "". 3 2 $ 2 21#% $," .
2 .
4.
View key SRDF/A information for the device group representing the R1 data volumes (for example, 1R1_3) by
typing:
$ /nas/symcli/bin/symrdf -g 1R1_3 query -rdfa
Note: Ensure that you provide the appropriate device group name with the command. Information you can
monitor is highlighted in the output. Also, the output uses ... ? to indicate a continuation of the device entries;
not all entries are listed.
Output
Device Group (DG) Name
: 1R1_3
DG's Type
: RDF1
DG's Symmetrix ID
: 000190100582
RDFA Session Number
: 2
RDFA Cycle Number
: 139
RDFA Session Status
: Active
RDFA Minimum Cycle Time
: 00:00:30
RDFA Avg Cycle Time
: 00:00:30
Duration of Last cycle
: 00:00:30
RDFA Session Priority
: 33
Tracks not Committed to the R2 Side: 36
Time that R2 is behind R1
: 00:00:36
RDFA R1 Side Percent Cache In Use : 0
RDFA R2 Side Percent Cache In Use : 0
Transmit Idle Time
: 00:00:00
Source (R1) View
Target (R2) View
MODES
51
Configuring
Step
Action
---------------------------------------------ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv R2 Inv K
T R1 Inv R2 Inv
Device Dev E Tracks Tracks S Dev E Tracks Tracks
--------------------------- -- ------------------d1
034D RW
0
0
RW 034D WD
0
0
d2
034E RW
0
0
RW 034E WD
0
0
d3
034F RW
0
0
RW 034F WD
0
0
d4
0350 RW
0
0
RW 0350 WD
0
0
d5
0351 RW
0
0
RW 0351 WD
0
0
d6
0352 RW
0
0
RW 0352 WD
0
0
d7
035A RW
0
0
RW 035A WD
0
0
d8
035B RW
0
0
RW 035B WD
0
0
d9
035C RW
0
0
RW 035C WD
0
0
d10
035D RW
0
0
RW 035D WD
0
0
...
d138 0397 RW
0
0
RW 0397 WD
0
0
d139 0398 RW
0
0
RW 0398 WD
0
0
d140 0399 RW
0
0
RW 0399 WD
0
0
Total
-------- ----Track(s)
0
0
MB(s)
0.0
0.0
Legend for MODES:
M(ode of Operation):
Copy
D(omino)
:
A(daptive Copy)
:
C(onsistency State):
---- --------
MDAC
---A...
A...
A...
A...
A...
A...
A...
A...
A...
A...
RDF Pair
STATE
--------Consistent
Consistent
Consistent
Consistent
Consistent
Consistent
Consistent
Consistent
Consistent
Consistent
A... Consistent
A... Consistent
A... Consistent
------ -----0
0
0.0
0.0
A = Async, S = Sync, E = Semi-sync, C = Adaptive

X = Enabled, . = Disabled
D = Disk Mode, W = WP Mode, . = ACp off
X = Enabled, . = Disabled, - = N/A
Note: Check the session status, average cycle time, tracks not committed to R2, time R2 is behind R1 (in seconds), as well as the mode (A for asynchronous) and RDF pair state (Consistent).
Activate a failover (active/passive)

5-7 ()
/ 21#%/ .
Prerequisites
8 () ,
,
.
( , 5-7
2 , 5-7.
1 ,
///_ - 5-7.
52
Configuring
3 / 21#%/
1. / 53
2.
5-7 55
3. 5 21#%/
59
4. $ 65
CAUTION: % " 2, 21#%
///_ -, -, -
" 2 0 ("20). $ "21
- - . 6 "21 ,
/// . 3
0 - _1 .
Prepare for a graceful failover

Step
Action
1.
Log in to the source VNX (cs100_src) as nasadmin and switch (su) to root.
2.
Halt all Data Movers and restart the source Control Station (CS0) for the source VNX by typing:
# /nas/sbin/nas_halt now
Output:
************************** WARNING! ****************************
You are about to HALT this Celerra including all of its Control
Stations and Data Movers.
DATA will be UNAVAILABLE when the system is halted.
Note that this command does *not* halt the storage array.
Note: As an alternative to nas_halt, you can run server_cpu ALL -halt now &, to halt all the Data Movers.
However, this requires an explicit restart of the source Control Station (CS0) with -reboot -f -n. For an NS600,
server_cpu is the recommended command.
53
Configuring
Step
Action
3.
At the prompt, confirm the halting by typing:

yes
Example:
ARE YOU SURE YOU WANT TO CONTINUE? [ yes or no ] : yes
Sending the halt signal to the Master Control Daemon...: Done
Feb 7 18:39:35 cs100_src EMCServer: nas_mcd: Check and halt other
CS...: Done
Feb 7 18:40:00 cs100_src get_datamover_status: Data Mover server_2:
COMMAND doesnt match.
Feb 7 18:40:12 cs100_src setup_enclosure: Executing -dhcpd stop option
Feb 7 18:40:12 cs100_src snmptrapd[4743]: Stopping snmptrapd
Feb 7 18:40:12 cs100_src EV_AGENT[7847]: Signal TERM received
Feb 7 18:40:12 cs100_src EV_AGENT[7847]: Agent is going down
Feb 7 18:40:24 cs100_src DHCPDMON: Starting DHCPD on CS 0
Feb 7 18:40:26 cs100_src setup_enclosure: Executing -dhcpd start
option
Feb 7 18:40:26 cs100_src dhcpd: Internet Software Consortium DHCP
Server V3.0pl1
Feb 7 18:40:26 cs100_src dhcpd: Copyright 1995-2001 Internet Software
Consortium.
Feb 7 18:40:26 cs100_src dhcpd: All rights reserved.
Feb 7 18:40:26 cs100_src dhcpd: For info, please visit
http://www.isc.org/products/DHCP
Feb 7 18:40:26 cs100_src dhcpd: Wrote 0 deleted host decls to leases
file.
Feb 7 18:40:26 cs100_src dhcpd: Wrote 0 new dynamic host decls to
leases file.
Feb 7 18:40:26 cs100_src dhcpd: Wrote 0 leases to leases file.
Feb 7 18:40:26 cs100_src dhcpd: Listening on
LPF/eth2/00:00:f0:9c:1f:d5/128.221.253.0/24
Feb 7 18:40:26 cs100_src dhcpd: Sending on
LPF/eth2/00:00:f0:9c:1f:d5/128.221.253.0/24
Feb 7 18:40:26 cs100_src dhcpd: Listening on
LPF/eth0/00:00:f0:9d:00:e2/128.221.252.0/24
Feb 7 18:40:26 cs100_src dhcpd: Sending on
LPF/eth0/00:00:f0:9d:00:e2/128.221.252.0/24
Feb 7 18:40:26 cs100_src dhcpd: Sending on Socket/fallback/fallbacknet
Feb 7 18:40:40 cs100_src mcd_helper: : Failed to umount /nas (0)
Feb 7 18:40:40 cs100_src EMCServer: nas_mcd: Failed to gracefully
shutdown MCD and halt
servers. Forcing halt and reboot...
Feb 7 18:40:40 cs100_src EMCServer: nas_mcd: Halting all servers...
54
Configuring
Activate a failover from the destination VNX

Note: ( 2 #,7 ,
$," " 2 1 .
Step
Action
1.

Note: The activation must always be performed from the destination VNX.
2.
List the device groups on the destination VNX by typing:

$ /nas/symcli/bin/symdg list
Output:
D E V I C E G R O U P S
Name
1R1_4
1REG
1R2_500_3
Type
RDF1
REGULAR
RDF2
Valid
Yes
Yes
Yes
Symmetrix ID
000190100557
000190100557
000190100557
Number of
Devs GKs BCVs VDEVs TGTs
6
0
0
0
0
0
0
62
0
0
70
0
0
0
0
Note: In the sample cs110_dst configuration, these device groups represent the following: 1R1_4 represents
the R1 volumes of the destination Control Station, 1REG represents the local (non-SRDF/A) volumes, and
1R2_500_3 represents the R2 data volumes. The device groups in the configuration might have different names.
These steps apply to both types of failover scenarios (graceful or disaster recovery). However, the sample output
is based on a graceful failover activation.
3.
Query the destinations SRDF/A information for the device group representing the R2 data volumes (on cs110_dst,
1R2_500_3) by typing:
$ /nas/symcli/bin/symrdf -g 1R2_500_3 query -rdfa
Note: The output uses ... ? to indicate a continuation of the device entries; not all device entries are listed.
Output:
Device Group (DG) Name
DG's Type
DG's Symmetrix ID
RDFA Session Number
RDFA Cycle Number
:
:
:
:
:
1R2_500_3
RDF2
000190100557
2
41
55
Configuring
Step
Action
RDFA Session Status
RDFA Minimum Cycle Time
RDFA Avg Cycle Time
Tracks not Committed to the R2 Side
Time that R2 is behind R1
RDFA R1 Side Percent Cache In Use
RDFA R2 Side Percent Cache In Use
Transmit Idle Time
:
:
:
:
:
:
:
:
:
:
Active
00:00:30
00:00:30
00:00:30
33
1276
00:00:32
0
0
00:00:00
Target (R2) View

Source (R1) View
MODES
--------------------------------------------- ---- -------ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv R2 Inv K
T R1 Inv R2 Inv
RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAC STATE
-------------------------------- -- -------------- ---- -------DEV001 034D WD
0
0 RW 034D RW
0
0 A... Consistent
DEV002 034E WD
0
0 RW 034E RW
0
0 A... Consistent
DEV003 034F WD
0
0 RW 034F RW
0
0 A... Consistent
DEV004 0350 WD
0
0 RW 0350 RW
0
0 A... Consistent
DEV005 0351 WD
0
0 RW 0351 RW
0
0 A... Consistent
DEV006 0352 WD
0
0 RW 0352 RW
0
0 A... Consistent
DEV007 035A WD
0
0 RW 035A RW
0
0 A... Consistent
DEV008 035B WD
0
0 RW 035B RW
0
0 A... Consistent
DEV009 035C WD
0
0 RW 035C RW
0
0 A... Consistent
DEV010 035D WD
0
0 RW 035D RW
0
0 A... Consistent
...
DEV067 0396 WD
0
0 RW 0396 RW
0
0 A... Consistent
DEV068 0397 WD
0
0 RW 0397 RW
0
0 A... Consistent
DEV069 0398 WD
0
0 RW 0398 RW
0
0 A... Consistent
DEV070 0399 WD
0
0 RW 0399 RW
0
0 A... Consistent
Total
-------- -------- -------- -------Track(s)
0
0
0
0
MB(s)
0.0
0.0
0.0
0.0
Legend for MODES:
M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive
Copy
D(omino)
: X = Enabled, . = Disabled
A(daptive Copy)
: D = Disk Mode, W = WP Mode, . = ACp off
C(onsistency State): X = Enabled, . = Disabled, - = N/A
Note: The output uses ... ? to indicate a continuation of the device entries; not all device entries are listed.
4.
Switch (su) to rdfadmin by typing:

$ su - rdfadmin
Output:
Password:
56
Configuring
Step
Action
5.

$ su
Output:
Password:
6.
Activate the failover by typing:

# /nas/sbin/nas_rdf -activate
CAUTION: For sites with redundant Control Stations, the /nas/sbin/nas_rdf -activate command must be
run from the primary Control Station located in slot 0 (CS0). Ensure that CS1 is powered off at both sites
before you run the nas_rdf -activate command, and CS1 remains powered off for the duration of the
activate and subsequent restore operations.
Note: Ensure that all Data Movers at the source are halted before proceeding. At the destination, do not shut
down or restart any Data Movers, that is, SRDF-protected or non-SRDF Data Movers, while the nas_rdf -activate
or nas_rdf - restore command is running. This might interrupt the communication of VNX with the backend and
cause the command to fail.
7.
At the prompt, if this is a true disaster scenario, ensure that you have powered off the source VNX:
Is remote site cs100_src completely shut down (power OFF)?
Note: This prompt serves as a reminder to shut down the source site in a disaster scenario. If you are performing
a graceful failover for testing purposes, the source VNX can remain powered on.
8.
At the next prompt, confirm the SRDF/A activation by typing:

yes
Example:
Do you wish to continue [yes or no]: yes
Successfully pinged (Remotely) Symmetrix ID: 000190100582
Note: The ping success message appears if the Symmetrix DMX system attached to the source VNX is successfully contacted, indicating it is operational and ready on the SRDF/A link. Activating the destination VNX
write-enables the destination volumes and write-disables the source volumes, as long as SRDF/A and the source
Symmetrix system are operational.
57
Configuring
Step
Action
An RDF 'Failover' operation execution is in progress for device group
'1R2_500_3'.
Please wait...
Write Disable device(s) on SA at source (R1)..............Done.
Suspend RDF link(s).......................................Started.
Suspend RDF link(s).......................................Done.
Read/Write Enable device(s) on RA at target (R2)..........Done.
The RDF 'Failover' operation successfully executed for device group
'1R2_500_3'.
Note: A file system check is executed on the R2 control volumes of the sources Control Station file systems.
Waiting for nbs clients to die ... done
/net/500 /etc/auto.500 -t 1,ro
/dev/ndj1: recovering journal
/dev/ndj1: clean, 11591/231360 files, 204230/461860 blocks
fsck 1.26 (3-Feb-2002)
id
type
acl
slot groupID state name
1
1
1000
2
0
server_2
2
4
1000
3
0
server_3
3
1
1000
4
0
server_4
4
4
1000
5
0
server_5
Note: The SRDF/A standby Data Movers now become active.
server_2 :
server_2 : going offline
rdf : going active
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
done
server_3 :
rdf : going active
done
server_4 :
Error 4003: server_4 : standby is not configured
server_5 :
58
Configuring
Step
Action
9.

# exit
exit
Note: The failover is complete.
Note: ( 2 #,7 ,
$," " 2 1 .
Verify SRDF/A after failover activation

Step
Action
1.
Log in to the destination VNX (cs110_dst) as rdfadmin.
2.
List the available Data Movers at the destination by typing:

$ /nas/bin/nas_server -list
1 1
0
2
0
server_2
2 4
0
3
0
server_3
Note:
3 # , (#, ,
( "+) , , (#, , # ,.
8 5-7 "+( , 28,"+( ,
21#%/ - 5-7.
59
Configuring
Step
Action
3.
List and manage the file systems mounted for the Data Movers now active at the destination by typing:
$ /nas/bin/server_mount ALL
server_2 :
root_fs_2 on / uxfs,perm,rw
root_fs_common on /.etc_common uxfs,perm,ro
fs2 on /fs2 uxfs,perm,rw
fs1a on /fs1a uxfs,perm,rw
fst1 on /fst1 uxfs,perm,rw
server_3 :
root_fs_3 on / uxfs,perm,rw,<unmounted>
root_fs_common on /.etc_common uxfs,perm,ro,<unmounted>
Note: The standby Data Movers activated at the destination acquire the IP and MAC addresses, file systems,
and export tables of their counterparts on the source and have read/write access to all the R2 volumes on the
destination.
4.
List interface configuration information for Data Mover server_2 by typing:

$ /nas/bin/server_ifconfig server_2 -all
Output:
server_2 :
cge1 protocol=IP device=cge1
inet=192.168.97.147 netmask=255.255.255.0 broadcast=192.168.97.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:9:32:71
loop protocol=IP device=loop
UP, loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhost
el31 protocol=IP device=mge1
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:5:5d:23 netname=localhost
el30 protocol=IP device=mge0
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:5:5d:24 netname=localhost
60
Configuring
Step
Action
5.
Display disk information after the failover activation by typing:

$ nas_disk -list
id
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
inuse
y
y
y
y
y
y
n
n
n
n
y
n
n
y
y
y
y
y
n
n
sizeMB
11619
11619
2077
2077
2077
31874
22999
22999
22999
22999
22999
22999
22999
22999
22999
22999
22999
22999
22999
22999
storageID-devID
000190300281-002C
000190300281-002D
000190300281-002E
000190300281-002F
000190300281-0030
000190300281-0031
000190300281-0083
000190300281-0084
000190300281-0085
000190300281-0086
000190300281-0087
000190300281-0088
000190300281-0089
000190300281-008A
000190300281-008B
000190300281-008C
000190300281-008D
000190300281-008E
000190300281-008F
000190300281-0090
type
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
name
root_disk
root_ldisk
d3
d4
d5
d6
d7
d8
d9
d10
d11
d12
d13
d14
d15
d16
d17
d18
d19
d20
servers
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
61
Configuring
Step
Action
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
6.
n
n
n
n
n
n
n
n
n
n
n
y
y
y
y
y
y
y
y
y
y
y
y
n
y
y
y
y
y
y
n
n
n
y
y
y
n
n
n
n
n
22999
22999
22999
22999
22999
22999
22999
22999
22999
22999
22999
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
61424
000190300281-0091
000190300281-0092
000190300281-0093
000190300281-0094
000190300281-0095
000190300281-0096
000190300281-00AB
000190300281-00AC
000190300281-00AD
000190300281-00AE
000190300281-00AF
000190300281-00B6
000190300281-00B7
000190300281-00B8
000190300281-00B9
000190300281-00BA
000190300281-00BB
000190300281-00BC
000190300281-00BD
000190300281-00BE
000190300281-00BF
000190300281-00C0
000190300281-00C1
000190300281-00C2
000190300281-00C3
000190300281-00C4
000190300281-00C5
000190300281-00C6
000190300281-00C7
000190300281-00C8
000190300281-00C9
000190300281-00CA
000190300281-00CB
000190300281-00CC
000190300281-00CD
000190300281-00CE
000190300281-00D4
000190300281-00D5
000190300281-00D6
000190300281-00D7
000190300281-00D8
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
1,2
Display information for the Data Movers and the file systems at the destination after the failover activation, including
the available disk space for all Data Movers or file systems and how much of the total capacity of a file system
has been used by typing:
$ /nas/bin/server_df ALL
62
STD d21
STD d22
STD d23
STD d24
STD d25
STD d26
BCV rootd27
BCV rootd28
BCV rootd29
BCV rootd30
BCV rootd31
ATA d32
ATA d33
ATA d34
ATA d35
ATA d36
ATA d37
ATA d38
ATA d39
ATA d40
ATA d41
ATA d42
ATA d43
ATA d44
ATA d45
ATA d46
BCVA rootd47
BCVA rootd48
BCVA rootd49
BCVA rootd50
BCVA rootd51
R1ATA d52
R1ATA d53
R1ATA d54
R1ATA d55
R1ATA d56
R1BCA rootd57
R1BCA rootd58
R1BCA rootd59
R1BCA rootd60
R1BCA rootd61
Configuring
Step
Action
Output:
[server_2 :
server_2 :
Filesystem
fst1
fs1a
fs2
root_fs_common
root_fs_2
kbytes
28798424
9224
460787024
13624
114592
used
avail
600
28797824
600
8624
600 460786424
5264
8360
776
113816
capacity
0%
7%
0%
39%
1%
Mounted on
/fst1
/fs1a
/fs2
/.etc_common
/
server_3 :
Error 2: server_3 : No such file or directory
no error message in response
7.
Query the key SRDF/A information now existing for the destination device group with the data volumes (on
cs110_dst, 1R2_500_3) by using this command syntax:
$ /nas/symcli/bin/symrdf -g <group> query -rdfa
Where:
<group> = name of the device group
Note: Use only Solutions Enabler Symmetrix SYMCLI informational commands on the VNX device group; do
not invoke any Solutions Enabler Symmetrix SYMCLI action commands using the Control Station host component,
laptop service processor, or EMC ControlCenter. The Solutions Enabler Symmetrix SRDF family documentation
on the EMC Online Support website provides more information.
Note: The session state is now Inactive, the mode is A for asynchronous, and the RDF pair state is now Failed
Over. Also note the output uses ... ? to indicate a continuation of the device entries, because not all device entries
are listed.
Example:
$ /nas/symcli/bin/symrdf -g 1R2_500_3 query -rdfa
Output:
Device Group (DG) Name : 1R2_500_3
DG's Type
: RDF2
DG's Symmetrix ID
: 000190100557
63
Configuring
Step
Action
RDFA Session Number
: 2
RDFA Cycle Number
: 0
RDFA Session Status
: Inactive RDFA Minimum Cycle
Time
: 00:00:30
RDFA Avg Cycle Time
: 00:00:00
:00:00:00
: 33
Tracks not Committed to the R2 Side: 0 Time
that R2 is behind R1
: 00:00:00
RDFA R1 Side Percent Cache In Use : 0 RDFA R2
Side Percent Cache In Use
: 0
Transmit Idle Time
: 00:00:00
Target (R2) View
Source (R1) View MODES
--------------------------------------------- ----ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv R2 Inv K
T R1 Inv R2 Inv
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAC
-------------------------- -- -------------------- ---DEV001 034D RW
20
0 NR 034D WD
0
0
A...
DEV002 034E RW 2048
0 NR 034E WD
0
0
A...
DEV003 034F RW
0
0 NR 034F WD
0
0
A...
DEV004 0350 RW
0
0 NR 0350 WD
0
0
A...
DEV005 0351 RW 1204
0 NR 0351 WD
0
0
A...
DEV006 0352 RW
0
0 NR 0352 WD
0
0
A...
DEV007 035A RW
0
0 NR 035A WD
0
0
A...
DEV008 035B RW
0
0 NR 035B WD
0
0
A...
DEV009 035C RW
0
0 NR 035C WD
0
0
A...
DEV010 035D RW
0
0 NR 035D WD
0
0
A...
...
DEV060 038F RW
0
0 NR 038F WD
0
0
A...
DEV061 0390 RW
0
0 NR 0390 WD
0
0
A...
DEV062 0391 RW
0
0 NR 0391 WD
0
0
A...
DEV063 0392 RW
0
0 NR 0392 WD
0
0
A...
DEV064 0393 RW
0
0 NR 0393 WD
0
0
A...
DEV065 0394 RW
2
0 NR 0394 WD
0
0
A...
DEV066 0395 RW
2
0 NR 0395 WD
0
0
A...
DEV067 0396 RW
0
0 NR 0396 WD
0
0
A...
DEV068 0397 RW
0
0 NR 0397 WD
0
0
A...
DEV069 0398 RW
0
0 NR 0398 WD
0
0
A...
DEV070 0399 RW
0
0 NR 0399 WD
0
0
A...
Total
------ ---------- ---Track(s)
3280
0
0
0
MB(s)
102.5
0.0
0.0 0.0
-------RDF Pair
STATE
-------Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed
Failed
Failed
Failed
Failed
Failed
Failed
Failed
Failed
Failed
Failed
Over
Over
Over
Over
Over
Over
Over
Over
Over
Over
Over
Legend for MODES:

Copy
D(omino)
A(daptive Copy)
C(onsistency State): X = Enabled, . = Disabled, - = N/A
64
Configuring
Ensure access after failover

( (/ ,
,
- 5-7,
- 5-7.
Note: 8 . (
,
///_ - . 3
. 1 5-7 65
.
Step
Action
1.
Halt CIFS.
2.
Set IP addresses and default routes.
3.
Adjust services such as WINs, DNS, NIS, and NTP.
4.
Restart CIFS.
Restore the source VNX

5-7 ,
$," " 2 1
2 #,7 .
3 5-7:
1. / 66
2. 1 66
CAUTION: % " 2, 21#%
_ -, -, - "
2 0 ("20). "21
- - . 6 "21 ,
/// . 3
0 - _1 . ! , "21
.
65
Configuring
Prepare for the restore

Note: / $," " 2 1.
Step
Action
1.
Verify proper SRDF/A operations by performing a complete system check of the Symmetrix system and SRDF/A.
CAUTION:
( , 5-7 (100_)
$," " 2
1. 8 $," " 2 1
2 5-7.
/ $," " 2 1.
2.
Power up the source VNX, ensuring that the source Control Station restarts, and perform a restart by typing:
# reboot -f -n
Note: You can now perform the restore from the destination VNX.
Restore from the destination

3 :
66
3 -
5-7 2 2
. 3
.
3 - , 20 ,

2 .
Step
Action
1.
Log in to the destination VNX (cs110_dst) as rdfadmin and switch (su) to root.
Configuring
Step
Action
2.
Start the restore of the source VNX by typing:

# /nas/sbin/nas_rdf -restore
CAUTION:
% " 2, _ -
" 2 0 ("20).
"21 - . 6
"21 , ///
. 3 0 - _1 .
! , "21
.
# # , (21#%- -21#% #
,) _ - . 3
5-7 .
/ $," " 2 1
2 #,7 21#%/ .
3.
At the prompt, to continue restoration and begin the device-group update phase, type:
yes
Example:
Is remote site cs100_src ready for Storage restoration?
4.
At the next prompt, to continue the restore process, type:

yes
Example:
Restore will now reboot the source side control station.
Do you wish to continue? [yes or no]: yes
CAUTION: The source Symmetrix system must be operational and all volumes must be ready on the
link.
Note: The system verifies that the Symmetrix devices are in proper condition to be restored at the source site.
Note that the output uses ... ? to indicate a continuation of the device entries, because not all device entries are
listed.
DG's Type : RDF2
DG's Symmetrix ID : 000190100557
67
Configuring
Step
Action
Target (R2) View
----------------------------ST
LI
Standard
A
N
Logical
T R1 Inv R2 Inv K
Device Dev E Tracks Tracks S
----------------------------DEV001 034D RW
20
0 NR
DEV002 034E RW 2048
0 NR
DEV003 034F RW
0
0 NR
DEV004 0350 RW
0
0 NR
DEV005 0351 RW 1204
0 NR
DEV006 0352 RW
0
0 NR
DEV007 035A RW
0
0 NR
DEV008 035B RW
0
0 NR
DEV009 035C RW
0
0 NR
DEV010 035D RW
0
0 NR
DEV011 035E RW
0
0 NR
DEV012 035F RW
0
0 NR
...
DEV065 0394 RW
2
0 NR
DEV066 0395 RW
2
0 NR
DEV067 0396 RW
0
0 NR
DEV068 0397 RW
0
0 NR
DEV069 0398 RW
0
0 NR
DEV070 0399 RW
0
0 NR
Source (R1) View MODES

------------------ --- -------ST
A
T R1 Inv R2 Inv
RDF Pair
Dev E Tracks Tracks MDA STATE
-- ----------------- --- -------034D WD
0
0 A.. Failed Over
034E WD
0
0 A.. Failed Over
034F WD
0
0 A.. Failed Over
0350 WD
0
0 A.. Failed Over
0351 WD
0
0 A.. Failed Over
0352 WD
0
0 A.. Failed Over
035A WD
0
0 A.. Failed Over
035B WD
0
0 A.. Failed Over
035C WD
0
0 A.. Failed Over
035D WD
0
0 A.. Failed Over
035E WD
0
0 A.. Failed Over
035F WD
0
0 A.. Failed Over
0394
0395
0396
0397
0398
0399
WD
WD
WD
WD
WD
WD
0
0
0
0
0
0
0
0
0
0
0
0
A..
A..
A..
A..
A..
A..
Failed
Failed
Failed
Failed
Failed
Failed
Over
Over
Over
Over
Over
Over
Total
------ ------------ -----Track(s)
3280
0
0
0
MB(s)
102.5
0.0
0.0
0.0
Legend for MODES:
Copy
D(omino)
A(daptive Copy)
Note:
3 2
21#% 28-" () .
3
. 4 , ,
. ( , " 4
. ( , $," " 2
1.
68
Configuring
Step
Action
+++++ Setting RDF group 1R2_500_3 to SYNC mode.
An RDF 'Update R1' operation execution is in progress for device
group '1R2_500_3'. Please wait...
Merge device track tables between source and target.......Started.
Devices: 036B-037C in (0557,03).......................... Merged.
Devices: 034D-0352, 035A-036A in (0557,03)............... Merged.
Devices: 037D-038E in (0557,03).......................... Merged.
Devices: 038F-0399 in (0557,03).......................... Merged.
Merge device track tables between source and target.......Done.
Resume RDF link(s)........................................Started.
Resume RDF link(s)........................................Done.
The RDF 'Update R1' operation successfully initiated for device group
'1R2_500_3'.
Note: The device-group update phase is now complete. The next step begins the device-group failback phase.
5.
At the next prompt, to begin the network restoration phase, type:

yes
Note: Ensure that the source CS0 is operational and on the data network.
Example:
Is remote site cs100_src ready for Network restoration?
Note: The SRDF/A standby Data Movers are halted and the destination file systems and shares become unavailable to network clients while the Symmetrix DMX systems (source and destination) fully synchronize.
server_2 : done
server_3 : done
server_4 :
server_5 :
fsck 1.26 (3-Feb-2002)
/net/500 /etc/auto.500 -t 0,rw,sync
Waiting for 1R2_500_3 access ...done
Note: The R2 devices on the destination are set to read-only while the Symmetrix systems fully synchronize.
Note: The failback operation now occurs.
69
Configuring
Step
Action
An RDF 'Failback' operation execution is in progress for device group
'1R2_500_3'.
Please wait...
Write Disable device(s) on RA at target (R2)..............Done.
Devices: 036B-037C in (0557,03).......................... Merged.
Devices: 034D-0352, 035A-036A in (0557,03)............... Merged.
Devices: 038F-0399 in (0557,03).......................... Merged.
Devices: 037D-038E in (0557,03).......................... Merged.
Read/Write Enable device(s) on SA at source (R1)..........Done.
The RDF 'Failback' operation successfully executed for device group
'1R2_500_3'.
Waiting for 1R2_500_3 sync ....done
Note: The device-group failback phase is complete.
6.
At the prompt, set the device group to run in SRDF/A mode by typing:
yes
Example:
Starting restore on remote site cs100_src ...
Waiting for nbs clients to start ... done
server_2 :
server_2 : going standby
rdf : going active
done
server_3 :
rdf : going active
done
70
Configuring
Step
Action
server_4 :
server_5 :
If the RDF device groups were setup to operate in ASYNCHRONOUS (
SRDF/A ) mode, now would
be a good time to set it back to that mode.
Would you like to set device group 1R2_500_3 to ASYNC Mode ? [yes
or no]: yes
An RDF Set 'Asynchronous Mode' operation execution is in progress
for device group
'1R2_500_3'. Please wait...
The RDF Set 'Asynchronous Mode' operation successfully executed for
device group
'1R2_500_3'.
Starting Services on remote site cs100_src ...done
7.

# exit
Output:
exit
8.
Exit rdfadmin by typing:

$ exit
Output:
logout
Note: The restoration is complete.
Note: , 5-7 (100_),

. " 4
,
5-7. ( , $," " 2 1.
71
Configuring
72
4
Troubleshooting

, $,"
. 3,

. % --
, .
(
, $," " 2 1.
/ 1 1 5-7
$," . 2 .
3 :
$," $-+ ( - 74
* 74
$ 94
$," 3 / 2 95
73
Troubleshooting
EMC E-Lab Interoperability Navigator

3 $," $-+ ( - , -
$," . (
://2.$,".. $," . 2 ,
2 / , Tools, E-Lab Interoperability Navigator.
Known problems and limitations

3 :
1 74
1 75
1 80
1 83
1 # , 91
' 94
Retrieve information from log files

-, . 3
:
" (_) _
" (_.)
3 21#%/
4 ///__ , ,
, :
///_.
///_..
///_..
///_..*
///.*
3 .
74
Troubleshooting
3 _ , /
. , // .
3 , , :
# (*)
3 .
/ ,
+ -
Resolve initialization failures

3 #
, (_2 _3), 21#%/
# ,, # , (_5). 3
, , # , 21#%/
# ,.
3 :
$ 1 75
1 1 77
$ 2 78
Example 1 for initialization failure

[root@cs110_dst nasadmin]# /nas/sbin/nas_rdf -init

done
Start R2 dos client ...
done
Start R2 nas client ...
done
Please create a new login account to manage RDF site cs100_src
New login: rdfadmin
New password:
BAD PASSWORD: it is based on a dictionary word
Retype new password:
Changing password for user rdfadmin
passwd: all authentication tokens updated successfully
done
75
Troubleshooting

Please enter the passphrase for RDF site cs100_src:
Passphrase:
rdfadmin
Retype passphrase:
rdfadmin

id
= 1
name
= cs100_src
owner
= 500
device
= /dev/ndj1
channel
= rdev=/dev/ndg, off_MB=391; wdev=/dev/nda, off_MB=391
net_path
= 192.168.97.140
celerra_id = 000190100582034D
Discover remote storage devices ...done
The following servers have been detected on the system (cs110_dst):
id
type acl slot groupID state name
1
1
1000 2
0
server_2
2
1
1000 3
0
server_3
3
1
1000 4
0
server_4
4
4
1000 5
0
server_5
Please enter the id(s) of the server(s) you wish to reserve
(separated by spaces) or "none" for no servers.
Select server(s) to use as standby:1 2
server_2 : Error 4031: server_2 : server_2 has a standby
server: server_5
server_3 : Error 4031: server_3 : server_3 has a standby
server: server_5
id
= 1
name
= cs100_src
owner
= 500
device
= /dev/ndj1
channel
= rdev=/dev/ndg, off_MB=391; wdev=/dev/nda, off_MB=391
net_path
= 192.168.97.140
celerra_id = 000190100582034D
server server_2 in slot 2, remote standby in slot [2] (or none):none
76
Troubleshooting
Resolution for initialization failure example 1

Step
Action
1.
List and verify the servers by typing:

# nas_server -list
Output:
id
1
2
3
4
2.
type
1
1
1
4
acl
1000
1000
1000
1000
slot groupID state

2
0
3
0
4
0
5
0
name
server_2
server_3
server_4
server_5
Delete the local standby relationship by typing:

# server_standby server_2 -delete mover=server_5
Output:
server_2 : done
3.
Delete.....by typing:
[root@cs110_dst nasadmin]# /nas/sbin/getreason
Output:
4.
[root@cs110_dst nasadmin]# /nas/sbin/getreason
Output:
5.
Delete the.....by typing:

[root@cs110_dst nasadmin]# /nas/bin/nas_server -list
Output:
id
1
2
3
4
type
1
1
1
4
acl
1000
1000
1000
1000
slot groupID state

2
0
3
0
4
0
5
0
name
server_2
server_3
server_4
server_5
77
Troubleshooting
Step
Action
6.
[root@cs110_dst nasadmin]# /nas/bin/nas_server -info -all
Output:
id
name
acl
type
slot
member_of
standby
status
defined
actual
=
=
=
=
=
=
=
:
=
=
id
name
acl
type
slot
member_of
standby
status
defined
actual
=
=
=
=
=
=
=
:
=
=
id
name
acl
type
slot
member_of
standby
status
defined
actual
=
=
=
=
=
=
=
:
=
=
id
=
name
=
acl
=
type
=
slot
=
member_of =
standbyfor=
status
:
defined =
actual
=
1
server_2
nas
2
enabled
online, ready
2
server_3
nas
3
enabled
online, ready
3
server_4
nas
4
enabled
online, ready
4
server_5
standby
5
server_4
enabled
online, ready

3
# ,, 1#% . 3

.
78
Troubleshooting

[root@cs110_dst nasadmin]# /nas/sbin/nas_rdf -init

done
Error 3122: server_2 : filesystem is unreachable: rl64k
Server server_2 has local file system mounted.
Please unmount those file system in another window and try again.
Do you wish to continue? [yes or no]:
********************
$ nas_server -i server_2
id
= 1
name
= server_2
acl
type
= nas
slot
= 2
member_of =
standby
RDFstandby= slot=2
status
:
defined= enabled
actual = online, active
$ server_mount server_2 rl64k /rl64k
server_2 : done
Warning 17716815751: server_2 :has a standby server: rdf, filesystem:
rl64k is local, will not be able to failover
[nasadmin@cs100_src ~]$ server_df server_2
server_2 :
Filesystem
kbytes
used
avail
capacity
Mounted on
rl64k
230393504 124697440 105696064 54%
/rl64
mc1
230393504 45333944 185059560 20%
/mc1
mc2
460787024 327825496 132961528 71%
/mc2
mc1a_ckpt1
230393504 410408
229983096 0%
/mc1a_ckpt1
mc1a
230393504 410424
229983080 0%
/mc1a
rl32krdf
230393504 696
230392808 0%
/caddata/wdc1/32k
root_fs_common 13624
root_fs_2
231944
5288
6152
8336
225792
9%
3%
/.etc_common
/
79
Troubleshooting
Resolve activation failures

3
21#%- # ,. 3
.
3 :
$ 80
1 81
Example for activation failure

Example of activation failure
[root@cs110_dst rdfadmin]# /nas/sbin/nas_rdf -activate
Is remote site cs100_src completely shut down (power OFF)?

Successfully pinged (Remotely) Symmetrix ID: 000190100582
An RDF 'Failover' operation execution is in progress for device group
'1R2_500_3'.
Please wait...
Write Disable device(s) on SA at source (R1)..............Done.
Read/Write Enable device(s) on RA at target (R2)..........Done.
The RDF 'Failover' operation successfully executed for
device group '1R2_500_3'.
/net/500 /etc/auto.500 -t 1,ro
/dev/ndj1: recovering journal
fsck 1.26 (3-Feb-2002)
1 1
1000 2
0
server_2
2 4
1000 3
0
server_3
3 1
1000 4
0
server_4
4 4
1000 5
0
server_5
server_2 :
rdf : going active
replace in progress ...failed
80
Troubleshooting
Example of activation failure

replace_storage:
replace_volume: volume is unreachable
d141,d142,d143,d144,d145,d146,d147,d148
server_3 :
rdf : going active
done
server_4 :
server_5 :
An RDF 'Update R1' operation execution is in progress for device
'DEV001' in group '1R2_500_3'. Please wait...
Device: 034D in (0557,03)................................ Merged.
The RDF 'Update R1' operation successfully initiated for device
'DEV001' in group '1R2_500_3'.
Resolution for activation failure

Step
Action
1.
List and verify the servers by typing:

# nas_server -list
Output:
id
1
2
3
4
2.
type
1
4
1
4
acl
1000
0
1000
1000
slot groupID state

2
2
3
0
4
0
5
0
name
server_2.faulted.rdf
server_3
server_4
server_5
Unmount all non-SRDF (local) file systems from the Data Mover that failed to activate (in this case, server_2)
by typing:
[root@cs110_dst rdfadmin] # server_umount server_2.faulted.rdf - perm fs5
Output:
server_2.faulted.rdf : done
81
Troubleshooting
Step
Action
3.
Manually activate SRDF for the Data Mover that originally failed by typing:
[root@cs110_dst rdfadmin]# server_standby server_2.faulted.rdf - activate rdf
Output:
server_2.faulted.rdf :
server_2.faulted.rdf : going standby
rdf : going active
done
4.
Verify the configuration by typing:

[root@cs110_dst rdfadmin]# /nas/sbin/getreason
Output:
5.
[root@cs110_dst rdfadmin] # /nas/bin/nas_server -list
Output:
id
1
2
3
4
6.
type
1
4
1
4
acl
0
0
1000
1000
slot groupID state

2
0
3
0
4
0
5
0
name
server_2
server_3
server_4
server_5
[root@cs110_dst rdfadmin]# /nas/bin/server_mount ALL
Output:
server_2 :
fs2 on /fs2 uxfs,perm,rw
fs1a on /fs1a uxfs,perm,rw
fst1 on /fst1 uxfs,perm,rw
server_3 :
server_4 :
server_5 :
82
Troubleshooting
Resolve restore failures

3 .
Note: 3 - " 2 0 , 5-7
. 6 #
1 ///
. 3 , #1 ,
, - 1#%
. $ 94
.
3 :
$ 1 83
1 1 87
$ 2 (-2 ) 88
1 2 88
$ 3 ( ) 89
1 3 91
Example 1 for restoration failure

3 /
110_ _ - . 3
5-7,
.
Example 1 restore failure
[root@cs110_dst rdfadmin]# /nas/sbin/nas_rdf -restore

Contact cs100_src ...
Unable to contact node cs100_src at 192.168.96.58.
DG's Type
: RDF2
DG's Symmetrix ID
: 000187940255
83
Troubleshooting

Target (R2) View
Source (R1) View
-------------------------------- -----------------ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv R2 Inv K
T R1 Inv R2 Inv
Device Dev E Tracks Tracks S Dev E Tracks Tracks
-------------------------------- -- -------- ------DEV001 0000 RW 12
0 NR 0000 WD
0
0
DEV002 0001 RW 4096
0 NR 0001 WD
0
0
DEV003 000D RW 1
0 NR 000D WD
0
0
DEV004 000E RW 1
0 NR 000E WD
0
0
DEV005 000F RW 0
0 NR 000F WD
0
0
DEV006 0010 RW 0
0 NR 0010 WD
0
0
DEV007 0011 RW 0
0 NR 0011 WD
0
0
DEV008 0012 RW 0
0 NR 0012 WD
0
0
DEV009 0013 RW 0
0 NR 0013 WD
0
0
DEV010 0014 RW 0
0 NR 0014 WD
0
0
DEV011 0015 RW 1
0 NR 0015 WD
0
0
DEV012 0016 RW 1
0 NR 0016 WD
0
0
...
DEV161 02D3 RW 0
0 NR 0253 WD
0
0
DEV162 02D7 RW 0
0 NR 0257 WD
0
0
DEV163 0003 RW 0
0 NR 0003 WD
0
0
DEV164 0004 RW 851
0 NR 0004 WD
0
0
DEV165 0005 RW 0
0 NR 0005 WD
0
0
Total
-------- --------Track(s)
4965
0
MB(s)
155.2
0.0
MODES
---- --------
MDA
---A..
A..
A..
A..
A..
A..
A..
A..
A..
A..
A..
A..
RDF Pair
STATE
-------Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
Failed Over
A..
A..
A..
A..
A..
Failed
Failed
Failed
Failed
Failed
Over
Over
Over
Over
Over
------ -----0
0
0.0
0.0
Legend for MODES:

Copy
D(omino) : X = Enabled, . = Disabled
A(daptive Copy) : D = Disk Mode, W = WP Mode, . = ACp off
+++++ Setting RDF group 1R2_500_11 to SYNC mode.
An RDF 'Update R1' operation execution is in progress for device group
'1R2_500_11'.
Please wait...
Devices: 0000-0001 ...................................... Merged.
Devices: 0003-0005 ...................................... Merged.
Devices: 000D-0015 ...................................... Merged.
Devices: 0016-001E ...................................... Merged.
Devices: 001F-0027 ...................................... Merged.
84
Troubleshooting

Devices: 0028-0030 ...................................... Merged.
Devices: 0031-0039 ...................................... Merged.
Devices: 003A-0042 ...................................... Merged.
Devices: 0043-004B ...................................... Merged.
Devices: 004C-0054 ...................................... Merged.
Devices: 0055-005D ...................................... Merged.
Devices: 005E-0066 ...................................... Merged.
Devices: 0067-006F ...................................... Merged.
Devices: 0070-0078 ...................................... Merged.
Devices: 0079-0081 ...................................... Merged.
Devices: 0082-008A ...................................... Merged.
Devices: 008B-008C ...................................... Merged.
Devices: 01DB-01E1 ...................................... Merged.
Devices: 01E2-01E8 ...................................... Merged.
Devices: 01E9-01EF ...................................... Merged.
Devices: 01F0-01F6 ...................................... Merged.
Devices: 01F7-01FD ...................................... Merged.
Devices: 01FE-0204 ...................................... Merged.
Devices: 0205-020B ...................................... Merged.
Devices: 020C-0212 ...................................... Merged.
Devices: 0213-0219 ...................................... Merged.
Devices: 021A-0220 ...................................... Merged.
Devices: 0221-0227 ...................................... Merged.
Devices: 0228-022E ...................................... Merged.
Devices: 022F-0235 ...................................... Merged.
Devices: 0236-023C ...................................... Merged.
Devices: 023D-0243 ...................................... Merged.
Devices: 0244-024A ...................................... Merged.
Devices: 024B-0251 ...................................... Merged.
Devices: 0252-0258 ...................................... Merged.
Devices: 0259-025A ...................................... Merged.
'1R2_500_11'.
server_2 : done
server_3 : done
server_4 :
server_5 :
/dev/sdj1: clean, 11464/231360 files, 164742/461860 blocks
fsck 1.26 (3-Feb-2002)
85
Troubleshooting

'1R2_500_11'.
Please wait...
Devices: 0000-0001 ...................................... Merged.
Devices: 0003-0005 ...................................... Merged.
Devices: 000D-0015 ...................................... Merged.
Devices: 0016-001E ...................................... Merged.
Devices: 001F-0027 ...................................... Merged.
Devices: 0028-0030 ...................................... Merged.
Devices: 0031-0039 ...................................... Merged.
Devices: 003A-0042 ...................................... Merged.
Devices: 0043-004B ...................................... Merged.
Devices: 004C-0054 ...................................... Merged.
Devices: 0055-005D ...................................... Merged.
Devices: 005E-0066 ...................................... Merged.
Devices: 0067-006F ...................................... Merged.
Devices: 0070-0078 ...................................... Merged.
Devices: 0079-0081 ...................................... Merged.
Devices: 0082-008A ...................................... Merged.
Devices: 008B-008C ...................................... Merged.
Devices: 01DB-01E1 ...................................... Merged.
Devices: 01E2-01E8 ...................................... Merged.
Devices: 01E9-01EF ...................................... Merged.
Devices: 01F0-01F6 ...................................... Merged.
Devices: 01F7-01FD ...................................... Merged.
Devices: 01FE-0204 ...................................... Merged.
Devices: 0205-020B ...................................... Merged.
Devices: 020C-0212 ...................................... Merged.
Devices: 0213-0219 ...................................... Merged.
Devices: 021A-0220 ...................................... Merged.
Devices: 0221-0227 ...................................... Merged.
Devices: 0228-022E ...................................... Merged.
Devices: 022F-0235 ...................................... Merged.
Devices: 0236-023C ...................................... Merged.
Devices: 023D-0243 ...................................... Merged.
Devices: 0244-024A ...................................... Merged.
Devices: 024B-0251 ...................................... Merged.
Devices: 0252-0258 ...................................... Merged.
Devices: 0259-025A ...................................... Merged.
'1R2_500_11'.
Waiting for 1R2_500_11 sync ...done
failed
---------------------------------------------------------------Please execute /nasmcd/sbin/nas_rdf -restore on remote site cs100_src
---------------------------------------------------------------[root@cs100_src rdfadmin]#
86
Troubleshooting
Note: 3 ,
5-7.
Resolution for restoration failure example 1

Step
Action
1.
[root@cs100_src nasadmin]# /nasmcd/sbin/nas_rdf -restore
server_2 : rdf : reboot in progress ............
rdf : going active
done
server_3 : rdf : reboot in progress ............
rdf : going active
done
server_4 :
server_5 :
Would you like to set device group 1R1_11 to ASYNC Mode ? [yes or
no]: yes
An RDF Set 'Asynchronous Mode' operation execution is in progress
for device group
'1R1_11'. Please wait...
The RDF Set 'Asynchronous Mode' operation successfully executed
for device group '1R1_11'.
Would you like to set device group 1R1_12 to ASYNC Mode ? [yes or
no]: no
Starting Services ...done
[root@cs100_src nasadmin]#
2.
Exit as root. This concludes the device-group failback phase.
87
Troubleshooting
Step
Action
3.
Log in to and manage the source VNX directly from the nasadmin account on the source VNX (cs100_src).
If the restoration is still unsuccessful, gather SRDF/A logging information using the script /nas/tools/collect_support_materials.
Example 2 for restoration failure (NS series gateway)

3 -2600& -2700&
.
[root@Celerra2 nasadmin]# /nas/sbin/nas_rdf restore
...
Starting restore on remote site Celerra1 ...
Waiting for nbs clients to start ... WARNING: Timed out
CRITICAL FAULT:
Unable to mount /nas/dos
Starting Services on remote site Celerra1 ...done
Note: ..." .

Step
Action
1.
Stop the services at the source as root by typing:

[root@Celerra1 nasadmin] # /sbin/service nas stop
2.
Perform a restore at the source as root by typing:

[root@Celerra1 nasadmin] # /nasmcd/sbin/nas_rdf restore
Output:
...
server_2 :
done
server_3 :
Resume RDF
link(s)........................................Done.
Starting Services ...done
88
Troubleshooting
Example 3 for restoration failure (database lock error)

3
. 3 ,
_ .
3 .
Example 3 restore error
[root@cs0_dst rdfadmin]# /nas/sbin/nas_rdf restore

Target (R2) View
Source (R1) View
-------------------------------- -------------------ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv R2 Inv K
T R1 Inv R2 Inv
Device Dev E Tracks Tracks S Dev
E Tracks Tracks
-------------------------------- -- ----------------DEV001 08F2 RW
1
0 RW 37CD WD
0
0
DEV002 08F3 RW
58
0 RW 37CE WD
0
0
DEV003 08FA RW
0
0 RW 37D3 WD
0
0
DEV004 08FB RW
0
0 RW 37D4 WD
0
0
DEV005 08FC RW
12
0 RW 37D5 WD
0
0
DEV006 08FD RW
0
0 RW 37D6 WD
0
0
DEV007 092C RW
3546
0 RW 0629 WD
0
0
DEV008 0930 RW
2562
0 RW 062D WD
0
0
DEV009 06F5 RW
0
0 RW 0631 WD
0
0
Total
-------- ---------- ----Track(s)
6179
0
0
0
MB(s)
193.1
0.0
0.0
0.0
MODES
---- -------RDF Pair
MDA STATE
--- -------C.D R1 Updated
C.D R1 Updated
C.D R1 Updated
C.D R1 Updated
C.D R1 Updated
C.D R1 Updated
C.D R1 Updated
C.D R1 Updated
C.D R1 Updated
Legend for MODES:

Copy
D(omino)
A(daptive Copy)
An RDF 'Update R1' operation execution is in progress for device group
'1R2_500_4'.
Please wait...
Devices: 37CD-37CE ...................................... Merged.
Devices: 37D3-37D6 ...................................... Merged.
Devices: 0629-0634 ...................................... Merged.
'1R2_500_4'.
89
Troubleshooting

server_2 : done
server_3 : done
server_4 :
server_5 :
fsck 1.26 (3-Feb-2002)
'1R2_500_4'.
Please wait...
Devices: 37CD-37CE ...................................... Merged.
Devices: 37D3-37D6 ...................................... Merged.
Devices: 0629-0634 ...................................... Merged.
'1R2_500_4'.
Waiting for 1R2_500_4 sync ...done
server_2 :
Error 2201: server_2 : unable to acquire lock(s), try later
server_3 :
rdf : going active
done
server_4 :
server_5 :
90
Troubleshooting

If the RDF device groups were setup to operate in ASYNCHRONOUS ( SRDF/A )
mode,
now would be a good time to set it back to that mode.
Would you like to set device group 1R2_500_4 to ASYNC Mode ? [yes or no]:
yes
Starting Services on remote site cs0_src ...

[root@cs0_dst rdfadmin]# exit
[rdfadmin@cs0_dst rdfadmin]$ exit
[nasadmin@cs0_dst nasadmin]$ exit

Action
Run the server_standby command on the source VNX for the server that had the lock contention (in this example, server_2).
Example:
[nasadmin@cs0_src nasadmin]$ server_standby server_2 -restore rdf
Output
server_2 :
rdf : going active
done
server_2 : Nil
Resolve Data Mover failure after failover activation

( # , , #
, . 3 ,
_ ()
() .
Step
Action
1.
Log in to the destination VNX (cs110_dst) as nasadmin and switch (su) to root.
91
Troubleshooting
Step
Action
2.
Initialize the Data Mover by using this command syntax:

[root@cs110_dst nasadmin]# /nas/sbin/setup_slot -init <x>
where:
<x> = Slot number of the new Data Mover
Example:
To initialize the Data Mover for slot 2, type:
[root@cs110_dst nasadmin]# /nas/sbin/setup_slot -init 2
Initializing server in slot 2 as server_2 ...
Starting PXE service...:done
Reboot server in slot 2, waiting..... 0 0 0 0 0 0 1 1 1 3 3 3 3 3
3 3 4 (154 secs)
Stopping PXE service...:done
Ping server in slot 2 on primary interface ...ok
Ping server in slot 2 on backup interface ...ok
Discover disks attached to server in slot 2 ...
server_2 : done
server_2 : done
server_2 : done
server_2 : done
Synchronize date+time on server in slot 2 ...
server_2 : Mon Aug 17 12:11:05 EDT 2009
server_2 :
Processor
= Intel Pentium 4
Processor speed (MHz) = 2800
Total main memory (MB) = 4093
Mother board
= CMB-Sledgehammer
Bus speed (MHz)
= 800
Bios Version
= 03.80
Post Version
= Rev. 01.59
server_2 : reboot in progress 0.0.0.0.0.0.0.0.1.1.3.3.3.3.3.4.done
Checking to make sure slot 2 is ready........ 5 5 (63 secs)
Completed setup of server in slot 2 as server_2
This Data Mover (also referred to as Blade) is a MirrorView or RDF
standby Data Mover, log in to the system as rdfadmin and switch
(su) to root, and, regardless of straight (for example, server 2
to server 2) or criss-cross (for example, server 2 to server 3)
configuration, use the CLI command with the same slot id:
/nas/sbin/setup_slot -i 2
[root@cs110_dst nasadmin]#
3.

[root@cs110_dst nasadmin]# exit
exit
4.
Exit nasadmin by typing:

[nasadmin@cs110_dst ~]$ exit
logout
92
Troubleshooting
Step
Action
5.
Log in to the destination VNX (cs110_dst) as rdfadmin and switch (su) to root.
6.
Initialize the Data Mover by using this command syntax:

[root@cs110_dst rdfadmin]# /nas/sbin/setup_slot -init <x>
where:
<x> = Slot number of the new Data Mover
Example:
To initialize the Data Mover for slot 2, type:
[root@cs110_dst rdfadmin]#
/nas/sbin/setup_slot -init 2
The script will update only hardware related configuration such

as the MAC addresses for the internal network and then reboot the
Data Mover (also referred to as Blade).
server_2 : reboot in progress 0.0.0.0.0.0.0.0.1.1.3.3.3.3.3.4.done
Checking to make sure slot 2 is ready........ 5 5 (64 secs)
Completed setup of server in slot 2 as server_2
[root@cs110_dst rdfadmin]#
CAUTION: Ensure that you run the setup_slot command first as nasadmin switching (su) to root and
then as rdfadmin switching (su) to root.
If you run the command as rdfadmin before running it as nasadmin, you will get the following error message:
setup_slot has not been run as nasadmin before running it as rdfadmin user on this Data Mover (also referred to as Blade) The script
will exit without changing the state of the system or rebooting
it. Please do the following to set up this Data Mover correctly:
1. Initialize the new Data Mover for the nasadmin database by
logging in to the system as nasadmin, switching (su) to root,and
using the CLI command:
2. Initialize the new Data Mover for the rdfadmin database by
logging in to the system as rdfadmin user, switching (su) to root,
and using the CLI command:
7.

[root@cs110_dst rdfadmin]# exit
exit
8.
Exit rdfadmin by typing:

[rdfadmin@cs110_dst ~]$ exit
logout
93
Troubleshooting
Handle additional error situations

( # , (21#%- -21#% # ,)
///_ - //_ -
, " 2 . 6
5-7 , . 1
:
1. 1 ///_ - ///_ -
# , .
2. # # ,
.
Error messages
, ,
.
3 , :
4 :
4 -
.
$," . 2:
94
3 _ - <,(#>, <,(#>
.
" $ , &:
"+(:
1- , , $ #,
#, 2 #.
4 ' ' (#
* $," . 2 . $,"
. 2, Support by Product ,
.
Troubleshooting
EMC Training and Professional Services

$," " $ $,"
. $," "
$ - ---
. $," $,"
. & $," . 2 ://2.$,".
.
$," / 2 5-7 . "
, (3 , ,
. % ,
(3
. " $," " 2 1
.
EMC Training and Professional Services
95
Troubleshooting
96
Appendix A
Portfolio of High-Availability
Options
3 5-7 21#% -
. % 4 98 /
21#% (21#%/ )
(21#%/2).
% 4 98, % 5 98, % 6 98, % 7
99, % 8 99, % 9 100, % 10
100
21#%/2 , 21#% , , 3%/%2 -",
3%/%2 %", , (
- ).
Note: / 21#%/ ,
21#%.
97
Portfolio of High-Availability Options
%
, $," .
Production site
VNX
Symmetrix
SRDF
DR recovery site
Symmetrix
SRDF
Dedicated SRDF links
(synchronous or
asynchronous mode)
PFS
VNX
R1 data
volumes
VNX
SRDF
SRDF
VNX DR over
SRDF/S
VNX
R2 data
volumes
DR mirror of
PFS
VNX-000038
Figure 4. VNX replication and recovery with active/passive synchronous

SRDF (SRDF/S) or asynchronous SRDF (SRDF/A)
Production site
VNX
Symmetrix
DR recovery +
business
continuance site
SRDF
Symmetrix
SRDF
PFS
VNX
R1 data
volumes

(synchronous mode only)
VNX
SRDF
SRDF
DR mirror of
PFS
VNX DR over
SRDF/S
VNX
R2 data
volumes
VNX
local BCV
volumes
NearCopy
snapshot of
PFS
VNX-000039
Figure 5. VNX disaster recovery active/passive SRDF/S only with

98
Production + DR
recovery site
VNX
Symmetrix
Production + DR
recovery site
SRDF

(synchronous mode only)
PFS
DR mirror of
PFS
VNX
R2 data
volumes
VNX
Symmetrix
SRDF
VNX
R1 data
volumes
SRDF
SRDF
DR mirror of
PFS
VNX DR over
SRDF/S
VNX
R2 data
volumes
PFS
VNX
R1 data
volumes
VNX-000040
Figure 6. VNX disaster recovery active/active SRDF/S only

Production site
VNX
Symmetrix
Business
continuance
recovery site
SRDF
Symmetrix
SRDF
PFS
VNX
local STD
volumes
BCV snapshot of
PFS
VNX
R1 BCV
volumes

(adaptive copy
write-pending mode)
VNX
SRDF
SRDF
Imported FS
Adaptive
copy
VNX
R2 BCV
volumes
VNX
local STD
volumes
FarCopy
snapshot of
PFS
VNX-000041
Figure 7. VNX business continuance with TimeFinder/FS FarCopy (version

5.1)
99
Production site
VNX
Symmetrix
Control Station IP
IP WAN
PFS
SRDF
VNX
local STD
volumes
Control Station IP
Business
continuance
recovery site
SRDF
Symmetrix
BCV snapshot of
PFS

(adaptive copy
write-pending mode)
VNX
R1 BCV
volumes
VNX
SRDF
SRDF
BCV snapshot of
PFS
Imported FS
Adaptive copy
VNX
R2 BCV
volumes
VNX
local STD
volumes
FarCopy
snapshot of
PFS
VNX-000042
Figure 8. VNX business continuance with TimeFinder/FS FarCopy (version

5.3)
Symmetrix
VNX
Business
continuance
recovery site 1
Control Station IP
IP WAN
FarCopy
snapshot of
PFS
SRDF
VNX
local STD
volumes
Control
Station IP
Control
Station IP
Business
continuance
recovery
site 2
SRDF
Dedicated SRDF Links
(adaptive copy
write-pending mode)
Imported FS
Symmetrix
VNX
SRDF
VNX
R2 BCV
volumes
SRDF
SRDF
Production site
VNX FarCopy over

adaptive copy
Symmetrix
VNX
BCV snapshot of
PFS
PFS
BCV snapshot of
PFS
VNX
R1 BCV
volumes
VNX
local STD
volumes
VNX
R1 BCV
volumes
SRDF
Imported FS
FarCopy
snapshot of
PFS
VNX
R2 BCV
volumes
VNX
local STD
volumes
VNX FarCopy over

adaptive copy
Figure 9. VNX business continuance with redundant FarCopy sites
100
VNX-000043
Production site 1
Control Station IP
IP WAN
VNX
Symmetrix
PFS
BCV snapshot of
PFS
VNX
local STD
volumes
VNX
R1 BCV
volumes
Control Station IP
Control Station IP
Imported FS
VNX FarCopy over
adaptive copy
VNX
R2 BCV
volumes
Production site 2
SRDF
(adaptive copy
write-pending mode)
FarCopy
snapshot of
PFS
VNX
local STD
volumes
Symmetrix
Imported FS
FarCopy
snapshot of
PFS
VNX
R2 BCV
volumes
VNX
local STD
volumes
PFS
VNX
local STD
volumes
BCV snapshot of
PFS
VNX
R1 BCV
volumes
VNX FarCopy over

adaptive copy
VNX
Symmetrix
SRDF
(adaptive copy
write-pending mode)
VNX
Business
continuance
recovery site
VNX-000044
Figure 10. VNX business continuance using TimeFinder/FS FarCopy with

many sites
101
102
Glossary
A
active/active
% $," 2 1 # % (21#%) $," ,5/2
, ,
. $ 5-7 # ,. (
, . % 21#%, 2
() . % ,5/2,
5-7 +4- .
active/passive
% 21#% ,5/2 , 5-7 ,
, () 5-7 ,
, (). 3
. 21#%
2 . ,5/2
5-7 .
adaptive copy disk-pending mode
21#%
. 3
(/. . 3 (/.
.
C
Common Internet File System (CIFS)
%- , 2 , ! (2,!). (
( .
D
delta set
% 21#%/ (21#%/ ),
. $ (/. .
3 (/. . % 5-7 1,
103
Glossary
5-7 1
(-, --, ).
3 - 128 ,!.
dependent write consistency
% 21#%/ , --
,
.
destination VNX for file
3 () 5-7 21#% ,5/2 . 3
5-7 .
2 5-7 : 5-7 .
L
local mirror
2
. ( , (/.
.
2 11 .
M
metavolume
. 5-7 , , , , .
. $
.
2 , , , .
MirrorView Synchronous (MirrorView/S)
2 ( +4-)
. 3
, 5-7
5-7 . 2
( +4-)
(/.. ,5/2 5-7 .
Multi-Path File System (MPFS)
5-7 ,/%2
, % " 2"2( , $," 2
5-7 . ,/%2 % , /
(%,/) .
P
Production File System (PFS)
/ % 2 5-7 . /%2 2 5-7
+4- # , 5-7 .
104
Glossary
R
R1 volume
21#% () 2 .
2 .
R2 volume
21#% () 2 .
2 .
remote mirror
% 21#%, 2
2 . 4 $," 21#% ,
. ( ,
. % ,5/2, +4- 5-7 .
$ +4- ( )
+4- ( ). ( , +4-
, .
2 12 .
S
SnapSure
. 5-7 , -, -- ,
, .
SRDF/Asynchronous (SRDF/A)
21#% - , --
. 4 21#%/ 5-7
5-7 /2 #,7
5-7 /2 #,7 (
).
SRDF/Synchronous (SRDF/S)
21#% , -
2
2 ( 200 ). 21#%/2 $,"
3%/%2 -" (/; /).
Symmetrix Remote Data Facility (SRDF)
$," 2
. 3 , ,
- . 3 21#%
- ,
21#%/2 (21#%/2) 21#%/ (21#%/ ).
105
Glossary
T
TimeFinder/FS
! 2
(!"5) -- 5-7 .
106
Index
21#%/
21#%/ 33, 55
/
17, 41
55
20, 41
65
21#%/ 20
B
24
C
21
48, 53, 65, 67
"+( 11
"-2-14 29
_ - 43
28,"+( 11
_ 24
_ 36, 38
5-7 24
/ 20, 41
# , 28
" 2
17
38
" 2 17
18
"20 11
21
21
# ,
29
28
48
28
44

21

21
" - 2 55
5-7
46
66

55, 63
-2 "-2-14
29
21#%/ 21#%/2 23
E
// 49
$," $-+ - 74
75, 80, 87, 88, 89, 94
89
21#% # , 80
21#% 75
-2 88
107
Index
()
... 87
F
10, 33, 34, 52, 55
/ 33, 52, 55
21#%/ 33
5-7 34
%, 12
_ , 24
G
53
H
# , 30, 53
31, 35
-
" 1 (52) 26
,5/2 24
24
22 26
21#%/ 25
21#%/2 24
24
3%/%2 25
3%/%2 -" %" 25
'33/ 47
/ 20, 41
/ 33, 52
21#% 32, 36, 38
(/ 17
(/ 65
L
10
_ 38
+ 11
18
108
47
2 19
, 94
# , 28
,/%2 12
N
_ - 33
_ - 32, 36, 38
_ - 34
-2
# , 29
88
P
38, 47
_ 38
18
65
,5/2 38
R
21
1 12
21
/ 65
67
5-7 - 34
S
22 30
22, 11
12
5-7
43
66
21#%
17
21#%/
21#%/2 23
20
... 87
2 #,7 10
2 19
Index
2 (# 2
19
(21#%/2) 23
T
21
73
30
12
59
5-7 %, 12
28
4 11
109
Index
110

SRDF A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRDF A

Uploaded by

Copyright:

Available Formats

EMC VNX Series

Using SRDF/A with VNX

" 1998 - 2009 $," ".

Using SRDF/A with VNX 7.0

Using SRDF/A with VNX 7.0

Appendix A: Portfolio of High-Availability Options.............................97

Using SRDF/A with VNX 7.0

Using SRDF/A with VNX 7.0

Special notice conventions

Where to get help

Using SRDF/A with VNX 7.0

Using SRDF/A with VNX 7.0

Using SRDF/A with VNX 7.0

Using SRDF/A with VNX 7.0

DMX systems with SRDF/A.

VNX version 7.0 on the source and destination servers.

Similar source and destination VNX models.

Two attached VNX/Symmetrix DMX system pairs.

Using SRDF/A with VNX 7.0

21#%/ $," 4 . 21#%/

% "-2-14 , "20 + 21#%

SnapSure checkpoints restrictions

VNX feature-specific restrictions

21#%/ 3%/%2 -"

, 21#% $," ,5/2 .

21#%/ 1 (21#%/ 1) 21#%/

21#% 5-7 %,. 4 5-7 %,

21#% ,/%2. " $,"

" 21#% # 21#%.

User interface choices

Using SRDF/A with VNX 7.0

4 3%/%2, -", %" 5-7

2 $ 2 21#% % "+( / &

EMC VNX documentation on the EMC Online Support website

Using SRDF/A with VNX 7.0

Using SRDF/A with VNX 7.0

Using SRDF/A with VNX 7.0

Communication between Control Stations

Dedicated link for SRDF

Figure 1. Basic VNX-with-SRDF configuration

SRDF and logical volumes

Using SRDF/A with VNX 7.0

Logical volume 001

Dedicated SRDF link

Figure 2. VNX with SRDF logical volume

Note: ( 5-7 , $," 2

" 3 5-7 21#%/2,

$- 3 5-7 21#%/ , 21#%

Using SRDF/A with VNX 7.0

SRDF/A delta sets

SRDF/A delta sets

SRDF/A device pair

SRDF/A delta set begins

Important resource considerations

Using SRDF/A with VNX 7.0

Differences between SRDF/A and SRDF/S

Table 2. Summary of differences between SRDF/A and SRDF/S

Complete disaster recovery configuration for systems

Provides manual failover and failback of backend

Provides I/O-level consistency.

Differences between SRDF/A and SRDF/S

Comparison of VNX for file high-availability and replication products

Using SRDF/A with VNX 7.0