Vxdisk list | grep -i configs - db location Vxdg list | grep permlen - the size of the configuration db Private and public are the same partition but continuous (slice 3) format=simple Disk Layouts private and public region slices are on separate partitions (3 & 4), this type of disk is not suitable for moving between different O/S's Sliced Disk layout but are suitable for boot partitions format=sliced Can be converted to CDS CDS (Cross-platform private and public regions are one slice (slice 7), this type is Data Sharing) suitable for moving between different O/S's but not suitable forīoot partitions. Normally configured as slice 3 Once the private region is created it cannot be changed, thus if it fills up then you have to reinitize the disk with a new private region length, see disks -> initialize disk This is the area that will store the users data. Veritas will try and keep 5 copies of the configuration database. A copy of the configuration database is copied to each private region within the disk group. This is were veritas holds the meta data regarding the disk. Install volume manger (use /etc/vx/disk to exclude any disks or controllers) Mode = what mode the vxconfigd is running in enable = enable the vxconfigd daemon (reread the db) disable = disable the vxconfigd daemon stop = kill the vxconfigd daemon (Use 'vxconfigd -k -m enable' to start again) license = print out license info or reread licenses support = display version and components list = display entries in /etc/vx/volboot init = recreate /etc/vx/volboot Note: when in disabled or stopped mode no VX commands will be able to run The vxdctl utility manages aspects of the state of the volume configuration daemon vxconfigd and also manages aspects of configuration for bootstrapping the rootdg disk group. Vxiod set = set number of runnning viod daemon Note: when run on its own it displays # of vxiod daemons that are running. An I/O daemon provides a process context for performing I/O in VxVM.Manage extended disk i/o & handles dirty regions, logging vxiod The vxiod utility starts, stops, or reports on VERITAS Volume Manager (VxVM) I/O daemons. Log to syslog date and timestamp every entry log all possible tracing to file Log to /var/vxvm/vxconfigd.log log to filename Vxconfigd -k -m enable -x -x log -x logfile = Used to backup configuration chnages, the files created can be used with vxmake to restored lost groups.ĭisplay veritas volume manager events used with the vxconfigd daemon Kernel Info The kernel can be in three states:Įnabled - both private and public regions are accessible Disabled - no private or public regions are accessible Detached - only private regions are accessible Monitors for failure events and relocates failed subdisks It can be in three states: Enable = Normal mode Disable = Most operations cannot be be used Booted = Normal startup while using boot disk group If the daemon is stopped it does not disable any configuration state loaded into the kernel, it only affects the ability to make configuration changes until vxconfigd is restarted. Here is a summary of it along in the form of LVM cheatsheet for your quick reference.Veritas Volume Manager VM daemons Maintains system configuration in the kernel & disk (private region). Previously we have seen a series of LVM command tutorials on KernelTalks. Veritas Volume Manager is another volume manager that is as popular as LVM. LVM helps to manage your disk volumes efficiently for performance and data integrity. LVM enables raw disks to be used as a data store, file system defined mount points. LVM is a volume manager in Unix-Linux systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |