0% found this document useful (0 votes)
145 views10 pages

Veritas Volume Manager

The vxconfigd daemon maintains the Veritas Volume Manager configuration state in the kernel and disk private regions. It can be in one of three states: enabled, disabled, or booted. The vxrelocd daemon monitors for failure events and relocates failed subdisks. The vxnotify utility displays Veritas Volume Manager events. The kernel can also be in three of three states that determine if the private and public regions are accessible.

Uploaded by

animeshdoc
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
145 views10 pages

Veritas Volume Manager

The vxconfigd daemon maintains the Veritas Volume Manager configuration state in the kernel and disk private regions. It can be in one of three states: enabled, disabled, or booted. The vxrelocd daemon monitors for failure events and relocates failed subdisks. The vxnotify utility displays Veritas Volume Manager events. The kernel can also be in three of three states that determine if the private and public regions are accessible.

Uploaded by

animeshdoc
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 10

Veritas Volume Manager VM daemons

Maintains system configuration in the kernel & disk (private region). If the daemon is does not disable any configuration state loaded into the kernel, it only affects the abilit configuration changes until vxconfigd is restarted. vxconfigd It can be in three states: Enabl = Normal mode Disable = Most operations cannot be be used Booted = Normal startup while using boot disk group Monitors for failure events and relocates failed subdisks

vxrelocd vxconfigbackupd vxnotify

Used to backup configuration chnages, the files created can be used with vxmake to re groups. Display vertias volume manager events used with the vxconfigd daemon Kernel Info The kernel can be in three states: Enabled - both private and public regions are accessible Disabled - no private or public regions are accessible Detached - only private regions are accessible

Kernel States

VM utilities vxconfigd -k -m enable -x <debug option> VxVM debug -x log -x logfile = <name> -x syslog -x timestamp -x tracefile=name log to /var/vxvm/vxconfigd.log log to filename log to syslog date and timestamp every entry log all possible tracing to file

The vxiod utility starts, stops, or reports on VERITAS Volume Manager (VxVM) I/O daemon daemon provides a process context for performing I/O in VxVM.Manage extended disk i/o & dirty regions, logging vxiod vxiod set <number> = set number of runnning viod daemon Note: when run on its own it displays # of vxiod daemons that are running. vxdctl [option]

The vxdctl utility manages aspects of the state of the volume configuration daemon vxconfigd manages aspects of configuration for bootstrapping the rootdg disk group. mode = what mode the vxconfigd is running in enable = enable the vxconfigd daemon (reread the db)

disable = disable the vxconfigd daemon stop = kill the vxconfigd daemon (Use 'vxconfigd -k -m disable' to start again) license [init] = print out license info or reread licenses support = display version and components list = display entries in /etc/vx/volboot init [dmp] = recreate /etc/vx/volboot Note: when is disabled or stop mode no VX commands will be able to run vxinstall Disk Regions Install volume manger (use /etc/vx/disk to exclude any disks or controllers)

Private

This is were veritas holds the meta data regarding the disk. A copy of the configuration copied to each private region within the disk group. Veritas will try and keep 5 copies o configuration database. Normally configured as slice 3 This is the area that will store the users data. Normally configured as slice 4. Disk Layouts private region and public region slices are on seprate partitions (3 & 4), tis type of disk suitable for moving between different O/S's but are suitable for boot partitions Can be converted to CDS

Public

Sliced Disk layout CDS (Cross-platform Data Sharing) Simple None

private and public regions are one slice (slice 7) , this type is suitable for moving betwe different O/S's but not suitable for boot parttions. Private and public are the same partition but continuous (slice 3) Can be converted to CDS None partitioning

VxVM Configuration Database DB size DB location File Locations vxinstall has not be run Host ID's /etc/vx/reconfig.d/state.d/install-db /etc/vx/volboot vxdg list <group> | grep permlen - the size of the configuration db vxdisk list <disk> | grep -i configs - db location

backup config files (vxconfigbackupd) delete or deported disk group config files All commands logs Licenses Imported disk groups info vxconfigd log file Backup & Restore

/etc/vx/cbr/bk /etc/vx/dgcfg/deport /var/adm/vx/veacmdlog /etc/vx/licenses/lic /var/vxvm/tempdb Note: to clear the tempdb file: vxconfigd -k -x cleartempdir - clear the /var/vxvm/tempdb /var/vxvm/vxconfigd.log

Backup

/usr/lib/vxvm/bin/vxconfigbackup -l /var/vxvm/backups -l = location where to store backup vxconfigrestore -p <group> # either one of the below after the precommit vxconfigrestore -d <group> vxconfigrestore -c <group> Note: -p = when you want to check that the restore is correct (use vxprint to check) -d = abort the precommit -c = commit the precommit

Restore (precommit/commit)

Disks vxdisksetup -i c2t0d0 privlen=768 vxdisksetup -i <device> format=sliced - initialized a disk as a sliced disk vxdiskunsetup -C c2t0d0 vxdisk -g <group> list <disk> vxdisk -s list vxdisk -g <group> resize <disk> length=8G vxdctl add disk <device> type=simple vxdisk f <device> type=simple vxdiskadd c1t0d0 or c1 (all disk on controller)

