VXVM Interview Question and answers

VXVM Interview Question and answers 1. Name the mandatory disk group in VxVM 3.5 ? How will you configure VxVM in 3.5 ? ANS: rootdg is the mandatory disk group in VxVM 3.5, vxinstall is the command to configure VxVM, It will create the disk groups, initializes the disks and adds them to the group. 2. How will you create private and shared disk group using VxVM ? ANS: For Private DG: Command: vxdg init For Shared DG: Command: vxdg -s init < disk1 disk2 disk3 > 3. Which are the different layouts for volumes in VxVM ? ANS: mirror, stripe, concat (default one), raid5, stripe-mirror, mirror-stripe. 4. What is the basic difference between private disk group and shared disk group ? ANS: Private DG: The DG which is only visible for the host on which you have created it, if the host is a part of cluster, the private DG will not be visible to the other cluster nodes. Shared DG: The DG which is sharable and visible to the other cluster nodes. 5. How will you add new disk to the existing disk group ? ANS: Run vxdiskadm command, which will open menu driven program to do various disk operations, select add disks option or you can use another command vxdiskadd. 6. How will you grow/shrink the volume/file system ? What is the meaning of growby and growto options ? What is the meaning on shrinkto and shrinkby options ? ANS: vxassist command is used to do all volume administration, following is the description and syntax. Growby option: This is will grow your file system by adding new size to the existing file

10. This WILL NOT ADD new size to the existing one. growby. 9. Growto option: This will grow your file system as per the new size. How will you list the disks. shrinkby] length 7. you can check the same using vxprint command too. Shrinkto option: This will shrink your file system as per the new size. This WILL NOT REDUCE the file system by reducing new size. vxdisk -o alldgs list command list all the disks which are in different dg's. How will you setup and unsetup disks explicitly using VxVM ? ANS: You can use /etc/vx/bin/vxdiskunsetup to unsetup the disk. In short words it has metadata of the disk. this will definitely help! [ /etc/vx/bin/vxdiskunsetup will remove the private region from the disk and destroys data. what steps you will follow to make the respective disks online ? ANS: If you faced this issue because of fabric disconnection then simply do vxdisk scandisks. which are in different disk groups ? ANS: vxdisk list is the command will list the disks from the DG which is currently imported. What is the private region in VxVM ? ANS: Private region stores the structured VxVM information. it also stores the disk ID and disk geometry. backup the data before using this option] . and /etc/vx/vxdisksetup to setup the disk. vxdisk list command gives you disks status as "error".system. Command: vxassist -g [growto. otherwise unsetup the disk using using /etc/vx/bin/vxdiskunsetup and setup the disks again using /etc/vx/bin/vxdisksetup. 8. shrinkto. If. Shrinkby option: This will shrink your file system by reducing new size from existing file system.

What is the difference between switchover and failover ? Ans: Switchover is an manual task where as failover is automatic. broken because of some disaster or system hung. Which command you will use to check the syntax of the main. 3. What is the service group in VCS ? Ans: Service group is made up of resources and their links which you normally requires to maintain the HA of application. schedule shutdown and reboot. What is the use of halink command ? Ans: halink is used to link the dependencies of the resources 7. . How do check the status of VERITAS Cluster Server aka VCS ? Ans: hastatus –sum3 2.cf is the main configuration file for VCS and it is located in /etc/VRTSvcs/conf/config. Which is the main config file for VCS and where it is located? Ans: main. How will you check the status of individual resources of VCS cluster? Ans: hares –state 5.cf? Ans: hacf -verify /etc/VRTSvcs/conf/config 4. But the failover will failover the service group to the other node when VCS heartbeat link down. You can switchover service group from online cluster node to offline cluster node in case of power outage. hardware failure. What is the use of hagrp command ? Ans: hagrp is used for doing administrative actions on service groups like online. 8. switch etc.Veritas cluster services Interview questions 1. 6. damaged. offline.

