VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes

Patches and Fixes in This Version

Chapter 1 35

Disk group conﬁguration corruption usually shows up as missing or

duplicate records in the conﬁguration databases. This can result in a

variety of vxconﬁgd error messages, including 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 speciﬁc disk group

conﬁguration 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 Volume Manager error messages.

If you use the VERITAS VCS product, all disk group failover issues can

be managed correctly. VCS includes a high availability monitor and

includes failover scripts for Volume Manager, 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 Volume

Manager.

Restarting VEA after Obtaining New Licenses If, after installing

and starting VEA, you obtain a new license (either explicitly, using

vxlicinst, or implicitly, by installing bundles B9116AA, B9117AA, or

B9118AA), you will not have access to the newly licensed features until

you restart the VEA service:

Step 1. Stop the VEA backend service:

# /opt/VRTSob/bin/vxsvc -k

Step 2. Start the VEA backend service:

# /opt/VRTSob/bin/vxsvc

Running VEA in Non-English Mode

• Problem: Strings in the search dialog could become corrupted when

running VEA in non-English locales.