Home > Veritas Storage Foundation™ Volume Manager Manual Pages
VXDARESTORE (1M) |
Maintenance Commands |
The use of vxdarestore is required if you use the vxdiskadm command to change from the c#t#d#s#-based to the enclosure-based naming scheme. As a result, some existing simple or nopriv disks go into the "error" state and the VxVM objects on those disks fail.
vxdarestore may be used to restore the disk access records that have failed. The utility also recovers the VxVM objects on the failed disk access records.
Note: vxdarestore may only be run when vxconfigd is using the enclosure-based naming scheme.
The following sections describe how to use the vxdarestore utility under various conditions.
- 1.
- Use the vxdiskadm command to change back to the c#t#d#s# based naming scheme.
- 2.
- Either shut down and reboot the host, or run the following command:
vxconfigd -kr reset
- 3.
- If you want to use the enclosure-based naming scheme, add a sliced disk to the bootdg disk group, use vxdiskadm to change to the enclosure-based naming scheme, and then run vxdarestore.
- 1.
- Deport the disk group using the following command:
vxdg deport diskgroup
- 2.
- Run the vxdarestore command.
- 3.
- Re-import the disk group using the following command:
vxdg import diskgroup
- If there are no simple or nopriv disk access records on a Solaris host.
- If all devices on which simple or nopriv disks are present are not automatically configurable by VxVM. For example, third-party drivers (such as for some versions of EMC PowerPath) export devices that are not automatically configured by VxVM. VxVM objects on simple/nopriv disks created from such disks are not affected by switching to the enclosure based naming scheme.
The vxdarestore command does not handle the following cases:
- If the enclosure-based naming scheme is in use and the vxdmpadm command is used to change the name of an enclosure, the disk access names of all devices in that enclosure are also changed. As a result, any simple/nopriv disks in the enclosure are put into the "error" state, and VxVM objects configured on those disks fail.
- If the enclosure-based naming scheme is in use and the system is rebooted after making hardware configuration changes to the host, this may change the disk access names and cause some simple/nopriv disks to be put into the "error" state.
- If any persistent sliced disk records are defined on the system, these may fail if enclosure-based naming is enabled.
Last updated: 31 Aug 2008
Copyright ©2009 Symantec Corporation
All rights reserved.