.hy 0
.HP 8
\fBamadmin\fR \fIconfig\fR \fIcommand\fR [\fIoptions\fR]
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 8
\fBamcheck\fR [\fIoptions\fR] \fIconfig\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 10
\fBamcheckdb\fR \fIconfig\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 10
\fBamcleanup\fR \fIconfig\fR
+.br
+
+.ad
+.hy
+.ad l
+.hy 0
+.HP 8
+\fBamcrypt\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 7
\fBamdump\fR \fIconfig\fR
+.br
+
+.ad
+.hy
+.ad l
+.hy 0
+.HP 10
+\fBamaespipe\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 8
\fBamflush\fR [\-f] \fIconfig\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 10
\fBamgetconf\fR [\fIconfig\fR] \fIparameter\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 8
\fBamlabel\fR \fIconfig\fR \fIlabel\fR [\fIslot\fR\ \fIslot\fR]
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 11
\fBamoverview\fR \fIconfig\fR [\fIoptions\fR]
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 7
\fBamplot\fR [\fIoptions\fR] \fIamdump\-files\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 10
\fBamrecover\fR [\fIconfig\fR] [\fIoptions\fR]
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 9
\fBamreport\fR [\fIconfig\fR] [\fIoptions\fR]
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 10
\fBamrestore\fR [\fIoptions\fR] \fItapedevice\fR [\fIhostname\fR\ [\fIdiskname\fR]]
+.br
+
+.ad
+.hy
+.ad l
+.hy 0
+.HP 12
+\fBamfetchdump\fR [\fIoptions\fR] \fIconfig\fR [\fIhostname\fR\ [\fIdiskname\fR\ [\fIdate\fR\ [level]]]]
.ad
.hy
.ad l
.hy 0
.HP 9
\fBamrmtape\fR [\fIoptions\fR] \fIconfig\fR \fIlabel\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 9
\fBamstatus\fR \fIconfig\fR [\fIoptions\fR]
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 7
\fBamtape\fR \fIconfig\fR \fIcommand\fR [\fIoptions\fR]
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 6
\fBamtoc\fR [\fIoptions\fR] \fIlogfile\fR
+.br
+
.ad
.hy
.ad l
.hy 0
.HP 9
\fBamverify\fR \fIconfig\fR
+.br
+
.ad
.hy
.ad l
.SH "DESCRIPTION"
.PP
-\fBAMANDA\fR is the "Advanced Maryland Automatic Network Disk Archiver"\&. This manual page gives an overview of the \fBAMANDA\fR commands and configuration files for quick reference\&.
+\fBAmanda\fR is the "Advanced Maryland Automatic Network Disk Archiver"\&. This manual page gives an overview of the \fBAmanda\fR commands and configuration files for quick reference\&.
.PP
-Here are all the \fBAMANDA\fR commands\&. Each one has its own manual page\&. See them for all the gory details\&.
+Here are all the \fBAmanda\fR commands\&. Each one has its own manual page\&. See them for all the gory details\&.
.TP
\fBamdump\fR
-Take care of automatic \fBAMANDA\fR backups\&. This is normally executed by \fBcron\fR on a computer called the \fBtape server host\fR and requests backups of file systems located on \fBbackup\fR \fBclients\fR\&. \fBAmdump\fR backs up all disks in the \fBdisklist\fR file (discussed below) to tape or, if there is a problem, to a special \fBholding\fR \fBdisk\fR\&. After all backups are done, \fBamdump\fR sends mail reporting failures and successes\&.
+Take care of automatic \fBAmanda\fR backups\&. This is normally executed by \fBcron\fR on a computer called the \fBtape server host\fR and requests backups of file systems located on \fBbackup\fR \fBclients\fR\&. \fBAmdump\fR backs up all disks in the \fBdisklist\fR file (discussed below) to tape or, if there is a problem, to a special \fBholding\fR \fBdisk\fR\&. After all backups are done, \fBamdump\fR sends mail reporting failures and successes\&.
.TP
\fBamflush\fR
.TP
\fBamrecover\fR
-Provides an interactive interface to browse the \fBAMANDA\fR index files (backup image catalogues) and select which tapes to recover files from\&. It can also run \fBamrestore\fR and a restore program (e\&.g\&. \fBtar\fR) to actually recover the files\&.
+Provides an interactive interface to browse the \fBAmanda\fR index files (backup image catalogues) and select which tapes to recover files from\&. It can also run \fBamrestore\fR and a restore program (e\&.g\&. \fBtar\fR) to actually recover the files\&.
.TP
\fBamrestore\fR
-Read an \fBAMANDA\fR tape, searching for requested backups\&. \fBAmrestore\fR is suitable for everything from interactive restores of single files to a full restore of all partitions on a failed disk\&.
+Read an \fBAmanda\fR tape, searching for requested backups\&. \fBAmrestore\fR is suitable for everything from interactive restores of single files to a full restore of all partitions on a failed disk\&.
+
+.TP
+\fBamfetchdump\fR
+Performs \fBAmanda\fR tape restoration, similar to \fBamrestore\fR\&. Additional capabilities include "hands\-off" searching of multiple tapes, automatic retrieval of specific dump files based on dump logs, and assembly of tape\-spanning split dump files\&.
.TP
\fBamlabel\fR
-Write an \fBAMANDA\fR format label onto a tape\&. All \fBAMANDA\fR tapes must be labeled with \fBamlabel\fR\&. \fBAmdump\fR and \fBamflush\fR will not write to an unlabeled tape (see TAPE MANAGEMENT below)\&.
+Write an \fBAmanda\fR format label onto a tape\&. All \fBAmanda\fR tapes must be labeled with \fBamlabel\fR\&. \fBAmdump\fR and \fBamflush\fR will not write to an unlabeled tape (see TAPE MANAGEMENT below)\&.
.TP
\fBamcheck\fR
.TP
\fBamverify\fR
-Check \fBAMANDA\fR backup tapes for errors\&.
+Check \fBAmanda\fR backup tapes for errors\&.
.TP
\fBamrmtape\fR
-Delete a tape from the \fBAMANDA\fR databases\&.
+Delete a tape from the \fBAmanda\fR databases\&.
.TP
\fBamstatus\fR
.TP
\fBamplot\fR
-Generate utilization plots of \fBAMANDA\fR runs for performance tuning\&.
+Generate utilization plots of \fBAmanda\fR runs for performance tuning\&.
.TP
\fBamreport\fR
-Generate an \fBAMANDA\fR summary E\-mail report\&.
+Generate an \fBAmanda\fR summary E\-mail report\&.
.TP
\fBamtoc\fR
-Generate table of content files for \fBAMANDA\fR tapes\&.
+Generate table of content files for \fBAmanda\fR tapes\&.
.TP
\fBamcheckdb\fR
-Verify every tape \fBAMANDA\fR knows about is consistent in the database\&.
+Verify every tape \fBAmanda\fR knows about is consistent in the database\&.
.TP
\fBamgetconf\fR
-Look up parameters in the \fBAMANDA\fR configuration file\&.
+Look up parameters in the \fBAmanda\fR configuration file\&.
.TP
\fBamtapetype\fR
Generate a tapetype definition\&.
+.TP
+\fBamaespipe\fR
+Wrapper program from aespipe (data encryption utility)
+
+.TP
+\fBamcrypt\fR
+Reference encryption program for Amanda symmetric data encryption
+
.SH "CONFIGURATION"
.PP
-There are three user\-editable files that control the behavior of \fBAMANDA\fR\&.
+There are three user\-editable files that control the behavior of \fBAmanda\fR\&.
.PP
-The first is \fBamanda\&.conf\fR, the main configuration file\&. It contains parameters to customize \fBAMANDA\fR for the site\&. Refer to the \fBamanda\&.conf\fR(5), manpage for details on \fBAMANDA\fR configuration parameters\&.
+The first is \fBamanda\&.conf\fR, the main configuration file\&. It contains parameters to customize \fBAmanda\fR for the site\&. Refer to the \fBamanda\&.conf\fR(5), manpage for details on \fBAmanda\fR configuration parameters\&.
.PP
Second is the \fBdisklist\fR file, which lists hosts and disk partitions to back up\&.
Third is the \fBtapelist\fR file, which lists tapes that are currently active\&. These files are described in more detail in the following sections\&.
.PP
-All files are stored in individual configuration directories under \fI/usr/local/etc/amanda/\fR\&. A site will often have more than one configuration\&. For example, it might have a \fBnormal\fR configuration for everyday backups and an \fBarchive\fR configuration for infrequent full archival backups\&. The configuration files would be stored under directories \fI/usr/local/etc/amanda/normal/\fR and \fI/usr/local/etc/amanda/archive/\fR, respectively\&. Part of the job of an \fBAMANDA\fR administrator is to create, populate and maintain these directories\&.
+All files are stored in individual configuration directories under \fI/usr/local/etc/amanda/\fR\&. A site will often have more than one configuration\&. For example, it might have a \fBnormal\fR configuration for everyday backups and an \fBarchive\fR configuration for infrequent full archival backups\&. The configuration files would be stored under directories \fI/usr/local/etc/amanda/normal/\fR and \fI/usr/local/etc/amanda/archive/\fR, respectively\&. Part of the job of an \fBAmanda\fR administrator is to create, populate and maintain these directories\&.
.PP
-All log and database files generated by \fBAMANDA\fR go in corresponding directories somewhere\&. The exact location is controlled by entries in \fBamanda\&.conf\fR\&. A typical location would be under \fI/var/adm/amanda\fR\&. For the above example, the files might go in \fI/var/adm/amanda/normal/\fR and \fI/var/adm/amanda/archive/\fR\&.
+All log and database files generated by \fBAmanda\fR go in corresponding directories somewhere\&. The exact location is controlled by entries in \fBamanda\&.conf\fR\&. A typical location would be under \fI/var/adm/amanda\fR\&. For the above example, the files might go in \fI/var/adm/amanda/normal/\fR and \fI/var/adm/amanda/archive/\fR\&.
.PP
-As log files are no longer needed (no longer contain relevant information), \fBAMANDA\fR cycles them out in various ways, depending on the type of file\&.
+As log files are no longer needed (no longer contain relevant information), \fBAmanda\fR cycles them out in various ways, depending on the type of file\&.
.PP
Detailed information about \fBamdump\fR runs are stored in files named \fBamdump\&.\fR\fBNN\fR where \fBNN\fR is a sequence number, with 1 being the most recent file\&. \fBAmdump\fR rotates these files each run, keeping roughly the last \fBtapecycle\fR (see below) worth of them\&.
.PP
-The file used by \fBamreport\fR to generate the mail summary is named \fBlog\&.\fR\fBYYYYMMDD\&.NN\fR where \fBYYYYMMDD\fR is the datestamp of the start of the \fBamdump\fR run and \fBNN\fR is a sequence number started at 0\&. At the end of each \fBamdump\fR run, log files for runs whose tapes have been reused are renamed into a subdirectory of the main log directory (see the \fBlogdir\fR parameter below) named \fBoldlog\fR\&. It is up to the \fBAMANDA\fR administrator to remove them from this directory when desired\&.
+The file used by \fBamreport\fR to generate the mail summary is named \fBlog\&.\fR\fBYYYYMMDD\&.NN\fR where \fBYYYYMMDD\fR is the datestamp of the start of the \fBamdump\fR run and \fBNN\fR is a sequence number started at 0\&. At the end of each \fBamdump\fR run, log files for runs whose tapes have been reused are renamed into a subdirectory of the main log directory (see the \fBlogdir\fR parameter below) named \fBoldlog\fR\&. It is up to the \fBAmanda\fR administrator to remove them from this directory when desired\&.
.PP
Index (backup image catalogue) files older than the full dump matching the oldest backup image for a given client and disk are removed by \fBamdump\fR at the end of each run\&.
.SH "DISKLIST FILE"
.PP
-The \fBdisklist\fR file determines which disks will be backed up by \fBAMANDA\fR\&. The file usually contains one line per disk:
+The \fBdisklist\fR file determines which disks will be backed up by \fBAmanda\fR\&. The file usually contains one line per disk:
.nf
\fBhostname diskname\fR [\fBdiskdevice\fR] \fBdumptype\fR [\fBspindle\fR [\fBinterface\fR] ]
.TP
\fBhostname\fR
-The name of the host to be backed up\&. If \fBdiskdevice\fR refers to a PC share, this is the host \fBAMANDA\fR will run the Samba \fBsmbclient\fR program on to back up the share\&.
+The name of the host to be backed up\&. If \fBdiskdevice\fR refers to a PC share, this is the host \fBAmanda\fR will run the Samba \fBsmbclient\fR program on to back up the share\&.
.TP
\fBdiskname\fR
-The name of the disk (a label)\&. In most case, you set your \fBdiskname\fR to the \fBdiskdevice\fR and you don't set the \fBdiskdevice\&.\fR If you want multiple entries with the same \fBdiskdevice\fR, you must set a different \fBdiskname\fR for each entry\&. It's the \fBdiskname\fR that you use on the commandline for any \fBAMANDA\fR command\&. Look at the example/disklist file for example\&.
+The name of the disk (a label)\&. In most case, you set your \fBdiskname\fR to the \fBdiskdevice\fR and you don't set the \fBdiskdevice\&.\fR If you want multiple entries with the same \fBdiskdevice\fR, you must set a different \fBdiskname\fR for each entry\&. It's the \fBdiskname\fR that you use on the commandline for any \fBAmanda\fR command\&. Look at the example/disklist file for example\&.
.TP
\fBdiskdevice\fR
.TP
\fBspindle\fR
-Default: \fB\-1\fR\&. A number used to balance backup load on a host\&. \fBAMANDA\fR will not run multiple backups at the same time on the same spindle, unless the spindle number is \-1, which means there is no spindle restriction\&.
+Default: \fB\-1\fR\&. A number used to balance backup load on a host\&. \fBAmanda\fR will not run multiple backups at the same time on the same spindle, unless the spindle number is \-1, which means there is no spindle restriction\&.
.TP
\fBinterface\fR
.SH "TAPE MANAGEMENT"
.PP
-The \fBtapelist\fR file contains the list of tapes in active use\&. This file is maintained entirely by \fBAMANDA\fR and should not be created or edited during normal operation\&. It contains lines of the form:
+The \fBtapelist\fR file contains the list of tapes in active use\&. This file is maintained entirely by \fBAmanda\fR and should not be created or edited during normal operation\&. It contains lines of the form:
.PP
.PP
-Where \fBYYYYMMDD\fR is the date the tape was written, \fBlabel\fR is a label for the tape as written by \fBamlabel\fR and \fBflags\fR tell \fBAMANDA\fR whether the tape may be reused, etc (see the \fBreuse\fR options of \fBamadmin\fR)\&.
+Where \fBYYYYMMDD\fR is the date the tape was written, \fBlabel\fR is a label for the tape as written by \fBamlabel\fR and \fBflags\fR tell \fBAmanda\fR whether the tape may be reused, etc (see the \fBreuse\fR options of \fBamadmin\fR)\&.
.PP
\fBAmdump\fR and \fBamflush\fR will refuse to write to an unlabeled tape, or to a labeled tape that is considered active\&. There must be more tapes in active rotation (see the \fBtapecycle\fR option) than there are runs in the backup cycle (see the \fBdumpcycle\fR option) to prevent overwriting a backup image that would be needed to do a full recovery\&.
.SH "OUTPUT DRIVERS"
.PP
-The normal value for the \fBtapedev\fR parameter, or for what a tape changer returns, is a full path name to a non\-rewinding tape device, such as \fI/dev/nst0\fR or \fI/dev/rmt/0mn\fR or \fI/dev/nst0\&.1\fR or whatever conventions the operating system uses\&. \fBAMANDA\fR provides additional application level drivers that support non\-traditional tape\-simulations or features\&. To access a specific output driver, set \fBtapedev\fR (or configure your changer to return) a string of the form \fBdriver\fR:\fBdriver\-info\fR where \fBdriver\fR is one of the supported drivers and \fBdriver\-info\fR is optional additional information needed by the driver\&.
+The normal value for the \fBtapedev\fR parameter, or for what a tape changer returns, is a full path name to a non\-rewinding tape device, such as \fI/dev/nst0\fR or \fI/dev/rmt/0mn\fR or \fI/dev/nst0\&.1\fR or whatever conventions the operating system uses\&. \fBAmanda\fR provides additional application level drivers that support non\-traditional tape\-simulations or features\&. To access a specific output driver, set \fBtapedev\fR (or configure your changer to return) a string of the form \fBdriver\fR:\fBdriver\-info\fR where \fBdriver\fR is one of the supported drivers and \fBdriver\-info\fR is optional additional information needed by the driver\&.
.PP
The supported drivers are:
.TP
\fBnull\fR
-This driver throws away anything written to it and returns EOF for any reads except a special case is made for reading a label, in which case a "fake" value is returned that \fBAMANDA\fR checks for and allows through regardless of what you have set in \fBlabelstr\fR\&. The \fBdriver\-info\fR field is not used and may be left blank:
+This driver throws away anything written to it and returns EOF for any reads except a special case is made for reading a label, in which case a "fake" value is returned that \fBAmanda\fR checks for and allows through regardless of what you have set in \fBlabelstr\fR\&. The \fBdriver\-info\fR field is not used and may be left blank:
.nf
One way to use this driver with a real device such as a CD\-writer is to create a directory for the \fBfile\fR device and one or more other directories for the actual data\&. Create a symlink named \fBdata\fR in the \fBfile\fR directory to one of the data directories\&. Set the \fBtapetype\fR length to whatever the medium will hold\&.
-When \fBAMANDA\fR fills the \fBfile\fR device, remove the symlink and (optionally) create a new symlink to another data area\&. Use a CD writer software package to burn the image from the first data area\&.
+When \fBAmanda\fR fills the \fBfile\fR device, remove the symlink and (optionally) create a new symlink to another data area\&. Use a CD writer software package to burn the image from the first data area\&.
To read the CD, mount it and create the \fBdata\fR symlink in the \fBfile\fR device directory\&.
.SH "AUTHORIZATION"
.PP
-\fBAMANDA\fR processes on the tape server host run as the \fBdumpuser\fR user listed in \fBamanda\&.conf\fR\&. When they connect to a backup client, they do so with an \fBAMANDA\fR\-specific protocol\&. They do not, for instance, use \fBrsh\fR or \fBssh\fR directly\&.
+\fBAmanda\fR processes on the tape server host run as the \fBdumpuser\fR user listed in \fBamanda\&.conf\fR\&. When they connect to a backup client, they do so with an \fBAmanda\fR\-specific protocol\&. They do not, for instance, use \fBrsh\fR or \fBssh\fR directly\&.
.PP
On the client side, the \fBamandad\fR daemon validates the connection using one of several methods, depending on how it was compiled and on options it is passed:
.TP
\&.rhosts
-Even though \fBAMANDA\fR does not use \fBrsh\fR, it can use \&.rhosts\-style authentication and a \&.rhosts file\&.
+Even though \fBAmanda\fR does not use \fBrsh\fR, it can use \&.rhosts\-style authentication and a \&.rhosts file\&.
.TP
\&.amandahosts
-This is essentially the same as \&.rhosts authentication except a different file, with almost the same format, is used\&. This is the default mechanism built into \fBAMANDA\fR\&.
+This is essentially the same as \&.rhosts authentication except a different file, with almost the same format, is used\&. This is the default mechanism built into \fBAmanda\fR\&.
The format of the \fI\&.amandahosts\fR file is:
.TP
Kerberos
-\fBAMANDA\fR may use the Kerberos authentication system\&. Further information is in the \fBdocs/KERBEROS\fR file that comes with an \fBAMANDA\fR distribution\&.
+\fBAmanda\fR may use the Kerberos authentication system\&. Further information is in the \fBdocs/KERBEROS\fR file that comes with an \fBAmanda\fR distribution\&.
-For Samba access, \fBAMANDA\fR needs a file on the Samba server (which may or may not also be the tape server) named \fI/etc/amandapass\fR with share names, (clear text) passwords and (optional) domain names, in that order, one per line, whitespace separated\&. By default, the user used to connect to the PC is the same for all PC's and is compiled into \fBAMANDA\fR\&. It may be changed on a host by host basis by listing it first in the password field followed by a percent sign and then the password\&. For instance:
+For Samba access, \fBAmanda\fR needs a file on the Samba server (which may or may not also be the tape server) named \fI/etc/amandapass\fR with share names, (clear text) passwords and (optional) domain names, in that order, one per line, whitespace separated\&. By default, the user used to connect to the PC is the same for all PC's and is compiled into \fBAmanda\fR\&. It may be changed on a host by host basis by listing it first in the password field followed by a percent sign and then the password\&. For instance:
.nf
//some\-pc/home normalpw
//another\-pc/disk otheruser%otherpw.fi
-With clear text passwords, this file should obviously be tightly protected\&. It only needs to be readable by the \fBAMANDA\fR\-user on the Samba server\&.
+With clear text passwords, this file should obviously be tightly protected\&. It only needs to be readable by the \fBAmanda\fR\-user on the Samba server\&.
-You can find further information in the \fBdocs/SAMBA\fR file that comes with an \fBAMANDA\fR distribution\&.
+You can find further information in the \fBdocs/SAMBA\fR file that comes with an \fBAmanda\fR distribution\&.
.SH "HOST & DISK EXPRESSION"
.PP
The matcher matches by word, each word is a glob expression, words are separated by the separator '\&.' for host and '/' for disk\&. You can anchor the expression at left with a '^'\&. You can anchor the expression at right with a '$'\&. The matcher is case insensitive for host but is case sensitive for disk\&. A match succeeds if all words in your expression match contiguous words in the host or disk\&.
-\&. word separator for a host/ word separator for a disk^ anchor at left$ anchor at right? match exactly one character except the separator* match zero or more characters except the separator**match zero or more characters including the separator
+
+.nf
+
+\&. word separator for a host
+/ word separator for a disk
+^ anchor at left
+$ anchor at right
+? match exactly one character except the separator
+* match zero or more characters except the separator
+** match zero or more characters including the separator
+
+.fi
+
.PP
Some examples:
-EXPRESSIONWILL MATCH WILL NOT MATCHhosta hosta hostb hoSTA\&.dOMAIna\&.ORG foo\&.hosta\&.org host host hostahost? hosta host hostb ho*na hoina ho\&.aina\&.orgho**na hoina ho\&.aina\&.org ^hosta hosta foo\&.hosta\&.orgsda* /dev/sda1 /dev/sda12 /opt/ opt (disk) opt (host)\&.opt\&. opt (host) opt (disk)/ / any other disk/usr /usr /usr/opt /usr$ /usr /usr/opt
-.PP
+.nf
+
+EXPRESSION WILL MATCH WILL NOT MATCH
+hosta hosta hostb
+ hoSTA\&.dOMAIna\&.ORG
+ foo\&.hosta\&.org
+host host hosta
+host? hosta host
+ hostb
+ho*na hoina ho\&.aina\&.org
+ho**na hoina
+ ho\&.aina\&.org
+^hosta hosta foo\&.hosta\&.org
+sda* /dev/sda1
+ /dev/sda12
+/opt/ opt (disk) opt (host)
+\&.opt\&. opt (host) opt (disk)
+/ / any other disk
+/usr /usr
+ /usr/opt
+/usr$ /usr /usr/opt
+
+.fi
.SH "DATESTAMP EXPRESSION"
James da Silva, <jds@amanda\&.org> : Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAMANDA\fR\-documentation: XML\-conversion, major update
+Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion, major update
.SH "SEE ALSO"
.PP
- \fBamadmin\fR(8), \fBamanda\&.conf\fR(5), \fBamcheck\fR(8), \fBamcheckdb\fR(8), \fBamcleanup\fR(8), \fBamdd\fR(8), \fBamdump\fR(8), \fBamflush\fR(8), \fBamgetconf\fR(8), \fBamlabel\fR(8), \fBammt\fR(8), \fBamoverview\fR(8), \fBamplot\fR(8), \fBamrecover\fR(8), \fBamreport\fR(8), \fBamrestore\fR(8), \fBamrmtape\fR(8), \fBamstatus\fR(8), \fBamtape\fR(8), \fBamtapetype\fR(8), \fBamtoc\fR(8), \fBamverify\fR(8), \fBamverifyrun\fR(8)
+ \fBamadmin\fR(8), \fBamanda\&.conf\fR(5), \fBamcheck\fR(8), \fBamcheckdb\fR(8), \fBamcleanup\fR(8), \fBamdd\fR(8), \fBamdump\fR(8), \fBamfetchdump\fR(8) \fBamflush\fR(8), \fBamgetconf\fR(8), \fBamlabel\fR(8), \fBammt\fR(8), \fBamoverview\fR(8), \fBamplot\fR(8), \fBamrecover\fR(8), \fBamreport\fR(8), \fBamrestore\fR(8), \fBamrmtape\fR(8), \fBamstatus\fR(8), \fBamtape\fR(8), \fBamtapetype\fR(8), \fBamtoc\fR(8), \fBamverify\fR(8), \fBamverifyrun\fR(8)
projects / debian / amanda / blobdiff