1.

Veritas Storage Foundation Getting started Veritas Storage Foundation suite consists of volume management, file system management and data replication products. This document covers the volume management and file system only. This document outlines the basic administration tasks in command level and gui interface. 2. Veritas Storage Foundation Basics 2.1 Disk Configuration : Veritas volume management software manages the physical disks (Luns) to manage easily. Group of disk arrangements is called disk group . A disk should be part of a disk group to utilize under volume manager. 1. Initialize a disk : This process create private and public regions on disk 2. Assign to a disk group ( eg. Datadg01) 3. Assign disk space to a volume

2.2 Concatenated Layout: A volume consists of one or more subdisks to create a bigger volume. Data is written to one subdisk at a time. 100 % utilization of sub-disk.There is no redundancy part of these volumes. Eg datadg01, datadadg02 - disks datadadg01-01, datadadg02-03 - Subdisks datavol - Volume Name

Striped Volume: This layout allows data is splitted as small stripe units and written over multiple subdisks. This increase the performance for read access.

Mirrored layout: In this method, same data is written in parallel to two different plexes. Even one plex fails data is continue to be accessible using another plex.

Raid -5 layout: mechanism.

This layout also recoverable when one sub-disk fails. It uses Stripe with parity

Volume Management using VEA (GUI):

Following screen shots gives an overview of disk management using VEA utility.

Adding new Disk Group using VEA:

3.

Installation requirements: a minimum of 1167 MB space available in /opt file system a valid Veritas Storage Foundation license

Installation: 1. Mount the software CD 2. Software installation can be performed using pkgadd or installer utility comes with software suite. 3. Refer Vertias Storage Foundation installation suite.

4. Basic Volume Management can be performed with vxdiskadm utility. This utlity allow to initialize, add,remove, replace, mirror, assign spare and change disk naming conventions using this utility. Volume Manager Support Operations Menu: VolumeManager/Disk 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 list ? ?? q Add or initialize one or more disks Encapsulate one or more disks Remove a disk Remove a disk for replacement Replace a failed or removed disk Mirror volumes on a disk Move volumes from a disk Enable access to (import) a disk group Remove access to (deport) a disk group Enable (online) a disk device Disable (offline) a disk device Mark a disk as a spare for a disk group Turn off the spare flag on a disk Unrelocate subdisks back to a disk Exclude a disk from hot-relocation use Make a disk available for hot-relocation use Prevent multipathing/Suppress devices from VxVM's view Allow multipathing/Unsuppress devices from VxVM's view List currently suppressed/non-multipathed devices Change the disk naming scheme Get the newly connected/zoned disks in VxVM view Change/Display the default disk layouts List disk information Display help about menu Display help about the menuing system Exit from menus

Select an operation to perform:

5. Volume Management: Volume management in SLF environment requires better understanding of various storage technologies used. All the internal disks are managed by Solaris Disk Suite/Solaris Volume Management software. Only the SAN type of storages are managed by Veritas volume Manager. SAN Storage Attached Network. Most of the servers have 2 HBA attached to the SAN environment. There are 4 paths available to a LUN. However, Volume Management uses DMP ( dynamic multipathing) to map all the paths as one DMP path under volume manager. vxdisk list c2t500009720841A10Cd180 Device: c2t500009720841A10Cd180s2 devicetag: c2t500009720841A10Cd180 type: auto hostid: a01704 disk: name=dgzbmb4-05 id=1317151984.404.a01704 group: name=dgzbmb4 id=1317152084.406.a01704 info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2 flags: online ready private autoconfig noautoimport imported thinrclm pubpaths: block=/dev/vx/dmp/c2t500009720841A10Cd180s2 char=/dev/vx/rdmp/c2t500009720841A10Cd180s2 guid: {84c1f0c2-e93f-11e0-beef-002128b5e37c} udid: EMC%5FSYMMETRIX%5F000192604200%5F000158A008 site: version: 3.1 iosize: min=512 (bytes) max=2048 (blocks) public: slice=2 offset=65792 len=104787328 disk_offset=0 private: slice=2 offset=256 len=65536 disk_offset=0 update: time=1317193390 seqno=0.18 ssb: actual_seqno=0.0 headers: 0 240 configs: count=1 len=48144 logs: count=1 len=7296 Defined regions: config priv 000048-000239[000192]: copy=01 offset=000000 enabled config priv 000256-048207[047952]: copy=01 offset=000192 enabled log priv 048208-055503[007296]: copy=01 offset=000000 enabled lockrgn priv 055504-055647[000144]: part=00 offset=000000 Multipathing information: numpaths: 4 c2t500009720841A10Cd180s2 state=enabled

