veritas versions

[gany59]

which veritas version is used in HP-UX lliv3 version and in 11iv2.

[Roopesh Francis_1]

check thse links.
http://docs.hp.com/en/5992-4607/5992-4607.pdf
http://docs.hp.com/en/5187-2725/5187-2725.pdf

[James R. Ferguson]

Hi:

From the installation guides:

for 11.23 - OnlineJFS 4.1 and VxFS 4.1

for 11.31 - OnlineJFS 4.1 and VxFS 4.1 with OnlineJFS 5.0 and VxFS 5.0 being optionally available.

Regards!

...JRF...

[Steven E. Protter]

Shalom,

swlist -l product | grep -i vxfs

SEP

[Duncan Edmonstone]

Veritas is (or was - they're now part of Symantec) a company, *not* a product...

There are two products that run on HP-UX which I guess you could be referring to here...

The Volume Manager (VxVM)
The File System (VxFS)

These are part of HP-UX, but then there are numerous other Veritas products which can be installed on HP-UX, such as NetBackup, or Veritas Cluster Server (VCS) to name just two.

So what are you actually interested in...

HTH

Duncan

[gany59]

i need to know about VxVM

[Vinod Kumar Yadav · Accepted solution]

Hi,

Complete VXVM Administration


VxVM CLI Cheat Sheet

VxVM Cheat Sheet
INFORMATION
vxprint -ht ==> Prints VxVM config
* -h List hierarchies below selected records.
* -t Print single-line output records that depend upon the configuration record type. For disk groups,
the output consists of the record type (dg) the disk group name, and the disk group ID.
vxprint -g -ht ==> Prints VxVM config of
vxdisk list ==> Lists all disks (both VxVM and Unix Controlled)
VOLUME GROUPS

vxdctl enable ==> scan system for new disks. (i.e. after adding disks from EMC, you need to run `vxdctl enable` to see them through VxVM.

How to create a volume manager(ed) disk:
# Scan for Added Disk
vxdctl enable
# Initialize new disks ()
/usr/lib/vxvm/bin/vxdisksetup -i

# Create new volume group, and add disk(s)
vxdg init = =

VOLUMES
vxassist -g -b make layout= comment= fstype=<fstype> <disk> <disk> <disk><BR /> *-b option puts command in the background, this is advisable.<BR /> *VALID <layouttype>'s SEE APPENDIX A<BR />vxassist -g <vg> -b remove volume <volumename><BR />Top Secret Cool Stuff:<BR /> vxassist -g vg27 -b make unused `vxassist -g vg27 maxsize | awk '{print $4}'` layout=concat comment="UNUSED"<BR />## MAINTENANCE COMMANDS<BR /># Grow Volume<BR />vxassist -g <vg> growto <volname> <length><BR /><BR />FILE SYSTEMS<BR /><BR /># Create VXfS filesystem, with large file support<BR /><BR />mkfs -F vxfs -o largefiles /dev/vx/rdsk/vg02/lvol03<BR /><BR />APPENDIX A<BR /><BR /> concat-mirror<BR /> New volumes should be concatenated and mirrored. <BR /> The mirroring is handled at each a subdisk level. The attribute stripe-mirror-col-split-trigger-pt<BR /> is applied.<BR /> contig, nocontig<BR /> Disallow or allow (default) plexes, regular stripe columns, or RAID-5 stripe columns from using multiple regions of disk. If contig is specified, then plexes and columns must be allocated from <BR /> a single contiguous region of disk. If this is not possible, the allocation fails. By default, vxas-<BR /> sist tries to allocate space contiguously, but will use multiple regions or multiple disks if<BR /> needed.<BR /> diskalign, nodiskalign<BR /> Align (default) or do not align subdisks on cylinder boundaries. When alignment is not dis-<BR /> abled, subdisks are created beginning on cylinder boundaries and are extended to match the end of a cylinder. Dirty region log subdisks, however, are not cylinder aligned (they are usually only 2 or 3 blocks long). Instead, when creating log subdisks, spaces are located from the available disk that could not be turned into regular subdisks because the spaces aren't cylinder aligned. For example, once one cylinder is used for a log subdisk, that cylinder cannot be used to <BR /> create an aligned data (or RAID-5 log) subdisk, so other log subdisks will be created there until that <BR /> cylinder fills up.<BR /> grow, nogrow<BR /> Allows a volume to grow during a relayout operation.<BR /> log, nolog<BR /> Create (or do not create) dirty region logs (for mirrored volumes) or log plexes (for RAID-5<BR /> volumes) when creating a new volume. This attribute can be specified independently for mirrored and RAID-5 volumes with the raid5log and regionlog layout specifications. The current <BR /> implementation does not support the creation of DCM logs in the layout specification.<BR /> mirror, nomirror, raid5<BR /> New volumes should be mirrored, unmirrored (default), or RAID-5, respectively. For mirror,<BR /> the attributes stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt are applied.<BR />mirror-concat<BR /> New volumes should be mirrored. The mirroring is done at the volume level. The attributes <BR /> stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt are ignored with this layout.<BR /> mirror-stripe<BR /> New volumes should be mirrored and striped. The mirroring is done at the volume level. The <BR /> attributes stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt are ignored with this<BR /> layout.<BR /> raid5log, noraid5log<BR /> Create (default) or do not create log plexes for RAID-5 volumes.<BR /> regionlog, noregionlog<BR /> Create or do not create (default) dirty-region log subdisks for mirrored volumes.<BR /> shrink, noshrink<BR /> Allows a volume to shrink during a relayout operation.<BR /> span, nospan<BR /> Allow (default) or disallow plexes, regular stripe columns, or RAID-5 stripe columns from <BR /> spanning multiple disks. If nospan is indicated, then plexes or columns can be formed from <BR /> multiple regions of the same disk, but cannot be formed from more than one disk.<BR /> stripe, nostripe<BR /> New plexes should be striped or unstriped, respectively. When creating a new volume, the default<BR /> is nostripe. When adding a new plex to an existing volume, the default is stripe if the volume<BR /> already has one or more striped plexes, and nostripe in other cases. For stripe (when combined<BR /> with mirror, the attributes stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt<BR /> are applied.<BR /> stripe-mirror<BR /> New volumes should be striped and mirrored. The mirroring is handled at each column level or sub-<BR /> disk level depending on the attribute stripe-mirror-col-split-trigger-pt.<BR /> stripe-mirror-col<BR /> New volumes should be striped and mirrored. The mirroring is handled at each column level. The<BR /> attributes stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt are ignored<BR /> with this layout.<BR /> stripe-mirror-sd<BR /> New volumes should be striped and mirrored. The mirroring is handled at each a subdisk level.<BR /><BR /><BR />Disk Group Related Tasks<BR /><BR />vxdiskadd or vxdiskadm<BR />vxdiskadd and vxdiskadm are interactive programs. It may ask you series of questions. Answer to these questions according to your requirement.<BR /><BR /># vxdiskadd [ all | c0t0d0 c0t1d0]<BR />OR<BR /># vxdiskadm<BR /><BR />To add disk c1t1d0 to a diskgroup<BR /># vxdiskadd c1t1d0 ( answer the questions appropriately)<BR />or<BR /># vxdiskadm<BR /><BR />To find out maximum size that a volume could be created in the disk group (free space in a DG)<BR /># vxassist -g appdg maxsize<BR />Maximum volume size: 31170560 (15220Mb)<BR /><BR />To list the available diskgroups<BR /># vxdg list<BR />NAME STATE ID<BR />tmpdg enabled,cds 1144189106.24.ultra5<BR />testdg enabled,cds 1144135936.13.ultra5<BR /><BR />To remove disk disk01 from diskgroup dg01<BR /># vxdg â g dg01 rmdisk disk01<BR /><BR />To get the detailed information about dg01 diskgroup<BR /># vxdg list dg01<BR /><BR />To display free space available in each disk in a disk group â dg01â <BR /># vxdg -g tmpdg free<BR />DISK DEVICE TAG OFFSET LENGTH FLAGS<BR />tmpdg01 c1t2d0s2 c1t2d0 4194304 31171664 -<BR />tmpdg02 c1t3d0s2 c1t3d0 0 35365968 -<BR /><BR />The actual space available is LENGTH in 512b<BR /><BR />To deport a diskgroup dg01<BR /># vxdg deport dg01<BR /><BR />To import a diskgroup dg01<BR /># vxdg import dg01<BR /><BR />To import a diskgroup with a newname<BR /># vxdg -n <new_dgname> import <old_dgname><BR /><BR />To destroy a diskgroup dg01<BR /># vxdg destroy dg01<BR /><BR />Upgrade disk group to highest version currently running<BR /><BR />#vxdg upgrade <dgname><BR /><BR />Move a diskgroup<BR /><BR />[Stop any applications associated with all volumes in the disk group; Unmount and stop all volumes in the disk group]<BR /><BR />a)Deport(disable local access) the disk group to be moved on first system.<BR />#vxdg deprot <dgname><BR /><BR />b)IMport(enable local access) the diskgroup and its disks from the second system.<BR /><BR />#vxdg import <dgname><BR /><BR />c) Start all volumes in the diskgroup on the second system<BR /><BR />#vxrecover â g <dgname> -sb<BR />OR<BR />#vxvol â g <dgname> startall<BR /><BR /><BR />Disk Related Tasks<BR /><BR />To display the disks information<BR /># vxdisk list<BR />DEVICE TYPE DISK GROUP STATUS<BR />c0t0d0s2 auto:none - - online invalid<BR />c1t2d0s2 auto:cdsdisk tmpdg01 tmpdg online<BR />c1t3d0s2 auto:cdsdisk tmpdg02 tmpdg online<BR />c1t4d0s2 auto:none - - online invalid<BR />c1t5d0s2 auto:cdsdisk testdg01 testdg online<BR />c1t10d0s2 auto:none - - online invalid<BR />c1t11d0s2 auto:none - - online invalid<BR />c1t12d0s2 auto:none - - online invalid<BR /><BR />To remove the disk c1t1d0 from volume manager control<BR /># vxdisk rm c1t1d0<BR /><BR />To make a disk as spare for hot relocation spare[Reserve]<BR /># vxedit set spare=on disk03<BR /><BR />To remove a spare disk disk03 from a hot relocation spare[Unreserve]<BR /># vxedit set spare=off disk03<BR /><BR />Note: Space wonâ t be allocated unless specifically mentioned in vxassist.<BR /><BR />To rename disk01 to disk03<BR /># vxedit rename disk01 disk03<BR /><BR />To make disk01 offline<BR /># vxdisk offline disk01<BR /><BR />To display detailed disk information about disk01<BR /># vxdisk -g tmpdg list testdg01<BR /># vxdisk -g tmpdg list testdg01<BR /> VxVM vxdisk ERROR V-5-1-558 Disk testdg01: Disk not in the configuration<BR /> ultra5 [/tmpfs] # vxdisk -g tmpdg list tmpdg01<BR /> Device: c1t2d0s2<BR /> devicetag: c1t2d0<BR /> type: auto<BR /> hostid: ultra5<BR /> disk: name=tmpdg01 id=1144189105.22.ultra5<BR /> group: name=tmpdg id=1144189106.24.ultra5<BR /> info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2<BR /> flags: online ready private autoconfig autoimport imported<BR /> pubpaths: block=/dev/vx/dmp/c1t2d0s2 char=/dev/vx/rdmp/c1t2d0s2<BR /> version: 3.1<BR /> iosize: min=512 (bytes) max=2048 (blocks)<BR /> public: slice=2 offset=2304 len=35365968 disk_offset=0<BR /> private: slice=2 offset=256 len=2048 disk_offset=0<BR /> update: time=1144283192 seqno=0.7<BR /> ssb: actual_seqno=0.0<BR /> headers: 0 240<BR /> configs: count=1 len=1280<BR /> logs: count=1 len=192<BR /> Defined regions:<BR /> config priv 000048-000239[000192]: copy=01 offset=000000 enabled<BR /> config priv 000256-001343[001088]: copy=01 offset=000192 enabled<BR /> log priv 001344-001535[000192]: copy=01 offset=000000 enabled<BR /> lockrgn priv 001536-001679[000144]: part=00 offset=000000<BR /> Multipathing information:<BR /> numpaths: 1<BR /> c1t2d0s2 state=enabled<BR /><BR /><BR />To find out the free space in a particular disk â tmpdg02â ³<BR /># vxdg -g tmpdg free tmpdg01<BR />DISK DEVICE TAG OFFSET LENGTH FLAGS<BR />tmpdg01 c1t2d0s2 c1t2d0 4194304 31171664 -<BR />The actual space available is LENGTH in 512b<BR /><BR />To display multipath information of VM Disk<BR /># vxdisk path<BR />SUBPATH DANAME DMNAME GROUP STATE<BR />c1t0d0s2 c1t0d0s2 mydg01 mydg ENABLED<BR />c4t0d0s2 c1t0d0s2 mydg01 mydg ENABLED<BR />c1t1d0s2 c1t1d0s2 mydg02 mydg ENABLED<BR />c4t1d0s2 c1t1d0s2 mydg02 mydg ENABLED<BR /><BR />#vxdisk path<BR />SUBPATH DANAME DMNAME GROUP STATE<BR />c1t1d0s2 disk_0 - - ENABLED<BR />c1t0d0s2 disk_1 - - ENABLED<BR />c4t50060482D5311F89d8s2 emc0_1073 appldg01 appldg ENABLED<BR />c2t50060482D5311FA6d8s2 emc0_1073 appldg01 appldg ENABLED<BR />c2t50060482D5311FA6d6s2 emc0_1820 rootdisk rootdg ENABLED<BR />c4t50060482D5311F89d6s2 emc0_1820 rootdisk rootdg ENABLED<BR />c4t50060482D5311F89d7s2 emc0_1822 rootdisk rootdg2 ENABLED<BR />c2t50060482D5311FA6d7s2 emc0_1822 rootdisk rootdg2 ENABLED<BR /><BR /><BR />vxdisk list command also shows the multipathing information<BR /><BR />#vxdisk list<BR />DEVICE TYPE DISK GROUP STATUS<BR />disk_0 auto:none - - online invalid<BR />disk_1 auto:none - - online invalid<BR />emc0_1073 auto:cdsdisk appldg01 appldg online<BR />emc0_1820 auto:sliced rootdisk rootdg online<BR />emc0_1822 auto:sliced rootdisk rootdg2 online<BR /><BR /><BR />vxdisk list emc0_1073<BR />Device: emc0_1073<BR />devicetag: emc0_1073<BR />type: auto<BR />hostid: lsprod66<BR />disk: name=appldg01 id=1243974515.11.lsprod66<BR />group: name=appldg id=1243974572.13.lsprod66<BR />info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2<BR />flags: online ready private autoconfig autoimport imported<BR />pubpaths: block=/dev/vx/dmp/emc0_1073s2 char=/dev/vx/rdmp/emc0_1073s2<BR />guid: {f28fd9f2-1dd1-11b2-a124-0021281a9efe}<BR />udid: EMC%5FSYMMETRIX%5F000190104702%5F02073008<BR />site: -<BR />version: 3.1<BR />iosize: min=512 (bytes) max=2048 (blocks)<BR />public: slice=2 offset=65792 len=46152448 disk_offset=0<BR />private: slice=2 offset=256 len=65536 disk_offset=0<BR />update: time=1243978462 seqno=0.8<BR />ssb: actual_seqno=0.0<BR />headers: 0 240<BR />configs: count=1 len=48144<BR />logs: count=1 len=7296<BR />Defined regions:<BR /> config priv 000048-000239[000192]: copy=01 offset=000000 enabled<BR /> config priv 000256-048207[047952]: copy=01 offset=000192 enabled<BR /> log priv 048208-055503[007296]: copy=01 offset=000000 enabled<BR /> lockrgn priv 055504-055647[000144]: part=00 offset=000000<BR />Multipathing information:<BR />numpaths: 2<BR />c4t50060482D5311F89d8s2 state=enabled<BR />c2t50060482D5311FA6d8s2 state=enabled<BR /><BR />vxdisk list c4t50060482D5311F89d8s2<BR />Device: emc0_1073<BR />devicetag: emc0_1073<BR />type: auto<BR />hostid: lsprod66<BR />disk: name=appldg01 id=1243974515.11.lsprod66<BR />group: name=appldg id=1243974572.13.lsprod66<BR />info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2<BR />flags: online ready private autoconfig autoimport imported<BR />pubpaths: block=/dev/vx/dmp/emc0_1073s2 char=/dev/vx/rdmp/emc0_1073s2<BR />guid: {f28fd9f2-1dd1-11b2-a124-0021281a9efe}<BR />udid: EMC%5FSYMMETRIX%5F000190104702%5F02073008<BR />site: -<BR />version: 3.1<BR />iosize: min=512 (bytes) max=2048 (blocks)<BR />public: slice=2 offset=65792 len=46152448 disk_offset=0<BR />private: slice=2 offset=256 len=65536 disk_offset=0<BR />update: time=1243978462 seqno=0.8<BR />ssb: actual_seqno=0.0<BR />headers: 0 240<BR />configs: count=1 len=48144<BR />logs: count=1 len=7296<BR />Defined regions:<BR /> config priv 000048-000239[000192]: copy=01 offset=000000 enabled<BR /> config priv 000256-048207[047952]: copy=01 offset=000192 enabled<BR /> log priv 048208-055503[007296]: copy=01 offset=000000 enabled<BR /> lockrgn priv 055504-055647[000144]: part=00 offset=000000<BR />Multipathing information:<BR />numpaths: 2<BR />c4t50060482D5311F89d8s2 state=enabled<BR />c2t50060482D5311FA6d8s2 state=enabled<BR /><BR />Remove a Disk<BR />[First stop any application associated with the volume; unmount the volume, stop the volume. If you need the data on the disk, move the volumes to another disk or backup volume]<BR /><BR />a) Remove the disk from its DiskGroup<BR /><BR /># vxdg -g <diskgroup> rmdisk <diskname><BR /><BR />b) Remove the disk from Volume Manager Control [devicename=c?t?d?s2]<BR /><BR />#vxdisk rm <devicename><BR />Sub-Disk Related Tasks<BR /><BR />To create a subdisk disk01-01 on disk disk01 of size 500MB<BR /># vxmake sd disk01-01 disk01,0,500m<BR />Note: If a second subdisk is created on the same vmdisk, the offset value 0 can not be given. It will overlap with the existing subdisk. We can find out the free offset value by giving the command vxdg â g (group-name) free which is used to find out the free disk space in diskgroups<BR />To associate subdisks disk01-01, disk02-01 to an existing plex plex01<BR /># vxsd assoc plex01 disk01-01 disk02-01<BR /><BR />To dissociate subdisk disk01-01 from a plex<BR /># vxsd dis disk01-01<BR /><BR />To remove a subdisk sd01<BR /># vxedit rm sd01<BR /><BR />To move data from subdisk sd01 to subdisk sd02<BR /># vxsd mv sd01 sd02<BR /><BR />To join two subdisks sd01 and sd02 and make it as single subdisk sd03<BR /># vxsd join sd01 sd02 sd03<BR /><BR />To split subdisk sd01 into two subdisks called sd04 sd05<BR /># vxsd â s size split sd01 sd04 sd04 (-s zize - size of the first subdisk to be created)<BR /><BR />Note:- if sub disk sd01 is associated with a plex before split , after split, both subdisks will be associated with the same plex. become<BR /><BR />To display detailed information about all subdisks<BR /># vxprint â ls<BR />Plex related tasks<BR /><BR />To create a plex and associate subdisks disk01-01 and disk03-01 to the plex<BR /># vxmake plex plex01 sd=disk01-01,disk03-01<BR /><BR />To create a striped plex plex01<BR /># vxmake plex plex01 layout=stripe stwidth=32 ncolumn=2 sd=disk01-01,disk02-01<BR /><BR />To create a RAID5 plex called plex01<BR /># vxmake plex plex01 layout=raid5 stwidth=32 ncolumn=2 sd=disk01-01, disk02-01, disk03-01<BR /><BR />To associate (attach) a plex to an existing volume<BR /># vxplex att vol01 plex01<BR /><BR />To create a new volume and associate plex to that volume<BR /># vxmake â U fsgen vol vol01 plex=plex01,plex02<BR /><BR />To dissociate a plex from a volume<BR /># vxplex dis plex02<BR /><BR />To temporarily detach a plex from a volume<BR /># vxplex det plex02<BR /><BR />To remove a plex<BR /># vxedit -r rm plex02<BR /><BR />To dissociate and remove a plex from a volume (removing mirror)<BR /># vxplex â o rm dis plex02<BR /><BR />To display detailed information about all plexes<BR /># vxprint â lp<BR /><BR />To display detailed information about a specific plex<BR /># vxprint â l plex01<BR /><BR />To make a plex called plex01 to clean state from stale state<BR /># vxmend fix clean plex01<BR /><BR />To make a plex from the disabled state to stale state<BR /># vxmend on plex01<BR /><BR />Volume related tasks<BR /><BR />To create a volume vol01 with attached plexes plex01 & plex02<BR /># vxmake â U fsgen vol vol01 plex=plex01,plex02<BR /><BR />Note:- -U Usage type. It should be â fsgenâ , if file system to be created on that volume<BR /><BR />To enable (start) a volume<BR /># vxvol start vol01<BR /><BR />To disable (stop) a volume<BR /># vxvol stop vol01<BR /><BR />To stop all enabled volumes<BR /># vxvol stopall<BR /><BR />To set the state of the volume vol01 to CLEAN<BR /># vxvol init clean vol01<BR /><BR />To display detailed information about all volumes<BR /># vxprint â lv<BR /><BR />To start a volume vol01, vol02 which can not be enabled<BR /># vxrecover â s vol01 vol02<BR /><BR />To increase or decrease the size of the volume & file system to 500MB<BR /># vxresize vol01 500m<BR /><BR />To list all the tasks currently running on the system<BR /># vxtask list<BR /><BR />To remove the volume appvol1<BR /># vxedit -g appvg -rf rm appvol1<BR /><BR />Estimating maximum volume size (any_valid_type=strip,mirror,raid5)<BR /># vxassist â g <dgname> maxsize layout=<any_valid_type><BR /><BR />Create a concatenated volume (length examples = 15g, 15m)<BR /># vxassist â g <dgname> make <volname> <length> <diskname> <diskname><BR /><BR />Create a striped volume(length examples = 15g, 15m)<BR /># vxassist â g <dgname> make <volname> <length> layout=stripe <diskname> <diskname><BR /><BR />Create a raid5 volume without logging<BR /># vxassist â g <dgname> make <volname> <length> layout=raid5,nolog <diskname> <diskname> <diskname> <diskname><BR /><BR /><BR />Create a raid5 volume with logging<BR /># vxassist â g <dgname> make <volname> <length> layout=raid5,log <diskname> <diskname> <diskname> <diskname><BR /><BR /><BR />Create a mirrored volume with DRL<BR /># vxassist â g <dgname> make <volname> <length> layout=mirror,log <diskname> <diskname> <BR /><BR />Mirror an existing Volume<BR /># vxassist mirror <volname> <diskname of disk to be mirrored> <BR /><BR />Mirror all volumes within a Disk Group<BR /># vxmirror â g <dgname> -a<BR /><BR />Mirror the root(boot) disk<BR /># vxrootmir â v <medianame><BR /><BR />NOTE:EEPROM variable â use-nvramrc?â must be set to true.<BR /> <BR /><BR />Remove a mirror <BR /><BR />Use vxprint â g <dgname> -ht to get plexname<BR /><BR /># vxplex â o rm dis <plexname><BR />Add a log to an existing volume<BR /><BR /># vxassist addlog <volname> <diskname><BR /><BR /><BR />Remove a log from an existing volume <BR /><BR /># vxassist remove log <volname><BR /><BR /><BR />Create RAID 0+1 without DRL<BR /><BR /># vxassist â g <dgname> make <volname> <length> layour=mirror-stripe,nolog nmirror=# nstripe=# <diskname> <diskname> <diskname><BR /><BR /><BR />Create RAID 1+0 without DRL<BR /><BR /># vxassist â g <dgname> make <volname> <length> layour=stripe-mirror,nolog nmirror=# nstripe=# <diskname> <diskname> <diskname><BR /><BR /><BR />Estimate how much a volume can grow<BR /><BR /># vxassist â g <dgname> maxgrow <volname> <BR /><BR />Remove a volume<BR /><BR />[Stop all applications associated with the volume, unmount volume, remove /etc/vfstab entry]<BR /><BR />a) Stop volume<BR />#vxvol stop <volname><BR /><BR />b) Remove volume [For RAID 1+0, use â rf rm]<BR /><BR /># vxedit â r rm <volname> <BR />OR<BR />#vxassist remote volume <volname><BR /><BR /><BR />Change a volume attributes<BR /><BR /># vxedit set <field>=<value> <volname> <BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR />#vxresize â g <dgname> <volname> -<size><BR /><BR />QQQ<BR /><BR />Create a new volume appvol of 100MB in the default disk group rootdg with available disks<BR /><BR /># vxassist make appvol 100m<BR /><BR />To create the volume appvol of 100MB on disk03<BR /><BR /># vxassist make appvol 100m disk03<BR /><BR />Create a striped volume appvol2 with the default stripe unit size on the default number of disks<BR /><BR /># vxassist make appvol2 100m layout=stripe<BR /><BR />Create a striped volume appvol2 100m striped volume on three specific disks<BR /><BR /># vxassist make appvol2 100m layout=stripe disk04 disk05 disk06<BR /><BR />Create the RAID-5 volume appvol4 with the default stripe unit size on the default number of disks with RAID-5 log<BR /><BR /># vxassist make appvol4 100m layout=raid5<BR /><BR />Extend vol3 upto 8000 sectors[extending up to certain length]<BR /><BR /># vxassist growto vol3 8000<BR /><BR />Extend vol RAID-5 volume appvol4 with the default stripe unit size on the default number of disks with RAID-5 log<BR /><BR /># vxassist make appvol4 100m layout=raid5<BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR /><BR />Resize a filesystem [UFS cannot be shrunk, only grown]<BR /><BR /># vxresize â g <dgname> <volname> +<size><BR /><BR /><BR /><BR />VXPRINT<BR /><BR />vxprint command is used to display the various information about disk, diskgroups, subdisk, plex, volume and etcâ ¦ It displays the information from Veritas volume manager configuration.<BR /><BR />vxprint [-aAbcCdfGhHlLmnpPqQrstvVx] [-g diskgroup] [name...]<BR />where:<BR />-d Display only disk media records<BR />-G Display only disk group records<BR />-g diskgroup Display records from the specified disk group<BR />-p Display only the plex records<BR />-s Display only subdisk records<BR />-h List hierarchies below selected records<BR />-l Display all information from each selected record<BR /><BR />To display all the available diskgroups<BR /># vxprint -G<BR />TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0<BR />dg dg01 dg01 - - - - - -<BR />dg dg02 dg02 - - - - - -<BR /><BR /><BR />To display details about a diskgroup<BR /># vxprint -g dg01<BR />TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0<BR />dg dg01 dg01 - - - - - -<BR />dm disk01 c1t2d0s2 - 35365968 - - - -<BR />dm disk02 c1t3d0s2 - 35365968 - - - -<BR />v vol01 fsgen DISABLED 2097152 - ACTIVE - -<BR />pl vol01-01 vol01 DISABLED 2097152 - ACTIVE - -<BR />sd sd01 vol01-01 ENABLED 2097152 0 - - -<BR /><BR />To display short note of volume vol1<BR /># vxprint -g dg01 -v vol01<BR />TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0<BR />v vol01 fsgen DISABLED 2097152 - ACTIVE - -<BR /><BR />To get the detailed output about a volume<BR /># vxprint -g dg01 -lv vol01<BR /><BR />Volume: vol01<BR />info: len=2097152<BR />type: usetype=fsgen<BR />state: state=ACTIVE kernel=DISABLED cdsrecovery=0/0 (clean)<BR />assoc: plexes=vol01-01<BR />policies: read=SELECT (round-robin) exceptions=NO_OP<BR />flags: closed writeback<BR />logging: type=REGION loglen=0 serial=0/0 mapalign=0 maplen=0 (disabled)<BR />apprecov: seqno=0/0<BR />recovery: mode=default<BR />recov_id=0<BR />device: minor=34000 bdev=272/34000 cdev=272/34000 path=/dev/vx/dsk/dg01/vol01<BR />perms: user=root group=root mode=0600<BR />guid: {5d61a4fe-1dd2-11b2-8e6d-080020b5a36b}<BR /><BR />Display Volume manager object listings<BR /><BR />#vxprint -ht<BR /><BR />VXEDIT<BR />The vxedit utility can be used to rename/remove the disks, subdisks, plex and volume information from the veritas configuration.<BR /><BR />vxedit [-dpPsvV ] [-g diskgroup] rename oldname newname<BR />vxedit [-dfpPrsvV ] [-g diskgroup] rm nameâ ¦<BR />vxedit [-dfGpPrsvV ] [-e pattern] [-g diskgroup] set<BR />attribute=valueâ ¦ [name...]<BR />where:<BR />-d for disk operation<BR />-p for plex operation<BR />-s for subdisk operation<BR />-v for volume operation<BR />-G for Disk group operation<BR />-f Force an operation<BR />-r Operate recursively on records associated with the selected records<BR />For selected volume records, this affects associated plex, subdisk, and subvolumes records. For selected plex records, this affects associated subdisk and subvolume records<BR /><BR />To remove appvol1 including the associated plex and subdisks<BR /># vxedit -g appvg -rf rm appvol1<BR /><BR />Note: if the above command tried with out the â -râ option, it will fail saying there are associated plexes.<BR /><BR /># vxedit -g dg01 -f rm vol01<BR />VxVM vxedit ERROR V-5-1-1189 Volume vol01 has associated plexes<BR /><BR />To remove a plex plex01 along with associated sub-disks<BR /># vxedit -g appvg -rf rm plex01<BR /><BR />To rename a plex name from plex-old to plex-new<BR /># vxedit -g dg01 -p rename plex-old plex-new<BR /><BR />Some useful commands<BR />vxtask<BR />vxtask command is used to administer operations on VxVM tasks that are running on the system. Operations include listing tasks, modifying the state of a task (pausing, resuming, aborting) and modifying the rate of progress of a task.<BR /><BR />vxtask abort taskid<BR />vxtask [-ahlpqr ] [-g dg_name [-g dg_name...]] [[-G dg_name] -v volume [-v volume...]] [-i taskid] list [taskid...]<BR />vxtask pause taskid<BR />vxtask resume tasked<BR /><BR />To list all Volume Manager tasks currently running on the system<BR /># vxtask list<BR /><BR />To print tasks hierarchically, with child tasks following the parent tasks<BR /># vxtask -h list<BR /><BR />LINUX Vxdisk command tips<BR /># vxdisk list<BR /><BR />DEVICE TYPE DISK GROUP STATUS<BR />sda auto:sliced rootdisk rootdg online<BR />sdb auto:sliced appdg01 appdg online<BR /><BR /># vxdisk list sda<BR />Device: sda<BR />devicetag: sda<BR />type: auto<BR />hostid: system7044<BR />disk: name=rootdisk id=1188098145.7.system7044<BR />group: name=rootdg id=1188098145.9.sytem7044<BR />info: format=sliced,privoffset=1,pubslice=3,privslice=6<BR />flags: online ready private autoconfig autoimport imported<BR />pubpaths: block=/dev/vx/dmp/sda3 char=/dev/vx/rdmp/sda3<BR />privpaths: block=/dev/vx/dmp/sda6 char=/dev/vx/rdmp/sda6<BR />version: 2.1<BR />iosize: min=512 (bytes) max=256 (blocks)<BR />public: slice=3 offset=0 len=71665902 disk_offset=63<BR />private: slice=6 offset=1 len=2047 disk_offset=71663917<BR />update: time=1188098305 seqno=0.8<BR />ssb: actual_seqno=0.0<BR />headers: 0 248<BR />configs: count=1 len=1481<BR />logs: count=1 len=224<BR />Defined regions:<BR />config priv 000017-000247[000231]: copy=01 offset=000000 enabled<BR />config priv 000249-001498[001250]: copy=01 offset=000231 enabled<BR />log priv 001499-001722[000224]: copy=01 offset=000000 enabled<BR />Multipathing information:<BR />numpaths: 2<BR />sda state=enabled<BR />sdc state=enabled<BR /><BR /><BR />Tips <BR />01. To exclude disks from Volume Manager control <BR />Create a file called /etc/vx/disks.exclude and place the disk name into this file <BR /> # cat /etc/vx/disks.exclude<BR /> c1t1d0<BR /> c1t2d0<BR /><BR />02. To exclude controllers from Volume Manager control <BR />Create a file called /etc/vx/cntrls.exclude and place the disk name into this file <BR /> # cat /etc/vx/cntrls.exclude<BR /> c1<BR /> c5<BR /><BR />03. To make the new disks detected under Veritas <BR /> Make sure the new disks are labeled<BR /> vxdctl enable<BR /> vxdisk scandisks new<BR /><BR />Using VxVM Commands: Examples<BR /><BR />1. Initialize disks c1t0d0, c1t1d0, c1t2d0, c2t0d0 c2t1d0 and c2t2d0:<BR /># vxdisksetup -i c1t0d0<BR /># vxdisksetup -i c1t1d0<BR /># vxdisksetup -i c1t2d0<BR /># vxdisksetup -i c2t0d0<BR /># vxdisksetup -i c2t1d0<BR /># vxdisksetup -i c2t2d0<BR /><BR />2. Create a diskgroup named database1 and add the six disks:<BR />#vxdg init database1 disk01=c1t0d0 disk02=c1t1d0 disk03=c1t2d0<BR />#vxdg -g database1 adddisk disk04=c2t0d0 disk05=c2t1d0 disk06=c2t2d0<BR /> <BR />3. Using the top down (modern) technique, create a RAID-5 volume named db01 of size 2GB on the six disks (5 + log). Also create and mount a UFS file system on the volume:<BR /><BR />#vxassist -g database1 make db01 2g layout=raid5 disk01 disk02 disk03 disk04 disk05 disk06<BR /><BR />#newfs /dev/vx/rdsk/database01/db01<BR />#mkdir db01<BR />#mount /dev/vx/dsk/database01/db01 db01<BR />#edit /etc/vfstab - using filesystem type of UFS and not vxfs.<BR /><BR />4. Remove the volume db01:<BR />#umount /db01<BR />#vxvol stop db01<BR />#vxedit -g database1 -r rm db01<BR /><BR />5. Using the bottom up technique, create a two-way mirrored volume named db02 of size 1GB using disks disk01, disk04:<BR />- 1 BG = 2097152 sectors [ 1 x 1024 x1024=1048576 x 2 = 2097152<BR />- Subdisks should be cylinder aligned<BR />- If disk uses 1520 sectors/cylinder, subdisk size = 2097600 sectors<BR />#vxmake -g database1 sd sd01 disk01,0,2097600<BR />#vxmake -g database1 sd sd02 disk04,0,2097600<BR />#vxmake -g database1 plex plex01 sd=sd01:0/0<BR />#vxmake -g database1 plex plex02 sd=sd02:0/0<BR />#vxmake -g database1 -U fsgen vol db02 plex=plex01,plex02<BR />#vxvol start db02<BR /><BR />6. Change the permissions of the volume so that dba is the owner and dbgroup is the group:<BR />#vxedit set user=dba group=dbgroup mode=0744 db02<BR /><BR />7. Destroy volume and remove disks from disk group database1. Also, remove disks from volume manager control:<BR />#vxvol stop db02<BR />#vxedit -g database1 -rf rm db02<BR />#vxdg -g database1 rmdisk disk01 disk02 disk03 disk04 disk05 disk06<BR />#vxdg deport database1<BR />#vxdiskunsetip c1t0d0<BR />#vxdiskunsetup c1t1d0<BR />#vxdiskunsetup c1t2d0...<BR /><BR /><BR />