This action might not be possible to undo. Are you sure you want to continue?
-d - vxdctl init - vxdctl enable 2) Un-mirror the rootdisk using VMSA: - Start-up Veritas Volume Manager - Select the root volume - Right click, and select mirror - Then select disable - Choose rootvol-02 to disable - Do the same steps for /usr, and any swap volumes that are mirrored - Then get out of Volume Manager 3) Unmirror the root disk using command line run: - vxplex -o rm dis rootvol-01 - vxplex -o rm dis swapvol-01 (if needed) - vxplex -o rm dis usrvol-01 (if needed) 4) Un-Encapsulate root disk 1. boot single user mode from cdrom or net ok> boot cdrom -s or boot net -s 2. fsck the root filesystem # fsck -y /dev/rdsk/c0t0d0s0 3. mount the root filesystem on /a # mount /dev/dsk/c0t0d0s0 /a 4. cp /a/etc/system /a/etc/system.vxvm 5. vi /a/etc/system and remove the following 2 entries rootdev:/pseudo/vxio@0:0 set vxio:vol_rootdev_is_volume=1 6. cp /a/etc/vfstab /a/etc/vfstab.vxvm 7. cp /a/etc/vfstab.prevm /a/etc/vfstab 8. rm /a/etc/vx/reconfig.d/state.d/root-done 9. touch /a/etc/vx/reconfig.d/state.d/install-db 10. reboot *** install your new key 11. run commands below to start vxvm vxiod set 10 vxconfigd-m disable vxdctl init vxdctl enable
12.vxdctl enable DISPLAY & MONITORING COMMAND .support.start up Volume manager (see documentation above) .cd /a/etc .reboot (init 6) .fmthard -s /a/etc/vx/reconfig.d .Veritas File Manager GUI . in our example we'll mount c0t0d0s2 on /a .d/c0t0d0/vtoc /dev/rdsk/c0t0d0s2 .boot from the net or cdrom .veritas.remove the "0x" in the second column from each row.2 http://seer.d/disk.touch install-db .rootdev:/pseudo/vxio@0:0 .To see newly added disks . 5) Can't mount encapsulated swap during boot .veritas.prevm vxfstab . At this point you need to make sure all the volumes are ENABLED ACTIVE and detach all the plexes on your root mirror.remove rootdisk .cp vfstab vfstab.mount your root drive to a temporary location like /tmp/mnt or /a (/a for our example) (mount /dev/dsk/c0t0d0s2 /a .support.boot from CD or net .com/docs/240006.set vxio:vol_rootdev_is_volume=1 .remove volumes .set the vtoc back to its original state .init 6 .Upgrade procedure http://seer. .vxedit -rf rm rootdisk .vi /etc/vfstab and add any additional file systems you may need .umount /a .Installation located on cidcsssp0:/jsid/veritas .d/c0t0d0/vtoc .cd /a/etc/vx/reconfig.Technote for the required patches and SUN package for VxVM 3. .reinstall VXVM and remirror your drives.htm .mount the drive.htm .d/state.vi /a/etc/vx/reconfig.hold .This should include encapsulating your root drive.vxedit -rf rm <volumes> .cp vfstab.remove root-done ./opt/VRTSvmsa/bin/vmsa .comment out these two lines in /a/etc/system .com/docs/240304.mount /dev/dsk/c0t0d0s2 /a .d/disk. . both should be commented out .remove the first three characters from the third column .remove the 1st two lines in the file.
only displays "rootdg". This is best for a true picture of your configuration. layout type. etc. and volumes. By default. So for instance. including mutlipathing information. size. "vxprint vol01" shows information about all subcomponants of vol01. DISK TASKS and COMMANDS 1) vxdiskadd <devname> Adds a disk to Vx by Initializing and Encapsolating it.1 ) vxdisk list List all disks used by Veritas (VX). ncolumns. 6) vxdg list Display listing and state information of all Disk Groups. including flags. This works for plexes. Vx version. to display a different Disk Group. etc. specified in sectors. 2) vxedit rename <oldname> <newname> . disk groups. and more. including disks. 4) vxprint <componant> Display report style information about the current status of ONLY the componant you request. subdisks. plexes. logs status. 2) vxdisk list <diskname> Display detailed information about a single disk. 8) vxinfo Display volume status and volume type. 3) vxprint Display report style information about the current status of all Vx componants. No reboots needed for changing DG's. and more. type. read policy. Just follow the prompts. 7) vxdg list <diskgroup name> Display detailed information about a diskgroup. can also be used to add a disk to a specified disk group. version. offsets. use "vxinfo -g <dgname>". NOTE: You'll need to reboot to finalize the disk addition! This command. including stwdith. 5) vxprint -hrt Display detailed information about all Vx componanats. Specified by its device name (ex: c0t1d0s2). 9) vxassist maxgrow <volume> This command will output the maximum size the volume specified can increased by.
7) vxedit set spare=off <diskname> Same as above but removes the disk from the "hot spare pool". which is then added to the "hot spare pool". and to moved DG's from one system to another. 5) vxdg list <dgname> Use this to check the version numbers of Disk Groups. DISK GROUPS and COMMANDS 1) vxdg init <diskgroup> <diskname>=<devname> Creates a new disk group. or generally used. and assigns the naming scheme to the first disk added to the group.Rename a Vx disk. The disk should be removed from its diskgroup before being offlined. It's easier to use "vxdiskadd". 4) vxdisk offline <diskname> Used to "offline" a disk. 3) vxdg import <diskgroup> Reverse of above. ex: "vxdg init newdg newdg01=c0t10d0s2". 6) vxdg destroy <dgname> Removes the specified DG. 5) vxdisk rm <devname> Used to remove disks from Vx control completely. This is used to make the specified disk a hot spare. 4) vxdg -n <newdgname> <olddgname> Change a Disk Groups name. SUBDISKS and COMMANDS . and frees all its disks back to general use by Vx. NOTE: This is kinda tricky because the disk that you're adding can't be a member of ANY DG. Ex: "vxdisk rm c0t1d0s2" Make sure to removed the disk from its diskgroup. but must be initialized. Often used as an organized pool of disk to realocate. but doesn't remove it. This is used to keep specific disks from being accidentally. 2) vxdg deport <diskgroup> Disables a diskgroup. Shows other details about the DG too. and add the disk to a newdg by specifying a new DG name for the DG field. and offline the disk before removing it. Enables local access to the specified disk group. 6) vxedit set spare=on <diskname> Sets the "spare" flag to a Vx disk. Ex: "vxedit rename disk01 disk05" 3) vxedit set reserve=on <diskname> Sets the "reserve" flag to a Vx disk.
. you need to specify the column# so use the following: 4) vxsd -l <col#/offset> assoc <plexname> <subdiskname>. (Adds a mirror) NOTE: Attachment will take a while. 3) vxsd assoc <plexname> <subdiskname>. The layout is constrained by the defined number of columns.. and stripe width.. 5) vxsd aslog <plex> <subdiskname> Adds a log subdisk to the specified plex. but specifies layout type as defined by <layout>... Ex: "vxsd aslog vol01-02 disk03-01" vxsd dis <subdiskname> Disassociates the specified subdisk from its current plex.. its good to check the other subdisks in that plex to see what their lengths and offsets are. vxmake plex <plexname> layout=<layout> stwidth=<stwidth> ncolumn=<ncolumn> sd=. Subdisks specified are added to the created plex.0.disk02-01" NOTE: Striped volumes are different. Use the command "vxprint -st" to see what other subdisk in the plex look like.<length> Creates a subdisk with the specified name. Example: "vxsd assoc vol01-03 disk01-01. PLEX and COMMANDS 1) vxmake plex <plexname> sd=<subdiskname>..1) vxmake sd <subdiskname> <disk>.. Watch it with Vxtask..<subdiskname>.<offset>.. which is used for creation of striped and RAID5 plexes. use the command: "vxprint -st" 2) vxedit rm <subdiskname> Removes a subdisk.. 2) vxplex att <volname> <plexname> Associates specified plex with specified volume. ex: "vxmake sd disk02-01 disk02. but used for associating subdisks to a striped plex.. Associates the specified subdisks to the specified plex. and then set the new subdisks column number and offset (found in the seventh column of output) to the appropriate value. and by the offset and length specified.. Creates a new plex by the name specified and assigns the specified subdisks to it.8000" NOTE: If you are going to add this subdisk to a plex. . Like above command. or via vxprint 3) vxplex dis <plexname> Disassociate specified plex from its connected volume. Same as above.
NOTE: The old plex must be active (ENABLED).. but maintians association with it's volume.4) vxedit -r rm <plexname> Remove the plex. 6) vxplex det <plexname> Detaches specified plex from its connected volume. but with layout specified. 5) vxmend off <plexname> Offlines a plex for repair to it's disks. The new plex should be the same length. 7) vxmend fix clean <plexname> Used to clean plexes that are in the "unclean" state. NOTE: The new plex cannot be associated with any other volume. and attachs the specified plexes to that volume. The new plex must not be associated with another volume. see notes from above) VOLUMES and COMMANDS 1) vxassist make <volumename> <length> Creates a new volume with the name specified and is made to the length specified. 2) vxmake vol <volname> len=<length> plex=<plexname>. further. NOTE: See the vxmake(1M) man page for more information. vxvol init <state> <volname> [plexname] Manually sets the state of a volume. Like the above command. The plex is no longer used for I/O untill it is (re)attached. Useful for creating volumes to house copied or moved plexes. (Also.. NOTE: Not for the squimish. 3) vxassist maxsize [layout=raid5] . Creates a new volume of specified length (usually in sectors). Used with unstartable volumes. vxassist make <volname> <length> layout=<layouttype> <disk> <disk> . or larger than the old plex.. Ex: "vxassist make newvol 10m" NOTE: This command will pull disk space from the generally avalible Vx disk space. 8) vxplex mv <originalplex> <newplex> Moves the data content from the origonal plex onto a new plex. The new plex. The most common layouts are: striped and raid5 ex: "vxassist make newvol 100m layout=raid5 disk01 disk02 disk03" NOTE: See the vxassist(1M) man page for more information... will NOT be attached to the specified volume.. (duh) 9) vxplex cp <volume> <newplex> Copies the data from the specified volume to a new plex.
. NOTE: There is also a resize(1M) command. NOTE: Don't shrink volumes to be less that its contained filesystem! (duh) 10) vxvol set len=<length> <volname> An alternate to above command. vxassist remove log <volname> Reverse of above. If you didn't guess. 5) vxassist mirror <volname> Creates a mirror for the specified volume. you will need to use the command "vxedit -f <volname>". 11) vxedit rm <volname> Removes the specified volume. but the disks you want used may not be used. 9) vxassit growto/growby/shrinkto/shrinkby <volname> <length> Resizes the volume specified. and "f" is Force. 6) vxassist addlog <volname> Adds a Dirty Region Log (DRL) for the specified volume.. used for resizing both volume AND filesytem. and shrinkby in order to descide what <length> specifies. By adding "layout=raid5" to the command the calulations take into account losse due to raid5. This is fast.Returns the maximum size avalible via Vx to create a new volume. NOTE: Think of this as "handsfree plex creation". growby. by default. This does not resize the filesystem inside the volume. See the man page for that one. By default length is specified in sectors. 4) vxassist maxgrow <volname> Returns the maximum ammount of Vx space that can be added to the specified volume. in sectors. Misc Stuff: To calculate the size of a filesystem inside a volume. "r" is Recursive. Output is in sectors and Megs. Sets the absolute lenths of the specified volume to the length specified. use the command: fstyp -v <volume-device-path> | head -30 | grep ncg Ignore the errors. Alternately you can use command as such: "vxvol stopall" in order to stop all volumes. 7 ) vxvol start <volname> Starts a volume 8 )vxvol stop <volname> Stops a volume. Also. Output will look this this: . shrinkto. (poof!) NOTE: If the volume specified is in the ENABLED state. using the "r" with "f" will remove all plexes and subdisks with the volume. This does not resize the filesystem inside the volume. Use one of the following: growto. often best to do manually.
actually grow the volume (NOT THE FS) via the command (assuming maxgrow outputed 10639360 as the maxsize): ex:# vxassist -g rootdg growto vol01 10639360 disk01 disk02 disk03 3) Now VxVM grinds away. and look for the "len". Convert to kilobytes by dividing by 2. ------------Volume Growth Procudure: 1) You can use vxassist to estimate the max size of a given volume based on the disks you wish to add: ex: # vxassist -g rootdg maxgrow vol01 disk01 disk02 disk03 2) Next.# fstyp -v /dev/vx/rdsk/datadg/vol01 | head -30 | grep ncg ncg 17152 size 70254592 blocks 65863396 # Broken Pipe Unknown_fstyp (no matches) The size found after the label "size" is presented in kilobytes. ----------To calculate the size of a volume. You can convert to sectors by multiplying by 2. The volume length is in sectors. 4) Now Grow the Filesystem. for UFS use: # /usr/lib/fs/ufs/mkfs -F ufs -M /export /dev/vx/rdsk/rootdg/vol01 10639360 for VXFS ufs: # /usr/lib/fs/vxfs/fsadm -b 10639360 -r /dev/vx/rdsk/rootdg/vol01 /mnt 5) Done! Changing User/Group of a Raw Volume: (ex:) vxedit -g xxxdg set group=dba data_vol_123 vxedit -g xxxdg set user=oracle data_vol_123 . use vxprint. monitor with vxtask.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.