1 # amanda.conf - sample Amanda configuration file. See amanda.conf(5) for
4 org "@DEFAULT_CONFIG@" # your organization name for reports
5 mailto "@CLIENT_LOGIN@" # space separated list of operators at your site
6 dumpuser "@CLIENT_LOGIN@" # the user to run dumps under
8 inparallel 4 # maximum dumpers that will run in parallel (max 63)
9 # this maximum can be increased at compile-time,
10 # modifying MAX_DUMPERS in server-src/driverio.h
11 dumporder "sssS" # specify the priority order of each dumper
16 # b -> smallest bandwitdh
17 # B -> biggest bandwitdh
18 # try "BTBTBTBTBTBT" if you are not holding
21 taperalgo first # The algorithm used to choose which dump image to send
24 # [first|firstfit|largest|largestfit|smallest|last]
26 # first First in - first out.
27 # firstfit The first dump image that will fit
28 # on the current tape.
29 # largest The largest dump image.
30 # largestfit The largest dump image that will fit
31 # on the current tape.
32 # smallest The smallest dump image.
33 # last Last in - first out.
35 displayunit "k" # Possible values: "k|m|g|t"
37 # The unit used to print many numbers.
38 # k=kilo, m=mega, g=giga, t=tera
40 netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per sec
42 dumpcycle 4 weeks # the number of days in the normal dump cycle
43 runspercycle 20 # the number of amdump runs in dumpcycle days
44 # (4 weeks * 5 amdump runs per week -- just weekdays)
45 tapecycle 25 tapes # the number of tapes in rotation
46 # 4 weeks (dumpcycle) times 5 tapes per week (just
47 # the weekdays) plus a few to handle errors that
48 # need amflush and so we do not overwrite the full
49 # backups performed at the beginning of the previous
52 bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
53 bumppercent 20 # minimum savings (threshold) to bump level 1 -> 2
54 bumpdays 1 # minimum days at each level
55 bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
57 etimeout 300 # number of seconds per filesystem for estimates.
58 dtimeout 1800 # number of idle seconds before a dump is aborted.
59 ctimeout 30 # maximum number of seconds that amcheck waits
60 # for each client host
62 device_output_buffer_size 1280k
63 # amount of buffer space to use when writing to devices
65 # By default, Amanda can only track at most one run per calendar day. When
66 # the usetimestamps option is enabled, however, Amanda can track as many
67 # runs as you care to make.
68 # WARNING: This option is not backward-compatible. Do not enable it if you
69 # intend to downgrade your server installation to Amanda community
73 # flush-threshold-dumped, flush-threshold-scheduled, taperflush, and autoflush
74 # are used to control tape utilization. See the amanda.conf (5) manpage for
75 # details on how they work. Taping will not start until all criteria are
76 # satisfied. Here are some examples:
78 # You want to fill tapes completely even in the case of failed dumps, and
79 # don't care if some dumps are left on the holding disk after a run:
80 # flush-threshold-dumped 100 # (or more)
81 # flush-threshold-scheduled 100 # (or more)
85 # You want to improve tape performance by waiting for a complete tape of data
86 # before writing anything. However, all dumps will be flushed; none will
87 # be left on the holding disk.
88 # flush-threshold-dumped 100 # (or more)
89 # flush-threshold-scheduled 100 # (or more)
92 # You don't want to use a new tape for every run, but want to start writing
93 # to tape as soon as possible:
94 # flush-threshold-dumped 0 # (or more)
95 # flush-threshold-scheduled 100 # (or more)
98 # maxdumpsize 100k # amount of data to dump each run; see above.
100 # You want to keep the most recent dumps on holding disk, for faster recovery.
101 # Older dumps will be rotated to tape during each run.
102 # flush-threshold-dumped 300 # (or more)
103 # flush-threshold-scheduled 300 # (or more)
108 # (no restrictions; flush to tape immediately; don't flush old dumps.)
109 flush-threshold-dumped 0
110 flush-threshold-scheduled 0
114 # Specify tape device and/or tape changer. If you don't have a tape
115 # changer, and you don't want to use more than one tape per run of
116 # amdump, just comment out the definition of tpchanger.
118 # Some tape changers require tapedev to be defined; others will use
119 # their own tape device selection mechanism. Some use a separate tape
120 # changer device (changerdev), others will simply ignore this
121 # parameter. Some rely on a configuration file (changerfile) to
122 # obtain more information about tape devices, number of slots, etc;
123 # others just need to store some data in files, whose names will start
126 # At most one changerfile entry must be defined; select the most
127 # appropriate one for your configuration. If you select man-changer,
128 # keep the first one; if you decide not to use a tape changer, you may
129 # comment them all out.
131 runtapes 1 # number of tapes to be used in a single run of amdump
132 tpchanger "chg-manual" # the tape-changer glue script
133 tapedev "@EXAMPLE_TAPEDEV@" # the no-rewind tape device to be used
135 #changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer"
136 #changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer-status"
137 changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer.conf"
138 changerdev "@DEFAULT_CHANGER_DEVICE@"
140 # If you want Amanda to automatically label any non-Amanda tapes it
141 # encounters, uncomment the line below. Note that this will ERASE any
142 # non-Amanda tapes you may have, and may also ERASE any near-failing tapes.
144 ## label_new_tapes "@DEFAULT_CONFIG@-%%%"
146 maxdumpsize -1 # Maximum number of bytes the planner will schedule
147 # for a run (default: runtapes * tape_length).
148 tapetype HP-DAT # what kind of tape it is (see tapetypes below)
149 labelstr "^@DEFAULT_CONFIG@-[0-9][0-9]*$" # label constraint regex: all tapes must match
151 amrecover_do_fsf yes # amrecover will call amrestore with the
152 # -f flag for faster positioning of the tape.
153 amrecover_check_label yes # amrecover will call amrestore with the
154 # -l flag to check the label.
155 amrecover_changer "changer" # amrecover will use the changer if you restore
156 # from this device. It could be a string like 'changer' and amrecover will use your
157 # changer if you set your tape to 'changer' with 'setdevice changer' or via
158 # 'tapedev "changer"' in amanda-client.conf
160 # Specify holding disks. These are used as a temporary staging area for
161 # dumps before they are written to tape and are recommended for most sites.
162 # The advantages include: tape drive is more likely to operate in streaming
163 # mode (which reduces tape and drive wear, reduces total dump time); multiple
164 # dumps can be done in parallel (which can dramatically reduce total dump time.
165 # The main disadvantage is that dumps on the holding disk need to be flushed
166 # (with amflush) to tape after an operating system crash or a tape failure.
167 # If no holding disks are specified then all dumps will be written directly
168 # to tape. If a dump is too big to fit on the holding disk than it will be
169 # written directly to tape. If more than one holding disk is specified then
170 # they will all be used based on activity and available space.
173 comment "main holding disk"
174 directory "/dumps/amanda" # where the holding disk is
175 use -100 Mb # how much space can we use on it
176 # a non-positive value means:
177 # use all space but that value
178 chunksize 1Gb # size of chunk if you want big dump to be
179 # dumped on multiple files on holding disks
180 # N Kb/Mb/Gb split images in chunks of size N
181 # The maximum value should be
182 # (MAX_FILE_SIZE - 1Mb)
183 # 0 same as INT_MAX bytes
186 # directory "/dumps2/amanda"
190 # directory "/mnt/disk4"
195 # If amanda cannot find a tape on which to store backups, it will run
196 # as many backups as it can to the holding disks. In order to save
197 # space for unattended backups, by default, amanda will only perform
198 # incremental backups in this case, i.e., it will reserve 100% of the
199 # holding disk space for the so-called degraded mode backups.
200 # However, if you specify a different value for the `reserve'
201 # parameter, amanda will not degrade backups if they will fit in the
202 # non-reserved portion of the holding disk.
204 # reserve 30 # percent
205 # This means save at least 30% of the holding disk space for degraded
208 # The format for a ColumnSpec is a ',' seperated list of triples.
209 # Each triple consists of
210 # + the name of the column (as in ColumnNameStrings)
211 # + prefix before the column
212 # + the width of the column, if set to -1 it will be recalculated
213 # to the maximum length of a line to print.
215 # "Disk=1:17,HostName=1:10,OutKB=1:7"
217 # "Disk=1:-1,HostName=1:10,OutKB=1:7"
219 # You need only specify those colums that should be changed from
220 # the default. If nothing is specified in the configfile, the
221 # above compiled in values will be in effect, resulting in an
222 # output as it was all the time.
223 # The names of the colums are:
224 # HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime, DumpRate,
225 # TapeTime and TapeRate.
227 # columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
230 # Amanda needs a few Mb of diskspace for the log and debug files,
231 # as well as a database. This stuff can grow large, so the conf directory
232 # isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm.
233 # Create an amanda directory under there. You need a separate infofile and
234 # logdir for each configuration, so create subdirectories for each conf and
235 # put the files there. Specify the locations below.
237 # Note that, although the keyword below is infofile, it is only so for
238 # historic reasons, since now it is supposed to be a directory (unless
239 # you have selected some database format other than the `text' default)
240 infofile "@CONFIG_DIR@/@DEFAULT_CONFIG@/curinfo" # database DIRECTORY
241 logdir "@CONFIG_DIR@/@DEFAULT_CONFIG@" # log directory
242 indexdir "@CONFIG_DIR@/@DEFAULT_CONFIG@/index" # index directory
243 #tapelist "@CONFIG_DIR@/@DEFAULT_CONFIG@/tapelist" # list of used tapes
244 # tapelist is stored, by default, in the directory that contains amanda.conf
248 # Define the type of tape you use here, and use it in "tapetype"
249 # above. Some typical types of tapes are included here. The tapetype
250 # tells amanda how many MB will fit on the tape, how big the filemarks
251 # are, and how fast the tape device is.
253 # A filemark is the amount of wasted space every time a tape section
254 # ends. If you run `make tapetype' in tape-src, you'll get a program
255 # that generates tapetype entries, but it is slow as hell, use it only
256 # if you really must and, if you do, make sure you post the data to
257 # the amanda mailing list, so that others can use what you found out
258 # by searching the archives.
260 # For completeness Amanda should calculate the inter-record gaps too,
261 # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using
262 # 9 tracks for amanda and need IRG calculations? Drop me a note if
265 # If you want amanda to print postscript paper tape labels
266 # add a line after the comment in the tapetype of the form
267 # lbl-templ "/path/to/postscript/template/label.ps"
269 # if you want the label to go to a printer other than the default
270 # for your system, you can also add a line above for a different
271 # printer. (i usually add that line after the dumpuser specification)
273 # dumpuser "operator" # the user to run dumps under
274 # printer "mypostscript" # printer to print paper label on
276 # here is an example of my definition for an EXB-8500
278 # define tapetype EXB-8500 {
280 # lbl-templ "@CONFIG_DIR@/config/lbl.exabyte.ps"
284 define tapetype QIC-60 {
285 comment "Archive Viper"
287 filemark 100 kbytes # don't know a better value
288 speed 100 kbytes # dito
291 define tapetype DEC-DLT2000 {
292 comment "DEC Differential Digital Linear Tape 2000"
298 # goluboff@butch.Colorado.EDU
299 # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
300 define tapetype DLT {
301 comment "DLT tape drives"
302 length 20000 mbytes # 20 Gig tapes
303 filemark 2000 kbytes # I don't know what this means
304 speed 1536 kbytes # 1.5 Mb/s
307 define tapetype SURESTORE-1200E {
308 comment "HP AutoLoader"
314 define tapetype EXB-8500 {
315 comment "Exabyte EXB-8500 drive on decent machine"
321 define tapetype EXB-8200 {
322 comment "Exabyte EXB-8200 drive on decent machine"
328 define tapetype HP-DAT {
329 comment "DAT tape drives"
330 # data provided by Rob Browning <rlb@cs.utexas.edu>
336 define tapetype DAT {
337 comment "DAT tape drives"
338 length 1000 mbytes # these numbers are not accurate
339 filemark 100 kbytes # but you get the idea
343 define tapetype MIMSY-MEGATAPE {
344 comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
347 speed 170 kbytes # limited by the Emulex bus interface, ugh
350 define tapetype SEAGATE-ULTRIUM-LTO {
351 comment "SEAGATE ULTRIUM 06242 LTO, compression off"
359 # These are referred to by the disklist file. The dumptype specifies
360 # certain parameters for dumping including:
361 # auth - authentication scheme to use between server and client.
362 # Valid values are "bsd", "krb4", "krb5" and "ssh".
363 # Default: [auth bsd]
364 # comment - just a comment string
365 # comprate - set default compression rate. Should be followed by one or
366 # two numbers, optionally separated by a comma. The 1st is
367 # the full compression rate; the 2nd is the incremental rate.
368 # If the second is omitted, it is assumed equal to the first.
369 # The numbers represent the amount of the original file the
370 # compressed file is expected to take up.
371 # Default: [comprate 0.50, 0.50]
372 # compress - specify compression of the backed up data. Valid values are:
373 # "none" - don't compress the dump output.
374 # "client best" - compress on the client using the best (and
375 # probably slowest) algorithm.
376 # "client fast" - compress on the client using fast algorithm.
377 # "client custom" - compress using your custom client compression program.
378 # use client_custom_compress "PROG" to specify
379 # the custom compression program.
380 # PROG must not contain white space.
381 # "server best" - compress on the tape host using the best (and
382 # probably slowest) algorithm.
383 # "server fast" - compress on the tape host using a fast
384 # algorithm. This may be useful when a fast
385 # tape host is backing up slow clients.
386 # "server custom" - compress using your server custom compression program.
387 # use server_custom_compress "PROG" to specify
388 # the custom compression program.
389 # PROG must not contain white space.
390 # Default: [compress client fast]
391 # dumpcycle - set the number of days in the dump cycle, ie, set how often a
392 # full dump should be performed. Default: from DUMPCYCLE above
393 # estimate Determine the way AMANDA does it's estimate.
394 # "client" - Use the same program as the dumping program,
395 # this is the most accurate way to do estimates,
396 # but it can take a long time.
397 # "calcsize" - Use a faster program to do estimates, but the
398 # result is less accurate.
399 # "server" - Use only statistics from the previous run to
401 # it takes only a few seconds but the result is not
402 # accurate if your disk usage changes from day to day.
404 # encrypt - specify encryption of the backed up data. Valid values are:
405 # "none" - don't encrypt the dump output.
406 # "client" - encrypt on the client using the program specified by
407 # client_encrypt "PROG".
408 # Use client_decrypt_option to specify the decrypt-
409 # parameter, default is "-d".
410 # PROG and decrypt-parameter must not contain white space.
411 # "server" - encrypt on the server using the program specified by
412 # server_encrypt "PROG".
413 # Use server_decrypt_option to specify the decrypt-
414 # parameter, default is "-d".
415 # PROG and decrypt-parameter must not contain white space.
417 # exclude - specify files and directories to be excluded from the dump.
418 # Useful with gnutar only; silently ignored by dump and samba.
420 # "pattern" - a shell glob pattern defining which files
422 # gnutar gets --exclude="pattern"
423 # list "filename" - a file (on the client!) containing patterns
424 # re's (1 per line) defining which files to
426 # gnutar gets --exclude-from="filename"
427 # Note that the `full pathname' of a file within its
428 # filesystem starts with `./', because of the way amanda runs
429 # gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
430 # the final dot!) Thus, if you're backing up `/usr' with a
431 # diskfile entry like ``host /usr gnutar-root', but you don't
432 # want to backup /usr/tmp, your exclude list should contain
433 # the pattern `./tmp', as this is relative to the `/usr' above.
434 # Please refer to the man-page of gnutar for more information.
435 # If a relative pathname is specified as the exclude list,
436 # it is searched from within the directory that is
437 # going to be backed up.
438 # Default: include all files
439 # holdingdisk - should the holding disk be used for this dump. Useful for
440 # dumping the holding disk itself. Default: [holdingdisk auto]
441 # "never" - Never use the holding disk.
442 # "auto" - Use the holding disk if possible.
443 # "required" - Always use the holding disk.
444 # ignore - do not back this filesystem up. Useful for sharing a single
445 # disklist in several configurations.
446 # index - keep an index of the files backed up. Default: [index no]
447 # kencrypt - encrypt the data stream between the client and server.
448 # Default: [kencrypt no]
449 # maxdumps - max number of concurrent dumps to run on the client.
450 # Default: [maxdumps 1]
451 # maxpromoteday - max number of day for a promotion, set it 0 if you don't
452 # want promotion, set it to 1 or 2 if your disk get
455 # priority - priority level of the dump. Valid levels are "low", "medium"
456 # or "high". These are really only used when Amanda has no
457 # tape to write to because of some error. In that "degraded
458 # mode", as many incrementals as will fit on the holding disk
459 # are done, higher priority first, to insure the important
460 # disks are at least dumped. Default: [priority medium]
461 # program - specify the dump system to use. Valid values are "DUMP",
462 # or "GNUTAR". Default: [program "DUMP"].
463 # record - record the backup in the time-stamp-database of the backup
464 # program (e.g. /etc/dumpdates for DUMP or
465 # @GNUTAR_LISTED_INCREMENTAL_DIRX@ for GNUTAR.).
466 # Default: [record yes]
467 # skip-full - skip the disk when a level 0 is due, to allow full backups
468 # outside Amanda, eg when the machine is in single-user mode.
469 # skip-incr - skip the disk when the level 0 is NOT due. This is used in
470 # archive configurations, where only full dumps are done and
472 # starttime - delay the start of the dump? Default: no delay
473 # strategy - set the dump strategy. Valid strategies are currently:
474 # "standard" - the standard one.
475 # "nofull" - do level 1 dumps every time. This can be used,
476 # for example, for small root filesystems that
477 # only change slightly relative to a site-wide
478 # prototype. Amanda then backs up just the
480 # "noinc" - do level 0 dumps every time.
481 # "skip" - skip all dumps. Useful for sharing a single
482 # disklist in several configurations.
483 # "incronly" - do only incremental dumps. This is similar
484 # to strategy 'nofull', but will increase
485 # the dump level as usual. Full dumps will
486 # only be performed when an 'amadmin force'
488 # Default: [strategy standard]
489 # tape_splitsize - (optional) split dump file into pieces of a specified size.
490 # This allows dumps to be spread across multiple tapes, and can
491 # potentially make more efficient use of tape space. Note that
492 # if this value is too large (more than half the size of the
493 # average dump being split), substantial tape space can be
494 # wasted. If too small, large dumps will be split into
495 # innumerable tiny dumpfiles, adding to restoration complexity.
496 # A good rule of thumb, usually, is 1/10 of the size of your
497 # tape. Default: [disabled]
498 # split_diskbuffer - (optional) When dumping a split dump in PORT-WRITE
499 # mode (usually meaning "no holding disk"), buffer the split
500 # chunks to a file in the directory specified by this option.
502 # fallback_splitsize - (optional) When dumping a split dump in PORT-WRITE
503 # mode, if no split_diskbuffer is specified (or if we somehow
504 # fail to use our split_diskbuffer), we must buffer split
505 # chunks in memory. This specifies the maximum size split
506 # chunks can be in this scenario, and thus the maximum amount
507 # of memory consumed for in-memory splitting. Default: [10m]
509 # Note that you may specify previously defined dumptypes as a shorthand way of
510 # defining parameters.
512 define dumptype global {
513 comment "Global definitions"
514 # This is quite useful for setting global parameters, so you don't have
515 # to type them everywhere. All dumptype definitions in this sample file
516 # do include these definitions, either directly or indirectly.
517 # There's nothing special about the name `global'; if you create any
518 # dumptype that does not contain the word `global' or the name of any
519 # other dumptype that contains it, these definitions won't apply.
520 # Note that these definitions may be overridden in other
521 # dumptypes, if the redefinitions appear *after* the `global'
523 # You may want to use this for globally enabling or disabling
524 # indexing, recording, etc. Some examples:
527 # split_diskbuffer "/raid/amanda"
528 # fallback_splitsize 64m
531 define dumptype always-full {
533 comment "Full dump of this filesystem always"
539 # Dumptypes for gnutar
540 define dumptype root-tar {
543 comment "root partitions dumped with tar"
546 # exclude list "@CONFIG_DIR@/exclude.gtar"
550 define dumptype user-tar {
552 comment "user partitions dumped with tar"
556 define dumptype user-tar-span {
559 comment "tape-spanning user partitions dumped with tar"
563 define dumptype high-tar {
565 comment "partitions dumped with tar"
569 define dumptype comp-root-tar {
571 comment "Root partitions with compression"
575 define dumptype comp-user-tar {
580 define dumptype comp-user-tar-span {
585 define dumptype holding-disk {
587 comment "The master-host holding disk itself"
588 holdingdisk never # do not use the holding disk
592 define dumptype comp-user {
594 comment "Non-root partitions on reasonably fast machines"
599 define dumptype comp-user-span {
602 comment "Tape-spanning non-root partitions on reasonably fast machines"
607 define dumptype nocomp-user {
609 comment "Non-root partitions on slow machines"
613 define dumptype nocomp-user-span {
615 comment "Tape-spanning non-root partitions on slow machines"
619 define dumptype comp-root {
621 comment "Root partitions with compression"
626 define dumptype nocomp-root {
628 comment "Root partitions without compression"
632 define dumptype comp-high {
634 comment "very important partitions on fast machines"
639 define dumptype nocomp-high {
641 comment "very important partitions on slow machines"
645 define dumptype nocomp-test {
647 comment "test dump without compression, no /etc/dumpdates recording"
653 define dumptype comp-test {
655 comment "test dump with compression, no /etc/dumpdates recording"
659 define dumptype custom-compress {
662 comment "custom client compression dumped with tar"
663 compress client custom
664 client_custom_compress "/usr/bin/bzip2"
667 define dumptype server-encrypt-fast {
670 comment "fast client compression and server symmetric encryption"
673 server_encrypt "/usr/sbin/amcrypt"
674 server_decrypt_option "-d"
677 define dumptype client-encrypt-nocomp {
680 comment "no compression and client symmetric encryption"
683 client_encrypt "/usr/sbin/amcrypt"
684 client_decrypt_option "-d"
688 # To use gpg public-key encryption, gpg does compress with zlib by default.
689 # Thus, no need to specify compress
691 #define dumptype gpg-encrypt {
694 # comment "server public-key encryption, dumped with tar"
697 # server_encrypt "/usr/sbin/amgpgcrypt"
698 # server_decrypt_option "-d"
704 # These are referred to by the disklist file. They define the attributes
705 # of the network interface that the remote machine is accessed through.
706 # Notes: - netusage above defines the attributes that are used when the
707 # disklist entry doesn't specify otherwise.
708 # - the values below are only samples.
709 # - specifying an interface does not force the traffic to pass
710 # through that interface. Your OS routing tables do that. This
711 # is just a mechanism to stop Amanda trashing your network.
713 # use - bandwidth above which amanda won't start
714 # backups using this interface. Note that if
715 # a single backup will take more than that,
716 # amanda won't try to make it run slower!
718 define interface local {
719 comment "a local disk"
723 #define interface le0 {
724 # comment "10 Mbps ethernet"
728 # You may include other amanda configuration files, so you can share
729 # dumptypes, tapetypes and interface definitions among several
732 #includefile "@CONFIG_DIR@/amanda.conf.main"