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

94 Administering disks
Changing the disk-naming scheme
Note: You cannot run vxdarestore if c#t#d# naming is in use. Additionally,
vxdarestore does not handle failures on persistent simple/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.
For more information about the
vxdarestore command, see the vxdarestore(1M)
manual page.
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.
To remove the error state for persistent simple or nopriv disks in the boot disk group
1 Use vxdiskadm to change back to c#t#d# naming.
2 Enter the following command to restart the VxVM configuration daemon:
# vxconfigd -kr reset
3 If you want to use enclosure-based naming, use vxdiskadm to add a non-persistent
simple disk to the bootdg disk group, change back to the enclosure-based naming
scheme, and then run the following command:
# /etc/vx/bin/vxdarestore
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.
Persistent simple or nopriv disks in non-boot disk groups
If an imported disk group, other than bootdg, consists only of persistent simple and/or
nopriv disks, it is put in the “online dgdisabled” state after the change to the
enclosure-based naming scheme.
To remove the error state for persistent simple or nopriv disks in non-boot disk
groups
1 Deport the disk group using the following command:
# vxdg deport diskgroup
2Use the vxdarestore command to restore the failed disks, and to recover the
objects on those disks: