Verifying the integrity of a configuration database backup

  • Article ID:100028544
  • Modified Date:
  • Product(s):


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:


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


cat <file_containing_configuration_record> | vxprint -D - -ht

Note: The output of this command should correlate with the output of
vxprint -g <disk_group> -ht


Example, with typical output:

# cat 1356551082.35.server1.cfgrec | vxprint -D - -ht
Disk group: proddg

dg proddg       default      default  29000    1356551082.35.server1

dm proddg01     ams_wms0_59  auto     65536    1931008  -
dm proddg02     ams_wms0_60  auto     65536    1931008  -
dm proddg03     ams_wms0_61  auto     65536    1931008  -
dm proddg04     ams_wms0_62  auto     65536    1931008  -

v  prodvol      -            DISABLED ACTIVE   204800   SELECT    -        fsgen
pl prodvol-01   prodvol      DISABLED IOFAIL   204800   CONCAT    -        RW
sd proddg01-01  prodvol-01   proddg01 0        204800   0         ams_wms0_59 ENA


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.

# ls -l
total 48192
-rw-r--r--   1 root     root     24649728 Jan 11 03:07 1356551082.35.server1.binconfig
-rw-r--r--   1 root     root        8140 Jan 11 03:07 1356551082.35.server1.cfgrec
-rw-r--r--   1 root     root        2032 Jan 11 03:07 1356551082.35.server1.dginfo
-rw-r--r--   1 root     root        5094 Jan 11 03:07 1356551082.35.server1.diskinfo




Was this content helpful?

Get Support