VxVM Restoring Configuration Data

Restoring Configuration Data

When configuration information is lost due to a system outage or a mistake at the keyboard, the configuration can often be recovered to a point in time (preferably to a point in time when a known working backup was taken with vxconfigbackup(1m)) with the vxconfigrestore(1m) utility. The following example shows how to restore the contents on the oradg disk group using the configuration backup in the /etc/dgbackups directory:

$ /usr/lib/vxvm/bin/vxconfigrestore -l /etc/dgbackups oradg

Diskgroup oradg configuration restoration started ......

Installing volume manager disk header for c1t1d0s2 ...
Installing volume manager disk header for c1t2d0s2 ...
Installing volume manager disk header for c1t3d0s2 ...
Installing volume manager disk header for c1t4d0s2 ...
Installing volume manager disk header for c1t5d0s2 ...
Installing volume manager disk header for c1t6d0s2 ...
-
oradg's diskgroup configuration is restored (in a precommitted state).
Diskgroup can be accessed in read only and can be examined using
vxprint(1m) in this state.

Run:
vxconfigrestore -l /etc/dgbackups/ -c oradg ==> to commit the restoration.
vxconfigrestore -l /etc/dgbackups/ -d oradg ==> to abort the restoration.

When vxconfigrestore(1m) is invoked, the configuration will be staged to a transient location, allowing the administrator to validate the configuration with the vxprint(1m) utility. If the configuration looks sound, the configuration can be committed to the disk headers and the configuration database by invoking vxconfigrestore(1m) with the "-c" (commit) option:

$ /usr/lib/vxvm/bin/vxconfigrestore -l /etc/dgbackups/ -c oradg

Committing configuration restoration for diskgroup oradg ....

oradg's diskgroup configuration restoration is committed.

Once the configuration is restored, the volumes can be started, and the file systems that reside on those volume can be mounted.