Symmetrix DMX - Possible Questions for Interview

Can you explain about DMX Architecture Can you briefly explain about symmetrix series pro!ucts
Symmetrix 8000/4 was the first symmetrix to introduce a dual bus arcitecture, providing redundancy in the path to memory. Symmetrix D !800 is an incrementally scalable, high"end storage array which features modular dis# array enclosures. Symmetrix Direct atrix $rchitecture is storage array technology that employs a matrix of dedicated serial point"to"point connections instead of traditional buses or switches. Symmetrix D !% is a channel director specification for the D ! with faster processors and newer components. Symmetrix D !"& and D !"4 are the latest technology using redundant global memory and largest capacity.

Can you explain "n#inuity release co!e $%%&'%('$)

'( represents the D !&/4 )ardware (& represents the microcode family (* represents the field release level to the microcode '8 represents the field release to the service processor code '% +Symm4, '' +Symm', ', +D !/D !%, '( +D !&/4, '8 +- $!.

*ow many Cache !irectors+ ,ront-en! !irectors an! -ac.-en! !irectors we can use in DMX-/
.ache Directors + 4 in to 8 ax. /ront"end Directors + up to 0% max. 1ac#"end Directors + , in to 8 ax.

0hat are the !ifferent types of ,ront-en! !irectors an! the purpose of each one
2S.34 52$6 7 for mainframe attachment and S8D/ family lin#s /9.34 52/6 7 provides the industry:s highest performance connectivity 3ption for the
1

mainframe. /ibre 5/$/D$6 7 .onnectivity option for open systems direct and S$4 $ttachment, and can be used for S8D/ family remote 8eplication lin#s. iS.S9 5S26 7 ;rovides the industry:s first high"end 9scsi 9mplementation. <ig2 5826 7 for S8D/ family replication with compression support.

"xplain 1ule 2% in DMX

;ossible answers7 8ule of 0( ensured that /$s being used for host connectivity were in different power =ones. >he rule of 0( is simply a way to ma#e sure that the paths you connect your host to are not running on the same director, but one physically far away from it. >he original 8ule of 0( was put into place to ensure that there was a path on each bus 5odd and even6.>he bus architecture went away in D !"0 5 Symm,6. 1ut we had % power =ones? one =one for directors 0"8, and another =one for directors *"0,. So the 8ule of 0( still had value. but D98 & 5odd6 and D98 4 5even6 reside on different buses yet in the same power =one, so even if you had your host connected to & and 4 ..if that power =one went down ..@our hosts went down.

0hat are the Mana#ement 3ools for DMX

Symcli 5Symmetrix .ommand Aine 9nterface6 S . 5Symmetrix anagement .onsole6 2.. 52 . .ontrol .enter6

0hat are the "n#inuity 4perational 5ayes

Symmetrix 1ased $pplication )ost 1ased Symmetrix $pplication 9ndependent Software vendor application 2 . Solutions 2nabler $;9 Symmetrix 2nginuity 3perating 2nvironment /unctions Symmetrix )ardware

0hat are the ma6or components of System -ay an! Stora#e -ay in DMX
System 1ay .omponents7 2ither six or eight dis# directors and up to 0% channel directors 5.ombined total + 0,6. /rom four to eight global memory directors.
2

Bp to eight power supplies, each of having a dedicated 1attery 1ac# Bp511B6 0B service processor with C- 5#eyboard, video screen and mouse6 and dedicated B;S. >hree cooling fan assemblies 5each containing & fans6. Storage 1ay .omponents7 0%0 or %40 dis# drives per storage bay 2ach Drive 2nclosure 5D26 includes7 >wo lin# control cards 5A..6. 8edundant power supplies with 11Bs to provide standby power. >he D !"4 storage bay has %4 power =ones with independent power cables, each =one capable of powering the fully configured storage bay. >he storage bay can be populated with various combinations of currently available D ! one" inch low"profile 4 <b/s /ibre .hannel dis# drives available in7 (& <1, 04, <1, &00 <1, and 400 <1 /ibre .hannel drives (& <1 and 04, <1 /lash drives '00 <1 and 0 >1 S$>$ 99 dis# drives

Can you explain about 1ea! *it+ 1ea! Miss an! ,ast 0rite an! Delaye! 0rite
8ead )it7 9n a read hit operation, the reDuested data resides in global memory. >he channel director transfers the reDuested data through the channel interface to the host and updates the global memory directory. Since the data is in global memory, there are no mechanical delays due to see# and latency. 8ead iss7 9n a read miss operation, the reDuested data is not in global memory and must be retrieved from a dis# device. Ehile the channel director creates space in the global memory, the dis# director reads the data from the dis# device. >he dis# director stores the data in global memory and updates the directory table. >he channel director then reconnects with the host and transfers the data. because the data is not in global memory, the symmetrix system must search for data on the dis# and then transfer it to the channel adding see# and latency times to the operation. /ast Erite $ fast write occurs when the percentage of modified data in global memory is less than the fast write threshold. 3n a host write command, the channel director places the incoming bloc#s directly into global memory. /or fast write operations, the channel director stores the data in global memory and sends a Fchannel endG and Fdevice endG to the host computer. >he dis# director then asynchronously destages the data from global memory to the dis# device. Delayed /ast Erite7 $ delayed fast write occurs only when the fast write threshold has been exceeded. >hat is the percentage of global memory containing modified data is higher than the fast write threshold. 9f this situation occurs, the symmetrix system disconnects the channel directors from the channels. >he dis# director then de"stages the data to dis#. Ehen sufficient global memory space is available. >he channel directors reconnect to their channels and process the fast 9/3 reDuires as a fast write. >he symmectrix system continues to process read operations during delayed fast writes with sufficient global memory present, this type of global memory operation rarely occurs.
3

