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 39
Long Delay Time when Running vxconfigd
• Problem: You may experience a long (20 seconds) delay time when
running vxconfigd without a CD-ROM in the CD/DVD drive.
• Workaround: Ensure there is a CD in the CD-ROM drive.
Business Copy (BC) Limitation on XP Disk Arrays
• Problem: VxVM will allow an import of the volumes from only one
BCV on a node where volumes have the same disk and group
identification. If the Primary (P-Vol) is accessible, then this volume
will be used. The Secondary (S-Vol) is only imported if the P-Vol is
inaccessible at the time of import. There is currently no ability to
change the disk group identification (group id) on XP BC volumes.
• Workaround: None
NOTE In the case where VxVM and XP512 BCs are being
used together; if the BCs are split, you cannot then
import the split BC to the machine on which P-Vol is
currently being used. The reason for this is that the
split BC and the P-Vol will have the same private
region, and VxVM allows you to import only one of
them; by default, it chooses P-Vol. If you want,
however, you can import the split BC (S-Vol) onto a
secondary host.
VxVM Commands Do Not Always Show Current Status of VxVM
Disks
• Problem: The VEA and frequently used VxVM commands, such as
vxdisk and vxprint, do not necessarily show the current status of
disks managed by VxVM. VxVM builds and maintains a
configuration database in system memory. This configuration
database also includes Disk Access (DA) records with information
about the disk devices obtained by the vxconfigd scan pass. VxVM
relies on the operating system kernel to notify it of disk status
changes. The HP-UX kernel does not currently notify VxVM of disk
status changes.
• Workaround: Use either of the following commands to force an
update of the VxVM configuration database: