backup_dbverify - Checks the integrity of the Backup Database


backup dbverify [-detail] [-localauth] [-butc_noauth] [-cell <cell name>] [-config <configuration file>] [-help]


The backup dbverify command checks the integrity of the Backup Database. The command's output indicates whether the Backup Database is damaged (data is corrupted) or not. If the Backup Database is undamaged, it is safe to continue using it. If it is corrupted, discontinue any backup operations until it is repaired.


While this command runs, no other backup operation can access the Backup Database; the other commands do not run until this command completes. Avoid issuing this command when other backup operations are likely to run. The backup savedb command repairs some types of corruption.



Reports the number of orphaned blocks found, any inconsistencies, and the name of the server machine running the Backup Server that is checking its copy of the database.


Constructs a server ticket using a key from the local /etc/yfs/server/KeyFileExt file. The backup command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more details, see backup(8).


Assigns the unprivileged identity anonymous to the issuer for all connections to Tape Controllers butc. This option should only be used when the Tape Controller is incapable of authenticated connections.

-cell <cell name>

Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8).

-config <configuration file>

Sets the location of the configuration file to be used. The default file is /etc/yfs/yfs-client.conf.


Prints the online help for this command. All other valid options are ignored.


The command displays one of the following two messages:

Database OK

The database is undamaged and can be used.

Database not OK

The database is damaged. You can use the backup savedb command to repair many kinds of corruption as it creates a backup copy. For more detailed instructions, see the OpenAFS Administration Guide chapter about performing backup operations.

The -detail flag provides additional information:


The following command confirms that the Backup Database is undamaged:

   % backup dbverify
   Database OK

The following command confirms that the Backup Database is undamaged and that it has no orphan blocks or invalid Tape Coordinator entries. The Backup Server running on the machine checked its copy of the Database.

   % backup dbverify -detail
   Database OK
   Orphan blocks 0
   Database checker was


The issuer must be listed in the /etc/yfs/server/UserListExt file on every machine where the Backup Server is running, or must be logged onto a server with an account capable of reading the /etc/yfs/server/KeyFileExt file if the -localauth flag is included. =head1 SEE ALSO

BackupLog(5), backup(8), backup_restoredb(8), backup_savedb(8), bos_getlog(8)


IBM Corporation 2000. All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.


"AFS" is a registered mark of International Business Machines Corporation, used under license. (USPTO Registration 1598389)

"OpenAFS" is a registered mark of International Business Machines Corporation. (USPTO Registration 4577045)

The "AuriStor" name, log 'S' brand mark, and icon are registered marks of AuriStor, Inc. (USPTO Registrations 4849419, 4849421, and 4928460) (EUIPO Registration 015539653).

"Your File System" is a registered mark of AuriStor, Inc. (USPTO Registrations 4801402 and 4849418).

"YFS" and "AuriStor File System" are trademarks of AuriStor, Inc.