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 or tape changer.
116 runtapes 1 # number of tapes to be used in a single run of amdump
117 tapedev "@EXAMPLE_TAPEDEV@" # tape changer or device to use
119 # To use vtapes, create some slotN directories (slot0, slot1, etc.) under
120 # /var/amanda/vtapes and use this tapedev:
121 ## tapedev "chg-disk:/var/amanda/vtapes"
123 # To use a tape library, uncomment this definition. See amanda-changers(7)
124 # for more configuration options.
126 # define changer myrobot {
127 # tpchanger "chg-robot:/dev/sg0" # your changer device file
128 # tapedev "tape:@EXAMPLE_TAPEDEV@" # your tape drive device file
132 # If you want Amanda to automatically label any non-Amanda tapes it
133 # encounters, uncomment the line below. Note that this will ERASE any
134 # non-Amanda tapes you may have, and may also ERASE any near-failing tapes.
136 ## label_new_tapes "@DEFAULT_CONFIG@-%%%"
138 maxdumpsize -1 # Maximum number of bytes the planner will schedule
139 # for a run (default: runtapes * tape_length).
140 tapetype HP-DAT # what kind of tape it is (see tapetypes below)
141 labelstr "^@DEFAULT_CONFIG@-[0-9][0-9]*$" # label constraint regex: all tapes must match
143 amrecover_do_fsf yes # amrecover will call amrestore with the
144 # -f flag for faster positioning of the tape.
145 amrecover_check_label yes # amrecover will call amrestore with the
146 # -l flag to check the label.
147 amrecover_changer "changer" # amrecover will use the changer if you restore
148 # from this device. It could be a string like 'changer' and amrecover will use your
149 # changer if you set your tape to 'changer' with 'setdevice changer' or via
150 # 'tapedev "changer"' in amanda-client.conf
152 # Specify holding disks. These are used as a temporary staging area for
153 # dumps before they are written to tape and are recommended for most sites.
154 # The advantages include: tape drive is more likely to operate in streaming
155 # mode (which reduces tape and drive wear, reduces total dump time); multiple
156 # dumps can be done in parallel (which can dramatically reduce total dump time.
157 # The main disadvantage is that dumps on the holding disk need to be flushed
158 # (with amflush) to tape after an operating system crash or a tape failure.
159 # If no holding disks are specified then all dumps will be written directly
160 # to tape. If a dump is too big to fit on the holding disk than it will be
161 # written directly to tape. If more than one holding disk is specified then
162 # they will all be used based on activity and available space.
165 comment "main holding disk"
166 directory "/dumps/amanda" # where the holding disk is
167 use -100 Mb # how much space can we use on it
168 # a non-positive value means:
169 # use all space but that value
170 chunksize 1Gb # size of chunk if you want big dump to be
171 # dumped on multiple files on holding disks
172 # N Kb/Mb/Gb split images in chunks of size N
173 # The maximum value should be
174 # (MAX_FILE_SIZE - 1Mb)
175 # 0 same as INT_MAX bytes
178 # directory "/dumps2/amanda"
182 # directory "/mnt/disk4"
187 # If amanda cannot find a tape on which to store backups, it will run
188 # as many backups as it can to the holding disks. In order to save
189 # space for unattended backups, by default, amanda will only perform
190 # incremental backups in this case, i.e., it will reserve 100% of the
191 # holding disk space for the so-called degraded mode backups.
192 # However, if you specify a different value for the `reserve'
193 # parameter, amanda will not degrade backups if they will fit in the
194 # non-reserved portion of the holding disk.
196 # reserve 30 # percent
197 # This means save at least 30% of the holding disk space for degraded
200 # The format for a ColumnSpec is a ',' seperated list of triples.
201 # Each triple consists of
202 # + the name of the column (as in ColumnNameStrings)
203 # + prefix before the column
204 # + the width of the column, if set to -1 it will be recalculated
205 # to the maximum length of a line to print.
207 # "Disk=1:17,HostName=1:10,OutKB=1:7"
209 # "Disk=1:-1,HostName=1:10,OutKB=1:7"
211 # You need only specify those colums that should be changed from
212 # the default. If nothing is specified in the configfile, the
213 # above compiled in values will be in effect, resulting in an
214 # output as it was all the time.
215 # The names of the colums are:
216 # HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime, DumpRate,
217 # TapeTime and TapeRate.
219 # columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
222 # Amanda needs a few Mb of diskspace for the log and debug files,
223 # as well as a database. This stuff can grow large, so the conf directory
224 # isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm.
225 # Create an amanda directory under there. You need a separate infofile and
226 # logdir for each configuration, so create subdirectories for each conf and
227 # put the files there. Specify the locations below.
229 # Note that, although the keyword below is infofile, it is only so for
230 # historic reasons, since now it is supposed to be a directory (unless
231 # you have selected some database format other than the `text' default)
232 infofile "@CONFIG_DIR@/@DEFAULT_CONFIG@/curinfo" # database DIRECTORY
233 logdir "@CONFIG_DIR@/@DEFAULT_CONFIG@" # log directory
234 indexdir "@CONFIG_DIR@/@DEFAULT_CONFIG@/index" # index directory
235 #tapelist "@CONFIG_DIR@/@DEFAULT_CONFIG@/tapelist" # list of used tapes
236 # tapelist is stored, by default, in the directory that contains amanda.conf
240 # Define the type of tape you use here, and use it in "tapetype"
241 # above. Some typical types of tapes are included here. The tapetype
242 # tells amanda how many MB will fit on the tape, how big the filemarks
243 # are, and how fast the tape device is.
245 # A filemark is the amount of wasted space every time a tape section
248 # For completeness Amanda should calculate the inter-record gaps too,
249 # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using
250 # 9 tracks for amanda and need IRG calculations? Drop me a note if
253 # If you want amanda to print postscript paper tape labels
254 # add a line after the comment in the tapetype of the form
255 # lbl-templ "/path/to/postscript/template/label.ps"
257 # if you want the label to go to a printer other than the default
258 # for your system, you can also add a line above for a different
259 # printer. (i usually add that line after the dumpuser specification)
261 # dumpuser "operator" # the user to run dumps under
262 # printer "mypostscript" # printer to print paper label on
264 # here is an example of my definition for an EXB-8500
266 # define tapetype EXB-8500 {
268 # lbl-templ "@CONFIG_DIR@/config/lbl.exabyte.ps"
272 define tapetype QIC-60 {
273 comment "Archive Viper"
275 filemark 100 kbytes # don't know a better value
276 speed 100 kbytes # dito
279 define tapetype DEC-DLT2000 {
280 comment "DEC Differential Digital Linear Tape 2000"
286 # goluboff@butch.Colorado.EDU
287 # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
288 define tapetype DLT {
289 comment "DLT tape drives"
290 length 20000 mbytes # 20 Gig tapes
291 filemark 2000 kbytes # I don't know what this means
292 speed 1536 kbytes # 1.5 Mb/s
295 define tapetype SURESTORE-1200E {
296 comment "HP AutoLoader"
302 define tapetype EXB-8500 {
303 comment "Exabyte EXB-8500 drive on decent machine"
309 define tapetype EXB-8200 {
310 comment "Exabyte EXB-8200 drive on decent machine"
316 define tapetype HP-DAT {
317 comment "DAT tape drives"
318 # data provided by Rob Browning <rlb@cs.utexas.edu>
324 define tapetype DAT {
325 comment "DAT tape drives"
326 length 1000 mbytes # these numbers are not accurate
327 filemark 100 kbytes # but you get the idea
331 define tapetype MIMSY-MEGATAPE {
332 comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
335 speed 170 kbytes # limited by the Emulex bus interface, ugh
338 define tapetype SEAGATE-ULTRIUM-LTO {
339 comment "SEAGATE ULTRIUM 06242 LTO, compression off"
347 # These are referred to by the disklist file. The dumptype specifies
348 # certain parameters for dumping including:
349 # auth - authentication scheme to use between server and client.
350 # Valid values are "bsd", "bsdudp", "bsdtcp", "krb5", "local",
352 # Default: [auth "bsd"]
353 # comment - just a comment string
354 # comprate - set default compression rate. Should be followed by one or
355 # two numbers, optionally separated by a comma. The 1st is
356 # the full compression rate; the 2nd is the incremental rate.
357 # If the second is omitted, it is assumed equal to the first.
358 # The numbers represent the amount of the original file the
359 # compressed file is expected to take up.
360 # Default: [comprate 0.50, 0.50]
361 # compress - specify compression of the backed up data. Valid values are:
362 # "none" - don't compress the dump output.
363 # "client best" - compress on the client using the best (and
364 # probably slowest) algorithm.
365 # "client fast" - compress on the client using fast algorithm.
366 # "client custom" - compress using your custom client compression program.
367 # use client_custom_compress "PROG" to specify
368 # the custom compression program.
369 # PROG must not contain white space.
370 # "server best" - compress on the tape host using the best (and
371 # probably slowest) algorithm.
372 # "server fast" - compress on the tape host using a fast
373 # algorithm. This may be useful when a fast
374 # tape host is backing up slow clients.
375 # "server custom" - compress using your server custom compression program.
376 # use server_custom_compress "PROG" to specify
377 # the custom compression program.
378 # PROG must not contain white space.
379 # Default: [compress client fast]
380 # dumpcycle - set the number of days in the dump cycle, ie, set how often a
381 # full dump should be performed. Default: from DUMPCYCLE above
382 # estimate Determine the way AMANDA does it's estimate.
383 # "client" - Use the same program as the dumping program,
384 # this is the most accurate way to do estimates,
385 # but it can take a long time.
386 # "calcsize" - Use a faster program to do estimates, but the
387 # result is less accurate.
388 # "server" - Use only statistics from the previous run to
390 # it takes only a few seconds but the result is not
391 # accurate if your disk usage changes from day to day.
393 # encrypt - specify encryption of the backed up data. Valid values are:
394 # "none" - don't encrypt the dump output.
395 # "client" - encrypt on the client using the program specified by
396 # client_encrypt "PROG".
397 # Use client_decrypt_option to specify the decrypt-
398 # parameter, default is "-d".
399 # PROG and decrypt-parameter must not contain white space.
400 # "server" - encrypt on the server using the program specified by
401 # server_encrypt "PROG".
402 # Use server_decrypt_option to specify the decrypt-
403 # parameter, default is "-d".
404 # PROG and decrypt-parameter must not contain white space.
406 # exclude - specify files and directories to be excluded from the dump.
407 # Useful with gnutar only; silently ignored by dump and samba.
409 # "pattern" - a shell glob pattern defining which files
411 # gnutar gets --exclude="pattern"
412 # list "filename" - a file (on the client!) containing patterns
413 # re's (1 per line) defining which files to
415 # gnutar gets --exclude-from="filename"
416 # Note that the `full pathname' of a file within its
417 # filesystem starts with `./', because of the way amanda runs
418 # gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
419 # the final dot!) Thus, if you're backing up `/usr' with a
420 # diskfile entry like ``host /usr gnutar-root', but you don't
421 # want to backup /usr/tmp, your exclude list should contain
422 # the pattern `./tmp', as this is relative to the `/usr' above.
423 # Please refer to the man-page of gnutar for more information.
424 # If a relative pathname is specified as the exclude list,
425 # it is searched from within the directory that is
426 # going to be backed up.
427 # Default: include all files
428 # holdingdisk - should the holding disk be used for this dump. Useful for
429 # dumping the holding disk itself. Default: [holdingdisk auto]
430 # "never" - Never use the holding disk.
431 # "auto" - Use the holding disk if possible.
432 # "required" - Always use the holding disk.
433 # ignore - do not back this filesystem up. Useful for sharing a single
434 # disklist in several configurations.
435 # index - keep an index of the files backed up. Default: [index no]
436 # kencrypt - encrypt the data stream between the client and server.
437 # Default: [kencrypt no]
438 # maxdumps - max number of concurrent dumps to run on the client.
439 # Default: [maxdumps 1]
440 # maxpromoteday - max number of day for a promotion, set it 0 if you don't
441 # want promotion, set it to 1 or 2 if your disk get
444 # priority - priority level of the dump. Valid levels are "low", "medium"
445 # or "high". These are really only used when Amanda has no
446 # tape to write to because of some error. In that "degraded
447 # mode", as many incrementals as will fit on the holding disk
448 # are done, higher priority first, to insure the important
449 # disks are at least dumped. Default: [priority medium]
450 # program - specify the dump system to use. Valid values are "DUMP",
451 # or "GNUTAR". Default: [program "DUMP"].
452 # record - record the backup in the time-stamp-database of the backup
453 # program (e.g. /etc/dumpdates for DUMP or
454 # @GNUTAR_LISTED_INCREMENTAL_DIRX@ for GNUTAR.).
455 # Default: [record yes]
456 # skip-full - skip the disk when a level 0 is due, to allow full backups
457 # outside Amanda, eg when the machine is in single-user mode.
458 # skip-incr - skip the disk when the level 0 is NOT due. This is used in
459 # archive configurations, where only full dumps are done and
461 # starttime - delay the start of the dump? Default: no delay
462 # strategy - set the dump strategy. Valid strategies are currently:
463 # "standard" - the standard one.
464 # "nofull" - do level 1 dumps every time. This can be used,
465 # for example, for small root filesystems that
466 # only change slightly relative to a site-wide
467 # prototype. Amanda then backs up just the
469 # "noinc" - do level 0 dumps every time.
470 # "skip" - skip all dumps. Useful for sharing a single
471 # disklist in several configurations.
472 # "incronly" - do only incremental dumps. This is similar
473 # to strategy 'nofull', but will increase
474 # the dump level as usual. Full dumps will
475 # only be performed when an 'amadmin force'
477 # Default: [strategy standard]
478 # tape_splitsize - (optional) split dump file into pieces of a specified size.
479 # This allows dumps to be spread across multiple tapes, and can
480 # potentially make more efficient use of tape space. Note that
481 # if this value is too large (more than half the size of the
482 # average dump being split), substantial tape space can be
483 # wasted. If too small, large dumps will be split into
484 # innumerable tiny dumpfiles, adding to restoration complexity.
485 # A good rule of thumb, usually, is 1/10 of the size of your
486 # tape. Default: [disabled]
487 # split_diskbuffer - (optional) When dumping a split dump in PORT-WRITE
488 # mode (usually meaning "no holding disk"), buffer the split
489 # chunks to a file in the directory specified by this option.
491 # fallback_splitsize - (optional) When dumping a split dump in PORT-WRITE
492 # mode, if no split_diskbuffer is specified (or if we somehow
493 # fail to use our split_diskbuffer), we must buffer split
494 # chunks in memory. This specifies the maximum size split
495 # chunks can be in this scenario, and thus the maximum amount
496 # of memory consumed for in-memory splitting. Default: [10m]
498 # Note that you may specify previously defined dumptypes as a shorthand way of
499 # defining parameters.
501 define dumptype global {
502 comment "Global definitions"
503 # This is quite useful for setting global parameters, so you don't have
504 # to type them everywhere. All dumptype definitions in this sample file
505 # do include these definitions, either directly or indirectly.
506 # There's nothing special about the name `global'; if you create any
507 # dumptype that does not contain the word `global' or the name of any
508 # other dumptype that contains it, these definitions won't apply.
509 # Note that these definitions may be overridden in other
510 # dumptypes, if the redefinitions appear *after* the `global'
512 # You may want to use this for globally enabling or disabling
513 # indexing, recording, etc. Some examples:
516 # split_diskbuffer "/raid/amanda"
517 # fallback_splitsize 64m
520 define dumptype always-full {
522 comment "Full dump of this filesystem always"
528 # Dumptypes for gnutar
529 define dumptype root-tar {
532 comment "root partitions dumped with tar"
535 # exclude list "@CONFIG_DIR@/exclude.gtar"
539 define dumptype user-tar {
541 comment "user partitions dumped with tar"
545 define dumptype user-tar-span {
548 comment "tape-spanning user partitions dumped with tar"
552 define dumptype high-tar {
554 comment "partitions dumped with tar"
558 define dumptype comp-root-tar {
560 comment "Root partitions with compression"
564 define dumptype comp-user-tar {
569 define dumptype comp-user-tar-span {
574 define dumptype holding-disk {
576 comment "The master-host holding disk itself"
577 holdingdisk never # do not use the holding disk
581 define dumptype comp-user {
583 comment "Non-root partitions on reasonably fast machines"
588 define dumptype comp-user-span {
591 comment "Tape-spanning non-root partitions on reasonably fast machines"
596 define dumptype nocomp-user {
598 comment "Non-root partitions on slow machines"
602 define dumptype nocomp-user-span {
604 comment "Tape-spanning non-root partitions on slow machines"
608 define dumptype comp-root {
610 comment "Root partitions with compression"
615 define dumptype nocomp-root {
617 comment "Root partitions without compression"
621 define dumptype comp-high {
623 comment "very important partitions on fast machines"
628 define dumptype nocomp-high {
630 comment "very important partitions on slow machines"
634 define dumptype nocomp-test {
636 comment "test dump without compression, no /etc/dumpdates recording"
642 define dumptype comp-test {
644 comment "test dump with compression, no /etc/dumpdates recording"
648 define dumptype custom-compress {
651 comment "custom client compression dumped with tar"
652 compress client custom
653 client_custom_compress "/usr/bin/bzip2"
656 define dumptype server-encrypt-fast {
659 comment "fast client compression and server symmetric encryption"
662 server_encrypt "/usr/sbin/amcrypt"
663 server_decrypt_option "-d"
666 define dumptype client-encrypt-nocomp {
669 comment "no compression and client symmetric encryption"
672 client_encrypt "/usr/sbin/amcrypt"
673 client_decrypt_option "-d"
677 # To use gpg public-key encryption, gpg does compress with zlib by default.
678 # Thus, no need to specify compress
680 #define dumptype gpg-encrypt {
683 # comment "server public-key encryption, dumped with tar"
686 # server_encrypt "/usr/sbin/amgpgcrypt"
687 # server_decrypt_option "-d"
693 # These are referred to by the disklist file. They define the attributes
694 # of the network interface that the remote machine is accessed through.
695 # Notes: - netusage above defines the attributes that are used when the
696 # disklist entry doesn't specify otherwise.
697 # - the values below are only samples.
698 # - specifying an interface does not force the traffic to pass
699 # through that interface. Your OS routing tables do that. This
700 # is just a mechanism to stop Amanda trashing your network.
702 # use - bandwidth above which amanda won't start
703 # backups using this interface. Note that if
704 # a single backup will take more than that,
705 # amanda won't try to make it run slower!
707 define interface local {
708 comment "a local disk"
712 #define interface le0 {
713 # comment "10 Mbps ethernet"
717 #define application-tool and dumptype for the amgtar application
718 define application-tool app_amgtar {
721 #property "GNUTAR-PATH" "/path/to/gtar"
722 #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
723 #default from gnutar_list_dir setting in amanda-client.conf
726 define dumptype dt_amgtar {
727 program "APPLICATION"
728 application "app_amgtar"
731 #define application-tool and dumptype for the amstar application
732 define application-tool app_amstar {
735 #property "STAR-PATH" "/path/to/star"
736 #property "STAR-TARDUMP" "/path/to/tardumps" # default /etc/tardumps
737 #property "STAR-DLE-TARDUMP" "no"
738 # if 'yes' then create a different tardump file for each DLE,
739 # it is required if you do many dump in parallel (maxdump>1)
742 define dumptype dt_amstar {
743 program "APPLICATION"
744 application "app_amstar"
747 #define a script-tool to send an email
748 define script-tool sc-email {
749 comment "script-email"
750 plugin "script-email"
751 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
752 execute_where server # or client
753 property "mailto" "martinea"
755 #your dumptype must include: script "sc-email"
758 # You may include other amanda configuration files, so you can share
759 # dumptypes, tapetypes and interface definitions among several
762 #includefile "@CONFIG_DIR@/amanda.conf.main"