DMX-4 Storage Provisioning Step by Step

Step by Step Procedure for storage provisioning & Reclamation in DMX-4 Storage Provisioning

1. 2. 3. 4. 1. 2. 3. 4. 5.

Creating STD device Forming Meta Device Mapping Masking Unmasking Write Disable Un-mapping Dissolve meta Deleting hypers

Storage Reclamation

Step by Step Procedure for storage provision in DMX-4 Creating STD device Verify the Symmetrix status

1.

symconfigure sid 4282 verify If any hung activities found abort symconfigure sid 4282 abort Verify the available free space symconfigure -sid SymmID [-v | -freespace [-units cylinders | MB]] list or symdisk sid 4282 list disk_group 2 Create Command file Create dev count=8, size=12394, data_member_count=3, emulation=FBA, config=RAID-5, disk_group=2; Verify the command line syntax by performing PREVIEW usingSymconfigure command Symconfigure sid 4282 f Create_hypers.txt v noprompt preview Verify the Array readiness by performing PREPARE usingSymconfigure command Symconfigure sid 4282 f Create_hypers.txt v noprompt prepare Execute COMMIT using Symconfigure command Symconfigure sid 4282 f Create_hypers.txt v noprompt commit

Verify the newly created devices Symdev sid 4282 list noport

2.

Forming Meta Device Verify the Symmetrix status

symconfigure sid 4282 verify If any hung activities found abort

symconfigure sid 4282 abort Create Command file

Form meta from dev 26CA, config=striped, stripe_size=1920; add dev 26CB:26E4 to meta 26ca; Verify the command line syntax by performing PREVIEW usingSymconfigure ommand Symconfigure sid 4282 f meta.txt v noprompt preview Verify the Array readiness by performing PREPARE usingSymconfigure command Symconfigure sid 4282 f meta.txt v noprompt prepare Execute COMMIT using Symconfigure command

Symconfigure sid 4282 f meta.txt v noprompt commit Verify the newly created meta devices

Symdev sid 4282 list noport

3.

Mappping

Find the host connected Director and Port details symcfg sid 4282 list connections Find the available addresses on that port

symcfg sid 4282 list address available dir 7d p 0 Create a command file for mapping

map dev 26ca to dir 7d:0, lun=036; Verify the command line syntax by performing PREVIEW using

Symconfigure command symconfigure sid 4282 f create_hypers.txt v nop preview Verify the Array readiness by performing PREPARE using

Symconfigure command symconfigure sid 4282 f create_hypers.txt v nop prepare Execute COMMIT using Symconfigure command

symconfigure sid 4282 f create_hypers.txt v nop commit Check the device have been mapped

symcfg sid 4282 list address available dir 7d p 0

4.
nop

Mappping Masking devices to the host

symmaskdb sid 4282 wwn 10000000c93f62cf dir 7d p 0 add devs 26ca Symmask sid 4282 refresh Check whether devices have masked

symmaskdb -sid 4282 list database -dir 7d -p 0

Step by Step Procedure for Storage Reclamation

1.

Unmasking Unmasking devices from the host

symmaskdb sid 4282 www 10000000c93f62cf dir 7d p 0 remove devs 26ca Refresh the Symmetrix Array

Symmask sid 4282 refresh

2.

Write Disable Write Disable the devices before unmapping from the Director and from port

symdev -sid 4282 write_disable 26ca -sa 7d -p 0 -noprompt

3.

Un-mapping Create a cmd/txt file with the following line

Unmap dev 26ca from dir all:all; Perform preview operation using symconfigure command

Symconfigure sid 4282 f unmap.txt v nop preview Perform prepare operation using symconfigure command

Symconfigure sid 4282 f unmap.txt v nop prepare Perform Commit operation using symconfigure command

Symconfigure sid 4282 f unmap.txt v nop commit Verify that the device has been unmapped

Symdev sid 4282 list -noport

4.

Dissolve meta To Dissolve meta create a cmd/txt file with the following line

Dissolve meta dev 26ca; Perform preview operation using symconfigure command

Symconfigure sid 4282 f dissolve.txt v nop preview Perform prepare operation using symconfigure command

Symconfigure sid 4282 f dissolve.txt v nop prepare Perform Commit operation using symconfigure command

Symconfigure sid 4282 f dissolve.txt v nop commit Verify that the meta has been Dissoved.

Symdev sid 4282 list noport

5.

Deleting hypers To delete the hypers create a cmd/txt file with the following line.

Delete dev 26ca:26d1; Perform preview operation using symconfigure command

Symconfigure sid 4282 f dissolve.txt v nop preview Perform prepare operation using symconfigure command

Symconfigure sid 4282 f dissolve.txt v nop prepare Perform Commit operation using symconfigure command

Symconfigure sid 4282 f dissolve.txt v nop commit Verify that Hypers have been deleted.

Symdev sid 4282 list -noport -------------------------------------------- E N D ------------------------------------------Command Line Syntax for creating devices create dev count=n, size=Cylinders, size = <n> [MB | GB | CYL], emulation=EmulationType, config=DeviceConfig,[, data_member_count=nn] [, remote_config=DeviceConfig, remote_data_member_count=nn,

ra_group=n, [remote_mvs_ssid=nnn], [dynamic_capability=[dyn_rdf | dyn_rdf1_only | dyn_rdf2_only], ] [, mvs_ssid=nnn] [, attribute=ckd_meta | savedev |datadev, [in pool PoolName] [member_state=ENABLE | DISABLE], ] [, disk_group_num=nnn, remote_disk_group_num=nnn]] [meta_member_size = n [MB |GB| CYL]] [meta_config = [striped | concatenated]] [, binding to pool = PoolName, [preallocate size = n [MB |GB |CYL]] [remote_pool = PoolName]];

Command Line Syntax for Forming Meta devices form meta from dev SymDevName, config=MetaOption [, stripe_size=<MetaStripeSize>[cyl]] [, count=<member_count>]; where: config = the meta configuration type. Possible values are concatenated or striped. stripe_size = the size of the striped meta device. This value can be expressed in blocks or cylinders. Possible sizes in 512 byte blocks are 1920, 3840, 7680, 15360, 30720, and 61440. If you do not specify a stripe size when creating a striped meta, two cylinders will be assigned. For information on meta volume strip sizes, cyl = if the stripe_size is expressed in cylinders, include cyl with theMetaStripeSize value. The size of a cylinder for FBA emulation is 960 512-byte blocks. count = the total number of devices for the configuration server to add to the new meta device, including the head. This option may be omitted if you want to specify the members using the add dev command. Adding a meta member add dev SymDevName[:SymDevName] to meta SymDevName [, protect_data=[TRUE | FALSE], bcv_meta_head=SymDevName]; Brief Description about meta devices Concatenated Meta Devices Concatenated devices are volume sets that are organized with the first byte of data at the beginning of the first device. Addressing continues to the end of the first device before any data on the next device is referenced. When 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 Stripped Meta Devices Meta device addressing by striping divides each meta member device into a series of stripes, addressing a stripe from each device before advancing to the next stripe on the first

device. When writing to a striped volume, equal size stripes of data from each participating drive are written alternately to each member of the set.

Symconfigure Preview, Prepare and Commit The preview argument verifies the syntax and correctness of each individual change defined, and then terminates the session without change execution. The prepare argument performs the preview checks 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 The commit argument completes all stages and executes the changes in the specified Symmetrix array