*ow !o you calculate number of cylin!ers for 278 9- 5:;

aximum device si=es by 2nginuity version 2nginuity version7HHHHHHHHHH7 1s7HHHHHHH7.@As7HHHHHH7<1s 2nginuity '8(47HHHHHHHHHHHHH7%4'(,07HHHH7%,%,,87HHHH7%40 2nginuity '((& and earlier7H7,04%'7HHHHH7,''%07HHHHH7'* Since D !"4 supports maximum of ,0<1 hyper si=e, we have to create two hypers and form a eta devices as 0%0<1 AB4. >o calculate cylinders for ,0<1 AB4 use the below formula .ylinders + ,0<1/0' trac#sI 8 sectorsI 0, bloc#s I '0% bytes .ylinders + ,0000000000/0'I8I0,I'0% .ylinders + ,0000000000/*8&040 .ylinders + ,00&' cyl >o calculate the number of cylinders 5for pre"Symmetrix D !6, use either of the following7 bloc#s J *,0 or 5si=e in megabytes6 x %.0&&& >o calculate the number of cylinders 5for Symmetrix D ! and Symmetrix -" ax arrays6, use the following7 0 cylinder + 0' trac#s? each trac# is ,4 C1, 0' x ,4 trac#s + .*&( 1 for each cylinder

0hat is the maximum hyper si<e in DMX-/

aximum .ylinders + ,''%0 aximum .apacity + '*<1 or ,04%' 1

*ow many hypers can create in a Sin#le !is. in DMX/

%'' hypers per dis#.

*ow many members can contain in one Meta

0 eta head K %'' members

*ow many 5:; IDs available per ,A port

%', AB4 9Ds are available per /$ port, %'' AB4 9Ds are usable out of %',.

0hat is Dynamic 5:; a!!ressin#

>his feature will automatically selects and assigns the AB4 9Ds to the devices while device mapping to the port 9nstead of manually assigning address to the device while mapping
4

*ow !o you a!! a new member to the existin# Meta

add dev !!!! to meta !!!!, protectHdata+>8B2, bcvHmetaHhead+!!!!? or for multiple ranges7 add dev !!!07!!!, to meta !!!!, protectHdata+>8B2, bcvHmetaHhead+!!!!?

0hat is strippin# an! what is Concatenatin#

Stripped eta Devices7 eta device addressing by striping divides each eta member device into a series of stripes, addressing a stripe from each device before advancing to the next stripe on the first device. Ehen writing to a striped volume, eDual si=e stripes of data from each participating drive are written alternately to each member of the set. .oncatenated eta Devices7 .oncatenated devices are volume sets that are organi=ed with the first byte of data at the beginning of the first device. $ddressing continues to the end of the first device before any data on the next device is referenced. Ehen writing to a concatenated device, the first meta device member receives all the data until it is full, and then data is directed to the next member and so on

0hat are the DMX-/ supporte! !is. types+ no' of !is.s an! maximum capacity
/. drives, iS.S9 drives and /lash drives 0' drives per D$2 0%0 drivers per .age %40 drives per Storage 1ay %400 drives per array 9f total of 00 storage bays connected aximum storage capacity is 0 ;1.

-riefly explain the DMX-/ supporte! Device types

Standard Devices7 $ Symmetrix device configured for normal Symmetrix operation under a desired protection method 5such as 8$9D"0,8$9D"S, and S8D/L6. <ate#eeper Devices7 S.S9 commands executed by S@ $;9 are transferred to the Symmetrix array via a Symmetrix device that is designated as a <ate#eeper device. >he gate#eeper allows you to retrieve configuration and status information from the Symmetrix array without interfering with normal device 9/3 operations. eta Devices7 $llow individual devices to be concatenated to create larger devices. 1.- Devices7 Speciali=ed devices used to create a local copy of data contained in a standard Symmetrix device, which can be used for bac#up, restore, decision support, and application testing.
5

S8D/ Devices 580, 8% and 8%06 Devices configured as 8D/0 or 8D/% to support S8D/ operations. 80 is source device for S8D/ operations 8% is target device for S8D/ operations 8%0 is used for multi hop S8D/ operations -irtual Devices7 $ host"accessible device containing trac#"level location information 5pointers6, which indicates where the copy session data is located in the physical storage. Device copies use virtual devices to support >ime/inder/Snap operations. -irtual devices consume minimal physical dis# storage, as they store only the address pointers to the data stored on the source device or a pool of save devices., Save Devices7 Special devices 5not mapped to the host6 that provide physical storage space for pre"update images or changed trac#s during a virtual copy session of >ime/inder/Snap operations. Device as#ing 5-. 6Devices7 Symmetrix devices that have been mas#ed for visibility to certain hosts. >he device mas#ing database 5-. D16 holds device mas#ing records and typically resides on a %4 or 48 cylinder dis# device.. D8- Devices7 $ non"user"addressable Symmetrix device used by the Symmetrix 3ptimi=er to temporarily hold user data while reorgani=ation of the devices is being executed. >ypically, it is used by the 3ptimi=er in logical volume swapping operations.

0hat is =ault !rives an! *ot Spare

-ault Drivers7 $t the time of emergency shutdown of an $rray, what ever the data in cache memory will be destaged/saved on temporary drives called vault drives )ot Spare7 $t the time of physical drive failure hot spare drives will ta#e place

