Command Reference Manual


[Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

backup dbverify

Purpose

Checks the integrity of the Backup Database

Synopsis

backup dbverify  [-detail]  [-localauth]  [-cell <cell name>]  [-help]
  
backup db  [-d]  [-l]  [-c <cell name>]  [-h]

Description

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.

Cautions

While this command runs, no other backup operation can access the Backup Database; the other commands appear to hang 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.

Options

-detail
Displays additional information about the Backup Database.

-localauth
Constructs a server ticket using a key from the local /usr/afs/etc/KeyFile 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 the introductory backup reference page.

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

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

Output

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 AFS System Administrator's Guide chapter about performing backup operations.

The -detail flag provides additional information about the Backup Database. The output reports whether there are any orphan blocks, which are ranges of memory that the Backup Server preallocated in the database but cannot use. Orphan blocks do not interfere with database access, but do waste disk space. To free the unusable space, dump the database to tape by using the backup savedb command, and then restore it by using the backup restoredb command.

The -detail flag also reports any inconsistencies in the database, such as invalid hostnames for Tape Coordinator machines. The database checker field in the output names the database server machine on which the Backup Database was checked.

If the Database is damaged, the /usr/afs/logs/BackupLog file on the Backup Server machine records more details.

Examples

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 db1.abc.com checked its copy of the Database.

% backup dbverify -detail
Database OK
Orphan blocks 0
Database checker was db1.abc.com

Privilege Required

The issuer must be listed in the /usr/afs/etc/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser root if the -localauth flag is included.

Related Information

backup

backup restoredb

backup savedb


[Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]



© IBM Corporation 1999. All Rights Reserved