.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. .ie n \{\ . ds C` "" . ds C' "" 'br\} .el\{\ . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "BACKUP_DBVERIFY 8" .TH BACKUP_DBVERIFY 8 2024-03-20 OpenAFS "AFS Command Reference" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH NAME backup_dbverify \- Checks the integrity of the Backup Database .SH SYNOPSIS .IX Header "SYNOPSIS" \&\fBbackup dbverify\fR [\fB\-detail\fR] [\fB\-localauth\fR] [\fB\-cell\fR\ <\fIcell\ name\fR>] [\fB\-help\fR] .PP \&\fBbackup db\fR [\fB\-d\fR] [\fB\-l\fR] [\fB\-c\fR\ <\fIcell\ name\fR>] [\fB\-h\fR] .SH DESCRIPTION .IX Header "DESCRIPTION" The \fBbackup dbverify\fR 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. .SH CAUTIONS .IX Header "CAUTIONS" 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 \fBbackup savedb\fR command repairs some types of corruption. .SH OPTIONS .IX Header "OPTIONS" .IP \fB\-detail\fR 4 .IX Item "-detail" 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. .IP \fB\-localauth\fR 4 .IX Item "-localauth" Constructs a server ticket using a key from the local \&\fI/etc/openafs/server/KeyFile\fR file. The \fBbackup\fR command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the \fB\-cell\fR argument. For more details, see \fBbackup\fR\|(8). .IP "\fB\-cell\fR <\fIcell name\fR>" 4 .IX Item "-cell " Names the cell in which to run the command. Do not combine this argument with the \fB\-localauth\fR flag. For more details, see \fBbackup\fR\|(8). .IP \fB\-help\fR 4 .IX Item "-help" Prints the online help for this command. All other valid options are ignored. .SH OUTPUT .IX Header "OUTPUT" The command displays one of the following two messages: .IP "Database OK" 4 .IX Item "Database OK" The database is undamaged and can be used. .IP "Database not OK" 4 .IX Item "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 \fIOpenAFS Administration Guide\fR chapter about performing backup operations. .PP The \fB\-detail\fR flag provides additional information: .IP \(bu 4 The number of \fIorphan blocks\fR found. These 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 \fBbackup savedb\fR command, and then restore it by using the \fBbackup restoredb\fR command. .IP \(bu 4 Any inconsistencies in the database, such as invalid hostnames for Tape Coordinator machines. .IP \(bu 4 The name of the database server machine on which the Backup Database was checked, designated as the \f(CW\*(C`Database checker\*(C'\fR. For a detailed trace of the verification operation, see the \fI/var/log/openafs/BackupLog\fR file on the indicated machine. You can use the \fBbos getlog\fR command to display it. .SH EXAMPLES .IX Header "EXAMPLES" The following command confirms that the Backup Database is undamaged: .PP .Vb 2 \& % backup dbverify \& Database OK .Ve .PP 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 \f(CW\*(C`db1.example.com\*(C'\fR checked its copy of the Database. .PP .Vb 4 \& % backup dbverify \-detail \& Database OK \& Orphan blocks 0 \& Database checker was db1.example.com .Ve .SH "PRIVILEGE REQUIRED" .IX Header "PRIVILEGE REQUIRED" The issuer must be listed in the \fI/etc/openafs/server/UserList\fR file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser \f(CW\*(C`root\*(C'\fR if the \fB\-localauth\fR flag is included. .SH "SEE ALSO" .IX Header "SEE ALSO" \&\fBBackupLog\fR\|(5), \&\fBbackup\fR\|(8), \&\fBbackup_restoredb\fR\|(8), \&\fBbackup_savedb\fR\|(8), \&\fBbos_getlog\fR\|(8) .SH COPYRIGHT .IX Header "COPYRIGHT" IBM Corporation 2000. All Rights Reserved. .PP 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.