If you change from OS-based naming to enclosure-based naming, simple or nopriv disks may be put in the "
error" state and cause VxVM objects on those disks to fail.
You can use the
vxdarestore command to handle simple/nopriv disk failures that arise from changing to the enclosure-based naming scheme. You do not need to use this command if your system does not have any simple or nopriv disks, or 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).
You cannot run
vxdarestore if OS-based naming is in use. Additionally,
vxdarestore does not handle failures on simple/nopriv disks that are caused by renaming enclosures, by hardware reconfiguration that changes device names, or by changing the naming scheme on a system that includes persistent sliced disk records.
See "Removing the error state for simple or nopriv disks in the boot disk group" on page 100.
See "Removing the error state for simple or nopriv disks in non-boot disk groups" on page 100.
vxdarestore(1M) manual page.
If the boot disk group (usually aliased as
bootdg) is comprised of only simple and/or nopriv disks, the
vxconfigd daemon goes into the disabled state after the naming scheme change.
To remove the error state for simple or nopriv disks in the boot disk group
vxdiskadmto change back to c#t#d#s# naming.
vxconfigd -kr reset
vxdiskadmto add a sliced disk to the
bootdgdisk group, change back to the enclosure-based naming scheme, and then run the following command:
If an imported disk group, other than
bootdg, is comprised of only simple and/or nopriv disks, the disk group is in the "
dgdisabled" state after the change to the enclosure-based naming scheme.
To remove the error state for simple or nopriv disks in non-boot disk groups
vxdg deport diskgroup
vxdarestorecommand to restore the failed disks, and to recover the objects on those disks:
vxdg import diskgroup