Veritas Volume Manager 5.0 Administrator's Guide (September 2006)

168 Creating and administering disk groups
Handling disks with duplicated identifiers
# vxdisk updateudid c2t66d0 c2t67d0
Importing a disk group containing cloned disks
By default, disks on which the udid_mismatch flag or the clone_disk flag has been
set are not imported by the
vxdg import command unless all disks in the disk group have
at least one of these flags set, and no two of the disks have the same UDID. You can then
import the cloned disks by specifying the
-o useclonedev=on option to the vxdg import command, as shown in this example:
# vxdg -o useclonedev=on [-o updateid] import mydg
Note: This form of the command allows only cloned disks to be imported. All non-cloned
disks remain unimported.
If the clone_disk flag is set on a disk, this indicates the disk was previously imported
into a disk group with the udid_mismatch flag set.
The
-o updateid option can be specified to write new identification attributes to the
disks, and to set the clone_disk flag on the disks. (The
vxdisk set clone=on
command can also be used to set the flag.) However, the import fails if multiple copies of
one or more cloned disks exist. In this case, you can either update the UDIDs of the cloned
disks as described in “Writing a new UDID to a disk” on page 167, or you can use the
following command to tag all the disks in the disk group that are to be imported:
# vxdisk [-g diskgroup] settag tagname disk ...
where tagname is a string of up to 128 characters, not including spaces or tabs. For
example, the following command sets the tag, my_tagged_disks, on several disks that
are to be imported together:
# vxdisk settag my_tagged_disks c2t66d0 c2t67d0
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