COMMAND EXPLANATION

Symconfigure h Provides brief, online help information including

definitions and syntax
Symconfigure version Lists the SYMCLI, SYMPI, and configuration
server version information
Symconfigure verify !erifies that the configuration currently running in
the specified Symmetrix
symconfigure "sid #$ abort borting a %ung Session
symconfigure freespace vie& ho& much available 'unformatted( dis) space
is in the Symmetrix*

CREATING DEVICES

symconfigure "sid +, verify !erify that you can open a session on the service
processor*
symdev list "da all space -or. symdis) list Identify free space location*
create dev count/+ si0e/1222 emulation/fba
config/+"&ay"mir3
dding a 4e& device
count / the number of devices to create*
si0e / the si0e of the device needed in number of
cylinders*
emulation / the device emulation type
config / the device configuration type*
delete dev xx, raidset / 56789 :;LS9< deleting a symm device
Update the symapi_db.bi ! a"" atta#hed
se$%e$s $&i' S!"&ti!s Eab"e$ (sym#)'
dis#!%e$*

MAPPING DEVICES
symdev list Confirm ne& devices &ere created*
symconfigure "sid +, verify !erify that you can open a session on the service
processor*
symdev list or symdev list noport Select the device-s. to map*
symcfg list available addresses sa $a p 2 =etermine available host addresses
map dev >f+ to dir $b?2, lun/>f
&&n/>2222222c@++#fa13
;or peripheral device addressing -;C"SA or ;C"
L. and to automatically updateBrefresh the
!CM=C?
map dev aa to dir #a?>, target/a, lun/>d3 ;or SCSI?
map dev cc to dir >+a?>, vbus/>, target/$,
lun/>+3
;or fibre ;C"SA or ;C"L &ith using volume set
addressing? -%P.-!bus";iber !irtual ; bus.
Update the symapi_db.bi ! a"" atta#hed
se$%e$s $&i' S!"&ti!s Eab"e$ (sym#)'
dis#!%e$*

symdev list sa #a p > !erify devices are mapped*
UNMAPPING DEVICES
Se"e#t De%i#es t! Umap
symdev list Select the device-s. to unmap*
symdev list sa xx p x If selecting device-s. on a specific port to unmap?
symdev list multiport If you need to see device-s. mapped to multiple
ports?
symdev sho& ,$ If you need see one deviceDs mapping information?
St!p I+O ! A))e#ted De%i#es
symld "g unmapdg &riteEdisable 6o &rite"disable a device on all ports?
symld "g unmapdg &riteEdisable "sa $a "p > 6o &rite disable a device on a select port?
symdev &riteEdisable xxxx sa xx p x It is also possible to &rite"disable a device &ithout
using device groups by using the follo&ing
T! #$eate a $e'&"a$ type !) de%i#e '$!&p,
symdg create"g dgname 6o create a regular type of device group?
symld "g dgname add dev $$ dd device-s. to device group?
symld "g dgname addall dev "range ,#?,f 6o add a range of devices?
UNMAP
unmap dev ff?>22 from dir >+a?23 6o unmap a range of devices?
unmap dev >2> from dir #a?23 6o unmap a device?
unmap dev ccd from dir all?all3 6o unmap devices from all directors?
Update the symapi_db.bi ! a"" atta#hed
se$%e$s $&i' S!"&ti!s Eab"e$ (sym#)'
dis#!%e$*

-ORMING META DEVICES
symconfigure "sid +, verify !erify that you can open a session on the service
processor
symdev list -or. symdev list noport !erify the devices are unmapped*
symdev list noport Select the devices to form the meta*
symmir "g dgname split Split standards and CC!s if they are used to form a
meta*
symld "g dgname remove =9!22> =9!22F 7emove meta member candidates from device
groups
-ORMING CONCATENATED . STRIPED
META DEVICES

form meta from dev 2b1 config/concatenated3
add dev 2>$?2>F to meta 2b13
6o create a concatenated meta -manually selecting
all members.?
form meta from dev 2>>
config/striped
stripeEsi0e/>@+2
count/,3
6o create a striped meta -letting the soft&are
automatically select the members.?
symconfigure sid +, v f filename commit 7un the symconfigure command*
Update symapi_db.bi ! a"" atta#hed Se$%e$s
$&i' S!"&ti!s Eab"e$ (sym#)' Dis#!%e$*

=isplay the meta device* symdev sho& xxx -&here xxx is the meta head. or
symdev list meta