0hat is Preview+ Prepare an! Commit while usin# Symconfi#ure comman!

>he preview argument verifies the syntax and correctness of each individual change defined, and then terminates the session without change execution. >he prepare argument performs the preview chec#s and also verifies the appropriateness of the resulting configuration definition against the current state of the Symmetrix array? the argument then terminates the session without change execution >he commit argument completes all stages and executes the changes in the specified Symmetrix array

0hat are the possible !evice service states an! !evice status states
Device Service States 7 4ormal, /ailed and Degraded Device Status States 7 8eady, 4ot 8eady and Erite Disable.

*ow !o you reserve the !evices

symconfigure "sid !!!! "f createdev.cmd "expire expiration date"owner myself "comment Mthis devices are reserved for S8D/ activityM reserve

*ow !o you create the Dis. 9roups

Ee can not create Dis# <roups, 9t should be done by changing 194 file by .2. Ee can rename the existing dis# groups. 2xample7 symconfigure "sid %0( "cmd Fset dis#Hgroup 4 dis#HgroupHname + flashHds#s?G "v "nop commit

*ow !o you chec. the free space by Dis. #roup an! Array as whole
1y Dis# <roup 7 Symdis# "sid !!!! list "byHdis#group $rray as whole 7 Symconfigure "sid !!!! list "freespace

*ow !o you chec. the total assi#ne! !evices to a particular *ost

Symmas#db "sid !!!! list devs "wwn Mhost hba wwnM

*ow !o you chec. the total allocate! stora#e of a particular *ost

symmas#db "sid !!!! list capacity ")ost hostname

0hat is pre chec. list to assi#n stora#e to the host

7

-erify the available free space in the symmetrix array symconfigure "sid Symm9D N"v O "freespace N"units cylinders O symdis# "sid MSym9DM list "dis#Hgroup M<roup4umberM -erify the Symmetrix status Symconfigure "sid MSym9DM verify 9f any hung activities found abort symconfigure "sid MSym9DM abort

