Description
| This article is a part of a set on troubleshooting failed, or failing, disks. Click here to start at the beginning: https://www.veritas.com/docs/000080622 |
Table of Contents
Introduction
1. Verify the integrity of a configuration database backup
2. Back up the existing configuration
3. Deport the disk group to be restored
4. Restore the configuration
5. Commit the restoration
Introduction
(Back to top)
Use vxconfigrestore to restore a private region backup that was created with vxconfigbackup. A restore may be necessary if the private region of a diskgroup has been corrupted or lost. Vxconfigrestore does not restore data to the actual volumes.
1. Verify the integrity of a configuration database backup
(Back to top)
Before running vxconfigrestore, verify the integrity of the configuration database backup to ensure that the data being restored is correct. The integrity of the backup can be verified with vxprint.
Note: See this article for details on verifying the integrity of a configuration database backup
"Verifying the integrity of a configuration database backup"
https://www.veritas.com/docs/000087566
2. Back up the existing configuration
(Back to top)
Before running vxconfigrestore, complete these two steps to back up the existing configuration.
- Make a copy of the directory that contains the existing vxconfigbackup files. By default, the vxconfigbackup files are stored under /etc/vx/cbr/bk. The location may be different if a manual backup was performed using the "-l" argument.
- Use vxconfigbackup to create a new backup of the configuration.
Note: See this article for details on using vxconfigbackup:
"Using vxconfigbackup and vxprivutil to back up up the disk group configuration of the Veritas private region"
https://www.veritas.com/docs/000087431
3. Deport the disk group to be restored
(Back to top)
A disk group must be deported before running a restore with vxconfigrestore is possible. Attempting to run vxconfigrestore to an imported disk group will trigger the error "ERROR V-5-2-3705 Diskgroup datadg is currently online imported."
Figure 1 - Using vxdg to deport a disk group
|
Syntax: vxdg deport <disk_group> Example: # vxdg deport proddg
|
4. Restore the configuration
(Back to top)
By default, Volume Manager automatically creates periodic backups of the private region to /etc/vx/cbr/bk. If a manual backup was created in an alternate location, specify this location when running vxconfigrestore.
Figure 2 - Using vxconfigrestore to restore the private region to a disk
|
Syntax: # vxconfigrestore -p -l /directory <disk_group> Example, with typical output: # vxconfigrestore -p -l /tmp/vxconfigbackup proddg
Note: The configuration has been restored, but the restoration has not yet been committed. Vxprint can be used to review the restored configuration using before committing it. |
5. Commit the restoration
(Back to top)
If the "-p" argument was used while running vxconfigrestore, the disk configuration is still in a "precommit" state. In this state, the volumes and configuration are read-only. The precommit state makes it possible to review the configuration before commiting the restoration. To abort the restoration, use the "-d" argument.
Figure 3 - Using vxconfigrestore to commit a restoration
Syntax: # vxconfigrestore -l /directory -c <disk_group> Example, with typical output: # vxconfigrestore -l /tmp/vxconfigbackup -c proddg |
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.