2009 5:55 pm 1. How do check the status of VERITAS Cluster Server aka VCS ? Ans: hastatus –sum 2. What is the difference between switchover and failover ? Ans: Switchover is an manual task where as failover is automatic. Which command you will use to check the syntax of the main. What is the service group in VCS ? Ans: Service group is made up of resources and their links which you normally requires to maintain the HA of application. How to switchover the service group in VCS ? Ans: hagrp –switch -to 10. What is the use of halink command ? Ans: halink is used to link the dependencies of the resources 7. You can switchover service group from online cluster node to offline cluster node in case of power outage.cf is the main configuration file for VCS and it is located in /etc/VRTSvcs/conf/config.cf ? Ans: hacf -verify /etc/VRTSvcs/conf/config 4. . 3. 6. How to online the service groups in VCS ? Ans: hagrp –online -sy Interview Questions with answers : Veritas Cluster Server Admin on Wed Jul 08.9. How will you check the status of individual resources of VCS cluster? Ans: hares –state 5. Which is the main config file for VCS and where it is located? Ans: main.

But the failover will failover the service group to the other node when VCS heartbeat link down. 8. How to online the service groups in VCS ? Ans: hagrp –online -sys .hardware failure. broken because of some disaster or system hung. offline. What is the use of hagrp command ? Ans: hagrp is used for doing administrative actions on service groups like online. switch etc. 9. How to switchover the service group in VCS ? Ans: hagrp –switch -to 10. schedule shutdown and reboot. damaged.

0/pci@1c. veritas volume manager Rootdg corruption Server fails to boot with one comment There are times when one has to go through the cut… Server has a bad panic/power trip and it corrupts the rootdg badly and the server is unable to boot with VxVM. 1.d/state. disable the start up of VxVM. 2010 at 1:40 pm Posted in Solaris. Once mounted.cp -p /a/etc/vfstab /a/etc/vfstab.Edit /a/etc/system. try again: failed to offline: /devices/ssm@0.touch install-db . Comment out the vx parameter as follow: *rootdev:/pseudo/vxio@0:0 *set vxio:vol_rootdev_is_volume=1 .700000/pci@1/SUNW. the “-f” (for force) option needs to be used: root@abc>/> vxdmpadm -f disable path=c1t0d0s2 root@abc>/> vxdmpadm getsubpaths ctlr=c1 NAME STATE[A] PATH-TYPE[M] DMPNODENAME ENCLR-TYPE ENCLR-NAME ATTRS ======================================================= ========================= c1t0d0s2 DISABLED c1t0d0s2 Disk Disk c1t6d0s2 ENABLED(A) c1t6d0s2 Disk Disk You can see the path now disabled from DMP. Mount the rootdisk. Since there is only one path to this disk.isptwo@4/sd@0.UNIXLOG Archive for the ‘veritas volume manager’ Category cfgadm:::Device being used by VxVM leave a comment » root@abc>/> cfgadm -c unconfigure c1::dsk/c1t0d0 cfgadm: Component system is busy.withvm .0 Resource Information —————— ————————/dev/dsk/c1t0d0s2 Device being used by VxVM “cfgadm unconfigure” command fails here. root@abc>/> cfgadm -c unconfigure c1::dsk/c1t0d0 cfgadm goes through fine. . Boot from the cdrom or from the network 2. Here is a procedure to recover from the situation. 3.rm root-done . root@abc>/> Written by krishsubramanian November 3.d/ .cd /a/etc/vx/reconfig. The way to resolve this is to disable the disks path from DMP control.

Reboot machine upon completed Option 2 above. I upgraded to Storage Foundation 5. .vxdiskadm. Zero out private and public region partitions from the disks on the rootdg.prevm /a/etc/vfstab .d/ . then run “vxvol -g groupname startall” to start the volume. Manually start the veritas volume manager. to verify all the volume are enabled. Option 2 to encapsulate the primary bootdisk . 11. . .vxiod set 10 .vxdiskadm. 12.vxdctl enable . If the volume not started. . 2010 at 4:32 pm Posted in veritas volume manager VxVM Upgrade leave a comment » Lets look at VxVM Upgrade this week… The setup is a) Solaris 9 b) VxVM 4. . The tech plan is as below: . then run “/usr/sbin/vxconfigd -m disable” . . Verify for the boot and all volumes coming up clean.vxprint -ht. Once this is done.ps -ef |grep vxconfigd.format -d <c#t#d#> 9.vxdctl mode 6. Option 1 to Add or initialize the second bootdisk .vxdg list 7. Deport the rootdg so that it does not come up again. .cp -p /a/etc/vfstab. .withvm to /etc/vfstab .mount all the volume and verify. Ensure the server comes up without veritas starting up.Revert back the /etc/vfstab. Mirror to second bootdisk .vxdisk list 10.. Option 6 to mirror the secondary bootdisk Written by krishsubramanian May 1.vxdg deport rootdg 8.vxdctl mode. the disks should show as error.cd /etc/vx/reconfig.0 MP3. Check the diskgroups. . 5. If vxconfigd is not running. Re encapsulate the disk.d/state.vxdiskadm.rm install-db . Should see it is in disabled mode.0 / VxDMP –> No powerpath c) Oracle databases.vxdctl init .init 6 4.

