Error In Disk Group Configuration
Contents |
use from another host, disk group configuration corruption is likely to occur. Volume content corruption is also likely if vxconfigd is not running cannot enable a file system or database is started on the imported volumes
Vxvm Vxdctl Error V-5-1-1589 Enable Failed: Volboot File Not Loaded
before the other host crashes or shuts down. If this kind of corruption occurs, your configuration must vxvm vxdctl error v-5-1-1589 enable failed: error in disk group configuration copies typically be rebuilt from scratch and all data be restored from a backup. There are typically numerous configuration copies for each disk group, but corruption nearly always
Vxvm Vxdisk Error V-5-1-684 Ipc Failure: Configuration Daemon Is Not Accessible
affects all configuration copies, so redundancy does not help in this case. As long as the configuration backup daemon, vxconfigbackupd, is running, VxVM will backup configurations whenever the configuration is changed. By default, backups are stored in /etc/vx/cbr/bk. You may also manually backup the configuration using the vxconfigbackup utility. The configuration can be rebuilt using the vxrestore utility. See the vxconfigbackup, vxconfigbackupd, vxconfigrestore man pages. Disk group configuration corruption usually shows up as missing or duplicate records in the configuration databases. This can result in a variety of vxconfigd error messages VxVM vxconfigd ERROR V-5-1-569 Disk group group,Disk disk: Cannot auto-import group: reason where the reason can describe errors such as: Association not resolved Association count is incorrect Duplicate record in configuration Configuration records are inconsistent These errors are typically reported in association with specific disk group configuration copies, but usually apply to all copies. The following is usually displayed along with the error: Disk group has no valid configuration copies If you use the Veritas Cluster Server product, all disk group failover issues can be managed correctly. VCS includes a high availability monitor and includes failover scripts for VxVM, VxFS, and for several popular databases. The -t option to vxdg prevents automatic re-imports on reboot and is necessary when used with a host monitor (such as VCS) that controls imports itself
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English ä¸æ–‡(简体) English Français Deutsch Italiano 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet Using vxconfigrestore to restore the Veritas private region Article:000087440 Publish: Article URL:http://www.veritas.com/docs/000087440 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe https://sort.veritas.com/public/documents/sf/5.1/aix/html/vxvm_admin/ch14s02s03.htm Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Using vxconfigrestore to restore the Veritas private region. Solution  This article is a part of a set on troubleshooting failed, or failing, disks. Click here to start at the beginning: http://www.symantec.com/docs/TECH200618  Table of ContentsIntroduction1. Verify the https://www.veritas.com/support/en_US/article.000087440 integrity of a configuration database backup2. Back up the existing configuration3. Deport the disk group to be restored4. Restore the configuration5. Commit the restorationIntroduction(Back to top)Use vxconfigrestore to restore a private region backup that was created with vxconfigbackup. A restore may be necessary if the private region of a diskgroup has been corrupted or lost. Vxconfigrestore does not restore data to the actual volumes. 1. Verify the integrity of a configuration database backup(Back to top)Before running vxconfigrestore, verify the integrity of the configuration database backup to ensure that the data being restored is correct. The integrity of the backup can be verified with vxprint.  Note: See this article for details on verifying the integrity of a configuration database backup"Verifying the integrity of a configuration database backup"http://www.symantec.com/docs/TECH201925 2. Back up the existing configuration(Back to top)Before running vxconfigrestore, complete these two steps to back up the existing configuration. Make a copy of the directory that contains the existing vxconfigbackup files. By default, the vxconfigbackup files are stored under /etc/vx/cbr/bk. The location may be different if a manual backup was performed using the "-l" argument. U
is likely to occur. Volume content corruption is also likely if a file system or database is started on https://sort.symantec.com/public/documents/sf/5.0/hpux/html/vxvm_admin/ag_ch_cluster_vm21.html the imported volumes before the other host crashes or shuts down. If this kind of corruption occurs, you must probably rebuild your configuration from scratch and reload all http://unixadminschool.com/blog/2012/03/recovery-of-diskgroup-in-vxvm-veritas-volume-manager/ volumes in the disk group from a backup. To backup and rebuild the configuration, if nothing has changed, use vxprint -mspvd and store the output which can be error in fed to vxmake to restore the layouts. There are typically numerous configuration copies for each disk group, but corruption nearly always affects all configuration copies, so redundancy does not help in this case. Disk group configuration corruption usually shows up as missing or duplicate records in the configuration databases. This can result in a variety of vxconfigd error in disk error messages VxVM vxconfigd ERROR V-5-1-569 Disk group group,Disk disk:Cannot auto-import group: reason where the reason can describe errors such as: Association not resolved
Association count is incorrect
Duplicate record in configuration
Configuration records are inconsistent These errors are typically reported in association with specific disk group configuration copies, but usually apply to all copies. The following is usually displayed along with the error: Disk group has no valid configuration copies See the Veritas Volume Manager Troubleshooting Guide for more information on Veritas Volume Manager error messages. If you use the Veritas Cluster Server product, all disk group failover issues can be managed correctly. VCS includes a high availability monitor and includes failover scripts for VxVM, VxFS, and for several popular databases. The -t option to vxdg prevents automatic re-imports on reboot and is necessary when used with a host monitor (such as VCS) that controls imports itself, rather than relying on automatic imports by Veritas Volume Manager. ^Return to Top
LinkedIn How to Use this Site ? Recovery of DISKGROUP in VXVM (Veritas Volume Manager). March 28, 2012By Yogesh RahejaOther Learning Articles that you may like to read Latest ArticlesInformation CentersLinux AdminSolaris AdminVxVM AdminVCS AdminCareer GuidanceScriptingStorage AdminQuick ReferenceLatest Articles Information Centers Linux Admin Solaris Admin VxVM Admin VCS Admin Career Guidance Scripting Storage Admin Quick Reference Free Courses We Offer Linux Administration Interview Preparation [Free Email Crash Course] Roles and Responsibilities of System Admin [Free Course] Getting Started with RHEL7 Administration [Free Course] Paid Training Courses we Offer Self Paced CoursesLive WebexSelf Paced CoursesSolaris11 Self Paced Video Learning RHEL7 Self Paced Video Learning VxVM + VCS Self Paced Video Learning Solaris10 Self Paced Video Learning Puppet Automation Self Paced Video Learning Live WebexSolaris 11 Administration Live WebEx Puppet Automation - Live WebEx Veritas ( VCS+VxVM) Live Webex Since long time I was thinking to have practical hands-on to how to recover Diskgroup in VXVM (which got faulty and we are unable to import that). But unfortunately I wont have real time outputs with me to show how that can be achieved. But here I got all of them from one of my Friend "Karn Gussain -> Unix Killer". Thanks Karn because of you I am able to post this unique/complex procedure at our gurkulindia and many of Unix SA's will take this document as a reference in such critical situations. We have sol-test as a Physical server (Global Zone) having sol-test-zone as a Logical Server (Non-Global Zone). root@sol-test: zoneadm list -cvi ID NAME            STATUS    PATH        BRAND   IP 0 global          running   /            native  shared 1 sol-test-zone  Â