Documente Academic
Documente Profesional
Documente Cultură
html
VxVM Disk
Q-1 How to add a disk to a disk group in Veritas Volume Manager?
Ans: To add the physical disk c0t0d0 in the disk group homedg calling it disk90 in Veritas Volume
Manager:
# vxdg -g homedg adddisk disk90=c0t0d0
Q-2 How to remove a disk from a disk group in Veritas Volume Manager?
Ans: To remove a disk, disk90, from a disk group, homedg, in Veritas Volume Manager:
# vxdg -g homedg rmdisk disk90
Q-4 How to list all disks and display their status in VxVM?
Ans: # vxdisk list
Q-5 How to remove a grayed out or obsolete disk, or remove a disk from a disk group in Veritas
Volume Manager?
Ans: # vxdisk rm disk01
Q-6 How to remove a disk so that it is no longer under Veritas Volume Manager controls?
Ans: # vxdisk rm c0t0d0
Q-7 How to add or bring a disk under Veritas Volume Manager control?
Ans: To add or bring a disk under Veritas Volume Manager control:
# vxdiskadd c0t0d1
or
# vxdisksetup -i c0t0d1
Note: It might help to newfs the s2 slice of the disk and perform a vxdctl enable to get it to add a disk.
Q-8 How to remove a volume and any subdisks and plexes associated in VxVM?
Ans: # vxedit -rf rm volume_name
Q-9 How to rename the disk disk90 to be called disk80 in the group rootdg in Veritas Volume
Manager?
Ans: # vxedit -g rootdg rename disk90 disk80
Q-10 How to set disk90 in the group homedg to be a hot spare in Veritas Volume Manager?
Ans: # vxedit -g homedg set spare=on disk90
Q-11 How to set the comment field of subdisk subdisk01-01 to "comments are here"?
Ans: # vxedit set comment"comments are here" subdisk01-01
Q-12 How to sets the user to ep, the group to epgrp and the mode rw-rw-rw on the volume vg01?
Ans: # vxedit set user=ep group=epgrp mode=0666 vg01
Disk Group
Q-1 How to display the default disk group?
Ans: #vxdg defaultdg
Q-6 How to create a disk group with a specified disk group version no.?
Ans: # vxdg T <DG version> init <disk group>
Q-7 How to make a non CDS disk group to CDS disk group or vice versa?
Ans: # vxdg g <disk group> set cds=on|of
Q-8 How to import a disk group?
Ans # vxdg import <disk group>
Q-2 How set the number of kernel thread in Veritas Volume Manager?
Ans: # vxiod set 10
Note: This is the daemon that allows for extended I/O calls without blocking calling processes. As this is a
kernel thread you cannot see it with ps command so you have to use the vxiod command to see if it is
running.
Q-8 How to mirror all the volumes on the disk rootdisk to disk90 in Veritas Volume Manager?
Ans: # vxmirror rootdisk disk90
Q-9 How to rebuild the partition table after a root disk failure in Veritas Volume Manager?
Ans: To rebuild the partition table after recovering from a root disk failure after re-mirroring the disk
in Veritas Volume Manager:
# vxmksdpart -g rootdg diskpart 1 0x03 0x01
Q-10 How to attach a plex to a volume in Veritas Volume Manager?
Ans: # vxplex att <volume_name> <plex-name>
Q-11 How to display all the available information in Veritas Volume Manager?
Ans: # vxprint ht
Q-12 How to display all the information about plexes in Veritas Volume Manager?
Ans: # vxprint -l <plex-name>
OR
# vxprint lp
Q-13 How to display all the information about subdisks in Veritas Volume Manager?
Ans: # vxprint -l <diskname>
OR
# vxprint st
Q-14 How to display all the information about volumes in Veritas Volume Manager?
Ans: # vxprint -l volumename
OR
# vxprint -vl
OR
# vxprint vt
Q-15 How to list all the volumes on a boot disk Veritas Volume Manager?
Ans: # vxprint -t -v -e 'aslist.aslist.sd_disk="boot-disk-name"'
Q-16 How to bring a volume back online in background mode in Veritas Volume Manager?
Ans: # vxrecover -b volume
Q-21 How to move the contents of a subdisk to another in Veritas Volume Manager?
Ans: To move the contents of subdisk-90 to subdisk-80 in Veritas Volume Manager:
# vxsd mv subdisk-90 subdisk-80
Q-22 How to report disk statistics in Veritas Volume Manager?
Ans: # vxstat g diskgroup d
Q-23 How to trace all the I/O on the selected volume in Veritas Volume Manager?
Ans: # vxtrace <volume-name>
Q-31 How to get the path of a particular disk or how to check the enclosure of a particular device?
Ans # vxdmpadm getsubpaths dmpnodename=<device name (c1t2d0)>
Or
# vxdisk list <device name (c1t2d0)>
Q-35 How to reserve a disk for special purpose or vice versa? (Reserve disk cant use for normal
volume operation)
Q-36 How do you determine by how much a Veritas Volume can be expanded?
Ans: # vxassist g <DG> maxgrow <volume>
Q-43 How to display free space on the disks in Veritas volume Manager?
Ans: # vxdg free
Q-44 How to find how much a volume can be grown by in Veritas Volume Manager?
Ans: # vxassist maxgrow <volume-name>
Q-45 How to find the largest raid5 partition you can have in Veritas Volume Manager?
Ans: # vxassist maxsize layout=raid5
Q-46 How to find the largest stripe you can have in VxVM?
Ans: # vxassist maxsize layout=stripe
Q-47 How to move a volume to another disk except a particular one in Veritas Volume Manager?
Ans: To move a volume vg01 to any other disk except disk90 in Veritas Volume Manager:
# vxassist move vg01 !disk90
Q-48 How to set a preferred plex to read from in Veritas Volume Manager?
Ans: # vxvol rdpol prefer <volume-name> <plex-name>
Q-49 How to set a round robin read policy on the volume in Veritas Volume Manager?
Ans: # vxvol rdpol round volume_name
Q-51 How to add a log disk for a volume in Veritas Volume Manager?
Ans: To add a log disk for a raid5 or mirror of a volume in Veritas Volume Manager:
# vxassist addlog volume-name
Example to make a 50 mb mirror on volume called vg01 using any two free disks:
# vxassist mirror vg01 50m layout=mirror
Q-56 How to create a raid5 volume in Veritas Volume Manager?
Ans: To create a raid5 volume in Veritas Volume Manager using any available disks:
# vxassist make vg01 100m layout=raid5
Example to make a volume called vg01 to be 100m big using the disk disk80:
# vxassist g <DG> make <vol> 100m disk80
Q-58 How to create a volume with a mirror and log in Veritas Volume Manager?
Ans: Example to make a volume named vg01 with 50mb stripe disk using disks disk80 and disk90 and
mirror this on a stripped mirror using disk92 and disk95 and use a log subdisk:
# vxassistg <DG> make <vol> layout=mirror,stripe,log disk80 disk90 disk92 disk95
Q-61 How to mirror a volume on any free disk in Veritas Volume Manager?
Ans: To mirror a volume vg01 on any free disk in Veritas Volume Manager:
# vxassist mirror vg01
Q-65 How to enable, disable or verify the vxconfigd daemon in Veritas Volume Manager?
To verify the vxconfigd daemon in Veritas Volume Manager:
# vxdctl mode
This script is called by the vxmirror command if the root disk is required to be mirrored. It is also called
from the vxdiskadm menus through the choice of the mirror volumes on a disk operation.
Q-69 What is vxmirror utility?
Ans: The vxmirror command provides a mechanism to mirror all the contents of a specified disk, to
mirror all currently un-mirrored volumes in the specified disk group, or to change or display the current
defaults for mirroring. All volumes that have only a single plex (mirror copy), will be mirrored by adding
an additional plex.
Volumes containing subdisks that reside on more than one disk will not be mirrored by vxmirror.
vxmirror is generally called from the vxdiskadm menus. It is not an interactive command and once called,
will continue until completion of the operation or until a failure is detected.
Q-70 What is vxunroot utility?
Ans: The vxunroot script causes the root, swap, usr and var file systems to be converted back into
being accessible directly through disk partitions instead of through volume devices. Other changes made
to ensure the booting of the system from the root volume are also removed such that the system will
boot with no dependency on the Volume Manager.
For vxunroot to work properly, all but one plexes of rootvol, swapvol, usr and var should be removed.
The plexes left behind for the above volumes should be the ones created by vxrootmir or the original
ones created when the root disk was encapsulated. This will ensure that the underlying subdisks will
have equivalent partitions defined for them on the disk. If none of these conditions are met, the
vxunroot operation will fail and none of the volumes will be converted to disk partitions.
Q-71 How to recover from the root disk and root-mirror disk failure?
Ans:
1) Boot the system into single user mode from Solaris installation CD.
ok boot cdrom s
2) Use the format command to create partitions on the new root disk (c0t0d0s2). These should be
identical in size to those on the original root disk before encapsulation unless you are using this
procedure to change their sizes.
10) Now edit the vfstab file to replace the volume device names with the disk slices.
12) Now reboot the system. System will be booted into multi user mode.
# init 6
Q-72 How to recover the VxVM configuration after reinstallation of Solaris?
Ans: Reinstallation is necessary if all copies of your root disks are damaged, or if certain critical files
are lost due to file system damage. Disconnect all the disks which are not involved in reinstallation
process.
1) Install the Solaris OS
2) Install the VxVM software and also install the VxVM license also.
3) Recover the VxVM configuration.
4) touch the /etc/vx/reconfig.d/state.d/install-db file
5) Shut down the system
6) Reattach the disks which were removed before installation.
7) Reboot the system and when the system comes up, bring it into single user mode.
8) Remove the /etc/vx/reconfig.d/state.d/install-db file
9) Start VxVM IO daemons.
# vxiod set 10
10) Start the VxVM daemon in disable mode
# vxconfigd m disable
11) Initialize the vxconfigd daemon
# vxdctl init
12) Initialize the DMP subsystem
# vxdctl initdmp
13) Now start the vxconfigd daemon
# vxdctl enable
14) Now reboot the system
Now the configuration preserved on the disks not involved in the reinstallation has now been recovered.
Q-73 How to convert the SVM meta devices into VxVM volumes?
Ans: There are three utilities used to convert SVM meta devices into VxVM volumes.
1) Run the preconvert utility to analyze the current SVM configuration:
# preconvert
The preconvert utility analyzes the current Solaris Volume Manager configuration and builds a
description for the new VxVM configuration. preconvert does not make any changes to the Solaris
Volume Manager configuration or to the host system.
2) Now run the showconvert utility to display the preconvert conversions plan into readable format.
# showconvert
3) Now run the convertname utility to display the VxVM volume names .
# convertname /dev/md/dsk/d12
Note: The convertname utility takes Solaris Volume Manager device paths as arguments (metadevice
paths or raw disk paths) and returns the VxVM volume path for the device as it will show after the
conversion.
4) Now run the doconvert utility to start the actual conversion process
# doconvert
2. How will you create private and shared disk group using VxVM ?
ANS: For Private DG:
Command: vxdg init
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
system.
Growto option: This will grow your file system as per the new size. This WILL NOT ADD
new size to the existing one.
Shrinkby option: This will shrink your file system by reducing new size from existing file
system.
Shrinkto option: This will shrink your file system as per the new size. This WILL NOT
REDUCE the file system by reducing new size.
Command:
vxassist -g [growto, growby, shrinkto, shrinkby] length
7. How will you setup and unsetup disks explicitly using VxVM ?
ANS: You can use /etc/vx/bin/vxdiskunsetup to unsetup the disk, and /etc/vx/vxdisksetup
to setup the disk.
8. How will you list the disks, which are in different disk groups ?
ANS: vxdisk list is the command will list the disks from the DG which is currently
imported, you can check the same using vxprint command too. vxdisk -o alldgs list
command list all the disks which are in different dg's.
10. If, vxdisk list command gives you disks status as "error", 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, otherwise unsetup the disk using using /etc/vx/bin/vxdiskunsetup and setup
the disks again using /etc/vx/bin/vxdisksetup, this will definitely help! [
/etc/vx/bin/vxdiskunsetup will remove the private region from the disk and destroys data,
backup the data before using this option]
2. How do you remove Meta only for the root slice? Remaining slices should run under meta?
3. What you would do if you want to replace a slice using met replace option?
5. What are the common errors you find in Solaris Volume manager?
6. You have a boot disk under SVM; the machine fails to boot and remains in ok prompt? what could
be the possible reason?
7. Metastat -p shows a metavolume needs replacement. Metavolume is a single way mirror only.
Actually you find disk and metavolumes are ok and I/O is happening to the file systems how you will
remove the Meta replace message that comes out of metastat.
9. What is the difference between private and public regions in VERITAS Volume manager?
10. what would you do if the private region of a particular disk group is full? What are the design
considerations for the size of private region in Vxvm disk group?
11. How to replace a corrupt private region? In Vxvm 4, 5 and greater versions
12. How would you convert a volume from gen to fsgen? why should you do that?
15. What is the difference between Vxdump and EMC power path?
16. Vxdisk -o alldgs list o/p shows some disk groups in braces What does that signify?
17. What are the various layouts that are available in VxVM?
23. Plex is in a disabled state. How will you recover? what are the steps to follow?
26. Whats the difference between SVM and VxVM? What would you recommend to your clients? Why?
27. What are the various clusters you have worked on?
30. How will you start VCS service? What are the configuration files in VCS?
Which action will most evenly distribute the I/O across all disks in the disk group?
a. Mirror the volume using the two unused disks
b. Remove the two unused disks from the disk group
c. Resize the volume to use all of the disks
d. Stripe the volume across all four disks
12. Which layout options are available when using the vxassist command to create a
layered volume? (Choose two)
a. concat-mirror
b. mirror-concatenate
c. stripe-mirror
d. mirror-stripe
e. concatenate-stripe
f. stripe-concatenate
13. Which menu option within the vxdiskadm utility can be used to create a new disk
group?
a. Add or initialize one or more disks
b. Add or initialize one or more disk groups
c. Make a disk available for hot-relocation use
d. Enable access to (import) a disk group
14. What are the benefits of enclosure-based naming? (Choose three)
a. easier fault isolation
b. improved array availability
c. device-name independence
d. improved SAN management
e. improved disk performance
15. Which command creates a 10 GB volume named datavol in the datadg disk group,
assuming that the /etc/default/vxassist file does NOT exist on the system?
a. vxvmvol -g datadg new 10g datavol
b. vxvol -g datadg create 10g datavol
c. vxassist -g datadg make datavol 10g
d. vxdisk -g datadg 10g newvol datavol
16. Online resizing of a Volume Manager volume and file system requires that the file
system is _____.
a. in the bootdg disk group
b. checked before the process
c. shared across disk groups
d. mounted during the process
17.Which command displays the contents of the volboot file?
a. vxvolboot list
b. vxcat volboot
c. vxdctl list
d. vxconfig volboot
18. What are the characteristics of a space-optimized snapshot? (Choose two)
a. contains compressed primary data
b. references the primary data
c. requires less space than a full-sized point-in-time copy
d. initially contains a complete copy of primary data
e. performs an automatic atomic-copy resynchronization
19. Which Veritas Volume Manager command displays average volume read and
write times?
a. vxprint
b. vxstat
c. vxtrace
d. vxinfo
20. What is the recommended next step to be performed after a failed disk has been
physically replaced?
a. Logically replace the disk in volume Manager
b. Unrelocate any relocated Volume Manager subdisks to the new disk
c. Synchronize any STALE plexes
d. Ensure that the operating system can access the disk
21. Which commands can be used to manage dynamic multipathing? (Choose two)
a. vxddladm
b. vxdiskadm
c. vxdmpadm
d. vxpathadm
e. vxassist
22. Which task related to protecting the Volume Manager configuration has the steps
precommit and commit associated with it?
a. restore
b. backup
c. replace
d. remove
Answers: 1-d, 2-d,3-a, 4-b, 5-c, 6-a, 7-a, 8-c, 9-c,10-a,11-d, 12-a&c, 13-a, 14-a&c&d,
15-c, 16-d, 17-c, 18-b&c, 19-b, 20-d, 21-b&c, 22-a
Explain What are the common errors you find in Solaris Volume manager?
1) Disks failures (Boot device failures)
2) Insufficient state database replicas issues
3) Wrong entries in /etc/vfstab file
How to create a shared disk group in VxVM?
Creating shared dg form the existing dgs
1) List all the dg available: #vxdg list
2) Find out the node that is master or slace using:
#vxdctl -c mode
3) Deport the disk groups to be shared: #vxdg deport
<dg name>
4) Import dgs to be shared: #vxdg -s import < dg
name> % Do this on master node
5) To check the shared disk groups: #vxdg list
Knowing how to build a volume from scratch does not hurt and is a good exercise in learning the
building blocks of VX. Lets see in detail how it works out. vxmake allows you to create objects
individually.
The approach will be to create Subdisks, associate plex with subdisk and put the plex in the volume. I
am assuming that the disk test01 is part of the testdg diskgroup.
The volboot is an important file, it contains the hostid of the system and this is used by VxVM to
establish the ownership of disks. The volboot is important in the management of vxconfigd as well. If
the rootdisk is under VxVM control it also has the information of boot disk group information.
During boot up, vxvm config dameon reads the volboot file, if the file is missing, vxconfigd fails and the
boot sequence is aborted.
Solution will be
a) to copy the volboot file from backup and reboot the system.
b) If a valid backup is not available we may need to run the sequence of commands to enable it again.
The way to resolve this is to disable the disks path from DMP control. Since there is only one path to
this disk, the -f (for force) option needs to be used:
root@abc>/>
- vxiod set 10
- ps -ef |grep vxconfigd. If vxconfigd is not running, then run /usr/sbin/vxconfigd -m disable
- vxdctl mode. Should see it is in disabled mode.
- vxdctl init
- vxdctl enable
- vxdctl mode
6. Check the diskgroups.
- vxdg list
7. Deport the rootdg so that it does not come up again.
- format -d <c#t#d#>
9. Once this is done, the disks should show as error.
- vxdisk list
10. Re encapsulate the disk.
- cd /etc/vx/reconfig.d/state.d/
- rm install-db
- vxdiskadm. Option 2 to encapsulate the primary bootdisk
- Reboot machine upon completed Option 2 above.
11. Verify for the boot and all volumes coming up clean.
- vxprint -ht, to verify all the volume are enabled. If the volume not started, then run vxvol -g
groupname startall to start the volume.
- Revert back the /etc/vfstab.withvm to /etc/vfstab
- mount all the volume and verify.
12. Mirror to second bootdisk
VxVM Upgrade
Posted February 13, 2010
Filed under: veritas volume manager |
Leave a Comment
Lets look at VxVM Upgrade this week
The setup is
a) Solaris 9
b) VxVM 4.0 / VxDMP > No powerpath
c) Oracle databases.
I upgraded to Storage Foundation 5.0 MP3. The tech plan is as below:
1. Install the VRTSspt Package. Down load the package from symantec website
2. Run the VRTSexplorer and keep the file at a safe location if you may need it in case you run in any
issue.
Make changes to /etc/vfstab to ensure the system boots from the mirror disk ( c#t#d#)
5. Boot the server from rootmirror and verify for the server coming up.
7. Check for the pre-requiste packages. Solaris 9 for Storage Foundation need
http://www.sun.com/downloads
and choose A-Z downloads
9. Verify the pre-staged software is not corrupted and working fine. ( You can do this by doing a tar
and keeping the software ready)
10. Ensure all applications/Databases are shutdown and the file-systems are down.
Note: If a file system is not clean, enter the following commands for that file system:
# /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.
17. Remove all packages that start with VRTS but for VRTSvlic. Dont remove the VRTSvlic packages. I
believe you can remove this as well, but I have not tried it myself.
# ./installer
Note : Answer the questions and complete the installation. Insome cases veritas may not start
correctly and will require a reboot.
19. If you are upgrading from 4.0 or later the licenses should take of themselves.
20. Manually Encapsualte the rootdisk after upgrade.
# vxdiskadm
Choose option 2 and give the root disk for encapsulation.
a) Get the LUN information from Storage and update the sd.conf accordingly on both the servers
b) Make the LUNS Visible on the server. Run the command on both the nodes
#update_drv -f sd
c) Verify for the LUNS present; # format
d) Configure emcpower devices. Run on both the servers.
# /etc/powermt config
# /etc/powermt save
e) Create the Sun Cluster DID devices. Run on both nodes if required.
# devfsadm
# scgdevs
f) Verify the sun Cluster DID devices. # scdidadm -L
g) Add the disks to veritas diskgroup ; # vxdiskadm
h) Grow the FS
#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.K.) 2000002037f87099
1 On (O.K.) 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
SSC100s 0=Base Bkpln, 1=Base LoopB, 2=Exp Bkpln, 3=Exp LoopB
SSC100 #0: O.K.(11.A)
SSC100 #1: O.K.(11.A)
SSC100 #2: Not Installed
SSC100 #3: Not Installed
Temperature Sensors 0 Base, 1 Expansion
0:21C
1:Not Installed
Here we can identify the disk failure at the slot no 2. This is a good way to identify the failed disk
under internal FCAL loop.
Since its a VxvM disk, make sure its in failed was or removed state.
# 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. After running vxdiskadm the output
should look similar to this:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced disk01 rootdg online
c1t2d0s2 sliced - - online
- - disk02 rootdg removed was:c1t2d0s2
1. Put the disk into offline state; # vxdisk offline c1t2d0s2
2. VxVM is ready for removal of the disk, run the luxadm offline to remove the WWN entries and device
links for the failed drive ; # luxadm -e offline /dev/rdsk/c1t2d0s2
3. Do the luxadm to remove the device. ; #luxadm remove_device /dev/rdsk/c1t2d0s2
4. check the device file ; #devfsadm -C ; # ls -ld /dev/rdsk/c1t2d0*
5. Replace the disk physically
From 3.5 MP3 ( if am correct) vxvm offers vxconfigbackup & vxconfigrestore options for automatic
object backups. 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. All the backups are stored
in /etc/vx/cbr/bk/dgnamedirectory. Whenever a configuration change
occurs, vxconfigbackupd daemon updates the directories with the latest configuration. One can also
manually do the object backups using the vxconfigbackup command. One can use the -l option to
change the default location of the backups.
vxconfigbackup -l /var/vxvmbackups datadg
This would update all the configuration backups to /var/vxvmbackups directory for datadg. If we
need to recover the configuration information for the entire datadg, we can use
the vxconfigrestore option. There can be situations where the configuration information is completely
lost due to system outages or reboots.
/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. There may be situations when someone accidentally deletes the volume
of a diskgroup. In such situations, backups of individual object information will come in handy You
can schedule a cron to backup individual object configuration