1PP list

"xplain step by step proce!ure to provi!e stora#e to the *ost

0. .reating S>D device %. eta Device .reation &. apping 4. as#ing 2xample7 .reate a commandfile with the following entry to create hypers. .reate dev count+8, si=e+0%&*4, emulation+/1$, config+%"way"mir, dis#Hgroup+%? 2xecute the command file using symconfigure command with preview, prepare and commit options. Symconfigure "sid MSym9DM "f .ommandfile.cmd "v "noprompt commit -erify the newly created devices symdev "sid MSym9DM list "noport .reate a commandfile with following entry to form metas and devices to the meta head. /orm meta from dev %,.$, config+striped, stripeHsi=e+0*%0? add dev %,.17%,24 to meta %,ca? 2xecute the command file using symconfigure command with preview, prepare and commit options. symconfigure "sid MSym9DM "f .ommandfile.txt "v "noprompt commit -erify the newly created meta devices symdev "sid MSym9DM list "noport /ind the host connected Director and ;ort details symcfg "sid 4%8% list "connections /ind the available addresses on that port symcfg "sid MSym9DM list "address "available "dir (d "p 0 .reate a commandfile with the following entry to map the device to the /$ port
8

map dev %,ca to dir (d70, lun+0&,? 2xecute the commandfile using symconfigure with the preview, prepare and commit options. Symconfigure "sid 4%8% "f .ommandfile.txt "v "noprompt commit as# the devices to the host )1$ and refresh the sym configuration symmas#db "sid MSym9DM "wwn 00000000c*&f,%cf "dir (d "p 0 add devs %,ca "nop Symmas# "sid MSymiDM "refresh 8escan the dis#s and refresh the powerpath or reboot the server to get the assigned devices at host"end

*ow !o you chec. particular !evice #eometry

symdev "sid !!!! show dev 00%.

*ow !o you chec. the particular !evice is connecte! to which *ost

symmas#db "sid !!!! list assignment "dev 00%c

0hat are the steps for stora#e reclamation

Bnmas#ing Erite Disable Bn"mapping Dissolve meta Deleting hypers 0. Bnmas#ing devices from the host symmas#db "sid 4%8% "wwn 00000000c*&f,%cf "dir (d "p 0 remove devs %,ca %. 8efresh the Symmetrix $rray Symmas# "sid 4%8% "refresh &. Erite Disable the devices before unmapping from the Director port symdev "sid 4%8% writeHdisable %,ca "sa (d "p 0 "noprompt 4. .reate a cmd/txt file Bnmap dev %,ca from dir all7all? '. ;erform preview operation using symconfigure command Symconfigure "sid 4%8% "f unmap.txt "v "nop preview ,. ;erform prepare operation using symconfigure command Symconfigure "sid 4%8% "f unmap.txt "v "nop prepare

(. ;erform .ommit operation using symconfigure command Symconfigure "sid 4%8% "f unmap.txt "v "nop commit 8. -erify that the device has been unmapped Symdev "sid 4%8% list "noport *. >o Dissolve meta, create a cmd/txt file Dissolve meta dev %,ca? 00. ;erform preview operation using symconfigure command Symconfigure "sid 4%8% "f dissolve.txt "v "nop preview 00. ;erform prepare operation using symconfigure command Symconfigure "sid 4%8% "f dissolve.txt "v "nop prepare 0%. ;erform .ommit operation using symconfigure command Symconfigure "sid 4%8% "f dissolve.txt "v "nop commit 0&. -erify that the meta has been Dissoved. Symdev "sid 4%8% list "noport 04. >o delete the hypers create a cmd/txt file. Delete dev %,ca? 0'. ;erform preview operation using symconfigure command Symconfigure "sid 4%8% "f dissolve.txt "v "nop preview 0,. ;erform prepare operation using symconfigure command Symconfigure "sid 4%8% "f dissolve.txt "v "nop prepare 0(. ;erform .ommit operation using symconfigure command Symconfigure "sid 4%8% "f dissolve.txt "v "nop commit 08. -erify that )ypers have been deleted. Symdev "sid 4%8% list "noport

*ow many mirror positions 1AID-2 an! 1AID-$ will occupy

8$9D"0 occupies % mirror positions 8$9D"' occupies % mirror positions

*ow !o you convert the concatenatin# meta !evice to strippe! meta

10

convert meta !!!!, config+striped, stripeHsi=e+0*%0, protectHdata+>8B2, bcvHmetaHhead+!!!!?

*ost is unable to see the stora#e+ how !o you troubleshoot

.hec# that the host is logged in to the $rray .hec# that the cable connectivity status by logging in to the host .hec# that the )1$ drivers are properly configured .hec# the Qoning table by logging in to the switch .hec# that the devices status in $rray .hec# the -. D1 for mas#ing information, etc..

0hat is 3hin Provisionin#

>hin provisioning is a method of optimi=ing the efficiency with which the available space is utili=ed in storage area networ#s. >hin provisioning operates by allocating dis# space in a flexible manner among multiple users, based on the minimum space reDuired by each user at any given time.

*ow !o you create thin pools an! thin !evices

.reating >hin ;ools .reating Data devs and added these Data devs to >hin ;ools .reating >D2-s and bind these >D2-s to >hin ;ool $ssign >D2-s to host.

"xplain step by step proce!ure to setup new host

Aet us assume cable connectivity is done properly 9nstall )1$ drivers in host. 9nstall ;ower path if reDuired. .hec# that the )1$ ports are showing online .reate =oning at switch end. .hec# that this host is logged in to the Storage array .reate AB4/hypers in storage array /orm meta devices if reDuired ap the devices to the /$ port. as# the devices to the host hba 5wwn6. 8efresh the $rray to affect the changes.

*ow !o you chec. the faile! components in Symmetrix Array

11

Symcfg "sid 0'0 list "envHdata "serviceHstate failed

*ow !o you chec. the faile! !is.s in the Symmetrix Array

Symdis# "sid !!!! list "failed

0hat is the purpose of 9ate >eeper !evice

Aow"level 9/3 commands executed using S@ .A9 are routed to the Symmetrix array by a Symmetrix storage device that is specified as a gate#eeper. >he gate#eeper device allows S@ .A9 commands to retrieve configuration and status information from the Symmetrix array without interfering with normal Symmetrix operations. >he gate#eeper must be accessible from the host where the commands are being executed.

*ow many #ate .eeper !evices are re?uire! per Array

9t depends on the Symmetrix management applications using in management servers, $s per 2 . recommendations , gate#eepers are reDuired per management host using symcli

*ow to list hosts an! their "MC re#istere! software+ usin# Solutions "nabler
Symcfg "sid !!!! list "applications

0hat is =CMD- an! how !o you ta.e the bac.up

>he device mas#ing database 5-. D16 holds device mas#ing records and typically resides on a %4 or 48 cylinder dis# device.. Symmas#db "sid !!!! bac#up "f filename

*ow !o you list the *osts which are connecte! to particular !irector port
Symmas#db "sid !!!! list database "dir !! "p !

*ow !o you chec. the number of stora#e bays connecte! to the system bay an! number of !is.s in each stora#e bay
Symcfg "sid !!!! list "envHdata

*ow !o chec. the !evices which are not mappe! an! mas.e!
Symdev "sid 4%8% list dev "noport

*ow !o you chec. the !evices which are mappe! to ,A but not mas.e! to any host
12

Symmas#db "sid 0%& list noHassignment "dir $AA "p $AA

*ow !o you chec. the lo#in hosts in the Symmetrix Array

Symmas# "sid 4%8% list logins

*ow to !isplay an! set the Symmetrix metrics

Symcfg "sid !!!! "S$ all list "v Set Symmetrix atric4ame+ atric-alue

*ow !o you chec. the confi#ure! environmental variables

Symcli "def

Can win!ows+ 5inux+ Solaris share the same ,A in DMX

@es, if they share the same port flags

0hat are the Symmetrix "xternal loc.s an! how to chec. an! release
Symmetrix external loc#s are used by S@ $;9 5loc#s 0 to 0'6 and also for applications assigned by 2 . 5R0'6 to loc# access to the entire Symmetrix arrayduring critical operations Ee can chec# the external loc#s by giving the below command symcfg "sid !!!! list "loc#n Ee can chec# the external loc#s by giving the below command symcfg release "sid "loc#n 0' "force

*ow to monitor performance of "MC Symmetrix *ow !o you chec. the cache activity of front-en! !irectory
symstat "sid 4%8% "type cache "i ' "c 4 "sa all

*ow !o you chec. the I@4 re?uests an! throu#hput of selecte! !is.
Symstat "sid 4%8% "type dis# "i ' "c & "dis# %a,.,'

0hat are the available performance types in SAMS3A3 comman!

82SB2S>S7 8eports 9/3 reDuests and throughput for selected devices, directors, or S8D//$ sessions. 5>his is the default type? if no type is specified 82SB2S>S is used.6 1$.C24D7 8eports bac#"end 9/3 reDuests and throughput for selected devices.
13

;38>7 8eports performance statistics for a director port. 9S.S9 8eport <ig"2 networ# statistics. .$.)27 8eports cache activity for selected front"end or remote lin# directors, or S8D//$ sessions. 2 937 8eports cache memory to dis# activity for selected devices. ;$>) 8eport 8".opy path information for nonincremental sessions. Symmetrix arrays that have all or some incremental sessions will report an error. .@.A27 8eport cycle summary information for S8D/"$ sessions. D9SC7 8eports bac#"end 9/3 reDuests and throughput for selected dis#s. ;82/2>.)7 8eports trac# prefetch dis# activity for selected bac#"end directors only.D S; 8eports dynamic mirroring service policy 5D S;6 statistics for the selected device5s6. 8D/7 8eports S8D/ statistics from the perspective of 8$ groups, devices, or directors.

0hat is symmetrix optimi<er an! how it wor.s

Symmetrix 3ptimi=er improves array performance by continuously monitoring access patterns and migrating devices 5Symmetrix logical volumes6 to achieve balance across the dis#s in the array Step 07 Symmetrix 3ptimi=er builds a database of device activity statistics on the Symmetrix bac#"end. Step %7 Bsing the statistical data collected, configuration information, and the user"defined parameters, the 3ptimi=er algorithm identifies busy and idle devicesand their locations on the physical drives. >he algorithm tries to minimi=e average dis# service time by balancing 9/3 activity across physical dis#s. 3ptimi=er determines which dis#s reDuire balancing by locating busy devices close to each other on the same dis#, and/or by locating busy devices on faster dis#s or faster areas of the dis#s. 3ptimi=er ta#es into account the speed of the dis#, the dis# geometry, and the actuator speed to determine faster dis#s. Step &7 3nce a solution for load balancing has been developed, the next phase is to carry out the Symmetrix device swaps. >his is done using established >ime/inder technology, which maintains data protection and availability. we can specify whether swaps should occur in a completely automated fashion, or if the device swaps reDuire user approval before the action is ta#en. Step 47 3nce a swap function completes, Symmetrix 3ptimi=er continues data analysis for the next swap.

0hat is Symmetrix QoS an! how it wor.s

14

Suality of Service 5SoS6 allows more flexibility in managing Symmetrix system:s performance. 1y increasing the response time for specific copy operations on selected devices, we can increase the overall performance of the other Symmetrix devices. >he SoS 5Suality of Service6 feature allows us to adTust the data transfer pace on specified devices, or devices in a device group, for certain operations. >he contention for cache access can be Duality of service managed by the least recently used 5A8B6 ring partitions in the Symmetrix cache. Ee can control the priority service time of devices and control cache partitions for different device groupings.

0hat is the purpose of Symmetrix Chan#e 3rac.er

>o measure changes to data on a Symmetrix volume or group of volumes. .hange >rac#er data is often used to analy=e and design >ime/inder and Symmetrix 8emote Data /acility 5S8D/6 configurations. .hange >rac#er 5Delta ar#6 session must be created using the symchg create command. >he symchg mar# command is then used to perform a timestamp and mar# the selected area of dis# storage occupied by a data obTect using a Delta ar# bitmap

0hat is Dynamic Cache Partitionin#

$ SoS feature, dynamic cache partitioning allows the $dministrator the means to dynamically control the cache area si=e, servicing a given device group 9/3, by defining flexible partitions through cache memory. Dynamic .ache ;artitioning divides the cache memory into multiple partitions with uniDue names and their device path assignments. ;artition areas can be made static or dynamic in si=e. >he dynamic partitioning provides flexibility to the amount of floating memory that can be allocated with a high and low watermar#. >his allows memory resources to be temporarily donated to other partitions when needed. >he symDos command allows you to create partitions for different device groupings in addition to the default partition that all devices belong to initially. 2ach partition will have a target cache percentage as well as a minimum and maximum percentage. 9n addition, you can donate unused cache to other partitions after a specified donation time.

0hat are the lo#s available at host-en! an! on symmetrix array

15

)ost"end logs are available in USymapiUlog folder 2vent logs and $udit logs in symmetrix array