remove dev 2b@ from meta 2b13 6o remove a meta member or members from the tail
of a concatenated meta device
symmir "g dgname split Split meta device from CC! meta before removing
member*
ADDING DEVICES IN STRIPED META
symconfigure "sid +, verify
!erify that you can open a session on the service
processor*
symmir g dgname split
Split standards and CC!s before adding them to a
meta device
add dev ### to meta ##,, protectEdata/true,
bcvEmetaEhead/,,,3 6o add a device to a striped meta?
symconfigure sid +, v f filename commit 7un the symconfigure command*
Update the symapi_db.bi ! a"" atta#hed
se$%e$s $&i' S!"&ti!s Eab"e$ (sym#)'
dis#!%e$*
symdev list meta =isplay the meta device*
DISSOLVING META DEVICES
symconfigure "sid +, verify
!erify that you can open a session on the service
processor*
symmir "g dgname split Split meta device from meta CC! before dissolving
dissolve meta dev 2b13 6o dissolve a meta?
symconfigure sid +, v f filename commit 7un the symconfigure command*
symdev list meta !erify that meta device is dissolved
/CV
symbcv list pd
6o list all CC! devices that are visible to your host,
enter?
symbcv list dev
6o list all CC! devices, regardless of &hether they
are visible to your host, enter?
symmir "g prod "full establish
6o initiate a full establish on all the CC! pairs in
the prod device group
symmir -g prod -full establish DEV001
6o initiate a full establish on one CC! pair,
=9!22>, in the prod device group, enter
symmir "g prod "full establish =9!22> CC! ld
CC!22$ =9!22+ CC! ld CC!22G =9!22,
CC! ld CC!221
6o initiate a full establish on more than one CC!
pair -list. in the prod device group &ith one
command, enter?
symmir "full establish =9!22, CC! dev 2b+ symmir establish? Selected =evices
symmir split symmir split
symmir restore "full noprompt symmir restore
CLONE
symclone g Prod=C create =9!22> sym ld
=9!22$ symclone g Prod=C
create =9!22> sym ld =9!22F Multiple Clone Copies
symclone"g clonegrp activate S7C22> sym ld
6H622+ "notEready 6he clone volume is placed in 47 state
symclone "g clonegrp activate "consistent
Create a consistent image of a heterogeneous
database environment
symclone "g clonegrp terminate S7C22> sym ld
6H622+ Terminate a Copy Session
symclone g clonegrp restore S7C22> sym ld
6H622+ Restore from a TimeFinder Clone
symclone list 6he symclone list B Iuery command?
symclone activate S7C22> sym ld 6H622> nop !ti"ate the sym!lone Session
symclone terminate S7C22> sym ld 6H622>
nop Terminate the sym!lone Session
S0MMSNAP OPERATIONS
symsnap "g savedb create =9!22> vdev ld
!=9!22$ "svp saveEdb Create
symsnap "g savedb activate =9!22> vdev ld
!=9!22$ ctivate
symsnap restore =9!22> vdev ld !=9!22$ 7estore
symsnap "g savedb terminate =9!22> vdev ld
!=9!22$ 6erminate
/////////////////////////////////////////////////////////////////////
/1SERIES S2it#h C!mmads
s&itch=isable J offline
ipddrSet Jset the IP address of a Crocade s&itch
configure J change s&itch parameters
routehelp J routing commands
s&itchSho& J display s&itch info
supportSho& J full detailed s&itch info
portSho& K J display port info
nsSho& J 4ame server contents
nsllSho& J 4S for full fabric
fabricSho& J fabric information
/1SERIES 3!i' C!mmads
0oneCreate 'Lone>(, '+2?22?22?e2?F@?#2?2G?213 $2?2F?2#?1+?b1?@2?c>?1d(
cfgCreate '6estEcfg(, 'Lone>3 Lone+(
cfgSave J saves 0oning information across reboots
cfg9nable '6estEcfg(
0oneSho& or cfgSho& J sho&s defined and effective 0ones and configurations
0onedd J adds a member to a 0one
0one7emove J removes a member from a 0one
0one=elete J deletes a 0one
cfgdd J adds a 0one to a 0one configuration
cfg7emove J removes a 0one from a 0one configuration
cfg=elete J deletes a 0one from a 0one configuration
cfgClear J clears all 0oning informationB must disable the effective configuration
cfg=isable J disables the effective 0one configuration
44444444444444444444444444444444444444444444444444444444444444444444
Addi' 5/A A##ess t! Symmet$i6 De%i#es
6o configure device mas)ing in the !CM=C, log on to the control station as dministrator* 6he
follo&ing steps outline ho& to add device access for an %C"to"; connection?
>* =iscover local %Cs on a host that have a channel to a Symmetrix array and generate an
AA4 for any %C that does not have an AA4 assigned yet, updating the !CM=C
&ith the ne& information*
symmas7 dis#!%e$ hba
+* List the %Cs on a host and the Symmetrix ; director port to &hich each %C is connected*
4ote the AA4 of the %C that you &ill be configuring and &hich ; port connects to that
%C*
symmas7 "ist hba
,* List devices mapped to the ; director that you &ill be configuring -for example, director
>F.*
sym#)' "ist 8-A 9:A 1add$
#* Ma)e an entry for the %C"to"; connection in the !CM=C
+
, specifying devices that the
%C can access* ;or example, add a range of devices -22,2 through 22,#. to the !CM=C
on the Symmetrix array -sid 1>#., specifying the %CMs AA4 and the ; directorBport
that the %C connects to*
symmas7 8sid ;9< 822 =>>>>>>>#?=>b<;< add de%s >>@>,>>@< 8di$ 9:A 1p >
$* Ahen you finish ma)ing %C entries in the !CM=C, proceed &ith the follo&ing steps* Cac)
up the revised !CM=C to a file -for example, a file called My=evMas)Cac)up.*
symmas7 8sid ;9< ba#7&p 8)i"e MyDe%Mas7/a#7&p
F* 7efresh the AA4"related profile tables in the Symmetrix cache &ith the latest !CM=C data*
6he follo&ing command updates the cache on all ; directors &ith the contents of the
!CM=C*
symmas7 $e)$esh
G* 7eboot the host &hose %C entry you added to the !CM=C*
1* Ahen you reboot a host, you need to scan the Symmetrix devices and refresh the SYMPI
database*
sym#)' dis#!%e$
Removing Devices
You can remove some devices associated &ith an %C entry, or you can remove the entire set of
devices associated &ith an %C entry* 7emoving some devices -but not all. reIuires syntax
similar to that for adding devices and the same refresh, bac)up, and discover steps after
completing the remove operation*
6o remove devices 22,> and 22,, from the 22,2"to"22,# range of devices that &as added
previously?
symmas7 8sid ;9< 822 =>>>>>>>#?=>b<;< $em!%e de%s >>@9A>>@@ 8di$ 9:A 1p >
6o remove the remaining devices in the 22,2"to"22,# device range, you can specify individual
devices or the range &ith an option -force. that allo&s you to remove a noncontiguous range*
;or example?
symmas7 8sid ;9< 822 =>>>>>>>#?=>b<;< $em!%e de%s >>@>,>>@< B 8di$ 9:A 1p >
5/A Ideti)ie$s (CCNA ACCNA ad iSCSI Name*
n %C can be specified in symmas) commands by its uniIue AA4
,
, by an AA4 alias
associated &ith the AA4, or by an iSCSI name -or its alias.* 6hese names appear in the
Symmetrix login history table and in the !CM=C*
Ahen you issue the symmas) discover hba command to update the login history table, the
Symmetrix PI -SYMPI. chec)s the !CM=C to determine &hether an AA4 exists for each
AA4 record* If not, SYMPI creates an AA4 that consists of t&o parts -the name of the
host and the name of the %C. and &rites it to the login history table* %o&ever, you can rename
the AA4 to a shorter name, if you prefer*
6he follo&ing command allo&s you to examine AA4s in the login history table of Symmetrix
1>#?
symmas7 8sid ;9< "ist "!'is
6o assign an AA4 to fit your naming reIuirements, you can use the symmas) rename
command at any time N even before SYMPI generates an AA4* ;or example, the
follo&ing command assigns the t&o"part name Solaris,Bb# as the AA4 for AA4
+2222222c@+2b#1#?
symmas7 8sid ;9< 822 =>>>>>>>#?=>b<;< $eame S!"a$is@A+b<
If later you decide you &ant to replace all user"defined AA4s -li)e Solaris,Bb#. &ith
system"generated AA4s, the follo&ing command over&rites all existing AA4 entries in
the !CM=C*
symmas7 dis#!%e$ hba 1$eame
You can identify the %C in symmas) commands through an iSCSI name* 6he iSCSI is a SCSI"
over"IP protocol that tries to ta)e advantage of the IP net&or) for SCSI traffic rather than
reIuiring a ne& ;ibre net&or)* n iSCSI name is used li)e an IP address or a AA4 and is
displayed using the symmas) list logins or the symmas) list hba commands* uniIue iSCSI
name is determined by the hard&are that logs into a Symmetrix array and, li)e the AA4, a
t&o"part alias name is generated from the symmas) discover hba command*
S2appi' a Ne2 5/A )!$ a -ai"ed 5/A
If an %C fails or needs replacement, you can use the follo&ing steps to s&ap in a ne& %C
&ithout having to redefine the old %C set of mas)ed devices for the ne& %C*
>* Issue the symmas) list logins command to determine the AA4 of the failed %C*
+* S&ap the %C boards*
,* Issue the symmas) list hba command to determine the ne& AA4*
#* Substitute the ne& AA4 for all occurrences of the old AA4 in the !CM=C* ;or example,
to replace old AA4 +2222222c@+2b#1# &ith ne& AA4 +2222222c@+2b,@,?
symmas7 8sid ;9< 822 =>>>>>>>#?=>b<;< $ep"a#e =>>>>>>>#?=>b@?@
$* Issue the symmas) discover command to establish the ne& AA4 in the login history table
or, if you prefer, issue the symmas) rename command to assign an AA4 to the ne& %C
in both the login history table and the !CM=C*
F* Issue symmas) refresh to update the !CM information in Symmetrix director cache*
O))setti' LUN Add$esses
L84 offset is an enhanced visibility feature that allo&s any host type to adOust host visibility by
offsetting -renumbering. L84 addresses* 6his is useful for host types that need to see L84 2222
or transform a noncontiguous L84 seIuence to a contiguous seIuence* In a case &here t&o
hosts access the same Symmetrix director port and need to see a L84 2222 but not the same
device, you can use L84 offset so that one host sees the devices mapped from L84 'x( as
starting from L84 2222, and the other host sees devices from L84 'y( as starting from L84
2222*
6o account for noncontiguous device L84 addresses, specify a L84 base and offset as
he#ade!imal values to adOust for the brea) in the L84 seIuence* 6he base hex value represents
the first L84 in a renumbered L84 seIuence* 6he offset hex value added to the base value
determines &here to begin renumbering* ;or example, if a host needs to detect L84 2222 but
you &ant your host to detect only L84s 222$ through 2221, you can specify a L84 base address
of 2222 and an offset of 222$* 6he follo&ing command renumbers L84s 222$ through 2221 as
L84s 2222 through 222,?
symmas7 8sid ;9< set "&!))set ! >>>D >>>> 8di$ 9:A 1p > 822 =>>>>>>>#?=>b<;<
Pn the other hand, if your mas)ed devices for an %C"to"; connection had L84 addresses
2222222, and 222G222@, you &ould need to specify a L84 base address of 222# and an
offset of 222, -to renumber L84s 222G222@ as L84s 222#222F.* You can record only one
gap per %C"to"; connection*
If you have multiple hosts that cannot discover devices &ith noncontiguous L84 addresses, you
need to issue the symmas) set lunoffset command for each host*
dd and 7emove Mas)ed =evices?
symmas7 1sid >9=; 1a2 5!st@b+<a add de%s >>9<A>>9D 1di$ 9:a 1p >
7emoving Meta Members?
symmas7db 8sid 6666 1meta_membe$ $em!%e
Initiali0ing the =atabase?
symmas7db 1sid >9=; iit 1)i"e /a#7&pDe%Mas79 (ame*
!ie&ing the Login %istory 6able?
symmas7 8s id :9?: "ist "!'is
7efreshing =irector Profile 6ables?
symmas7 $e)$esh Asymmas7 dis#!%e$ hba
!ie&ing the =atabase?
E symmas7db 1sid >9=; "ist database
Sort for port at a dir ?
symmas7db 1sid :9?: "ist database 1di$ =b 1p 9
!ie&ing =evice Capacity?
symmas7db 1sid :9?: "ist #apa#ity 1h!st api9<D (h!st ame*
symmas7db 1sid :9?: "ist assi'met 1de% >><>,>><@ (mapped de% t! h!st*
symmas7db 1sid :9?: "ist de%s 122 9>>>>>>>#?=@;>D@ (List de%s #!)i'&$ed t! h!st siFe*
Managing a Cac)up =atabase ;ile ?
symmas7db 1sid >9=; ba#7&p 1)i"e /a#7&pDe%Mas7 (ba#7 &p )i"e ame*
7estoring a =atabase?
symmas7db 1sid >9=; $est!$e 1)i"e /a#7&pDe%Mas7
symmas7db 1sid >9=; $est!$e 1)i"e /a#7&pDe%Mas7 1s7ip_a&theti#ati! (s7ip a&the )$!m
$est!$e*
Converting a =atabase 6ype?
symmas7db 1sid 0128 #!%e$t 1%#mdb_type type_<
Ariting =irectly to the !CM=C?
symmas7db 1sid >9=; set 1!_di$e#t_i! (disa""!2s the &se !) %e$si!s !) S0MCLI
p$i!$ t! %e$si! D.@. 1!_di$e#t_i! *

