HP Veritas Volume Manager 5.0 -UX 11i v3 manuals
Lawn and Garden > Landscape Lighting
When we buy new device such as HP Veritas Volume Manager 5.0 -UX 11i v3 we often through away most of the documentation but the warranty.
Very often issues with HP Veritas Volume Manager 5.0 -UX 11i v3 begin only after the warranty period ends and you may want to find how to repair it or just do some service work.
Even oftener it is hard to remember what does each function in Landscape Lighting HP Veritas Volume Manager 5.0 -UX 11i v3 is responsible for and what options to choose for expected result.
Fortunately you can find all manuals for Landscape Lighting on our side using links below.
HP Veritas Volume Manager 5.0 -UX 11i v3 Manual
557 pages 4.05 Mb
2 Legal Notices4 ChapterUnderstanding Veritas Volume Manager 5 Administering disks6 Administering dynamic multipathing (DMP)7 Creating and administering disk groupsChapter 5 Creating and administering subdisks 8 Creating and administering plexesCreating volumes 9 Administering volumes10 Administering volume snapshots11 Creating and administering volume setsConfiguring off-hostprocessing 12 Administering hot-relocationAdministering cluster functionality 13 Administeringsites and remote mirrors Using Storage Expert 14 Performance monitoring and tuningAppendix A Commands summary Appendix B Configuring Veritas Volume Manager 15 GlossaryIndex 16 Understanding VeritasVolume Manager 76 Administering disksDisk devicesDisk devices /dev/rdisk /dev/dsk /dev/rdsk DMP nodes /dev/vx/dmp /dev/vx/rdmp For more information, see “Administering dynamic multipathing (DMP)” on page 77 Disk device naming in VxVMThere are two different methods of naming disk devices: ■Operating system-basednaming ■Enclosure-basednaming Operating system-basednaming 79 Private and public disk regionsMost VM disks have two regions: ” on page 205) smallest the public area following the private area) nopriv There is no private region (only a public region for allocating subdisks). This is the simplest disk type consisting only of space for allocating subdisks. Such disks are most useful for which private region data would not persist between reboots They can also be used to encapsulate disks where there is insufficient room for a private region. The disks cannot store configuration and log copies, and they do not support the use VxVM cannot track the movement of nopriv disks on a SCSI chain or between controllers 80 When the vxconfigd daemon is started, VxVM obtains a list ofknown disk device addresses from the operating system and configures disk access records for them automatically cdsdisk disk that is suitable for moving between different operating systems. This is the default format for disks that are not used to boot the system.Typically, most disks on a system are configured as this disk type. However, it is not a suitable format for boot, root or swap disks, for mirrors or Interface (EFI) disks hpdisk The disk is formatted as a simple disk. This format can be be converted to a CDS disk if it was not initialized for use as a boot disk fdisk Auto-configuredEFI disks are formatted as hpdisk disks by default 81 Discovering and configuring newly added disk devices89 Placing disks under VxVM control90 Changing the disk-namingscheme95 Installing and formatting disks96 Displaying and changing default disk layout attributesAdding a disk to VxVM97 Adding a disk to VxVM<pattern-list c3t0d0 c3t1d0 c3t2d0 c3t3d0 specifies fours disks at separate target IDs on controller 98 To continue with the operation, enterHere are the disks selected. Output format: [Device] list of device names Continue operation? [y,n,q,?] (default: y) y Which disk group [<group>,none,list,q,?] If you specified the name of a disk group that does not already exist There is no active disk group named disk group name Create a new group named disk group name? [y,n,q,?] (default: y)y Create the disk group as a CDS disk group? [y,n,q,?] (default: n) Use default disk names for the disks? [y,n,q,?] (default: y) When prompted whether the disks should become Add disks as spare disks for disk group name? [y,n,q,?] (default: n) n When prompted whether to exclude the disks from Exclude disks from hot-relocationuse? [y,n,q,?} (default: n) n Add site tag to disks? [y,n,q,?] (default: n) 99 stepsite_name If one or more disks already contains a file system At the following prompt vxdiskadm then proceeds to add the disks Note: To bring LVM disks under VxVM control, use the Migration Utilities See the Veritas Volume Manager Migration Guide for details See the 100 Reinitializing a diskUsing vxdiskadd to place a disk under control of VxVM 101 Rootability107 Dynamic LUN expansion109 Removing disks111 Removing a disk from VxVM controlRemoving and replacing disks112 To replace a diskAt the following prompt, enter the name of the disk to be replaced (or enter Remove a disk for replacement Menu: VolumeManager/Disk/RemoveForReplace home src No data on these volumes will be lost mkting Are you sure you want do this? [y,n,q,?] (default: n) mkting #vxassist move mkting !mydg02 113 114Administering disksThe following devices are available as replacements: c0t1d0 You can choose one of these disks now, to replace mydg02 Select “none” if you do not wish to select a replacement disk VxVM NOTICE V-5-2-265Removal of disk mydg02 completed successfully VxVM NOTICE V-5-2-260Proceeding to replace mydg02 with device c0t1d0 At the following prompt, indicate whether you want to remove another disk to use only spare disks 114 Replacing a failed or removed diskTo specify a disk that has replaced a failed or removed disk 115 116Administering disksc0t1d0 c1t1d0 You can choose one of these disks to replace mydg02 Choose "none" to initialize another disk to replace mydg02 Replace another disk? [y,n,q,?] (default: n) 116 Enabling a disk117 Taking a disk offline118 Renaming a diskReserving disks 119 Displaying disk information120 Displaying disk information with vxdiskadmTo display disk information Start the list (List disk information) all List disk information Menu: VolumeManager/Disk/ListDisk Enter disk device or "all" [<address>,all,q,?] (default: all) ■If you enter all, VxVM displays the device name, disk name, group, and status 121 Controlling Powerfail Timeout124 Administering dynamic multipathing (DMP)164 Creating and administering disk groups214 Creating and administering subdisks222 Creating and administering plexes234 Creating volumes235 Types of volume layouts236 Supported volume logs and mapsVersion 0 DCO volumes only support Persistent FastResync for the traditional Version 0 DCO volume layout Version 20 DCO volume layout Creating a volume with a version 20 DCO volume 237 Creating a volume238 Using vxassist239 operationThe vxassist utility helps you perform the following tasks: ■Creating volumes ■Creating mirrors for existing volumes ■Growing or shrinking existing volumes ■Backing up volumes online ■Reconfiguring a volume’s layout online The vxassist command takes this form: #vxassist [options] keyword volume [attributes...] vxassist options #vxassist [options] make volume length [attributes] vxintro 240 Setting default values for vxassist/etc/default/vxassist /etc/default #vxassist help showattrs The following is a sample vxassist defaults file: #By default: #create unmirrored, unstriped volumes #allow allocations to span drives #with RAID-5create a log, with mirroring don’t create a log #use the fsgen usage type, except when creating RAID-5volumes usetype=fsgen #allow only root access to a volume mode=u=rw,g=,o user=root group=root #when mirroring, create two mirrors nmirror=2 #for regular striping, by default create between 2 and 8 stripe #columns 241 Discovering the maximum size of a volumeDisk group alignment constraints on volumes 242 Creating a volume on any disk243 Creating a volume on specific disks248 Creating a mirrored volume249 Creating a volume with a version 0 DCO volume250 To upgrade a disk group to version 90, use the following command:#vxdg -T90 upgrade diskgroup For more information, see “Upgrading a disk group” on page layout \ logtype=dco [ndcomirror ] [dcolen ] \ [fastresync=on] ndcomirror #vxvol [-g diskgroup] set logtype=drl|drlseq volume For more information, see the vxassist(1M) and vxvol(1M) manual pages log_type 251 Creating a volume with a version 20 DCO volumeCreating a volume with dirty region logging enabled 252 Creating a striped volume254Creating volumes #vxassist -b -gmydg make stripevol 30g layout=stripe \ mydg03 mydg04 mydg05 #vxassist -b -gmydg make stripevol 30g layout=stripe \ stripeunit=32k ncol=5 253 Creating a mirrored-stripevolumeA mirrored-stripevolume mirrors several striped data plexes To create a striped-mirrorvolume, use the following command: Creating a striped-mirrorvolume 254 Mirroring across targets, controllers or enclosures255 Creating a RAID-5volume256 Creating tagged volumes257 Creating a volume using vxmakemydg00-00 mydg03-00 mydg01-00 mydg04-00 mydg05-00 #vxmake -gmydg plex raidlog1 sd=mydg06-00 #vxmake -gmydg plex raidlog2 sd=mydg07-00 The following command creates a RAID-5volume, and associates the prepared RAID-5plex and RAID-5log plexes with it: The procedure is described in “Initializing and starting a volume” on page 258 Creating a volume using a vxmake description file#vxmake [-g diskgroup] < description_file Alternatively, you can specify the file to vxmake using the -d option: # vxmake [-g diskgroup] -d description_file 259 Initializing and starting a volume261 Accessing a volume262 Administering volumes263 Displaying volume information266 Monitoring and controlling tasks267 Managing tasks with vxtaskvxtask operationsEXITED pause Puts a running task in the paused state, causing it to suspend operation resume Causes a paused task to continue operation 268 Using the vxtask commandTo list all tasks currently running on the system, use the following command: #vxtask list #vxtask -hlist foodg sysstart #vxtask -gfoodg -p -isysstart list #vxtask -plist #vxtask resume To monitor all tasks with the tag myoperation, use the following command: #vxtask monitor myoperation To cause all tasks tagged with recovall to exit, use the following command: #vxtask abort recovall 269 Stopping a volume270 Starting a volumeAdding a mirror to a volumeAdding a mirror to a volume 271 Mirroring all volumes#/etc/vx/bin/vxmirror -g diskgroup -a #/etc/vx/bin/vxmirror -dyes nmirror=1 nomirror #vxassist -gmydg make nomirror 20g nmirror=1 Mirroring volumes on a VM diskTo mirror volumes on a disk 2Select menu item 5 (Mirror volumes on a disk) from the vxdiskadm main menu 272 Removing a mirror273 Adding logs and maps to volumes274 Preparing a volume for DRL and instant snapshotsUsing a DCO and DCO volume with a 275 Specifying storage for version 20 DCO plexesdisk05 disk06 #vxsnap -gmydg prepare myvol ndcomirs=2 alloc=disk05,disk06 vol1_dco 276 Using a DCO and DCO volume with a RAID-5volumeDetermining the DCO version number 277 Determining if DRL is enabled on a volume#vxprint [-g diskgroup] -F%drl$DCONAME DRL is enabled if this command displays on #vxprint [-g diskgroup] -F%sequentialdrl$DCONAME Sequential DRL is enabled if this command displays on Alternatively, you can use this command with the volume: #vxprint [-g diskgroup] -F%log_type volume REGION DRLSEQ NONE Determining if DRL logging is active on a volumeTo determine if DRL logging is active on a mirrored volume Use the following #DCOVOL=‘vxprint [-g diskgroup] -F%parent_vol$DCONAME‘ #vxprint [-g diskgroup] -F%drllogging$DCOVOL This command returns on if DRL logging is enabled Disabling and re-enablingDRLTo disable DRL (configured using a version 20 DCO volume) on a volume # vxvol [-g diskgroup] set drl=off volume 278 Upgrading existing volumes to use version 20 DCOs279 To upgrade a disk group to the latest version, use the following command:#vxprint [-g diskgroup] -F“%name” -e“v_hasdcolog” #vxassist [-g diskgroup] remove log volume [nlog=n] nlog #vxassist [-g diskgroup] snapback snapvol 5Use the following command to turn off FastResync for the volume: #vxvol [-g diskgroup] set fastresync=off volume #vxassist [-g diskgroup] remove log volume logtype=dco 7Use the following command on the volume to upgrade it: 280 Adding traditional DRL logging to a mirrored volumevol03 #vxassist -gmydg addlog vol03 logtype=drl logtype=drlseq #vxassist -gmydg addlog volume logtype=drlseq [nlog=n] 281 Removing a traditional DRL logTo remove a DRL log, use the vxassist command as follows: #vxassist [-g diskgroup] remove log volume logtype=drl [nlog=n] mydg10 # vxassist -gmydg remove log vol01 !mydg10 logtype=drl 282 Adding a RAID-5log283 Resizing a volume284 Resizing volumes using vxresize285 Resizing volumes using vxassistThe following modifiers are used with the vxassist command to resize a volume: growto Increase volume to a specified length Extending to a given lengthTo extend a volume to a specific length, use the following command: #vxassist [-b] [-g diskgroup] growto volume length Note: If specified, the -b option makes growing the volume a background task For example, to extend volcat to 2000 sectors, use the following command: #vxassist -gmydg growto volcat Extending by a given lengthTo extend a volume by a specific length, use the following command: # vxassist [-b] [-g diskgroup] growby volume length 286 Shrinking to a given lengthShrinking by a given length Resizing volumes using vxvol 287 Setting tags on volumes288 Changing the read policy for mirrored volumes289 Removing a volumeMoving volumes from a VM disk 291 Enabling FastResync on a volume293 Performing online relayout299 Converting between layered and non-layeredvolumes302 Administering volume snapshots304 Traditional third-mirror break-offsnapshots306 Full-sizedinstant snapshots308 Space-optimizedinstant snapshots309 Emulation of third-mirror break-offsnapshots310 Linked break-offsnapshot volumes311 Cascaded snapshots316 Creating multiple snapshotsRestoring the original volume from a snapshot 318 Creating instant snapshots319 voliomem_maxpool_szwarning such as the following (for a system whereis set to 12MB): To make the volumes usable for instant snapshot operations, use on the volume, and then use re-prepare the volume with a region size that is less than half the size of voliomem_maxpool_sz (in this example, 1MB): Preparing to create instant and ■“Creating and managing space-optimizedinstant snapshots” on page ■“Creating and managing full-sizedinstant snapshots” on page ■“Creating and managing third-mirror break-offsnapshots” on page ■“Creating and managing linked break-offsnapshot volumes” on page 320 Preparing to create instant and break-offsnapshotsTo prepare a volume for the creation of instant and break-offsnapshots #vxprint -g volumedg -F%instant volume #vxprint -g volumedg -F%fastresync volume 2To prepare a volume for instant snapshots, use the following command: vxsnap unprepare #vxsnap -gmydg prepare myvol regionsize=128k ndcomirs=2 \ alloc=mydg10,mydg11 If you need to create several 322Administering volume snapshots 321 Creating a shared cache objectTo create a shared cache object Having decided on its characteristics, use the cachevol mydg16 mydg17 #vxassist -gmydg make cachevol 1g layout=mirror \ init=active mydg16 mydg17 vxmake cache 16k autogrow=on cobjmydg 4Having created the cache object, use the following command to enable it: #vxcache [-g diskgroup] start cache_object ] start For example to start the cache object, cobjmydg: #vxcache -gmydg start cobjmydg For details of how to remove a cache, see “Removing a cache” on page 322 Creating a volume for use as a full-sizedinstant or linked break-offsnapshot#LEN=‘vxprint [-g diskgroup] -F%len volume‘ ksh bash csh tcsh 3Use the vxprint command on the DCO to discover its region size (in blocks): #RSZ=‘vxprint [-g diskgroup] -F%regionsz$DCONAME‘ 324Administering volume snapshots init=active 323 Creating and managing space-optimizedinstant snapshots324 Creating a shared cache objectTo create and manage a space-optimizedinstant snapshot To create a snap3myvol myvol mydg14 cobjmydg cachesize autogrow ncachemirror 325 snap4myvolmydg15 Use # fsck -Fvxfs /dev/vx/rdsk/diskgroup/snapshot You now have the following choices of what to do with a Refresh the contents of the snapshot. This creates a new Restore the contents of the original volume from the snapshot volume. The 326 Creating and managing full-sizedinstant snapshotsTo create and manage a full-sizedinstant snapshot instant snapshot, use the following form of the snap1myvol #vxsnap -gmydg make source=myvol/snapvol=snap1myvol syncing=on vxsnap syncwait #vxsnap [-g diskgroup] syncwait snapvol # vxsnap -gmydg syncwait snap2myvol 328 Creating and managing third-mirror break-offsnapshotsTo create and manage a third-mirror break-offsnapshot To create the snapshot, you can either take some of the existing SNAPATT # vxsnap -gmydg addmir vol1 nmirror=2 alloc=mydg10,mydg11 329 330Administering volume snapshots#vxsnap -gmydg snapwait vol1 nmirror=2 snapshot, use the following form of the state. (Such plexes could have been added to the volume by using the command.) snap2myvol #vxsnap -gmydg make source=myvol/newvol=snap2myvol\ /nmirror=1 330 Creating and managing linked break-offsnapshot volumesTo create and manage a linked break-offsnapshot Use the following command to link the prepared snapshot volume # vxsnap [-g diskgroup] [-b]addmir volume mirvol=snapvol 331 [mirdg=snapdg]snapdg mysnapdg #vxsnap -gmydg -baddmir vol1 mirvol=prepsnap \ mirdg=mysnapdg #vxsnap -gmydg snapwait vol1 mirvol=prepsnap \ mirdg=mysnapvoldg To create a linked snapdiskgroup You now have the following choices of what to do with a linked ■Reattach the snapshot volume with the original volume. See “Reattaching a linked break-offsnapshot volume” on page 339 for details 332 Creating multiple instant snapshotssnapvol1 snapvol2 Creating a volume for use as a full-sized instant or linked snapshot vol1 vol2 #vxsnap [-g diskgroup] make #vxsnap [-g diskgroup] make source=vol1/snapvol=snapvol1 334Administering volume snapshots snapvol1 snapvol2 snapvol3 333 Creating instant snapshots of volume sets, and vxvset list #vxvset -gmydg list vset1 INDEX vol_0 vol_1 vol_2 # vxvset -gmydg list snapvset1 334 nmirrorsvset1 snapvset1 #vxsnap -gmydg prepare vset1 #vxsnap -gmydg prepare snapvset1 #vxsnap -gmydg make source=vset1/snapvol=snapvset1 #vxsnap -gmydg prepare vset2 #vxsnap -gmydg addmir vset2 nmirror=1 #vxsnap -gmydg make source=vset2/newvol=snapvset2/nmirror=1 for more information about adding plexes to volumes or to volume sets #vxsnap -gmydg prepare vset3 #vxsnap -gmydg make source=vset3/newvol=snapvset3/ cachesize=20m #vxsnap -gmydg prepare vset4 #vxsnap -gmydg make source=vset4/newvol=snapvset4/cache=mycobj vset3 mycobj vset4 for more information on creating and administering volume sets 336Administering volume snapshots 335 Adding snapshot mirrors to a volume#vxsnap -gmydg addmir vol1 nmirror=2 alloc=mydg10,mydg11 plex Removing a snapshot mirrorTo remove a single snapshot mirror from a volume, use this command: #vxsnap [-g diskgroup] rmmir volume|volume_set ] rmmir # vxsnap -gmydg rmmir vol1 Note: This command is similar in usage to the vxassist snapabort command vxassist snapabort 336 Removing a linked break-offsnapshot volumeTo remove a linked break-offsnapshot volume from a volume, use this command: mirvol \ [mirdg snapvol snapdiskgroup #vxsnap -gmydg rmmir vol1 mirvol=prepsnap mirdg=mysnapdg Adding a snapshot to a cascaded snapshot hierarchythurs_bu dbvol wed_bu: fri_bu thurs_bu Cascaded snapshots Refreshing an instant snapshotsnapvolume snapvolume_set volume_set snapvol2 vol2 338Administering volume snapshots 337 Reattaching an instant snapshotNote: This operation is not supported for space-optimizedinstant snapshots snapmyvol #vxsnap -gmydg reattach snapmyvol source=myvol nmirror=1 SNAPTMP #vxsnap -gmydg snapwait myvol nmirror=1 338 Reattaching a linked break-offsnapshot volumeTo reattach a linked snapshot volume, use the following form of the sourcedg snapdiskgroup snapdg mydg: #vxsnap -gsnapdg reattach prepsnap source=myvol sourcedg=mydg 340Administering volume snapshots syncwait #vxsnap -gsnapdg snapwait myvol mirvol=prepsnap 339 Restoring a volume from an instant snapshotIt is not possible to restore a volume from an unrelated volume snap3myvol #vxsnap -gmydg restore myvol source=snap3myvol Dissociating an instant snapshot# vxsnap [-f] [-g diskgroup] dis snapvolume|snapvolume_set [-f] ] dis 340 Removing an instant snapshotSplitting an instant snapshot hierarchy 341 Displaying instant snapshot information(1M) manual page for more information about using the commands 343 Controlling instant snapshot synchronization344 Improving the performance of snapshot synchronizationsyncstart iosize size slow iodelay iosize iodelay Options may be combined as shown in the following examples: #vxsnap -gmydg -oiosize=10m,slow=250 syncstart snap2myvol Listing the snapshots created on a cache# vxcache [-g diskgroup] listvol cache_object 345 Tuning the autogrow attributes of a cacheattributes determine how the VxVM cache daemon ) maintains the cache if the feature has been enabled and is running: maxautogrow If the autogrow feature has been disabled: When cache usage reaches the high watermark value highwatermark #vxcache -gmydg set highwatermark=60 cobjmydg 346 Growing and shrinking a cacheRemoving a cache 347 Creating traditional third-mirror break-offsnapshots349 It is also possible to make a snapshot plex from an existing plex in a volumeSee “Converting a plex into a snapshot plex” on page 351 for details 3Create a snapshot volume using the following command: #vxassist [-g diskgroup] snapshot [nmirror=N] volume snapshot For example, to create a snapshot of voldef, use the following command: #vxassist [-g diskgroup] snapshot voldef snapvol ■Remove the snapshot volume to save space with this command: # vxedit [-g diskgroup] -rfrm snapshot 350 Converting a plex into a snapshot plexTo convert an existing plex into a snapshot plex for a volume on which Persistent FastResync is enabled, use the following command: #vxplex [-g diskgroup] -odcoplex=dcologplex convert \ state=SNAPDONE plex dcologplex trivol-03 trivol #vxplex -o dcoplex=trivol_dco-03convert state=SNAPDONE \ trivol-03 trivol_dco_03 #vxplex [-g diskgroup] convert state=SNAPDONE plex 351 Creating multiple snapshots#vxassist [-g diskgroup] snapshot volume1 volume2 ] snapshot reverses the order of the number and volume components in allvols #vxassist -g diskgroup -oallvols snapshot Reattaching a snapshot volume 352 Adding plexes to a snapshot volume353 Dissociating a snapshot volume354 Displaying snapshot information#vxassist snapprint [volume] Output from this command is shown in the following examples: #vxassist -gmydg snapprint SNAP-v2 355 Adding a version 0 DCO and DCO volume360 Creating and administering volume sets368 Configuring off-hostprocessing378 Administering hot-relocation396 Administering cluster functionality430 Administeringsites and remote mirrors 444 Using Storage ExpertAbout Storage Expert 445 How Storage Expert worksBefore using Storage Expert Running Storage ExpertRunning Storage Expert info Describes what the rule does Lists the attributes of the rule that you can set run Runs the rule See “Rule definitions and attributes” on page 446 Discovering what a rule doesDisplaying rule attributes and their default valuesmirror_threshold #vxse_drl1 list too_narrow_stripe - (3) columns in a striped volume Storage Expert lists the default value of each of the rule’s attributes To alter the behavior of rules, you can change the value of their attributes See “Setting rule attributes” on page Running a rule 447 Rule result typesSetting rule attributes 448 Identifying configuration problems using Storage Expert449 Checking for large mirror volumes without a dirty region log (vxse_drl1)See “Preparing a volume for DRL and instant snapshots” on page To check whether a large mirrored volume has a mirrored DRL log, run rule Checking for RAID-5volumes without a RAID-5log (vxse_raid5log1)To check whether a RAID-5volume has an associated RAID-5log, run rule See “Adding a RAID-5log” on page Checking minimum and maximum RAID-5log sizes (vxse_raid5log2) Checking for non-mirrored RAID-5logs (vxse_raid5log3)To check that the RAID-5log of a large volume is mirrored, run the rule 450 Disk groupsChecking whether a configuration database is too full (vxse_dg1)See “Creating a disk group” on page Checking disk group configuration copies and logs (vxse_dg2) Checking “on disk config” size (vxse_dg3)To check whether a disk group has the correct “on disk config” size, run rule Checking the version number of disk groups (vxse_dg4)To check the version number of a disk group, run rule vxse_dg4 See “Upgrading a disk group” on page 451 Checking the number of configuration copies in a disk group (vxse_dg5)See “Creating and administering disk groups” on page Checking for non-importeddisk groups (vxse_dg6)To check for disk groups that are visible to VxVM but not imported, run rule See “Importing a disk group” on page Checking for initialized VM disks that are not in a disk group (vxse_disk)See “Adding a disk to a disk group” on page Checking volume redundancy (vxse_redundancy)To check whether a volume is redundant, run rule vxse_redundancy See “Adding a mirror to a volume” on page Checking states of plexes and volumes (vxse_volplex)■disabled plexes ■detached plexes ■stopped volumes ■disabled volumes ■disabled logs ■failed plexes ■volumes needing recovery See “Reattaching plexes” on page See “Starting a volume” on page See the Veritas Volume Manager Troubleshooting Guide 452 Disk stripingChecking the configuration of large mirrored-stripevolumes (vxse_mirstripe)See “Converting between layered and non-layeredvolumes” on page Checking the number of columns in RAID-5volumes (vxse_raid5)To check whether volumes have too few or too many columns, run rule See “Performing online relayout” on page Checking the stripe unit size of striped volumes (vxse_stripes1) 453 Checking the number of columns in striped volumes (vxse_stripes2)Disk sparing and relocation management Checking the number of spare disks in a disk group (vxse_spares) Hardware failures Checking for disk failures and disabled controllers (vxse_dc_failures) Rootability Checking the validity of root mirrors (vxse_rootmir) System name 454 Checking the system name (vxse_host)455 Rule definitions and attributes462 Performance monitoring and tuning486 Commands summary487 ■ “Creating volumes” on page■ “Administering volumes” on page ■ “Monitoring and controlling tasks” on page Table A-1 Obtaining information about objects in VxVM # vxdisk -gmydg list # vxdg list mydg # vxdg -slist 488 # vxinfo -gmydg myvol1myvol2 # vxprint -gmydg myvol1 # vxprint -st -gmydg # vxprint -pt -gmydg Table A-2 489 # vxdiskadd c0t1d0# vxedit -gmydg rename mydg03 mydg02 # vxedit -gmydg set reserve=on mydg02 reserve=off mydg02 490 spare=on mydg04spare=off mydg04 # vxdisk offline c0t1d0 # vxdg -gmydg rmdisk c0t2d0 # vxdiskunsetup c0t3d0 491 Table A-3# vxdg init mydg mydg01=c0t1d0 # vxsplitlines -gmydg # vxdg -nnewdg deport mydg # vxdg -nnewdg import mydg # vxdg -nnewsdg -simport \ mysdg 492 # vxdg -oexpand listmovemydg newdg myvol1 # vxdg -oexpand move mydg newdg myvol1 # vxdg -oexpand split mydg newdg myvol2 myvol3 # vxdg join newdg mydg # vxdg -gmysdg set \ activation=sw 493 # vxrecover -gmydg -sb# vxdg destroy mydg Table A-4 # vxmake -gmydg sd mydg02-01mydg02,0,8000 # vxsd -gmydg assoc home-1 mydg02-01\ mydg02-00 mydg02-01 494 # vxsd -gmydg assocvol01-01 mydg10-01:0 mydg11-01:1 mydg12-01:2 # vxsd -gmydg mv mydg01-01 # vxsd -gmydg -s1000m split mydg03-02 mydg03-02 mydg03-03 # vxsd -gmydg join mydg03-02 mydg03-03 #vxassist -gmydg move \ myvol !mydg02 mydg05 495 # vxunreloc -gmydg mydg01# vxsd -gmydg -orm dis Table A-5 # vxmake -gmydg plex vol01-02 sd=mydg02-01,mydg02-02 496 vol01-02# vxplex -gmydg mv vol02-02 vol02-03 497 # vxplex -gmydg cp vol02vol03-01 vol02-02 Table A-6 # vxassist -gmydg maxsize \ layout=raid5 nlog=2 498 mysvol 20g layout=stripestripeunit=32 ncol=4 499 # vxmake -gmydg -Uraid5vol r5vol plex=raidplex,raidlog1 raidlog2 # vxvol -gmydg start r5vol # vxvol -gmydg init zero myvol 500 Table A-7#vxassist -gmydg mirror \ myvol mydg10 # vxassist -gmydg remove mirror myvol !mydg11 # vxassist -gmydg growby myvol 10g myvol 20g # vxassist -b -Fvxfs -gmydg myvol 20g mydg10 mydg11 501 # vxsnap -gmydg prepare \ myvol drl=on#vxsnap -gmydg make \ source=myvol/\ newvol=mysnpvol/\ nmiror=2 502 # vxassist -gmydg makecvol 1g layout=mirror init=active mydg16 mydg17 # vxmake -gmydg cache cobj cachevolname=cvol # vxsnap -gmydg make source=myvol newvol=mysosvol cache=cobj # vxsnap -gmydg refresh mysnpvol # vxsnap -gmydg dis mysnpvol 503 # vxsnap -gmydg unprepare \ myvol#vxassist -gmydg relayout \ vol2 layout=stripe vol3 layout=raid5 stripeunit=16 ncol=4 reverse vol3 504 #vxassist -gmydg remove \ myvolTable A-8 # vxrecover -gmydg -tmytask -bmydg05 # vxtask -h -gmydg list # vxtask monitor mytask 505 # vxtask pause mytask# vxtask -p -gmydg list # vxtask resume mytask # vxtask abort mytask 506 Online manual pages509 Section 4 — file formatsManual pages in section 4 describe the format of files that are used by Veritas Volume Manager Table A-10 Section 4 manual pages Section 7 — device driver interfaces 510 Configuring Veritas520 Glossary521 522 Glossarycluster A set of hosts (each termed a node) that share a set of disks cluster manager cluster-shareabledisk group shared disk group private disk group column concatenation configuration copy A single copy of a configuration database configuration database data change object (DCO) DCO volume data stripe dirty region logging detached device name enclosure-based naming disk access name 522 Glossarylog subdisk disabled path An alternative term for a device name disk access records disk array disk enclosure JBOD disk array serial number disk controller disk group defaultdg disk group ID A unique identifier used to identify a disk group disk ID disk media name 530 Index
Also you can find more HP manuals or manuals for other Lawn and Garden.