*ow !o you monitor the real time events on symmetrix array with example
>o monitor real time 000 event records with ,00 seconds interval in the symmetrix array Symevent "sid 4%8% monitor "i ,00 "c 000 "warn/"error/"fatal

*ow !o you trac. the history of events on symmetrix array with example
>o list all events in symmetrix array Symevent "sid 4%8% list >o list specific period of time events in event logs Symevent "sid 4%8% list "v "start *700 "end 0(700

*ow !o you chec. the au!it lo#s on symmetrix array

>o show the details about audit log it self. Symaudit "sid 4%8% show >o list the audit log records of specific period of time. Symaudit "sid 4%8% list "v "startHtime (/007*700 "endHtime (/00700700 >o monitor the real time audit logs 000 records with &0sec interval. symaudit "sid 4%8% monitor "i &0 "c 000

0hat is Symmetrix AC5

>o create access control list on symmetrix array to implement host level or user level security.

"xplain step by step to setup the access controls on symmetrix array

.reate $ccess <roup7 5.reate a command file with the following entries6 .reate accgroup $ccess<roup4ame? 52xecute the command file6 Symacl "sid 4%8% commit "file commandfile $dd host access 9D or user access 9D to access group7 5.reate a command file with the following entries6 $dd host accid 9d name 9dname to accgroup <roup4ame? $dd user accid 9d name 9dname to accgroup <roup4ame? 52xecute the command file6 Symacl "sid 4%8% "file M.ommand/ile4ameM commit
16

.reate $ccess ;ools7 5.reate a command file with the following entries6 .reate accpool $ccess;ool4ame? 52xecute the command file6 Symacl "sid 4%8% commit "file McommandfileM $dd devices to the access pool 5.reate a command file with the following entries6 $dd dev StartDev4ame72ndDev4ame to accpool $ccess;ool4ame? 52xecute the command file6 Symacl "sid 4%8% commit "file McommandfileM <rant 8ights to $ccess <roups7 5.reate a command file with the following entries6 <rant access+1ase/1.-/8D/ to accgroup $ccess<roup4ame to accpool $ccess;ool4ame? 52xecute the command file6 Symacl "sid 4%8% commit "file McommandfileM

*ow !o you ta.e the bac.up@restore of AC5s

Symacl "sid 4%8% bac#up "file McommandfileM Symacl "sid 4%8% commit "restore "f commandfile

0hat is Symmetrix :ser Authori<ation

Set up or update the Symmetrix array user authori=ation information

"xplain step by step proce!ure to setup user authori<ation on symmetrix array

Bser"to"role mappings have to be created7 5.reate a command file with the following entry 5ex7rolemap.txt66 $ssign user )7)ostUusername to role onitor? $ssign user D72ngUusername to role $dmin? 52xecute the above file6 Symauth "sid 4%8% "f rolemap.txt commit. 58oles7 4one, onitor, Storage admin, admin, $uditor, Security$dmin6 2nable the user authori=ation7 Symauth "sid 4%8% enable

*ow !o you perform bac.up an! restore user authori<ation information

Symauth "sid 4%8% bac#up "f bac#upfile.cmd commit Symauth "sid 4%8% restore "f bac#upfile.cmd commit

0hat is the purpose of bin file in SAMAPI !atabase

17

9t is a database file in the host which stores the symmetrix array:s configuration data. .an be used to get the configuration data offline.

*ow !o you prepare the Stora#e Capacity plannin# reports by host wise
0. 1y using 2 . .ontrol .enter %. 1y using symcli commands symcfg and symdis# Symcfg "sid 4%8% list "connections "capacity .opy and past the output of the above command in excel file and format according to the reDuirement. 3r Symdis# "sid 4%8% list "byHdis#group .opy and past the output of the above command in excel file and do the format according to the reDuirement.

-y usin# what symcli comman! we can chec. the *-A !etails

SyminD hba "fibre

0hat are the business continuity tools for symmetrix array

;ower path " host end >ime/inder " local replication S8D/ " 8emote 8eplication

18