vxconfigrestore

NAME

vxconfigrestore - restore disk group configuration

SYNOPSIS

DESCRIPTION

The vxconfigrestore utility is used to restore a disk group's configuration information if this has been lost or become corrupted. The disk group whose configuration is to be restore is specified either by name or by ID.

Any disks whose private region headers have become corrupted are reinstalled when the disk group configuration is restored. If you choose not to reinstall the VxVM headers for these disks, it may not be possible to restore the disk group.

The disk group configuration backup files may have been automatically created by the vxconfigbackupd daemon, or manually by running the vxconfigbackup command.

Restoration of a disk group configuration has two stages: precommit and commit. The precommit stage allows you to temporarily load the configuration that is to be restored, and examine it using the vxprint utility. At this stage, the disk group configuration is read-only. No permanent changes are written to disk until you choose to commit them. If desired, you can abandon the restore operation at the precommit stage.

OPTIONS

-c

(Commit) Permanently commits changes to the disks. The restoration must be at the precommit stage for this command to succeed.

Volumes are synchronized in the background. For large volume configurations, it may take some time to perform the synchronization. You can use the vxtask -l list command to monitor the progress of this operation.

-d

(Decommit) Abandons the restore operation at the precommit stage.

-n

(Precommit: no installation of VxVM disk header) Loads the disk group configuration at the precommit stage. This option specifies that disks whose private region headers have become corrupted are not to be reinstalled.

-l directory

Specifies a directory other than the default (/etc/vx/cbr/bk) where the backup configuration files are located.

-p

(Precommit: load) Loads the disk group configuration at the precommit stage. This option specifies that disks whose private region headers have become corrupted are to be reinstalled. The vxprint command can be used to examine the disk group configuration.

This is the default operation if no option is specified.

EXAMPLES

Load the configuration of the mydg disk group from the default directory, and reinstall disks that have corrupted VxVM disk headers:

Load the configuration of the mydg1 disk group from the backup files in the directory /dgbackup/mydg1 without reinstalling any disks that have corrupted private region disk headers:

Abandon the restoration of the mydg2 disk group at the precommit stage:

Commit the restoration of the configuration of the mydg disk group from the backup files in the directory /dgbackup/mydg:

FILES

/etc/vx/cbr/bk/dgname.dgid/dgid.dginfo

Default location of backup file for disk group information.

/etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo

Default location of backup file for disk attributes.

/etc/vx/cbr/bk/dgname.dgid/dgid.binconfig

Default location of backup file for binary configuration copy.

/etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec

Default location of backup file for configuration records in vxprint -m format.

NOTES

A disk group must be restored on the same physical disks as are defined in the configuration backup files.

The disk group configuration backup and restore utilities do not save any data in the public region. This includes file system or other application data that is configured within VxVM objects.

A shared disk group in a cluster is restored as a private disk group. After the commit phase has completed, you can deport the private disk group and re-import it as a shared disk group.

SEE ALSO

vxconfigbackup (1M), vxconfigbackupd (1M)