1 # amanda.conf - sample Amanda configuration file. See amanda.conf(5) for
4 org "DailySet1" # your organization name for reports
5 mailto "martinea" # space separated list of operators at your site
6 dumpuser "martinea" # 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 "tape:/dev/YOUR-TAPE-DEVICE-HERE" # the no-rewind tape device to be used
135 #changerfile "/etc/amanda/DailySet1/changer"
136 #changerfile "/etc/amanda/DailySet1/changer-status"
137 changerfile "/etc/amanda/DailySet1/changer.conf"
138 changerdev "/dev/null"
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 "DailySet1-%%%"
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 "^DailySet1-[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 "/etc/amanda/DailySet1/curinfo" # database DIRECTORY
241 logdir "/etc/amanda/DailySet1" # log directory
242 indexdir "/etc/amanda/DailySet1/index" # index directory
243 #tapelist "/etc/amanda/DailySet1/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
256 # For completeness Amanda should calculate the inter-record gaps too,
257 # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using
258 # 9 tracks for amanda and need IRG calculations? Drop me a note if
261 # If you want amanda to print postscript paper tape labels
262 # add a line after the comment in the tapetype of the form
263 # lbl-templ "/path/to/postscript/template/label.ps"
265 # if you want the label to go to a printer other than the default
266 # for your system, you can also add a line above for a different
267 # printer. (i usually add that line after the dumpuser specification)
269 # dumpuser "operator" # the user to run dumps under
270 # printer "mypostscript" # printer to print paper label on
272 # here is an example of my definition for an EXB-8500
274 # define tapetype EXB-8500 {
276 # lbl-templ "/etc/amanda/config/lbl.exabyte.ps"
280 define tapetype QIC-60 {
281 comment "Archive Viper"
283 filemark 100 kbytes # don't know a better value
284 speed 100 kbytes # dito
287 define tapetype DEC-DLT2000 {
288 comment "DEC Differential Digital Linear Tape 2000"
294 # goluboff@butch.Colorado.EDU
295 # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
296 define tapetype DLT {
297 comment "DLT tape drives"
298 length 20000 mbytes # 20 Gig tapes
299 filemark 2000 kbytes # I don't know what this means
300 speed 1536 kbytes # 1.5 Mb/s
303 define tapetype SURESTORE-1200E {
304 comment "HP AutoLoader"
310 define tapetype EXB-8500 {
311 comment "Exabyte EXB-8500 drive on decent machine"
317 define tapetype EXB-8200 {
318 comment "Exabyte EXB-8200 drive on decent machine"
324 define tapetype HP-DAT {
325 comment "DAT tape drives"
326 # data provided by Rob Browning <rlb@cs.utexas.edu>
332 define tapetype DAT {
333 comment "DAT tape drives"
334 length 1000 mbytes # these numbers are not accurate
335 filemark 100 kbytes # but you get the idea
339 define tapetype MIMSY-MEGATAPE {
340 comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
343 speed 170 kbytes # limited by the Emulex bus interface, ugh
346 define tapetype SEAGATE-ULTRIUM-LTO {
347 comment "SEAGATE ULTRIUM 06242 LTO, compression off"
355 # These are referred to by the disklist file. The dumptype specifies
356 # certain parameters for dumping including:
357 # auth - authentication scheme to use between server and client.
358 # Valid values are "bsd", "krb4", "krb5" and "ssh".
359 # Default: [auth bsd]
360 # comment - just a comment string
361 # comprate - set default compression rate. Should be followed by one or
362 # two numbers, optionally separated by a comma. The 1st is
363 # the full compression rate; the 2nd is the incremental rate.
364 # If the second is omitted, it is assumed equal to the first.
365 # The numbers represent the amount of the original file the
366 # compressed file is expected to take up.
367 # Default: [comprate 0.50, 0.50]
368 # compress - specify compression of the backed up data. Valid values are:
369 # "none" - don't compress the dump output.
370 # "client best" - compress on the client using the best (and
371 # probably slowest) algorithm.
372 # "client fast" - compress on the client using fast algorithm.
373 # "client custom" - compress using your custom client compression program.
374 # use client_custom_compress "PROG" to specify
375 # the custom compression program.
376 # PROG must not contain white space.
377 # "server best" - compress on the tape host using the best (and
378 # probably slowest) algorithm.
379 # "server fast" - compress on the tape host using a fast
380 # algorithm. This may be useful when a fast
381 # tape host is backing up slow clients.
382 # "server custom" - compress using your server custom compression program.
383 # use server_custom_compress "PROG" to specify
384 # the custom compression program.
385 # PROG must not contain white space.
386 # Default: [compress client fast]
387 # dumpcycle - set the number of days in the dump cycle, ie, set how often a
388 # full dump should be performed. Default: from DUMPCYCLE above
389 # estimate Determine the way AMANDA does it's estimate.
390 # "client" - Use the same program as the dumping program,
391 # this is the most accurate way to do estimates,
392 # but it can take a long time.
393 # "calcsize" - Use a faster program to do estimates, but the
394 # result is less accurate.
395 # "server" - Use only statistics from the previous run to
397 # it takes only a few seconds but the result is not
398 # accurate if your disk usage changes from day to day.
400 # encrypt - specify encryption of the backed up data. Valid values are:
401 # "none" - don't encrypt the dump output.
402 # "client" - encrypt on the client using the program specified by
403 # client_encrypt "PROG".
404 # Use client_decrypt_option to specify the decrypt-
405 # parameter, default is "-d".
406 # PROG and decrypt-parameter must not contain white space.
407 # "server" - encrypt on the server using the program specified by
408 # server_encrypt "PROG".
409 # Use server_decrypt_option to specify the decrypt-
410 # parameter, default is "-d".
411 # PROG and decrypt-parameter must not contain white space.
413 # exclude - specify files and directories to be excluded from the dump.
414 # Useful with gnutar only; silently ignored by dump and samba.
416 # "pattern" - a shell glob pattern defining which files
418 # gnutar gets --exclude="pattern"
419 # list "filename" - a file (on the client!) containing patterns
420 # re's (1 per line) defining which files to
422 # gnutar gets --exclude-from="filename"
423 # Note that the `full pathname' of a file within its
424 # filesystem starts with `./', because of the way amanda runs
425 # gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
426 # the final dot!) Thus, if you're backing up `/usr' with a
427 # diskfile entry like ``host /usr gnutar-root', but you don't
428 # want to backup /usr/tmp, your exclude list should contain
429 # the pattern `./tmp', as this is relative to the `/usr' above.
430 # Please refer to the man-page of gnutar for more information.
431 # If a relative pathname is specified as the exclude list,
432 # it is searched from within the directory that is
433 # going to be backed up.
434 # Default: include all files
435 # holdingdisk - should the holding disk be used for this dump. Useful for
436 # dumping the holding disk itself. Default: [holdingdisk auto]
437 # "never" - Never use the holding disk.
438 # "auto" - Use the holding disk if possible.
439 # "required" - Always use the holding disk.
440 # ignore - do not back this filesystem up. Useful for sharing a single
441 # disklist in several configurations.
442 # index - keep an index of the files backed up. Default: [index no]
443 # kencrypt - encrypt the data stream between the client and server.
444 # Default: [kencrypt no]
445 # maxdumps - max number of concurrent dumps to run on the client.
446 # Default: [maxdumps 1]
447 # maxpromoteday - max number of day for a promotion, set it 0 if you don't
448 # want promotion, set it to 1 or 2 if your disk get
451 # priority - priority level of the dump. Valid levels are "low", "medium"
452 # or "high". These are really only used when Amanda has no
453 # tape to write to because of some error. In that "degraded
454 # mode", as many incrementals as will fit on the holding disk
455 # are done, higher priority first, to insure the important
456 # disks are at least dumped. Default: [priority medium]
457 # program - specify the dump system to use. Valid values are "DUMP",
458 # or "GNUTAR". Default: [program "DUMP"].
459 # record - record the backup in the time-stamp-database of the backup
460 # program (e.g. /var/lib/dumpdates for DUMP or
461 # @GNUTAR_LISTED_INCREMENTAL_DIRX@ for GNUTAR.).
462 # Default: [record yes]
463 # skip-full - skip the disk when a level 0 is due, to allow full backups
464 # outside Amanda, eg when the machine is in single-user mode.
465 # skip-incr - skip the disk when the level 0 is NOT due. This is used in
466 # archive configurations, where only full dumps are done and
468 # starttime - delay the start of the dump? Default: no delay
469 # strategy - set the dump strategy. Valid strategies are currently:
470 # "standard" - the standard one.
471 # "nofull" - do level 1 dumps every time. This can be used,
472 # for example, for small root filesystems that
473 # only change slightly relative to a site-wide
474 # prototype. Amanda then backs up just the
476 # "noinc" - do level 0 dumps every time.
477 # "skip" - skip all dumps. Useful for sharing a single
478 # disklist in several configurations.
479 # "incronly" - do only incremental dumps. This is similar
480 # to strategy 'nofull', but will increase
481 # the dump level as usual. Full dumps will
482 # only be performed when an 'amadmin force'
484 # Default: [strategy standard]
485 # tape_splitsize - (optional) split dump file into pieces of a specified size.
486 # This allows dumps to be spread across multiple tapes, and can
487 # potentially make more efficient use of tape space. Note that
488 # if this value is too large (more than half the size of the
489 # average dump being split), substantial tape space can be
490 # wasted. If too small, large dumps will be split into
491 # innumerable tiny dumpfiles, adding to restoration complexity.
492 # A good rule of thumb, usually, is 1/10 of the size of your
493 # tape. Default: [disabled]
494 # split_diskbuffer - (optional) When dumping a split dump in PORT-WRITE
495 # mode (usually meaning "no holding disk"), buffer the split
496 # chunks to a file in the directory specified by this option.
498 # fallback_splitsize - (optional) When dumping a split dump in PORT-WRITE
499 # mode, if no split_diskbuffer is specified (or if we somehow
500 # fail to use our split_diskbuffer), we must buffer split
501 # chunks in memory. This specifies the maximum size split
502 # chunks can be in this scenario, and thus the maximum amount
503 # of memory consumed for in-memory splitting. Default: [10m]
505 # Note that you may specify previously defined dumptypes as a shorthand way of
506 # defining parameters.
508 define dumptype global {
509 comment "Global definitions"
510 # This is quite useful for setting global parameters, so you don't have
511 # to type them everywhere. All dumptype definitions in this sample file
512 # do include these definitions, either directly or indirectly.
513 # There's nothing special about the name `global'; if you create any
514 # dumptype that does not contain the word `global' or the name of any
515 # other dumptype that contains it, these definitions won't apply.
516 # Note that these definitions may be overridden in other
517 # dumptypes, if the redefinitions appear *after* the `global'
519 # You may want to use this for globally enabling or disabling
520 # indexing, recording, etc. Some examples:
523 # split_diskbuffer "/raid/amanda"
524 # fallback_splitsize 64m
527 define dumptype always-full {
529 comment "Full dump of this filesystem always"
535 # Dumptypes for gnutar
536 define dumptype root-tar {
539 comment "root partitions dumped with tar"
542 # exclude list "/etc/amanda/exclude.gtar"
546 define dumptype user-tar {
548 comment "user partitions dumped with tar"
552 define dumptype user-tar-span {
555 comment "tape-spanning user partitions dumped with tar"
559 define dumptype high-tar {
561 comment "partitions dumped with tar"
565 define dumptype comp-root-tar {
567 comment "Root partitions with compression"
571 define dumptype comp-user-tar {
576 define dumptype comp-user-tar-span {
581 define dumptype holding-disk {
583 comment "The master-host holding disk itself"
584 holdingdisk never # do not use the holding disk
588 define dumptype comp-user {
590 comment "Non-root partitions on reasonably fast machines"
595 define dumptype comp-user-span {
598 comment "Tape-spanning non-root partitions on reasonably fast machines"
603 define dumptype nocomp-user {
605 comment "Non-root partitions on slow machines"
609 define dumptype nocomp-user-span {
611 comment "Tape-spanning non-root partitions on slow machines"
615 define dumptype comp-root {
617 comment "Root partitions with compression"
622 define dumptype nocomp-root {
624 comment "Root partitions without compression"
628 define dumptype comp-high {
630 comment "very important partitions on fast machines"
635 define dumptype nocomp-high {
637 comment "very important partitions on slow machines"
641 define dumptype nocomp-test {
643 comment "test dump without compression, no /var/lib/dumpdates recording"
649 define dumptype comp-test {
651 comment "test dump with compression, no /var/lib/dumpdates recording"
655 define dumptype custom-compress {
658 comment "custom client compression dumped with tar"
659 compress client custom
660 client_custom_compress "/usr/bin/bzip2"
663 define dumptype server-encrypt-fast {
666 comment "fast client compression and server symmetric encryption"
669 server_encrypt "/usr/sbin/amcrypt"
670 server_decrypt_option "-d"
673 define dumptype client-encrypt-nocomp {
676 comment "no compression and client symmetric encryption"
679 client_encrypt "/usr/sbin/amcrypt"
680 client_decrypt_option "-d"
684 # To use gpg public-key encryption, gpg does compress with zlib by default.
685 # Thus, no need to specify compress
687 #define dumptype gpg-encrypt {
690 # comment "server public-key encryption, dumped with tar"
693 # server_encrypt "/usr/sbin/amgpgcrypt"
694 # server_decrypt_option "-d"
700 # These are referred to by the disklist file. They define the attributes
701 # of the network interface that the remote machine is accessed through.
702 # Notes: - netusage above defines the attributes that are used when the
703 # disklist entry doesn't specify otherwise.
704 # - the values below are only samples.
705 # - specifying an interface does not force the traffic to pass
706 # through that interface. Your OS routing tables do that. This
707 # is just a mechanism to stop Amanda trashing your network.
709 # use - bandwidth above which amanda won't start
710 # backups using this interface. Note that if
711 # a single backup will take more than that,
712 # amanda won't try to make it run slower!
714 define interface local {
715 comment "a local disk"
719 #define interface le0 {
720 # comment "10 Mbps ethernet"
724 #define application-tool and dumptype for the amgtar application
725 define application-tool app_amgtar {
728 #property "GNUTAR-PATH" "/path/to/gtar"
729 #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
730 #default from gnutar_list_dir setting in amanda-client.conf
733 define dumptype dt_amgtar {
734 program "APPLICATION"
735 application "app_amgtar"
738 #define application-tool and dumptype for the amstar application
739 define application-tool app_amstar {
742 #property "STAR-PATH" "/path/to/star"
743 #property "STAR-TARDUMP" "/path/to/tardumps" # default /etc/tardumps
744 #property "STAR-DLE-TARDUMP" "no"
745 # if 'yes' then create a different tardump file for each DLE,
746 # it is required if you do many dump in parallel (maxdump>1)
749 define dumptype dt_amstar {
750 program "APPLICATION"
751 application "app_amstar"
754 #define a script-tool to send an email
755 define script-tool sc-email {
756 comment "script-email"
757 plugin "script-email"
758 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
759 execute_where server # or client
760 property "mailto" "martinea"
762 #your dumptype must include: script "sc-email"
765 # You may include other amanda configuration files, so you can share
766 # dumptypes, tapetypes and interface definitions among several
769 #includefile "/etc/amanda/amanda.conf.main"