Symmetrix loc)s* 2">$ -&ith the exception K @.
sym#)' "ist 1"!#7 a"" 1% -If you are vie&ing from the host attached to the symm in Iuestion.
sym#)' 1sid XXXX "ist 1"!#7 a"" -7emote vie&ing "this &ill tell you all the symm loc)s
-config,optm,vcm.
sym#)' 1sid XXX "ist 1"!#7 a"" 1% -&ill sho& you more details &ho put the loc) and ho& long
it &as held
ie? 9,2>QQQQ " 6his &as set by customer 9Q2+QQQQ"
6his &as held by C9* =P 4P6 release any loc) that &as put there by the C9*
7eleasing Symmetrix loc)s?
sym#)' 1"!#7 G&mbe$H $e"ease 1)!$#e -if releasing from the host attached to symm.
sym#)' 1sid XXXX 1"!#7 G&mbe$H $e"ease 1force -ie? symcfg "sid QQQQ "loc)n >$ release
"force.
De%i#e "!#7s E ?,
symde% 1sid XXXX 1"!#7 "ist -if vie&ing from remote host.
symde% 1"!#7 "ist -&ill sho& all the devices that are loc)ed " -from attached host. at
times,ho&ever, you need to discover any ne& changes to see the loc) if it
comes bac) un)no&n -means there are no loc)s. then do
sym#)' dis#!%e$? this &ill discover any changes made* fter the prompt comes bac)* retry the
symdev "loc) list command it should sho& you all the devices, if any, that are
loc)ed on the symm*
Re"easi' de%i#e "!#7,
Caution? if you notice that there is a "L next to the flag setting? 6his indicates that there is a long
loc) that is normal* -most li)ely a symreplicate process*. before releasing loc) chec) &ith your
replicate manager and see if they can stop the process so that you can &or) &ith the devices in
Iuestion*
symde% 1"!#7 ? $e"ease 1)!$#e 1!p
symde% 1sid XXXX 1"!#7 ? $e"ease 1)!$#e 1!p, -that stands for 4P Prompt" so that you are not
prompted for each and every device that is loc)ed*
/////////////////////////////////////////////////////////////////////
EMC, SRD- m!des
S7=; N Heneral monitor and control operations3 R S7=;BS N Synchronous mode 3 RS7=;B N
synchronous mode
S7=;B7 N utomated 7eplication 3 RS7=;BCH N Consistency Hroups 3
Conceptually, even operationally, S7=; is very similar to 6imefinder* bout the only difference
is that S7=; &or)s across Symms3 &hile 6imefinder &or)s internally to one Symm*
6hat difference, intersymm vs intrasym, means that S7=; operations can cover Iuite a bit of
ground geographically* Aith the advent of geographically separated symms, the integrity of the
data from one symm to the other becomes a concern* 9MC has a number of operational modes in
&hich the S7=; operates* 6he choice bet&een these operational modes is a balancing act
bet&een ho& Iuic)ly the calling application gets an ac)no&ledgement bac) versus ho& sure you
need to be that the data has been received on the remote symm*
Sy#h$!!&s m!de
Synchronous mode basically means that the remote symm must have the IBP in cache before the
calling application receives the ac)no&ledgement* =epending on distance bet&een symms, this
may have a significant impact on performance &hich is the main reason that 9MC suggests this
set up in a campus -damn near co"located. environment only*
If youDre particularly paranoid about ensuring data on one symm is on the other, you can enable
the =omino effect -I thin) youDre supposed to be hearing suspense music in the bac)ground right
about no&***.* Casically, the domino effect ensures that the 7> devices &ill become Snot readyS
if the 7+ devices canDt be reached for any reason " effectively shutting do&n the filesystem-s.
until the problem can be resolved*
Esym$d) 1' p$!d set m!de sy#
Semi1sy#h$!!&s m!de
In semi"synchronous mode, the 7+ devices are one -or less. &rite IBP out of sync &ith their 7>
device counterparts* 6he application gets the ac)no&ledgement as soon as the first &rite IBP gets
to the local cache* 6he second IBP isnDt ac)no&ledged until the first is in the remote cache* 6his
should speed up the application over the synchronous mode* It does, ho&ever, mean that your
data might be a bit out of sync &ith the local symm*
Esym$d) 1' p$!d set m!de semi
Adapti%e C!py1C$ite Pedi'
6his mode copies data over to the 7+ volumes as Iuic)ly as it can3 ho&ever, doesnDt delay the
ac)no&ledgement to the application* 6his mode is useful &here some data loss is permissible
and local performance is paramount*
6hereDs a configurable s)e& parameter that lists the maximum allo&able dirty trac)s* Pnce that
number of pending IBPs is reached, the system s&itches to the predetermined mode -probably
semi"synchronous. until the remote symm catches up* t that point, it s&itches bac) to adaptive
copy"&rite pending mode*
Adapti%e C!py 8 Dis7
6he adaptive copy dis) mode is designed for situations reIuiring the transfer of large amounts of
data &ithout loss of performance* Cecause the Symmetrix array cannot fully guard against data
loss should a failure occur, it is recommended that you use this mode temporarily to transfer the
bul) of your data to target -7+. devices, and then s&itch to a full S7=; mode -synchronous or
semi"synchronous. or adaptive copy"&rite pending mode -if you can tolerate some lac) of
synchroni0ation bet&een the remotely mirrored pairs. to ensure full data protection* Ahen you
set the S7=; mode to adaptive copy dis), the Symmetrix array ac)no&ledges all &rites to
source -7>. devices as if they &ere local devices* 4e& data accumulates on the source -7>.
device and is mar)ed by the source -7>. side as invalid trac)s until it is subseIuently transferred
to the target -7+. device* 6he remote director transfers each &rite to the target -7+. device
&henever lin) paths become available*
;or example, to turn on the adaptive copy dis) mode for the prod group, enter?
Esym$d) 1' p$!d set m!de a#p_dis7
6o turn the adaptive copy dis) mode off for the prod group, enter?
Esym$d) 1' p$!d set m!de a#p_!))
6his attribute also has a user"configurable s)e& -maximum number of invalid trac)s threshold.,
that &hen exceeded, causes the remotely mirrored device to operate in the predetermined S7=;
state -synchronous or semi"synchronous. &hen this mode is in effect* s soon as the number of
invalid trac)s drops for a device belo& this value, the remotely mirrored pair reverts bac) to the
adaptive copy &rite pending mode*
Adapti%e C!py Cha'e S7e2
6his attribute is used to modify the adaptive copy s)e& threshold* Ahen the s)e& threshold is
exceeded, the remotely mirrored pair operates in the predetermined S7=; state -synchronous or
semi"synchronous.* s soon as the number of invalid trac)s drops belo& this value, the remotely
mirrored pair reverts bac) to the adaptive copy mode* 6he s)e& value is configured at the device
level and may be set to a value bet&een 2 and F$,$,# trac)s* ;or devices larger than a + HC
capacity drive, a value of F$,$,$ can be specified to target all the trac)s of any given drive*
;or example, to change the adaptive copy s)e& value to all trac)s of device CC!2+, of group
prod, enter? Ksym$d) 1' p$!d set a#p_s7e2 :DD@D /CV>=@
6o change the adaptive copy s)e& value to ,2,222 trac)s for device
CC!2+, of group prod, enter?
Esym$d) 1' p$!d set a#p_s7e2 @>>>> /CV>=@
R= N!t Ready
6his attribute is used to set the 7+ 4ot 7eady if there are invalid trac)s* Invalid trac)s could be
either remote invalids on the source -7>. side or target -7+. invalids on the source -7>. side*
Invalid trac)s occur &hen the user enables the target -7+. for 7eadBArite status* If there are
invalid trac)s, the device 7=; status is set to 4ot 7eady* Set the nrEifEinvalid argument to on or
off* ;or example, to set the target -7+. side of the S7=; configuration to the 4ot 7eady state if
there are invalid trac)s for device CC!2+, of group prod, enter?
Esym$d) 1' p$!d set $_i)_i%a"id ! /CV>=@
DOMINO -EATURE? =omino mode is recommended to ensure data currency on all
symmetrix frame that there is no possibility of inconsistent data at 7+ side incase of S7=; lin)
failure *If =omino mode is not enabled T if all S7=; lin)s fail and the application continues to
modify the data on the 7>, but the ne& data is not replicated to the 7+ side* 6he 7+ only contains
a copy of data up to the point of C lin)s failure* If additional failure occurs, such as a system
failure before the S7=; lin) is fixed* 6his can cause the application to fail over to the 7+ side, T
the application &ill have to deal &ith non"current data* 6he inconsistent and therefore unusable
data &ill result from the follo&ing seIuence of circumstances
=omino mode is not enabled S7=; lin)s fail the application continues to modify the
data the lin) is restoredresynchoroni0ation from 7> to 7+ starts but does not finish
6he disadvantage of enabling =omino Mode is that &hen S7=; lin) fails, all IBPs &ill be
refused -to those devices. until the S7=; lin) is restored* Pr manual intervention is underta)en
to disable domino mode*
Esym$d) 1' p$!d set d!mi! !))
Esym$d) 1' p$!d set d!mi! !
SRD-1A(Asy#h$!!&s*?S7=;" provides a long"distance replication solution &ith minimal
impact on performance* 6his level is intended for customers reIuiring minimal host application
impact, &ho need to maintain a restorable copy of data at the 7+ side, &hich preserves data
consistency &ithin the database* In the event of a disaster at the 7> site or if S7=; lin)s are lost
during data transfer, a partial delta set of data is discarded* %o&ever, a dependent &rite
consistent point"in"time copy of data is retained on the target side*
Esym$d) 1' p$!d set m!de asy#
SRD- PAIR
STATE
R9 STATE
(S!&$#e*
RD- LINI
STATUS
R= STATE
(Ta$'et*
I%a"id
T$a#7s
SynchInProg 7eady 7eady 4ot 7eady or A= U 2
Synchroni0ed 7eady 7eady 4ot 7eady or A= 2
Split 7eady 4ot 7eady or
A=
7eady """""
;ailed Pver 4ot 7eady or
A=
4ot 7eady 7eady """"
7> 8pdated 4ot 7eady or
A=
7eady or A= 7eady 2 -7>
trac)s on
Source.
7> 8pdinProg 4ot 7eady or
A=
7eady or A= 7eady U 2 -7>
tac)s on
Source.
Suspended ny Status 4ot 7eady or
A=
4ot 7eady or A= """""
Partitioned -from
7>.
ny Status 4ot 7eady 4ot vailable """"""
Partitioned -from
7+.
4ot vailable 4ot 7eady ny Status """""""
Invalid ny Status ny Status ny Status """""""
;rom 7> means vie&ed from the host locally connected to the 7> devices*
;rom 7+ means vie&ed from the host locally connected to the 7+ devices*
SRD- C!mmads
Important? You cannot add 7> devices to an 7+ device group type*
Ksymd' #$eate dbd' 1type RD-9 Creating device group dbdg
Ksym"d 1' dbd' add de% >>>: a##t9 dding symm* =evice 222F &hich logical name is
acct> in dbdg
Ksym"d 8' dbd' $em!%e DEV>>9 - 7emove a device from a device group
Ksym$d) 8' dbd' estab"ish 8full - 6o full establish of 7> mirror to 7+ mirror*
Ksym$d) 8' dbd' estab"ish 8!p - executing incremental establish in bac)ground
Ksym$d) 8' dbd' s&sped 8)!$#e - suspend 7=; pair &ith force option
Ksym$d) 1' dbd'_$= 1b#% 1)!$#e 1istat s&s - 6o instance Suspend
Ksym$d) 8' dbd' sp"it 8)!$#e - split 7=; pair &ith force option
Esym$d) 1' dbd'_$= 1b#% 1)!$#e sp"it 1immediate /CV>>= - 6o Split immediately -pplies
only to S7=;B"capable devices* Causes the S7=;B session to be dropped immediately if a
failover, split, or suspend operation is reIuested* .
Ksymrdf g dbdg failbac) - Copy from 7+ to 7> -S&itches data processing bac) to the source
-7>. side*
Ksymrdf "g dbdg failover - S&itches data processing from the source -7>. to the target -7+.
side*
Ksymrdf sid 7emote"Symmid ping - 6o chec) net&or) availability of 7emote Symmetrix*
Ksymrdf g dbdg Iuery - chec) the status of 7=; pair*
Ksymrdf g dbdg resume -7esume the 7> and 7+
Esym$d) 1' dbd'_$= 1b#% 1)!$#e est /CV>>= 6o establish CC!22+ device - single device.
Esym$d) 1' dbd'_$= 1b#% 1)!$#e s&s /CV>>= 6o Suspend CC!22+ device -single device.
Ksym$d) 1' dbd'_$= 1b#% 1sym)!$#e 1)!$#e s&s 7eIuests the Symmetrix to force the
operation to occur that overrides instances &here they are normally reOected*
Aarning? 8se care &hen applying this option as data could be lost or corrupted* 9MC does not
recommend using this flag, except in an emergency*6o enable the "symforce option for 7=; use,
a parameter called S0MAPI_ALLOC_RD-_S0M-ORCE in the options file must be set to
6789*
Aith "sym)!$#eA a split command &ill execute on an 7=; pair, even &hen they are in
sync in progress or restore in progress state* =uring the execution of an establish or restore
command, 1sym)!$#e &ill inhibit the verification of valid trac)s on the device at the source*
Esym$d) 8' dbd' $est!$e 8)&"" 6o initiate full restore on all 7=; pair for device group
dbdg*
Esym$d) 8' dbd' $est!$e 8)&"" DEV>>9 T! iitiate )&"" $est!$e ! RD- pai$ 2ith "!'i#a"
de%i#e DEV>>9 i dbd' de%i#e '$!&p.


9* symmas7db
Cac)s up, restores, initiali0es, and sho&s the contents of the =evice Mas)ing
database*
9* symmas7db "ist !_assi'met 1di$ a"" 1sid ?=
It &ill list all the devices from the SYMM @+ &hich are not yet mas)ed for any %C for
any ; port, mean these devices are not
available to any host* Cut these devices are mapped to respective ;s*
=* symmas7db "ist 1sid ?= !_assi'met 1di$ 9:# 1p >
It &ill sho& all the devices mapped to ; >Fc2 but not mas)ed for any %C*
@* symmas7db "ist 1sid ?= assi'met 1de% =;J
It &ill sho& mas)ing info for the SYMM dev id +1G from the SYMM @+*
Celo& output is sho&ing the =ir, port and %C PAA4 info, to &hom this device is
assigned*
<* symmas7db 1sid ?= "ist database 1di$ a""
It &ill list &hole mas)ing database for the SYMM @+*
=. symmas7
Sets up or modifies Symmetrix =evice Mas)ing functionality*
;or help """ symmas) h
9* symmas7 1sid ?= "ist "!'is
It &ill sho& all the 0oned %CDs login status to the ;*
=*symmas7 1sid ?= "ist "!'is 1di$ 9:# 1p >
6his command is sho&ing the login status of %Cs for the ; >FC -=ir >Fc and Port 2
@* symmas7 1sid ?= 122 =9>>>>9b@=9aJ9D9 1di$ 9:# 1p > add de% =;J
It &ill mas) the device +1G for the hba S+>2222>b,+>aG>$>S on the ; >Fc2* 6hen the
host 0oned &ith ; >Fc2 &ill be able to see this device*
@. syme%et
9nables the monitoring and trac)ing of events on Symmetrix arrays*
;or help "" symevent "h
a. syme%et 1sid ?= 1% 12a$ "ist
It &ill sho& all the &arning messages from the SYMM*
b. syme%et 1sid ?= "ist 1sta$t >9+9>+=>9> 1ed >;+9>+=>9>
It &ill sho& all the events from the date mentioned start date ->st Pct to 1th Pct. from the
SYMM @+*
<. symdis7
7eports on the configuration and status of dis)s and their hypers &ithin Symmetrix
arrays*
for help "" symdis) "h
a. symdis7 "ist 1sid ?= 1)ai"ed
It &ill lsit all failed dis)s in the SYMM @+
b. symdis7 "ist 1sid ?= 1da a""
It &ill list all the physical devices on to this SYMM
#. symdis7 "ist 1sid ?= 1da 9a 1ite$)a#e # 1tid > 1%
bove command &ill sho& the detail of the particular dis)* It &ill sho& all the hypers
curved on this dis)*
d. symdis7 "ist 1sid ?= 1h!tspa$es
It &ill list all the hotspare dis)s configured on this SYMM*
e. symdis7 "ist 1sid ?= 1h!tspa$es 1%
It &ill give the details of the hotspare status and also it invo)ed or not V
@. symde%
=isplays information for the selected, or all, Symmetrix devices*
;or help issue " suymdev h
a. symde% "ist 1sid ?=
It &ill sho& all the created devicesBvolumes on to the SYMM @+*
symdev list "sid @+ "v
It &ill sho& the detail information for all the volumes*
If you &ant to see detail of any one volume, then issue
symdev sho& "sid Wsymm device idU
b. symde% "ist 1sid ?= 1)a 9D# 1p 9
It &ill list the device mapped to the ; >$c and port >
#. T! ma7e a NR de%i#e t! Ready*
symdev "sid @+ ready WSym=ev4ameU
d. T! ma7e a de%i#e N!t Ready
symdev "sid @+ notEready WSym=ev4ameU
e. T! ma7e the de%i#e 2$ite disab"e !) pa$ti#&"a$ -A 9DC P!$t >
symdev "sid @+ &riteEdisable WSym=ev4ameU "sa >$c "p 2
). T! ma7e the de%i#e 2$ite eab"e ! pa$ti#&"a$ -A 9D# p!$t >
symdev "sid @+ r&Eenable WSym=ev4ameU "sa >$c "p 2
'. symde% "ist 1sid ?= 1i%et!$y
It &ill sho& over all inventory lists li)e belo&**
h. symde% "ist 1sid ?= 1%#m 1%
It &ill sho& the details of the !CM =C device from this SYMM
i. symde% "ist 1sid ?= 1DA a""
It &ill list all the volumes and the = information for them*
K.
You can list all volumes &ith specific configuration
symdev list "sid @+ "raid$ "protection ,X>
or
symdev list "sid @+ "raid$ "protection GX>
bove commands &ill list all 7I=$ volumes created on to this SYMM
symdev list "sid @+ "raidF "protection FX+
symdev list "sid @+ "raidF "protection >#X+
K.
symdev list "sid @+ "r> "" &ill list all 7> volumes created on to this SYMM
symdev list "sid @+ "r+ "" &ill list all 7+ volumes created on to this SYMM
)* symdev list "sid @+ "da >a "interface c
6he above command &ill list volumes created from the dis)s attached to = >a and the
interface or loop c
=. sym#!)i'&$e
llo&s the user to manage configuration changes affecting devices of specified
Symmetrix arrays, as &ell as manage device reservations, and virtual provisioning*
;or help you need to issue " symconfigure h
a. sym#!)i'&$e "ist 1sid ?= 1)$eespa#es 1&its M/
It &ill sho& the free space on the SYMM @+ -unalocated space*.
b. sym#!)i'&$e 1%e$si! 1% 1sid ?=
It &ill sho& the detail version of the installed Solution9nabler and the enginuity code of
the SYMM mentioned*
9. sym#)'
=iscovers or displays Symmetrix configuration information* 7efreshes the hostDs
Symmetrix database file or removes Symmetrix information from the database file*
7ebuilds the set of devices )no&n to the local host* It can also be used to vie& or
release a hanging Symmetrix exclusive loc), online or offline 7=; -7., or front"end
-S or ;. director ports*
a. sym#)' 1h
Its for help* It &ill sho& all s&itches are available to this command*
b. sym#)' dis#!%e$
It &ill get latest data from SYMM itself and store on to the host from &here you are
issuing the SYMCLI commands*
#. sym#)' "ist
It &ill sho& all the visible SYMMs from the host &here you issued the command*
#. sym#)' "ist 1sid G"ast @ di'it !) S0MM S+NH 1%
It &ill sho& verbose or detail info for the SYMM* Li)e cache si0e, last po&er on, IPL
time** etc*
d. sym#)' "ist 1sid ?= 1mem!$y
It &ill sho& the details of the cache installed*
e. sym#)' "ist 1sid ?= 1stat&s
It &ill sho& the current status of the SYMM, enguinity maOor version**
). sym#)' "ist 1sid ?= 1&pat#hesLm!$e
It &ill sho& all the installed patches to the SYMM @+*
'. sym#)' "ist 1da a"" 1sid ?=
It &ill list all the = attached to the SYMM @+*
nd
sym#)' "ist 1da a"" 1sid ?= 1%
&ill sho& the detail verbose output of the above command regarding all =s*
;or individual =, you can issue the comamnd in belo& &ay **
sym#)' "ist 1sid ?= 1da 9a
or
sym#)' "ist 1sid ?= 1da 9a 1%
h. sym#)' "ist 1)a a"" 1sid ?=
It &ill sho& all the ; installed on to the SYMM @+
nd
symcfg list "fa all "sid @+ "v
&ill sho& the detail and verbose output of the above command*
same for single ;, you can issue the command in belo& manner**
symcfg list "sid @+ "fa >c
i. sym#)' "ist 1sid ?= 1$a a""
It &ill list all the configured 7 director on the SYMM @+
K. sym#)' "ist 1sid ?= 1#!e#ti!s
It &ill sho&, &hat type of %osts are connected &ith this SYMM and on &hich ;*
7. sym#)' "ist 1sid ?= 1e%_data
It &ill sho& all the environment data on the screen
". sym#)' "ist 1sid ?= 1#!e#ti!s 1#apa#ity
It &ill sho& &hat total space is allocated to all the hosts*
m* symcfg list "sid @+ "loc)n all
It &ill list the loc) no* present in the SYMM @+*
symcfg list "sid @+ "loc)n all "v
&ill sho& the detail of the loc)*
. sym#)' 1sid ?= m!it!$
It &ill sho& the present status of all the pool created on to this SYMM @+*
Symmetrix I=? 222>@2,22F@+

