Verifying the integrity of a configuration database backup
|Article:TECH201925|||||Created: 2013-01-22|||||Updated: 2013-08-05|||||Article URL http://www.symantec.com/docs/TECH201925|
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.
|This article is a part of a set on troubleshooting failed, or failing, disks. Click here to start at the beginning: http://www.symantec.com/docs/TECH200618|
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
Note: The output of this command should correlate with the output of
vxprint -g <disk_group> -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
Figure 2 - An example of a binconfig file that has a size that is greater than zero
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.
Article URL http://www.symantec.com/docs/TECH201925