7. Run the upgrade_start -check . Boot the server from rootmirror and verify for the server coming up. 6. Run the VRTSexplorer and keep the file at a safe location if you may need it in case you run in any issue. A dusty file system has pending extended operations. Verify the pre-staged software is not corrupted and working fine. # mount /dev/dsk/c0t1d0s0 /alt.d/state. Break the rootmirror 4. 8.SUNWcfclr. 11.root/etc # touch /alt. Note: If a file system is not clean. 0x3c incidates the file system is dirty. Down load the package from symantec website 2. 12. Solaris 9 for Storage Foundation need SUNWcfcl. Install the VRTSspt Package.root/etc/system file Make changes to /etc/vfstab to ensure the system boots from the mirror disk ( c#t#d#) 5. 3.com/downloads and choose A-Z downloads 9.p S” | fsdb -F vxfs <Raw_Device> | grep clean Receive: flags 0 mod 0 clean clean_value Note: A clean_value value of 0x5a indicates the file system is clean.root/etc/vx/reconfig. Install the packages first and then the patches. Ensure all applications/Databases are shutdown and the file-systems are down. ( You can do this by doing a tar and keeping the software ready) 10.d/install-db rootdev:/pseudo/vxio@0:0 set vxio:vol_rootdev_is_volume=1 Remove the above lines from /alt. SUNWcfclx packages and patch 114477-04. Boot again from the rootdisk. Packages and patches can be downloaded from http://www. Ensure all the apps/db’s are umounted clean . Unencapsulate the rootmirror. and 0×69 indicates the file system is dusty. Check for the pre-requiste packages.1. enter the following commands for that file system: Enter: fsck -F vxfs filesystem Enter: mount -F vxfs [Block_Device] [mountpoint] Enter: umount [mountpoint] Note: This should complete any extended operations that were outstanding on the file system and unmount the file system cleanly.sun.root # cd /alt. # echo “8192B.

d #/usr/bin/rm root-done #/usr/bin/touch install-db 15 . # pkginfo | grep VRTS # pkgrm VRTSxxxx 18. 16. 20. Remirror the rootdrive follow standard procedures. but I have not tried it myself. Manually Encapsualte the rootdisk after upgrade. 17. Deport all appdiskgroups.Ensure that the root mirror is removed from rootdg. The steps I followed are : a) Get the LUN information from Storage and update the sd. Ensure applications are working fine 23.# /storage_foundation/scripts/upgrade_start -check -Note: this is a veritas check script that will check to see if this machine is eligible for upgrade. Reboot the node to single user mode. Don’t remove the VRTSvlic packages. 21. # vxdiskadm Choose option 2 and give the root disk for encapsulation. Solaris 9 OS with VxVM. If you are upgrading from 4. 2010 at 4:50 pm Posted in veritas volume manager Extending Filesystems in Sun Cluster using VxVM leave a comment » I did an activity to add LUNS to existing database file systems running sun Cluster 3.conf accordingly on both the servers . 19.1. Remove all packages that start with VRTS but for VRTSvlic. Un encapsulate the rootdisk Remove the following lines from /etc/system rootdev:/pseudo/vxio@0:0 set vxio:vol_rootdev_is_volume=1 Prevent veritas from starting up. Install the Veritas 5. # /sbin/vxdg –g rootdg –f rmdisk rootmirror 14./installer Note : Answer the questions and complete the installation. Insome cases veritas may not start correctly and will require a reboot.0 or later the licenses should take of themselves. 22. I believe you can remove this as well. Written by krishsubramanian February 13.d/state. 13. Import the disk groups and mount the filesystems.0 Software # . #/usr/bin/cd /etc/vx/reconfig.