DMX ;>> DMX 9>>>A =>>>A @>>> DMX @
> 4o Catteries, instead of that SPS
are used, it &ill act as a battery
Catteries are available,
=MQ >222 / > Catt
=MQ +222,,222 / + Catteries
-Cat K 2,>.
and no SPS
4o Catteries, instead of that SPS
are used, it &ill act as battery
+ =9s are present
-=is) rray 9nclosure.
> =9 / >$ drives
Maxm 4o of =9s / 1
Maxm 4o of drives / >+2 drives
4o =9s concept
=is) cages are present
> =is) cage / ,F drives
=MQ >222 / + dis) cage -;ront. T +
dis) cage - 7ear.
Maxm 4o of drives / #Y,F / >## drives
=MQ +222 / / # dis) cage -;ront. T #
dis) cage - 7ear.
Maxm 4o of drives / 1Y,F / +11 drives
=9s are present
-=is) rray 9nclosure.
> =9 / >$ drives
> Cay / >F =9s - +#2 drives.
Maxm 4o of Cays / >2 bays
Maxm 4o of =rives / +#22 drives
, 4o 9CMs, CCMs, QCMs are
present, instead of that ;9C9s are
used,
+ ;9C9s -;9C9 2, ;9C9 >.
;ront 9nd Cac) 9nd dapter
9CMs and CCMs are available
- 9CM ? It is board that &ill monitors
and logs environmental events for all
=MQ series field replaceable units
-;78s.*
;78s include devices such as director
boards, memory boards, port bypass
cards, smo)e detector unit -S=8.,
po&er supplies, fans and s&itches
QCM -functions are similar to
9CM, CCM.
9CMXCCM/ QCM
# 4o SP, instead of that
Z!M -Zeyboard, !ideo, Mouse.
Server
8PS
SP -Service Processor. is present 4o SP, instead of that
Z!M -Zeyboard, !ideo, Mouse.
Server
8PS
$ LCCs are present
> =9 / + LCC and + PS
# =9 / + SPS
LCC &ill connect drives and
directors through =I
PCCs instead of LCCs
;unction is similar to LCC
LCCs are present
> =9 / + LCC and + PS
# =9 / + SPS
LCC &ill connect drives and
directors through =I
F SP9 -SPS for System bay.
SPS -SPS for =is) bay.
4o SPS are present SPS for system bay
SPS for dis) bay
EMC Symmet$i6 DMX1< EMC Symmet$i6 V1Ma6
=MQ? =irect Matrix
rchitecture
!"Max? !irtual Matrix
rchitecture
Max Capacity? > PC 7a&
Storage
Max Capacity? + PC of 8sable
Storage
Max =rives? >@22* Pn 7P[?
+#22 max
Max =rives? +#22
Symmetrix Management Symmetrix Management Console
Console F*2 G*2
Solutions 9nabler F*2 Solutions 9nabler G*2
Predecessor of =MQ"# is
=MQ",
Predecessor of !"Max is =MQ"#
# Ports per =irector 1 Ports per =irector
4o 9ngine based concept 9ngine based concept
+# slots 6he concept of slots is gone
> System bay, @ Storage bays > System bay, >2 Storage bays
4o engines 1 9ngines in one System -serial
number.
F# ;iber Channel total ports
on all directors for host
connectivity
>+1 ;iber Channel total ports on
directorsBengines for host
connectivity
,+ ;ICP4 ports for host
connectivity
F# ;ICP4 ports for host
connectivity
,+ Hb9 iSCSI ports F# Hb9 iSCSCI ports
6otal Cache? $>+HC &ith
+$F HC usable -mirrored.
6otal Cache? >2+# HC &ith $>+
HC usable -mirrored.
Hreen color drive L9=
means +HC loop speed, Clue
color drive L9= means #HC
loop speed
Pnly #HC drive speed supported*
Largest supported volume is
F#HC per L84
Large !olume Support? +#2HC
per L84 -Ppen Systems. and
++,HC per L84 -Mainframe
Systems.
>+1 hypers per =rive -luns
per drive.
$>+ hypers per =rive -luns per
drive.
Hlobal Cache on Hlobal
Memory =irectors
Hlobal Cache on local engines
chips? again as cache is shared
bet&een multiple engines, cache
latency is expected as multiple
engines reIuest this IP
6otal S7=; Hroups
supported >+1
6otal S7=; Hroups supported
+$2
>F Hroups on Single Port for
S7=;
F# Hroups on Single Port for
S7=;
RAID Levels
2 Striped array &ith no fault tolerance
> =is) mirroring
+ 4ested 7I= -i*e*, > X 2, 2 X >, etc*.
, Parallel access array &ith dedicated parity dis)
# Striped array &ith independent dis)s and a dedicated parity dis)
$ Striped array &ith independent dis)s and distributed parity
F Striped array &ith independent dis)s and =8L distributed parity
Physical drives or groups of 7I= protected drives can be logically split into volumes )no&n as
logical volumes, commonly referred to as $ogi!al %nit &umbers -L84s.*
LUN masking is a process that provides data access control by defining &hich L84s a host can
access* L84 mas)ing function is typically implemented at the front end controller* 6his ensures
that volume access by servers is controlled appropriately, preventing unauthori0ed or accidental
use in a distributed environment\
EMC CLARiiON
"8ltra;lex technology for dual protocol connectivity, online expansion via IP modules, and
readiness for future technologiesNsuch as 1 HbBs ;ibre Channel and >2 HbBs iSCSI*
"Scalable from up to @F2 dis)s
"Supports flash drives &ith ,2 times more IPPS capability*
"Supports different types and si0es of drives, and 7I= types -2, >, >X2, ,, $, F.
"Supports up to >F HC of available cache memory per controller -Storage Processor.
"9nhances availability &ith non disruptive upgrade and failover
"9nsures data protection through mirrored &rite cache and cache vaulting
"Provides data integrity through dis) scrubbing* 6he bac)ground verification process runs
continually and reads all sectors of all the dis)s* If a bloc) is unreadable, the bac)"end error
handling recovers the bad sectors from parity or mirror data*
"Supports storage"based local and remote data replication for bac)up and disaster recovery
through Snap!ie& and Mirror!ie& soft&are*
EMC Symmeti!
"Incrementally scalable to +,#22 dis)s
" Supports ;lash"based solid"state drives
" =ynamic global cache memory ->F HC$>+ HC.
" dvanced processing po&er -up to >,2 Po&erPC.
" Large number of concurrent data paths available -,+>+1 data paths. for IBP processing
" %igh data processing band&idth -up to >+1 HCBs.
" =ata protection &ith 7I= >, >X2 -also )no&n as >2 for mainframe., $, and F
" Storage"based local and remote replication for business continuity through 6ime;inder and
S7=; Soft&are
Direct-attached storage (DAS): This type of storage connects directly to a server (host) or a
group of servers in a cluster. Storage can be either internal or external to the server. External
DAS alleviated the challenges of limited internal storage capacity.
pplications access data from =S using bloc)"level access protocols*
Storage area network (SAN): This is a dedicated, highperformance Fibre Channel (FC)
net!or" to facilitate block-level communication bet!een servers and storage. Storage is
partitioned and assigned to a server for accessing its data. SA# offers scalability, availability,
performance, and cost benefits compared to DAS.
S4 implementation uses?
Copper cables for short distance
Pptical fiber cables for long distance
6&o types of optical cables
Si'"e1m!de
Can carry single beams of light
=istance up to >2 ZM
M&"ti1m!de
Can carry multiple beams of light simultaneously
=istance up to $22 meters
Stada$d #!e#t!$ -SC. and a L&#et #!e#t!$ -LC. are t&o commonly used connectors
for fiber optic cables* n SC is used for data transmission speeds up to > HbBs, &hereas an LC is
used for speeds up to # HbBs* Staig"t #i$ 'ST( is a fiber optic connector &ith a plug and a
soc)et that is loc)ed &ith a half"t&isted bayonet loc)* In the early days of ;C deployment, fiber
optic cabling predominantly used S6 connectors* 6his connector is often used &ith ;ibre
Channel patch panels*
Network-attached storage (NAS): This is dedicated storage for file serving applications.
$nli"e a SA#, it connects to an existing communication net!or" (%A#) and provides file access
to heterogeneous clients. &ecause it is purposely built for providing storage to file server
applications, it offers higher scalability, availability, performance, and cost benefits compared to
general purpose file servers.
'()S, #)S

Internet Protocol SAN (IP-SAN): *ne of the latest evolutions in storage architecture, (+SA#
is a convergence of technologies used in SA# and #AS. (+SA# provides bloc"level
communication across a local or !ide area net!or" (%A# or ,A#), resulting in greater
consolidation and availability of data.
Block-level access is the basic mechanism for dis" access. (n this type of access, data is stored
and retrieved from dis"s by specifying the logical bloc" address. The bloc" address is derived
based on the geometric configuration of the dis"s. &loc" si-e defines the basic unit of data
storage and retrieval by an application Databases, such as *racle and S.% Server, define the
bloc" si-e for data access and the location of the data on the dis" in terms of the logical bloc"
address !hen an (/* operation is performed.

File-level access is an abstraction of bloc"level access. )ilelevel access to data is provided by
specifying the name and path of the file. (t uses the underlying bloc"level access to
%oint&to&$oint is the simplest ;C configuration N t&o devices are connected directly to each
other* 6his configuration provides a dedicated connection for data transmission bet&een nodes*
%o&ever, the point"to"point configuration offers limited connectivity, as only t&o devices can
communicate &ith each other at a given time* Moreover, it cannot be scaled to accommodate a
large number of net&or) devices* Standard =S uses point"to"point connectivity*
'C&AL con(ig)ation, devices are attached to a shared loop* ;C"L has the characteristics of a
to)en ring topology and a physical star topology* In ;C"L, each device contends &ith other
devices to perform IBP operations* =evices on the loop must 'arbitrate( to gain control of the
loop* t any given time, only one device can perform IBP operations on the loop*
'i*e C"annel s+itc"e, (a*ic -'C&S./ et2!$7 p$!%ides
interconnected devices, dedicated band&idth, and scalability* 6he addition or removal of a
device in a s&itched fabric is minimally disruptive3 it does not affect the ongoing traffic bet&een
other devices*;C"SA is also referred to as fabri! !onne!t* fabric is a logical space in &hich all
nodes communicate &ith one another in a net&or)*
N_p!$t, n end point in the fabric* 6his port is also )no&n as the node port* 6ypically, it is a
host port -%C. or a storage array port that is connected to a s&itch in a s&itched fabric*
NL_p!$t, node port that supports the arbitrated loop topology* 6his port is also )no&n as the
node loop port*
E_p!$t, n ;C port that forms the connection bet&een t&o ;C s&itches* 6his port is also
)no&n as the e#pansion port* 6he 9Eport on an ;C s&itch connects to the 9Eport of another ;C
s&itch in the fabric through a lin), &hich is called an InteS+itc" Link -ISL/. ISLs are used to
transfer host"to storage data as &ell as the fabric management traffic from one s&itch to another*
ISL is also one of the scaling mechanisms in S4 connectivity*
-_p!$t, port on a s&itch that connects an 4Eport* It is also )no&n as a fabri! port and cannot
participate in ;C"L*
-L_p!$t, fabric port that participates in ;C"L* 6his port is connected to the 4LEports on an
;C"L loop* ;LEport also connects a loop to a s&itch in a s&itched fabric* s a result, all
4LEports in the loop can participate in ;C"SA* 6his configuration is referred to as a publi! loop*
In contrast, an arbitrated loop &ithout any s&itches is referred to as a pri"ate loop* private
loop contains nodes &ith 4LEports, and does not contain ;LEport*
G_p!$t, generic port that can operate
ISL connects t&o or more ;C s&itches to each other using 9"Ports
Login #y$es in a S+itc"e, Net+ok
-ab$i# "!'i (-LOGI* is performed bet&een an 4Eport and an ;Eport* 6o log on to the fabric, a
device sends a ;LPHI frame &ith the Aorld Aide 4ode 4ame -AA44. and Aorld Aide Port
4ame -AAP4. parameters to the login service at the &ell")no&n ;C address ;;;;;9* In turn,
the s&itch accepts the login and returns an ccept -CC. frame &ith the assigned ;C address for
the device* Immediately after the ;LPHI, the 4Eport registers itself &ith the local name server
on the s&itch, indicating its AA44, AAP4, and assigned ;C address*
P!$t "!'i (PLOGI* is performed bet&een an 4Eport and another 4Eport to establish a
session*4Eport returns an CC to the initiator 4Eport* 4ext, the 4Eports exchange service
parameters relevant to the session*
P$!#ess "!'i (PRLI* is also performed bet&een an 4Eport and another 4E port* 6his login
relates to the ;C upper layer protocols -8LP. such as SCSI* 4Eports exchange SCSI","related
service parameters* 4Eports share information about the 8LP type in use, the SCSI initiator, or
the target*
3ONING,
Loning is an ;C s&itch function that enables nodes &ithin the fabric to be logically segmented
into groups that can communicate &ith each other*
P!$t F!i', It uses the ;C addresses of the physical ports to define 0ones* In port 0oning,
access to data is determined by the physical s&itch port to &hich a node is connected* 6he ;C
address is dynamically assigned &hen the port logs on to the fabric* 6herefore, any change in the
fabric configuration affects 0oning* Port 0oning is also called hard )oning* lthough this method
is secure, it reIuires updating of 0oning configuration information in the event of fabric
reconfiguration*
CCN F!i', It uses Aorld Aide 4ames to define 0ones* AA4 0oning is also referred to as
soft )oning* maOor advantage of AA4 0oning is its flexibility* It allo&s the S4 to be re"
cabled &ithout reconfiguring the 0one information* 6his is possible because the AA4 is static to
the node port*
Mi6ed F!i', It combines the Iualities of both AA4 0oning and port 0oning* 8sing mixed
0oning enables a specific port to be tied to the AA4 of a node*
=escribe basic architecture of
iSCSI
;CIP
;Co9

'i*e C"annel ove Et"enet -'CoE/
ne& protocol that maps ;ibre Channel protocol natively over 9thernet
;Co9 allo&s the use of multi"function net&or)Bstorage adapters called Converged 4et&or)
dapters -C4. consolidating both net&or) and storage traffic*
."at is 0it)ali1ation
!irtuali0ation is a techniIue of abstracting physical resources in to logical vie&
."at is a 2ack)$3
Cac)up is an additional copy of data that can be used for restore and recovery purposes
-)ll *ack)$ is a bac)up of the complete data on the production volumes at a certain point in
time* full bac)up copy is created by copying the data on the production volumes to a
secondary storage
device*
Incemental *ack)$ copies the data that has changed since the last full or incremental bac)up,
&hichever has occurred more recently* 6his is much faster because the volume of data bac)ed up
is restricted to changed data, but it ta)es longer to restore*
C)m)lative !$ ,i((eential *ack)$ #!pies the data that has changed since the last full bac)up*
6his method ta)es longer than incremental bac)up but is faster to restore*
Synt"etic !$ const)cte, ()ll *ack)$ is another type of bac)up that is used in implementations
&here the production volume resources cannot be exclusively reserved for a bac)up process for
extended periods to perform a full bac)up* It is usually created from the most recent full bac)up
and all the incremental bac)ups performed after that full bac)up* synthetic full bac)up enables
a full bac)up copy to be created offline &ithout disrupting the IBP operation on the production
volume* 6his also frees up net&or) resources from the bac)up process, ma)ing them available
for other production uses*
Rep"i#ati!,
Local and remote
Time-ide$
6ime;inder is a family of 9MC replication products that operate in a single Symmetrix array and
non"disruptively create and manage point"in"time copies of data volumes* 6ime;inder runs in
Symmetrix 9nginuity but is controlled by 6ime;inder soft&are running on an attached host* It
can be administered by the user through Solutions 9nabler Command Line Interface, Symmetrix
Management Console -SMC., 9MC Control Center -9CC. or Mainframe 9nablers* 6ime;inder
includes the follo&ing sets of products?
Time-ide$+Mi$$!$
6ime;inderBMirror is the original 6ime;inder product that has been in existence for about >+
years* It provides full copies of source volumes through a techniIue of hard&are mirroring* 6he
target volume for a 6ime;inderBMirror process is a Cusiness Continuance !olume -CC!.3 a
specially designated volume &ithin the Symmetrix configuration* Ahen a CC! is fully
synchroni0ed &ith a data device, the CC! is separated or split, and made available to a host for
bac)up or other host processes*
Full Copy Mode (MIRROR)
*n session start, the entire contents of the Source device is copied to the Target device in the
bac"ground
0ost vendor implementations provide the ability to trac" changes.
1 0ade to the Source or Target
1 Enables incremental resynchroni-ation
Time-ide$+C"!e
6ime;inderBClone provides single or multiple point"in"time copies of full volumes or individual
datasets* Cloned data is available to a host immediately upon activation, even if the copy process
has not completed*
4o invalid trac)s, 7ather than invalids to )eep trac) of syncing
8se Protected trac)s on Source
8se Indirect on 6arget
Pointer Based Full Volume Replication (CLO!)
+rovide full copy of source data on the target.
Target device is made accessible for business operation as soon as the replication session is
started
+ointinTime is determined by time of session activation
T!o modes
1 'opy on )irst Access (deferred)
1 )ull 'opy mode
Target device is at least as large as the source device
Time-ide$+Sap
6ime;inderBSnap provides pointer"only based replicas simultaneously on multiple target devices
from a single source device* Aith a space saving 6ime;inderBSnap only changed data is &ritten
to a pool of save devices* =ata reconstruction is from the source device and the pointers into the
change trac)ing save pool* =ata may be copied from a single source device to as many as >+1
target virtual devices*
Pointer Based Virtual Replication ("#P)
Targets (2dev) do not hold actual data, but hold pointers to !here the data is located (SA2 or
log) pool
1 Target re3uires a small fraction of the si-e of the source volumes
A replication session is setup bet!een source and target devices
1 Target devices are accessible immediately !hen the session is started
1 At the start of the session the target device holds pointers to data on source device typically
recommended if the changes to the source are less than 456
Time-ide$ C!siste#y G$!&ps
Set of devices &ith normal character in order to maintain integrity of database distributed in
multiple S7=; units*
BC $erminolo%ies (continued)
Recovery Point Obective (RPO)
+oint in time to !hich systems and data must be recovered after an outage
Amount of data loss that a business can endure
Recovery !i"e Obective (R!O)
Time !ithin !hich systems, applications, or functions must be recovered after an outage
Amount of do!ntime that a business can endure and survive
"ync&ronous Replication
,rite must be committed to source and replica before ac"no!ledging the host
"emi-sync&ronous Replication
,rite is committed to the source and immediately ac"no!ledged to the host
Secondary7 Adaptive copy 1,rite pending mode, dis" mode.
Concurrent, dynamic,domino,SRDF over I,SRDF-S!"R,SRDF#" , SRDF#"R$
C$ite1ba#7 #a#he, =ata is placed in cache and an ac)no&ledgment is sent to the host
immediately* Later, data from several &rites are committed -de"staged. to the dis)* Arite
responsetimes are much faster, as the &rite operations are isolated from the mechanical delays of
the dis)*%o&ever, uncommitted data is at ris) of loss in the event of cache failures*
C$ite1th$!&'h #a#he, =ata is placed in the cache and immediately &ritten to the dis), and an
ac)no&ledgment is sent to the host* Cecause data is committed to dis) as it arrives, the ris)s of
data loss are lo& but &rite response time is longer because of the dis) operations*
Least Re#et"y Used (LRU*? algorithm that continuously monitors data access in cache and
identifies the cache pages that have not been accessed for a long time* L78 either frees up these
pages or mar)s them for reuse* 6his algorithm is based on the assumption that data &hich hasnMt
been accessed for a &hile &ill not be reIuested by the host* %o&ever, if a page contains &rite
data that has not yet been committed to dis), data &ill first be &ritten to dis) before the page is
reused*
M!st Re#et"y Used (MRU*? n algorithm that is the converse of L78* In M78, the pages that
have been accessed most recently are freed up or mar)ed for reuse* 6his algorithm is based on
the assumption that recently accessed data may not be reIuired for a &hile*
Cate$ mas7i', ;lushing of data from cache, if its almost full
#ailover: sy"rd$ $ailover
0a"e copy of data on target Symmetrix volumes (89) available to
attached hosts
#ailback: sy"rd$ $ailback
8esumes operation using primary host and copy of data on source
volumes (8:)

P!2e$ Va&"ti' ,
/U Introduced in =MQ , to reduce system po&er do&n time
/U =uring po&er do&n, data from global memory is dumped into the po&er vault devices, this
process is called as vault save
/U once the po&er is bac) up, data from po&er vault devices &ill be copied to Hlobal Memory,
this process is called as vault restore
/U Capacity of P! devices is $HC, #*$ HC is used to store the data and remaining 2*$HC is for
future use
/U per = processor there &ill be #P! devices
/U P! devices are configured as first logical in the physical drive, so that it can be accessed
faster during po&er do&n**