Initialize disk Uninitialize disk Disk Information Resize a LUN Add a disk slice to volboot Add a disk slice Add a disk

Note: format can be either sliced, simple, cdsdisk or none (see above - Disk Reg

vxdisksetup -i <device> Remove a disk totally from VM vxdisk rm <device> Remove a disk from a volume Remove a disk slice from VM Clear any host ID flags Renaming a disk Move disk to different disk group Offline a disk Online a disk Hot spare NoHotUse Turn off failing flag Encapsulate a disk vxdg -g <group> rmdisk <diskname> vxdctl rm disk <device> vxdisk clearimport <disk name> vxedit -g <disk> rename <old disk name> <new disk name> vxdg move <source dg> <target dg> <disk> vxdisk offline <dev name> Note: disk must not be in a disk group vxdisk online <dev name> Note: disk must have a private region otherwise you need to initialise the disk vxedit g <group> set spare=on <disk> vxedit g <group> set nohotuse=on <disk> vxedit -g <group> set failing=off <disk> vxdisk define c0t0d0s0 type=nopriv vxreattach [-br | -c] Reattach disk (SAN) -b = Background process -r = Recover volumes -c = Checks to see if reattach is possible vxdisk scandisks [new | fabric ] vxedit -g <group> set comment="......." <disk>

Discover new disks Disk Comment Disk Group Create a disk group Remove a group Add a disk to a group Remove a disk from a group Replace failed disk

vxdg init group <disk>=<device> vxdg init <group> <disk>=<device> cds=off vxdg destroy <group> vxdg g <group> adddisk <disk>=<device> vxdg g <group> rmdisk <disk> vxdg -k -g <group> adddisk <disk>=<device>

- initialize a non-cds disk group

-k = forces vxvm to take media name of the failed disk & assign it to the new disk vxdg import <group> vxdg -n <new-group-name> import <old-group-name> vxdg -C import <group>

Import a group

Import group (clear any flags) Depot a group List no hot use on disk List spare space on disk Display free space

vxdg import -C <group> -C - clears any exist host flags vxdg deport <group> vxdg -n <new-group-name> deport <old_group_name> vxdg g <group> nohotuse <disk> vxdg g <group> spare <disk> vxdg g <group> free

Backup disk group (vxvm 4.0) vxconfigbackup Restore disk group (vxvm 4.0) vxconfigrestore [-p|-d|-c] Diskgroup Version Upgrade disk version vxdg list <group> | grep -i version vxdg upgrade <group> - upgrade to current version vxdg -T 50 upgrade <group> - upgrade to version 50 vxdg -T 50 init <group> <disk>=<device> - creater new group @ version 50 vxdg bootdg vxdg defaultdg vxdctl defaultdg <group> - set defaultdg Volume Adding mirror to root /etc/vx/bin/vxrootmir <alternate> create rootvol, swap vol, vxassist make <volume> <size> <disk> vxassist -g <group> make <vol> <size> !ctrl:c2 Create a simple volume stripe-mirror = layered volume concat-mirror = layered volume mirror-concat = non-layered volume mirror-stripe = non-layered volume Mirror a simple volume Create a stripped volume vxassist mirror <volume> >disk> vxassist -g <group> remove mirror <vol> !disk01 vxassist make <volume> <size> layout=stripe - don't use controller 2

Boot/Default DG

vxassist make <volume> <size> <disk> layout=[stripe-mirror|concat-mirror|mir

- remove the disk01 mirror

vxassist -g <group> -o ordered make <vol> <size> layout=stripe ncol=3 <disk1 vxassist make <volume> <size> layout=raid5 vxedit rf rm <volume> vxassist -g <group> remove volume <vol>

Create mirrored volume with log vxassist make <volume> <size> layout=mirror, log nmirror=# nlog=# Create a raid volume Remove a volume

Note: you must disable the volume first Initializing a volume vxvol init state <volume> [plex]state=clean,enable,active vxassist -g <group> relayout <vol> layout=stripe ncol=2 vxassist -g <group> relayout <vol> layout=stripe ncol=+1 vxassist -g <group> relayout <vol> layout=stripe ncol=-1 vxassist -g <group> relayout <vol> layout=stripe stripe=32k ncol=5 vxassist -g <group> relayout <vol> layout=raid5 stripeunit=32k ncol3 vxassist -g <group> convert <vol> layout=stripe-mirror # Display the relayout operation vxrelayout -g <group> [status|reverse|start] <vol> vxtask list Starting a volume Start a disabled volume Disable a volume Evacuate a volume Maintenance mode Not clean No kernel state Extending a volume size Shrinking a volume size add a DRL log to a volume remove a DRL log from a volume Extending log size Detering volume size Recover a volume Change volumes permissions Plexs Creating a plex Remove a plex vxmake plex <plex> sd =<sub disk name> vxplex o rm dis <plex> vxplex -g <group> dis <plex> vxvol start <volume> vxrecover sb <volume> -s = start volume after recovery -b = background the recovery task vxvol -g <group> stop <volume> vxevac -g <group> <from-disk> <to-disk> vxvol maint <volume> vxmend mirror clean <plex> vxplex att <vol_name> <plex> vxresize <volume> <new length> vxresize -g <group> <volume> +100m vxresize <volume> <new length> vxresize -g <group> <volume> -100m vxassist addlog <volume> vxassist remove log <volume> vxvol set loglen = 2m <volume/log> - increase the volume by 100Mb - decrease the volume by 100Mb

Online Relayout

vxassit -g <group> maxsize layout=mirror - the maximum size you can create a vxassist -g <group> maxgrow <volume> - the maximum size the volume can Vxmend fix clean <plex> vxedit -g <group> set owner=<user> group=<group> mode=<perms> <vol>

vxedit -g <group> -rf rm <plex> Moving a plex Copying a plex Attaching a plex Detaching a plex Offlining a plex Sub-disks Creating sub-disk Removing sub-disk Moving sub-disk Associating with a plex Dissociating Splitting Joining relocating a sub disk vxmake sd <sub-disk> <disk>, offset, len vxedit rm <sub-disk> vxsd mv <old sub-disk> <new sub-disk> vxmake plex <plex> sd=<sub-disk>, i.e vxmake plex home-1 sd= disk02-01, disk02-00, disk02-02 vxsd dis <sub-disk> vxsd s<size> split sd<new sub><newsub2> vxsd join <sub-disk1><subdisk2><new subdisk> vxassist -g <disk group> move !disk05 disk02 vxplex mv <original plex> <new plex> vxplex cp <volume> <new plex> vxplex att <volume> <plex> vxplex det <plex> vxmend off vol01-02

relocating a whole disk sub vxprint -g rootdg -se 'sd_orig_dmname="disk02"' disks vxunreloc -g rootdg disk02 Volume Manager Information Disks Display all the physical disks Display detailed disk info Check for disk failures Display group properties vxdisk list vxdisk -o alldgs list vxdisk list <disk> vxstat g <group>ff d Disk Group vxdg list vxinfo -p -g <group> Volume Display volume info vxprint Aht <vol> Display volume properties vxprint vl Display unstartable volume vxinfo -g <group> <vol> Display detailed group info vxdg list <group>

Check for volume failures Display plex properties Check for plex failures

vxstat g <group>ff -v Plex vxprint vp vxstat g <group>ff -p Sub-Disks

Display sub-disk properties vxprint st Veritas Tasks vxtask list vxtask monitor - continuously monitor Display tasks States: r = running p = pause a = aborting Statistics and Tracing Iostats vxstat -g <group> -r d <disks> - reset all stats on disk vxstat -g <group> -d - display stats vxstat -g <group> -i 1 -d <vol> - display stats every 1 sec intervals for volume vxstat -g <group> -i 10 -c 5 -d - display 5 sets @ 10 secs intervals vxtrace -d <filename> -o dev,disk <vol> vxtrace -f <filename> -o dev,disk <vol> | more

Tracing Licensing Add View Paths Reload new license VEA Start/Stop Status

vxlicinst vxlicense -c vxlicrep vxlicense -p

- versions greater than 3.5 - versions below 3.5 - versions greater than 3.5 - versions below 3.5

/etc/vx/licenses/lic - versions greater than 3.5 /etc/vx/elm - versions below 3.5 vxdctl license init

/etc/init.d/isisd [start|stop|restart] vxsvcctrl status vxsvc [-m|-k|-v] -m = status -k = kill

-v = version Daemons Start VEA GUI /opt/VRTSob/bin/vxsvc /opt/VRTSob/bin/vxsvcctrl /opt/VRTSob/bin/vea You must have X-windows running

Logging Logging help in recovery and can speed it up dramatically, the main form of logging in veritas is the DRL (dirty region log) which performs the following

log keeps track of changed regions if system fails only the changed regions of the volume are recovered vxassist -g <group> addlog <vol> logtype=drl vxassist -g <group> addlog <vol> - used for raid logs (no type) vxassist -g <group> remove log <vol> [nlog=n] <vol>

Add Remove Volume Read Policy

Policies can be used if you have slower disks within a volume and you wish to use the faster disks. Round Robin Preffered Plex Selected Plex Storage Expert (vxse) Veritas have created some scripots that can check the integrity of the vxvm setup i.e mirrored volumes, spares, etc. The scripts are based on rules and there are a number of differents rules veritas has set, look in the rules directory to see all of them. Display Description Check rules List spare rules Run spare run vxse_raid5log1 info vxse_raid5log1 -g <group> check vxse_spares list vxse_spares run Note: you need to run "/etc/init.d/isisd start" to start the necessary daemons first vxvol -g <group> rdpol round <vol> vxvol -g <group> rdpol prefer <vol> <plex> vxvol -g <group> rdpol select <vol>

VXSE Paths Rules Default Parameters VxDMP see VxDMP for more information Veritas links /opt/VRTS/vxse/vxvm /etc/default/vxse

You might also like