c3t500009720841A108d180s2 c2t500009720841A10Dd180s2 c3t500009720841A109d180s2 6. New LUN identification order

state=enabled state=enabled state=enabled

1. Run cfgadm -al, devfsadm -v to create device drivers in OS. 2. Run format < /dev/null | more to list the new LUNs eg. c3t500009720842AD51d54: configured with capacity of 84.00GB c3t500009720842AD51d61: configured with capacity of 249.83GB c3t500009720842AD51d62: configured with capacity of 199.68GB c3t500009720842AD69d54: configured with capacity of 84.00GB c3t500009720842AD69d61: configured with capacity of 249.83GB c3t500009720842AD69d62: configured with capacity of 199.68GB c4t500009720842AD6Dd54: configured with capacity of 84.00GB c4t500009720842AD6Dd61: configured with capacity of 249.83GB c4t500009720842AD6Dd62: configured with capacity of 199.68GB c4t500009720842AD55d54: configured with capacity of 84.00GB c4t500009720842AD55d61: configured with capacity of 249.83GB c4t500009720842AD55d62: configured with capacity of 199.68GB These type of entries will be listed on top of the format LUN list. There are 4 paths to each LUN. There are only 3 LUNs and 12 paths. Run format c3t500009720842AD51d54 and label the disk. Run vxdisk list | grep c3t500009720842AD51d54 Initialize LUN under Volume Manager eg. vxdisksetup -i c3t500009720842AD51d54 Adding a disk to an existing disk group or new diskgroup. Vxdg init <new dg name> <new-disk-name>=<new-LUN-name> Run vxdisksetup -i < LUN name> to initialize a disk or LUN

vxdg init newdg newdg-dsk01= c3t500009720842AD51d54 or Adding to an existing diskgroup vxdg -g abcdg adddisk abcdg-dsk01=c3t500009720842AD51d54 Create a volume : vxassist -g <diskgroupname> make <volname> <size> Eg. vxassist -g abcdg make abcvol01 5g

Veritas File Systems: This is flexible file systems. Easy to manage and fix.

vxresize -g atral11 -b -F vxfs -t u312resize vol03 200g atral1107 -t - Task name 200g - target size atral1107 disk name or vxresize -g atral11 -b -F vxfs vol03 +2g where 2g is the additional lun size to the existing volume. How to identify free space in a disk group vxdg -g atral11 free DISK DEVICE TAG OFFSET LENGTH FLAGS atral1101 SAN_VC0_32 SAN_VC0_32 356415488 1792 atral1102 SAN_VC0_34 SAN_VC0_34 314472448 1792 atral1103 SAN_VC0_38 SAN_VC0_38 41871360 1792 atral1104 SAN_VC0_43 SAN_VC0_43 52357120 1792 atral1105 SAN_VC0_44 SAN_VC0_44 52357120 1792 -

atral1106 atral1107 atral1108

SAN_VC1_31 SAN_VC1_31 251557888 1792 SAN_VC1_30 SAN_VC1_30 272873472 41600768 SAN_VC1_34 SAN_VC1_34 251858944 62615296 -

LENGTH column provides the free space in blocks.