Problem
After backing up the private region, the integrity of the backup can be verified with vxprint.This verifies that the configuration database contains valid data.
Solution
| 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 |
1. Use vxprint to parse the file that contains the configuration records (Figure 1). If vxconfigbackup was used to create the backup, this file will usually have an extension of "cfgrec." If vxprivutil was used, the filename will be whatever was specified when the backup was run.
Figure 1 - Using vxprint to verify the integrity of a configuration database backup
Syntax:
Note: The output of this command should correlate with the output of
vxprint -g <disk_group> -ht
# cat 1356551082.35.server1.cfgrec | vxprint -D - -ht
|
2. If vxconfigbackup was used, verify that the binconfig file that it creates has a size that is greater than zero. A size of zero indicates that the backup attempt failed.
More details about binconfig "zero size" issue can be found in the following article:
"WARNING V-5-2-3718 Unable to backup Binary disk group configuration for disk group" is reported by vxconfigbackup
https://www.veritas.com/docs/000007602
Figure 2 - An example of a binconfig file that has a size that is greater than zero
Example: In this case, the binconfig file has a size of "24649728." This suggests that the configuration database was actually backed up successfully. A length of "0" indicates that the backup failed. # ls -l |
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.