Veritas Volume Manager 5.0.1 Administrator's Guide, HP-UX 11i v3, First Edition, November 2009

Veritas Volume Manager can support failover, but it relies on the administrator
or on an external high-availability monitor to ensure that the first system is shut
down or unavailable before the disk group is imported to another system.
See “Moving disk groups between systems” on page 216.
See the vxdg(1M) manual page.
Corruption of disk group configuration
If vxdg import is used with -C (clears locks) and/or -f (forces import) to import
a disk group that is still in use from another host, disk group configuration
corruption is likely to occur. Volume content corruption is also likely if a file
system or database is started on 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 volumes in the disk group from a backup. To backup
and rebuild the configuration, if nothing has changed, use vxprint -mspvd before
performing any configuration changes, and store the output which can be 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 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
475Administering cluster functionality
Multiple host failover configurations