Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

You do not need to perform either procedure if the devices on which any simple
or nopriv disks are present are not automatically configured by VxVM (for example,
non-standard disk devices such as ramdisks).
The disk access records for simple disks are either persistent or non-persistent.
The disk access record for a persistent simple disk is stored in the disk’s private
region. The disk access record for a non-persistent simple disk is automatically
configured in memory at VxVM startup. A simple disk has a non-persistent disk
access record if autoconfig is included in the flags field that is displayed by the
vxdisk list disk_access_name command. If the autoconfig flag is not present,
the disk access record is persistent. Nopriv disks are always persistent.
Note: You cannot run vxdarestore if c#t#d# naming is in use. Additionally,
vxdarestore does not handle failures on persistent simple or nopriv disks that
are caused by renaming enclosures, by hardware reconfiguration that changes
device names. or by removing support from the JBOD category for disks that
belong to a particular vendor when enclosure-based naming is in use.
See “Removing the error state for persistent simple or nopriv disks in the boot
disk group” on page 105.
See “Removing the error state for persistent simple or nopriv disks in non-boot
disk groups” on page 106.
See the vxdarestore(1M) manual page.
Removing the error state for persistent simple or nopriv disks
in the boot disk group
If all persistent simple and nopriv disks in the boot disk group (usually aliased as
bootdg) go into the error state, the vxconfigd daemon is disabled after the naming
scheme change.
Note: If not all the disks in bootdg go into the error state, you need only run
vxdarestore to restore the disks that are in the error state and the objects that
they contain.
105Administering disks
Changing the disk-naming scheme