-2006-03-28 Jean-Louis Martineau <martineau@zmanda.com>
+2006-05-28 Jean-Louis Martineau <martineau@zmanda.com>
+ * amandad-src/amandad.c (service_new): Apply the correct patch.
+
+2006-05-28 Jean-Louis Martineau <martineau@zmanda.com>
+ * Amanda 2.5.0p2 released.
+ * configure.in: AM_INIT_AUTOMAKE(amanda, 2.5.0p2).
+ * NEWS: Changes in release 2.5.0p2.
+
+2006-05-07 Jean-Louis Martineau <martineau@zmanda.com>
+ * amandad-src/amandad.c (service_new): Make sure that the 3 data[] fd
+ are not in the range DATA_FD_OFFSET to
+ DATA_FD_OFFSET+DATA_FD_COUNT-1.
+
+2006-05-04 Jean-Louis Martineau <martineau@zmanda.com>
+ * server-src/taper.c: Write the slot number in the
+ 'taper: wrote label' line.
+ * server-src/amverifyrun.sh.in: Parse that line.
+
+2006-05-02 Jean-Louis Martineau <martineau@zmanda.com>
+ * amstatus.pl.in: Limit characters for hostname in setup_estimate line.
+
+2006-04-28 Jean-Louis Martineau <martineau@zmanda.com>
+ * Amanda 2.5.0p1 released.
+ * configure.in: AM_INIT_AUTOMAKE(amanda, 2.5.0p1).
+ * NEWS: Changes in release 2.5.0p1.
+
+2006-04-24 Ian Turner <ian@zmanda.com>
+ * server-src/changer.c: Don't crash if we go to taperscan "Plan B".
+
+2006-04-24 Jean-Louis Martineau <martineau@zmanda.com>
+ * server-src/planner.c: Fix divide by zero if runtapes==0.
+
+2006-04-23 Jean-Louis Martineau <martineau@zmanda.com>
+ * server-src/driver.c (handle_chunker_result): make sure that
+ est_size > act-size.
+
+2006-04-23 Jean-Louis Martineau <martineau@zmanda.com>
+ * server-src/chunker.c: Read the START command to set the datestamp.
+ * server-src/driver.c: Send a START command to the chunker.
+ * server-src/driverio.c (chunker_cmd): Add the START command.
+ * server-src/server_util.c (cmdstr): Add the START command.
+ * server-src/server_util.h (cmd_t): Add the START command.
+
+2006-04-14 Jean-Louis Martineau <martineau@zmanda.com>
+ * server-src/amtape.c: Add update command.
+
+2006-04-11 Jean-Louis Martineau <martineau@zmanda.com>
+ * common-src/krb4-security.c: Increase timeout to 60 seconds.
+ * common-src/rsh-security.c: Increase timeout to 60 seconds.
+ * common-src/ssh-security.c: Increase timeout to 60 seconds.
+
+2006-04-07 Jean-Louis Martineau <martineau@zmanda.com>
+ * restore-src/amrestore.c: reset count_error to 0 on a restore.
+
+2006-04-05 Jean-Louis Martineau <martineau@zmanda.com>
+ * server-src/driver.c: Change expression to remove overflow.
+
+2006-03-29 Jean-Louis Martineau <martineau@zmanda.com>
+ * client-src/calcsize.c: Don't use declaration after instruction,
+ older compiler don't accept it.
+
+2006-03-23 Jean-Louis Martineau <martineau@zmanda.com>
* Amanda 2.5.0 released.
* configure.in: AM_INIT_AUTOMAKE(amanda, 2.5.0).
* NEWS: Update for 2.5.0
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+Changes in release 2.5.0p2
+
+* Fix major bug in amandad.
+* amverifyeun works.
+* amstatus works with ':' in diskname.
+
+Changes in release 2.5.0p1
+
+* Add the 'amtape update' command.
+* Many small bug fix.
+
Changes in release 2.5.0
* Communication security/authentication: Kerberos 4/5, OpenSSH
-# generated automatically by aclocal 1.9.5 -*- Autoconf -*-
+# generated automatically by aclocal 1.9.6 -*- Autoconf -*-
# Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
# 2005 Free Software Foundation, Inc.
# Call AM_AUTOMAKE_VERSION so it can be traced.
# This function is AC_REQUIREd by AC_INIT_AUTOMAKE.
AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION],
- [AM_AUTOMAKE_VERSION([1.9.5])])
+ [AM_AUTOMAKE_VERSION([1.9.6])])
# AM_AUX_DIR_EXPAND -*- Autoconf -*-
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
# Makefile for Amanda tape changer programs.
-SOURCES = $(chg_scsi_SOURCES) $(chg_scsi_chio_SOURCES)
-
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-SOURCES = $(libamclient_la_SOURCES) amandad.c calcsize.c $(getfsent_SOURCES) killpgrp.c noop.c rundump.c runtar.c selfcheck.c $(sendbackup_SOURCES) sendsize.c versionsuffix.c
-
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
*/
/*
- * $Id: amandad.c,v 1.62 2006/03/09 16:51:41 martinea Exp $
+ * $Id: amandad.c,v 1.62.2.2 2006/05/08 11:50:16 martinea Exp $
*
* handle client-host side of Amanda network communications, including
* security checks, execution of the proper service, and acking the
int data[DATA_FD_COUNT + 2][2], i;
struct active_service *as;
pid_t pid;
+ int newfd;
assert(security_handle != NULL);
assert(cmd != NULL);
* The rest start at the offset defined in amandad.h, and continue
* through the internal defined.
*/
+ for (i = 0; i < DATA_FD_COUNT; i++)
+ aclose(data[i + 2][0]);
+
+ /*
+ * Make sure they are not open in the range DATA_FD_OFFSET to
+ * DATA_FD_OFFSET + DATA_FD_COUNT - 1
+ */
+ for (i = 0; i < DATA_FD_COUNT; i++) {
+ while(data[i + 2][1] >= DATA_FD_OFFSET &&
+ data[i + 2][1] <= DATA_FD_OFFSET + DATA_FD_COUNT - 1) {
+ newfd = dup(data[i + 2][1]);
+ if(newfd == -1)
+ error("Can't dup out off DATA_FD range");
+ data[i + 2][1] = newfd;
+ }
+ }
+ for (i = 0; i < DATA_FD_COUNT; i++)
+ close(DATA_FD_OFFSET + i);
+
for (i = 0; i < DATA_FD_COUNT; i++) {
if (dup2(data[i + 2][1], i + DATA_FD_OFFSET) < 0) {
error("dup %d to %d failed: %s\n", data[i + 2][1],
i + DATA_FD_OFFSET, strerror(errno));
}
- aclose(data[i + 2][0]);
aclose(data[i + 2][1]);
}
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: calcsize.c,v 1.36 2006/03/09 16:51:41 martinea Exp $
+ * $Id: calcsize.c,v 1.37 2006/03/29 15:45:08 martinea Exp $
*
* traverse directory tree to get backup size estimates
*/
int l;
int parent_len;
int has_exclude = !is_empty_sl(exclude_sl) && use_gtar_excl;
+ char *aparent;
if(parent_dir == NULL || include == NULL) return;
- char *aparent = vstralloc(parent_dir, "/", include, NULL);
+ aparent = vstralloc(parent_dir, "/", include, NULL);
if(stat(parent_dir, &finfo) != -1)
parent_dev = finfo.st_dev;
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
# Makefile for Amanda library.
-SOURCES = $(libamanda_la_SOURCES) $(amfeatures_SOURCES) $(bsdsecurity_SOURCES) $(file_SOURCES) $(genversion_SOURCES) $(statfs_SOURCES) $(token_SOURCES)
-
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
*/
/*
- * $Id: krb4-security.c,v 1.9 2006/02/21 04:13:55 ktill Exp $
+ * $Id: krb4-security.c,v 1.9.2.1 2006/04/11 11:11:16 martinea Exp $
*
* krb4-security.c - helper functions for kerberos v4 security.
*/
* and useconds by one. Reencrypt, and present to the other side.
* Timeout in 10 seconds.
*/
- if (net_read(fd, &enc, sizeof(enc), 10) < 0) {
+ if (net_read(fd, &enc, sizeof(enc), 60) < 0) {
security_stream_seterror(&ks->secstr,
"krb4 stream handshake read error: %s", strerror(errno));
return (-1);
* If they incremented it properly, then succeed.
* Timeout in 10 seconds.
*/
- if (net_read(fd, &enc, sizeof(enc), 10) < 0) {
+ if (net_read(fd, &enc, sizeof(enc), 60) < 0) {
security_stream_seterror(&ks->secstr,
"krb4 stream handshake read error: %s", strerror(errno));
return (-1);
*/
/*
- * $Id: rsh-security.c,v 1.18 2005/12/01 01:14:39 martinea Exp $
+ * $Id: rsh-security.c,v 1.18.2.1 2006/04/11 11:11:16 martinea Exp $
*
* rsh-security.c - security and transport over rsh or a rsh-like command.
*
rshprintf(("rsh: conn_read_callback\n"));
/* Read the data off the wire. If we get errors, shut down. */
- rval = recv_token(rc, 5);
+ rval = recv_token(rc, 60);
rshprintf(("rsh: conn_read_callback: recv_token returned %d\n", rval));
if (rval <= 0) {
rc->pktlen = 0;
*/
/*
- * $Id: ssh-security.c,v 1.8 2006/02/17 00:58:51 ktill Exp $
+ * $Id: ssh-security.c,v 1.8.2.1 2006/04/11 11:11:16 martinea Exp $
*
* ssh-security.c - security and transport over ssh or a ssh-like command.
*
sshprintf(("%s: ssh: conn_read_callback\n",debug_prefix_time(NULL)));
/* Read the data off the wire. If we get errors, shut down. */
- rval = recv_token(rc, 5);
+ rval = recv_token(rc, 60);
sshprintf(("%s: ssh: conn_read_callback: recv_token returned %d\n", debug_prefix_time(NULL), rval));
if (rval <= 0) {
rc->pktlen = 0;
/* version.c - generated by genversion.c - DO NOT EDIT! */
const char * const version_info[] = {
- "build: VERSION=\"Amanda-2.5.0\"\n",
- " BUILT_DATE=\"Thu Mar 23 20:20:38 EST 2006\"\n",
- " BUILT_MACH=\"Linux minifee.iro.umontreal.ca 2.6.15-1.1833_FC4 #1 Wed Mar 1 23:41:37 EST 2006 i686 i686 i386 GNU/Linux\"\n",
+ "build: VERSION=\"Amanda-2.5.0p2\"\n",
+ " BUILT_DATE=\"Mon May 8 07:54:11 EDT 2006\"\n",
+ " BUILT_MACH=\"Linux modemcable099.122-200-24.mc.videotron.ca 2.6.16-1.2111_FC5 #1 SMP Thu May 4 21:16:04 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux\"\n",
" CC=\"gcc\"\n",
- " CONFIGURE_COMMAND=\"'./configure' '--prefix=/u/martinea/linux' '--with-configdir=/u/martinea/etc/amanda' '--with-gnutar-listdir=/var/gnutar-lists' '--with-bsd-security' '--with-user=amanda' '--with-group=amandag' '--mandir=/u/martinea/man'\"\n",
- "paths: bindir=\"/u/martinea/linux/bin\"\n",
- " sbindir=\"/u/martinea/linux/sbin\"\n",
- " libexecdir=\"/u/martinea/linux/libexec\"\n",
- " mandir=\"/u/martinea/man\" AMANDA_TMPDIR=\"/tmp/amanda\"\n",
+ " CONFIGURE_COMMAND=\"'./configure' '--prefix=/home/martinea/linux' '--with-configdir=/home/martinea/etc/amanda' '--with-gnutar-listdir=/var/gnutar-lists' '--with-bsd-security' '--with-ssh-security' '--with-rsh-security' '--with-krb4-security' '--without-krb5-security' '--with-user=martinea' '--with-group=martinea' '--mandir=/home/martinea/man'\"\n",
+ "paths: bindir=\"/home/martinea/linux/bin\"\n",
+ " sbindir=\"/home/martinea/linux/sbin\"\n",
+ " libexecdir=\"/home/martinea/linux/libexec\"\n",
+ " mandir=\"/home/martinea/man\" AMANDA_TMPDIR=\"/tmp/amanda\"\n",
" AMANDA_DBGDIR=\"/tmp/amanda\"\n",
- " CONFIG_DIR=\"/u/martinea/etc/amanda\" DEV_PREFIX=\"/dev/\"\n",
+ " CONFIG_DIR=\"/home/martinea/etc/amanda\" DEV_PREFIX=\"/dev/\"\n",
" RDEV_PREFIX=\"/dev/\" DUMP=\"/sbin/dump\"\n",
" RESTORE=\"/sbin/restore\" VDUMP=UNDEF VRESTORE=UNDEF\n",
" XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF\n",
" SAMBA_CLIENT=\"/usr/bin/smbclient\" GNUTAR=\"/bin/gtar\"\n",
- " COMPRESS_PATH=\"/bin/gzip\" UNCOMPRESS_PATH=\"/bin/gzip\"\n",
- " LPRCMD=\"/usr/bin/lpr\" MAILER=\"/usr/bin/Mail\"\n",
- " listed_incr_dir=\"/var/gnutar-lists\"\n",
- "defs: DEFAULT_SERVER=\"minifee.iro.umontreal.ca\"\n",
+ " COMPRESS_PATH=\"/usr/bin/gzip\"\n",
+ " UNCOMPRESS_PATH=\"/usr/bin/gzip\" LPRCMD=\"/usr/bin/lpr\"\n",
+ " MAILER=\"/usr/bin/Mail\" listed_incr_dir=\"/var/gnutar-lists\"\n",
+ "defs: DEFAULT_SERVER=\"modemcable099.122-200-24.mc.videotron.ca\"\n",
" DEFAULT_CONFIG=\"DailySet1\"\n",
- " DEFAULT_TAPE_SERVER=\"minifee.iro.umontreal.ca\"\n",
+ " DEFAULT_TAPE_SERVER=\"modemcable099.122-200-24.mc.videotron.ca\"\n",
" DEFAULT_TAPE_DEVICE=\"null:\" HAVE_MMAP HAVE_SYSVSHM\n",
" LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE\n",
" AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS\n",
- " CLIENT_LOGIN=\"amanda\" FORCE_USERID HAVE_GZIP\n",
+ " CLIENT_LOGIN=\"martinea\" FORCE_USERID HAVE_GZIP\n",
" COMPRESS_SUFFIX=\".gz\" COMPRESS_FAST_OPT=\"--fast\"\n",
" COMPRESS_BEST_OPT=\"--best\" UNCOMPRESS_OPT=\"-dc\"\n",
0
const int VERSION_MAJOR = 2;
const int VERSION_MINOR = 5;
const int VERSION_PATCH = 0;
-const char *const VERSION_COMMENT = "";
+const char *const VERSION_COMMENT = "p2";
const char *
versionsuffix()
{
#ifdef USE_VERSION_SUFFIXES
- return "-2.5.0";
+ return "-2.5.0p2";
#else
return "";
#endif
const char *
version()
{
- return "2.5.0";
+ return "2.5.0p2";
}
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
# Define the identity of the package.
PACKAGE=amanda
- VERSION=2.5.0
+ VERSION=2.5.0p2
cat >>confdefs.h <<_ACEOF
[Saves the original ./configure command line arguments])
AC_SUBST(CONFIGURE_COMMAND)
-AM_INIT_AUTOMAKE(amanda, 2.5.0)
+AM_INIT_AUTOMAKE(amanda, 2.5.0p2)
AM_CONFIG_HEADER(config/config.h)
AC_PREREQ(2.57) dnl Minimum Autoconf version required.
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
cleanslot 7 # slot containing the cleaning disk
cleansleep 300 # How long to wait before the cleaning tape finishes (default: 5 min)
cleanme 45 # number of days before messages popup to clean tape drive
-cleanfile /u/martinea/etc/amanda/changer/times_cleaned
-lastfile /u/martinea/etc/amanda/changer/last_cleaned
+cleanfile /home/martinea/etc/amanda/changer/times_cleaned
+lastfile /home/martinea/etc/amanda/changer/last_cleaned
# Names a status file where the current 'changer' state is stored.
-currentslot /u/martinea/etc/amanda/changer/currentslot
+currentslot /home/martinea/etc/amanda/changer/currentslot
# Where to log changer debugging info
logfile /tmp/amanda/changer.debug
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
.IP "\\$1" \\$2
..
.TH "AMADMIN" 8 "" "" ""
-.SH NAME
-amadmin \- administrative interface to control Amanda backups
+.SH "NAME"
+amadmin - administrative interface to control Amanda backups
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 8
-\fBamadmin\fR \fIconfig\fR \fIcommand\fR [\fIcommand\fR\ \fIoptions\fR]
-.ad
-.hy
-
+\fBamadmin\fR \fIconfig\fR \fIcommand\fR [\fIcommand\fRÂ \fIoptions\fR]
.SH "DESCRIPTION"
-
.PP
-\fBAmadmin\fR performs various administrative tasks on the \fBconfig\fR \fBAmanda\fR configuration\&.
-
+\fBAmadmin\fR
+performs various administrative tasks on the
+\fBconfig\fR\fBAmanda\fR
+configuration.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "COMMANDS"
-
.PP
-Commands that take a \fBhostname\fR [ \fBdisks\fR ] parameter pair operate on all disks in the \fBdisklist\fR for that \fBhostname\fR if no disks are specified\&. Where \fBhostname\fR is also marked as being optional, the command operates on all hosts and disks in the \fBdisklist\fR\&. Both \fBhostname\fR and \fBdisks\fR are special expressions, see the "HOST & DISK EXPRESSION" section of \fBamanda\fR(8) for a description\&.
-
+Commands that take a
+\fBhostname\fR
+[
+\fBdisks\fR
+] parameter pair operate on all disks in the
+\fBdisklist\fR
+for that
+\fBhostname\fR
+if no disks are specified. Where
+\fBhostname\fR
+is also marked as being optional, the command operates on all hosts and disks in the
+\fBdisklist\fR. Both
+\fBhostname\fR
+and
+\fBdisks\fR
+are special expressions, see the "HOST & DISK EXPRESSION" section of
+\fBamanda\fR(8)
+for a description.
.TP
\fBversion\fR
-Show the current version and some compile time and runtime parameters\&. The \fBconfig\fR parameter must be present but is ignored\&.
-
+Show the current version and some compile time and runtime parameters. The
+\fBconfig\fR
+parameter must be present but is ignored.
.TP
-\fBforce\-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
-Force the \fBdisks\fR on \fBhostname\fR to bump to a new incremental level during the next \fBAmanda\fR run\&.
-
+\fBforce-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
+Force the
+\fBdisks\fR
+on
+\fBhostname\fR
+to bump to a new incremental level during the next
+\fBAmanda\fR
+run.
.TP
-\fBforce\-no\-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
-Force the \fBdisks\fR on \fBhostname\fR to not bump to a new incremental level during the next \fBAmanda\fR run\&.
-
+\fBforce-no-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
+Force the
+\fBdisks\fR
+on
+\fBhostname\fR
+to not bump to a new incremental level during the next
+\fBAmanda\fR
+run.
.TP
-\fBunforce\-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
-Undo a previous \fBforce\-bump\fR or \fBforce\-no\-bump\fR command\&.
-
+\fBunforce-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
+Undo a previous
+\fBforce-bump\fR
+or
+\fBforce-no-bump\fR
+command.
.TP
\fBforce\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
-Force the \fBdisks\fR on \fBhostname\fR to do a full (level 0) backup during the next \fBAmanda\fR run\&.
-
+Force the
+\fBdisks\fR
+on
+\fBhostname\fR
+to do a full (level 0) backup during the next
+\fBAmanda\fR
+run.
.TP
\fBunforce\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
-Undo a previous \fBforce\fR command\&.
-
+Undo a previous
+\fBforce\fR
+command.
.TP
-\fBreuse\fR \fBtapelabel\fR [ \&.\&.\&. ]
-The tapes listed will be available for reuse at their point in the tape cycle\&.
-
+\fBreuse\fR \fBtapelabel\fR [ ... ]
+The tapes listed will be available for reuse at their point in the tape cycle.
.TP
-\fBno\-reuse\fR \fBtapelabel\fR [ \&.\&.\&. ]
-The tapes listed will not be reused when their turn comes up again in the tape cycle\&. Note that if this causes the number of reusable tapes to drop below the \fBamanda\&.conf\fR \fBtapecycle\fR value, \fBAmanda\fR will request new tapes until the count is satisfied again\&.
-
+\fBno-reuse\fR \fBtapelabel\fR [ ... ]
+The tapes listed will not be reused when their turn comes up again in the tape cycle. Note that if this causes the number of reusable tapes to drop below the
+\fBamanda.conf\fR\fBtapecycle\fR
+value,
+\fBAmanda\fR
+will request new tapes until the count is satisfied again.
.TP
\fBdue\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
-Show when the next full dump is due\&.
-
+Show when the next full dump is due.
.TP
-\fBfind\fR [ \fB\-\-sort\fR \fIhkdlpb\fR ]\fB\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
-Display all backups currently on tape or in the holding disk\&. The tape label or holding disk filename, file number, and status are displayed\&.
-
-The \fB\-\-sort\fR option changes the sort order using the following flags:
-
-\fBh\fRhost name \fBk\fRdisk name \fBd\fRdump date \fBl\fRbackup level \fBp\fR dump part \fBb\fRtape label
-
-An uppercase letter reverses the sort order for that key\&. The default sort order is \fBhkdlpb\fR\&.
-
+\fBfind\fR [ \fB--sort\fR \fIhkdlpb\fR ]\fB\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
+Display all backups currently on tape or in the holding disk. The tape label or holding disk filename, file number, and status are displayed.
+.sp
+The
+\fB--sort\fR
+option changes the sort order using the following flags:
+.sp
+\fBh\fR
+host name
+\fBk\fR
+disk name
+\fBd\fR
+dump date
+\fBl\fR
+backup level
+\fBp\fR
+dump part
+\fBb\fR
+tape label
+.sp
+An uppercase letter reverses the sort order for that key. The default sort order is
+\fBhkdlpb\fR.
.TP
\fBdelete\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
-Delete the specified \fBdisks\fR on \fBhostname\fR from the \fBAmanda\fR database\&.
-
-.RS
-.Sh "Note"
+Delete the specified
+\fBdisks\fR
+on
+\fBhostname\fR
+from the
+\fBAmanda\fR
+database.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
If you do not also remove the disk from the
\fBdisklist\fR
-file, \fBAmanda\fR will treat it as a new disk during the next run\&.
-.RE
-
-.TP
+file, \fBAmanda\fR will treat it as a new disk during the next run..TP
\fBtape\fR
-Display the tape(s) \fBAmanda\fR expects to write to during the next run\&. See also \fBamcheck\fR(8)\&.
-
+Display the tape(s)
+\fBAmanda\fR
+expects to write to during the next run. See also
+\fBamcheck\fR(8).
.TP
\fBbumpsize\fR
-Display the current bump threshold parameters, calculated for all backup levels\&.
-
+Display the current bump threshold parameters, calculated for all backup levels.
.TP
-\fBbalance\fR [ \fB\-\-days\fR \fI<num>\fR ]\fB\fR \fB\fR \fB\fR
-Display the distribution of full backups throughout the dump schedule\&.
-
+\fBbalance\fR [ \fB--days\fR \fI<num>\fR ]\fB\fR \fB\fR \fB\fR
+Display the distribution of full backups throughout the dump schedule.
.TP
\fBexport\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
-Convert records from the \fBAmanda\fR database to a text format that may be transmitted to another \fBAmanda\fR machine and \fBimport\fRed\&.
-
+Convert records from the
+\fBAmanda\fR
+database to a text format that may be transmitted to another
+\fBAmanda\fR
+machine and
+\fBimport\fRed.
.TP
\fBimport\fR
-Convert \fBexport\fRed records read from standard input to a form \fBAmanda\fR uses and insert them into the database on this machine\&.
-
+Convert
+\fBexport\fRed records read from standard input to a form
+\fBAmanda\fR
+uses and insert them into the database on this machine.
.TP
\fBdisklist\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
-Display the \fBdisklist\fR information for each of the \fBdisks\fR on \fBhostname\fR (or all hosts)\&. Mostly used for debugging\&.
-
+Display the
+\fBdisklist\fR
+information for each of the
+\fBdisks\fR
+on
+\fBhostname\fR
+(or all hosts). Mostly used for debugging.
.TP
\fBinfo\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
-Display the database record for each of the \fBdisks\fR on \fBhostname\fR (or all hosts)\&. Mostly used for debugging\&.
-
+Display the database record for each of the
+\fBdisks\fR
+on
+\fBhostname\fR
+(or all hosts). Mostly used for debugging.
.SH "EXAMPLES"
-
.PP
-Request three specific file systems on \fBmachine\-a\fR get a full level 0 backup during the next \fBAmanda\fR run\&.
+Request three specific file systems on
+\fBmachine-a\fR
+get a full level 0 backup during the next
+\fBAmanda\fR
+run.
.nf
-$ amadmin daily force machine\-a / /var /usr
-amadmin: machine\-a:/ is set to a forced level 0 tonight\&.
-amadmin: machine\-a:/var is set to a forced level 0 tonight\&.
-amadmin: machine\-a:/usr is set to a forced level 0 tonight\&.
+$ amadmin daily force machine-a / /var /usr
+amadmin: machine-a:/ is set to a forced level 0 tonight.
+amadmin: machine-a:/var is set to a forced level 0 tonight.
+amadmin: machine-a:/usr is set to a forced level 0 tonight.
.fi
-
.PP
-Request all file systems on \fBmachine\-b\fR get a full level 0 backup during the next \fBAmanda\fR run\&.
+Request all file systems on
+\fBmachine-b\fR
+get a full level 0 backup during the next
+\fBAmanda\fR
+run.
.nf
-$ amadmin daily force machine\-b
-amadmin: machine\-b:/ is set to a forced level 0 tonight\&.
-amadmin: machine\-b:/var is set to a forced level 0 tonight\&.
-amadmin: machine\-b:/usr is set to a forced level 0 tonight\&.
-amadmin: machine\-b:/home is set to a forced level 0 tonight\&.
+$ amadmin daily force machine-b
+amadmin: machine-b:/ is set to a forced level 0 tonight.
+amadmin: machine-b:/var is set to a forced level 0 tonight.
+amadmin: machine-b:/usr is set to a forced level 0 tonight.
+amadmin: machine-b:/home is set to a forced level 0 tonight.
.fi
-
.PP
-Undo the previous \fBforce\fR request for \fI/home\fR on \fBmachine\-b\fR\&. The other file systems will still get a full level 0 backup\&.
+Undo the previous
+\fBforce\fR
+request for
+\fI/home\fR
+on
+\fBmachine-b\fR. The other file systems will still get a full level 0 backup.
.nf
-$ amadmin daily unforce machine\-b /home
-amadmin: force command for machine\-b:/home cleared\&.
+$ amadmin daily unforce machine-b /home
+amadmin: force command for machine-b:/home cleared.
.fi
-
.PP
-Locate backup images of \fI/var\fR from \fBmachine\-c\fR\&. The \fBtape or file\fR column displays either a tape label or a filename depending on whether the image is on tape or is still in the holding disk\&. If the image is on tape, the \fBfile\fR column tells you which file on the tape has the image (file number zero is a tape label)\&. This column shows zero and is not meaningful if the image is still in the holding disk\&. The \fBstatus\fR column tells you whether the backup was successful or had some type of error\&.
+Locate backup images of
+\fI/var\fR
+from
+\fBmachine-c\fR. The
+\fBtape or file\fR
+column displays either a tape label or a filename depending on whether the image is on tape or is still in the holding disk. If the image is on tape, the
+\fBfile\fR
+column tells you which file on the tape has the image (file number zero is a tape label). This column shows zero and is not meaningful if the image is still in the holding disk. The
+\fBstatus\fR
+column tells you whether the backup was successful or had some type of error.
.nf
-$ amadmin daily find machine\-c /var
+$ amadmin daily find machine-c /var
date host disk lv tape or file file part status
-2000\\\-11\\\-09 machine\\\-c /var 0 000110 9 \-\- OK
-2000\\\-11\\\-08 machine\\\-c /var 2 000109 2 \-\- OK
-2000\\\-11\\\-07 machine\\\-c /var 2 /amanda/20001107/machine\-c\&._var\&.2 0 OK
-2000\\\-11\\\-06 machine\\\-c /var 2 000107 2 \-\- OK
-2000\\\-11\\\-05 machine\\\-c /var 2 000106 3 \-\- OK
-2000\\\-11\\\-04 machine\\\-c /var 2 000105 2 \-\- OK
-2000\\\-11\\\-03 machine\\\-c /var 2 000104 2 \-\- OK
-2000\\\-11\\\-02 machine\\\-c /var 2 000103 2 \-\- OK
-2000\\\-11\\\-01 machine\\\-c /var 1 000102 5 \-\- OK
-2000\\\-10\\\-31 machine\\\-c /var 1 000101 3 \-\- OK
+2000\-11\-09 machine\-c /var 0 000110 9 -- OK
+2000\-11\-08 machine\-c /var 2 000109 2 -- OK
+2000\-11\-07 machine\-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
+2000\-11\-06 machine\-c /var 2 000107 2 -- OK
+2000\-11\-05 machine\-c /var 2 000106 3 -- OK
+2000\-11\-04 machine\-c /var 2 000105 2 -- OK
+2000\-11\-03 machine\-c /var 2 000104 2 -- OK
+2000\-11\-02 machine\-c /var 2 000103 2 -- OK
+2000\-11\-01 machine\-c /var 1 000102 5 -- OK
+2000\-10\-31 machine\-c /var 1 000101 3 -- OK
.fi
-
.PP
-Forget about the \fI/workspace\fR disk on \fBmachine\-d\fR\&. If you do not also remove the disk from the \fBdisklist\fR file, \fBAmanda\fR will treat it as a new disk during the next run\&.
+Forget about the
+\fI/workspace\fR
+disk on
+\fBmachine-d\fR. If you do not also remove the disk from the
+\fBdisklist\fR
+file,
+\fBAmanda\fR
+will treat it as a new disk during the next run.
.nf
-$ amadmin daily delete machine\-d /workspace
-amadmin: machine\-d:/workspace deleted from database\&.
-amadmin: NOTE: you'll have to remove these from the disklist yourself\&.
+$ amadmin daily delete machine-d /workspace
+amadmin: machine-d:/workspace deleted from database.
+amadmin: NOTE: you'll have to remove these from the disklist yourself.
.fi
-
.PP
-Find the next tape \fBAmanda\fR will use (in this case, 123456)\&.
+Find the next tape
+\fBAmanda\fR
+will use (in this case,
+123456).
.nf
$ amadmin daily tape
-The next \fBAmanda\fR run should go onto tape 123456 or a new tape\&.
+The next \fBAmanda\fR run should go onto tape 123456 or a new tape.
.fi
-
.PP
-Show how well full backups are balanced across the dump cycle\&. The \fBdue\-date\fR column is the day the backups are due for a full backup\&. \fB#fs\fR shows the number of filesystems doing full backups that night, and \fBorig KB\fR and \fBout KB\fR show the estimated total size of the backups before and after any compression, respectively\&.
-
+Show how well full backups are balanced across the dump cycle. The
+\fBdue-date\fR
+column is the day the backups are due for a full backup.
+\fB#fs\fR
+shows the number of filesystems doing full backups that night, and
+\fBorig KB\fR
+and
+\fBout KB\fR
+show the estimated total size of the backups before and after any compression, respectively.
.PP
-The \fBbalance\fR column shows how far off that night's backups are from the average size (shown at the bottom of the balance column)\&. \fBAmanda\fR tries to keep the backups within +/\- 5%, but since the amount of data on each filesystem is always changing, and \fBAmanda\fR will never delay backups just to rebalance the schedule, it is common for the schedule to fluctuate by larger percentages\&. In particular, in the case of a tape or backup failure, a bump will occur the following night, which will not be smoothed out until the next pass through the schedule\&.
-
+The
+\fBbalance\fR
+column shows how far off that night's backups are from the average size (shown at the bottom of the balance column).
+\fBAmanda\fR
+tries to keep the backups within +/- 5%, but since the amount of data on each filesystem is always changing, and
+\fBAmanda\fR
+will never delay backups just to rebalance the schedule, it is common for the schedule to fluctuate by larger percentages. In particular, in the case of a tape or backup failure, a bump will occur the following night, which will not be smoothed out until the next pass through the schedule.
.PP
-The last line also shows an estimate of how many \fBAmanda\fR runs will be made between full backups for a file system\&. In the example, a file system will probably have a full backup done every eight times \fBAmanda\fR is run (e\&.g\&. every eight days)\&.
+The last line also shows an estimate of how many
+\fBAmanda\fR
+runs will be made between full backups for a file system. In the example, a file system will probably have a full backup done every eight times
+\fBAmanda\fR
+is run (e.g. every eight days).
.nf
$ amadmin daily balance
- due\-date #fs orig KB out KB balance
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-11/10 Mon 21 930389 768753 +5\&.1%
-11/11 Tue 29 1236272 733211 +0\&.2%
-11/12 Wed 31 1552381 735796 +0\&.6%
-11/13 Thu 23 1368447 684552 \-6\&.4%
-11/14 Fri 32 1065603 758155 +3\&.6%
-11/15 Sat 14 1300535 738430 +0\&.9%
-11/16 Sun 31 1362696 740365 +1\&.2%
-11/17 Mon 30 1427936 773397 +5\&.7%
-11/18 Tue 11 1059191 721786 \-1\&.3%
-11/19 Wed 19 1108737 661867 \-9\&.5%
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ due-date #fs orig KB out KB balance
+-------------------------------------------
+11/10 Mon 21 930389 768753 +5.1%
+11/11 Tue 29 1236272 733211 +0.2%
+11/12 Wed 31 1552381 735796 +0.6%
+11/13 Thu 23 1368447 684552 -6.4%
+11/14 Fri 32 1065603 758155 +3.6%
+11/15 Sat 14 1300535 738430 +0.9%
+11/16 Sun 31 1362696 740365 +1.2%
+11/17 Mon 30 1427936 773397 +5.7%
+11/18 Tue 11 1059191 721786 -1.3%
+11/19 Wed 19 1108737 661867 -9.5%
+-------------------------------------------
TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
.fi
-
.SH "FILES"
-
.PP
-/usr/local/etc/amanda/\fBconfig\fR/amanda\&.conf
-
+/usr/local/etc/amanda/\fBconfig\fR/amanda.conf
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org> : Original text
-
+James da Silva,
+<jds@amanda.org>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamcheck\fR(8), \fBamdump\fR(8), \fBamrestore\fR(8), \fBamfetchdump\fR(8)
+\fBamanda\fR(8),
+\fBamcheck\fR(8),
+\fBamdump\fR(8),
+\fBamrestore\fR(8),
+\fBamfetchdump\fR(8)
.IP "\\$1" \\$2
..
.TH "AMAESPIPE" 8 "" "" ""
-.SH NAME
-amaespipe \- wrapper program for aespipe
+.SH "NAME"
+amaespipe - wrapper program for aespipe
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 10
\fBamaespipe\fR
-.ad
-.hy
-
.SH "DESCRIPTION"
-
.PP
- \fBamaespipe\fR requires \fBaespipe\fR and \fBgpg\fR to work\&. Aespipe is available from : http://loop-aes.sourceforge.net
-
+\fBamaespipe\fR
+requires
+\fBaespipe\fR
+and
+\fBgpg\fR
+to work. Aespipe is available from
+: http://loop-aes.sourceforge.net
.PP
- \fBamaespipe\fR will search for the aespipe program in the following directories: /usr/bin:/usr/local/bin:/sbin:/usr/sbin\&.
-\fBamaespipe\fR is called by \fBamcrypt\fR for \fBAmanda\fR data encryption\&.
-
+\fBamaespipe\fR
+will search for the aespipe program in the following directories: /usr/bin:/usr/local/bin:/sbin:/usr/sbin.
+\fBamaespipe\fR is called by \fBamcrypt\fR for \fBAmanda\fR data encryption.
.PP
- \fBamaespipe\fR is based on aespipe's bzaespipe program\&. It calls aespipe to encrypt data using AES256 as the encryption and SHA256 as the hash function\&. GPG key should be stored in $AMANDA_HOME/\&.gnupg/am_key\&.gpg\&. \fBamaespipe\fR reads passphrase from file descriptor 3\&. During decryption, \fBamaespipe\fR autodects encryption type and hash function from the encrypted image\&.
-
+\fBamaespipe\fR
+is based on aespipe's bzaespipe program. It calls aespipe to encrypt data using AES256 as the encryption and SHA256 as the hash function. GPG key should be stored in $AMANDA_HOME/.gnupg/am_key.gpg.
+\fBamaespipe\fR
+reads passphrase from file descriptor 3. During decryption,
+\fBamaespipe\fR
+autodects encryption type and hash function from the encrypted image.
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamanda\&.conf\fR(5), \fBaespipe\fR(1), \fBamcrypt\fR(8), \fBgpg\fR(1)
+\fBamanda\fR(8),
+\fBamanda.conf\fR(5),
+\fBaespipe\fR(1),
+\fBamcrypt\fR(8),
+\fBgpg\fR(1)
.IP "\\$1" \\$2
..
.TH "AMANDA" 8 "" "" ""
-.SH NAME
-amanda \- Advanced Maryland Automatic Network Disk Archiver
+.SH "NAME"
+amanda - Advanced Maryland Automatic Network Disk Archiver
.SH "SYNOPSIS"
-.ad l
-.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 5
\fBamdd\fR [\fIoptions\fR]
-.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
+\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]
+\fBamlabel\fR \fIconfig\fR \fIlabel\fR [\fIslot\fRÂ \fIslot\fR]
.br
-.ad
-.hy
-.ad l
-.hy 0
.HP 5
\fBammt\fR [\fIoptions\fR]
-.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
+\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]]
+\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
+\fBamfetchdump\fR [\fIoptions\fR] \fIconfig\fR [\fIhostname\fRÂ [\fIdiskname\fRÂ [\fIdate\fRÂ [level]]]]
.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 11
\fBamtapetype\fR [\fIoptions\fR]
-.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
-.hy 0
.HP 12
\fBamverifyrun\fR \fIconfig\fR
-.ad
-.hy
-
.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
-Flush backups from the holding disk to tape\&. \fBAmflush\fR is used after \fBamdump\fR has reported it could not write backups to tape for some reason\&. When this happens, backups stay in the holding disk\&. Run \fBamflush\fR after the tape problem is corrected to write backups from the holding disk to tape\&.
-
+Flush backups from the holding disk to tape.
+\fBAmflush\fR
+is used after
+\fBamdump\fR
+has reported it could not write backups to tape for some reason. When this happens, backups stay in the holding disk. Run
+\fBamflush\fR
+after the tape problem is corrected to write backups from the holding disk to tape.
.TP
\fBamcleanup\fR
-Clean up after an interrupted \fBamdump\fR\&. This command is only needed if \fBamdump\fR was unable to complete for some reason, usually because the tape server host crashed while \fBamdump\fR was running\&.
-
+Clean up after an interrupted
+\fBamdump\fR. This command is only needed if
+\fBamdump\fR
+was unable to complete for some reason, usually because the tape server host crashed while
+\fBamdump\fR
+was running.
.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\&.
-
+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
-Verify the correct tape is mounted and all file systems on all backup client systems are ready to be backed up\&. Often run by \fBcron\fR before \fBamdump\fR to generate a mail warning that backups might fail unless corrective action is taken\&.
-
+Verify the correct tape is mounted and all file systems on all backup client systems are ready to be backed up. Often run by
+\fBcron\fR
+before
+\fBamdump\fR
+to generate a mail warning that backups might fail unless corrective action is taken.
.TP
\fBamadmin\fR
-Take care of administrative tasks like finding out which tapes are needed to restore a filesystem, forcing hosts to do full backups of selected disks and looking at schedule balance information\&.
-
+Take care of administrative tasks like finding out which tapes are needed to restore a filesystem, forcing hosts to do full backups of selected disks and looking at schedule balance information.
.TP
\fBamtape\fR
-Take care of tape changer control operations like loading particular tapes, ejecting tapes and scanning the tape storage slots\&.
-
+Take care of tape changer control operations like loading particular tapes, ejecting tapes and scanning the tape storage slots.
.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
-Report the status of a running or completed \fBamdump\fR\&.
-
+Report the status of a running or completed
+\fBamdump\fR.
.TP
\fBamoverview\fR
-Display a chart of hosts and file systems backed up every run\&.
-
+Display a chart of hosts and file systems backed up every run.
.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\&.
-
+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\&.
-
-.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\&.
-
-.PP
-Second is the \fBdisklist\fR file, which lists hosts and disk partitions to back up\&.
-
-.PP
-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\&.
-
-.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\&.
-
-.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\&.
-
-.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\&.
-
-.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\&.
-
+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.
+.PP
+Second is the
+\fBdisklist\fR
+file, which lists hosts and disk partitions to back up.
+.PP
+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.
+.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.
+.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.
+.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.
+.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] ]
.fi
-
.PP
-All pairs [ \fBhostname diskname\fR ] must be unique\&.
-
+All pairs [
+\fBhostname diskname\fR
+] must be unique.
.PP
-Lines starting with # are ignored, as are blank lines\&. The fields have the following meanings:
-
+Lines starting with # are ignored, as are blank lines. The fields have the following meanings:
.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
-Default: same as diskname\&. The name of the disk device to be backed up\&. It may be a full device name, a device name without the \fI/dev/\fR prefix, e\&.g\&. \fBsd0a\fR, or a mount point such as \fI/usr\fR\&.
-
-It may also refer to a PC share by starting the name with two (forward) slashes, e\&.g\&. \fI//some\-pc/home\fR\&. In this case, the \fBprogram\fR option in the associated \fBdumptype\fR must be entered as \fBGNUTAR\fR\&. It is the combination of the double slash disk name and \fBprogram GNUTAR\fR in the \fBdumptype\fR that triggers the use of Samba\&.
-
+Default: same as diskname. The name of the disk device to be backed up. It may be a full device name, a device name without the
+\fI/dev/\fR
+prefix, e.g.
+\fBsd0a\fR, or a mount point such as
+\fI/usr\fR.
+.sp
+It may also refer to a PC share by starting the name with two (forward) slashes, e.g.
+\fI//some-pc/home\fR. In this case, the
+\fBprogram\fR
+option in the associated
+\fBdumptype\fR
+must be entered as
+\fBGNUTAR\fR. It is the combination of the double slash disk name and
+\fBprogram GNUTAR\fR
+in the
+\fBdumptype\fR
+that triggers the use of Samba.
.TP
\fBdumptype\fR
-Refers to a \fBdumptype\fR defined in the \fBamanda\&.conf\fR file\&. \fBDumptype\fRs specify backup related parameters, such as whether to compress the backups, whether to record backup results in \fI/etc/dumpdates\fR, the disk's relative priority, etc\&.
-
+Refers to a
+\fBdumptype\fR
+defined in the
+\fBamanda.conf\fR
+file.
+\fBDumptype\fRs specify backup related parameters, such as whether to compress the backups, whether to record backup results in
+\fI/etc/dumpdates\fR, the disk's relative priority, etc.
.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
-Default: \fBlocal\fR\&. The name of a network interface definition in the \fBamanda\&.conf\fR file, used to balance network load\&.
-
+Default:
+\fBlocal\fR. The name of a network interface definition in the
+\fBamanda.conf\fR
+file, used to balance network load.
.PP
-Instead of naming a \fBdumptype\fR, it is possible to define one in\-line, enclosing \fBdumptype\fR options within curly braces, one per line, just like a \fBdumptype\fR definition in \fBamanda\&.conf\fR\&. Since pre\-existing \fBdumptype\fRs are valid option names, this syntax may be used to customize \fBdumptype\fRs for particular disks\&.
-
+Instead of naming a
+\fBdumptype\fR, it is possible to define one in-line, enclosing
+\fBdumptype\fR
+options within curly braces, one per line, just like a
+\fBdumptype\fR
+definition in
+\fBamanda.conf\fR. Since pre-existing
+\fBdumptype\fRs are valid option names, this syntax may be used to customize
+\fBdumptype\fRs for particular disks.
.PP
-A line break \fBmust\fR follow the left curly bracket\&.
-
+A line break
+\fBmust\fR
+follow the left curly bracket.
.PP
-For instance, if a \fBdumptype\fR named \fBnormal\fR is used for most disks, but use of the holding disk needs to be disabled for the file system that holds it, this would work instead of defining a new dumptype:
+For instance, if a
+\fBdumptype\fR
+named
+\fBnormal\fR
+is used for most disks, but use of the holding disk needs to be disabled for the file system that holds it, this would work instead of defining a new dumptype:
.nf
\fBhostname diskname\fR [ \fBdiskdevice\fR ] {
holdingdisk no
} [ \fBspindle\fR [ \fBinterface\fR ] ]
.fi
-
.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
+.sp
.nf
YYYYMMDD label flags
.fi
-
-.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)\&.
-
.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\&.
-
+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
\fBtape\fR
-This is the default driver\&. The \fBdriver\-info\fR is the tape device name\&. Entering
+This is the default driver. The
+\fBdriver-info\fR
+is the tape device name. Entering
+
+.sp
.nf
tapedev /dev/rmt/0mn
.fi
- is really a short hand for
+is really a short hand for
+
+.sp
.nf
tapedev tape:/dev/rmt/0mn
.fi
-\&.
-
+.
.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:
+.sp
+
+.sp
.nf
tapedev null:
.fi
-
-The \fBlength\fR value from the associated \fBtapetype\fR is used to limit the amount of data written\&. When the limit is reached, the driver will simulate end of tape\&.
-
-.RS
-.Sh "Note"
+.sp
+The
+\fBlength\fR
+value from the associated
+\fBtapetype\fR
+is used to limit the amount of data written. When the limit is reached, the driver will simulate end of tape.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
This driver should only be used for debugging and testing,
and probably only with the
\fBrecord\fR
option set to
-\fBno\fR\&.
-.RE
-
-.TP
+\fBno\fR..TP
\fBrait\fR
-\fBR\fRedundant \fBA\fRrray of \fBI\fRnexpensive (?) \fBT\fRapes\&. Reads and writes tapes mounted on multiple drives by spreading the data across N\-1 drives and using the last drive for a checksum\&. See docs/RAIT for more information\&.
-
-The \fBdriver\-info\fR field describes the devices to use\&. Curly braces indicate multiple replacements in the string\&. For instance:
-
-
+\fBR\fRedundant
+\fBA\fRrray of
+\fBI\fRnexpensive (?)
+\fBT\fRapes. Reads and writes tapes mounted on multiple drives by spreading the data across N-1 drives and using the last drive for a checksum. See docs/RAIT for more information.
+.sp
+The
+\fBdriver-info\fR
+field describes the devices to use. Curly braces indicate multiple replacements in the string. For instance:
+.sp
+
+.sp
.nf
tapedev rait:/dev/rmt/tps0d{4,5,6}n
.fi
-
+.sp
would use the following devices:
-
-\fI/dev/rmt/tps0d4n\fR \fI/dev/rmt/tps0d5n\fR \fI/dev/rmt/tps0d6n\fR
-
+.sp
+\fI/dev/rmt/tps0d4n\fR\fI/dev/rmt/tps0d5n\fR\fI/dev/rmt/tps0d6n\fR
.TP
\fBfile\fR
-This driver emulates a tape device with a set of files in a directory\&. The \fBdriver\-info\fR field must be the name of an existing directory\&. The driver will test for a subdirectory of that named \fBdata\fR and return \fBoffline\fR until it is present\&. When present, the driver uses two files in the \fBdata\fR subdirectory for each tape file\&. One contains the actual data\&. The other contains record length information\&.
-
-The driver uses a file named \fBstatus\fR in the \fBfile\fR device directory to hold driver status information, such as tape position\&. If not present, the driver will create it as though the device is rewound\&.
-
-The \fBlength\fR value from the associated \fBtapetype\fR is used to limit the amount of data written\&. When the limit is reached, the driver will simulate end of tape\&.
-
-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\&.
-
-To read the CD, mount it and create the \fBdata\fR symlink in the \fBfile\fR device directory\&.
-
+This driver emulates a tape device with a set of files in a directory. The
+\fBdriver-info\fR
+field must be the name of an existing directory. The driver will test for a subdirectory of that named
+\fBdata\fR
+and return
+\fBoffline\fR
+until it is present. When present, the driver uses two files in the
+\fBdata\fR
+subdirectory for each tape file. One contains the actual data. The other contains record length information.
+.sp
+The driver uses a file named
+\fBstatus\fR
+in the
+\fBfile\fR
+device directory to hold driver status information, such as tape position. If not present, the driver will create it as though the device is rewound.
+.sp
+The
+\fBlength\fR
+value from the associated
+\fBtapetype\fR
+is used to limit the amount of data written. When the limit is reached, the driver will simulate end of tape.
+.sp
+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.
+.sp
+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.
+.sp
+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\&.
-
-.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\&.
-
-.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\&.
-
-The format of the \fI\&.amandahosts\fR file is:
-
-\fBhostname\fR [ \fBusername\fR ]
-
-If \fBusername\fR is ommitted, it defaults to the user running \fBamandad\fR, i\&.e\&. the user listed in the \fBinetd\fR or \fBxinetd\fR configuration file\&.
-
+\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.
+.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.
+.sp
+The format of the
+\fI.amandahosts\fR
+file is:
+.sp
+\fBhostname\fR
+[
+\fBusername\fR
+]
+.sp
+If
+\fBusername\fR
+is ommitted, it defaults to the user running
+\fBamandad\fR, i.e. the user listed in the
+\fBinetd\fR
+or
+\fBxinetd\fR
+configuration file.
.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\&.
-
-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:
-
+\fBAmanda\fR
+may use the Kerberos authentication system. Further information is in the
+\fBdocs/KERBEROS\fRfile that comes with an
+\fBAmanda\fR
+distribution.
+.sp
+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\&.
-
-You can find further information in the \fBdocs/SAMBA\fR file that comes with an \fBAmanda\fR distribution\&.
-
+ //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.
+.sp
+You can find further information in the
+\fBdocs/SAMBA\fRfile that comes with an
+\fBAmanda\fR
+distribution.
.SH "HOST & DISK EXPRESSION"
-
.PP
-All host and disk arguments to programs are special expressions\&. The command applies to all disks that match your arguments\&. This section describes the matcher\&.
-
+All host and disk arguments to programs are special expressions. The command applies to all disks that match your arguments. This section describes the matcher.
.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\&.
-
+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.
+.sp
.nf
-\&. word separator for a host
+. word separator for a host
/ word separator for a disk
^ anchor at left
$ anchor at right
** match zero or more characters including the separator
.fi
-
.PP
Some examples:
-
+.sp
.nf
EXPRESSION WILL MATCH WILL NOT MATCH
hosta hosta hostb
- hoSTA\&.dOMAIna\&.ORG
- foo\&.hosta\&.org
+ 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
ho**na hoina
- ho\&.aina\&.org
-^hosta hosta foo\&.hosta\&.org
+ ho.aina.org
+^hosta hosta foo.hosta.org
sda* /dev/sda1
/dev/sda12
/opt/ opt (disk) opt (host)
-\&.opt\&. opt (host) opt (disk)
+.opt. opt (host) opt (disk)
/ / any other disk
/usr /usr
/usr/opt
/usr$ /usr /usr/opt
.fi
-
.SH "DATESTAMP EXPRESSION"
-
.PP
-A \fBdatestamp\fR expression is a range expression where we only match the prefix\&. Leading ^ is removed\&. Trailing $ forces an exact match\&.
-20001212\-14match all dates beginning with 20001212, 20001213 or 2000121420001212\-4same as previous20001212\-24match all dates between 20001212 and 200012242000121match all dates that start with 2000121 (20001210\-20001219)2match all dates that start with 2 (20000101\-29991231)2000\-10match all dates between 20000101\-20101231200010$match only 200010
-.PP
-
+A
+\fBdatestamp\fR
+expression is a range expression where we only match the prefix. Leading ^ is removed. Trailing $ forces an exact match.
+20001212-14match all dates beginning with 20001212, 20001213 or 2000121420001212-4same as previous20001212-24match all dates between 20001212 and 200012242000121match all dates that start with 2000121 (20001210-20001219)2match all dates that start with 2 (20000101-29991231)2000-10match all dates between 20000101-20101231200010$match only 200010.PP
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org> : Original text
-
+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), \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)
+\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)
.IP "\\$1" \\$2
..
.TH "AMANDA.CONF" 5 "" "" ""
-.SH NAME
-amanda.conf \- Main configuration file for Amanda, the Advanced Maryland Automatic Network Disk Archiver
+.SH "NAME"
+amanda.conf - Main configuration file for Amanda, the Advanced Maryland Automatic Network Disk Archiver
.SH "DESCRIPTION"
-
.PP
-\fIamanda\&.conf\fR is the main configuration file for \fBAmanda\fR\&. This manpage lists the relevant sections and parameters of this file for quick reference\&.
-
+\fIamanda.conf\fR
+is the main configuration file for
+\fBAmanda\fR. This manpage lists the relevant sections and parameters of this file for quick reference.
.SH "PARAMETERS"
-
.PP
-There are a number of configuration parameters that control the behavior of the \fBAmanda\fR programs\&. All have default values, so you need not specify the parameter in \fBamanda\&.conf\fR if the default is suitable\&.
-
+There are a number of configuration parameters that control the behavior of the
+\fBAmanda\fR
+programs. All have default values, so you need not specify the parameter in
+\fBamanda.conf\fR
+if the default is suitable.
.PP
-Lines starting with # are ignored, as are blank lines\&. Comments may be placed on a line with a directive by starting the comment with a #\&. The remainder of the line is ignored\&.
-
+Lines starting with # are ignored, as are blank lines. Comments may be placed on a line with a directive by starting the comment with a #. The remainder of the line is ignored.
.PP
-Keywords are case insensitive, i\&.e\&. \fBmailto\fR and \fBMailTo\fR are treated the same\&.
-
+Keywords are case insensitive, i.e.
+\fBmailto\fR
+and
+\fBMailTo\fR
+are treated the same.
.PP
Integer arguments may have one of the following (case insensitive) suffixes, some of which have a multiplier effect:
-
.SS "POSSIBLE SUFFIXES"
-
.TP
\fBb byte bytes\fR
-Some number of bytes\&.
-
+Some number of bytes.
.TP
\fBbps\fR
-Some number of bytes per second\&.
-
+Some number of bytes per second.
.TP
\fBk kb kbyte kbytes kilobyte kilobytes\fR
-Some number of kilobytes (bytes*1024)\&.
-
+Some number of kilobytes (bytes*1024).
.TP
\fBkps kbps\fR
-Some number of kilobytes per second (bytes*1024)\&.
-
+Some number of kilobytes per second (bytes*1024).
.TP
\fBm mb meg mbyte mbytes megabyte megabytes\fR
-Some number of megabytes (bytes*1024*1024)\&.
-
+Some number of megabytes (bytes*1024*1024).
.TP
\fBmps mbps\fR
-Some number of megabytes per second (bytes*1024*1024)\&.
-
+Some number of megabytes per second (bytes*1024*1024).
.TP
\fBg gb gbyte gbytes gigabyte gigabytes\fR
-Some number of gigabytes (bytes*1024*1024*1024)\&.
-
+Some number of gigabytes (bytes*1024*1024*1024).
.TP
\fBtape tapes\fR
-Some number of tapes\&.
-
+Some number of tapes.
.TP
\fBday days\fR
-Some number of days\&.
-
+Some number of days.
.TP
\fBweek weeks\fR
-Some number of weeks (days*7)\&.
-
-.RS
-.Sh "Note"
+Some number of weeks (days*7).
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
The value
\fBinf\fR
may be used in most places where an integer is expected
-to mean an infinite amount\&.
-
-Boolean arguments may have any of the values \fBy\fR, \fByes\fR, \fBt\fR, \fBtrue\fR or \fBon\fR to indicate a true state, or \fBn\fR, \fBno\fR, \fBf\fR, \fBfalse\fR or \fBoff\fR to indicate a false state\&. If no argument is given, \fBtrue\fR is assumed\&.
-
-.RE
-
+to mean an infinite amount.
+
+Boolean arguments may have any of the values
+\fBy\fR,
+\fByes\fR,
+\fBt\fR,
+\fBtrue\fR
+or
+\fBon\fR
+to indicate a true state, or
+\fBn\fR,
+\fBno\fR,
+\fBf\fR,
+\fBfalse\fR
+or
+\fBoff\fR
+to indicate a false state. If no argument is given,
+\fBtrue\fR
+is assumed.
.SS "PARAMETERS"
-
.TP
\fBorg\fR \fB string\fR
-Default: \fBdaily\fR\&. A descriptive name for the configuration\&. This string appears in the Subject line of mail reports\&. Each \fBAmanda\fR configuration should have a different string to keep mail reports distinct\&.
-
+Default:
+\fBdaily\fR. A descriptive name for the configuration. This string appears in the Subject line of mail reports. Each
+\fBAmanda\fR
+configuration should have a different string to keep mail reports distinct.
.TP
\fBmailto\fR \fB string\fR
-Default: \fBoperators\fR\&. A space separated list of recipients for mail reports\&.
-
+Default:
+\fBoperators\fR. A space separated list of recipients for mail reports.
.TP
\fBdumpcycle\fR \fB int\fR
-Default: \fB10 days\fR\&. The number of days in the backup cycle\&. Each disk will get a full backup at least this often\&. Setting this to zero tries to do a full backup each run\&.
-
-.RS
-.Sh "Note"
+Default:
+\fB10 days\fR. The number of days in the backup cycle. Each disk will get a full backup at least this often. Setting this to zero tries to do a full backup each run.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
This parameter may also be set in a specific
\fBdumptype\fR
-(see below)\&.
+(see below).
This value sets the default for all
\fBdumptype\fRs
so must appear in
-\fBamanda\&.conf\fR
+\fBamanda.conf\fR
before any
\fBdumptype\fRs
-are defined\&.
-.RE
-
-.TP
+are defined..TP
\fBrunspercycle\fR \fB int\fR
-Default: \fBsame as dumpcycle\fR\&. The number of amdump runs in \fBdumpcycle\fR days\&. A value of 0 means the same value as \fBdumpcycle\fR\&. A value of \-1 means guess the number of runs from the \fBtapelist\fR file, which is the number of tapes used in the last \fBdumpcycle\fR days / \fBruntapes\fR\&.
-
+Default:
+\fBsame as dumpcycle\fR. The number of amdump runs in
+\fBdumpcycle\fR
+days. A value of 0 means the same value as
+\fBdumpcycle\fR. A value of -1 means guess the number of runs from the
+\fBtapelist\fR
+file, which is the number of tapes used in the last
+\fBdumpcycle\fR
+days /
+\fBruntapes\fR.
.TP
\fBtapecycle\fR \fB int\fR
-Default: \fB15 tapes\fR\&. Typically tapes are used by \fBAmanda\fR in an ordered rotation\&. The \fBtapecycle\fR parameter defines the size of that rotation\&. The number of tapes in rotation must be larger than the number of tapes required for a complete dump cycle (see the \fBdumpcycle\fR parameter)\&.
-
-This is calculated by multiplying the number of \fBamdump\fR runs per dump cycle (\fBrunspercycle\fR parameter) times the number of tapes used per run (\fBruntapes\fR parameter)\&. Typically two to four times this calculated number of tapes are in rotation\&. While \fBAmanda\fR is always willing to use a new tape in its rotation, it refuses to reuse a tape until at least '\fBtapecycle\fR \-1' number of other tapes have been used\&.
-
-It is considered good administrative practice to set the \fBtapecycle\fR parameter slightly lower than the actual number of tapes in rotation\&. This allows the administrator to more easily cope with damaged or misplaced tapes or schedule adjustments that call for slight adjustments in the rotation order\&.
-
+Default:
+\fB15 tapes\fR. Typically tapes are used by
+\fBAmanda\fR
+in an ordered rotation. The
+\fBtapecycle\fR
+parameter defines the size of that rotation. The number of tapes in rotation must be larger than the number of tapes required for a complete dump cycle (see the
+\fBdumpcycle\fR
+parameter).
+.sp
+This is calculated by multiplying the number of
+\fBamdump\fR
+runs per dump cycle (\fBrunspercycle\fR
+parameter) times the number of tapes used per run (\fBruntapes\fR
+parameter). Typically two to four times this calculated number of tapes are in rotation. While
+\fBAmanda\fR
+is always willing to use a new tape in its rotation, it refuses to reuse a tape until at least '\fBtapecycle\fR
+-1' number of other tapes have been used.
+.sp
+It is considered good administrative practice to set the
+\fBtapecycle\fR
+parameter slightly lower than the actual number of tapes in rotation. This allows the administrator to more easily cope with damaged or misplaced tapes or schedule adjustments that call for slight adjustments in the rotation order.
.TP
\fBlabel_new_tapes\fR \fB string\fR
-Default: not set\&. When set, this directive will cause \fBAmanda\fR to automatically write an \fBAmanda\fR tape label to any blank tape she encounters\&. This option is DANGEROUS because when set, \fBAmanda\fR will ERASE any non\-\fBAmanda\fR tapes you may have, and may also ERASE any near\-failing tapes\&. Use with caution\&.
-
-When using this directive, specify the template for new tape labels\&. The template should contain some number of contiguous '%' characters, which will be replaced with a generated number\&. Be sure to specify enough '%' characters that you do not run out of tape labels\&. Example: label_new_tapes "DailySet1\-%%%"
-
+Default: not set. When set, this directive will cause
+\fBAmanda\fR
+to automatically write an
+\fBAmanda\fR
+tape label to any blank tape she encounters. This option is DANGEROUS because when set,
+\fBAmanda\fR
+will ERASE any non-\fBAmanda\fR
+tapes you may have, and may also ERASE any near-failing tapes. Use with caution.
+.sp
+When using this directive, specify the template for new tape labels. The template should contain some number of contiguous '%' characters, which will be replaced with a generated number. Be sure to specify enough '%' characters that you do not run out of tape labels. Example:
+label_new_tapes "DailySet1-%%%"
.TP
+\fBlabel_new_tapes\fR \fB string\fR
=======
- \fBlabel_new_tapes\fR \fB string\fR
-Default: not set\&. When set, this directive will cause \fBAmanda\fR to automatically write an Amanda tape label to any black tape she encounters\&. This option is DANGEROUS because when set, \fBAmanda\fR will ERASE any non\-\fBAmanda\fR tapes you may have, and may also ERASE any near\-failing tapes\&. Use with caution\&.
-
-When using this directive, specify the template for new tape labels\&. The template should contain some number of contiguous '%' characters, which will be replaced with a generated number\&. Be sure to specify enough '%' characters that you do not run out of tape labels\&. Example: label_new_tapes "DailySet1\-%%%"
-
+ Default: not set. When set, this directive will cause
+\fBAmanda\fR
+to automatically write an Amanda tape label to any black tape she encounters. This option is DANGEROUS because when set,
+\fBAmanda\fR
+will ERASE any non-\fBAmanda\fR
+tapes you may have, and may also ERASE any near-failing tapes. Use with caution.
+.sp
+When using this directive, specify the template for new tape labels. The template should contain some number of contiguous '%' characters, which will be replaced with a generated number. Be sure to specify enough '%' characters that you do not run out of tape labels. Example:
+label_new_tapes "DailySet1-%%%"
.TP
\fBdumpuser\fR \fB string\fR
-Default: \fBamanda\fR\&. The login name \fBAmanda\fR uses to run the backups\&. The backup client hosts must allow access from the tape server host as this user via \&.rhosts or \&.amandahosts, depending on how the \fBAmanda\fR software was built\&.
-
+Default:
+\fBamanda\fR. The login name
+\fBAmanda\fR
+uses to run the backups. The backup client hosts must allow access from the tape server host as this user via
+.rhosts
+or
+.amandahosts, depending on how the
+\fBAmanda\fR
+software was built.
.TP
\fBprinter\fR string
-Printer to use when doing tape labels\&. See the \fBlbl\-templ\fR \fBtapetype\fR option\&.
-
+Printer to use when doing tape labels. See the
+\fBlbl-templ\fR\fBtapetype\fR
+option.
.TP
\fBtapedev\fR string
-Default: \fInull:\fR\&. The path name of the non\-rewinding tape device\&. Non\-rewinding tape device names often have an 'n' in the name, e\&.g\&. \fI/dev/rmt/0mn\fR, however this is operating system specific and you should consult that documentation for detailed naming information\&.
-
-If a tape changer is configured (see the \fBtpchanger\fR option), this option might not be used\&.
-
-If the \fBnull\fR output driver is selected (see the section OUTPUT DRIVERS in the \fBamanda\fR(8) manpage for more information), programs such as \fBamdump\fR will run normally but all images will be thrown away\&. This should only be used for debugging and testing, and probably only with the \fBrecord\fR option set to \fBno\fR\&.
-
+Default:
+\fInull:\fR. The path name of the non-rewinding tape device. Non-rewinding tape device names often have an 'n' in the name, e.g.
+\fI/dev/rmt/0mn\fR, however this is operating system specific and you should consult that documentation for detailed naming information.
+.sp
+If a tape changer is configured (see the
+\fBtpchanger\fR
+option), this option might not be used.
+.sp
+If the
+\fBnull\fR
+output driver is selected (see the section OUTPUT DRIVERS in the
+\fBamanda\fR(8)
+manpage for more information), programs such as
+\fBamdump\fR
+will run normally but all images will be thrown away. This should only be used for debugging and testing, and probably only with the
+\fBrecord\fR
+option set to
+\fBno\fR.
.TP
\fBrawtapedev\fR string
-Default: \fInull:\fR\&. The path name of the raw tape device\&. This is only used if \fBAmanda\fR is compiled for Linux machines with floppy tapes and is needed for QIC volume table operations\&.
-
+Default:
+\fInull:\fR. The path name of the raw tape device. This is only used if
+\fBAmanda\fR
+is compiled for Linux machines with floppy tapes and is needed for QIC volume table operations.
.TP
\fBtpchanger\fR string
-Default: \fBnone\fR\&. The name of the tape changer\&. If a tape changer is not configured, this option is not used and should be commented out of the configuration file\&.
-
-If a tape changer is configured, choose one of the changer scripts (e\&.g\&. \fBchg\-scsi\fR) and enter that here\&.
-
+Default:
+\fBnone\fR. The name of the tape changer. If a tape changer is not configured, this option is not used and should be commented out of the configuration file.
+.sp
+If a tape changer is configured, choose one of the changer scripts (e.g.
+\fBchg-scsi\fR) and enter that here.
.TP
\fBchangerdev\fR string
-Default: \fI/dev/null\fR\&. A tape changer configuration parameter\&. Usage depends on the particular changer defined with the \fBtpchanger\fR option\&.
-
+Default:
+\fI/dev/null\fR. A tape changer configuration parameter. Usage depends on the particular changer defined with the
+\fBtpchanger\fR
+option.
.TP
\fBchangerfile\fR string
-Default: \fI/usr/adm/amanda/log/changer\-status\fR\&. A tape changer configuration parameter\&. Usage depends on the particular changer defined with the \fBtpchanger\fR option\&.
-
+Default:
+\fI/usr/adm/amanda/log/changer-status\fR. A tape changer configuration parameter. Usage depends on the particular changer defined with the
+\fBtpchanger\fR
+option.
.TP
\fBruntapes\fR int
-Default: 1\&. The maximum number of tapes used in a single run\&. If a tape changer is not configured, this option is not used and should be commented out of the configuration file\&.
-
-If a tape changer is configured, this may be set larger than one to let \fBAmanda\fR write to more than one tape\&.
-
-Note that this is an upper bound on the number of tapes, and \fBAmanda\fR may use less\&.
-
-Also note that as of this release, \fBAmanda\fR does not support true tape overflow\&. When it reaches the end of one tape, the backup image \fBAmanda\fR was processing starts over again on the next tape\&.
-
+Default:
+1. The maximum number of tapes used in a single run. If a tape changer is not configured, this option is not used and should be commented out of the configuration file.
+.sp
+If a tape changer is configured, this may be set larger than one to let
+\fBAmanda\fR
+write to more than one tape.
+.sp
+Note that this is an upper bound on the number of tapes, and
+\fBAmanda\fR
+may use less.
+.sp
+Also note that as of this release,
+\fBAmanda\fR
+does not support true tape overflow. When it reaches the end of one tape, the backup image
+\fBAmanda\fR
+was processing starts over again on the next tape.
.TP
\fBmaxdumpsize\fR int
-Default: \fBruntapes\fR*\fBtape_length\fR\&. Maximum number of bytes the planner will schedule for a run\&.
-
+Default:
+\fBruntapes\fR*\fBtape_length\fR. Maximum number of bytes the planner will schedule for a run.
.TP
\fBtaperalgo\fR [first|firstfit|largest|largestfit|smallest|last]
-Default: \fBfirst\fR\&. The algorithm used to choose which dump image to send to the taper\&.
-
+Default:
+\fBfirst\fR. The algorithm used to choose which dump image to send to the taper.
.RS
-
.TP
\fBfirst\fR
-First in, first out\&.
-
+First in, first out.
.TP
\fBfirstfit\fR
-The first dump image that will fit on the current tape\&.
-
+The first dump image that will fit on the current tape.
.TP
\fBlargest\fR
-The largest dump image\&.
-
+The largest dump image.
.TP
\fBlargestfit\fR
-The largest dump image that will fit on the current tape\&.
-
+The largest dump image that will fit on the current tape.
.TP
\fBsmallest\fR
-The smallest dump image\&.
-
+The smallest dump image.
.TP
\fBlast\fR
-Last in, first out\&.
-
+Last in, first out.
.RE
-.IP
-
.TP
\fBlabelstr\fR \fB string\fR
-Default: \fB\&.*\fR\&. The tape label constraint regular expression\&. All tape labels generated (see \fBamlabel\fR(8)) and used by this configuration must match the regular expression\&. If multiple configurations are run from the same tape server host, it is helpful to set their labels to different strings (for example, "DAILY[0\-9][0\-9]*" vs\&. "ARCHIVE[0\-9][0\-9]*") to avoid overwriting each other's tapes\&.
-
+Default:
+\fB.*\fR. The tape label constraint regular expression. All tape labels generated (see
+\fBamlabel\fR(8)) and used by this configuration must match the regular expression. If multiple configurations are run from the same tape server host, it is helpful to set their labels to different strings (for example, "DAILY[0-9][0-9]*" vs. "ARCHIVE[0-9][0-9]*") to avoid overwriting each other's tapes.
.TP
\fBtapetype\fR \fB string\fR
-Default: \fBEXABYTE\fR\&. The type of tape drive associated with \fBtapedev\fR or \fBtpchanger\fR\&. This refers to one of the defined \fBtapetype\fRs in the config file (see below), which specify various tape parameters, like the \fBlength\fR, \fBfilemark\fR size, and \fBspeed\fR of the tape media and device\&.
-
-First character of a \fBtapetype\fR string must be an alphabetic character
-
+Default:
+\fBEXABYTE\fR. The type of tape drive associated with
+\fBtapedev\fR
+or
+\fBtpchanger\fR. This refers to one of the defined
+\fBtapetype\fRs in the config file (see below), which specify various tape parameters, like the
+\fBlength\fR,
+\fBfilemark\fR
+size, and
+\fBspeed\fR
+of the tape media and device.
+.sp
+First character of a
+\fBtapetype\fR
+string must be an alphabetic character
.TP
\fBctimeout\fR int
-Default: \fB30 seconds\fR\&. Maximum amount of time that \fBamcheck\fR will wait for each client host\&.
-
+Default:
+\fB30 seconds\fR. Maximum amount of time that
+\fBamcheck\fR
+will wait for each client host.
.TP
\fBdtimeout\fR int
-Default: \fB1800 seconds\fR\&. Amount of idle time per disk on a given client that a \fBdumper\fR running from within \fBamdump\fR will wait before it fails with a data timeout error\&.
-
+Default:
+\fB1800 seconds\fR. Amount of idle time per disk on a given client that a
+\fBdumper\fR
+running from within
+\fBamdump\fR
+will wait before it fails with a data timeout error.
.TP
\fBetimeout\fR int
-Default: \fB300 seconds\fR\&. Amount of time per disk on a given client that the \fBplanner\fR step of \fBamdump\fR will wait to get the dump size estimates\&. For instance, with the default of 300 seconds and four disks on client A, \fBplanner\fR will wait up to 20 minutes for that machine\&. A negative value will be interpreted as a total amount of time to wait per client instead of per disk\&.
-
+Default:
+\fB300 seconds\fR. Amount of time per disk on a given client that the
+\fBplanner\fR
+step of
+\fBamdump\fR
+will wait to get the dump size estimates. For instance, with the default of 300 seconds and four disks on client A,
+\fBplanner\fR
+will wait up to 20 minutes for that machine. A negative value will be interpreted as a total amount of time to wait per client instead of per disk.
.TP
\fBnetusage\fR int
-Default: \fB300 Kbps\fR\&. The maximum network bandwidth allocated to \fBAmanda\fR, in Kbytes per second\&. See also the \fBinterface\fR section\&.
-
+Default:
+\fB300 Kbps\fR. The maximum network bandwidth allocated to
+\fBAmanda\fR, in Kbytes per second. See also the
+\fBinterface\fR
+section.
.TP
\fBinparallel\fR int
-Default: 10\&. The maximum number of backups that \fBAmanda\fR will attempt to run in parallel\&. \fBAmanda\fR will stay within the constraints of network bandwidth and holding disk space available, so it doesn't hurt to set this number a bit high\&. Some contention can occur with larger numbers of backups, but this effect is relatively small on most systems\&.
-
+Default:
+10. The maximum number of backups that
+\fBAmanda\fR
+will attempt to run in parallel.
+\fBAmanda\fR
+will stay within the constraints of network bandwidth and holding disk space available, so it doesn't hurt to set this number a bit high. Some contention can occur with larger numbers of backups, but this effect is relatively small on most systems.
.TP
\fBdisplayunit\fR "k|m|g|t"
-Default: "k"\&. The unit used to print many numbers, k=kilo, m=mega, g=giga, t=tera\&.
-
+Default:
+"k". The unit used to print many numbers, k=kilo, m=mega, g=giga, t=tera.
.TP
\fBdumporder\fR string
-Default: \fBtttTTTTTTT\fR\&. The priority order of each dumper:
-
+Default:
+\fBtttTTTTTTT\fR. The priority order of each dumper:
.RS
.TP 3
-\(bu
+•
s: smallest size
.TP
-\(bu
+•
S: largest size
.TP
-\(bu
+•
t: smallest time
.TP
-\(bu
+•
T: largest time
.TP
-\(bu
+•
b: smallest bandwidth
.TP
-\(bu
+•
B: largest bandwidth
-.LP
.RE
-.IP
-
.TP
\fBmaxdumps\fR int
-Default: 1\&. The maximum number of backups from a single host that \fBAmanda\fR will attempt to run in parallel\&. See also the \fBinparallel\fR option\&.
-
-Note that this parameter may also be set in a specific \fBdumptype\fR (see below)\&. This value sets the default for all \fBdumptype\fRs so must appear in \fBamanda\&.conf\fR before any \fBdumptype\fRs are defined\&.
-
+Default:
+1. The maximum number of backups from a single host that
+\fBAmanda\fR
+will attempt to run in parallel. See also the
+\fBinparallel\fR
+option.
+.sp
+Note that this parameter may also be set in a specific
+\fBdumptype\fR
+(see below). This value sets the default for all
+\fBdumptype\fRs so must appear in
+\fBamanda.conf\fR
+before any
+\fBdumptype\fRs are defined.
.TP
\fBbumpsize\fR int
-Default: \fB10 Mbytes\fR\&. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as size\&. If \fBAmanda\fR determines that the next higher backup level will be this much smaller than the current level, it will do the next level\&. The value of this parameter is used only if the parameter \fBbumppercent\fR is set to 0\&.
-
-The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
-
-See also the options \fBbumppercent\fR, \fBbumpmult\fR and \fBbumpdays\fR\&.
-
+Default:
+\fB10 Mbytes\fR. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as size. If
+\fBAmanda\fR
+determines that the next higher backup level will be this much smaller than the current level, it will do the next level. The value of this parameter is used only if the parameter
+\fBbumppercent\fR
+is set to 0.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype-definition.
+.sp
+See also the options
+\fBbumppercent\fR,
+\fBbumpmult\fR
+and
+\fBbumpdays\fR.
.TP
\fBbumppercent\fR int
-Default: \fB0 percent\fR\&. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as percentage of the current size of the DLE (size of current level 0)\&. If \fBAmanda\fR determines that the next higher backup level will be this much smaller than the current level, it will do the next level\&.
-
-If this parameter is set to 0, the value of the parameter \fBbumpsize\fR is used to trigger bumping\&.
-
-The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
-
-See also the options \fBbumpsize\fR, \fBbumpmult\fR and \fBbumpdays\fR\&.
-
+Default:
+\fB0 percent\fR. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as percentage of the current size of the DLE (size of current level 0). If
+\fBAmanda\fR
+determines that the next higher backup level will be this much smaller than the current level, it will do the next level.
+.sp
+If this parameter is set to 0, the value of the parameter
+\fBbumpsize\fR
+is used to trigger bumping.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype-definition.
+.sp
+See also the options
+\fBbumpsize\fR,
+\fBbumpmult\fR
+and
+\fBbumpdays\fR.
.TP
\fBbumpmult\fR \fB float\fR
-Default: 1\&.5\&. The bump size multiplier\&. \fBAmanda\fR multiplies \fBbumpsize\fR by this factor for each level\&. This prevents active filesystems from bumping too much by making it harder to bump to the next level\&. For example, with the default \fBbumpsize\fR and \fBbumpmult\fR set to 2\&.0, the bump threshold will be 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level three, and so on\&.
-
-The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
-
+Default:
+1.5. The bump size multiplier.
+\fBAmanda\fR
+multiplies
+\fBbumpsize\fR
+by this factor for each level. This prevents active filesystems from bumping too much by making it harder to bump to the next level. For example, with the default
+\fBbumpsize\fR
+and
+\fBbumpmult\fR
+set to 2.0, the bump threshold will be 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level three, and so on.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype-definition.
.TP
\fBbumpdays\fR \fB int\fR
-Default: \fB2 days\fR\&. To insure redundancy in the dumps, \fBAmanda\fR keeps filesystems at the same incremental level for at least \fBbumpdays\fR days, even if the other bump threshold criteria are met\&.
-
-The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
-
+Default:
+\fB2 days\fR. To insure redundancy in the dumps,
+\fBAmanda\fR
+keeps filesystems at the same incremental level for at least
+\fBbumpdays\fR
+days, even if the other bump threshold criteria are met.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype-definition.
.TP
\fBdiskfile\fR \fB string\fR
-Default: \fBdisklist\fR\&. The file name for the \fBdisklist\fR file holding client hosts, disks and other client dumping information\&.
-
+Default:
+\fBdisklist\fR. The file name for the
+\fBdisklist\fR
+file holding client hosts, disks and other client dumping information.
.TP
\fBinfofile\fR \fB string\fR
-Default: \fI/usr/adm/amanda/curinfo\fR\&. The file or directory name for the historical information database\&. If \fBAmanda\fR was configured to use DBM databases, this is the base file name for them\&. If it was configured to use text formated databases (the default), this is the base directory and within here will be a directory per client, then a directory per disk, then a text file of data\&.
-
+Default:
+\fI/usr/adm/amanda/curinfo\fR. The file or directory name for the historical information database. If
+\fBAmanda\fR
+was configured to use DBM databases, this is the base file name for them. If it was configured to use text formated databases (the default), this is the base directory and within here will be a directory per client, then a directory per disk, then a text file of data.
.TP
\fBlogdir\fR \fB string\fR
-Default: \fI/usr/adm/amanda\fR\&. The directory for the \fBamdump\fR and \fBlog\fR files\&.
-
+Default:
+\fI/usr/adm/amanda\fR. The directory for the
+\fBamdump\fR
+and
+\fBlog\fR
+files.
.TP
\fBindexdir\fR \fB string\fR
-Default \fI/usr/adm/amanda/index\fR\&. The directory where index files (backup image catalogues) are stored\&. Index files are only generated for filesystems whose \fBdumptype\fR has the \fBindex\fR option enabled\&.
-
+Default
+\fI/usr/adm/amanda/index\fR. The directory where index files (backup image catalogues) are stored. Index files are only generated for filesystems whose
+\fBdumptype\fR
+has the
+\fBindex\fR
+option enabled.
.TP
\fBtapelist\fR \fB string\fR
-Default: \fBtapelist\fR\&. The file name for the active \fBtapelist\fR file\&. \fBAmanda\fR maintains this file with information about the active set of tapes\&.
-
+Default:
+\fBtapelist\fR. The file name for the active
+\fBtapelist\fR
+file.
+\fBAmanda\fR
+maintains this file with information about the active set of tapes.
.TP
\fBtapebufs\fR \fB int\fR
-Default: 20\&. The number of buffers used by the \fBtaper\fR process run by \fBamdump\fR and \fBamflush\fR to hold data as it is read from the network or disk before it is written to tape\&. Each buffer is a little larger than 32 KBytes and is held in a shared memory region\&.
-
+Default:
+20. The number of buffers used by the
+\fBtaper\fR
+process run by
+\fBamdump\fR
+and
+\fBamflush\fR
+to hold data as it is read from the network or disk before it is written to tape. Each buffer is a little larger than 32 KBytes and is held in a shared memory region.
.TP
\fBreserve\fR \fB number\fR
-Default: 100\&. The part of holding\-disk space that should be reserved for incremental backups if no tape is available, expressed as a percentage of the available holding\-disk space (0\-100)\&. By default, when there is no tape to write to, degraded mode (incremental) backups will be performed to the holding disk\&. If full backups should also be allowed in this case, the amount of holding disk space reserved for incrementals should be lowered\&.
-
+Default:
+100. The part of holding-disk space that should be reserved for incremental backups if no tape is available, expressed as a percentage of the available holding-disk space (0-100). By default, when there is no tape to write to, degraded mode (incremental) backups will be performed to the holding disk. If full backups should also be allowed in this case, the amount of holding disk space reserved for incrementals should be lowered.
.TP
\fBautoflush\fR \fB bool\fR
-Default: \fBoff\fR\&. Whether an amdump run will flush the dumps from holding disk to tape\&.
-
+Default:
+\fBoff\fR. Whether an amdump run will flush the dumps from holding disk to tape.
.TP
\fBamrecover_do_fsf\fR \fB bool\fR
-Default: \fBoff\fR\&. Amrecover will call amrestore with the \-f flag for faster positioning of the tape\&.
-
+Default:
+\fBoff\fR. Amrecover will call amrestore with the -f flag for faster positioning of the tape.
.TP
\fBamrecover_check_label\fR \fB bool\fR
-Default: \fBoff\fR\&. Amrecover will call amrestore with the \-l flag to check the label\&.
-
+Default:
+\fBoff\fR. Amrecover will call amrestore with the -l flag to check the label.
.TP
\fBamrecover_changer\fR \fB string\fR
-Default: ''\&. Amrecover will use the changer if you use 'settape <string>' and that string is the same as the amrecover_changer setting\&.
-
+Default: ''. Amrecover will use the changer if you use 'settape <string>' and that string is the same as the amrecover_changer setting.
.TP
\fBcolumnspec\fR \fB string\fR
-Defines the width of columns \fBamreport\fR should use\&. \fBString\fR is a comma (',') separated list of triples\&. Each triple consists of three parts which are separated by a equal sign ('=') and a colon (':') (see the example)\&. These three parts specify:
-
-
+Defines the width of columns
+\fBamreport\fR
+should use.
+\fBString\fR
+is a comma (',') separated list of triples. Each triple consists of three parts which are separated by a equal sign ('=') and a colon (':') (see the example). These three parts specify:
.RS
.TP 3
-\(bu
+•
the name of the column, which may be:
-
.RS
.TP 3
-\(bu
+•
Compress (compression ratio)
.TP
-\(bu
+•
Disk (client disk name)
.TP
-\(bu
+•
DumpRate (dump rate in KBytes/sec)
.TP
-\(bu
+•
DumpTime (total dump time in hours:minutes)
.TP
-\(bu
+•
HostName (client host name)
.TP
-\(bu
+•
Level (dump level)
.TP
-\(bu
+•
OrigKB (original image size in KBytes)
.TP
-\(bu
+•
OutKB (output image size in KBytes)
.TP
-\(bu
+•
TapeRate (tape writing rate in KBytes/sec)
.TP
-\(bu
+•
TapeTime (total tape time in hours:minutes)
-.LP
.RE
-.IP
.TP
-\(bu
-the amount of space to display before the column (used to get whitespace between columns)\&.
+•
+the amount of space to display before the column (used to get whitespace between columns).
.TP
-\(bu
-the width of the column itself\&. If set to a negative value, the width will be calculated on demand to fit the largest entry in this column\&.
-.LP
+•
+the width of the column itself. If set to a negative value, the width will be calculated on demand to fit the largest entry in this column.
.RE
.IP
Here is an example:
.fi
The above will display the disk information in 18 characters
-and put one space before it\&. The hostname column will be 10 characters wide with
-no space to the left\&. The output KBytes column is seven characters wide
-with one space before it\&.
-
-.TP
+and put one space before it. The hostname column will be 10 characters wide with
+no space to the left. The output KBytes column is seven characters wide
+with one space before it.
+ .TP
\fBincludefile\fR \fB string\fR
-Default: \fBnone\fR\&. The name of an \fBAmanda\fR configuration file to include within the current file\&. Useful for sharing dumptypes, tapetypes and interface definitions among several configurations\&.
-
+Default:
+\fBnone\fR. The name of an
+\fBAmanda\fR
+configuration file to include within the current file. Useful for sharing dumptypes, tapetypes and interface definitions among several configurations.
.SH "HOLDINGDISK SECTION"
-
.PP
-The \fBamanda\&.conf\fR file may define one or more holding disks used as buffers to hold backup images before they are written to tape\&. The syntax is:
+The
+\fBamanda.conf\fR
+file may define one or more holding disks used as buffers to hold backup images before they are written to tape. The syntax is:
.nf
holdingdisk \fBname\fR {
- \fBholdingdisk\-option\fR \fBholdingdisk\-value\fR
- \&.\&.\&.
+ \fBholdingdisk-option\fR \fBholdingdisk-value\fR
+ ...
}.fi
-
.PP
-\fBName\fR is a logical name for this holding disk\&.
-
+\fBName\fR
+is a logical name for this holding disk.
.PP
The options and values are:
-
.TP
\fBcomment\fR \fB string\fR
-Default: \fBnone\fR\&. A comment string describing this holding disk\&.
-
+Default:
+\fBnone\fR. A comment string describing this holding disk.
.TP
\fBdirectory\fR \fB disk\fR
-Default: \fI/dumps/amanda\fR\&. The path to this holding area\&.
-
+Default:
+\fI/dumps/amanda\fR. The path to this holding area.
.TP
\fBuse\fR \fB int\fR
Default:
-\fB0 Gb\fR\&.
-Amount of space that can be used in this holding disk area\&.
-If the value is zero, all available space on the file system is used\&.
-If the value is negative, \fBAmanda\fR will use all available space minus that value\&.
-
-.TP
+\fB0 Gb\fR.
+Amount of space that can be used in this holding disk area.
+If the value is zero, all available space on the file system is used.
+If the value is negative, \fBAmanda\fR will use all available space minus that value.
+ .TP
\fBchunksize\fR \fB int\fR
Default:
-\fB1 Gb\fR\&.
-Holding disk chunk size\&. Dumps larger than the specified size will be stored in multiple
-holding disk files\&. The size of each chunk will not exceed the specified value\&.
+\fB1 Gb\fR.
+Holding disk chunk size. Dumps larger than the specified size will be stored in multiple
+holding disk files. The size of each chunk will not exceed the specified value.
However, even though dump images are split in the holding disk, they are concatenated as
they are written to tape, so each dump image still corresponds to a single continuous
-tape section\&.
+tape section.
If 0 is specified, \fBAmanda\fR will create holding disk chunks as large as
-((INT_MAX/1024)\-64) Kbytes\&.
+((INT_MAX/1024)-64) Kbytes.
Each holding disk chunk includes a 32 Kbyte header, so the minimum
-chunk size is 64 Kbytes (but that would be really silly)\&.
+chunk size is 64 Kbytes (but that would be really silly).
Operating systems that are limited to a maximum file size of 2 Gbytes
-actually cannot handle files that large\&.
-They must be at least one byte less than 2 Gbytes\&.
+actually cannot handle files that large.
+They must be at least one byte less than 2 Gbytes.
Since \fBAmanda\fR works with 32 Kbyte blocks, and
to handle the final read at the end of the chunk, the chunk size
should be at least 64 Kbytes (2 * 32 Kbytes) smaller than the maximum
-file size, e\&.g\&. 2047 Mbytes\&.
-
-.SH "DUMPTYPE SECTION"
-
+file size, e.g. 2047 Mbytes.
+ .SH "DUMPTYPE SECTION"
.PP
-The \fIamanda\&.conf\fR file may define multiple sets of backup options and refer to them by name from the \fIdisklist\fR file\&. For instance, one set of options might be defined for file systems that can benefit from high compression, another set that does not compress well, another set for file systems that should always get a full backup and so on\&.
-
+The
+\fIamanda.conf\fR
+file may define multiple sets of backup options and refer to them by name from the
+\fIdisklist\fR
+file. For instance, one set of options might be defined for file systems that can benefit from high compression, another set that does not compress well, another set for file systems that should always get a full backup and so on.
.PP
-A set of backup options are entered in a \fBdumptype\fR section, which looks like this:
+A set of backup options are entered in a
+\fBdumptype\fR
+section, which looks like this:
.nf
define dumptype \fBname\fR {
- \fBdumptype\-option\fR \fBdumptype\-value\fR
- \&.\&.\&.
+ \fBdumptype-option\fR \fBdumptype-value\fR
+ ...
}
.fi
-
.PP
-\fBName\fR is the name of this set of backup options\&. It is referenced from the \fIdisklist\fR file\&.
-
+\fBName\fR
+is the name of this set of backup options. It is referenced from the
+\fIdisklist\fR
+file.
.PP
-Some of the options in a \fBdumptype\fR section are the same as those in the main part of \fIamanda\&.conf\fR\&. The main option value is used to set the default for all \fBdumptype\fR sections\&. For instance, setting \fBdumpcycle\fR to 50 in the main part of the config file causes all following \fBdumptype\fR sections to start with that value, but the value may be changed on a section by section basis\&. Changes to variables in the main part of the config file must be done before (earlier in the file) any \fBdumptype\fRs are defined\&.
-
+Some of the options in a
+\fBdumptype\fR
+section are the same as those in the main part of
+\fIamanda.conf\fR. The main option value is used to set the default for all
+\fBdumptype\fR
+sections. For instance, setting
+\fBdumpcycle\fR
+to 50 in the main part of the config file causes all following
+\fBdumptype\fR
+sections to start with that value, but the value may be changed on a section by section basis. Changes to variables in the main part of the config file must be done before (earlier in the file) any
+\fBdumptype\fRs are defined.
.PP
The dumptype options and values are:
-
.TP
\fBauth\fR \fB string\fR
-Default: \fBbsd\fR\&. Type of authorization to perform between tape server and backup client hosts\&.
-
-\fBkrb4\fR to use Kerberos\-IV authorization\&.
-
-\fBkrb5\fR to use Kerberos\-V authorization\&.
-
-\fBssh\fR to use OpenSSH authorization\&.
-
+Default:
+\fBbsd\fR. Type of authorization to perform between tape server and backup client hosts.
+.sp
+\fBkrb4\fR
+to use Kerberos-IV authorization.
+.sp
+\fBkrb5\fR
+to use Kerberos-V authorization.
+.sp
+\fBssh\fR
+to use OpenSSH authorization.
.TP
\fBbumpsize\fR int
-Default: \fB10 Mbytes\fR\&. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as size\&. If \fBAmanda\fR determines that the next higher backup level will be this much smaller than the current level, it will do the next level\&. The value of this parameter is used only if the parameter \fBbumppercent\fR is set to 0\&.
-
-See also the options \fBbumppercent\fR, \fBbumpmult\fR and \fBbumpdays\fR\&.
-
+Default:
+\fB10 Mbytes\fR. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as size. If
+\fBAmanda\fR
+determines that the next higher backup level will be this much smaller than the current level, it will do the next level. The value of this parameter is used only if the parameter
+\fBbumppercent\fR
+is set to 0.
+.sp
+See also the options
+\fBbumppercent\fR,
+\fBbumpmult\fR
+and
+\fBbumpdays\fR.
.TP
\fBbumppercent\fR int
-Default: \fB0 percent\fR\&. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as percentage of the current size of the DLE (size of current level 0)\&. If \fBAmanda\fR determines that the next higher backup level will be this much smaller than the current level, it will do the next level\&.
-
-If this parameter is set to 0, the value of the parameter \fBbumpsize\fR is used to trigger bumping\&.
-
-See also the options \fBbumpsize\fR, \fBbumpmult\fR and \fBbumpdays\fR\&.
-
+Default:
+\fB0 percent\fR. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as percentage of the current size of the DLE (size of current level 0). If
+\fBAmanda\fR
+determines that the next higher backup level will be this much smaller than the current level, it will do the next level.
+.sp
+If this parameter is set to 0, the value of the parameter
+\fBbumpsize\fR
+is used to trigger bumping.
+.sp
+See also the options
+\fBbumpsize\fR,
+\fBbumpmult\fR
+and
+\fBbumpdays\fR.
.TP
\fBbumpmult\fR \fB float\fR
-Default: 1\&.5\&. The bump size multiplier\&. \fBAmanda\fR multiplies \fBbumpsize\fR by this factor for each level\&. This prevents active filesystems from bumping too much by making it harder to bump to the next level\&. For example, with the default \fBbumpsize\fR and \fBbumpmult\fR set to 2\&.0, the bump threshold will be 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level three, and so on\&.
-
+Default:
+1.5. The bump size multiplier.
+\fBAmanda\fR
+multiplies
+\fBbumpsize\fR
+by this factor for each level. This prevents active filesystems from bumping too much by making it harder to bump to the next level. For example, with the default
+\fBbumpsize\fR
+and
+\fBbumpmult\fR
+set to 2.0, the bump threshold will be 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level three, and so on.
.TP
\fBbumpdays\fR \fB int\fR
-Default: \fB2 days\fR\&. To insure redundancy in the dumps, \fBAmanda\fR keeps filesystems at the same incremental level for at least \fBbumpdays\fR days, even if the other bump threshold criteria are met\&.
-
+Default:
+\fB2 days\fR. To insure redundancy in the dumps,
+\fBAmanda\fR
+keeps filesystems at the same incremental level for at least
+\fBbumpdays\fR
+days, even if the other bump threshold criteria are met.
.TP
\fBcomment\fR \fB string\fR
-Default: \fBnone\fR\&. A comment string describing this set of backup options\&.
-
+Default:
+\fBnone\fR. A comment string describing this set of backup options.
.TP
\fBcomprate\fR \fBfloat\fR [, \fBfloat\fR ]
-Default: 0\&.50, 0\&.50\&. The expected full and incremental compression factor for dumps\&. It is only used if \fBAmanda\fR does not have any history information on compression rates for a filesystem, so should not usually need to be set\&. However, it may be useful for the first time a very large filesystem that compresses very little is backed up\&.
-
+Default:
+0.50,
+0.50. The expected full and incremental compression factor for dumps. It is only used if
+\fBAmanda\fR
+does not have any history information on compression rates for a filesystem, so should not usually need to be set. However, it may be useful for the first time a very large filesystem that compresses very little is backed up.
.TP
\fBcompress [client|server]\fR \fB string\fR
-Default: \fBclient fast\fR\&. If \fBAmanda\fR does compression of the backup images, it can do so either on the backup client host before it crosses the network or on the tape server host as it goes from the network into the holding disk or to tape\&. Which place to do compression (if at all) depends on how well the dump image usually compresses, the speed and load on the client or server, network capacity, holding disk capacity, availability of tape hardware compression, etc\&.
-
-For either type of compression, \fBAmanda\fR also allows the selection of three styles of compression\&. \fBBest\fR is the best compression available, often at the expense of CPU overhead\&. \fBFast\fR is often not as good a compression as \fBbest\fR, but usually less CPU overhead\&. Or to specify \fBCustom\fR to use your own compression method\&. (See dumptype custom\-compress in example/amanda\&.conf for reference)
-
-So the \fBcompress\fR options line may be one of:
-
-
+Default:
+\fBclient fast\fR. If
+\fBAmanda\fR
+does compression of the backup images, it can do so either on the backup client host before it crosses the network or on the tape server host as it goes from the network into the holding disk or to tape. Which place to do compression (if at all) depends on how well the dump image usually compresses, the speed and load on the client or server, network capacity, holding disk capacity, availability of tape hardware compression, etc.
+.sp
+For either type of compression,
+\fBAmanda\fR
+also allows the selection of three styles of compression.
+\fBBest\fR
+is the best compression available, often at the expense of CPU overhead.
+\fBFast\fR
+is often not as good a compression as
+\fBbest\fR, but usually less CPU overhead. Or to specify
+\fBCustom\fR
+to use your own compression method. (See dumptype custom-compress in example/amanda.conf for reference)
+.sp
+So the
+\fBcompress\fR
+options line may be one of:
.RS
.TP 3
-\(bu
+•
compress none
.TP
-\(bu
+•
compress [client] fast
.TP
-\(bu
+•
compress [client] best
.TP
-\(bu
+•
compress client custom
-
+.sp
Specify client_custom_compress "PROG"
-
-PROG must not contain white space and it must accept \-d for uncompress\&.
+.sp
+PROG must not contain white space and it must accept -d for uncompress.
.TP
-\(bu
+•
compress server fast
.TP
-\(bu
+•
compress server best
.TP
-\(bu
+•
compress server custom
-
+.sp
Specify server_custom_compress "PROG"
-
-PROG must not contain white space and it must accept \-d for uncompress\&.
-.LP
+.sp
+PROG must not contain white space and it must accept -d for uncompress.
.RE
.IP
-Note that some tape devices do compression and this option has nothing to do with whether that is used\&. If hardware compression is used (usually via a particular tape device name or \fBmt\fR option), \fBAmanda\fR (software) compression should be disabled\&.
-
+Note that some tape devices do compression and this option has nothing to do with whether that is used. If hardware compression is used (usually via a particular tape device name or
+\fBmt\fR
+option),
+\fBAmanda\fR
+(software) compression should be disabled.
.TP
\fBdumpcycle\fR \fB int\fR
-Default: \fB10 days\fR\&. The number of days in the backup cycle\&. Each disk using this set of options will get a full backup at least this of ten\&. Setting this to zero tries to do a full backup each run\&.
-
+Default:
+\fB10 days\fR. The number of days in the backup cycle. Each disk using this set of options will get a full backup at least this of ten. Setting this to zero tries to do a full backup each run.
.TP
\fBencrypt [none|client|server]\fR
-Default: \fBnone\fR\&. To encrypt backup images, it can do so either on the backup client host before it crosses the network or on the tape server host as it goes from the network into the holding disk or to tape\&.
-
-So the \fBencrypt\fR options line may be one of:
-
+Default:
+\fBnone\fR. To encrypt backup images, it can do so either on the backup client host before it crosses the network or on the tape server host as it goes from the network into the holding disk or to tape.
+.sp
+So the
+\fBencrypt\fR
+options line may be one of:
.RS
.TP 3
-\(bu
+•
encrypt none
.TP
-\(bu
+•
encrypt client
-
+.sp
Specify client_encrypt "PROG"
-
-PROG must not contain white space\&.
-
-Specify client_decrypt_option "decryption\-parameter" Default: "\-d"
-
-decryption\-parameter must not contain white space\&.
-
-(See dumptype encrypt\-fast in example/amanda\&.conf for reference)
-.TP
-\(bu
+.sp
+PROG must not contain white space.
+.sp
+Specify client_decrypt_option "decryption-parameter" Default: "-d"
+.sp
+decryption-parameter must not contain white space.
+.sp
+(See dumptype encrypt-fast in example/amanda.conf for reference)
+.TP
+•
encrypt server
-
+.sp
Specify server_encrypt "PROG"
-
-PROG must not contain white space\&.
-
-Specify server_decrypt_option "decryption\-parameter" Default: "\-d"
-
-decryption\-parameter must not contain white space\&.
-.LP
+.sp
+PROG must not contain white space.
+.sp
+Specify server_decrypt_option "decryption-parameter" Default: "-d"
+.sp
+decryption-parameter must not contain white space.
.RE
-.IP
-
.PP
-Note that current logic assumes compression then encryption during backup(thus decrypt then uncompress during restore)\&. So specifying client\-encryption AND server\-compression is not supported\&. \fBamcrypt\fR which is a wrapper of \fBaespipe\fR is provided as a reference encryption program\&.
-
+Note that current logic assumes compression then encryption during backup(thus decrypt then uncompress during restore). So specifying client-encryption AND server-compression is not supported.
+\fBamcrypt\fR
+which is a wrapper of
+\fBaespipe\fR
+is provided as a reference encryption program.
.TP
\fBestimate\fR \fBclient|calcsize|server\fR
-Default: \fBclient\fR\&. Determine the way \fBAmanda\fR does it's estimate\&.
-
+Default:
+\fBclient\fR. Determine the way
+\fBAmanda\fR
+does it's estimate.
.RS
.TP 3
-\(bu
+•
client:
-
-Use the same program as the dumping program, this is the most accurate way to do estimates, but it can take a long time\&.
+.sp
+Use the same program as the dumping program, this is the most accurate way to do estimates, but it can take a long time.
.TP
-\(bu
+•
calcsize:
-
-Use a faster program to do estimates, but the result is less accurate\&.
+.sp
+Use a faster program to do estimates, but the result is less accurate.
.TP
-\(bu
+•
server:
-
-Use only statistics from the previous run to give an estimate, it takes only a few seconds but the result is not accurate if your disk usage changes from day to day\&.
-.LP
+.sp
+Use only statistics from the previous run to give an estimate, it takes only a few seconds but the result is not accurate if your disk usage changes from day to day.
.RE
-.IP
-
.TP
\fBexclude\fR [ \fBlist|file\fR ][[optional][ \fBappend\fR ][ \fB string\fR ]+]
-Default: \fBfile\fR\&. There are two exclude lists, \fBexclude file\fR and \fBexclude list\&.\fR With \fBexclude file\fR , the \fBstring\fR is a \fBGNU\-tar\fR exclude expression\&. With \fBexclude list\fR , the \fBstring\fR is a file name on the client containing \fBGNU\-tar\fR exclude expressions\&. The path to the specified exclude list file, if present (see description of 'optional' below), must be readable by the \fBAmanda\fR user\&.
-
-All exclude expressions are concatenated in one file and passed to \fBGNU\-tar\fR as an \fB\-\-exclude\-from\fR argument\&.
-
-Exclude expressions must always be specified as relative to the head directory of the DLE\&.
-
-With the \fBappend\fR keyword, the \fBstring\fR is appended to the current list, without it, the \fBstring\fR overwrites the list\&.
-
-If \fBoptional\fR is specified for \fBexclude list\fR, then amcheck will not complain if the file doesn't exist or is not readable\&.
-
-For \fBexclude list\fR, if the file name is relative, the disk name being backed up is prepended\&. So if this is entered:
-
+Default:
+\fBfile\fR. There are two exclude lists,
+\fBexclude file\fR
+and
+\fBexclude list.\fR
+With
+\fBexclude file\fR
+, the
+\fBstring\fR
+is a
+\fBGNU-tar\fR
+exclude expression. With
+\fBexclude list\fR
+, the
+\fBstring\fR
+is a file name on the client containing
+\fBGNU-tar\fR
+exclude expressions. The path to the specified exclude list file, if present (see description of 'optional' below), must be readable by the
+\fBAmanda\fR
+user.
+.sp
+All exclude expressions are concatenated in one file and passed to
+\fBGNU-tar\fR
+as an
+\fB--exclude-from\fR
+argument.
+.sp
+Exclude expressions must always be specified as relative to the head directory of the DLE.
+.sp
+With the
+\fBappend\fR
+keyword, the
+\fBstring\fR
+is appended to the current list, without it, the
+\fBstring\fR
+overwrites the list.
+.sp
+If
+\fBoptional\fR
+is specified for
+\fBexclude list\fR, then amcheck will not complain if the file doesn't exist or is not readable.
+.sp
+For
+\fBexclude list\fR, if the file name is relative, the disk name being backed up is prepended. So if this is entered:
.nf
- exclude list "\&.amanda\&.excludes"
+ exclude list ".amanda.excludes"
.fi
-the actual file used would be \fI/var/\&.amanda\&.excludes\fR for a backup of \fI/var\fR, \fI/usr/local/\&.amanda\&.excludes\fR for a backup of \fI/usr/local\fR, and so on\&.
-
+the actual file used would be
+\fI/var/.amanda.excludes\fR
+for a backup of
+\fI/var\fR,
+\fI/usr/local/.amanda.excludes\fR
+for a backup of
+\fI/usr/local\fR, and so on.
.TP
\fBholdingdisk\fR \fB boolean\fR
-Default: \fByes\fR\&. Whether a holding disk should be used for these backups or whether they should go directly to tape\&. If the holding disk is a portion of another file system that \fBAmanda\fR is backing up, that file system should refer to a dumptype with \fBholdingdisk\fR set to \fBno\fR to avoid backing up the holding disk into itself\&.
-
+Default:
+\fByes\fR. Whether a holding disk should be used for these backups or whether they should go directly to tape. If the holding disk is a portion of another file system that
+\fBAmanda\fR
+is backing up, that file system should refer to a dumptype with
+\fBholdingdisk\fR
+set to
+\fBno\fR
+to avoid backing up the holding disk into itself.
.TP
\fBignore\fR \fB boolean\fR
-Default: \fBno\fR\&. Whether disks associated with this backup type should be backed up or not\&. This option is useful when the \fBdisklist\fR file is shared among several configurations, some of which should not back up all the listed file systems\&.
-
+Default:
+\fBno\fR. Whether disks associated with this backup type should be backed up or not. This option is useful when the
+\fBdisklist\fR
+file is shared among several configurations, some of which should not back up all the listed file systems.
.TP
\fBinclude\fR [ \fBlist|file\fR ][[optional][ \fBappend\fR ][ \fB string\fR ]+]
-Default: \fBfile\fR "\&."\&. There are two include lists, \fBinclude file\fR and \fBinclude list\&.\fR With \fBinclude file\fR , the \fBstring\fR is a glob expression\&. With \fBinclude list\fR , the \fBstring\fR is a file name on the client containing glob expressions\&.
-
-All include expressions are expanded by \fBAmanda\fR, concatenated in one file and passed to \fBGNU\-tar\fR as a \fB\-\-files\-from\fR argument\&. They must start with "\&./" and contain no other "/"\&.
-
-Include expressions must always be specified as relative to the head directory of the DLE\&.
-
-
-.RS
-.Sh "Note"
+Default:
+\fBfile\fR
+".". There are two include lists,
+\fBinclude file\fR
+and
+\fBinclude list.\fR
+With
+\fBinclude file\fR
+, the
+\fBstring\fR
+is a glob expression. With
+\fBinclude list\fR
+, the
+\fBstring\fR
+is a file name on the client containing glob expressions.
+.sp
+All include expressions are expanded by
+\fBAmanda\fR, concatenated in one file and passed to
+\fBGNU-tar\fR
+as a
+\fB--files-from\fR
+argument. They must start with "./" and contain no other "/".
+.sp
+Include expressions must always be specified as relative to the head directory of the DLE.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
For globbing to work at all, even the limited single level,
-the top level directory of the DLE must be readable by the \fBAmanda\fR user\&.
-.RE
-With the \fBappend\fR keyword, the \fBstring\fR is appended to the current list, without it, the \fBstring\fR overwrites the list\&.
-
-If \fBoptional\fR is specified for \fBinclude list,\fR then amcheck will not complain if the file doesn't exist or is not readable\&.
-
-For \fBinclude list\fR, If the file name is relative, the disk name being backed up is prepended\&.
-
+the top level directory of the DLE must be readable by the \fBAmanda\fR user.With the
+\fBappend\fR
+keyword, the
+\fBstring\fR
+is appended to the current list, without it, the
+\fBstring\fR
+overwrites the list.
+.sp
+If
+\fBoptional\fR
+is specified for
+\fBinclude list,\fR
+then amcheck will not complain if the file doesn't exist or is not readable.
+.sp
+For
+\fBinclude list\fR, If the file name is relative, the disk name being backed up is prepended.
.TP
\fBindex\fR \fB boolean\fR
-Default: \fBno\fR\&. Whether an index (catalogue) of the backup should be generated and saved in \fBindexdir\fR\&. These catalogues are used by the \fBamrecover\fR utility\&.
-
+Default:
+\fBno\fR. Whether an index (catalogue) of the backup should be generated and saved in
+\fBindexdir\fR. These catalogues are used by the
+\fBamrecover\fR
+utility.
.TP
\fBkencrypt\fR \fB boolean\fR
-Default: \fBno\fR\&. Whether the backup image should be encrypted by Kerberos as it is sent across the network from the backup client host to the tape server host\&.
-
+Default:
+\fBno\fR. Whether the backup image should be encrypted by Kerberos as it is sent across the network from the backup client host to the tape server host.
.TP
\fBmaxdumps\fR \fB int\fR
-Default: 1\&. The maximum number of backups from a single host that \fBAmanda\fR will attempt to run in parallel\&. See also the main section parameter \fBinparallel\fR\&.
-
+Default:
+1. The maximum number of backups from a single host that
+\fBAmanda\fR
+will attempt to run in parallel. See also the main section parameter
+\fBinparallel\fR.
.TP
\fBmaxpromoteday\fR \fB int\fR
-Default: 10000\&. The maximum number of day for a promotion, set it 0 if you don't want promotion, set it to 1 or 2 if your disks get overpromoted\&.
-
+Default:
+10000. The maximum number of day for a promotion, set it 0 if you don't want promotion, set it to 1 or 2 if your disks get overpromoted.
.TP
\fBpriority\fR \fB string\fR
-Default: \fBmedium\fR\&. When there is no tape to write to, \fBAmanda\fR will do incremental backups in priority order to the holding disk\&. The priority may be high (2), medium (1), low (0) or a number of your choice\&.
-
+Default:
+\fBmedium\fR. When there is no tape to write to,
+\fBAmanda\fR
+will do incremental backups in priority order to the holding disk. The priority may be high (2), medium (1), low (0) or a number of your choice.
.TP
\fBprogram\fR \fB string\fR
-Default: \fBDUMP\fR\&. The type of backup to perform\&. Valid values are \fBDUMP\fR for the native operating system backup program, and \fBGNUTAR\fR to use \fBGNU\-tar\fR or to do PC backups using Samba\&.
-
+Default:
+\fBDUMP\fR. The type of backup to perform. Valid values are
+\fBDUMP\fR
+for the native operating system backup program, and
+\fBGNUTAR\fR
+to use
+\fBGNU-tar\fR
+or to do PC backups using Samba.
.TP
\fBrecord\fR \fB boolean\fR
-Default: \fByes\fR\&. Whether to ask the backup program to update its database (e\&.g\&. \fI/etc/dumpdates\fR for DUMP or \fI/usr/local/var/amanda/gnutar\-lists\fR for GNUTAR) of time stamps\&. This is normally enabled for daily backups and turned off for periodic archival runs\&.
-
-.TP
-\fBskip\-full\fR \fB boolean\fR
-Default: \fBno\fR\&. If \fBtrue\fR and \fBplanner\fR has scheduled a full backup, these disks will be skipped, and full backups should be run off\-line on these days\&. It was reported that \fBAmanda\fR only schedules level 1 incrementals in this configuration; this is probably a bug\&.
-
+Default:
+\fByes\fR. Whether to ask the backup program to update its database (e.g.
+\fI/etc/dumpdates\fR
+for DUMP or
+\fI/usr/local/var/amanda/gnutar-lists\fR
+for GNUTAR) of time stamps. This is normally enabled for daily backups and turned off for periodic archival runs.
.TP
-\fBskip\-incr\fR \fB boolean\fR
-Default: \fBno\fR\&. If \fBtrue\fR and \fBplanner\fR has scheduled an incremental backup, these disks will be skipped\&.
-
+\fBskip-full\fR \fB boolean\fR
+Default:
+\fBno\fR. If
+\fBtrue\fR
+and
+\fBplanner\fR
+has scheduled a full backup, these disks will be skipped, and full backups should be run off-line on these days. It was reported that
+\fBAmanda\fR
+only schedules level 1 incrementals in this configuration; this is probably a bug.
+.TP
+\fBskip-incr\fR \fB boolean\fR
+Default:
+\fBno\fR. If
+\fBtrue\fR
+and
+\fBplanner\fR
+has scheduled an incremental backup, these disks will be skipped.
.TP
\fBstarttime\fR \fB int\fR
-Default: \fBnone\fR\&. Backups will not start until after this time of day\&. The value should be hh*100+mm, e\&.g\&. 6:30PM (18:30) would be entered as 1830\&.
-
+Default:
+\fBnone\fR. Backups will not start until after this time of day. The value should be hh*100+mm, e.g. 6:30PM (18:30) would be entered as
+1830.
.TP
\fBstrategy\fR \fB string\fR
-Default: \fBstandard\fR\&. Strategy to use when planning what level of backup to run next\&. Values are:
-
+Default:
+\fBstandard\fR. Strategy to use when planning what level of backup to run next. Values are:
.RS
-
.TP
\fBstandard\fR
-The standard \fBAmanda\fR schedule\&.
-
+The standard
+\fBAmanda\fR
+schedule.
.TP
\fBnofull\fR
-Never do full backups, only level 1 incrementals\&.
-
+Never do full backups, only level 1 incrementals.
.TP
\fBnoinc\fR
-Never do incremental backups, only full dumps\&.
-
+Never do incremental backups, only full dumps.
.TP
\fBskip\fR
-Never do backups (useful when sharing the \fBdisklist\fR file)\&.
-
+Never do backups (useful when sharing the
+\fBdisklist\fR
+file).
.TP
\fBincronly\fR
-Only do incremental dumps\&. \fBamadmin force\fR should be used to tell \fBAmanda\fR that a full dump has been performed off\-line, so that it resets to level 1\&. It is similar to skip\-full, but with incronly full dumps may be scheduled manually\&. Unfortunately, it appears that \fBAmanda\fR will perform full backups with this configuration, which is probably a bug\&.
-
+Only do incremental dumps.
+\fBamadmin force\fR
+should be used to tell
+\fBAmanda\fR
+that a full dump has been performed off-line, so that it resets to level 1. It is similar to skip-full, but with incronly full dumps may be scheduled manually. Unfortunately, it appears that
+\fBAmanda\fR
+will perform full backups with this configuration, which is probably a bug.
.RE
-.IP
-
.TP
\fBtape_splitsize\fR \fB int\fR
-Default: \fBnone\fR\&. Split dump file on tape into pieces of a specified size\&. This allows dumps to be spread across multiple tapes, and can potentially make more efficient use of tape space\&. Note that if this value is too large (more than half the size of the average dump being split), substantial tape space can be wasted\&. If too small, large dumps will be split into innumerable tiny dumpfiles, adding to restoration complexity\&. A good rule of thumb, usually, is 1/10 of the size of your tape\&.
-
+Default:
+\fBnone\fR. Split dump file on tape into pieces of a specified size. This allows dumps to be spread across multiple tapes, and can potentially make more efficient use of tape space. Note that if this value is too large (more than half the size of the average dump being split), substantial tape space can be wasted. If too small, large dumps will be split into innumerable tiny dumpfiles, adding to restoration complexity. A good rule of thumb, usually, is 1/10 of the size of your tape.
.TP
\fBsplit_diskbuffer\fR \fB string\fR
-Default: \fBnone\fR\&. When dumping a split dump in PORT\-WRITE mode (usually meaning "no holding disk"), buffer the split chunks to a file in the directory specified by this option\&.
-
+Default:
+\fBnone\fR. When dumping a split dump in PORT-WRITE mode (usually meaning "no holding disk"), buffer the split chunks to a file in the directory specified by this option.
.TP
\fBfallback_splitsize\fR \fB int\fR
-Default: \fB10M\fR\&. When dumping a split dump in PORT\-WRITE mode, if no split_diskbuffer is specified (or if we somehow fail to use our split_diskbuffer), we must buffer split chunks in memory\&. This specifies the maximum size split chunks can be in this scenario, and thus the maximum amount of memory consumed for in\-memory splitting\&. The size of this buffer can be changed from its (very conservative) default to a value reflecting the amount of memory that each taper process on the dump server may reasonably consume\&.
-
+Default:
+\fB10M\fR. When dumping a split dump in PORT-WRITE mode, if no split_diskbuffer is specified (or if we somehow fail to use our split_diskbuffer), we must buffer split chunks in memory. This specifies the maximum size split chunks can be in this scenario, and thus the maximum amount of memory consumed for in-memory splitting. The size of this buffer can be changed from its (very conservative) default to a value reflecting the amount of memory that each taper process on the dump server may reasonably consume.
.PP
-The following \fBdumptype\fR entries are predefined by \fBAmanda\fR:
+The following
+\fBdumptype\fR
+entries are predefined by
+\fBAmanda\fR:
.nf
-define dumptype no\-compress {
+define dumptype no-compress {
compress none
}
-define dumptype compress\-fast {
+define dumptype compress-fast {
compress client fast
}
-define dumptype compress\-best {
+define dumptype compress-best {
compress client best
}
define dumptype srvcompress {
compress server fast
}
-define dumptype bsd\-auth {
+define dumptype bsd-auth {
auth bsd
}
-define dumptype krb4\-auth {
+define dumptype krb4-auth {
auth krb4
}
-define dumptype no\-record {
+define dumptype no-record {
record no
}
-define dumptype no\-hold {
+define dumptype no-hold {
holdingdisk no
}
-define dumptype no\-full {
- skip\-full yes
+define dumptype no-full {
+ skip-full yes
}
.fi
-
.PP
-In addition to options in a \fBdumptype\fR section, one or more other \fBdumptype\fR names may be entered, which make this \fBdumptype\fR inherit options from other previously defined \fBdumptype\fRs\&. For instance, two sections might be the same except for the \fBrecord\fR option:
+In addition to options in a
+\fBdumptype\fR
+section, one or more other
+\fBdumptype\fR
+names may be entered, which make this
+\fBdumptype\fR
+inherit options from other previously defined
+\fBdumptype\fRs. For instance, two sections might be the same except for the
+\fBrecord\fR
+option:
.nf
define dumptype normal {
comment "Normal backup, no compression, do indexing"
- no\-compress
+ no-compress
index yes
maxdumps 2
}
record no
}
.fi
-
.PP
-\fBAmanda\fR provides a \fBdumptype\fR named \fBglobal\fR in the sample \fBamanda\&.conf\fR file that all \fBdumptype\fRs should reference\&. This provides an easy place to make changes that will affect every \fBdumptype\fR\&.
-
+\fBAmanda\fR
+provides a
+\fBdumptype\fR
+named
+\fBglobal\fR
+in the sample
+\fBamanda.conf\fR
+file that all
+\fBdumptype\fRs should reference. This provides an easy place to make changes that will affect every
+\fBdumptype\fR.
.SH "TAPETYPE SECTION"
-
.PP
-The \fBamanda\&.conf\fR file may define multiple types of tape media and devices\&. The information is entered in a \fBtapetype\fR section, which looks like this in the config file:
+The
+\fBamanda.conf\fR
+file may define multiple types of tape media and devices. The information is entered in a
+\fBtapetype\fR
+section, which looks like this in the config file:
.nf
define tapetype \fBname\fR {
- \fBtapetype\-option\fR \fBtapetype\-value\fR
- \&.\&.\&.
+ \fBtapetype-option\fR \fBtapetype-value\fR
+ ...
}
.fi
-
.PP
-\fBName\fR is the name of this type of tape medium/device\&. It is referenced from the \fBtapetype\fR option in the main part of the config file\&.
-
+\fBName\fR
+is the name of this type of tape medium/device. It is referenced from the
+\fBtapetype\fR
+option in the main part of the config file.
.PP
The tapetype options and values are:
-
.TP
\fBcomment\fR \fB string\fR
-Default: \fBnone\fR\&. A comment string describing this set of tape information\&.
-
+Default:
+\fBnone\fR. A comment string describing this set of tape information.
.TP
\fBfilemark\fR \fB int\fR
-Default: \fB1000 bytes\fR\&. How large a file mark (tape mark) is, measured in bytes\&. If the size is only known in some linear measurement (e\&.g\&. inches), convert it to bytes using the device density\&.
-
+Default:
+\fB1000 bytes\fR. How large a file mark (tape mark) is, measured in bytes. If the size is only known in some linear measurement (e.g. inches), convert it to bytes using the device density.
.TP
\fBlength\fR \fB int\fR
-Default: \fB2000 kbytes\fR\&. How much data will fit on a tape\&.
-
-Note that this value is only used by \fBAmanda\fR to schedule which backups will be run\&. Once the backups start, \fBAmanda\fR will continue to write to a tape until it gets an error, regardless of what value is entered for \fBlength\fR (but see the section OUTPUT DRIVERS in the \fBamanda\fR(8) manpage for exceptions)\&.
-
+Default:
+\fB2000 kbytes\fR. How much data will fit on a tape.
+.sp
+Note that this value is only used by
+\fBAmanda\fR
+to schedule which backups will be run. Once the backups start,
+\fBAmanda\fR
+will continue to write to a tape until it gets an error, regardless of what value is entered for
+\fBlength\fR
+(but see the section OUTPUT DRIVERS in the
+\fBamanda\fR(8)
+manpage for exceptions).
.TP
\fBblocksize\fR \fB int\fR
-Default: \fB32\fR\&. How much data will be written in each tape record expressed in KiloBytes\&. The tape record size (= blocksize) can not be reduced below the default 32 KBytes\&. The parameter blocksize can only be raised if \fBAmanda\fR was compiled with the configure option \-\-with\-maxtapeblocksize=N set with "N" greater than 32 during \fBconfigure\fR\&.
-
+Default:
+\fB32\fR. How much data will be written in each tape record expressed in KiloBytes. The tape record size (= blocksize) can not be reduced below the default 32 KBytes. The parameter blocksize can only be raised if
+\fBAmanda\fR
+was compiled with the configure option --with-maxtapeblocksize=N set with "N" greater than 32 during
+\fBconfigure\fR.
.TP
-\fBfile\-pad\fR \fB boolean\fR
-Default: \fBtrue\fR\&. If true, every record, including the last one in the file, will have the same length\&. This matches the way \fBAmanda\fR wrote tapes prior to the availability of this parameter\&. It may also be useful on devices that only support a fixed blocksize\&.
-
-Note that the last record on the tape probably includes trailing null byte padding, which will be passed back to \fBgzip\fR, \fBcompress\fR or the restore program\&. Most programs just ignore this (although possibly with a warning)\&.
-
-If this parameter is false, the last record in a file may be shorter than the block size\&. The file will contain the same amount of data the dump program generated, without trailing null byte padding\&. When read, the same amount of data that was written will be returned\&.
-
+\fBfile-pad\fR \fB boolean\fR
+Default:
+\fBtrue\fR. If true, every record, including the last one in the file, will have the same length. This matches the way
+\fBAmanda\fR
+wrote tapes prior to the availability of this parameter. It may also be useful on devices that only support a fixed blocksize.
+.sp
+Note that the last record on the tape probably includes trailing null byte padding, which will be passed back to
+\fBgzip\fR,
+\fBcompress\fR
+or the restore program. Most programs just ignore this (although possibly with a warning).
+.sp
+If this parameter is false, the last record in a file may be shorter than the block size. The file will contain the same amount of data the dump program generated, without trailing null byte padding. When read, the same amount of data that was written will be returned.
.TP
\fBspeed\fR \fB int\fR
-Default: \fB200 bps\fR\&. How fast the drive will accept data, in bytes per second\&. This parameter is NOT currently used by \fBAmanda\fR\&.
-
-.TP
-\fBlbl\-templ\fR \fB string\fR
-A PostScript template file used by \fBamreport\fR to generate labels\&. Several sample files are provided with the \fBAmanda\fR sources in the \fBexample\fR directory\&. See the \fBamreport\fR(8) man page for more information\&.
-
+Default:
+\fB200 bps\fR. How fast the drive will accept data, in bytes per second. This parameter is NOT currently used by
+\fBAmanda\fR.
+.TP
+\fBlbl-templ\fR \fB string\fR
+A PostScript template file used by
+\fBamreport\fR
+to generate labels. Several sample files are provided with the
+\fBAmanda\fR
+sources in the
+\fBexample\fR
+directory. See the
+\fBamreport\fR(8)
+man page for more information.
.PP
-In addition to options, another \fBtapetype\fR name may be entered, which makes this \fBtapetype\fR inherit options from another \fBtapetype\fR\&. For instance, the only difference between a DLT4000 tape drive using Compact\-III tapes and one using Compact\-IV tapes is the length of the tape\&. So they could be entered as:
+In addition to options, another
+\fBtapetype\fR
+name may be entered, which makes this
+\fBtapetype\fR
+inherit options from another
+\fBtapetype\fR. For instance, the only difference between a DLT4000 tape drive using Compact-III tapes and one using Compact-IV tapes is the length of the tape. So they could be entered as:
.nf
-define tapetype DLT4000\-III {
- comment "DLT4000 tape drives with Compact\-III tapes"
+define tapetype DLT4000-III {
+ comment "DLT4000 tape drives with Compact-III tapes"
length 12500 mbytes # 10 Gig tapes with some compression
filemark 2000 kbytes
speed 1536 kps
}
-define tapetype DLT4000\-IV {
- DLT4000\-III
- comment "DLT4000 tape drives with Compact\-IV tapes"
+define tapetype DLT4000-IV {
+ DLT4000-III
+ comment "DLT4000 tape drives with Compact-IV tapes"
length 25000 mbytes # 20 Gig tapes with some compression
}
.fi
-
.SH "INTERFACE SECTION"
-
.PP
-The \fBamanda\&.conf\fR file may define multiple types of network interfaces\&. The information is entered in an \fBinterface\fR section, which looks like this:
+The
+\fBamanda.conf\fR
+file may define multiple types of network interfaces. The information is entered in an
+\fBinterface\fR
+section, which looks like this:
.nf
define interface \fBname\fR {
- \fBinterface\-option\fR \fBinterface\-value\fR
- \&.\&.\&.
+ \fBinterface-option\fR \fBinterface-value\fR
+ ...
}
.fi
-
.PP
-\fBname\fR is the name of this type of network interface\&. It is referenced from the \fBdisklist\fR file\&.
-
+\fBname\fR
+is the name of this type of network interface. It is referenced from the
+\fBdisklist\fR
+file.
.PP
-Note that these sections define network interface characteristics, not the actual interface that will be used\&. Nor do they impose limits on the bandwidth that will actually be taken up by \fBAmanda\fR\&. \fBAmanda\fR computes the estimated bandwidth each file system backup will take based on the estimated size and time, then compares that plus any other running backups with the limit as another of the criteria when deciding whether to start the backup\&. Once a backup starts, \fBAmanda\fR will use as much of the network as it can leaving throttling up to the operating system and network hardware\&.
-
+Note that these sections define network interface characteristics, not the actual interface that will be used. Nor do they impose limits on the bandwidth that will actually be taken up by
+\fBAmanda\fR.
+\fBAmanda\fR
+computes the estimated bandwidth each file system backup will take based on the estimated size and time, then compares that plus any other running backups with the limit as another of the criteria when deciding whether to start the backup. Once a backup starts,
+\fBAmanda\fR
+will use as much of the network as it can leaving throttling up to the operating system and network hardware.
.PP
The interface options and values are:
-
.TP
\fBcomment\fR \fB string\fR
-Default: \fBnone\fR\&. A comment string describing this set of network information\&.
-
+Default:
+\fBnone\fR. A comment string describing this set of network information.
.TP
\fBuse\fR \fB int\fR
-Default: \fB300 Kbps\fR\&. The speed of the interface in Kbytes per second\&.
-
+Default:
+\fB300 Kbps\fR. The speed of the interface in Kbytes per second.
.PP
-In addition to options, another \fBinterface\fR name may be entered, which makes this \fBinterface\fR inherit options from another \fBinterface\fR\&. At the moment, this is of little use\&.
-
+In addition to options, another
+\fBinterface\fR
+name may be entered, which makes this
+\fBinterface\fR
+inherit options from another
+\fBinterface\fR. At the moment, this is of little use.
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org>: Original text
-
+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, splitting
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion, major update, splitting
.SH "SEE ALSO"
-
.PP
- \fBamanda\fR(8), \fBamcrypt\fR(8), \fBaespipe\fR(1),
+\fBamanda\fR(8),
+\fBamcrypt\fR(8),
+\fBaespipe\fR(1),
.IP "\\$1" \\$2
..
.TH "AMCHECK" 8 "" "" ""
-.SH NAME
-amcheck \- run Amanda self-checks
+.SH "NAME"
+amcheck - run Amanda self-checks
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 8
-\fBamcheck\fR [\-mwsclt] [\-Maddress] \fIconfig\fR [\fIhost\fR\ [\fIdisk\fR...]...]
-.ad
-.hy
-
+\fBamcheck\fR [-mwsclt] [-Maddress] \fIconfig\fR [\fIhost\fRÂ [\fIdisk\fR...]...]
.SH "DESCRIPTION"
-
.PP
-\fBAmcheck\fR runs a number of self\-checks on both the \fBAmanda\fR tape server host and the \fBAmanda\fR client hosts\&.
-
+\fBAmcheck\fR
+runs a number of self-checks on both the
+\fBAmanda\fR
+tape server host and the
+\fBAmanda\fR
+client hosts.
.PP
-On the tape server host, \fBamcheck\fR can go through the same tape checking used at the start of the nightly \fBamdump\fR run to verify the correct tape for the next run is mounted\&.
-
+On the tape server host,
+\fBamcheck\fR
+can go through the same tape checking used at the start of the nightly
+\fBamdump\fR
+run to verify the correct tape for the next run is mounted.
.PP
-\fBAmcheck\fR can also do a self\-check on all client hosts to make sure each host is running and that permissions on filesystems to be backed up are correct\&.
-
+\fBAmcheck\fR
+can also do a self-check on all client hosts to make sure each host is running and that permissions on filesystems to be backed up are correct.
.PP
-You can specify many host/disk expressions, only disks that match an expression will be checked\&. All disks are checked if no expressions are given\&.
-
+You can specify many host/disk expressions, only disks that match an expression will be checked. All disks are checked if no expressions are given.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "OPTIONS"
-
-.TP
-\fB\-s\fR
-Run the tape server local and tape checks (same as \fB\-lt\fR)\&.
-
-.TP
-\fB\-c\fR
-Run the client host checks\&.
-
-.TP
-\fB\-l\fR
-Run the local tests (e\&.g\&. permissions) on the server host\&.
-
.TP
-\fB\-t\fR
-Run the tape tests on the server host\&.
-
-.TP
-\fB\-w\fR
-Enables a DESTRUCTIVE check for write\-protection on the tape (which would otherwise cause the subsequent \fBamdump\fR to fail)\&. If the tape is writable, this check causes all data after the tape label to be erased\&. If the label_new_tapes option is enabled, this check may ERASE any non\-Amanda tape in the drive or changer\&. The check implies \fB\-t\fR and is only made if the tape is otherwise correct\&.
-
-.TP
-\fB\-m\fR
-Nothing is printed, but mail is sent if any errors are detected\&. The mail goes to the \fBmailto\fR address specified in the \fBamanda\&.conf\fR file or the \fBaddress\fR value if \fB\-M\fR is set\&.
-
-.TP
-\fB\-a\fR
-Like \fB\-m\fR but the mail is always sent\&.
-
-.TP
-\fB\-M\fR\fIaddress\fR
-Mail the report to \fBaddress\fR instead of the \fBmailto\fR value from \fBamanda\&.conf\fR\&. Implies \fB\-m\fR\&.
-
+\fB-s\fR
+Run the tape server local and tape checks (same as
+\fB-lt\fR).
+.TP
+\fB-c\fR
+Run the client host checks.
+.TP
+\fB-l\fR
+Run the local tests (e.g. permissions) on the server host.
+.TP
+\fB-t\fR
+Run the tape tests on the server host.
+.TP
+\fB-w\fR
+Enables a DESTRUCTIVE check for write-protection on the tape (which would otherwise cause the subsequent
+\fBamdump\fR
+to fail). If the tape is writable, this check causes all data after the tape label to be erased. If the label_new_tapes option is enabled, this check may ERASE any non-Amanda tape in the drive or changer. The check implies
+\fB-t\fR
+and is only made if the tape is otherwise correct.
+.TP
+\fB-m\fR
+Nothing is printed, but mail is sent if any errors are detected. The mail goes to the
+\fBmailto\fR
+address specified in the
+\fBamanda.conf\fR
+file or the
+\fBaddress\fR
+value if
+\fB-M\fR
+is set.
+.TP
+\fB-a\fR
+Like
+\fB-m\fR
+but the mail is always sent.
+.TP
+\fB-M\fR\fIaddress\fR
+Mail the report to
+\fBaddress\fR
+instead of the
+\fBmailto\fR
+value from
+\fBamanda.conf\fR. Implies
+\fB-m\fR.
.PP
-The default is \fB\-cs\fR\&.
-
+The default is
+\fB-cs\fR.
.SH "EXAMPLES"
-
.PP
-In this example, both the tape server and client tests are run\&. The results are displayed on standard output\&.
+In this example, both the tape server and client tests are run. The results are displayed on standard output.
.nf
% amcheck daily
\fBAmanda\fR Tape Server Host Check
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-/amanda2/amanda/work: 911475 KB disk space available, that's plenty\&.
-NOTE: skipping tape\-writable test\&.
-Tape VOL10 label ok\&.
-Server check took 34\&.966 seconds\&.
+-----------------------------
+/amanda2/amanda/work: 911475 KB disk space available, that's plenty.
+NOTE: skipping tape-writable test.
+Tape VOL10 label ok.
+Server check took 34.966 seconds.
\fBAmanda\fR Backup Client Hosts Check
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-WARNING: northstar: selfcheck request timed out\&. Host down?
-WARNING: drinkme: selfcheck request timed out\&. Host down?
-WARNING: scruffy: selfcheck request timed out\&. Host down?
-Client check: 136 hosts checked in 51\&.945 seconds, 3 problems found\&.
+--------------------------------
+WARNING: northstar: selfcheck request timed out. Host down?
+WARNING: drinkme: selfcheck request timed out. Host down?
+WARNING: scruffy: selfcheck request timed out. Host down?
+Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
-(brought to you by \fBAmanda\fR 2\&.5\&.0)
+(brought to you by \fBAmanda\fR 2.5.0)
.fi
-
.PP
-In this example, if the line \fBmailto csd\-amanda\fR is in \fBamanda\&.conf\fR, mail will be sent to \fBcsd\-amanda\fR if the server check returns an error\&.
+In this example, if the line
+\fBmailto csd-amanda\fR
+is in
+\fBamanda.conf\fR, mail will be sent to
+\fBcsd-amanda\fR
+if the server check returns an error.
.nf
-% amcheck \-s \-m daily
+% amcheck -s -m daily
.fi
-
.SH "MESSAGES"
-
.TP
fatal slot \fBslot\fR: \fBerror message\fR
-(error) The tape changer detected some kind of fatal error while trying to load slot \fBslot\fR\&.
-
+(error) The tape changer detected some kind of fatal error while trying to load slot
+\fBslot\fR.
.TP
slot \fBslot\fR: \fBerror message\fR
-(warning) The tape changer detected some kind of non\-fatal error (e\&.g\&. an empty slot was detected) while trying to load slot \fBslot\fR, or an error was detected trying to read the tape label\&.
-
+(warning) The tape changer detected some kind of non-fatal error (e.g. an empty slot was detected) while trying to load slot
+\fBslot\fR, or an error was detected trying to read the tape label.
.TP
slot \fBslot\fR: date \fBYYYYMMDD\fR label \fBlabel\fR (\fBresult\fR)
-(info) Tape \fBlabel\fR in slot \fBslot\fR was loaded and found to have been last written on \fBYYYYMMDD\fR\&. If the tape is new, the date field will be an \fBX\fR\&. The \fBresult\fR may be one of:
-
+(info) Tape
+\fBlabel\fR
+in slot
+\fBslot\fR
+was loaded and found to have been last written on
+\fBYYYYMMDD\fR. If the tape is new, the date field will be an
+\fBX\fR. The
+\fBresult\fR
+may be one of:
.RS
-
.TP
exact label match
-This is the expected tape\&.
-
+This is the expected tape.
.TP
no match
-This label does not match the \fBlabelstr\fR pattern in \fBamanda\&.conf\fR\&. Tape scanning will continue\&.
-
+This label does not match the
+\fBlabelstr\fR
+pattern in
+\fBamanda.conf\fR. Tape scanning will continue.
.TP
active tape
-This tape is still active and cannot be overwritten\&. Tape scanning will continue\&.
-
+This tape is still active and cannot be overwritten. Tape scanning will continue.
.TP
first labelstr match
-This tape is the first one that matches the \fBlabelstr\fR pattern in \fBamanda\&.conf\fR\&. Tape scanning will continue if necessary\&.
-
+This tape is the first one that matches the
+\fBlabelstr\fR
+pattern in
+\fBamanda.conf\fR. Tape scanning will continue if necessary.
.TP
labelstr match
-This tape is the next one that matches the \fBlabelstr\fR pattern in \fBamanda\&.conf\fR\&. Tape scanning will continue\&.
-
+This tape is the next one that matches the
+\fBlabelstr\fR
+pattern in
+\fBamanda.conf\fR. Tape scanning will continue.
.RE
.IP
-
.TP
ERROR: cannot look up dump user \fBuser\fR
-(error) Dump user \fBuser\fR from \fBamanda\&.conf\fR could not be found in the system password information\&.
-
+(error) Dump user
+\fBuser\fR
+from
+\fBamanda.conf\fR
+could not be found in the system password information.
.TP
ERROR: cannot look up my own uid (\fBuid\fR)
-(error) User id \fBuid\fR running \fBamcheck\fR could not be found in the system password information\&.
-
+(error) User id
+\fBuid\fR
+running
+\fBamcheck\fR
+could not be found in the system password information.
.TP
ERROR: running as user \fBrunuser\fR instead of \fBdumpuser\fR
-(error) \fBAmcheck\fR should be run as the dump user \fBdumpuser\fR from \fBamanda\&.conf\fR instead of \fBrunuser\fR\&.
-
+(error)
+\fBAmcheck\fR
+should be run as the dump user
+\fBdumpuser\fR
+from
+\fBamanda.conf\fR
+instead of
+\fBrunuser\fR.
.TP
ERROR: program dir \fBdirectory\fR: not accessible
-(error) The directory \fBAmanda\fR expects to find its auxiliary programs in, \fBdirectory\fR, is not accessible\&.
-
+(error) The directory
+\fBAmanda\fR
+expects to find its auxiliary programs in,
+\fBdirectory\fR, is not accessible.
.TP
ERROR: program \fBprogram\fR: does not exist
-(error) Program \fBprogram\fR needed on the tape server could not be found\&.
-
+(error) Program
+\fBprogram\fR
+needed on the tape server could not be found.
.TP
ERROR: program \fBprogram\fR: not a file
-(error) Program \fBprogram\fR needed on the tape server exists but is not a file\&.
-
+(error) Program
+\fBprogram\fR
+needed on the tape server exists but is not a file.
.TP
ERROR: program \fBprogram\fR: not executable
-(error) Program \fBprogram\fR needed on the tape server exists but is not executable\&.
-
+(error) Program
+\fBprogram\fR
+needed on the tape server exists but is not executable.
.TP
-WARNING: program \fBprogram\fR: not setuid\-root
-(warning) Program \fBprogram\fR needed on the tape server exists but should be owned by user "root" and setuid\&.
-
+WARNING: program \fBprogram\fR: not setuid-root
+(warning) Program
+\fBprogram\fR
+needed on the tape server exists but should be owned by user "root" and setuid.
.TP
ERROR: \fBXXX\fR dir \fBdirectory\fR: not writable
-(error) Directory \fBdirectory\fR is either not writable, i\&.e\&. the dump user will not be able to create or remove files, or cannot be accessed, perhaps because a parent directory does not allow search permission\&. The \fBXXX\fR may be:
-
+(error) Directory
+\fBdirectory\fR
+is either not writable, i.e. the dump user will not be able to create or remove files, or cannot be accessed, perhaps because a parent directory does not allow search permission. The
+\fBXXX\fR
+may be:
.RS
-
.TP
log
-for the \fBAmanda\fR log directory (see \fBlogdir\fR in \fBamanda\&.conf\fR)
-
+for the
+\fBAmanda\fR
+log directory (see
+\fBlogdir\fR
+in
+\fBamanda.conf\fR)
.TP
oldlog
-for the directory that holds the old log files (see \fBlogdir\fR in \fBamanda\&.conf\fR)
-
+for the directory that holds the old log files (see
+\fBlogdir\fR
+in
+\fBamanda.conf\fR)
.TP
info
-for an \fBAmanda\fR database information directory (see \fBcurinfo\fR in \fBamanda\&.conf\fR) or
-
+for an
+\fBAmanda\fR
+database information directory (see
+\fBcurinfo\fR
+in
+\fBamanda.conf\fR) or
.TP
index
-for an \fBAmanda\fR index directory (see \fBindexdir\fR in \fBamanda\&.conf\fR)
-
+for an
+\fBAmanda\fR
+index directory (see
+\fBindexdir\fR
+in
+\fBamanda.conf\fR)
.TP
tapelist
-for the \fBAmanda\fR tapelist directory (see \fBtapelist\fR in \fBamanda\&.conf\fR)
-
+for the
+\fBAmanda\fR
+tapelist directory (see
+\fBtapelist\fR
+in
+\fBamanda.conf\fR)
.RE
.IP
-
.TP
NOTE: \fBXXX\fR dir \fBdirectory\fR: does not exist
-(info) A database (info) or index directory does not exist or cannot be accessed\&. This might just mean this is a new client or disk, but if that is not the case, this should be treated as an error\&.
-
+(info) A database (info) or index directory does not exist or cannot be accessed. This might just mean this is a new client or disk, but if that is not the case, this should be treated as an error.
.TP
NOTE: it will be created on the next run
-(info) This indicates the info directory listed in the previous message will be created on the next run\&.
-
+(info) This indicates the info directory listed in the previous message will be created on the next run.
.TP
ERROR: \fBXXX\fR dir \fBname\fR: not a directory
-(error) \fBAmcheck\fR expected \fBname\fR to be a directory, but it is something else (e\&.g\&. file)\&.
-
+(error)
+\fBAmcheck\fR
+expected
+\fBname\fR
+to be a directory, but it is something else (e.g. file).
.TP
WARNING: info file \fIfile\fR: does not exist
-(warning) File \fBfile\fR does not exist in the text format database\&. Since the parent directories do exist, the file should already have been created\&.
-
+(warning) File
+\fBfile\fR
+does not exist in the text format database. Since the parent directories do exist, the file should already have been created.
.TP
ERROR: info file \fIname\fR: not a file
-(error) \fBAmcheck\fR expected \fBname\fR to be a file, but it is something else (e\&.g\&. file)\&.
-
+(error)
+\fBAmcheck\fR
+expected
+\fBname\fR
+to be a file, but it is something else (e.g. file).
.TP
ERROR: info file \fIfile\fR: not readable
-(error) The text format database file \fBfile\fR is not readable\&.
-
+(error) The text format database file
+\fBfile\fR
+is not readable.
.TP
ERROR: log file \fIfile\fR: not writable
-(error) Log file \fBfile\fR (file \fBlog\fR in \fBlogdir\fR from \fBamanda\&.conf\fR) is either not writable, or cannot be accessed, perhaps because a parent directory does not allow search permission\&.
-
+(error) Log file
+\fBfile\fR
+(file
+\fBlog\fR
+in
+\fBlogdir\fR
+from
+\fBamanda.conf\fR) is either not writable, or cannot be accessed, perhaps because a parent directory does not allow search permission.
.TP
ERROR: tape list \fBtapelist\fR: not writable
-(error) \fBAmanda\fR tape list file \fBtapelist\fR (see \fBtapelist\fR in \fBamanda\&.conf\fR) is not writable or was not found\&.
-
+(error)
+\fBAmanda\fR
+tape list file
+\fBtapelist\fR
+(see
+\fBtapelist\fR
+in
+\fBamanda.conf\fR) is not writable or was not found.
.TP
ERROR: tape list \fBtapelist\fR: parse error
-(error) \fBAmanda\fR tape list file \fBtapelist\fR (see \fBtapelist\fR in \fBamanda\&.conf\fR) could not be read or parsed\&.
-
+(error)
+\fBAmanda\fR
+tape list file
+\fBtapelist\fR
+(see
+\fBtapelist\fR
+in
+\fBamanda.conf\fR) could not be read or parsed.
.TP
WARNING: tapedev is /dev/null, dumps will be thrown away
-(warning) The \fBtapedev\fR parameter in \fBamanda\&.conf\fR is set to \fI/dev/null\fR and \fBAmanda\fR uses that when debugging to throw all the dump images away\&.
-
+(warning) The
+\fBtapedev\fR
+parameter in
+\fBamanda.conf\fR
+is set to
+\fI/dev/null\fR
+and
+\fBAmanda\fR
+uses that when debugging to throw all the dump images away.
.TP
WARNING: hold file \fIfile\fR exists
-(info) Hold file \fBfile\fR exists and will cause \fBamdump\fR to pause at the beginning until it is removed\&.
-
+(info) Hold file
+\fBfile\fR
+exists and will cause
+\fBamdump\fR
+to pause at the beginning until it is removed.
.TP
ERROR: holding disk \fBdisk\fR: statfs: \fBerror message\fR
-(error) An error was returned from the \fBstatfs\fR system call on holding disk \fBdisk\fR (maybe because it does not exist)\&.
-
+(error) An error was returned from the
+\fBstatfs\fR
+system call on holding disk
+\fBdisk\fR
+(maybe because it does not exist).
.TP
ERROR: holding disk \fBdisk\fR: not writable
-(error) Holding disk \fBdisk\fR, is not writable, probably because the caller does not have write permission or a parent directory does not allow search permission\&.
-
-.TP
-WARNING: holding disk \fBdisk\fR: available space unknown \fBN\fR KB requested\&.
-(warning) \fBAmcheck\fR could not determine the amount of available space on holding disk \fBdisk\fR to see if there were at least \fBN\fR KBytes available\&.
-
-.TP
-WARNING: holding disk \fBdisk\fR: only \fBF\fR KB free (\fBR\fR KB requested)\&.
-(warning) \fBamanda\&.conf\fR requested \fBR\fR KBytes of free space on holding disk \fBdisk\fR, but only \fBF\fR KBytes were available\&. 10 MBytes is subtracted for each backup process (see the \fBinparallel\fR \fBamanda\&.conf\fR option) to allow for unexpected overruns\&.
-
-.RS
-.Sh "Note"
-Even though this message is listed as a warning, it causes \fBamcheck\fR to exit with a non\-zero status\&.
-.RE
-
-.TP
-Holding disk \fBdisk\fR: \fBN\fR KB disk space available, that's plenty\&.
-(info) There was sufficient free space on holding disk \fBdisk\fR\&.
-
+(error) Holding disk
+\fBdisk\fR, is not writable, probably because the caller does not have write permission or a parent directory does not allow search permission.
+.TP
+WARNING: holding disk \fBdisk\fR: available space unknown \fBN\fR KB requested.
+(warning)
+\fBAmcheck\fR
+could not determine the amount of available space on holding disk
+\fBdisk\fR
+to see if there were at least
+\fBN\fR
+KBytes available.
+.TP
+WARNING: holding disk \fBdisk\fR: only \fBF\fR KB free (\fBR\fR KB requested).
+(warning)
+\fBamanda.conf\fR
+requested
+\fBR\fR
+KBytes of free space on holding disk
+\fBdisk\fR, but only
+\fBF\fR
+KBytes were available. 10 MBytes is subtracted for each backup process (see the
+\fBinparallel\fR\fBamanda.conf\fR
+option) to allow for unexpected overruns.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+Even though this message is listed as a warning, it causes \fBamcheck\fR to exit with a non-zero status..TP
+Holding disk \fBdisk\fR: \fBN\fR KB disk space available, that's plenty.
+(info) There was sufficient free space on holding disk
+\fBdisk\fR.
.TP
WARNING: holding disk \fBdisk\fR: only \fBF\fR KB free, using nothing
-(warning) Holding disk \fBdisk\fR has \fBF\fR KBytes of free space, but that is not enough for what is requested in \fBamanda\&.conf\fR\&.
-
+(warning) Holding disk
+\fBdisk\fR
+has
+\fBF\fR
+KBytes of free space, but that is not enough for what is requested in
+\fBamanda.conf\fR.
.TP
Holding disk \fBdisk\fR: \fBF\fR KB disk space available, using \fBU\fR KB
-(info) Holding disk \fBdisk\fR has \fBF\fR KBytes of free space and \fBAmanda\fR will be using up to \fBU\fR Kbytes\&.
-
-.TP
-WARNING: if a tape changer is not available, runtapes must be set to 1\&.
-(warning) The \fBruntapes\fR \fBamanda\&.conf\fR option must be set to 1 if the \fBtpchanger\fR \fBamanda\&.conf\fR option is not set\&.
-
-.TP
-ERROR: \fBerror message\fR\&.
-(error) An error was detected while initializing the tape changer\&.
-
-.TP
-ERROR: \fBtape device\fR: \fBerror message\fR\&.
-(error) An error was detected while processing the tape label\&.
-
-.TP
-ERROR: cannot overwrite active tape \fBlabel\fR\&.
-(error) Tape \fBlabel\fR is still active and cannot be used\&.
-
-.TP
-ERROR: label \fBlabel\fR doesn't match labelstr \fBpattern\fR \&.
-(error) The label on tape \fBlabel\fR does not match the \fBlabelstr\fR \fBamanda\&.conf\fR option\&.
-
+(info) Holding disk
+\fBdisk\fR
+has
+\fBF\fR
+KBytes of free space and
+\fBAmanda\fR
+will be using up to
+\fBU\fR
+Kbytes.
+.TP
+WARNING: if a tape changer is not available, runtapes must be set to 1.
+(warning) The
+\fBruntapes\fR\fBamanda.conf\fR
+option must be set to 1 if the
+\fBtpchanger\fR\fBamanda.conf\fR
+option is not set.
+.TP
+ERROR: \fBerror message\fR.
+(error) An error was detected while initializing the tape changer.
+.TP
+ERROR: \fBtape device\fR: \fBerror message\fR.
+(error) An error was detected while processing the tape label.
+.TP
+ERROR: cannot overwrite active tape \fBlabel\fR.
+(error) Tape
+\fBlabel\fR
+is still active and cannot be used.
+.TP
+ERROR: label \fBlabel\fR doesn't match labelstr \fBpattern\fR .
+(error) The label on tape
+\fBlabel\fR
+does not match the
+\fBlabelstr\fR\fBamanda.conf\fR
+option.
.TP
(expecting a new tape)
-(info) The tape is not OK and a new tape was expected\&.
-
+(info) The tape is not OK and a new tape was expected.
.TP
(expecting tape \fBlabel\fR or a new tape)
-(info) The tape is not OK and either tape \fBlabel\fR or a new tape was expected\&.
-
+(info) The tape is not OK and either tape
+\fBlabel\fR
+or a new tape was expected.
.TP
-ERROR: tape \fBlabel\fR label ok, but is not writable\&.
-(error) Tape \fBlabel\fR is OK, but the write enable test failed\&.
-
+ERROR: tape \fBlabel\fR label ok, but is not writable.
+(error) Tape
+\fBlabel\fR
+is OK, but the write enable test failed.
.TP
-Tape \fBlabel\fR is writable\&.
-(info) Tape \fBlabel\fR is OK and the write enable test succeeded\&.
-
+Tape \fBlabel\fR is writable.
+(info) Tape
+\fBlabel\fR
+is OK and the write enable test succeeded.
.TP
-NOTE: skipping tape\-writable test\&.
-(info) The tape write test (see the \fB\-w\fR option) was not enabled\&.
-
+NOTE: skipping tape-writable test.
+(info) The tape write test (see the
+\fB-w\fR
+option) was not enabled.
.TP
WARNING: skipping tape test because amdump or amflush seem to be running, WARNING: if they are not, you must run amcleanup
-(warning) It looked to \fBamcheck\fR like either \fBamdump\fR or \fBamflush\fR were running because a log file or amdump file exists\&. If they are not running, you probably need to run \fBamcleanup\fR to clear up a previous failure\&. Otherwise, you need to wait until they complete before running \fBamcheck\fR\&.
-
+(warning) It looked to
+\fBamcheck\fR
+like either
+\fBamdump\fR
+or
+\fBamflush\fR
+were running because a log file or amdump file exists. If they are not running, you probably need to run
+\fBamcleanup\fR
+to clear up a previous failure. Otherwise, you need to wait until they complete before running
+\fBamcheck\fR.
.TP
NOTE: skipping tape checks
-(info) The tape tests are being skipped because you used the \fB\-t\fR command line option\&.
-
+(info) The tape tests are being skipped because you used the
+\fB-t\fR
+command line option.
.TP
-WARNING: \fBcompress\fR is not executable, server\-compression and indexing will not work
-(warning) Compression program \fBcompress\fR is not executable, so compression on the tape server host and creating index files will not work\&.
-
+WARNING: \fBcompress\fR is not executable, server-compression and indexing will not work
+(warning) Compression program
+\fBcompress\fR
+is not executable, so compression on the tape server host and creating index files will not work.
.TP
-Tape \fBlabel\fR label ok\&.
-(info) Tape \fBlabel\fR is OK for the next run\&.
-
+Tape \fBlabel\fR label ok.
+(info) Tape
+\fBlabel\fR
+is OK for the next run.
.TP
-Server check took \fBS\fR seconds\&.
-(info) Reports how long the tape server host checks took\&.
-
+Server check took \fBS\fR seconds.
+(info) Reports how long the tape server host checks took.
.TP
ERROR: \fBhost\fR: could not resolve hostname
-(error) Could not look up client hostname \fBhost\fR\&.
-
+(error) Could not look up client hostname
+\fBhost\fR.
.TP
-Client check: \fBH\fR hosts checked in \fBS\fR seconds, \fBN\fR problems found\&.
-(info) Reports the number of client hosts checked, how long it took and the number of errors detected\&.
-
+Client check: \fBH\fR hosts checked in \fBS\fR seconds, \fBN\fR problems found.
+(info) Reports the number of client hosts checked, how long it took and the number of errors detected.
.TP
-WARNING: \fBhost\fR: selfcheck request timed out\&. Host down?
-(warning) There was no response from \fBhost\fR when trying to do the client checks\&. The host might really be down or it might not be configured properly\&.
-
+WARNING: \fBhost\fR: selfcheck request timed out. Host down?
+(warning) There was no response from
+\fBhost\fR
+when trying to do the client checks. The host might really be down or it might not be configured properly.
.TP
ERROR: \fBhost\fR NAK: \fBmessage\fR
-(error) \fBHost\fR reported a negative acknowledgment error of \fBmessage\fR to the status check request\&.
-
+(error)
+\fBHost\fR
+reported a negative acknowledgment error of
+\fBmessage\fR
+to the status check request.
.TP
ERROR: \fBhost\fR NAK: [NAK parse failed]
-(error) \fBAmcheck\fR could not parse the negative acknowledgment error from \fBhost\fR\&. There might be an \fBAmanda\fR version mismatch between the host running \fBamcheck\fR and \fBhost\fR\&.
-
-.TP
-ERROR: \fBhost\fR [mutual\-authentication failed]
-(error) Kerberos authentication failed while contacting \fBhost\fR\&.
-
+(error)
+\fBAmcheck\fR
+could not parse the negative acknowledgment error from
+\fBhost\fR. There might be an
+\fBAmanda\fR
+version mismatch between the host running
+\fBamcheck\fR
+and
+\fBhost\fR.
+.TP
+ERROR: \fBhost\fR [mutual-authentication failed]
+(error) Kerberos authentication failed while contacting
+\fBhost\fR.
.TP
ERROR: \fBhost\fR: \fBmessage\fR
-(error) Error \fBmessage\fR was reported by the status check on \fBhost\fR\&.
-
+(error) Error
+\fBmessage\fR
+was reported by the status check on
+\fBhost\fR.
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org> : Original text
-
+James da Silva,
+<jds@amanda.org>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamdump\fR(8)
+\fBamanda\fR(8),
+\fBamdump\fR(8)
.IP "\\$1" \\$2
..
.TH "AMCHECKDB" 8 "" "" ""
-.SH NAME
-amcheckdb \- check Amanda database for tape consistency
+.SH "NAME"
+amcheckdb - check Amanda database for tape consistency
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 10
\fBamcheckdb\fR \fIconfig\fR
-.ad
-.hy
-
.SH "DESCRIPTION"
-
.PP
-\fBAmcheckdb\fR verifies that every tape mentioned in the \fBAmanda\fR database is still valid in the \fBtapelist\fR file\&.
-
+\fBAmcheckdb\fR
+verifies that every tape mentioned in the
+\fBAmanda\fR
+database is still valid in the
+\fBtapelist\fR
+file.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "EXAMPLE"
-
.PP
This shows a normal response:
.nf
# amcheckdb daily
-Ready\&.
+Ready.
.fi
-
.PP
-This shows tape \fBDMP014\fR is still listed in the database but is no longer listed in the \fBtapelist\fR file:
+This shows tape
+\fBDMP014\fR
+is still listed in the database but is no longer listed in the
+\fBtapelist\fR
+file:
.nf
# amcheckdb daily
Tape DMP014 missing in /usr/local/etc/amanda//daily/tapelist
-Ready\&.
+Ready.
.fi
-
.SH "AUTHOR"
-
.PP
-Adrian T\&. Filipi\-Martin <atf3r@cs\&.virginia\&.edu>: Original text
-
+Adrian T. Filipi-Martin <atf3r@cs.virginia.edu>: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamadmin\fR(8), \fBamrmtape\fR(8), \fBamanda\fR(8)
+\fBamadmin\fR(8),
+\fBamrmtape\fR(8),
+\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMCLEANUP" 8 "" "" ""
-.SH NAME
-amcleanup \- run the Amanda cleanup process after a failure
+.SH "NAME"
+amcleanup - run the Amanda cleanup process after a failure
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 10
\fBamcleanup\fR \fIconfig\fR
-.ad
-.hy
-
.SH "DESCRIPTION"
-
.PP
-\fBAmcleanup\fR generates the \fB\fBAmanda\fR Mail Report\fR and updates the \fBAmanda\fR databases after a system failure on a tape server host\&. This cleanup process is normally done automatically as part of the \fBamdump\fR program, but if \fBamdump\fR cannot complete for some reason (usually because of a tape server host crash), \fBamcleanup\fR must be run some time later (usually during system boot)\&.
-
+\fBAmcleanup\fR
+generates the
+\fB\fBAmanda\fR Mail Report\fR
+and updates the
+\fBAmanda\fR
+databases after a system failure on a tape server host. This cleanup process is normally done automatically as part of the
+\fBamdump\fR
+program, but if
+\fBamdump\fR
+cannot complete for some reason (usually because of a tape server host crash),
+\fBamcleanup\fR
+must be run some time later (usually during system boot).
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "EXAMPLES"
-
.PP
-This example runs the \fBAmanda\fR cleanup process by hand after a failure\&.
+This example runs the
+\fBAmanda\fR
+cleanup process by hand after a failure.
.nf
% amcleanup daily
.fi
-
.PP
-Putting the following line in a system boot script (e\&.g\&. \fI/etc/rc\&.local\fR) runs the \fBAmanda\fR cleanup process as part of the reboot, eliminating the need to run it by hand\&.
+Putting the following line in a system boot script (e.g.
+\fI/etc/rc.local\fR) runs the
+\fBAmanda\fR
+cleanup process as part of the reboot, eliminating the need to run it by hand.
.nf
/usr/local/sbin/amcleanup daily
.fi
-
.PP
-If nothing needs to be done, \fBamcleanup\fR exits normally with the message:
+If nothing needs to be done,
+\fBamcleanup\fR
+exits normally with the message:
.nf
-amcleanup: no unprocessed logfile to clean up\&.
+amcleanup: no unprocessed logfile to clean up.
.fi
-
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org>: Original text
-
+James da Silva,
+<jds@amanda.org>: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamdump\fR(8)
+\fBamanda\fR(8),
+\fBamdump\fR(8)
.IP "\\$1" \\$2
..
.TH "AMCRYPT" 8 "" "" ""
-.SH NAME
-amcrypt \- reference crypt program for Amanda symmetric data encryption
+.SH "NAME"
+amcrypt - reference crypt program for Amanda symmetric data encryption
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 8
\fBamcrypt\fR
-.ad
-.hy
-
.SH "DESCRIPTION"
-
.PP
- \fBamcrypt\fR requires \fBaespipe\fR and \fBgpg\fR to work\&. Aespipe is available from : http://loop-aes.sourceforge.net
-
+\fBamcrypt\fR
+requires
+\fBaespipe\fR
+and
+\fBgpg\fR
+to work. Aespipe is available from
+: http://loop-aes.sourceforge.net
.PP
- \fBamcrypt\fR will search for the aespipe program in the following directories: /usr/bin:/usr/local/bin:/sbin:/usr/sbin\&.
+\fBamcrypt\fR
+will search for the aespipe program in the following directories: /usr/bin:/usr/local/bin:/sbin:/usr/sbin.
\fBamcrypt\fR calls \fBamaespipe\fR and pass the
-\fBpassphrase\fR through file descriptor 3\&.
-The passphrase should be stored in ~amanda/\&.am_passphrase\&.
-
+\fBpassphrase\fR through file descriptor 3.
+The passphrase should be stored in ~amanda/.am_passphrase.
.SH "HOW TO CREATE ENCRYPTION KEYS FOR AMCRYPT"
-1\&. Create 65 random encryption keys and encrypt those keys using gpg\&. Reading
+1. Create 65 random encryption keys and encrypt those keys using gpg. Reading
from /dev/random may take indefinitely long if kernel's random entropy pool
-is empty\&. If that happens, do some other work on some other console (use
-keyboard, mouse and disks)\&.
-
+is empty. If that happens, do some other work on some other console (use
+keyboard, mouse and disks).
.PP
-head \-c 2925 /dev/random | uuencode \-m \- | head \-n 66 | tail \-n 65 \\ | gpg \-\-symmetric \-a > ~amanda/\&.gnupg/am_key\&.gpg
-
+head -c 2925 /dev/random | uuencode -m - | head -n 66 | tail -n 65 \ | gpg --symmetric -a > ~amanda/.gnupg/am_key.gpg
.PP
-This will ask for a passphrase\&. Remember this passphrase as you will need it in the next step\&.
-
+This will ask for a passphrase. Remember this passphrase as you will need it in the next step.
.PP
-2\&. Store the passphrase inside the home\-directory of the AMANDA\-user and protect it with proper permissions:
+2. Store the passphrase inside the home-directory of the AMANDA-user and protect it with proper permissions:
.nf
-echo my_secret_passphrase > ~amanda/\&.am_passphrase
-chown amanda:disk ~amanda/\&.am_passphrase
-chmod 700 ~amanda/\&.am_passphrase
+echo my_secret_passphrase > ~amanda/.am_passphrase
+chown amanda:disk ~amanda/.am_passphrase
+chmod 700 ~amanda/.am_passphrase
.fi
-
.SH "KEY AND PASSPHRASE"
-
.PP
- \fBamcrypt\fR uses the same key to encrypt and decrypt data\&.
+\fBamcrypt\fR
+uses the same key to encrypt and decrypt data.
It is very important to store and protect the key and the passphrase
-properly\&. Encrypted backup data can \fBonly\fR be recovered with the correct key and
-passphrase\&.
-
+properly. Encrypted backup data can \fBonly\fR be recovered with the correct key and
+passphrase.
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamanda\&.conf\fR(5), \fBaespipe\fR(1), \fBamaespipe\fR(8), \fBgpg\fR(1)
+\fBamanda\fR(8),
+\fBamanda.conf\fR(5),
+\fBaespipe\fR(1),
+\fBamaespipe\fR(8),
+\fBgpg\fR(1)
.IP "\\$1" \\$2
..
.TH "AMDD" 8 "" "" ""
-.SH NAME
-amdd \- Amanda version of dd
+.SH "NAME"
+amdd - Amanda version of dd
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 5
-\fBamdd\fR [\-d] [\fIif=input\fR] [\fIof=output\fR] [\fIbs=blocksize\fR] [\fIskip=count\fR] [\fIcount=count\fR]
-.ad
-.hy
-
+\fBamdd\fR [-d] [\fIif=input\fR] [\fIof=output\fR] [\fIbs=blocksize\fR] [\fIskip=count\fR] [\fIcount=count\fR]
.SH "DESCRIPTION"
-
.PP
-\fBAmdd\fR provides just enough of the standard UNIX \fBdd\fR command for the needs of \fBAmanda\fR\&. This is handy when doing a full restore and the standard \fBdd\fR program has not yet been found\&.
-
+\fBAmdd\fR
+provides just enough of the standard UNIX
+\fBdd\fR
+command for the needs of
+\fBAmanda\fR. This is handy when doing a full restore and the standard
+\fBdd\fR
+program has not yet been found.
.PP
-\fBAmdd\fR also provides access to the \fBAmanda\fR output drivers that support various tape simulations\&. This may be used for debugging or to convert from one format to another\&.
-
+\fBAmdd\fR
+also provides access to the
+\fBAmanda\fR
+output drivers that support various tape simulations. This may be used for debugging or to convert from one format to another.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&. See the \fBOUTPUT DRIVERS\fR section of \fBamanda(8)\fR for more information on the \fBAmanda\fR output drivers\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR. See the
+\fBOUTPUT DRIVERS\fR
+section of
+\fBamanda(8)\fR
+for more information on the
+\fBAmanda\fR
+output drivers.
.SH "OPTIONS"
-
.TP
-\fB\-d\fR
-Turn on debugging output\&.
-
+\fB-d\fR
+Turn on debugging output.
.TP
-\fB\-l\fR\fIlength\fR
-Set the output length\&. If the output driver limits the output size, this controls when end of tape will be simulated\&.
-
-\fBLength\fR may have a multiplier suffix:
-
-
+\fB-l\fR\fIlength\fR
+Set the output length. If the output driver limits the output size, this controls when end of tape will be simulated.
+.sp
+\fBLength\fR
+may have a multiplier suffix:
+.sp
.nf
-k \-> 1024 (Kilobytes)
-b \-> 512 (Blocks)
-M \-> 1024*1024 (Megabytes)
+k -> 1024 (Kilobytes)
+b -> 512 (Blocks)
+M -> 1024*1024 (Megabytes)
.fi
-The default is no multiplier (bytes)\&.
-
+The default is no multiplier (bytes).
.TP
\fBif=\fR\fBinput\fR
-Input to \fBdd\fR\&. Default is stdin\&.
-
+Input to
+\fBdd\fR. Default is stdin.
.TP
\fBof=\fR\fBoutput\fR
-Where to send the output of \fBdd\fR\&. Default is stdout\&.
-
+Where to send the output of
+\fBdd\fR. Default is stdout.
.TP
\fBbs=\fR\fBblocksize\fR
-Size of each record\&. Input records smaller than this will \fBnot\fR be padded\&. Output records will be the same size as the corresponding input record\&. Default is 512 bytes\&.
-
-\fBBlocksize\fR may have a multiplier suffix:
-
-
+Size of each record. Input records smaller than this will
+\fBnot\fR
+be padded. Output records will be the same size as the corresponding input record. Default is 512 bytes.
+.sp
+\fBBlocksize\fR
+may have a multiplier suffix:
+.sp
.nf
-k \-> 1024 (Kilobytes)
-b \-> 512 (Blocks)
-M \-> 1024*1024 (Megabytes)
+k -> 1024 (Kilobytes)
+b -> 512 (Blocks)
+M -> 1024*1024 (Megabytes)
.fi
-The default is no multiplier (bytes)\&.
-
+The default is no multiplier (bytes).
.TP
\fBcount=\fR\fBcount\fR
-Number of records to copy\&. Default is all records until end of file\&.
-
+Number of records to copy. Default is all records until end of file.
.TP
\fBskip=\fR\fBcount\fR
-Number of records to skip before copying input to output\&. Default is zero\&.
-
+Number of records to skip before copying input to output. Default is zero.
.SH "AUTHOR"
-
.PP
-Marc Mengel <mengel@fnal\&.gov>, John R\&. Jackson <jrj@purdue\&.edu> : Original text
-
+Marc Mengel
+<mengel@fnal.gov>, John R. Jackson
+<jrj@purdue.edu>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMDUMP" 8 "" "" ""
-.SH NAME
-amdump \- back up all disks in an Amanda configuration
+.SH "NAME"
+amdump - back up all disks in an Amanda configuration
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 7
-\fBamdump\fR \fIconfig\fR [\fIhost\fR\ [\fIdisk\fR...]...]
-.ad
-.hy
-
+\fBamdump\fR \fIconfig\fR [\fIhost\fRÂ [\fIdisk\fR...]...]
.SH "DESCRIPTION"
-
.PP
-\fBAmdump\fR switches to the appropriate \fBAmanda\fR configuration directory, e\&.g\&. /usr/local/etc/amanda/\fBconfig\fR, then attempts to back up every disk specified by the \fBamanda\&.conf\fR file\&. \fBAmdump\fR is normally run by \fBcron\fR\&.
-
+\fBAmdump\fR
+switches to the appropriate
+\fBAmanda\fR
+configuration directory, e.g. /usr/local/etc/amanda/\fBconfig\fR, then attempts to back up every disk specified by the
+\fBamanda.conf\fR
+file.
+\fBAmdump\fR
+is normally run by
+\fBcron\fR.
.PP
-You can specify many host/disk expressions, only disks that match an expression will be dumped\&. All disks are dumped if no expressions are given\&.
-
+You can specify many host/disk expressions, only disks that match an expression will be dumped. All disks are dumped if no expressions are given.
.PP
-If the file /usr/local/etc/amanda/\fBconfig\fR/hold exists, \fBamdump\fR will wait until it is removed before starting the backups\&. This allows scheduled backups to be delayed when circumstances warrant, for example, if the tape device is being used for some other purpose\&. While waiting, \fBamdump\fR checks for the hold file every minute\&.
-
+If the file /usr/local/etc/amanda/\fBconfig\fR/hold exists,
+\fBamdump\fR
+will wait until it is removed before starting the backups. This allows scheduled backups to be delayed when circumstances warrant, for example, if the tape device is being used for some other purpose. While waiting,
+\fBamdump\fR
+checks for the hold file every minute.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "EXAMPLE"
-
.PP
-Here is a typical crontab entry\&. It runs \fBamdump\fR every weeknight at 1 a\&.m\&. as user \fBbin\fR:
+Here is a typical crontab entry. It runs
+\fBamdump\fR
+every weeknight at 1 a.m. as user
+\fBbin\fR:
.nf
-0 1 * * 1\-5 bin /usr/local/sbin/amdump daily
+0 1 * * 1-5 bin /usr/local/sbin/amdump daily
.fi
-
.PP
-Please see the \fBcrontab\fR(5) or \fBcrontab\fR(1) manual page for the correct crontab format for your system\&.
-
+Please see the
+\fBcrontab\fR(5)
+or
+\fBcrontab\fR(1)
+manual page for the correct crontab format for your system.
.SH "MESSAGES"
-
.TP
amdump: waiting for hold file to be removed
-The "hold" file exists and \fBamdump\fR is waiting for it to be removed before starting backups\&.
-
+The "hold" file exists and
+\fBamdump\fR
+is waiting for it to be removed before starting backups.
.TP
amdump: amdump or amflush is already running, or you must run amcleanup
-Amdump detected another \fBamdump\fR or \fBamflush\fR running, or the remains of a previous incomplete \fBamdump\fR or \fBamflush\fR run\&. This run is terminated\&. If the problem is caused by the remains of a previous run, you must execute \fBamcleanup\fR(8) and then rerun \fBamdump\fR\&.
-
+Amdump detected another
+\fBamdump\fR
+or
+\fBamflush\fR
+running, or the remains of a previous incomplete
+\fBamdump\fR
+or
+\fBamflush\fR
+run. This run is terminated. If the problem is caused by the remains of a previous run, you must execute
+\fBamcleanup\fR(8)
+and then rerun
+\fBamdump\fR.
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org> : Original text
-
+James da Silva,
+<jds@amanda.org>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamcheck\fR(8), \fBamcleanup\fR(8), \fBamrestore\fR(8), \fBamflush\fR(8), \fBcron\fR(8)
+\fBamanda\fR(8),
+\fBamcheck\fR(8),
+\fBamcleanup\fR(8),
+\fBamrestore\fR(8),
+\fBamflush\fR(8),
+\fBcron\fR(8)
.IP "\\$1" \\$2
..
.TH "AMFETCHDUMP" 8 "" "" ""
-.SH NAME
-amfetchdump \- extract backup images from multiple Amanda tapes.
+.SH "NAME"
+amfetchdump - extract backup images from multiple Amanda tapes.
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 12
-\fBamfetchdump\fR [\-pcClawns] [\-d\ \fIdevice\fR] [\-o\ \fIdirectory\fR] [\-i\ \fIlogfile\fR] [\-b\ \fIblocksize\fR] \fIconfig\fR \fIhostname\fR [\fIdisk\fR\ [\fIdate\fR\ [\fIlevel\fR\ [\fIhostname\fR\ [\&.\&.\&.]]]]]
-.ad
-.hy
-
+\fBamfetchdump\fR [-pcClawns] [-d \fIdevice\fR] [-o \fIdirectory\fR] [-i \fIlogfile\fR] [-b \fIblocksize\fR] \fIconfig\fR \fIhostname\fR [\fIdisk\fR [ \fIdate\fR [ \fIlevel\fR [ \fIhostname\fR [...] ] ] ]]
.SH "DESCRIPTION"
-
.PP
-\fBAmfetchdump\fR pulls one or more matching dumps from tape or from the holding disk, handling the reassembly of multi\-tape split dump files as well as any tape autochanger operations\&.
-
+\fBAmfetchdump\fR
+pulls one or more matching dumps from tape or from the holding disk, handling the reassembly of multi-tape split dump files as well as any tape autochanger operations.
.PP
-It will automatically use the logs created by \fBamdump\fR(8) to locate available dumps on tape, in the same way that the \fBfind\fR feature of \fBamadmin\fR(8) lists available dumps\&. If these logs are unavailable, it can search tape\-by\-tape to find what it needs, and can generate new logs to serve as an emergency tape inventory\&.
-
+It will automatically use the logs created by
+\fBamdump\fR(8)
+to locate available dumps on tape, in the same way that the
+\fBfind\fR
+feature of
+\fBamadmin\fR(8)
+lists available dumps. If these logs are unavailable, it can search tape-by-tape to find what it needs, and can generate new logs to serve as an emergency tape inventory.
.PP
-The \fBhostname\fR, \fBdiskname\fR, \fBdatestamp\fR, and \fBlevel\fR dump pattern\-matching works as in \fBamrestore\fR(8), with the added requirement that at minimum a \fBhostname\fR must be specified when not in inventory mode\&.
-
+The
+\fBhostname\fR,
+\fBdiskname\fR,
+\fBdatestamp\fR, and
+\fBlevel\fR
+dump pattern-matching works as in
+\fBamrestore\fR(8), with the added requirement that at minimum a
+\fBhostname\fR
+must be specified when not in inventory mode.
.PP
-Unless \fB\-p\fR is used, backup images are extracted to files in the current directory named:
-
+Unless
+\fB-p\fR
+is used, backup images are extracted to files in the current directory named:
.PP
-\fBhostname\&.diskname\&.datestamp\&.dumplevel\fR
-
+\fBhostname.diskname.datestamp.dumplevel\fR
.SH "OPTIONS"
-
.TP
-\fB\-p\fR
-Pipe exactly one complete dump file to \fBstdout\fR, instead of writing the file to disk\&. This will restore only the first matching dumpfile (where "first" is determined by the dump log search facility)\&.
-
+\fB-p\fR
+Pipe exactly one complete dump file to
+\fBstdout\fR, instead of writing the file to disk. This will restore only the first matching dumpfile (where "first" is determined by the dump log search facility).
.TP
-\fB\-d\fR \fIdevice\fR
-Restore from this tape device instead of the default\&.
-
+\fB-d\fR \fIdevice\fR
+Restore from this tape device instead of the default.
.TP
-\fB\-o\fR \fIdirectory\fR
-Output restored files to this directory, instead of to the current working directory\&.
-
+\fB-o\fR \fIdirectory\fR
+Output restored files to this directory, instead of to the current working directory.
.TP
-\fB\-c\fR
-Compress output, fastest method available\&.
-
+\fB-c\fR
+Compress output, fastest method available.
.TP
-\fB\-C\fR
-Compress output, smallest file size method available\&.
-
+\fB-C\fR
+Compress output, smallest file size method available.
.TP
-\fB\-l\fR
-Leave dumps in the compressed/uncompressed state in which they were found on tape\&. By default, \fBamfetchdump\fR will automatically uncompress when restoring\&.
-
+\fB-l\fR
+Leave dumps in the compressed/uncompressed state in which they were found on tape. By default,
+\fBamfetchdump\fR
+will automatically uncompress when restoring.
.TP
-\fB\-a\fR
-Assume that all tapes are already available, via tape changer or otherwise, instead of prompting the operator to ensure that all tapes are loaded\&.
-
+\fB-a\fR
+Assume that all tapes are already available, via tape changer or otherwise, instead of prompting the operator to ensure that all tapes are loaded.
.TP
-\fB\-i\fR \fIfilename\fR
-Generate an inventory of all dumps "seen" on the tapes we search, for later use as a log\&.
-
+\fB-i\fR \fIfilename\fR
+Generate an inventory of all dumps "seen" on the tapes we search, for later use as a log.
.TP
-\fB\-w\fR
-Wait to put split dumps together until all chunks have been restored\&. Normally, \fBamfetchdump\fR will attempt to read pieces of a split file from tape in order, so that it can assemble them simply by appending each file to the first\&. This option disables the appending behavior, and instead restores each piece as an individual file and reassembles them only after all have been restored\&.
-
-
-.RS
-.Sh "Note"
+\fB-w\fR
+Wait to put split dumps together until all chunks have been restored. Normally,
+\fBamfetchdump\fR
+will attempt to read pieces of a split file from tape in order, so that it can assemble them simply by appending each file to the first. This option disables the appending behavior, and instead restores each piece as an individual file and reassembles them only after all have been restored.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
This requires at least double the size of your dump in free
-disk space, in order to build the final assembled dumpfile\&.
-.RE
-This behavior is implicitly invoked in circumstances where knowing the location of all dumps on tape in advance is not possible, such as when you are restoring without log files\&.
-
+disk space, in order to build the final assembled dumpfile.This behavior is implicitly invoked in circumstances where knowing the location of all dumps on tape in advance is not possible, such as when you are restoring without log files.
.TP
-\fB\-n\fR
-Do not reassemble split dump files at all, just restore each piece as an individual file\&.
-
+\fB-n\fR
+Do not reassemble split dump files at all, just restore each piece as an individual file.
.TP
-\fB\-s\fR
-Do not fast\-forward straight to needed files on tape\&. This will slow down most restores substantially\&. Only use this option if your tape drive does not properly support the fast\-forward operation\&.
-
+\fB-s\fR
+Do not fast-forward straight to needed files on tape. This will slow down most restores substantially. Only use this option if your tape drive does not properly support the fast-forward operation.
.TP
-\fB\-b\fR \fIblocksize\fR
-Force a particular block size when reading from tapes\&. This value will usually be autodetected, and should not normally need to be set\&.
-
+\fB-b\fR \fIblocksize\fR
+Force a particular block size when reading from tapes. This value will usually be autodetected, and should not normally need to be set.
.SH "EXAMPLES"
-
.PP
-All the examples here assume your configuration is called \fISetA\fR\&.
-
+All the examples here assume your configuration is called
+\fISetA\fR.
.PP
-Here's a simple case, restoring all known dumps of the host vanya to the current working directory\&.
-
+Here's a simple case, restoring all known dumps of the host vanya to the current working directory.
+.sp
.nf
$ amfetchdump SetA vanya
.fi
-
+.sp
.PP
-A more likely scenario involves restoring a particular dump from a particular date\&. We'll pipe this one to \fBGNU\-tar\fR as well, to automatically extract the dump\&.
-
+A more likely scenario involves restoring a particular dump from a particular date. We'll pipe this one to
+\fBGNU-tar\fR
+as well, to automatically extract the dump.
+.sp
.nf
-$ amfetchdump \-p SetA vanya /home 20051020 | gtar \-xvpf \-
+$ amfetchdump -p SetA vanya /home 20051020 | gtar -xvpf -
.fi
-
+.sp
.PP
-In a situation where all of our dump logs have been wiped out, we could also use amfetchdump to inventory our tapes and recreate an imitation of those logs, which we'll send to \fBstdout\fR for casual perusal\&.
-
+In a situation where all of our dump logs have been wiped out, we could also use amfetchdump to inventory our tapes and recreate an imitation of those logs, which we'll send to
+\fBstdout\fR
+for casual perusal.
+.sp
.nf
-$ amfetchdump \-i \- SetA
+$ amfetchdump -i - SetA
.fi
-
+.sp
.PP
-Note that you can specify a restore while in inventory mode, and \fBamfetchdump\fR will continue searching for more dumps from this host even after successfully restoring a dump, inventorying all the while\&. If your backup searcher has been trashed, this is a handy way to recover what you have\&.
-
+Note that you can specify a restore while in inventory mode, and
+\fBamfetchdump\fR
+will continue searching for more dumps from this host even after successfully restoring a dump, inventorying all the while. If your backup searcher has been trashed, this is a handy way to recover what you have.
+.sp
.nf
-$ amfetchdump \-i /var/amanda/log SetA backupserver
+$ amfetchdump -i /var/amanda/log SetA backupserver
.fi
-
+.sp
.SH "CAVEATS"
\fBAmfetchdump\fR is dependent on accessing your server's config,
-tape changer, and (normally) dump logs\&. As such, it's not necessarily
+tape changer, and (normally) dump logs. As such, it's not necessarily
the most useful tool when those have all been wiped out and you
-desperately need to pull things from your tape\&. Pains have been taken
+desperately need to pull things from your tape. Pains have been taken
to make it as capable as possible, but for seriously minimialist
restores, look to
\fBamrestore\fR(8)
or
\fBdd\fR(8)
-instead\&.
-
+instead.
.SH "AUTHOR"
-
.PP
-John Stange, <building@nap\&.edu>, National Academies Press
-
+John Stange,
+<building@nap.edu>, National Academies Press
.PP
-Ian Turner, <ian@zmanda\&.com>: XML\-conversion
-
+Ian Turner,
+<ian@zmanda.com>: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamadmin\fR(8), \fBamrestore\fR(8), \fBtar\fR(1) \fBrestore\fR(8)
+\fBamanda\fR(8),
+\fBamadmin\fR(8),
+\fBamrestore\fR(8),
+\fBtar\fR(1)\fBrestore\fR(8)
.IP "\\$1" \\$2
..
.TH "AMFLUSH" 8 "" "" ""
-.SH NAME
-amflush \- flush Amanda backup files from holding disk to tape
+.SH "NAME"
+amflush - flush Amanda backup files from holding disk to tape
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 8
-\fBamflush\fR [\-b] [\-f] [\-s] [\-D\ \fIdatestamp\fR...] \fIconfig\fR [\fIhost\fR\ [\fIdisk\fR...]...]
-.ad
-.hy
-
+\fBamflush\fR [-b] [-f] [-s] [-DÂ \fIdatestamp\fR...] \fIconfig\fR [\fIhost\fRÂ [\fIdisk\fR...]...]
.SH "DESCRIPTION"
-
.PP
-\fBAmflush\fR writes \fBAmanda\fR backups from the holding disks to tape, and updates the \fBAmanda\fR info database and tapelist accordingly\&. Backups may stay in a holding disk when something is wrong with the tape at the time \fBamdump\fR is run\&. When this happens, the problem must be corrected and \fBamflush\fR run by hand\&.
-
+\fBAmflush\fR
+writes
+\fBAmanda\fR
+backups from the holding disks to tape, and updates the
+\fBAmanda\fR
+info database and tapelist accordingly. Backups may stay in a holding disk when something is wrong with the tape at the time
+\fBamdump\fR
+is run. When this happens, the problem must be corrected and
+\fBamflush\fR
+run by hand.
.SH "OPTIONS"
-
.TP
-\fB\-b\fR
-Run \fBamflush\fR in batch mode\&. All datestamps are selected unless specified\&. The flush is started without confirmation\&.
-
+\fB-b\fR
+Run
+\fBamflush\fR
+in batch mode. All datestamps are selected unless specified. The flush is started without confirmation.
.TP
-\fB\-f\fR
-Run \fBamflush\fR in foreground\&. \fBAmflush\fR normally detaches itself from the tty and runs as a background process\&. With the \fB\-f\fR option, \fBamflush\fR stays in the foreground\&. This is useful if \fBamflush\fR is run as part of another script that, for example, advances the tape after the flush is completed\&.
-
+\fB-f\fR
+Run
+\fBamflush\fR
+in foreground.
+\fBAmflush\fR
+normally detaches itself from the tty and runs as a background process. With the
+\fB-f\fR
+option,
+\fBamflush\fR
+stays in the foreground. This is useful if
+\fBamflush\fR
+is run as part of another script that, for example, advances the tape after the flush is completed.
.TP
-\fB\-s\fR
-Write log to stdout/stderr instead of the amflush log file\&. Requires the \fB\-f\fR option\&.
-
+\fB-s\fR
+Write log to stdout/stderr instead of the amflush log file. Requires the
+\fB-f\fR
+option.
.TP
-\fB\-D datestamp\fR
-specify a datestamp expression you want to flush, see the "DATESTAMP EXPRESSION" section of \fBamanda\fR(8) for a description\&. \fB\-D 20001225\-7\fR will flush all dumps from 25 december 2000 to 27 december 2000\&.
-
+\fB-D datestamp\fR
+specify a datestamp expression you want to flush, see the "DATESTAMP EXPRESSION" section of
+\fBamanda\fR(8)
+for a description.
+\fB-D 20001225-7\fR
+will flush all dumps from 25 december 2000 to 27 december 2000.
.PP
-You can specify many host/disk expressions, only disks that match an expression will be flushed\&. All disks are flushed if no expressions are given\&. see the "HOST & DISK EXPRESSION" section of \fBamanda\fR(8) for a description\&.
-
+You can specify many host/disk expressions, only disks that match an expression will be flushed. All disks are flushed if no expressions are given. see the "HOST & DISK EXPRESSION" section of
+\fBamanda\fR(8)
+for a description.
.PP
-\fBAmflush\fR will look in the holding disks specified by the \fBamanda\&.conf\fR file in /usr/local/etc/amanda/\fBconfig\fR for any non\-empty \fBAmanda\fR work directories\&. It then prompts you to select a directory or to process all of the directories\&. The work directories in the holding disks are named by the date at the time \fBamdump\fR was run, e\&.g\&. 19910215\&.
-
+\fBAmflush\fR
+will look in the holding disks specified by the
+\fBamanda.conf\fR
+file in /usr/local/etc/amanda/\fBconfig\fR
+for any non-empty
+\fBAmanda\fR
+work directories. It then prompts you to select a directory or to process all of the directories. The work directories in the holding disks are named by the date at the time
+\fBamdump\fR
+was run, e.g.
+19910215.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "EXAMPLE"
-
.PP
-\fBAmflush\fR will search for holding areas associated with the \fBdaily\fR configuration\&. After you select which holding area to flush, \fBamflush\fR writes the data to tape, updates the databases and sends a mail report similar to \fBamdump\fR(8)\&.
+\fBAmflush\fR
+will search for holding areas associated with the
+\fBdaily\fR
+configuration. After you select which holding area to flush,
+\fBamflush\fR
+writes the data to tape, updates the databases and sends a mail report similar to
+\fBamdump\fR(8).
.nf
% amflush daily
-Scanning /amanda\-hold\&.\&.\&.
- 20001113: found \fBAmanda\fR directory\&.
- 20001114: found \fBAmanda\fR directory\&.
+Scanning /amanda-hold...
+ 20001113: found \fBAmanda\fR directory.
+ 20001114: found \fBAmanda\fR directory.
Multiple \fBAmanda\fR directories, please pick one by letter:
- A\&. 20001113
- B\&. 20001114
-Select directories to flush [A\&.\&.B]: [ALL] all
+ A. 20001113
+ B. 20001114
+Select directories to flush [A..B]: [ALL] all
Flushing dumps in 20001113, 20001114,
today: 20001117
-to tape drive /dev/rmt/0mn\&.
-Expecting tape DMP014 or a new tape\&. (The last dumps were to tape DMP013)
+to tape drive /dev/rmt/0mn.
+Expecting tape DMP014 or a new tape. (The last dumps were to tape DMP013)
Are you sure you want to do this? yes
-Running in background, you can log off now\&.
-You'll get mail when amflush is finished\&.
+Running in background, you can log off now.
+You'll get mail when amflush is finished.
.fi
-
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org> : Original text
-
+James da Silva,
+<jds@amanda.org>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamdump\fR(8)
+\fBamanda\fR(8),
+\fBamdump\fR(8)
.IP "\\$1" \\$2
..
.TH "AMGETCONF" 8 "" "" ""
-.SH NAME
-amgetconf \- look up amanda.conf variables
+.SH "NAME"
+amgetconf - look up amanda.conf variables
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 10
\fBamgetconf\fR [\fIconfig\fR] \fIparameter\fR
-.ad
-.hy
-
.SH "DESCRIPTION"
-
.PP
-\fBAmgetconf\fR looks up parameters in \fBamanda\&.conf\fR, the \fBAmanda\fR configuration file, or from the build and runtime environment, and returns their corresponding value\&.
-
+\fBAmgetconf\fR
+looks up parameters in
+\fBamanda.conf\fR, the
+\fBAmanda\fR
+configuration file, or from the build and runtime environment, and returns their corresponding value.
.PP
-If \fBconfig\fR is not specified, \fBamgetconf\fR assumes it is being run from the configuration directory and that \fBamanda\&.conf\fR is present\&.
-
+If
+\fBconfig\fR
+is not specified,
+\fBamgetconf\fR
+assumes it is being run from the configuration directory and that
+\fBamanda.conf\fR
+is present.
.PP
-If \fBparameter\fR begins with \fBbuild\&.\fR, the (case insensitive) string following the period is a build environment variable\&. Variables without a value (e\&.g\&. \fBXFSDUMP\fR on a system that does not support that type of file system) will not report an error and will return an empty string as the value\&. Flag variables (e\&.g\&. \fBUSE_AMANDAHOSTS\fR) will return 1 if the flag is set or an empty string if it is not\&.
-
+If
+\fBparameter\fR
+begins with
+\fBbuild.\fR, the (case insensitive) string following the period is a build environment variable. Variables without a value (e.g.
+\fBXFSDUMP\fR
+on a system that does not support that type of file system) will not report an error and will return an empty string as the value. Flag variables (e.g.
+\fBUSE_AMANDAHOSTS\fR) will return
+1
+if the flag is set or an empty string if it is not.
.PP
-If \fBparameter\fR begins with \fBdbopen\&.\fR, the string following the period is a program name and an \fBAmanda\fR debug file will be created for the caller\&. The name of the file is returned\&.
-
+If
+\fBparameter\fR
+begins with
+\fBdbopen.\fR, the string following the period is a program name and an
+\fBAmanda\fR
+debug file will be created for the caller. The name of the file is returned.
.PP
-If \fBparameter\fR begins with \fBdbclose\&.\fR, the string following the period is a program name previously used with \fBdbopen\&.\fR, followed by a colon (:) and the previously opened file name\&.
-
+If
+\fBparameter\fR
+begins with
+\fBdbclose.\fR, the string following the period is a program name previously used with
+\fBdbopen.\fR, followed by a colon (:) and the previously opened file name.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "EXAMPLE"
-
.PP
Find out the path to the log file directory:
-
+.sp
.nf
% amgetconf daily logdir
/usr/local/etc/amanda//daily
.fi
-
+.sp
.PP
Find out the current tape type:
-
+.sp
.nf
% amgetconf daily tapetype
-DLT4000\-IV
+DLT4000-IV
.fi
-
+.sp
.PP
Find out the default configuration directory:
-
+.sp
.nf
-% amgetconf daily build\&.CONFIG_DIR
+% amgetconf daily build.CONFIG_DIR
/usr/local/etc/amanda/
.fi
-
+.sp
.PP
Create, use and close a debug file in a script:
-
+.sp
.nf
-% set debug_file = `amgetconf daily dbopen\&.myscript`
+% set debug_file = `amgetconf daily dbopen.myscript`
% echo debug information >> $debug_file
-% amgetconf daily dbclose\&.myscript:$debug_file
+% amgetconf daily dbclose.myscript:$debug_file
.fi
-
+.sp
.SH "MESSAGES"
-
.TP
amgetconf: no such parameter \fBparam\fR
-Parameter \fBparam\fR is not a known keyword (e\&.g\&. not a valid \fBamanda\&.conf\fR keyword)\&. In this case, \fBamgetconf\fR will write "\fBBUGGY\fR" to stdout as the value\&.
-
+Parameter
+\fBparam\fR
+is not a known keyword (e.g. not a valid
+\fBamanda.conf\fR
+keyword). In this case,
+\fBamgetconf\fR
+will write "\fBBUGGY\fR" to stdout as the value.
.SH "SEE ALSO"
-
.PP
\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMLABEL" 8 "" "" ""
-.SH NAME
-amlabel \- label an Amanda tape
+.SH "NAME"
+amlabel - label an Amanda tape
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 8
-\fBamlabel\fR [\-f] \fIconfig\fR \fIlabel\fR [\fIslot\fR\ \fIslot\fR]
-.ad
-.hy
-
+\fBamlabel\fR [-f] \fIconfig\fR \fIlabel\fR [\fIslot\fRÂ \fIslot\fR]
.SH "DESCRIPTION"
-
.PP
-All \fBAmanda\fR tapes must be pre\-labeled before they are used\&. \fBAmanda\fR verifies the label in \fBamdump\fR and \fBamflush\fR before writing to make sure the proper tape is loaded\&.
-
+All
+\fBAmanda\fR
+tapes must be pre-labeled before they are used.
+\fBAmanda\fR
+verifies the label in
+\fBamdump\fR
+and
+\fBamflush\fR
+before writing to make sure the proper tape is loaded.
.PP
-\fBAmlabel\fR writes an \fBAmanda\fR label on the tape in the device specified by the \fBamanda\&.conf\fR file in /usr/local/etc/amanda/\fBconfig\fR\&. \fBLabel\fR may be any string that does not contain whitespace and that matches the \fBamanda\&.conf\fR \fBlabelstr\fR regular expression option\&. It is up to the system administrator to define a naming convention\&.
-
+\fBAmlabel\fR
+writes an
+\fBAmanda\fR
+label on the tape in the device specified by the
+\fBamanda.conf\fR
+file in /usr/local/etc/amanda/\fBconfig\fR.
+\fBLabel\fR
+may be any string that does not contain whitespace and that matches the
+\fBamanda.conf\fR\fBlabelstr\fR
+regular expression option. It is up to the system administrator to define a naming convention.
.PP
-\fBAmlabel\fR appends the new tape to the \fBtapelist\fR file so it will be used by \fBAmanda\fR before it reuses any other tapes\&. When you \fBamlabel\fR multiple tapes, they will be used in the order you \fBamlabel\fR them\&.
-
+\fBAmlabel\fR
+appends the new tape to the
+\fBtapelist\fR
+file so it will be used by
+\fBAmanda\fR
+before it reuses any other tapes. When you
+\fBamlabel\fR
+multiple tapes, they will be used in the order you
+\fBamlabel\fR
+them.
.PP
-\fBAmlabel\fR will not write the label if the tape contains an active \fBAmanda\fR tape or if the label specified is on an active tape\&. The \fB\-f\fR (force) flag bypasses these verifications\&.
-
+\fBAmlabel\fR
+will not write the label if the tape contains an active
+\fBAmanda\fR
+tape or if the label specified is on an active tape. The
+\fB-f\fR
+(force) flag bypasses these verifications.
.PP
-An optional \fBslot\fR may be specified after the tape label\&. If a tape changer is in use, \fBamlabel\fR will label the tape in the specified slot instead of the currently loaded tape\&.
-
+An optional
+\fBslot\fR
+may be specified after the tape label. If a tape changer is in use,
+\fBamlabel\fR
+will label the tape in the specified slot instead of the currently loaded tape.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "EXAMPLE"
-
.PP
-Write an \fBAmanda\fR label with the string "DMP000" on the tape loaded in the device named in the \fBtapedev\fR option in /usr/local/etc/amanda/daily/amanda\&.conf:
+Write an
+\fBAmanda\fR
+label with the string "DMP000" on the tape loaded in the device named in the
+\fBtapedev\fR
+option in /usr/local/etc/amanda/daily/amanda.conf:
.nf
% amlabel daily DMP000
.fi
-
.PP
Label the tape in slot 3 of the currently configured tape changer with the string "DMP003":
.nf
% amlabel daily DMP003 slot 3
.fi
-
.SH "MESSAGES"
-
.TP
label \fBlabel\fR doesn't match labelstr \fBstr\fR
-Label \fBlabel\fR on the command line does not match the \fBlabelstr\fR regular expression \fBstr\fR from \fBamanda\&.conf\fR\&.
-
+Label
+\fBlabel\fR
+on the command line does not match the
+\fBlabelstr\fR
+regular expression
+\fBstr\fR
+from
+\fBamanda.conf\fR.
.TP
label \fBlabel\fR already on a tape
-Label \fBlabel\fR is already listed as an active \fBAmanda\fR tape\&.
-
+Label
+\fBlabel\fR
+is already listed as an active
+\fBAmanda\fR
+tape.
.TP
no tpchanger specified in \fBpath\fR , so slot command invalid
-The command line has the \fBslot\fR parameter but the \fBamanda\&.conf\fR file in \fBpath\fR does not have a tape changer configured\&.
-
+The command line has the
+\fBslot\fR
+parameter but the
+\fBamanda.conf\fR
+file in
+\fBpath\fR
+does not have a tape changer configured.
.TP
reading label \fBlabel\fR, tape is in another amanda configuration
-This tape appears to be a valid \fBAmanda\fR tape, but label does not match \fBlabelstr\fR for this configuration so it is probably part of a different \fBAmanda\fR configuration\&.
-
+This tape appears to be a valid
+\fBAmanda\fR
+tape, but label does not match
+\fBlabelstr\fR
+for this configuration so it is probably part of a different
+\fBAmanda\fR
+configuration.
.TP
reading label \fBlabel\fR, tape is active
-Tape \fBlabel\fR appears to already be part of this \fBAmanda\fR configuration and active, i\&.e\&. has valid data on it\&.
-
+Tape
+\fBlabel\fR
+appears to already be part of this
+\fBAmanda\fR
+configuration and active, i.e. has valid data on it.
.TP
-no label found, are you sure \fBtape\fR is non\-rewinding?
-While checking that the label was written correctly, \fBamlabel\fR got an error that might be caused by mis\-configuring \fBAmanda\fR with a rewinding tape device name instead of a non\-rewinding device name for \fBtape\&.\fR
-
+no label found, are you sure \fBtape\fR is non-rewinding?
+While checking that the label was written correctly,
+\fBamlabel\fR
+got an error that might be caused by mis-configuring
+\fBAmanda\fR
+with a rewinding tape device name instead of a non-rewinding device name for
+\fBtape.\fR
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org>: Original text
-
+James da Silva,
+<jds@amanda.org>: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8) \fBamdump\fR(8) \fBamflush\fR(8)
+\fBamanda\fR(8)\fBamdump\fR(8)\fBamflush\fR(8)
.IP "\\$1" \\$2
..
.TH "AMMT" 8 "" "" ""
-.SH NAME
-ammt \- Amanda version of mt
+.SH "NAME"
+ammt - Amanda version of mt
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 5
-\fBammt\fR [\-d] [\fB\-f\fR | \fB\-t\fR | \fB\fIdevice\fR\fR] \fIcommand\fR [\fIcount\fR]
-.ad
-.hy
-
+\fBammt\fR [-d] [-f -t \fIdevice\fR] \fIcommand\fR [\fIcount\fR]
.SH "DESCRIPTION"
-
.PP
-\fBAmmt\fR provides just enough of the standard UNIX \fBmt\fR command for the needs of \fBAmanda\fR\&. This is handy when doing a full restore and the standard \fBmt\fR program has not yet been found\&.
-
+\fBAmmt\fR
+provides just enough of the standard UNIX
+\fBmt\fR
+command for the needs of
+\fBAmanda\fR. This is handy when doing a full restore and the standard
+\fBmt\fR
+program has not yet been found.
.PP
-\fBAmmt\fR also provides access to the \fBAmanda\fR output drivers that support various tape simulations\&.
-
+\fBAmmt\fR
+also provides access to the
+\fBAmanda\fR
+output drivers that support various tape simulations.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&. See the \fBOUTPUT DRIVERS\fR section of \fBamanda(8)\fR for more information on the \fBAmanda\fR output drivers\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR. See the
+\fBOUTPUT DRIVERS\fR
+section of
+\fBamanda(8)\fR
+for more information on the
+\fBAmanda\fR
+output drivers.
.SH "OPTIONS"
-
.TP
-\fB\-d\fR
-Turn on debugging output\&.
-
+\fB-d\fR
+Turn on debugging output.
.TP
-\fB\-f\fR\fI device\fR
-Access tape device \fBdevice\fR\&. If not specified, the \fBTAPE\fR environment variable is used\&.
-
+\fB-f\fR\fI device\fR
+Access tape device
+\fBdevice\fR. If not specified, the
+\fBTAPE\fR
+environment variable is used.
.TP
-\fB\-t\fR\fI device\fR
-Same as \fB\-f\fR\&.
-
+\fB-t\fR\fI device\fR
+Same as
+\fB-f\fR.
.TP
\fBcommand\fR\fB count\fR
-Which command to issue, and an optional count of operations\&.
-
+Which command to issue, and an optional count of operations.
.SH "COMMANDS"
-
.PP
-Each command may be abbreviated to whatever length makes it unique\&.
-
+Each command may be abbreviated to whatever length makes it unique.
.TP
\fBeof|weof\fR\fB count\fR
-Write \fBcount\fR (default: 1) end of file marks (tapemarks)\&.
-
+Write
+\fBcount\fR
+(default: 1) end of file marks (tapemarks).
.TP
\fBfsf\fR\fB count\fR
-Skip forward \fBcount\fR (default: 1) files\&.
-
+Skip forward
+\fBcount\fR
+(default: 1) files.
.TP
\fBbsf\fR\fB count\fR
-Skip backward \fBcount\fR (default: 1) files\&.
-
+Skip backward
+\fBcount\fR
+(default: 1) files.
.TP
\fBasf\fR\fB count\fR
-Position to file number \fBcount\fR (default: 0) where zero is beginning of tape\&. This is the same as a \fBrewind\fR followed by a \fBfsf\fR \fBcount\fR\&.
-
+Position to file number
+\fBcount\fR
+(default: 0) where zero is beginning of tape. This is the same as a
+\fBrewind\fR
+followed by a
+\fBfsf\fR\fBcount\fR.
.TP
\fBrewind\fR
-Rewind to beginning of tape\&.
-
+Rewind to beginning of tape.
.TP
\fBoffline|rewoffl\fR
-Rewind to beginning of tape and unload the tape from the drive\&.
-
+Rewind to beginning of tape and unload the tape from the drive.
.TP
\fBstatus\fR
-Report status information about the drive\&. Which data reported, and what it means, depends on the underlying operating system, and may include:
-
+Report status information about the drive. Which data reported, and what it means, depends on the underlying operating system, and may include:
.RS
-
.TP
ONLINE
-Indicates the drive is online and ready\&.
-
+Indicates the drive is online and ready.
.TP
OFFLINE
-Indicates the drive is offline or not ready\&.
-
+Indicates the drive is offline or not ready.
.TP
BOT
-Indicates the drive is at beginning of tape\&.
-
+Indicates the drive is at beginning of tape.
.TP
EOT
-Indicates the drive is at end of tape\&.
-
+Indicates the drive is at end of tape.
.TP
PROTECTED
-Indicates the tape is write protected\&.
-
+Indicates the tape is write protected.
.TP
ds
-Device status\&.
-
+Device status.
.TP
er
-Error register\&.
-
+Error register.
.TP
fileno
-Current tape file number\&.
-
+Current tape file number.
.TP
blkno
-Current tape block number file\&.
-
+Current tape block number file.
.RE
-.IP
-
-.RS
-.Sh "Note"
-Many systems only report good data when a tape is in the drive and ready\&.
-
-.RE
-
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+Many systems only report good data when a tape is in the drive and ready.
.PP
-
.SH "AUTHOR"
-
.PP
-Marc Mengel <mengel@fnal\&.gov>, John R\&. Jackson <jrj@purdue\&.edu>: Original text
-
+Marc Mengel
+<mengel@fnal.gov>, John R. Jackson
+<jrj@purdue.edu>: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMOVERVIEW" 8 "" "" ""
-.SH NAME
-amoverview \- display file systems processed by Amanda over time
+.SH "NAME"
+amoverview - display file systems processed by Amanda over time
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 11
-\fBamoverview\fR [[\-config]\ \fIconfig\fR] [\-hostwidth\ \fIwidth\fR] [\-diskwidth\ \fIwidth\fR] [\-skipmissed] [\-last] [\-num0] [\-togo0] [\-verbose]
-.ad
-.hy
-
+\fBamoverview\fR [[-config ] \fIconfig\fR] [-hostwidth \fIwidth\fR] [-diskwidth \fIwidth\fR] [-skipmissed] [-last] [-num0] [-togo0] [-verbose]
.SH "DESCRIPTION"
-
.PP
-\fBAmoverview\fR displays a chart showing hosts and file systems processed by \fBAmanda\fR along with the backup level performed each day\&.
-
+\fBAmoverview\fR
+displays a chart showing hosts and file systems processed by
+\fBAmanda\fR
+along with the backup level performed each day.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "OPTIONS"
-
.TP
-\fB\-config\fR \fIconfig\fR
-Use configuration \fBconfig\fR instead of configuration daily\&.
-
+\fB-config\fR \fIconfig\fR
+Use configuration
+\fBconfig\fR
+instead of configuration daily.
.TP
-\fB\-hostwidth\fR \fIwidth\fR
-Set \fBhost\fR field column width to \fBwidth\fR characters instead of 8\&.
-
+\fB-hostwidth\fR \fIwidth\fR
+Set
+\fBhost\fR
+field column width to
+\fBwidth\fR
+characters instead of 8.
.TP
-\fB\-diskwidth\fR \fIwidth\fR
-Set \fBdisk\fR field column width to \fBwidth\fR characters instead of 20\&.
-
+\fB-diskwidth\fR \fIwidth\fR
+Set
+\fBdisk\fR
+field column width to
+\fBwidth\fR
+characters instead of 20.
.TP
-\fB\-skipmissed\fR
-Compacts the output by only printing stats for the days \fBAmanda\fR actually ran\&.
-
+\fB-skipmissed\fR
+Compacts the output by only printing stats for the days
+\fBAmanda\fR
+actually ran.
.TP
-\fB\-last\fR
-Outputs the last status of each disk at the start\&. Useful for long tapecycles and/or sparse reports\&.
-
+\fB-last\fR
+Outputs the last status of each disk at the start. Useful for long tapecycles and/or sparse reports.
.TP
-\fB\-num0\fR
-Outputs the number of level 0 dumps for each disk\&.
-
+\fB-num0\fR
+Outputs the number of level 0 dumps for each disk.
.TP
-\fB\-togo0\fR
-Outputs the number of runs until the last level 0 dump is overwritten\&.
-
+\fB-togo0\fR
+Outputs the number of runs until the last level 0 dump is overwritten.
.TP
-\fB\-verbose\fR
-\fBAmoverview\fR can take a long while on large systems\&. This option reports intermediate steps while it is working\&.
-
+\fB-verbose\fR
+\fBAmoverview\fR
+can take a long while on large systems. This option reports intermediate steps while it is working.
.SH "RESULTS"
-
.PP
-\fBamoverview\fR is a summary of the output of " \fBamadmin <config> find\fR "\&. When the last column of \fBamadmin find\fR contains anything other than "OK", amoverview translates this into "E" for that day\&.
-
+\fBamoverview\fR
+is a summary of the output of "
+\fBamadmin <config> find\fR
+". When the last column of
+\fBamadmin find\fR
+contains anything other than "OK", amoverview translates this into "E" for that day.
.PP
-A number indicates the level of backup and it succeeded\&. An "E" indicates an error for that day\&. You get an "E" for all errors, like failed to connect, datatimeout, computer crashed, etc, but also for failing to write to tape\&.
-
+A number indicates the level of backup and it succeeded. An "E" indicates an error for that day. You get an "E" for all errors, like failed to connect, datatimeout, computer crashed, etc, but also for failing to write to tape.
.PP
-You can have an "E" followed by a number if a filesystem ran into end\-of\-tape once (gives an "E", and later that day, you flush it to a second tape (a number: the level, indicating success)\&. If the flush failed too, you get a double "EE" for that day\&.
-
+You can have an "E" followed by a number if a filesystem ran into end-of-tape once (gives an "E", and later that day, you flush it to a second tape (a number: the level, indicating success). If the flush failed too, you get a double "EE" for that day.
.PP
-You can also have a double code if you have two tapes in the changer and \fBAmanda\fR failed to write to tape the first time because it hit end of tape (resulting in "E0", for a full, "E1" for an incremental etc\&.) or twice with error ("EE"), and may a successful flush afterwards giving maybe "EE0"\&. (Only the latest 2 characters are printed)\&.
-
+You can also have a double code if you have two tapes in the changer and
+\fBAmanda\fR
+failed to write to tape the first time because it hit end of tape (resulting in "E0", for a full, "E1" for an incremental etc.) or twice with error ("EE"), and may a successful flush afterwards giving maybe "EE0". (Only the latest 2 characters are printed).
.SH "EXAMPLE"
-
.PP
-This shows the \fI/home\fR file system on \fBhost2\fR was backed up at level 3 on the 8th, 9th and 10th of December, had a full backup on the 11th, a level 1 on the 12th and a level 2 on the 13th\&.
+This shows the
+\fI/home\fR
+file system on
+\fBhost2\fR
+was backed up at level 3 on the 8th, 9th and 10th of December, had a full backup on the 11th, a level 1 on the 12th and a level 2 on the 13th.
.nf
# amoverview
host2 /opt 1 1 1 1 1 1
host2 /var 1 1 0 1 1 1
.fi
-
.SH "SEE ALSO"
-
.PP
-\fBamadmin\fR(8), \fBamanda\fR(8)
+\fBamadmin\fR(8),
+\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMPLOT" 8 "" "" ""
-.SH NAME
-amplot \- visualize the behavior of Amanda
+.SH "NAME"
+amplot - visualize the behavior of Amanda
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 7
-\fBamplot\fR [\-b] [\-c] [\-e] [\-g] [\-l] [\-p] [\-t\ \fIT\fR] \fIamdump_files\fR
+\fBamplot\fR [-b] [-c] [-e] [-g] [-l] [-p] [-t \fIT\fR] \fIamdump_files\fR
.br
-.ad
-.hy
-
.SH "DESCRIPTION"
-
.PP
-\fBAmplot\fR reads an \fBamdump\fR output file that \fBAmanda\fR generates each run (e\&.g\&. \fBamdump\&.1\fR) and translates the information into a picture format that may be used to determine how your installation is doing and if any parameters need to be changed\&. \fBAmplot\fR also prints out \fBamdump\fR lines that it either does not understand or knows to be warning or error lines and a summary of the start, end and total time for each backup image\&.
-
-.PP
-\fBAmplot\fR is a shell script that executes an \fBawk\fR program \fB\fR(\fBamplot\&.awk\fR) to scan the \fBamdump\fR output file\&. It then executes a \fBgnuplot\fR program \fB\fR(\fBamplot\&.g\fR) to generate the graph\&. The \fBawk\fR program is written in an enhanced version of awk, such as GNU awk \fB\fR(\fBgawk\fR version 2\&.15 or later) or \fBnawk\fR\&.
-
-.PP
-During execution, \fBamplot\fR generates a few temporary files that \fBgnuplot\fR uses\&. These files are deleted at the end of execution\&.
-
-.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+\fBAmplot\fR
+reads an
+\fBamdump\fR
+output file that
+\fBAmanda\fR
+generates each run (e.g.
+\fBamdump.1\fR) and translates the information into a picture format that may be used to determine how your installation is doing and if any parameters need to be changed.
+\fBAmplot\fR
+also prints out
+\fBamdump\fR
+lines that it either does not understand or knows to be warning or error lines and a summary of the start, end and total time for each backup image.
+.PP
+\fBAmplot\fR
+is a shell script that executes an
+\fBawk\fR
+program
+\fB\fR(\fBamplot.awk\fR) to scan the
+\fBamdump\fR
+output file. It then executes a
+\fBgnuplot\fR
+program
+\fB\fR(\fBamplot.g\fR) to generate the graph. The
+\fBawk\fR
+program is written in an enhanced version of awk, such as GNU awk
+\fB\fR(\fBgawk\fR
+version 2.15 or later) or
+\fBnawk\fR.
+.PP
+During execution,
+\fBamplot\fR
+generates a few temporary files that
+\fBgnuplot\fR
+uses. These files are deleted at the end of execution.
+.PP
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "OPTIONS"
-
.TP
-\fB\-b\fR
-Generate b/w postscript file (need \fB\-p\fR)\&.
-
+\fB-b\fR
+Generate b/w postscript file (need
+\fB-p\fR).
.TP
-\fB\-c\fR
-Compress \fBamdump_files\fR after plotting\&.
-
+\fB-c\fR
+Compress
+\fBamdump_files\fR
+after plotting.
.TP
-\fB\-e\fR
-Extend the X (time) axis if needed\&.
-
+\fB-e\fR
+Extend the X (time) axis if needed.
.TP
-\fB\-g\fR
-Direct \fBgnuplot\fR output directly to the X11 display (default)\&.
-
+\fB-g\fR
+Direct
+\fBgnuplot\fR
+output directly to the X11 display (default).
.TP
-\fB\-p\fR
-Direct postscript output to file \fB\fR\fBYYYYMMDD\fR\fB\&.ps\fR (opposite of \fB\-g\fR)\&.
-
+\fB-p\fR
+Direct postscript output to file
+\fB\fR\fBYYYYMMDD\fR\fB.ps\fR
+(opposite of
+\fB-g\fR).
.TP
-\fB\-l\fR
-Generate landscape oriented output (needs \fB\-p\fR)\&.
-
+\fB-l\fR
+Generate landscape oriented output (needs
+\fB-p\fR).
.TP
-\fB\-t \fR\fBT\fR
-Set the right edge of the plot to be \fBT\fR hours\&.
-
-.PP
-The \fBamdump_files\fR may be in various compressed formats \fB\fR(\fBcompress\fR, \fBgzip\fR, \fBpact\fR, \fBcompact\fR)\&.
-
+\fB-t \fR\fBT\fR
+Set the right edge of the plot to be
+\fBT\fR
+hours.
+.PP
+The
+\fBamdump_files\fR
+may be in various compressed formats
+\fB\fR(\fBcompress\fR,
+\fBgzip\fR,
+\fBpact\fR,
+\fBcompact\fR).
.SH "INTERPRETATION"
-
.PP
-The figure is divided into a number of regions\&. There are titles on the top that show important statistical information about the configuration and from this execution of \fBamdump\fR\&. In the figure, the X axis is time, with 0 being the moment \fBamdump\fR was started\&. The Y axis is divided into 5 regions:
-
+The figure is divided into a number of regions. There are titles on the top that show important statistical information about the configuration and from this execution of
+\fBamdump\fR. In the figure, the X axis is time, with 0 being the moment
+\fBamdump\fR
+was started. The Y axis is divided into 5 regions:
.PP
-\fBQUEUES:\fR How many backups have not been started, how many are waiting on space in the holding disk and how many have been transferred successfully to tape\&.
-
+\fBQUEUES:\fR
+How many backups have not been started, how many are waiting on space in the holding disk and how many have been transferred successfully to tape.
.PP
-\fB%BANDWIDTH:\fR Percentage of allowed network bandwidth in use\&.
-
+\fB%BANDWIDTH:\fR
+Percentage of allowed network bandwidth in use.
.PP
-\fBHOLDING DISK:\fR The higher line depicts space allocated on the holding disk to backups in progress and completed backups waiting to be written to tape\&. The lower line depicts the fraction of the holding disk containing completed backups waiting to be written to tape including the file currently being written to tape\&. The scale is percentage of the holding disk\&.
-
+\fBHOLDING DISK:\fR
+The higher line depicts space allocated on the holding disk to backups in progress and completed backups waiting to be written to tape. The lower line depicts the fraction of the holding disk containing completed backups waiting to be written to tape including the file currently being written to tape. The scale is percentage of the holding disk.
.PP
-\fBTAPE:\fR Tape drive usage\&.
-
+\fBTAPE:\fR
+Tape drive usage.
.PP
-\fB%DUMPERS:\fR Percentage of active dumpers\&.
-
+\fB%DUMPERS:\fR
+Percentage of active dumpers.
.PP
-The idle period at the left of the graph is time \fBamdump\fR is asking the machines how much data they are going to dump\&. This process can take a while if hosts are down or it takes them a long time to generate estimates\&.
-
+The idle period at the left of the graph is time
+\fBamdump\fR
+is asking the machines how much data they are going to dump. This process can take a while if hosts are down or it takes them a long time to generate estimates.
.SH "AUTHOR"
-
.PP
-Olafur Gudmundsson <ogud@tis\&.com>, Trusted Information Systems, formerly at University of Maryland, College Park: Original text
-
+Olafur Gudmundsson
+<ogud@tis.com>, Trusted Information Systems, formerly at University of Maryland, College Park: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "BUGS"
-
.PP
-Reports lines it does not recognize, mainly error cases but some are legitimate lines the program needs to be taught about\&.
-
+Reports lines it does not recognize, mainly error cases but some are legitimate lines the program needs to be taught about.
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamdump\fR(8), \fBgawk\fR(1), \fBnawk\fR(1), \fBawk\fR(1), \fBgnuplot\fR(1), \fBsh\fR(1), \fBcompress\fR(1), \fBgzip\fR(1)
+\fBamanda\fR(8),
+\fBamdump\fR(8),
+\fBgawk\fR(1),
+\fBnawk\fR(1),
+\fBawk\fR(1),
+\fBgnuplot\fR(1),
+\fBsh\fR(1),
+\fBcompress\fR(1),
+\fBgzip\fR(1)
.IP "\\$1" \\$2
..
.TH "AMRECOVER" 8 "" "" ""
-.SH NAME
-amrecover \- Amanda index database browser
+.SH "NAME"
+amrecover - Amanda index database browser
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 10
-\fBamrecover\fR [[\-C]\ \fIconfig\fR] [\-s\ \fIindex\-server\fR] [\-t\ \fItape\-server\fR] [\-d\ \fItape\-device\fR]
-.ad
-.hy
-
+\fBamrecover\fR [[-C ] \fIconfig\fR] [-s \fIindex-server\fR] [-t \fItape-server\fR] [-d \fItape-device\fR]
.SH "DESCRIPTION"
-
.PP
-\fBAmrecover\fR browses the database of \fBAmanda\fR index files to determine which tapes contain files to recover\&. Furthermore, it is able to recover files\&.
-
+\fBAmrecover\fR
+browses the database of
+\fBAmanda\fR
+index files to determine which tapes contain files to recover. Furthermore, it is able to recover files.
.PP
-In order to restore files in place, you must invoke \fBamrecover\fR from the root of the backed up filesystem, or use \fBlcd\fR to move into that directory, otherwise a directory tree that resembles the backed up filesystem will be created in the current directory\&. See the examples below for details\&.
-
+In order to restore files in place, you must invoke
+\fBamrecover\fR
+from the root of the backed up filesystem, or use
+\fBlcd\fR
+to move into that directory, otherwise a directory tree that resembles the backed up filesystem will be created in the current directory. See the examples below for details.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "OPTIONS"
-
-.RS
-.Sh "Note"
-The Default values are those set at compile\-time\&.
-Use \fBamrestore\fR to recover client\-encrypted or
-client\-custom\-compressed tapes\&.
-.RE
-
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+The Default values are those set at compile-time.
+Use \fBamrestore\fR to recover client-encrypted or
+client-custom-compressed tapes..TP
+\fB[ -C ] config\fR
+\fBAmanda\fR
+configuration.
.TP
-\fB[ \-C ] config\fR
-\fBAmanda\fR configuration\&.
-
+\fB-s index-server\fR
+Host that runs the index daemon.
.TP
-\fB\-s index\-server\fR
-Host that runs the index daemon\&.
-
-.TP
-\fB\-t tape\-server\fR
-Host that runs the tape server daemon\&.
-
+\fB-t tape-server\fR
+Host that runs the tape server daemon.
.TP
-\fB\-d tape\-device\fR
-Tape device to use on the tape server host\&.
-
+\fB-d tape-device\fR
+Tape device to use on the tape server host.
.SH "COMMANDS"
-
.PP
-\fBAmrecover\fR connects to the index server and then presents a command line prompt\&. Usage is similar to an ftp client\&. The GNU readline library is used to provide command line history and editing if it was built in to \fBamrecover\fR\&.
-
+\fBAmrecover\fR
+connects to the index server and then presents a command line prompt. Usage is similar to an ftp client. The GNU readline library is used to provide command line history and editing if it was built in to
+\fBamrecover\fR.
.PP
-The purpose of browsing the database is to build up a \fBrestore list\fR of files to be extracted from the backup system\&. The following commands are available:
-
+The purpose of browsing the database is to build up a
+\fBrestore list\fR
+of files to be extracted from the backup system. The following commands are available:
.TP
\fBsethost hostname\fR
-Specifies which host to look at backup files for (default: the local host)\&.
-
+Specifies which host to look at backup files for (default: the local host).
.TP
-\fBsetdate YYYY\-MM\-DD\fR
-Set the date (default: today)\&. File listing commands only return information on backup images for this day, for the day before with the next lower dump level, and so on, until the most recent level 0 backup on or before the specified date is encountered\&.
-
+\fBsetdate YYYY-MM-DD\fR
+Set the date (default: today). File listing commands only return information on backup images for this day, for the day before with the next lower dump level, and so on, until the most recent level 0 backup on or before the specified date is encountered.
+.sp
For example, if:
-
-
+.sp
.nf
-1996\-07\-01 was a level 0 backup
-1996\-07\-02 through 1996\-07\-05 were level 1 backups
-1996\-07\-06 through 1997\-07\-08 were level 2 backups
+1996-07-01 was a level 0 backup
+1996-07-02 through 1996-07-05 were level 1 backups
+1996-07-06 through 1997-07-08 were level 2 backups
.fi
-then if 1997\-07\-08 is the requested date, files from the following days would be used:
-
-
+.sp
+then if 1997-07-08 is the requested date, files from the following days would be used:
+.sp
.nf
-1997\-07\-08 (the latest level 2 backup)
-1997\-07\-05 (the latest level 1 backup)
-1997\-07\-01 (the latest level 0 backup)
+1997-07-08 (the latest level 2 backup)
+1997-07-05 (the latest level 1 backup)
+1997-07-01 (the latest level 0 backup)
.fi
-Only the most recent version of a file will be presented\&.
-
+.sp
+Only the most recent version of a file will be presented.
+.sp
The following abbreviated date specifications are accepted:
-
.RS
-
.TP
-\fB\-\-MM\-DD\fR
+\fB--MM-DD\fR
dates in the current year
-
.TP
-\fB\-\-\-DD\fR
+\fB---DD\fR
dates in the current month of the current year
-
.RE
-.IP
-
.TP
\fBsetdisk \fIdiskname\fR [\fImountpoint\fR]\fR
-Specifies which disk to consider (default: the disk holding the working directory where \fBamrecover\fR is started)\&. It can only be set after the host is set with \fBsethost\fR\&. \fBDiskname\fR is the device name specified in the \fBamanda\&.conf\fR or \fBdisklist\fR configuration file\&. The disk must be local to the host\&. If \fBmountpoint\fR is not specified, all pathnames will be relative to the (unknown) mount point instead of full pathnames\&.
-
+Specifies which disk to consider (default: the disk holding the working directory where
+\fBamrecover\fR
+is started). It can only be set after the host is set with
+\fBsethost\fR.
+\fBDiskname\fR
+is the device name specified in the
+\fBamanda.conf\fR
+or
+\fBdisklist\fR
+configuration file. The disk must be local to the host. If
+\fBmountpoint\fR
+is not specified, all pathnames will be relative to the (unknown) mount point instead of full pathnames.
.TP
\fBlistdisk [diskdevice]\fR
-List all \fBdiskname\fR
-
+List all
+\fBdiskname\fR
.TP
\fBsettape [[server]:][tapedev|default]\fR
-Specifies the host to use as the tape server, and which of its tape devices to use\&. If the server is omitted, but the colon is not, the server name reverts to the configure\-time default\&. If the tape device is omitted, it remains unchanged\&. To use the default tape device selected by the tape server, the word \fBdefault\fR must be specified\&. If no argument is specified, or the argument is an empty string, no changes occur, and the current settings are displayed\&.
-
-If you want amrecover to use your changer, the \fBtapedev\fR must be equal to the amrecover_changer setting on the server\&.
-
-If you need to change the protocol (tape:, rait:, file:, null:) then you must specify the hostname\&.
-
+Specifies the host to use as the tape server, and which of its tape devices to use. If the server is omitted, but the colon is not, the server name reverts to the configure-time default. If the tape device is omitted, it remains unchanged. To use the default tape device selected by the tape server, the word
+\fBdefault\fR
+must be specified. If no argument is specified, or the argument is an empty string, no changes occur, and the current settings are displayed.
+.sp
+If you want amrecover to use your changer, the
+\fBtapedev\fR
+must be equal to the amrecover_changer setting on the server.
+.sp
+If you need to change the protocol (tape:, rait:, file:, null:) then you must specify the hostname.
.nf
-settape 192\&.168\&.0\&.10:file:/file1
+settape 192.168.0.10:file:/file1
.fi
You can change the tape device when amrecover ask you to load the tape:
.nf
Continue? [Y/n/t]: t
Tape device: server2:/dev/nst2
Continue? [Y/n/t]: Y
-Using tape /dev/nst2 from server server2\&.
+Using tape /dev/nst2 from server server2.
.fi
-
.TP
\fBsetmode mode\fR
-Set the extraction mode for Samba shares\&. If \fBmode\fR is \fBsmb\fR, shares are sent to the Samba server to be restored back onto the PC\&. If \fBmode\fR is \fBtar\fR, they are extracted on the local machine the same way tar volumes are extracted\&.
-
+Set the extraction mode for Samba shares. If
+\fBmode\fR
+is
+\fBsmb\fR, shares are sent to the Samba server to be restored back onto the PC. If
+\fBmode\fR
+is
+\fBtar\fR, they are extracted on the local machine the same way tar volumes are extracted.
.TP
\fBmode\fR
-Displays the extracting mode for Samba shares\&.
-
+Displays the extracting mode for Samba shares.
.TP
\fBhistory\fR
-Show the backup history of the current host and disk\&. Dates, levels, tapes and file position on tape of each backup are displayed\&.
-
+Show the backup history of the current host and disk. Dates, levels, tapes and file position on tape of each backup are displayed.
.TP
\fBpwd\fR
-Display the name of the current backup working directory\&.
-
+Display the name of the current backup working directory.
.TP
\fBcd dir\fR
-Change the backup working directory to \fBdir\&.\fR If the mount point was specified with \fBsetdisk\fR, this can be a full pathname or it can be relative to the current backup working directory\&. If the mount point was not specified, paths are relative to the mount point if they start with "/", otherwise they are relative to the current backup working directory\&. The \fBdir\fR can be a shell style wildcards\&.
-
+Change the backup working directory to
+\fBdir.\fR
+If the mount point was specified with
+\fBsetdisk\fR, this can be a full pathname or it can be relative to the current backup working directory. If the mount point was not specified, paths are relative to the mount point if they start with "/", otherwise they are relative to the current backup working directory. The
+\fBdir\fR
+can be a shell style wildcards.
.TP
\fBcdx dir\fR
-Like the \fBcd\fR command but allow regular expression\&.
-
+Like the
+\fBcd\fR
+command but allow regular expression.
.TP
\fBlpwd\fR
-Display the \fBamrecover\fR working directory\&. Files will be restored under this directory, relative to the backed up filesystem\&.
-
+Display the
+\fBamrecover\fR
+working directory. Files will be restored under this directory, relative to the backed up filesystem.
.TP
\fBlcd path\fR
-Change the \fBamrecover\fR working directory to \fBpath\fR\&.
-
+Change the
+\fBamrecover\fR
+working directory to
+\fBpath\fR.
.TP
\fBls\fR
-List the contents of the current backup working directory\&. See the description of the \fBsetdate\fR command for how the view of the directory is built up\&. The backup date is shown for each file\&.
-
+List the contents of the current backup working directory. See the description of the
+\fBsetdate\fR
+command for how the view of the directory is built up. The backup date is shown for each file.
.TP
-\fBadd item1 item2 \&.\&.\&.\fR
-Add the specified files or directories to the restore list\&. Each item may have shell style wildcards\&.
-
+\fBadd item1 item2 ...\fR
+Add the specified files or directories to the restore list. Each item may have shell style wildcards.
.TP
-\fBaddx item1 item2 \&.\&.\&.\fR
-Add the specified files or directories to the restore list\&. Each item may be a regular expression\&.
-
+\fBaddx item1 item2 ...\fR
+Add the specified files or directories to the restore list. Each item may be a regular expression.
.TP
-\fBdelete item1 item2 \&.\&.\&.\fR
-Delete the specified files or directories from the restore list\&. Each item may have shell style wildcards\&.
-
+\fBdelete item1 item2 ...\fR
+Delete the specified files or directories from the restore list. Each item may have shell style wildcards.
.TP
-\fBdeletex item1 item2 \&.\&.\&.\fR
-Delete the specified files or directories from the restore list\&. Each item may be a regular expression\&.
-
+\fBdeletex item1 item2 ...\fR
+Delete the specified files or directories from the restore list. Each item may be a regular expression.
.TP
\fBlist file\fR
-Display the contents of the restore list\&. If a file name is specified, the restore list is written to that file\&. This can be used to manually extract the files from the \fBAmanda\fR tapes with \fBamrestore\fR\&.
-
+Display the contents of the restore list. If a file name is specified, the restore list is written to that file. This can be used to manually extract the files from the
+\fBAmanda\fR
+tapes with
+\fBamrestore\fR.
.TP
\fBclear\fR
-Clear the restore list\&.
-
+Clear the restore list.
.TP
\fBquit\fR
-Close the connection to the index server and exit\&.
-
+Close the connection to the index server and exit.
.TP
\fBexit\fR
-Close the connection to the index server and exit\&.
-
+Close the connection to the index server and exit.
.TP
\fBextract\fR
-Start the extract sequence (see the examples below)\&. Make sure the local working directory is the root of the backed up filesystem, or another directory that will behave like that\&. Use \fBlpwd\fR to display the local working directory, and \fBlcd\fR to change it\&.
-
+Start the extract sequence (see the examples below). Make sure the local working directory is the root of the backed up filesystem, or another directory that will behave like that. Use
+\fBlpwd\fR
+to display the local working directory, and
+\fBlcd\fR
+to change it.
.TP
\fBhelp\fR
-Display a brief list of these commands\&.
-
+Display a brief list of these commands.
.SH "EXAMPLES"
-
.PP
-The following shows the recovery of an old \fBsyslog\fR file\&.
+The following shows the recovery of an old
+\fBsyslog\fR
+file.
.nf
# cd /var/log
-# ls \-l syslog\&.7
-syslog\&.7: No such file or directory
+# ls -l syslog.7
+syslog.7: No such file or directory
# amrecover
-AMRECOVER Version 2\&.4\&.2\&. Contacting server on oops \&.\&.\&.
-220 oops \fBAmanda\fR index server (2\&.4\&.2) ready\&.
-Setting restore date to today (1997\-12\-09)
-200 Working date set to 1997\-12\-09\&.
-200 Config set to daily\&.
-200 Dump host set to this\-host\&.some\&.org\&.
-$CWD '/var/log' is on disk '/var' mounted at '/var'\&.
-200 Disk set to /var\&.
+AMRECOVER Version 2.4.2. Contacting server on oops ...
+220 oops \fBAmanda\fR index server (2.4.2) ready.
+Setting restore date to today (1997-12-09)
+200 Working date set to 1997-12-09.
+200 Config set to daily.
+200 Dump host set to this-host.some.org.
+$CWD '/var/log' is on disk '/var' mounted at '/var'.
+200 Disk set to /var.
/var/log
-WARNING: not on root of selected filesystem, check man\-page!
+WARNING: not on root of selected filesystem, check man-page!
amrecover> ls
-1997\-12\-09 daemon\&.log
-1997\-12\-09 syslog
-1997\-12\-08 authlog
-1997\-12\-08 sysidconfig\&.log
-1997\-12\-08 syslog\&.0
-1997\-12\-08 syslog\&.1
-1997\-12\-08 syslog\&.2
-1997\-12\-08 syslog\&.3
-1997\-12\-08 syslog\&.4
-1997\-12\-08 syslog\&.5
-1997\-12\-08 syslog\&.6
-1997\-12\-08 syslog\&.7
-amrecover> add syslog\&.7
-Added /log/syslog\&.7
+1997-12-09 daemon.log
+1997-12-09 syslog
+1997-12-08 authlog
+1997-12-08 sysidconfig.log
+1997-12-08 syslog.0
+1997-12-08 syslog.1
+1997-12-08 syslog.2
+1997-12-08 syslog.3
+1997-12-08 syslog.4
+1997-12-08 syslog.5
+1997-12-08 syslog.6
+1997-12-08 syslog.7
+amrecover> add syslog.7
+Added /log/syslog.7
amrecover> lpwd
/var/log
-amrecover> lcd \&.\&.
+amrecover> lcd ..
/var
amrecover> extract
-Extracting files using tape drive /dev/nst0 on host 192\&.168\&.0\&.10
+Extracting files using tape drive /dev/nst0 on host 192.168.0.10
The following tapes are needed: DMP014
Load tape DMP014 now
Continue? [Y/n/t]: y
-set owner/mode for '\&.'? [yn] n
+set owner/mode for '.'? [yn] n
amrecover> quit
-200 Good bye\&.
-# ls \-l syslog\&.7
+200 Good bye.
+# ls -l syslog.7
total 26
-\-rw\-r\-\-r\-\- 1 root other 12678 Oct 14 16:36 syslog\&.7
+-rw-r--r-- 1 root other 12678 Oct 14 16:36 syslog.7
.fi
-
.PP
-If you do not want to overwrite existing files, create a subdirectory to run \fBamrecover\fR from and then move the restored files afterward\&.
+If you do not want to overwrite existing files, create a subdirectory to run
+\fBamrecover\fR
+from and then move the restored files afterward.
.nf
# cd /var
-# (umask 077 ; mkdir \&.restore)
-# cd \&.restore
+# (umask 077 ; mkdir .restore)
+# cd .restore
# amrecover
-AMRECOVER Version 2\&.4\&.2\&. Contacting server on oops \&.\&.\&.
-\&.\&.\&.
+AMRECOVER Version 2.4.2. Contacting server on oops ...
+...
amrecover> cd log
/var/log
amrecover> ls
-\&.\&.\&.
-amrecover> add syslog\&.7
-Added /log/syslog\&.7
+...
+amrecover> add syslog.7
+Added /log/syslog.7
amrecover> lpwd
-/var/\&.restore
+/var/.restore
amrecover> extract
-Extracting files using tape drive /dev/nst0 on host 192\&.168\&.0\&.10
-\&.\&.\&.
+Extracting files using tape drive /dev/nst0 on host 192.168.0.10
+...
amrecover> quit
-200 Good bye\&.
-# mv \-i log/syslog\&.7 \&.\&./log/syslog\&.7\-restored
-# cd \&.\&.
-# rm \-fr \&.restore
+200 Good bye.
+# mv -i log/syslog.7 ../log/syslog.7-restored
+# cd ..
+# rm -fr .restore
.fi
-
.PP
-If you need to run \fBamrestore\fR by hand instead of letting \fBamrecover\fR control it, use the \fBlist\fR command after browsing to display the needed tapes\&.
+If you need to run
+\fBamrestore\fR
+by hand instead of letting
+\fBamrecover\fR
+control it, use the
+\fBlist\fR
+command after browsing to display the needed tapes.
.nf
# cd /var/log
# amrecover
-AMRECOVER Version 2\&.4\&.2\&. Contacting server on oops \&.\&.\&.
-\&.\&.\&.
+AMRECOVER Version 2.4.2. Contacting server on oops ...
+...
amrecover> ls
-\&.\&.\&.
-amrecover> add syslog syslog\&.6 syslog\&.7
+...
+amrecover> add syslog syslog.6 syslog.7
Added /log/syslog
-Added /log/syslog\&.6
-Added /log/syslog\&.7
+Added /log/syslog.6
+Added /log/syslog.7
amrecover> list
-TAPE DMP014 LEVEL 0 DATE 1997\-12\-08
- /log/syslog\&.7
- /log/syslog\&.6
-TAPE DMP015 LEVEL 1 DATE 1997\-12\-09
+TAPE DMP014 LEVEL 0 DATE 1997-12-08
+ /log/syslog.7
+ /log/syslog.6
+TAPE DMP015 LEVEL 1 DATE 1997-12-09
/log/syslog
amrecover> quit
.fi
-
.PP
-The \fBhistory\fR command shows each tape that has a backup of the current disk along with the date of the backup, the level, the tape label and the file position on the tape\&. All active tapes are listed, not just back to the most recent full dump\&.
-
+The
+\fBhistory\fR
+command shows each tape that has a backup of the current disk along with the date of the backup, the level, the tape label and the file position on the tape. All active tapes are listed, not just back to the most recent full dump.
.PP
-Tape file position zero is a label\&. The first backup image is in file position one\&.
+Tape file position zero is a label. The first backup image is in file position one.
.nf
# cd /var/log
# amrecover
-AMRECOVER Version 2\&.4\&.2\&. Contacting server on oops \&.\&.\&.
-\&.\&.\&.
+AMRECOVER Version 2.4.2. Contacting server on oops ...
+...
amrecover> history
-200\- Dump history for config "daily" host "this\-host\&.some\&.org" disk "/var"
-201\- 1997\-12\-09 1 DMP015 9
-201\- 1997\-12\-08 1 DMP014 11
-201\- 1997\-12\-07 0 DMP013 22
-201\- 1997\-12\-06 1 DMP012 16
-201\- 1997\-12\-05 1 DMP011 9
-201\- 1997\-12\-04 0 DMP010 11
-201\- 1997\-12\-03 1 DMP009 7
-201\- 1997\-12\-02 1 DMP008 7
-201\- 1997\-12\-01 1 DMP007 9
-201\- 1997\-11\-30 1 DMP006 6
-\&.\&.\&.
+200- Dump history for config "daily" host "this-host.some.org" disk "/var"
+201- 1997-12-09 1 DMP015 9
+201- 1997-12-08 1 DMP014 11
+201- 1997-12-07 0 DMP013 22
+201- 1997-12-06 1 DMP012 16
+201- 1997-12-05 1 DMP011 9
+201- 1997-12-04 0 DMP010 11
+201- 1997-12-03 1 DMP009 7
+201- 1997-12-02 1 DMP008 7
+201- 1997-12-01 1 DMP007 9
+201- 1997-11-30 1 DMP006 6
+...
amrecover> quit
.fi
-
.SH "ENVIRONMENT"
-
.PP
-\fBPAGER\fR The \fBls\fR and \fBlist\fR commands will use $PAGER to display the file lists\&. Defaults to \fBmore\fR if PAGER is not set\&.
-
+\fBPAGER\fRThe
+\fBls\fR
+and
+\fBlist\fR
+commands will use $PAGER to display the file lists. Defaults to
+\fBmore\fR
+if PAGER is not set.
.SH "AUTHOR"
-
.PP
-Alan M\&. McIvor <alan@kauri\&.auck\&.irl\&.cri\&.nz> : Original text
-
+Alan M. McIvor
+<alan@kauri.auck.irl.cri.nz>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamrestore\fR(8), \fBamfetchdump\fR(8), \fBreadline\fR(3)
+\fBamanda\fR(8),
+\fBamrestore\fR(8),
+\fBamfetchdump\fR(8),
+\fBreadline\fR(3)
.IP "\\$1" \\$2
..
.TH "AMREPORT" 8 "" "" ""
-.SH NAME
-amreport \- generate a formatted output of statistics for an Amanda run
+.SH "NAME"
+amreport - generate a formatted output of statistics for an Amanda run
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 9
-\fBamreport\fR [\fIconfig\fR] [\-l\ \fIlogfile\fR] [\-f\ \fIoutputfile\fR] [\-p\ \fIpostscriptfile\fR]
-.ad
-.hy
-
+\fBamreport\fR [\fIconfig\fR] [-l \fIlogfile\fR] [-f \fIoutputfile\fR] [-p \fIpostscriptfile\fR]
.SH "DESCRIPTION"
-
.PP
-\fBAmreport\fR generates a summary report of an \fBamanda\fR(8) backup run\&. If no configuration name is specified, amanda\&.conf is read from the current directory\&.
-
+\fBAmreport\fR
+generates a summary report of an
+\fBamanda\fR(8)
+backup run. If no configuration name is specified, amanda.conf is read from the current directory.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "OPTIONS"
-
.TP
\fBconfig\fR
-Name of the configuration to process\&.
-
+Name of the configuration to process.
.TP
-\fB\-l\fR \fIlogfile\fR
-Name of the log file to parse to generate the report\&. If a log file is not specified, it defaults to the file:
-
+\fB-l\fR \fIlogfile\fR
+Name of the log file to parse to generate the report. If a log file is not specified, it defaults to the file:
.PP
\fBlogdir\fR/log
-
.PP
-where \fBlogdir\fR is the log directory defined in amanda\&.conf\&.
-
+where
+\fBlogdir\fR
+is the log directory defined in amanda.conf.
.TP
-\fB\-f\fR \fIoutputfile\fR
-Normally, \fBamreport\fR sends the report via e\-mail to the \fBmailto\fR user as defined in the amanda\&.conf file\&. If \fBoutputfile\fR is specified, then the report is put in \fBoutputfile\fR\&.
-
+\fB-f\fR \fIoutputfile\fR
+Normally,
+\fBamreport\fR
+sends the report via e-mail to the
+\fBmailto\fR
+user as defined in the amanda.conf file. If
+\fBoutputfile\fR
+is specified, then the report is put in
+\fBoutputfile\fR.
.TP
-\fB\-p\fR \fIpostscriptfile\fR
-Send the postscript output to the file \fBpostscriptfile\fR instead of to the \fBlpr\fR(1) command\&. This option has an effect only if the \fBlbl\-templ\fR directive is specified in amanda\&.conf\&.
-
+\fB-p\fR \fIpostscriptfile\fR
+Send the postscript output to the file
+\fBpostscriptfile\fR
+instead of to the
+\fBlpr\fR(1)
+command. This option has an effect only if the
+\fBlbl-templ\fR
+directive is specified in amanda.conf.
.SH "LABEL PRINTING"
-
.PP
-\fBAmanda\fR can print postscript labels describing the contents of tape(s) written in a run\&. The labels are designed to be folded and inserted into the tape case along with the tape or hole punched and put in a 3\-ring binder\&. Various label templates are provided to format data for different tape sizes\&.
-
+\fBAmanda\fR
+can print postscript labels describing the contents of tape(s) written in a run. The labels are designed to be folded and inserted into the tape case along with the tape or hole punched and put in a 3-ring binder. Various label templates are provided to format data for different tape sizes.
.PP
-The information printed varies slightly between label templates due to size constraints\&. Labels contain one line for each host/file\-system pair and may also contain the file number on the tape, the level of the dump, the original size of the dump and the size of the (possibly compressed) tape file\&.
-
+The information printed varies slightly between label templates due to size constraints. Labels contain one line for each host/file-system pair and may also contain the file number on the tape, the level of the dump, the original size of the dump and the size of the (possibly compressed) tape file.
.PP
-Add the \fBlbl\-templ\fR parameter to the tapetype definition in amanda\&.conf to enable labels\&. If you don't add this line to your tapetype definition, \fBamreport\fR will not print tape labels\&.
-
+Add the
+\fBlbl-templ\fR
+parameter to the tapetype definition in amanda.conf to enable labels. If you don't add this line to your tapetype definition,
+\fBamreport\fR
+will not print tape labels.
.PP
-You may use the \fBremap='I'>printer\fR keyword in amanda\&.conf to print to other than the system default printer\&.
-
+You may use the
+\fBremap='I'>printer\fR
+keyword in amanda.conf to print to other than the system default printer.
.SH "TEMPLATES"
-
.PP
-\fBAmanda\fR provides label templates for the following tape types\&. These are pretty generic labels and should be easy to customize for other tape types or particular site needs\&.
-
+\fBAmanda\fR
+provides label templates for the following tape types. These are pretty generic labels and should be easy to customize for other tape types or particular site needs.
+.sp
.nf
* ExaByte 8mm tapes
* DAT 4mm tapes
* DLT tapes
-* 3\-ring binder
+* 3-ring binder
.fi
-
+.sp
.PP
-The 3\-ring binder type is the most generic\&. It may be used to make a hardcopy log of the tapes\&.
-
+The 3-ring binder type is the most generic. It may be used to make a hardcopy log of the tapes.
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamflush\fR(8)
+\fBamanda\fR(8),
+\fBamflush\fR(8)
.IP "\\$1" \\$2
..
.TH "AMRESTORE" 8 "" "" ""
-.SH NAME
-amrestore \- extract backup images from an Amanda tape
+.SH "NAME"
+amrestore - extract backup images from an Amanda tape
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 10
-\fBamrestore\fR [\fB\-r\fR | \fB\-c\fR | \fB\-C\fR] [\-b\ \fIblocksize\fR] [\-f\ \fIfileno\fR] [\-l\ \fIlabel\fR] [\-p] [\-h] \fB\fItapedevice\fR\fR | \fB\fIholdingfile\fR\fR | \fB\fIhostname\fR\ [\fIdiskname\fR\ [\fIdatestamp\fR\ [\fIhostname\fR\ [\fIdiskname\fR\ [\fIdatestamp\fR...]]]]]\fR
-.ad
-.hy
-
+\fBamrestore\fR [-r -c -C] [-b \fIblocksize\fR] [-f \fIfileno\fR] [-l \fIlabel\fR] [-p] [-h] \fItapedevice\fR \fIholdingfile\fR [\fIhostname\fR [\fIdiskname\fR [\fIdatestamp\fR [\fIhostname\fR [\fIdiskname\fR [\fIdatestamp\fR...]]]]]]
.SH "DESCRIPTION"
-
-.PP
-\fBAmrestore\fR extracts backup images from the tape mounted on \fBtapedevice\fR or from the holding disk file \fBholdingfile\fR that match \fBhostname\fR, \fBdiskname\fR and \fBdatestamp\fR patterns given on the command line\&. The tape or holding file must be in a format written by the \fBamdump\fR or \fBamflush\fR program\&.
-
-.PP
-If \fBdiskname\fR is not specified, all backups on the tape for the previous \fBhostname\fR are candidates\&. If \fBdatestamp\fR is not specified, all backups on the tape for the previous \fBhostname\fR and \fBdiskname\fR are candidates\&. If no \fBhostname\fR, \fBdiskname\fR or \fBdatestamp\fR are specified, every backup on the tape is a candidate\&.
-
-.PP
-\fBHostname\fR and \fBdiskname\fR are special expressions described in the "HOST & DISK EXPRESSION" section of \fBamanda\fR(8)\&. \fBDatestamp\fR are special expression described in the "DATESTAMP EXPRESSION" section of \fBamanda\fR(8)\&. For example, if \fBdiskname\fR is "rz[23]a", it would match disks \fBrz2a\fR and \fBrz3a\fR\&.
-
-.PP
-\fBDatestamp\fR is useful if \fBamflush\fR writes multiple backup runs to a single tape\&.
-
-.PP
-Unless \fB\-p\fR is used, candidate backup images are extracted to files in the current directory named:
-
.PP
-\fBhostname\&.diskname\&.datestamp\&.dumplevel\fR
-
-.PP
-Amrestore doesn't use a changer, it restore from the tape already loaded in the \fBtapedevice\&.\fR
-
+\fBAmrestore\fR
+extracts backup images from the tape mounted on
+\fBtapedevice\fR
+or from the holding disk file
+\fBholdingfile\fR
+that match
+\fBhostname\fR,
+\fBdiskname\fR
+and
+\fBdatestamp\fR
+patterns given on the command line. The tape or holding file must be in a format written by the
+\fBamdump\fR
+or
+\fBamflush\fR
+program.
+.PP
+If
+\fBdiskname\fR
+is not specified, all backups on the tape for the previous
+\fBhostname\fR
+are candidates. If
+\fBdatestamp\fR
+is not specified, all backups on the tape for the previous
+\fBhostname\fR
+and
+\fBdiskname\fR
+are candidates. If no
+\fBhostname\fR,
+\fBdiskname\fR
+or
+\fBdatestamp\fR
+are specified, every backup on the tape is a candidate.
+.PP
+\fBHostname\fR
+and
+\fBdiskname\fR
+are special expressions described in the "HOST & DISK EXPRESSION" section of
+\fBamanda\fR(8).
+\fBDatestamp\fR
+are special expression described in the "DATESTAMP EXPRESSION" section of
+\fBamanda\fR(8). For example, if
+\fBdiskname\fR
+is "rz[23]a", it would match disks
+\fBrz2a\fR
+and
+\fBrz3a\fR.
+.PP
+\fBDatestamp\fR
+is useful if
+\fBamflush\fR
+writes multiple backup runs to a single tape.
+.PP
+Unless
+\fB-p\fR
+is used, candidate backup images are extracted to files in the current directory named:
+.PP
+\fBhostname.diskname.datestamp.dumplevel\fR
+.PP
+Amrestore doesn't use a changer, it restore from the tape already loaded in the
+\fBtapedevice.\fR
.SH "OPTIONS"
-
.TP
-\fB\-b\fR
-Set the blocksize used to read the tape or holding file\&. All holding files must be read with a blocksize of 32 KBytes\&. \fBAmrestore\fR should normally be able to determine the blocksize for tapes on its own and not need this parameter\&.
-
+\fB-b\fR
+Set the blocksize used to read the tape or holding file. All holding files must be read with a blocksize of 32 KBytes.
+\fBAmrestore\fR
+should normally be able to determine the blocksize for tapes on its own and not need this parameter.
.PP
-The default is 32 KBytes\&.
-
+The default is 32 KBytes.
.TP
-\fB\-f\fR
-Do a rewind followed by a fsf <fileno> before trying to restore an image\&.
-
+\fB-f\fR
+Do a rewind followed by a fsf <fileno> before trying to restore an image.
.TP
-\fB\-l\fR
-Check if we restoring from the tape with the right \fBlabel\fR
-
+\fB-l\fR
+Check if we restoring from the tape with the right
+\fBlabel\fR
.TP
-\fB\-p\fR
-Pipe output\&. The first matching backup image is sent to standard output, which is normally a pipe to \fBrestore\fR or \fBtar\fR, then \fBamrestore\fR quits\&. It may be run again to continue selecting backups to process\&. Make sure you specify the no\-rewind \fBtapedevice\fR when doing this\&.
-
-.PP
-Note: \fBrestore\fR may report "short read" errors when reading from a pipe\&. Most versions of \fBrestore\fR support a blocking factor option to let you set the read block size, and you should set it to 2\&. See the example below\&.
-
+\fB-p\fR
+Pipe output. The first matching backup image is sent to standard output, which is normally a pipe to
+\fBrestore\fR
+or
+\fBtar\fR, then
+\fBamrestore\fR
+quits. It may be run again to continue selecting backups to process. Make sure you specify the no-rewind
+\fBtapedevice\fR
+when doing this.
+.PP
+Note:
+\fBrestore\fR
+may report "short read" errors when reading from a pipe. Most versions of
+\fBrestore\fR
+support a blocking factor option to let you set the read block size, and you should set it to 2. See the example below.
.TP
-\fB\-c\fR
-Compress output using the fastest method the compression program provides\&. \fBAmrestore\fR normally writes output files in a format understood by \fBrestore\fR or \fBtar\fR, even if the backups on the tape are compressed\&. With the \fB\-c\fR or \fB\-C\fR option, \fBamrestore\fR writes all files in compressed format, even if the backups on the tape are not compressed\&. Output file names will have a \&.Z or \&.gz extension depending on whether \fBcompress\fR or \fBgzip\fR is the preferred compression program\&. This option is useful when the current directory disk is small\&.
-
+\fB-c\fR
+Compress output using the fastest method the compression program provides.
+\fBAmrestore\fR
+normally writes output files in a format understood by
+\fBrestore\fR
+or
+\fBtar\fR, even if the backups on the tape are compressed. With the
+\fB-c\fR
+or
+\fB-C\fR
+option,
+\fBamrestore\fR
+writes all files in compressed format, even if the backups on the tape are not compressed. Output file names will have a
+.Z
+or
+.gz
+extension depending on whether
+\fBcompress\fR
+or
+\fBgzip\fR
+is the preferred compression program. This option is useful when the current directory disk is small.
.TP
-\fB\-C\fR
-Compress output using the best method the compression program provides (may be very CPU intensive)\&. See the notes above about the \fB\-c\fR option\&.
-
+\fB-C\fR
+Compress output using the best method the compression program provides (may be very CPU intensive). See the notes above about the
+\fB-c\fR
+option.
.TP
-\fB\-r\fR
-Raw output\&. Backup images are output exactly as they are on the tape, including the \fBamdump\fR headers\&. Output file names will have a \&.RAW extension\&. This option is only useful for debugging and other strange circumstances\&.
-
+\fB-r\fR
+Raw output. Backup images are output exactly as they are on the tape, including the
+\fBamdump\fR
+headers. Output file names will have a
+.RAW
+extension. This option is only useful for debugging and other strange circumstances.
.TP
-\fB\-h\fR
-Header output\&. The tape header block is output at the beginning of each file\&. This is like \fB\-r\fR except \fB\-c\fR or \fB\-C\fR may also be used to compress the result\&. \fBAmrecover\fR uses the header to determine the restore program to use\&.
-
-.PP
-If a header is written (\-r or \-h), only 32 KBytes are output regardless of the tape blocksize\&. This makes the resulting image usable as a holding file\&.
-
+\fB-h\fR
+Header output. The tape header block is output at the beginning of each file. This is like
+\fB-r\fR
+except
+\fB-c\fR
+or
+\fB-C\fR
+may also be used to compress the result.
+\fBAmrecover\fR
+uses the header to determine the restore program to use.
+.PP
+If a header is written (-r or -h), only 32 KBytes are output regardless of the tape blocksize. This makes the resulting image usable as a holding file.
.SH "EXAMPLES"
-
.PP
-The following does an interactive restore of disk \fBrz3g\fR from host \fBseine\fR, to restore particular files\&. Note the use of the \fBb\fR option to \fBrestore\fR, which causes it to read in units of two 512\-byte blocks (1 Kbyte) at a time\&. This helps keep it from complaining about short reads\&.
-
+The following does an interactive restore of disk
+\fBrz3g\fR
+from host
+\fBseine\fR, to restore particular files. Note the use of the
+\fBb\fR
+option to
+\fBrestore\fR, which causes it to read in units of two 512-byte blocks (1 Kbyte) at a time. This helps keep it from complaining about short reads.
+.sp
.nf
-% amrestore \-p /dev/nrmt9 seine rz3g | restore \-ivbf 2 \-
+% amrestore -p /dev/nrmt9 seine rz3g | restore -ivbf 2 -
.fi
-
+.sp
.PP
-The next example extracts all backup images for host \fBseine\fR\&. This is the usual way to extract all data for a host after a disk crash\&.
-
+The next example extracts all backup images for host
+\fBseine\fR. This is the usual way to extract all data for a host after a disk crash.
+.sp
.nf
% amrestore /dev/nrmt9 seine
.fi
-
-.PP
-If the backup datestamp in the above example is 19910125 and \fBseine\fR has level 0 backups of disks \fBrz1a\fR and \fBrz1g\fR on the tape, these files will be created in the current directory:
-
+.sp
+.PP
+If the backup datestamp in the above example is
+19910125
+and
+\fBseine\fR
+has level 0 backups of disks
+\fBrz1a\fR
+and
+\fBrz1g\fR
+on the tape, these files will be created in the current directory:
+.sp
.nf
-seine\&.rz1a\&.19910125\&.0
-seine\&.rz1g\&.19910125\&.0
+seine.rz1a.19910125.0
+seine.rz1g.19910125.0
.fi
-
+.sp
.PP
-You may also use \fBamrestore\fR to extract a backup image from a holding disk file that has not yet been flushed to tape:
-
+You may also use
+\fBamrestore\fR
+to extract a backup image from a holding disk file that has not yet been flushed to tape:
+.sp
.nf
-% amrestore \-p /amanda/20001119/seine\&.rz1a\&.2 | restore \-ivbf 2 \-
+% amrestore -p /amanda/20001119/seine.rz1a.2 | restore -ivbf 2 -
.fi
-
+.sp
.PP
-\fBAmrestore\fR may be used to generate a listing of images on a tape:
-
+\fBAmrestore\fR
+may be used to generate a listing of images on a tape:
+.sp
.nf
-% mt \-f /dev/nrmt9 rewind
-% amrestore \-p /dev/nrmt9 no\-such\-host > /dev/null
+% mt -f /dev/nrmt9 rewind
+% amrestore -p /dev/nrmt9 no-such-host > /dev/null
.fi
-
+.sp
.PP
-This asks \fBamrestore\fR to find images for host \fBno\-such\-host\fR\&. It will not find any entries that match, but along the way will report each image it skips\&.
-
+This asks
+\fBamrestore\fR
+to find images for host
+\fBno-such-host\fR. It will not find any entries that match, but along the way will report each image it skips.
.SH "CAVEATS"
-
.PP
-\fBGNU\-tar\fR must be used to restore files from backup images created with the GNUTAR dumptype\&. Vendor tar programs sometimes fail to read GNU tar images\&.
-
+\fBGNU-tar\fR
+must be used to restore files from backup images created with the GNUTAR dumptype. Vendor tar programs sometimes fail to read GNU tar images.
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org>, University of Maryland, College Park: Original text
-
+James da Silva,
+<jds@amanda.org>, University of Maryland, College Park: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamdump\fR(8), \fBamflush\fR(8), \fBtar\fR(1) \fBrestore\fR(8)
+\fBamanda\fR(8),
+\fBamdump\fR(8),
+\fBamflush\fR(8),
+\fBtar\fR(1)\fBrestore\fR(8)
.IP "\\$1" \\$2
..
.TH "AMRMTAPE" 8 "" "" ""
-.SH NAME
-amrmtape \- remove a tape from the Amanda database
+.SH "NAME"
+amrmtape - remove a tape from the Amanda database
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 9
-\fBamrmtape\fR [\-n] [\-v] [\-q] [\-d] \fIconfig\fR \fIlabel\fR
-.ad
-.hy
-
+\fBamrmtape\fR [-n] [-v] [-q] [-d] \fIconfig\fR \fIlabel\fR
.SH "DESCRIPTION"
-
.PP
-\fBAmrmtape\fR invalidates the contents of an existing backup tape in the configuration database\&. This is meant as a recovery mechanism when a good backup is damaged either by faulty hardware or user error, e\&.g\&. the tape is eaten by the drive or is overwritten\&.
-
+\fBAmrmtape\fR
+invalidates the contents of an existing backup tape in the configuration database. This is meant as a recovery mechanism when a good backup is damaged either by faulty hardware or user error, e.g. the tape is eaten by the drive or is overwritten.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "OPTIONS"
-
.TP
-\fB\-n\fR
-Generate new \fBtapelist\fR and database files with \fBlabel\fR removed, but leave them in \fI/tmp\fR and do not update the original copies\&.
-
+\fB-n\fR
+Generate new
+\fBtapelist\fR
+and database files with
+\fBlabel\fR
+removed, but leave them in
+\fI/tmp\fR
+and do not update the original copies.
.TP
-\fB\-v\fR
-List backups of hosts and disks that are being discarded\&. Enabled by default\&.
-
+\fB-v\fR
+List backups of hosts and disks that are being discarded. Enabled by default.
.TP
-\fB\-q\fR
-Opposite of \fB\-v\fR\&.
-
+\fB-q\fR
+Opposite of
+\fB-v\fR.
.TP
-\fB\-d\fR
-Run in debugging mode so all executed commands are shown\&.
-
+\fB-d\fR
+Run in debugging mode so all executed commands are shown.
.SH "EXAMPLE"
-
.PP
-Remove tape labeled \fBDAILY034\fR from the \fBDailySet1\fR configuration\&.
+Remove tape labeled
+\fBDAILY034\fR
+from the
+\fBDailySet1\fR
+configuration.
.nf
# amrmtape DailySet1 DAILY034
.fi
-
.SH "AUTHOR"
-
.PP
-Adrian T\&. Filipi\-Martin <atf3r@cs\&.virginia\&.edu>: Original text
-
+Adrian T. Filipi-Martin
+<atf3r@cs.virginia.edu>: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamadmin\fR(8), \fBamanda\fR(8)
+\fBamadmin\fR(8),
+\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMSTATUS" 8 "" "" ""
-.SH NAME
-amstatus \- display the state of an Amanda run
+.SH "NAME"
+amstatus - display the state of an Amanda run
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 9
-\fBamstatus\fR [\-\-config] \fIconfig\fR [\-\-file\ \fIamdumpfile\fR] [\-\-summary] [\-\-dumping] [\-\-waitdumping] [\-\-waittaper] [\-\-dumpingtape] [\-\-writingtape] [\-\-finished] [\-\-failed] [\-\-estimate] [\-\-gestimate] [\-\-stats]
-.ad
-.hy
-
+\fBamstatus\fR [--config] \fIconfig\fR [--file \fIamdumpfile\fR] [--summary] [--dumping] [--waitdumping] [--waittaper] [--dumpingtape] [--writingtape] [--finished] [--failed] [--estimate] [--gestimate] [--stats]
.SH "DESCRIPTION"
-
.PP
-\fBAmstatus\fR gives the current state of the \fBAmanda\fR run specified by the \fBconfig\fR configuration\&. If there is no active \fBAmanda\fR running, it summarizes the result of the last run\&. It may also be used to summarize the results of a previous run\&.
-
+\fBAmstatus\fR
+gives the current state of the
+\fBAmanda\fR
+run specified by the
+\fBconfig\fR
+configuration. If there is no active
+\fBAmanda\fR
+running, it summarizes the result of the last run. It may also be used to summarize the results of a previous run.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "OPTIONS"
-
.PP
-All options may be abbreviated to the shortest non\-ambiguous sub\-string\&. If no options are given, everything is displayed\&.
-
+All options may be abbreviated to the shortest non-ambiguous sub-string. If no options are given, everything is displayed.
.TP
-\fB[\-\-config] config\fR
-Specify the \fBAmanda\fR configuration you want to display the state for\&.
-
+\fB[--config] config\fR
+Specify the
+\fBAmanda\fR
+configuration you want to display the state for.
.TP
-\fB\-\-file amdumpfile\fR
-Specify an alternate file instead of the \fBamdump\fR or \fBamflush\fR file\&.
-
+\fB--file amdumpfile\fR
+Specify an alternate file instead of the
+\fBamdump\fR
+or
+\fBamflush\fR
+file.
.TP
-\fB\-\-summary\fR
-Display a summary of the state of the run\&.
-
+\fB--summary\fR
+Display a summary of the state of the run.
.TP
-\fB\-\-dumping\fR
-Display all partitions that are dumping\&.
-
+\fB--dumping\fR
+Display all partitions that are dumping.
.TP
-\fB\-\-waitdumping|wdumping\fR
-Display all partitions that are waiting to be dumped\&.
-
+\fB--waitdumping|wdumping\fR
+Display all partitions that are waiting to be dumped.
.TP
-\fB\-\-waittaper|wtaper\fR
-Display all partitions dumped that are waiting to be written to tape\&.
-
+\fB--waittaper|wtaper\fR
+Display all partitions dumped that are waiting to be written to tape.
.TP
-\fB\-\-dumpingtape|dtape\fR
-Display all partitions that are dumping directly to tape\&.
-
+\fB--dumpingtape|dtape\fR
+Display all partitions that are dumping directly to tape.
.TP
-\fB\-\-writingtape|wtape\fR
-Display all partitions that are writing to tape\&.
-
+\fB--writingtape|wtape\fR
+Display all partitions that are writing to tape.
.TP
-\fB\-\-finished\fR
-Display all partitions that are dumped and written to tape\&.
-
+\fB--finished\fR
+Display all partitions that are dumped and written to tape.
.TP
-\fB\-\-failed|error\fR
-Display all partitions that failed\&.
-
+\fB--failed|error\fR
+Display all partitions that failed.
.TP
-\fB\-\-estimate\fR
-Display all partitions whose estimate is finished\&. Works only during the estimate phase\&.
-
+\fB--estimate\fR
+Display all partitions whose estimate is finished. Works only during the estimate phase.
.TP
-\fB\-\-gestimate|gettingestimate\fR
-Display all partitions whose estimate is not finished\&. Works only during the estimate phase\&.
-
+\fB--gestimate|gettingestimate\fR
+Display all partitions whose estimate is not finished. Works only during the estimate phase.
.TP
-\fB\-\-stats|statistics\fR
-Display statistics about active\-time of taper and dumpers\&.
-
+\fB--stats|statistics\fR
+Display statistics about active-time of taper and dumpers.
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamcheck\fR(8), \fBamdump\fR(8), \fBamrestore\fR(8), \fBamadmin\fR(8)
+\fBamanda\fR(8),
+\fBamcheck\fR(8),
+\fBamdump\fR(8),
+\fBamrestore\fR(8),
+\fBamadmin\fR(8)
.IP "\\$1" \\$2
..
.TH "AMTAPE" 8 "" "" ""
-.SH NAME
-amtape \- user interface to Amanda tape changer controls
+.SH "NAME"
+amtape - user interface to Amanda tape changer controls
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 7
-\fBamtape\fR \fIconfig\fR \fIcommand\fR [\fIcommand\fR\ \fIoptions\fR]
-.ad
-.hy
-
+\fBamtape\fR \fIconfig\fR \fIcommand\fR [\fIcommand\fRÂ \fIoptions\fR]
.SH "DESCRIPTION"
-
.PP
-\fBAmtape\fR performs tape changer control operations\&. It uses the underlying tape changer script defined by the \fBtpchanger\fR option for a particular \fBAmanda\fR configuration as specified by the \fBconfig\fR argument\&.
-
+\fBAmtape\fR
+performs tape changer control operations. It uses the underlying tape changer script defined by the
+\fBtpchanger\fR
+option for a particular
+\fBAmanda\fR
+configuration as specified by the
+\fBconfig\fR
+argument.
.PP
-Tape changers maintain a notion of the \fBcurrent\fR and \fBnext\fR slot for each configuration\&. These may or may not correspond to an actual physical state of the device, but do tend to minimize searching through the tape storage slots\&. If the desired tape is in the current slot, it is likely the next tape needed is in the next slot rather than at some random position in the storage slots\&.
-
+Tape changers maintain a notion of the
+\fBcurrent\fR
+and
+\fBnext\fR
+slot for each configuration. These may or may not correspond to an actual physical state of the device, but do tend to minimize searching through the tape storage slots. If the desired tape is in the current slot, it is likely the next tape needed is in the next slot rather than at some random position in the storage slots.
.PP
-See the \fBamanda\fR(8) man page for more details about \fBAmanda\fR\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about
+\fBAmanda\fR.
.SH "COMMANDS"
-
.TP
\fBreset\fR
-Reset the tape changer to a known state\&. The \fBcurrent\fR slot is set to the \fBfirst\fR slot\&. Other device\-specific side effects may occur\&. Some gravity stackers need to be reset to the top position by hand\&. This command notifies \fBAmanda\fR the stacker is back in that position\&.
-
+Reset the tape changer to a known state. The
+\fBcurrent\fR
+slot is set to the
+\fBfirst\fR
+slot. Other device-specific side effects may occur. Some gravity stackers need to be reset to the top position by hand. This command notifies
+\fBAmanda\fR
+the stacker is back in that position.
.TP
\fBeject\fR
-If a tape is loaded in the drive, it is ejected and returned to the slot from which it was loaded\&.
-
+If a tape is loaded in the drive, it is ejected and returned to the slot from which it was loaded.
.TP
\fBclean\fR
-If a cleaning tape is defined for the changer, it is used to clean the drive\&.
-
+If a cleaning tape is defined for the changer, it is used to clean the drive.
.TP
\fBshow\fR
-Show the contents of all slots\&. This can be slow\&.
-
+Show the contents of all slots. This can be slow.
.TP
\fBlabel\fR \fBlabel\fR
-Search for and load the \fBAmanda\fR tape with label \fBlabel\fR\&.
-
+Search for and load the
+\fBAmanda\fR
+tape with label
+\fBlabel\fR.
.TP
\fBtaper\fR
-Perform the \fBtaper\fR scan algorithm\&. Load the next tape in the configuration's tape sequence, or a fresh tape with a suitable label\&.
-
+Perform the
+\fBtaper\fR
+scan algorithm. Load the next tape in the configuration's tape sequence, or a fresh tape with a suitable label.
.TP
\fBdevice\fR
-Display the name of the current tape device on \fBstdout\fR\&.
-
+Display the name of the current tape device on
+\fBstdout\fR.
.TP
\fBcurrent\fR
-Display the current slot\&.
-
+Display the current slot.
.TP
\fBupdate\fR
-Update the changer label database, if it has one, to match the tapes now available\&.
-
+Update the changer label database, if it has one, to match the tapes now available.
.TP
\fBslot\fR \fBslot\fR
-Eject any tape in the drive and put it away, then load the tape from slot \fBslot\fR and reset \fBcurrent\fR\&.
-
+Eject any tape in the drive and put it away, then load the tape from slot
+\fBslot\fR
+and reset
+\fBcurrent\fR.
.TP
\fBslot current\fR
-Eject any tape in the drive and put it away, then load the tape from the current slot\&.
-
+Eject any tape in the drive and put it away, then load the tape from the current slot.
.TP
\fBslot prev\fR
-Eject any tape in the drive and put it away, then load the tape from the previous slot and reset \fBcurrent\fR\&.
-
+Eject any tape in the drive and put it away, then load the tape from the previous slot and reset
+\fBcurrent\fR.
.TP
\fBslot next\fR
-Eject any tape in the drive and put it away, then load the tape from the next slot and reset \fBcurrent\fR\&.
-
+Eject any tape in the drive and put it away, then load the tape from the next slot and reset
+\fBcurrent\fR.
.TP
\fBslot first\fR
-Eject any tape in the drive and put it away, then load the tape from the first slot and reset \fBcurrent\fR\&.
-
+Eject any tape in the drive and put it away, then load the tape from the first slot and reset
+\fBcurrent\fR.
.TP
\fBslot last\fR
-Eject any tape in the drive and put it away, then load the tape from the last slot and reset \fBcurrent\fR\&.
-
+Eject any tape in the drive and put it away, then load the tape from the last slot and reset
+\fBcurrent\fR.
.TP
\fBslot advance\fR
-Eject any tape in the drive and put it away\&. Advance \fBcurrent\fR to the next tape, but do not load it\&.
-
+Eject any tape in the drive and put it away. Advance
+\fBcurrent\fR
+to the next tape, but do not load it.
.PP
-This is useful with non\-gravity stackers to unload the last tape used and set up \fBAmanda\fR for the next run\&. If you just use \fBeject\fR, the current tape will be mounted again in the next run, where it will be rejected as being still in use, ejected and the next tape requested\&. Using \fBslot next\fR followed by \fBeject\fR does an unnecessary mount\&.
-
+This is useful with non-gravity stackers to unload the last tape used and set up
+\fBAmanda\fR
+for the next run. If you just use
+\fBeject\fR, the current tape will be mounted again in the next run, where it will be rejected as being still in use, ejected and the next tape requested. Using
+\fBslot next\fR
+followed by
+\fBeject\fR
+does an unnecessary mount.
.PP
-Note: most changers optimize the \fBslot\fR commands to not eject the loaded tape if it is the one being requested\&.
-
+Note: most changers optimize the
+\fBslot\fR
+commands to not eject the loaded tape if it is the one being requested.
.SH "AUTHOR"
-
.PP
-James da Silva, <jds@amanda\&.org> : Original text
-
+James da Silva,
+<jds@amanda.org>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMTAPETYPE" 8 "" "" ""
-.SH NAME
-amtapetype \- generate a tapetype definition.
+.SH "NAME"
+amtapetype - generate a tapetype definition.
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 11
-\fBamtapetype\fR [\-h] [\-c] [\-o] [\-b\ \fIblocksize\fR] [\-e\ \fIestsize\fR] [\-f\ \fItapedev\fR] [\-t\ \fItypename\fR]
-.ad
-.hy
-
+\fBamtapetype\fR [-h] [-c] [-o] [-b \fIblocksize\fR] [-e \fIestsize\fR] [-f \fItapedev\fR] [-t \fItypename\fR]
.SH "DESCRIPTION"
-
.PP
-\fBamtapetype\fR generates a tapetype entry for \fBAmanda\fR\&.
-
+\fBamtapetype\fR
+generates a tapetype entry for
+\fBAmanda\fR.
.SH "OPTIONS"
-
.TP
-\fB\-h\fR
-Display an help message\&.
-
+\fB-h\fR
+Display an help message.
.TP
-\fB\-c\fR
-Run only the hardware compression detection heuristic test and stop\&. This takes a few minutes only\&.
-
+\fB-c\fR
+Run only the hardware compression detection heuristic test and stop. This takes a few minutes only.
.TP
-\fB\-o\fR
-Overwrite the tape, even if it's an \fBAmanda\fR tape\&.
-
+\fB-o\fR
+Overwrite the tape, even if it's an
+\fBAmanda\fR
+tape.
.TP
-\fB\-b\fR\fI blocksize\fR
+\fB-b\fR\fI blocksize\fR
record block size (default: 32k)
-
.TP
-\fB\-e\fR\fI estsize\fR
+\fB-e\fR\fI estsize\fR
estimated tape size (default: 1g == 1024m)
-
.TP
-\fB\-f\fR\fI tapedev\fR
-tape device name (default: $TAPE) The device to perform the test\&.
-
+\fB-f\fR\fI tapedev\fR
+tape device name (default: $TAPE) The device to perform the test.
.TP
-\fB\-t\fR\fI typename\fR
-tapetype name (default: unknown\-tapetype)
-
+\fB-t\fR\fI typename\fR
+tapetype name (default: unknown-tapetype)
.SH "EXAMPLE"
-
.PP
Generate a tapetype definition for your tape device:
-
+.sp
.nf
-% amtapetype \-f /dev/nst0
+% amtapetype -f /dev/nst0
.fi
-
.SH "NOTES"
-
.PP
-Hardware compression is detected by measuring the writing speed difference of the tape drive when writing an amount of compressable and uncompresseable data\&. It does not rely on the status bits of the tape drive or the OS parameters\&. If your tape drive has very large buffers or is very fast, the program could fail to detect hardware compression status reliably\&.
-
+Hardware compression is detected by measuring the writing speed difference of the tape drive when writing an amount of compressable and uncompresseable data. It does not rely on the status bits of the tape drive or the OS parameters. If your tape drive has very large buffers or is very fast, the program could fail to detect hardware compression status reliably.
.PP
-During the first pass, it writes files that are estimated to be 1% of the expected tape capacity\&. It gets the expected capacity from the \-e command line flag, or defaults to 1 GByte\&. In a perfect world (which means there is zero chance of this happening with tapes :\-), there would be 100 files and 100 file marks\&.
-
+During the first pass, it writes files that are estimated to be 1% of the expected tape capacity. It gets the expected capacity from the -e command line flag, or defaults to 1 GByte. In a perfect world (which means there is zero chance of this happening with tapes :-), there would be 100 files and 100 file marks.
.PP
-During the second pass, the file size is cut in half\&. In that same fairyland world, this means 200 files and 200 file marks\&.
-
+During the second pass, the file size is cut in half. In that same fairyland world, this means 200 files and 200 file marks.
.PP
-In both passes the total amount of data written is summed as well as the number of file marks written\&. At the end of the second pass, quoting from the code:
-
+In both passes the total amount of data written is summed as well as the number of file marks written. At the end of the second pass, quoting from the code:
.PP
-* Compute the size of a filemark as the difference in data written between pass 1 and pass 2 divided by the difference in number of file marks written between pass 1 and pass 2\&. \&.\&.\&. *
-
+* Compute the size of a filemark as the difference in data written between pass 1 and pass 2 divided by the difference in number of file marks written between pass 1 and pass 2. ... *
.PP
-So if we wrote 1\&.0 GBytes on the first pass and 100 file marks, and 0\&.9 GBytes on the second pass with 200 file marks, those additional 100 file marks in the second pass took 0\&.1 GBytes and therefor a file mark is 0\&.001 GBytes (1 MByte)\&.
-
+So if we wrote 1.0 GBytes on the first pass and 100 file marks, and 0.9 GBytes on the second pass with 200 file marks, those additional 100 file marks in the second pass took 0.1 GBytes and therefor a file mark is 0.001 GBytes (1 MByte).
.PP
-Note that if the estimated capacity is wrong, the only thing that happens is a lot more (or less, but unlikely) files, and thus, file marks, get written\&. But the math still works out the same\&. The \-e flag is there to keep the number of file marks down because they can be slow (since they force the drive to flush all its buffers to physical media)\&.
-
+Note that if the estimated capacity is wrong, the only thing that happens is a lot more (or less, but unlikely) files, and thus, file marks, get written. But the math still works out the same. The -e flag is there to keep the number of file marks down because they can be slow (since they force the drive to flush all its buffers to physical media).
.PP
-All sorts of things might happen to cause the amount of data written to vary enough to generate a big file mark size guess\&. A little more "shoe shining" because of the additional file marks (and flushes), dirt left on the heads from the first pass of a brand new tape, the temperature/humidity changed during the multi\-hour run, a different amount of data was written after the last file mark before EOT was reported, etc\&.
-
+All sorts of things might happen to cause the amount of data written to vary enough to generate a big file mark size guess. A little more "shoe shining" because of the additional file marks (and flushes), dirt left on the heads from the first pass of a brand new tape, the temperature/humidity changed during the multi-hour run, a different amount of data was written after the last file mark before EOT was reported, etc.
.PP
-Note that the file mark size might really be zero for whatever device this is, and it was just the measured capacity variation that caused \fBamtapetype\fR to think those extra file marks in pass 2 actually took up space\&.
-
+Note that the file mark size might really be zero for whatever device this is, and it was just the measured capacity variation that caused
+\fBamtapetype\fR
+to think those extra file marks in pass 2 actually took up space.
.PP
-It also explains why \fBamtapetype\fR used to sometimes report a negative file mark size if the math happened to end up that way\&. When that happens now we just report it as zero\&.
-
+It also explains why
+\fBamtapetype\fR
+used to sometimes report a negative file mark size if the math happened to end up that way. When that happens now we just report it as zero.
.SH "SEE ALSO"
-
.PP
\fBamanda\fR(8)
.IP "\\$1" \\$2
..
.TH "AMTOC" 8 "" "" ""
-.SH NAME
-amtoc \- generate TOC (Table Of Contents) for an Amanda run
+.SH "NAME"
+amtoc - generate TOC (Table Of Contents) for an Amanda run
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 6
-\fBamtoc\fR [\-a] [\-i] [\-t] [\-f\ \fIfile\fR] [\-s\ \fIsubs\fR] [\-w] [\-\-] \fIlogfile\fR
-.ad
-.hy
-
+\fBamtoc\fR [-a] [-i] [-t] [-f \fIfile\fR] [-s \fIsubs\fR] [-w] [--] \fIlogfile\fR
.SH "DESCRIPTION"
-
.PP
-\fBAmtoc\fR generates a table of contents for an \fBAmanda\fR run\&. It's a perl script (if you don't have perl, install it first!)\&.
-
+\fBAmtoc\fR
+generates a table of contents for an
+\fBAmanda\fR
+run. It's a perl script (if you don't have perl, install it first!).
.SH "OPTIONS"
-
.TP
-\fB\-a\fR
-The output file name will be \fBlabel\-of\-the\-tape\fR\&.toc in the same directory as \fBlogfile\fR\&.
-
+\fB-a\fR
+The output file name will be
+\fBlabel-of-the-tape\fR.toc in the same directory as
+\fBlogfile\fR.
.TP
-\fB\-i\fR
-Display help about \fBamtoc\fR\&.
-
+\fB-i\fR
+Display help about
+\fBamtoc\fR.
.TP
-\fB\-t\fR
-Generate the output in tabular form\&.
-
+\fB-t\fR
+Generate the output in tabular form.
.TP
-\fB\-f file\fR
-Write the output to a file ('\-' for stdout)\&.
-
+\fB-f file\fR
+Write the output to a file ('-' for stdout).
.TP
-\fB\-s subs\fR
-Evaluate the output file name from \fBsubs\fR, with $_ set to \fBlabel\-of\-the\-tape\fR\&. The \fB\-a\fR option is equivalent to \fB\-s\fR \fI's/$_/\&.toc/'\fR\&.
-
+\fB-s subs\fR
+Evaluate the output file name from
+\fBsubs\fR, with $_ set to
+\fBlabel-of-the-tape\fR. The
+\fB-a\fR
+option is equivalent to
+\fB-s\fR\fI's/$_/.toc/'\fR.
.TP
-\fB\-w\fR
-Separate tapes with form\-feeds and display blank lines before totals\&.
-
+\fB-w\fR
+Separate tapes with form-feeds and display blank lines before totals.
.TP
-\fB\-\-\fR
-Marks the last option so the next parameter is the \fBlogfile\fR\&.
-
+\fB--\fR
+Marks the last option so the next parameter is the
+\fBlogfile\fR.
.TP
\fBlogfile\fR
-(use '\-' for stdin)
-
+(use '-' for stdin)
.SH "OUTPUT FORMAT"
-
.PP
The standard output has five fields separated by two spaces:
-
+.sp
.nf
# Server:/partition date level size[Kb]
-0 daily\-05: 19991005 \- \-
+0 daily-05: 19991005 - -
1 cuisun15:/cuisun15/home 19991005 1 96
2 cuinfs:/export/dentiste 19991005 1 96
- \&.\&.\&.
+ ...
103 cuisg11:/ 19991005 0 4139136
-103 total: \- \- 16716288
+103 total: - - 16716288
.fi
-
.PP
-In tabular format (\-t), this would look like:
-
+In tabular format (-t), this would look like:
+.sp
.nf
# Server:/partition date lev size[Kb]
- 0 daily\-05: 19991005 \- \-
+ 0 daily-05: 19991005 - -
1 cuisun15:/cuisun15/home 19991005 1 96
2 cuinfs:/export/dentiste 19991005 1 96
- \&.\&.\&.
+ ...
103 cuisg11:/ 19991005 0 4139136
-103 total: \- \- 16716288
+103 total: - - 16716288
.fi
-
.SH "USAGE"
-
.PP
-The easiest way to use it is to run \fBamtoc\fR right after \fBamdump\fR in the \fBcron job:\fR
-
+The easiest way to use it is to run
+\fBamtoc\fR
+right after
+\fBamdump\fR
+in the
+\fBcron job:\fR
+.sp
.nf
-amdump daily ; logdir=`amgetconf daily logdir` ; log=`ls \-1t $logdir/log\&.*\&.[0\-9] | head \-1` ; amtoc \-a $log
+amdump daily ; logdir=`amgetconf daily logdir` ; log=`ls -1t $logdir/log.*.[0-9] | head -1` ; amtoc -a $log
.fi
-
+.sp
.PP
-which will generate /usr/local/etc/amanda//daily/\fBtape_label\fR\&.toc\&. You may also want to call \fBamtoc\fR after an \fBamflush\fR\&.
-
+which will generate /usr/local/etc/amanda//daily/\fBtape_label\fR.toc. You may also want to call
+\fBamtoc\fR
+after an
+\fBamflush\fR.
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamdump\fR(8), \fBamflush\fR(8), \fBamgetconf\fR(8), cron, perl
-
+\fBamanda\fR(8),
+\fBamdump\fR(8),
+\fBamflush\fR(8),
+\fBamgetconf\fR(8), cron, perl
.SH "AUTHOR"
-
.PP
-Nicolas Mayencourt <Nicolas\&.Mayencourt@cui\&.unige\&.ch>, University of Geneva/Switzerland : Original text
-
+Nicolas Mayencourt
+<Nicolas.Mayencourt@cui.unige.ch>, University of Geneva/Switzerland : Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.IP "\\$1" \\$2
..
.TH "AMVERIFY" 8 "" "" ""
-.SH NAME
-amverify \- check an Amanda tape for errors
+.SH "NAME"
+amverify - check an Amanda tape for errors
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 9
-\fBamverify\fR \fIconfig\fR [\fIslot\fR\ [\fIruntapes\fR]]
-.ad
-.hy
-
+\fBamverify\fR \fIconfig\fR [\fIslot\fRÂ [\fIruntapes\fR]]
.SH "DESCRIPTION"
-
.PP
-\fBAmverify\fR reads an Amanda format tape and makes sure each backup image can be processed by \fBamrestore\fR and, if possible, the appropriate restore program (e\&.g\&. \fBtar\fR)\&.
-
+\fBAmverify\fR
+reads an Amanda format tape and makes sure each backup image can be processed by
+\fBamrestore\fR
+and, if possible, the appropriate restore program (e.g.
+\fBtar\fR).
.PP
-\fBAmverify\fR runs \fBamrestore\fR on each file of the tape and pipes the output to a restore program (if available) with an option to create a catalogue of the backup\&. The catalogue itself is discarded\&. Only the success or failure of the operation itself is reported\&.
-
+\fBAmverify\fR
+runs
+\fBamrestore\fR
+on each file of the tape and pipes the output to a restore program (if available) with an option to create a catalogue of the backup. The catalogue itself is discarded. Only the success or failure of the operation itself is reported.
.PP
-If the backup image cannot be processed by the restore program, e\&.g\&. if it was written on a different operating system, the image is sent through \fBdd\fR to /dev/null\&. This still determines if the tape is readable, but does not do any internal consistency check on the image\&.
-
+If the backup image cannot be processed by the restore program, e.g. if it was written on a different operating system, the image is sent through
+\fBdd\fR
+to /dev/null. This still determines if the tape is readable, but does not do any internal consistency check on the image.
.PP
-If \fBconfig\fR is set up to use a tape changer, the \fBslot\fR argument may be used to choose the first tape to process\&. Otherwise, the \fBcurrent\fR slot is used\&.
-
+If
+\fBconfig\fR
+is set up to use a tape changer, the
+\fBslot\fR
+argument may be used to choose the first tape to process. Otherwise, the
+\fBcurrent\fR
+slot is used.
.PP
-The \fBruntapes\fR configuration parameter determines how many tapes are processed unless it is specified on the command line\&.
-
+The
+\fBruntapes\fR
+configuration parameter determines how many tapes are processed unless it is specified on the command line.
.PP
-See the \fBamanda\fR(8) man page for more details about Amanda\&.
-
+See the
+\fBamanda\fR(8)
+man page for more details about Amanda.
.SH "AUTHOR"
-
.PP
-Axel Zinser <fifi@icem\&.de> : Original text
-
+Axel Zinser
+<fifi@icem.de>
+: Original text
.PP
-Stefan G\&. Weichinger, <sgw@amanda\&.org>, maintainer of the \fBAmanda\fR\-documentation: XML\-conversion
-
+Stefan G. Weichinger,
+<sgw@amanda.org>, maintainer of the
+\fBAmanda\fR-documentation: XML-conversion
.SH "SEE ALSO"
-
.PP
-\fBamrestore\fR(8), \fBamanda\fR(8), \fBamverifyrun\fR(8)
+\fBamrestore\fR(8),
+\fBamanda\fR(8),
+\fBamverifyrun\fR(8)
.IP "\\$1" \\$2
..
.TH "AMVERIFYRUN" 8 "" "" ""
-.SH NAME
-amverifyrun \- check the tapes written by the last Amanda run
+.SH "NAME"
+amverifyrun - check the tapes written by the last Amanda run
.SH "SYNOPSIS"
-.ad l
-.hy 0
.HP 12
\fBamverifyrun\fR \fIconfig\fR
-.ad
-.hy
-
.SH "DESCRIPTION"
-
.PP
-\fBAmverifyrun\fR read the log from the last \fBAmanda\fR run to find the slot of the first tape used and the number of tapes used\&. It call \fBamverify\fR with these argument\&.
-
+\fBAmverifyrun\fR
+read the log from the last
+\fBAmanda\fR
+run to find the slot of the first tape used and the number of tapes used. It call
+\fBamverify\fR
+with these argument.
.SH "SEE ALSO"
-
.PP
-\fBamanda\fR(8), \fBamverify\fR(8)
+\fBamanda\fR(8),
+\fBamverify\fR(8)
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
# Makefile for Amanda file recovery programs.
-SOURCES = $(amrecover_SOURCES)
-
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
-/* A Bison parser, made by GNU Bison 2.0. */
+/* A Bison parser, made by GNU Bison 2.1. */
/* Skeleton parser for Yacc-like parsing with Bison,
- Copyright (C) 1984, 1989, 1990, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
+ Copyright (C) 1984, 1989, 1990, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place - Suite 330,
- Boston, MA 02111-1307, USA. */
+ Foundation, Inc., 51 Franklin Street, Fifth Floor,
+ Boston, MA 02110-1301, USA. */
/* As a special exception, when this file is copied by Bison into a
Bison output file, you may use that output file without restriction.
/* Identify Bison output. */
#define YYBISON 1
+/* Bison version. */
+#define YYBISON_VERSION "2.1"
+
/* Skeleton name. */
#define YYSKELETON_NAME "yacc.c"
DATE = 284
};
#endif
+/* Tokens. */
#define LISTDISK 258
#define SETHOST 259
#define SETDISK 260
# define YYERROR_VERBOSE 0
#endif
+/* Enabling the token table. */
+#ifndef YYTOKEN_TABLE
+# define YYTOKEN_TABLE 0
+#endif
+
#if ! defined (YYSTYPE) && ! defined (YYSTYPE_IS_DECLARED)
#line 40 "uparse.y"
typedef union YYSTYPE {
char *strval;
int subtok;
} YYSTYPE;
-/* Line 190 of yacc.c. */
-#line 149 "uparse.c"
+/* Line 196 of yacc.c. */
+#line 158 "uparse.c"
# define yystype YYSTYPE /* obsolescent; will be withdrawn */
# define YYSTYPE_IS_DECLARED 1
# define YYSTYPE_IS_TRIVIAL 1
/* Copy the second part of user declarations. */
-/* Line 213 of yacc.c. */
-#line 161 "uparse.c"
+/* Line 219 of yacc.c. */
+#line 170 "uparse.c"
-#if ! defined (yyoverflow) || YYERROR_VERBOSE
+#if ! defined (YYSIZE_T) && defined (__SIZE_TYPE__)
+# define YYSIZE_T __SIZE_TYPE__
+#endif
+#if ! defined (YYSIZE_T) && defined (size_t)
+# define YYSIZE_T size_t
+#endif
+#if ! defined (YYSIZE_T) && (defined (__STDC__) || defined (__cplusplus))
+# include <stddef.h> /* INFRINGES ON USER NAME SPACE */
+# define YYSIZE_T size_t
+#endif
+#if ! defined (YYSIZE_T)
+# define YYSIZE_T unsigned int
+#endif
-# ifndef YYFREE
-# define YYFREE free
+#ifndef YY_
+# if YYENABLE_NLS
+# if ENABLE_NLS
+# include <libintl.h> /* INFRINGES ON USER NAME SPACE */
+# define YY_(msgid) dgettext ("bison-runtime", msgid)
+# endif
# endif
-# ifndef YYMALLOC
-# define YYMALLOC malloc
+# ifndef YY_
+# define YY_(msgid) msgid
# endif
+#endif
+
+#if ! defined (yyoverflow) || YYERROR_VERBOSE
/* The parser invokes alloca or malloc; define the necessary symbols. */
# define YYSTACK_ALLOC __builtin_alloca
# else
# define YYSTACK_ALLOC alloca
+# if defined (__STDC__) || defined (__cplusplus)
+# include <stdlib.h> /* INFRINGES ON USER NAME SPACE */
+# define YYINCLUDED_STDLIB_H
+# endif
# endif
# endif
# endif
# ifdef YYSTACK_ALLOC
/* Pacify GCC's `empty if-body' warning. */
# define YYSTACK_FREE(Ptr) do { /* empty */; } while (0)
-# else
-# if defined (__STDC__) || defined (__cplusplus)
-# include <stdlib.h> /* INFRINGES ON USER NAME SPACE */
-# define YYSIZE_T size_t
+# ifndef YYSTACK_ALLOC_MAXIMUM
+ /* The OS might guarantee only one guard page at the bottom of the stack,
+ and a page size can be as small as 4096 bytes. So we cannot safely
+ invoke alloca (N) if N exceeds 4096. Use a slightly smaller number
+ to allow for a few compiler-allocated temporary stack slots. */
+# define YYSTACK_ALLOC_MAXIMUM 4032 /* reasonable circa 2005 */
# endif
+# else
# define YYSTACK_ALLOC YYMALLOC
# define YYSTACK_FREE YYFREE
+# ifndef YYSTACK_ALLOC_MAXIMUM
+# define YYSTACK_ALLOC_MAXIMUM ((YYSIZE_T) -1)
+# endif
+# ifdef __cplusplus
+extern "C" {
+# endif
+# ifndef YYMALLOC
+# define YYMALLOC malloc
+# if (! defined (malloc) && ! defined (YYINCLUDED_STDLIB_H) \
+ && (defined (__STDC__) || defined (__cplusplus)))
+void *malloc (YYSIZE_T); /* INFRINGES ON USER NAME SPACE */
+# endif
+# endif
+# ifndef YYFREE
+# define YYFREE free
+# if (! defined (free) && ! defined (YYINCLUDED_STDLIB_H) \
+ && (defined (__STDC__) || defined (__cplusplus)))
+void free (void *); /* INFRINGES ON USER NAME SPACE */
+# endif
+# endif
+# ifdef __cplusplus
+}
+# endif
# endif
#endif /* ! defined (yyoverflow) || YYERROR_VERBOSE */
# define YYCOPY(To, From, Count) \
do \
{ \
- register YYSIZE_T yyi; \
+ YYSIZE_T yyi; \
for (yyi = 0; yyi < (Count); yyi++) \
(To)[yyi] = (From)[yyi]; \
} \
#define YYUNDEFTOK 2
#define YYMAXUTOK 284
-#define YYTRANSLATE(YYX) \
+#define YYTRANSLATE(YYX) \
((unsigned int) (YYX) <= YYMAXUTOK ? yytranslate[YYX] : YYUNDEFTOK)
/* YYTRANSLATE[YYLEX] -- Bison symbol number corresponding to YYLEX. */
};
#endif
-#if YYDEBUG || YYERROR_VERBOSE
-/* YYTNME[SYMBOL-NUM] -- String name of the symbol SYMBOL-NUM.
+#if YYDEBUG || YYERROR_VERBOSE || YYTOKEN_TABLE
+/* YYTNAME[SYMBOL-NUM] -- String name of the symbol SYMBOL-NUM.
First, the terminals, then, starting at YYNTOKENS, nonterminals. */
static const char *const yytname[] =
{
40, 28, 42, 28, 0, 28, 28, 28, 28, 28
};
-#if ! defined (YYSIZE_T) && defined (__SIZE_TYPE__)
-# define YYSIZE_T __SIZE_TYPE__
-#endif
-#if ! defined (YYSIZE_T) && defined (size_t)
-# define YYSIZE_T size_t
-#endif
-#if ! defined (YYSIZE_T)
-# if defined (__STDC__) || defined (__cplusplus)
-# include <stddef.h> /* INFRINGES ON USER NAME SPACE */
-# define YYSIZE_T size_t
-# endif
-#endif
-#if ! defined (YYSIZE_T)
-# define YYSIZE_T unsigned int
-#endif
-
#define yyerrok (yyerrstatus = 0)
#define yyclearin (yychar = YYEMPTY)
#define YYEMPTY (-2)
goto yybackup; \
} \
else \
- { \
- yyerror ("syntax error: cannot back up");\
+ { \
+ yyerror (YY_("syntax error: cannot back up")); \
YYERROR; \
} \
while (0)
if (yydebug) \
{ \
YYFPRINTF (stderr, "%s ", Title); \
- yysymprint (stderr, \
+ yysymprint (stderr, \
Type, Value); \
YYFPRINTF (stderr, "\n"); \
} \
#endif
{
int yyi;
- unsigned int yylno = yyrline[yyrule];
- YYFPRINTF (stderr, "Reducing stack by rule %d (line %u), ",
+ unsigned long int yylno = yyrline[yyrule];
+ YYFPRINTF (stderr, "Reducing stack by rule %d (line %lu), ",
yyrule - 1, yylno);
/* Print the symbols being reduced, and their result. */
for (yyi = yyprhs[yyrule]; 0 <= yyrhs[yyi]; yyi++)
- YYFPRINTF (stderr, "%s ", yytname [yyrhs[yyi]]);
- YYFPRINTF (stderr, "-> %s\n", yytname [yyr1[yyrule]]);
+ YYFPRINTF (stderr, "%s ", yytname[yyrhs[yyi]]);
+ YYFPRINTF (stderr, "-> %s\n", yytname[yyr1[yyrule]]);
}
# define YY_REDUCE_PRINT(Rule) \
if the built-in stack extension method is used).
Do not make this value too large; the results are undefined if
- SIZE_MAX < YYSTACK_BYTES (YYMAXDEPTH)
+ YYSTACK_ALLOC_MAXIMUM < YYSTACK_BYTES (YYMAXDEPTH)
evaluated with infinite-precision integer arithmetic. */
#ifndef YYMAXDEPTH
const char *yystr;
# endif
{
- register const char *yys = yystr;
+ const char *yys = yystr;
while (*yys++ != '\0')
continue;
const char *yysrc;
# endif
{
- register char *yyd = yydest;
- register const char *yys = yysrc;
+ char *yyd = yydest;
+ const char *yys = yysrc;
while ((*yyd++ = *yys++) != '\0')
continue;
# endif
# endif
-#endif /* !YYERROR_VERBOSE */
+# ifndef yytnamerr
+/* Copy to YYRES the contents of YYSTR after stripping away unnecessary
+ quotes and backslashes, so that it's suitable for yyerror. The
+ heuristic is that double-quoting is unnecessary unless the string
+ contains an apostrophe, a comma, or backslash (other than
+ backslash-backslash). YYSTR is taken from yytname. If YYRES is
+ null, do not copy; instead, return the length of what the result
+ would have been. */
+static YYSIZE_T
+yytnamerr (char *yyres, const char *yystr)
+{
+ if (*yystr == '"')
+ {
+ size_t yyn = 0;
+ char const *yyp = yystr;
+
+ for (;;)
+ switch (*++yyp)
+ {
+ case '\'':
+ case ',':
+ goto do_not_strip_quotes;
+
+ case '\\':
+ if (*++yyp != '\\')
+ goto do_not_strip_quotes;
+ /* Fall through. */
+ default:
+ if (yyres)
+ yyres[yyn] = *yyp;
+ yyn++;
+ break;
+
+ case '"':
+ if (yyres)
+ yyres[yyn] = '\0';
+ return yyn;
+ }
+ do_not_strip_quotes: ;
+ }
+
+ if (! yyres)
+ return yystrlen (yystr);
+
+ return yystpcpy (yyres, yystr) - yyres;
+}
+# endif
+
+#endif /* YYERROR_VERBOSE */
\f
#endif
{
- register int yystate;
- register int yyn;
+ int yystate;
+ int yyn;
int yyresult;
/* Number of tokens to shift before error messages enabled. */
int yyerrstatus;
/* The state stack. */
short int yyssa[YYINITDEPTH];
short int *yyss = yyssa;
- register short int *yyssp;
+ short int *yyssp;
/* The semantic value stack. */
YYSTYPE yyvsa[YYINITDEPTH];
YYSTYPE *yyvs = yyvsa;
- register YYSTYPE *yyvsp;
+ YYSTYPE *yyvsp;
yyssp = yyss;
yyvsp = yyvs;
-
- yyvsp[0] = yylval;
-
goto yysetstate;
/*------------------------------------------------------------.
data in use in that stack, in bytes. This used to be a
conditional around just the two extra args, but that might
be undefined if yyoverflow is a macro. */
- yyoverflow ("parser stack overflow",
+ yyoverflow (YY_("memory exhausted"),
&yyss1, yysize * sizeof (*yyssp),
&yyvs1, yysize * sizeof (*yyvsp),
}
#else /* no yyoverflow */
# ifndef YYSTACK_RELOCATE
- goto yyoverflowlab;
+ goto yyexhaustedlab;
# else
/* Extend the stack our own way. */
if (YYMAXDEPTH <= yystacksize)
- goto yyoverflowlab;
+ goto yyexhaustedlab;
yystacksize *= 2;
if (YYMAXDEPTH < yystacksize)
yystacksize = YYMAXDEPTH;
union yyalloc *yyptr =
(union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize));
if (! yyptr)
- goto yyoverflowlab;
+ goto yyexhaustedlab;
YYSTACK_RELOCATE (yyss);
YYSTACK_RELOCATE (yyvs);
break;
+ default: break;
}
-/* Line 1037 of yacc.c. */
-#line 1291 "uparse.c"
+/* Line 1126 of yacc.c. */
+#line 1379 "uparse.c"
\f
yyvsp -= yylen;
yyssp -= yylen;
if (YYPACT_NINF < yyn && yyn < YYLAST)
{
- YYSIZE_T yysize = 0;
int yytype = YYTRANSLATE (yychar);
- const char* yyprefix;
- char *yymsg;
+ YYSIZE_T yysize0 = yytnamerr (0, yytname[yytype]);
+ YYSIZE_T yysize = yysize0;
+ YYSIZE_T yysize1;
+ int yysize_overflow = 0;
+ char *yymsg = 0;
+# define YYERROR_VERBOSE_ARGS_MAXIMUM 5
+ char const *yyarg[YYERROR_VERBOSE_ARGS_MAXIMUM];
int yyx;
+#if 0
+ /* This is so xgettext sees the translatable formats that are
+ constructed on the fly. */
+ YY_("syntax error, unexpected %s");
+ YY_("syntax error, unexpected %s, expecting %s");
+ YY_("syntax error, unexpected %s, expecting %s or %s");
+ YY_("syntax error, unexpected %s, expecting %s or %s or %s");
+ YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s");
+#endif
+ char *yyfmt;
+ char const *yyf;
+ static char const yyunexpected[] = "syntax error, unexpected %s";
+ static char const yyexpecting[] = ", expecting %s";
+ static char const yyor[] = " or %s";
+ char yyformat[sizeof yyunexpected
+ + sizeof yyexpecting - 1
+ + ((YYERROR_VERBOSE_ARGS_MAXIMUM - 2)
+ * (sizeof yyor - 1))];
+ char const *yyprefix = yyexpecting;
+
/* Start YYX at -YYN if negative to avoid negative indexes in
YYCHECK. */
int yyxbegin = yyn < 0 ? -yyn : 0;
/* Stay within bounds of both yycheck and yytname. */
int yychecklim = YYLAST - yyn;
int yyxend = yychecklim < YYNTOKENS ? yychecklim : YYNTOKENS;
- int yycount = 0;
+ int yycount = 1;
+
+ yyarg[0] = yytname[yytype];
+ yyfmt = yystpcpy (yyformat, yyunexpected);
- yyprefix = ", expecting ";
for (yyx = yyxbegin; yyx < yyxend; ++yyx)
if (yycheck[yyx + yyn] == yyx && yyx != YYTERROR)
{
- yysize += yystrlen (yyprefix) + yystrlen (yytname [yyx]);
- yycount += 1;
- if (yycount == 5)
+ if (yycount == YYERROR_VERBOSE_ARGS_MAXIMUM)
{
- yysize = 0;
+ yycount = 1;
+ yysize = yysize0;
+ yyformat[sizeof yyunexpected - 1] = '\0';
break;
}
+ yyarg[yycount++] = yytname[yyx];
+ yysize1 = yysize + yytnamerr (0, yytname[yyx]);
+ yysize_overflow |= yysize1 < yysize;
+ yysize = yysize1;
+ yyfmt = yystpcpy (yyfmt, yyprefix);
+ yyprefix = yyor;
}
- yysize += (sizeof ("syntax error, unexpected ")
- + yystrlen (yytname[yytype]));
- yymsg = (char *) YYSTACK_ALLOC (yysize);
- if (yymsg != 0)
- {
- char *yyp = yystpcpy (yymsg, "syntax error, unexpected ");
- yyp = yystpcpy (yyp, yytname[yytype]);
- if (yycount < 5)
+ yyf = YY_(yyformat);
+ yysize1 = yysize + yystrlen (yyf);
+ yysize_overflow |= yysize1 < yysize;
+ yysize = yysize1;
+
+ if (!yysize_overflow && yysize <= YYSTACK_ALLOC_MAXIMUM)
+ yymsg = (char *) YYSTACK_ALLOC (yysize);
+ if (yymsg)
+ {
+ /* Avoid sprintf, as that infringes on the user's name space.
+ Don't have undefined behavior even if the translation
+ produced a string with the wrong number of "%s"s. */
+ char *yyp = yymsg;
+ int yyi = 0;
+ while ((*yyp = *yyf))
{
- yyprefix = ", expecting ";
- for (yyx = yyxbegin; yyx < yyxend; ++yyx)
- if (yycheck[yyx + yyn] == yyx && yyx != YYTERROR)
- {
- yyp = yystpcpy (yyp, yyprefix);
- yyp = yystpcpy (yyp, yytname[yyx]);
- yyprefix = " or ";
- }
+ if (*yyp == '%' && yyf[1] == 's' && yyi < yycount)
+ {
+ yyp += yytnamerr (yyp, yyarg[yyi++]);
+ yyf += 2;
+ }
+ else
+ {
+ yyp++;
+ yyf++;
+ }
}
yyerror (yymsg);
YYSTACK_FREE (yymsg);
}
else
- yyerror ("syntax error; also virtual memory exhausted");
+ {
+ yyerror (YY_("syntax error"));
+ goto yyexhaustedlab;
+ }
}
else
#endif /* YYERROR_VERBOSE */
- yyerror ("syntax error");
+ yyerror (YY_("syntax error"));
}
if (yychar <= YYEOF)
{
- /* If at end of input, pop the error token,
- then the rest of the stack, then return failure. */
+ /* Return failure if at end of input. */
if (yychar == YYEOF)
- for (;;)
- {
-
- YYPOPSTACK;
- if (yyssp == yyss)
- YYABORT;
- yydestruct ("Error: popping",
- yystos[*yyssp], yyvsp);
- }
+ YYABORT;
}
else
{
`---------------------------------------------------*/
yyerrorlab:
-#ifdef __GNUC__
- /* Pacify GCC when the user code never invokes YYERROR and the label
- yyerrorlab therefore never appears in user code. */
+ /* Pacify compilers like GCC when the user code never invokes
+ YYERROR and the label yyerrorlab therefore never appears in user
+ code. */
if (0)
goto yyerrorlab;
-#endif
yyvsp -= yylen;
yyssp -= yylen;
| yyabortlab -- YYABORT comes here. |
`-----------------------------------*/
yyabortlab:
- yydestruct ("Error: discarding lookahead",
- yytoken, &yylval);
- yychar = YYEMPTY;
yyresult = 1;
goto yyreturn;
#ifndef yyoverflow
-/*----------------------------------------------.
-| yyoverflowlab -- parser overflow comes here. |
-`----------------------------------------------*/
-yyoverflowlab:
- yyerror ("parser stack overflow");
+/*-------------------------------------------------.
+| yyexhaustedlab -- memory exhaustion comes here. |
+`-------------------------------------------------*/
+yyexhaustedlab:
+ yyerror (YY_("memory exhausted"));
yyresult = 2;
/* Fall through. */
#endif
yyreturn:
+ if (yychar != YYEOF && yychar != YYEMPTY)
+ yydestruct ("Cleanup: discarding lookahead",
+ yytoken, &yylval);
+ while (yyssp != yyss)
+ {
+ yydestruct ("Cleanup: popping",
+ yystos[*yyssp], yyvsp);
+ YYPOPSTACK;
+ }
#ifndef yyoverflow
if (yyss != yyssa)
YYSTACK_FREE (yyss);
-/* A Bison parser, made by GNU Bison 2.0. */
+/* A Bison parser, made by GNU Bison 2.1. */
/* Skeleton parser for Yacc-like parsing with Bison,
- Copyright (C) 1984, 1989, 1990, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
+ Copyright (C) 1984, 1989, 1990, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place - Suite 330,
- Boston, MA 02111-1307, USA. */
+ Foundation, Inc., 51 Franklin Street, Fifth Floor,
+ Boston, MA 02110-1301, USA. */
/* As a special exception, when this file is copied by Bison into a
Bison output file, you may use that output file without restriction.
DATE = 284
};
#endif
+/* Tokens. */
#define LISTDISK 258
#define SETHOST 259
#define SETDISK 260
char *strval;
int subtok;
} YYSTYPE;
-/* Line 1318 of yacc.c. */
-#line 102 "uparse.h"
+/* Line 1447 of yacc.c. */
+#line 103 "uparse.h"
# define yystype YYSTYPE /* obsolescent; will be withdrawn */
# define YYSTYPE_IS_DECLARED 1
# define YYSTYPE_IS_TRIVIAL 1
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-SOURCES = $(librestore_la_SOURCES) $(amfetchdump_SOURCES) $(amidxtaped_SOURCES) amrestore.c
-
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: amrestore.c,v 1.56 2006/01/14 04:37:19 paddy_s Exp $
+ * $Id: amrestore.c,v 1.56.2.1 2006/04/07 10:52:17 martinea Exp $
*
* retrieves files from an amanda tape
*/
}
}
if(found_match) {
+ count_error=0;
read_result = restore(&file, filename,
tapedev, isafile, rst_flags);
if(comp_enc_pid > 0) {
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-SOURCES = $(libamserver_la_SOURCES) amadmin.c amcheck.c amcleanupdisk.c amflush.c $(amgetconf_SOURCES) $(amindexd_SOURCES) amlabel.c amlogroll.c $(amreport_SOURCES) amtape.c amtrmidx.c amtrmlog.c chunker.c $(conffile_SOURCES) $(diskfile_SOURCES) driver.c dumper.c $(infofile_SOURCES) planner.c taper.c
-
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
push @datestamp, $gdatestamp;
}
}
- elsif(/setup_estimate: (\S+):(\S+): command .*, options: *(\S+) *last_level -?\d+ next_level0 -?\d+ level_days \d+ *getting estimates (-?\d) \(-2\) (-?\d) \(-2\) (-?\d) \(-2\)/) {
+ elsif(/setup_estimate: ([_\-\d\.A-Za-z]*):(\S+): command .*, options: *(\S+) *last_level -?\d+ next_level0 -?\d+ level_days \d+ *getting estimates (-?\d) \(-2\) (-?\d) \(-2\) (-?\d) \(-2\)/) {
$host=$1;
$partition=$2;
$hostpart=&make_hostpart($host,$partition,$gdatestamp);
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: amtape.c,v 1.40 2006/01/14 04:37:19 paddy_s Exp $
+ * $Id: amtape.c,v 1.40.2.1 2006/04/14 11:32:07 martinea Exp $
*
* tape changer interface program
*/
void load_label P((int argc, char **argv));
void show_slots P((int argc, char **argv));
void show_current P((int argc, char **argv));
+void update_labeldb P((int argc, char **argv));
void amtape_taper_scan P((int argc, char **argv));
void show_device P((int argc, char **argv));
+int update_one_slot P((void *ud, int rc, char *slotstr, char *device));
int loadlabel_slot P((void *ud, int rc, char *slotstr, char *device));
int show_init P((void *ud, int rc, int ns, int bk, int s));
int show_init_all P((void *ud, int rc, int ns, int bk, int s));
"taper perform taper's scan alg." },
{ "device", show_device,
"device show current tape device" },
+ { "update", update_labeldb,
+ "update update the label matchingdatabase"},
};
#define NCMDS (sizeof(cmdtab) / sizeof(cmdtab[0]))
amfree(slot);
amfree(device);
}
+
+/* ---------------------------- */
+
+int update_one_slot(ud, rc, slotstr, device)
+ void *ud;
+ int rc;
+ char *slotstr;
+ char *device;
+{
+ char *errstr = NULL;
+ char *datestamp = NULL;
+ char *label = NULL;
+
+ if(rc > 1)
+ error("could not load slot %s: %s", slotstr, changer_resultstr);
+ else if(rc == 1)
+ fprintf(stderr, "slot %s: %s\n", slotstr, changer_resultstr);
+ else if((errstr = tape_rdlabel(device, &datestamp, &label)) != NULL)
+ fprintf(stderr, "slot %s: %s\n", slotstr, errstr);
+ else {
+ fprintf(stderr, "slot %s: date %-8s label %s\n",
+ slotstr, datestamp, label);
+ changer_label(slotstr, label);
+ }
+ amfree(errstr);
+ amfree(datestamp);
+ amfree(label);
+ return 0;
+}
+
+void update_labeldb(argc, argv)
+int argc;
+char **argv;
+{
+ if(argc != 1)
+ usage();
+
+ changer_find(NULL, show_init_all, update_one_slot, NULL);
+}
+
new tape
first labelstr match' | sed 1q | sed 's/://g' | awk '{print $3}'`
if [ X"$FIRST_SLOT" = X"" ]; then
- FIRST_SLOT='-1'
+ FIRST_SLOT=`grep "taper: slot: .* wrote label" $AMLOG | sed 1q | sed 's/://g' | awk '{print $3}'`
+ if [ X"$FIRST_SLOT" = X"" ]; then
+ FIRST_SLOT='-1'
+ fi
fi
-NBTAPES=`grep -c "taper: wrote label " $AMLOG`
+NBTAPES=`grep -c "taper: .*wrote label " $AMLOG`
if [ X"$NBTAPES" != X"0" ]; then
$AMVERIFY $CONFIG $FIRST_SLOT $NBTAPES
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: changer.c,v 1.29 2006/01/14 04:37:19 paddy_s Exp $
+ * $Id: changer.c,v 1.29.2.1 2006/04/24 14:43:01 martinea Exp $
*
* interface routines for tape changers
*/
char *s;
int ch;
- *slotstr = NULL;
- *rest = NULL;
+ if (slotstr) {
+ *slotstr = NULL;
+ }
+ if (rest) {
+ *rest = NULL;
+ }
exitcode = changer_command(cmd, arg);
s = changer_resultstr;
ch = *s++;
slot = s - 1;
skip_non_whitespace(s, ch);
s[-1] = '\0';
- *slotstr = newstralloc(*slotstr, slot);
+ if (slotstr) {
+ *slotstr = newstralloc(*slotstr, slot);
+ }
s[-1] = ch;
skip_whitespace(s, ch);
- *rest = s - 1;
+ if(rest) {
+ *rest = s - 1;
+ }
if(exitcode) {
if(ch == '\0') return report_bad_resultstr();
* Authors: the Amanda Development Team. Its members are listed in a
* file named AUTHORS, in the root directory of this distribution.
*/
-/* $Id: chunker.c,v 1.25 2006/03/21 13:23:35 martinea Exp $
+/* $Id: chunker.c,v 1.25.2.1 2006/04/23 18:52:04 martinea Exp $
*
* requests remote amandad processes to dump filesystems
*/
static char *progname = NULL;
static int level;
static char *dumpdate = NULL;
-static char *datestamp;
+static char *datestamp = NULL;
static int command_in_transit;
static dumpfile_t file;
signal(SIGPIPE, SIG_IGN);
signal(SIGCHLD, SIG_IGN);
- datestamp = construct_datestamp(NULL);
+ cmd = getcmd(&cmdargs);
+ if(cmd == START) {
+ if(cmdargs.argc <= 1)
+ error("error [dumper START: not enough args: datestamp]");
+ datestamp = newstralloc(datestamp, cmdargs.argv[2]);
+ }
+ else {
+ error("Didn't get START command");
+ }
/* do {*/
cmd = getcmd(&cmdargs);
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: driver.c,v 1.164 2006/03/22 15:07:08 martinea Exp $
+ * $Id: driver.c,v 1.165.2.2 2006/04/23 23:04:33 martinea Exp $
*
* controlling process for the Amanda backup system
*/
chunker->result = LAST_TOK;
dumper->result = LAST_TOK;
startup_chunk_process(chunker,chunker_program);
+ chunker_cmd(chunker, START, (void *)datestamp);
chunker->dumper = dumper;
chunker_cmd(chunker, PORT_WRITE, diskp);
cmd = getresult(chunker->fd, 1, &result_argc, result_argv, MAX_ARGS+1);
chunker_cmd( chunker, CONTINUE, dp );
} else { /* !h[++activehd] - must allocate more space */
sched(dp)->act_size = sched(dp)->est_size; /* not quite true */
- sched(dp)->est_size = sched(dp)->act_size * 21 / 20; /* +5% */
+ sched(dp)->est_size = (sched(dp)->act_size/20) * 21; /* +5% */
sched(dp)->est_size = am_round(sched(dp)->est_size, DISK_BLOCK_KB);
+ if(sched(dp)->est_size <= sched(dp)->act_size + DISK_BLOCK_KB)
+ sched(dp)->est_size = sched(dp)->act_size +
+ 2 * DISK_BLOCK_KB;
h = find_diskspace( sched(dp)->est_size - sched(dp)->act_size,
&dummy,
h[activehd-1] );
* University of Maryland at College Park
*/
/*
- * $Id: driverio.c,v 1.81 2006/03/11 21:57:18 martinea Exp $
+ * $Id: driverio.c,v 1.81.2.1 2006/04/23 18:52:04 martinea Exp $
*
* I/O-related functions for driver program
*/
assignedhd_t **h=NULL;
char *features;
- if(dp && sched(dp) && sched(dp)->holdp) {
+ if(cmd != START && dp && sched(dp) && sched(dp)->holdp) {
h = sched(dp)->holdp;
activehd = sched(dp)->activehd;
}
switch(cmd) {
+ case START:
+ cmdline = vstralloc(cmdstr[cmd], " ", (char *)dp, "\n", NULL);
+ break;
case PORT_WRITE:
if (dp && h) {
holdalloc(h[activehd]->disk)->allocated_dumpers++;
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: planner.c,v 1.180 2006/03/10 13:51:06 martinea Exp $
+ * $Id: planner.c,v 1.180.2.1 2006/04/24 11:16:43 martinea Exp $
*
* backup schedule planner for the Amanda backup system.
*/
char *label;
{
tape_t *tp;
+ int runtapes;
+
+ runtapes = conf_runtapes;
+ if(runtapes == 0) runtapes = 1;
if((tp = lookup_tapelabel(label)) == NULL)
return 1; /* "shouldn't happen", but trigger warning message */
else if(!reusable_tape(tp))
return 1024;
else if(lookup_nb_tape() > conf_tapecycle)
- return (lookup_nb_tape() - tp->position) / conf_runtapes;
+ return (lookup_nb_tape() - tp->position) / runtapes;
else
- return (conf_tapecycle - tp->position) / conf_runtapes;
+ return (conf_tapecycle - tp->position) / runtapes;
}
/* Return the estimated size for a particular dump */
old_tape = lookup_tapelabel(info->inf[lev-1].label);
if(cur_tape == NULL || old_tape == NULL) return 0;
- nb_runs = (old_tape->position - cur_tape->position) / conf_runtapes;
+ if(conf_runtapes == 0)
+ nb_runs = (old_tape->position - cur_tape->position) / 1;
+ else
+ nb_runs = (old_tape->position - cur_tape->position) / conf_runtapes;
info->consecutive_runs = nb_runs;
return nb_runs;
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: server_util.c,v 1.13 2005/10/20 23:18:15 martinea Exp $
+ * $Id: server_util.c,v 1.13.2.1 2006/04/23 18:52:04 martinea Exp $
*
*/
const char *cmdstr[] = {
"BOGUS", "QUIT", "QUITTING", "DONE", "PARTIAL",
- "FILE-DUMP", "PORT-DUMP", "CONTINUE", "ABORT", /* dumper cmds */
+ "START", "FILE-DUMP", "PORT-DUMP", "CONTINUE", "ABORT", /* dumper cmds */
"FAILED", "TRY-AGAIN", "NO-ROOM", "RQ-MORE-DISK", /* dumper results */
"ABORT-FINISHED", "BAD-COMMAND", /* dumper results */
"START-TAPER", "FILE-WRITE", "PORT-WRITE", /* taper cmds */
* file named AUTHORS, in the root directory of this distribution.
*/
/*
- * $Id: server_util.h,v 1.8 2005/10/11 01:17:01 vectro Exp $
+ * $Id: server_util.h,v 1.8.2.1 2006/04/23 18:52:04 martinea Exp $
*
*/
#ifndef SERVER_UTIL_H
typedef enum {
BOGUS, QUIT, QUITTING, DONE, PARTIAL,
- FILE_DUMP, PORT_DUMP, CONTINUE, ABORT, /* dumper cmds */
+ START, FILE_DUMP, PORT_DUMP, CONTINUE, ABORT, /* dumper cmds */
FAILED, TRYAGAIN, NO_ROOM, RQ_MORE_DISK, /* dumper results */
ABORT_FINISHED, BAD_COMMAND, /* dumper results */
START_TAPER, FILE_WRITE, PORT_WRITE, /* taper cmds */
* Authors: the Amanda Development Team. Its members are listed in a
* file named AUTHORS, in the root directory of this distribution.
*/
-/* $Id: taper.c,v 1.118 2006/03/17 15:34:12 vectro Exp $
+/* $Id: taper.c,v 1.118.2.1 2006/05/04 21:31:15 martinea Exp $
*
* moves files from holding disk to tape, or from a socket to tape
*/
static int first_call = 1;
char *timestamp;
char *error_msg;
+ char *s, *r;
+ int slot = -1;
if (taper_scan(NULL, &label, ×tamp, &error_msg, &tapedev) < 0) {
fprintf(stderr, "%s\n", error_msg);
amfree(timestamp);
return 0;
}
-
+ if(error_msg) {
+ s = error_msg; r = NULL;
+ while((s=strstr(s,"slot "))) { s += 5; r=s; };
+ if(r) {
+ slot = atoi(r);
+ }
+ }
if((tape_fd = tape_open(tapedev, O_WRONLY)) == -1) {
if(errno == EACCES) {
errstr = newstralloc(errstr,
return 0;
}
- fprintf(stderr, "taper: wrote label `%s' date `%s'\n", label, taper_datestamp);
+ if(slot > -1) {
+ fprintf(stderr, "taper: slot: %d wrote label `%s' date `%s'\n", slot,
+ label, taper_datestamp);
+ }
+ else {
+ fprintf(stderr, "taper: wrote label `%s' date `%s'\n", label,
+ taper_datestamp);
+ }
fflush(stderr);
#ifdef HAVE_LIBVTBLC
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-SOURCES = $(libamtape_la_SOURCES) amdd.c ammt.c $(amtapeio_SOURCES) $(amtapetype_SOURCES)
-
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
projects / debian / amanda / commitdiff