# devfsadm # scgdevs f) Verify the sun Cluster DID devices.b) Make the LUNS Visible on the server. 2008 at 12:09 pm Posted in veritas volume manager Identifying and Replacing failed disks in V880 leave a comment » . There are times when one need to confirm the number of paths for the disk. Written by krishsubramanian November 14. A workaround is # vxassist -g <dgname> make testvol 1g layout=mirror init=active dgname01 dgname02 init=active is the keyword here. This can be accomplished by the below command. this post is for you. Run on both the servers. # vxdisk list <diskname> In this one can look at the numpaths value at the bottom of the output. 2008 at 2:49 pm Posted in veritas volume manager Mirroring an Empty volume under VxVM leave a comment » If you are mirroring empty Veritas plexes. then the waiting time is more. Normally we would wait ensuring the plexes are in sync. Run the command on both the nodes #update_drv -f sd c) Verify for the LUNS present. This should save lot of time. 2009 at 6:27 am Posted in Solaris. # format d) Configure emcpower devices. Veritas Identifying multiple paths for a disk under VxVM control leave a comment » This is a routine task for people dealing with VERITAS volume manager. Sun cluster. # /etc/powermt config # /etc/powermt save e) Create the Sun Cluster DID devices. Written by krishsubramanian December 8. veritas volume manager Tagged with Sun cluster. # scdidadm -L g) Add the disks to veritas diskgroup . Run on both nodes if required. # vxdiskadm h) Grow the FS Written by krishsubramanian October 25. If the plex size is large.

So to identify that #luxadm probe Found Enclosure: SUNWGS INT FCBPL Name:LoopA Node WWN:508002000011d7d8 Logical Path:/dev/es/ses0 #luxadm display LoopA SUNWGS INT FCBPL DISK STATUS SLOT DISKS (Node WWN) 0 On (O. Server was running VxVM. 2=Exp Bkpln.K.K.K. I wanted to make sure if the disk has indeed failed. This is a good way to identify the failed disk under internal FCAL loop. 1 Expansion 0:21ºC 1:Not Installed Here we can identify the disk failure at the slot no 2.A) SSC100 #1: O. V880 has internal FCAL loop.K. make sure its in failed was or removed state. 1=Base LoopB. Did these commands to identify the disk failure.A) SSC100 #2: Not Installed SSC100 #3: Not Installed Temperature Sensors – 0 Base. # vxdisk list DEVICE TYPE DISK GROUP STATUS c1t0d0s2 sliced rootdisk rootdg online c1t1d0s2 sliced disk01 rootdg online c1t1d0s2 sliced – online disk02 rootdg failed was:c1t2d0s2 Run vxdiskadm option 4 to remove the disk for replacement.) 2000002037f39796 2 On (Login failed) 3 Not Installed 4 Not Installed 5 Not Installed 6 Not Installed 7 Not Installed 8 Not Installed 9 Not Installed 10 Not Installed 11 Not Installed SUBSYSTEM STATUS FW Revision:9218 Box ID:0 Node WWN:508002000011d7d8 Enclosure Name:LoopA SSC100′s – 0=Base Bkpln.(11.) 2000002037f87099 1 On (O. recently i ran in to a problem of failed disk with V880.(11. Since its a VxvM disk. After running vxdiskadm the output should look similar to this: # vxdisk list DEVICE TYPE c1t0d0s2 sliced c1t1d0s2 sliced DISK rootdisk disk01 GROUP rootdg rootdg STATUS online online .Hi. 3=Exp LoopB SSC100 #0: O.

