# The unit used to print many numbers.
# k=kilo, m=mega, g=giga, t=tera
-netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec
+netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 4 weeks # the number of days in the normal dump cycle
runspercycle 20 # the number of amdump runs in dumpcycle days
ctimeout 30 # maximum number of seconds that amcheck waits
# for each client host
-tapebufs 20 # A positive integer telling taper how many
- # 32k buffers to allocate. The default is 20 (640k).
+device_output_buffer_size 1280k
+ # amount of buffer space to use when writing to devices
# By default, Amanda can only track at most one run per calendar day. When
# the usetimestamps option is enabled, however, Amanda can track as many
# edition 2.5
usetimestamps yes
+# flush-threshold-dumped, flush-threshold-scheduled, taperflush, and autoflush
+# are used to control tape utilization. See the amanda.conf (5) manpage for
+# details on how they work. Taping will not start until all criteria are
+# satisfied. Here are some examples:
+#
+# You want to fill tapes completely even in the case of failed dumps, and
+# don't care if some dumps are left on the holding disk after a run:
+# flush-threshold-dumped 100 # (or more)
+# flush-threshold-scheduled 100 # (or more)
+# taperflush 100
+# autoflush yes
+#
+# You want to improve tape performance by waiting for a complete tape of data
+# before writing anything. However, all dumps will be flushed; none will
+# be left on the holding disk.
+# flush-threshold-dumped 100 # (or more)
+# flush-threshold-scheduled 100 # (or more)
+# taperflush 0
+#
+# You don't want to use a new tape for every run, but want to start writing
+# to tape as soon as possible:
+# flush-threshold-dumped 0 # (or more)
+# flush-threshold-scheduled 100 # (or more)
+# taperflush 100
+# autoflush yes
+# maxdumpsize 100k # amount of data to dump each run; see above.
+#
+# You want to keep the most recent dumps on holding disk, for faster recovery.
+# Older dumps will be rotated to tape during each run.
+# flush-threshold-dumped 300 # (or more)
+# flush-threshold-scheduled 300 # (or more)
+# taperflush 300
+# autoflush yes
+#
+# Defaults:
+# (no restrictions; flush to tape immediately; don't flush old dumps.)
+flush-threshold-dumped 0
+flush-threshold-scheduled 0
+taperflush 0
+autoflush no
-# Specify tape device and/or tape changer. If you don't have a tape
-# changer, and you don't want to use more than one tape per run of
-# amdump, just comment out the definition of tpchanger.
+# Specify tape device or tape changer.
-# Some tape changers require tapedev to be defined; others will use
-# their own tape device selection mechanism. Some use a separate tape
-# changer device (changerdev), others will simply ignore this
-# parameter. Some rely on a configuration file (changerfile) to
-# obtain more information about tape devices, number of slots, etc;
-# others just need to store some data in files, whose names will start
-# with changerfile.
+runtapes 1 # number of tapes to be used in a single run of amdump
+tapedev "@EXAMPLE_TAPEDEV@" # tape changer or device to use
-# At most one changerfile entry must be defined; select the most
-# appropriate one for your configuration. If you select man-changer,
-# keep the first one; if you decide not to use a tape changer, you may
-# comment them all out.
+# To use vtapes, create some slotN directories (slot0, slot1, etc.) under
+# /var/amanda/vtapes and use this tapedev:
+## tapedev "chg-disk:/var/amanda/vtapes"
-runtapes 1 # number of tapes to be used in a single run of amdump
-tpchanger "chg-manual" # the tape-changer glue script
-tapedev "@DEFAULT_TAPE_DEVICE@" # the no-rewind tape device to be used
-rawtapedev "@DEFAULT_RAW_TAPE_DEVICE@" # the raw device to be used (ftape only)
-#changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer"
-#changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer-status"
-changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer.conf"
-changerdev "@DEFAULT_CHANGER_DEVICE@"
+# To use a tape library, uncomment this definition. See amanda-changers(7)
+# for more configuration options.
+#
+# define changer myrobot {
+# tpchanger "chg-robot:/dev/sg0" # your changer device file
+# tapedev "tape:@EXAMPLE_TAPEDEV@" # your tape drive device file
+# }
+# tapedev "myrobot"
# If you want Amanda to automatically label any non-Amanda tapes it
# encounters, uncomment the line below. Note that this will ERASE any
# non-Amanda tapes you may have, and may also ERASE any near-failing tapes.
# Use with caution.
-## label_new_tapes "@DEFAULT_CONFIG@-%%%"
+## autolabel "@DEFAULT_CONFIG@-%%%" empty
maxdumpsize -1 # Maximum number of bytes the planner will schedule
# for a run (default: runtapes * tape_length).
tapetype HP-DAT # what kind of tape it is (see tapetypes below)
labelstr "^@DEFAULT_CONFIG@-[0-9][0-9]*$" # label constraint regex: all tapes must match
-amrecover_do_fsf yes # amrecover will call amrestore with the
- # -f flag for faster positioning of the tape.
-amrecover_check_label yes # amrecover will call amrestore with the
- # -l flag to check the label.
-amrecover_changer "@DEFAULT_TAPE_DEVICE@" # amrecover will use the changer if you restore
- # from this device.
- # It could be a string like 'changer' and
- # amrecover will use your changer if you
- # set your tape with 'settape changer'
+amrecover_changer "changer" # amrecover will use the changer if you restore
+ # from this device. It could be a string like 'changer' and amrecover will use your
+ # changer if you set your tape to 'changer' with 'setdevice changer' or via
+ # 'tapedev "changer"' in amanda-client.conf
# Specify holding disks. These are used as a temporary staging area for
# dumps before they are written to tape and are recommended for most sites.
# This means save at least 30% of the holding disk space for degraded
# mode backups.
-autoflush no #
-# if autoflush is set to yes, then amdump will schedule all dump on
-# holding disks to be flush to tape during the run.
-
# The format for a ColumnSpec is a ',' seperated list of triples.
# Each triple consists of
# + the name of the column (as in ColumnNameStrings)
# are, and how fast the tape device is.
# A filemark is the amount of wasted space every time a tape section
-# ends. If you run `make tapetype' in tape-src, you'll get a program
-# that generates tapetype entries, but it is slow as hell, use it only
-# if you really must and, if you do, make sure you post the data to
-# the amanda mailing list, so that others can use what you found out
-# by searching the archives.
+# ends.
# For completeness Amanda should calculate the inter-record gaps too,
# but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using
# lbl-templ "@CONFIG_DIR@/config/lbl.exabyte.ps"
# }
+define tapetype global {
+ part_size 3G
+ part_cache_type none
+}
define tapetype QIC-60 {
+ global
comment "Archive Viper"
length 60 mbytes
filemark 100 kbytes # don't know a better value
}
define tapetype DEC-DLT2000 {
+ global
comment "DEC Differential Digital Linear Tape 2000"
length 15000 mbytes
filemark 8 kbytes
# goluboff@butch.Colorado.EDU
# in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
define tapetype DLT {
+ global
comment "DLT tape drives"
length 20000 mbytes # 20 Gig tapes
filemark 2000 kbytes # I don't know what this means
}
define tapetype SURESTORE-1200E {
+ global
comment "HP AutoLoader"
length 3900 mbytes
filemark 100 kbytes
}
define tapetype EXB-8500 {
+ global
comment "Exabyte EXB-8500 drive on decent machine"
length 4200 mbytes
filemark 48 kbytes
}
define tapetype EXB-8200 {
+ global
comment "Exabyte EXB-8200 drive on decent machine"
length 2200 mbytes
filemark 2130 kbytes
}
define tapetype HP-DAT {
+ global
comment "DAT tape drives"
# data provided by Rob Browning <rlb@cs.utexas.edu>
length 1930 mbytes
}
define tapetype DAT {
+ global
comment "DAT tape drives"
length 1000 mbytes # these numbers are not accurate
filemark 100 kbytes # but you get the idea
}
define tapetype MIMSY-MEGATAPE {
+ global
comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
length 2200 mbytes
filemark 2130 kbytes
speed 170 kbytes # limited by the Emulex bus interface, ugh
}
+define tapetype SEAGATE-ULTRIUM-LTO {
+ global
+ comment "SEAGATE ULTRIUM 06242 LTO, compression off"
+ length 99584 mbytes
+ filemark 0 kbytes
+ speed 11288 kps
+}
# dumptypes
#
# These are referred to by the disklist file. The dumptype specifies
# certain parameters for dumping including:
# auth - authentication scheme to use between server and client.
-# Valid values are "bsd", "krb4", "krb5" and "ssh".
-# Default: [auth bsd]
+# Valid values are "bsd", "bsdudp", "bsdtcp", "krb5", "local",
+# "rsh" and "ssh".
+# Default: [auth "bsdtcp"]
# comment - just a comment string
# comprate - set default compression rate. Should be followed by one or
# two numbers, optionally separated by a comma. The 1st is
# program - specify the dump system to use. Valid values are "DUMP",
# or "GNUTAR". Default: [program "DUMP"].
# record - record the backup in the time-stamp-database of the backup
-# program (e.g. /etc/dumpdates for DUMP or
+# program (e.g. /var/lib/dumpdates for DUMP or
# @GNUTAR_LISTED_INCREMENTAL_DIRX@ for GNUTAR.).
# Default: [record yes]
# skip-full - skip the disk when a level 0 is due, to allow full backups
# only be performed when an 'amadmin force'
# has been issued
# Default: [strategy standard]
-# tape_splitsize - (optional) split dump file 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: [disabled]
-# split_diskbuffer - (optional) 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: [none]
-# fallback_splitsize - (optional) 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. Default: [10m]
#
# Note that you may specify previously defined dumptypes as a shorthand way of
# defining parameters.
# indexing, recording, etc. Some examples:
# index yes
# record no
- # split_diskbuffer "/raid/amanda"
- # fallback_splitsize 64m
+ # auth "bsdtcp"
}
define dumptype always-full {
define dumptype user-tar-span {
root-tar
- tape_splitsize 3 Gb
comment "tape-spanning user partitions dumped with tar"
priority medium
}
define dumptype comp-user-span {
global
- tape_splitsize 5 Gb
comment "Tape-spanning non-root partitions on reasonably fast machines"
compress client fast
priority medium
define dumptype nocomp-test {
global
- comment "test dump without compression, no /etc/dumpdates recording"
+ comment "test dump without compression, no /var/lib/dumpdates recording"
compress none
record no
priority medium
define dumptype comp-test {
nocomp-test
- comment "test dump with compression, no /etc/dumpdates recording"
+ comment "test dump with compression, no /var/lib/dumpdates recording"
compress client fast
}
define interface local {
comment "a local disk"
- use 1000 kbps
+ use 8000 kbps
+}
+
+#define interface le0 {
+# comment "10 Mbps ethernet"
+# use 400 kbps
+#}
+
+#define application-tool and dumptype for the amgtar application
+define application-tool app_amgtar {
+ comment "amgtar"
+ plugin "amgtar"
+ #property "GNUTAR-PATH" "/path/to/gtar"
+ #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
+ #default from gnutar_list_dir setting in amanda-client.conf
+}
+
+define dumptype dt_amgtar {
+ program "APPLICATION"
+ application "app_amgtar"
+}
+
+#define application-tool and dumptype for the amstar application
+define application-tool app_amstar {
+ comment "amstar"
+ plugin "amstar"
+ #property "STAR-PATH" "/path/to/star"
+ #property "STAR-TARDUMP" "/path/to/tardumps" # default /etc/tardumps
+ #property "STAR-DLE-TARDUMP" "no"
+ # if 'yes' then create a different tardump file for each DLE,
+ # it is required if you do many dump in parallel (maxdump>1)
}
-define interface le0 {
- comment "10 Mbps ethernet"
- use 400 kbps
+define dumptype dt_amstar {
+ program "APPLICATION"
+ application "app_amstar"
+}
+
+#define a script-tool to send an email
+define script-tool sc-email {
+ comment "script-email"
+ plugin "script-email"
+ execute_on pre-dle-amcheck, pre-host-amcheck, post-dle-amcheck, post-host-amcheck, pre-dle-estimate, pre-host-estimate, post-dle-estimate, post-host-estimate, pre-dle-backup, pre-host-backup, post-dle-backup, post-host-backup
+ execute_where server # or client
+ property "mailto" "martinea"
+}
+#your dumptype must include: script "sc-email"
+#to use the script
+
+define interactivity inter_tty {
+ plugin "tty"
+}
+define interactivity inter_email {
+ plugin "email"
+ property "mailto" "admin1" "admin2"
+ property "resend-delay" "10"
+ property "check-file" "/tmp/email_input"
+ property "check-file-delay" "10"
+}
+define interactivity inter_tty_email {
+ plugin "tty_email"
+ property "mailto" "admin1" "admin2"
+ property "resend-delay" "10"
+ property "check-file" "/tmp/email_input"
+ property "check-file-delay" "10"
+}
+interactivity "inter_tty_email"
+
+define taperscan taper_traditional {
+ comment "traditional"
+ plugin "traditional"
+}
+define taperscan taper_oldest {
+ comment "oldest"
+ plugin "oldest"
+}
+define taperscan taper_lexical {
+ comment "lexical"
+ plugin "lexical"
}
+taperscan "taper_lexical"
# You may include other amanda configuration files, so you can share
# dumptypes, tapetypes and interface definitions among several
projects / debian / amanda / blobdiff