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

Alternatively, you can update the UDIDs of the cloned disks.
See “Writing a new UDID to a disk” on page 206.
To check which disks are tagged, use the vxdisk listtag command:
# vxdisk listtag
DANAME DMNAME NAME VALUE
c0t06d0 mydg01 - -
c0t16d0 mydg02 - -
.
.
.
c2t64d0 mydg05 my_tagged_disks -
c2t65d0 mydg06 my_tagged_disks -
c2t66d0 mydg07 my_tagged_disks -
c2t67d0 mydg08 my_tagged_disks -
c2t68d0 mydg09 - -
The configuration database in a VM disk’s private region contains persistent
configuration data (or metadata) about the objects in a disk group. This database
is consulted by VxVM when the disk group is imported. At least one of the cloned
disks that are being imported must contain a copy of the current configuration
database in its private region.
You can use the following command to ensure that a copy of the metadata is placed
on a disk, regardless of the placement policy for the disk group:
# vxdisk [-g diskgroup] set disk keepmeta=always
Alternatively, use the following command to place a copy of the configuration
database and kernel log on all disks in a disk group that share a given tag:
# vxdg [-g diskgroup] set tagmeta=on tag=tagname nconfig=all \
nlog=all
To check which disks in a disk group contain copies of this configuration
information, use the vxdg listmeta command:
# vxdg [-q] listmeta diskgroup
The -q option can be specified to suppress detailed configuration information
from being displayed.
The tagged disks in the disk group may be imported by specifying the tag to the
vxdg import command in addition to the -o useclonedev=on option:
207Creating and administering disk groups
Handling cloned disks with duplicated identifiers