11. /etc/vx/bin/vxconfigrestore -p /var/vxvmbackups datadg # to precommit the changes /etc/vx/bin/vxconfigrestore -c /var/vxvmbackups datadg # to commit the changes A vxprint output will give the confirmation vxprint -g datadg I just explained how to go about backingup and recovering configuration data using the vxconfigbackup and vxconfigrestore options. Do the luxadm to remove the device. In order to save our a** its always better to be proactive and do the objects backups. One can use the “-l” option to change the default location of the backups. Verify the sync . you would see a new disk. Put the disk into offline state. run the luxadm offline to remove the WWN entries and device links for the failed drive . # devfsadm 7. Run the devfsadm . VxVM is ready for removal of the disk. use format and label 9. check the device file . Written by krishsubramanian October 17.c1t2d0s2 sliced online disk02 rootdg removed was:c1t2d0s2 1. we can use the vxconfigrestore option. 12. # luxadm -e offline /dev/rdsk/c1t2d0s2 3. Whenever a configuration change occurs. #luxadm remove_device /dev/rdsk/c1t2d0s2 4. There may be situations when someone accidentally deletes the volume of a diskgroup. verify with luxadm display . we may face situations where one deletes a volume accidentally or destroy a dg by mistake. As an admin. Give yes to the access question. backups of individual object information will come in handy… You can schedule a cron to backup individual object configuration… . Now use vxdiskadm option 5 to replace the disk. #devfsadm -C . label the disk . 2008 at 5:12 pm Posted in Servers. If we do not have configuration backups of the objects. vxconfigbackupd is a daemon which runs in the background and do upto date backups of all the disk group and the objects associated with it. we are in for some trouble. # vxtask list Thats it you should see the replaced disk doing just fine. In such situations. # vxdctl enable 10. From 3.5 MP3 ( if am correct) vxvm offers vxconfigbackup & vxconfigrestore options for automatic object backups. # vxdisk list . vxconfigbackupd daemon updates the directories with the latest configuration. There can be situations where the configuration information is completely lost due to system outages or reboots. # vxdisk offline c1t2d0s2 2. One can also manually do the object backups using the vxconfigbackupcommand. If we need to recover the configuration information for the entire datadg. # luxadm display LoopA 8. . Replace the disk physically 6. veritas volume manager Veritas recovery features leave a comment » In this post i will explain the volume recovery and disk group recovery in veritas volume manager. All the backups are stored in /etc/vx/cbr/bk/dgnamedirectory. # ls -ld /dev/rdsk/c1t2d0* 5. vxconfigbackup -l /var/vxvmbackups datadg This would update all the configuration backups to /var/vxvmbackups directory for datadg.

stop the volume . these options should be experimented before using in the production setup. using vxmake rebuild the volume from the saved file . open the file simplevol. vxmake -g dgname -d simplevol. mount /simplevol You are ready to perform I/O for the filesystem. vxvol -g dgname start simplevol 10. For most file systems this is the calling of sync to attempt to flush all in-memory data to disk. fsgen assumes that the volume contains a filesystem while gen assumes there is no filesystem. make sure you edit the use_type field alone… 4. fsck -y /dev/vx/rdsk/dgname/simplevol 11. In particular fsgen usage type attempts to flush inmemory data cached for the filesystem residing on the volume. vxvol -g dgname stop simplevol 6. 1. vxassist uses fsgen as the default type. we now need to convert this simplevol from gen to fsgen type. 3. where as vxmake uses gen as the default type… Conversion of volume from one usage type to other cannot be done on the fly./usr/sbin/vxprint -rhmvps ${volume_name} > ${DIR_NAME}/${volume_name}. vxvol -g <dgname> start <vol_name> Volume is ready to do I/O. vxedit -g dgname -rf rm simplevol 7. Written by krishsubramanian August 19. 2008 at 7:03 am Posted in Recovery. Umount the filesystem . it would be fsgen 9. Before going any further on the topic lets see what really fsgen and gen mean.vxout 8. fsgen and gen volume types provide similar but not identical semantics for operations using the vxplex utility. Lets take a look at this output… v simplevol gen ENABLED ACTIVE 8388608 SELECT pl simplevol-01 simplevol ENABLED ACTIVE 8392167 CONCAT – RW sd simple01-01 simplevol-01 simple-01 0 8392167 0 c1t0d0 ENA As you can see from the output.$ {DATE} using the backed up file and vxmake we can easily recover the deleted volume configuration… vxmake -g <dgname> -d <file_name> Verify the recovery using vxprint .. mount the filesystem . remove the volume . vxprint -g dgname -rhmvps simplevol > simplevol. check the vxprint out. . These are the steps that needs to be followed. umount /simplevol 5. vxprint -g datadg -hrt Start the volume .vxout 2. veritas volume manager Converting a volume from gen to fsgen with 10 comments There might be situations where one has to convert a volume from gen type to fsgen type. save the file.vxout using your fav editor and change the use_type field alone from gen to fsgen. I believe it is for this reason we associate all volumes that are using filesystems to be of fsgen type. we have a gen volume named simplevol. start the volume. check for the usage type. do a fsck for the volume. As with the case with any recovery options. vxprint -g dgname -hrt . it requires a volume downtime.

Sign up to vote on this title
UsefulNot useful