Beruflich Dokumente
Kultur Dokumente
Release 7.0
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
/ % 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
$,"..
.
" ': ', ,
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
Preface
,
$," . 3,
.
% -- , .
( ,
$," .
Preface
Important:
Note:
, -.
Hint: , -
.
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
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.
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
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
% " 2, 21#% ,
///_/_ , ,
, "20. " 2 1 ("21)
.
2 $ 2 28,"+( 5-7
" 2 , ,
$," ( "". ', 28,"+(
21#%/ .
6 _ ,
///500 . - 2
///500 . ( ///500 ,
.
$," 22 25
(/%2) # , . (
/%2 21#% +4-,
22 25 21#% +4-
/%2. ( 25
21#% +4-, ,
. $ .
21#%/ ,
.
( 22 , 25
___ . ( 25
, /%2 , .
Restrictions
11
Introduction
% 2 $
21#% , , # , 1#%
. 3 $," 3%/%2 -" %" .
3, _ -_
21#%. # : $
13421842457: 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#%/
21#%/ (22#) . (
22# 21#%/ , 5-7
.
$," $-+ ( - 74
. 2 10
.
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 21#%/2 5-7 # 1
. $," , :
2 1 # % (21#%) / &
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
.
(/ ()
21#% (
21#%)
SRDF
17
Concepts
% 1 18 5-7--21#%
.
PS2
PS3
PS4
SB15
SB13
SB11
SB7
SB5
SB3
PS0
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
18
Concepts
% 2 19 .
- 2 (# ( 001 001
).
SB15
SB13
PS2
PS3
PS4
SB7
SB5
SB3
SB2
SB0
PS0
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
Symmetrix
Symmetrix
VNX-000034
5-7 21#% :
SRDF
19
Concepts
2 !"5. 3 -" ,
(12) , 21#%/2 . 4 21#%/2 5-7 # 1
4 3%/%2, -", %" 5-7 .
" $,"
.
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
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)
Target
R2
device
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
22
. , 21#%/
.
.
# , -
20 , .
# - ( ),
. + $,"
. 8
21#%/ 12 11 28,"+(
21#%/ ( , //// -
<_> -. 111_3).
Concepts
21#%/2 5-7
SRDF/S
Requires Symmetrix DMX systems or later versions. Works with Symmetrix 3xxx, 5xxx, 8xxx, or DMX
systems.
Extended-distance replication facility.
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#%.
23
Concepts
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
Concepts
Storage platform
Description
Restrictions
SRDF/Asynchronous
TimeFinder/FS
Symmetrix only
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.
25
Concepts
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
SnapSure
Description
Restrictions
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#%/ .
( 21#% /, ///_ -
.
( / , 2
. 3 ,
2 . ! ,
///_ - " 2 ,
11 ,
Planning considerations
27
Concepts
12 .
6 ///_ - " 2,
. 3 12
. 3 12
2
///_ - .
% () # ,
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#%/ )
+ # , 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#%/ # ,.
Planning considerations
29
Concepts
$ # ,,
21#%- # ,, 21#%/ . 3
/ .
$ : 2
-(2/#-2 4-(7 , 6(-2//#"/!#"/#"
6 , -3 . 3 "(%2
21#% ,
-%2 . % ,
.2. % "(%2 ,
/ 4(#/&(#.
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.
5.
6.
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#%/
" .
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).
-ip<ip>-passphrase
<passphrase>
31
Concepts
Command used
32
Description
Concepts
Command used
Description
33
Concepts
Command used
Description
Synchronizes R2 to R1.
/nas/sbin/nas_rdf
-restore
34
Concepts
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
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.
100_ 5-7. ( .
35
Concepts
110_ 5-7. ( -
.
36
3
Configuring
3 21#%/
/ 38
( (/) 41
(/) 52
1 5-7 65
37
Configuring
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#%/
3 :
1. / () 5-7 39
2. / () 5-7 39
3. 5 40
38
Configuring
Action
1.
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
Action
1.
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
operation in progress (not interruptible)...
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
Action
1.
2.
40
Configuring
Note:
3 0 .
8 _ - ( _ -). 8 _
, , , .
Prerequisites
5-7 5-7 .
21#%/
3 2 27
2 5-7 # ,
.
5-7 .
3 / :
( 5-7 41
( 5-7 45
5 21#%/
5-7 (/) 49
Action
1.
41
Configuring
Step
Action
2.
3.
slot_0
slot_2
slot_3
slot_4
slot_5
4.
type
1
4
1
4
acl
1000
1000
1000
1000
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
1000, owner=nasadmin, ID=201
nas
4
server_5, policy=auto
enabled
online, ready
4
server_5
1000, owner=nasadmin, ID=201
standby
5
server_4
enabled
online, ready
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
= 1000, owner=nasadmin, ID=201
type
= nas
slot
= 2
member_of =
standby
= server_3, policy=auto
RDFstandby= slot=2
status
:
defined = enabled
actual
= online, active
server server_3 in slot 3, remote standby in slot [3] (or none): 3
server_3 : done
id
= 2
name
= server_3
acl
= 1000, owner=nasadmin, ID=201
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
server server_5 in slot 5, remote standby in slot [5] (or 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
Action
1.
2.
3.
type acl
1 1000 2
1 1000 3
1 1000 4
4 1000 5
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
1000, owner=nasadmin, ID=201
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
1000, owner=nasadmin, ID=201
nas
3
enabled
online, ready
3
server_4
1000, owner=nasadmin, ID=201
nas
4
server_5, policy=auto
enabled
online, ready
4
server_5
1000, owner=nasadmin, ID=201
standby
5
server_4
enabled
online, ready
6.
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
operation in progress (not interruptible)...
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
operation in progress (not interruptible)...
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
passphrase = rdfadmin
Please create a rdf standby for each server listed
server server_5 in slot 5, remote standby in slot [5] (or none):
none
server server_4 in slot 4, remote standby in slot [4] (or 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.
Important: ( (/ " 2 ,
///_ - . ( (/
,
// .
Action
1.
49
Configuring
Step
Action
2.
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.
/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
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).
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 .
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.
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:00 cs100_src get_datamover_status: Data Mover server_5:
COMMAND doesnt match.
Feb 7 18:40:01 cs100_src get_datamover_status: Data Mover server_3:
COMMAND doesnt match.
Feb 7 18:40:01 cs100_src get_datamover_status: Data Mover server_4:
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
Action
1.
2.
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
Duration of Last cycle
RDFA Session Priority
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
56
Configuring
Step
Action
5.
6.
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.
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.
Suspend RDF link(s).......................................Started.
Suspend RDF link(s).......................................Done.
Read/Write Enable device(s) on RA at target (R2)..........Done.
Suspend RDF link(s).......................................Started.
Suspend RDF link(s).......................................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)
Waiting for nbs clients to die ... done
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 :
server_3 : going offline
rdf : going active
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
done
server_4 :
Error 4003: server_4 : standby is not configured
server_5 :
Error 4003: server_5 : standby is not configured
58
Configuring
Step
Action
9.
exit
Note: The failover is complete.
Note: ( 2 #,7 ,
$," " 2 1 .
Action
1.
2.
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.
60
Configuring
Step
Action
5.
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
Duration of Last cycle
:00:00:00
RDFA Session Priority
: 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
64
Configuring
Action
1.
Halt CIFS.
2.
3.
4.
Restart CIFS.
65
Configuring
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.
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.
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?
Do you wish to continue [yes or no]: yes
Contact cs100_src ... is alive
4.
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.
Device Group (DG) Name : 1R2_500_3
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
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:
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
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...
Suspend RDF link(s).......................................Done.
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.
Note: Ensure that the source CS0 is operational and on the data network.
Example:
Is remote site cs100_src ready for Network restoration?
Do you wish to continue [yes or no]: yes
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 :
Error 4003: server_4 : standby is not configured
server_5 :
Error 4003: server_5 : standby is not configured
/dev/ndj1: clean, 11595/231360 files, 204256/461860 blocks
fsck 1.26 (3-Feb-2002)
Waiting for nbs clients to die ... done
Waiting for nbs clients to die ... done
/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.
Suspend RDF link(s).......................................Done.
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: 038F-0399 in (0557,03).......................... Merged.
Devices: 037D-038E in (0557,03).......................... Merged.
Merge device track tables between source and target.......Done.
Resume RDF link(s)........................................Started.
Resume RDF link(s)........................................Done.
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
Waiting for nbs clients to start ... done
Suspend RDF link(s).......................................Done.
server_2 :
server_2 : going standby
rdf : going active
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
done
server_3 :
server_3 : going standby
rdf : going active
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
done
70
Configuring
Step
Action
server_4 :
Error 4003: server_4 : standby is not configured
server_5 :
Error 4003: server_5 : standby is not configured
Resume RDF link(s)........................................Started.
Resume RDF link(s)........................................Done.
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.
8.
71
Configuring
72
4
Troubleshooting
, $,"
. 3,
. % --
, .
(
, $," " 2 1.
/ 1 1 5-7
$," . 2 .
3 :
$," $-+ ( - 74
* 74
$ 94
$," 3 / 2 95
73
Troubleshooting
1 74
1 75
1 80
1 83
1 # , 91
' 94
" (_) _
" (_.)
3 21#%/
4 ///__ , ,
, :
///_.
///_..
///_..
///_..*
///.*
3 .
74
Troubleshooting
3 _ , /
. , // .
3 , , :
# (*)
3 .
/ ,
+ -
$ 1 75
1 1 77
$ 2 78
75
Troubleshooting
Retype passphrase:
rdfadmin
76
Troubleshooting
Action
1.
2.
type
1
1
1
4
acl
1000
1000
1000
1000
name
server_2
server_3
server_4
server_5
3.
Delete.....by typing:
[root@cs110_dst nasadmin]# /nas/sbin/getreason
Output:
10 - slot_0 primary control station
5 - slot_2 contacted
5 - slot_3 contacted
5 - slot_4 contacted
5 - slot_5 contacted
4.
Delete.....by typing:
[root@cs110_dst nasadmin]# /nas/sbin/getreason
Output:
10 - slot_0 primary control station
5 - slot_2 contacted
5 - slot_3 contacted
5 - slot_4 contacted
5 - slot_5 contacted
5.
type
1
1
1
4
acl
1000
1000
1000
1000
name
server_2
server_3
server_4
server_5
77
Troubleshooting
Step
Action
6.
Delete.....by typing:
[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
1000, owner=nasadmin, ID=201
nas
2
enabled
online, ready
2
server_3
1000, owner=nasadmin, ID=201
nas
3
enabled
online, ready
3
server_4
1000, owner=nasadmin, ID=201
nas
4
server_5, policy=auto
enabled
online, ready
4
server_5
1000, owner=nasadmin, ID=201
standby
5
server_4
enabled
online, ready
78
Troubleshooting
5288
6152
8336
225792
9%
3%
/.etc_common
/
79
Troubleshooting
$ 80
1 81
80
Troubleshooting
Action
1.
2.
type
1
4
1
4
acl
1000
0
1000
1000
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
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
done
4.
5.
Delete.....by typing:
[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
name
server_2
server_3
server_4
server_5
Delete.....by typing:
[root@cs110_dst rdfadmin]# /nas/bin/server_mount ALL
Output:
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>
server_4 :
root_fs_4 on / uxfs,perm,rw
root_fs_common on /.etc_common uxfs,perm,ro
server_5 :
root_fs_5 on / uxfs,perm,rw,<unmounted>
root_fs_common on /.etc_common uxfs,perm,ro,<unmounted>
82
Troubleshooting
3 :
$ 1 83
1 1 87
$ 2 (-2 ) 88
1 2 88
$ 3 ( ) 89
1 3 91
83
Troubleshooting
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
84
Troubleshooting
85
Troubleshooting
86
Troubleshooting
Note: 3 ,
5-7.
Action
1.
Delete.....by typing:
[root@cs100_src nasadmin]# /nasmcd/sbin/nas_rdf -restore
server_2 : rdf : reboot in progress ............
server_2 : going standby
rdf : going active
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
done
server_3 : rdf : reboot in progress ............
server_3 : going standby
rdf : going active
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
done
server_4 :
Error 4003: server_4 : standby is not configured
server_5 :
Error 4003: server_5 : standby is not configured
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 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'.
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 1R1_12 to ASYNC Mode ? [yes or
no]: no
Starting Services ...done
[root@cs100_src nasadmin]#
2.
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.
...
Starting restore on remote site Celerra1 ...
Waiting for nbs clients to start ... WARNING: Timed out
Waiting for nbs clients to start ... done
CRITICAL FAULT:
Unable to mount /nas/dos
Starting Services on remote site Celerra1 ...done
Note: ..." .
Action
1.
2.
88
Troubleshooting
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
89
Troubleshooting
90
Troubleshooting
Action
1.
Log in to the destination VNX (cs110_dst) as nasadmin and switch (su) to root.
91
Troubleshooting
Step
Action
2.
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 ...
Discovering storage (may take several minutes)
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.
4.
92
Troubleshooting
Step
Action
5.
Log in to the destination VNX (cs110_dst) as rdfadmin and switch (su) to root.
6.
Example:
To initialize the Data Mover for slot 2, type:
[root@cs110_dst rdfadmin]#
/nas/sbin/setup_slot -init 2
8.
93
Troubleshooting
Error messages
, ,
.
3 , :
4 :
4 -
.
$," . 2:
94
3 _ - <,(#>, <,(#>
.
" $ , &:
"+(:
1- , , $ #,
#, 2 #.
4 ' ' (#
* $," . 2 . $,"
. 2, Support by Product ,
.
Troubleshooting
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
%
, $," .
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
Symmetrix
DR recovery +
business
continuance site
SRDF
Symmetrix
SRDF
PFS
VNX
R1 data
volumes
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
98
Production + DR
recovery site
VNX
Symmetrix
Production + DR
recovery site
SRDF
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
Symmetrix
Business
continuance
recovery site
SRDF
Symmetrix
SRDF
PFS
VNX
local STD
volumes
BCV snapshot of
PFS
VNX
R1 BCV
volumes
VNX
SRDF
SRDF
Imported FS
Adaptive
copy
VNX
R2 BCV
volumes
VNX
local STD
volumes
FarCopy
snapshot of
PFS
VNX-000041
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
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
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
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
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
Symmetrix
SRDF
(adaptive copy
write-pending mode)
VNX
Business
continuance
recovery site
VNX-000044
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