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 ## autolabel "@DEFAULT_CONFIG@-%%%" empty
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_changer "changer" # amrecover will use the changer if you restore
144 # from this device. It could be a string like 'changer' and amrecover will use your
145 # changer if you set your tape to 'changer' with 'setdevice changer' or via
146 # 'tapedev "changer"' in amanda-client.conf
148 # Specify holding disks. These are used as a temporary staging area for
149 # dumps before they are written to tape and are recommended for most sites.
150 # The advantages include: tape drive is more likely to operate in streaming
151 # mode (which reduces tape and drive wear, reduces total dump time); multiple
152 # dumps can be done in parallel (which can dramatically reduce total dump time.
153 # The main disadvantage is that dumps on the holding disk need to be flushed
154 # (with amflush) to tape after an operating system crash or a tape failure.
155 # If no holding disks are specified then all dumps will be written directly
156 # to tape. If a dump is too big to fit on the holding disk than it will be
157 # written directly to tape. If more than one holding disk is specified then
158 # they will all be used based on activity and available space.
161 comment "main holding disk"
162 directory "/dumps/amanda" # where the holding disk is
163 use -100 Mb # how much space can we use on it
164 # a non-positive value means:
165 # use all space but that value
166 chunksize 1Gb # size of chunk if you want big dump to be
167 # dumped on multiple files on holding disks
168 # N Kb/Mb/Gb split images in chunks of size N
169 # The maximum value should be
170 # (MAX_FILE_SIZE - 1Mb)
171 # 0 same as INT_MAX bytes
174 # directory "/dumps2/amanda"
178 # directory "/mnt/disk4"
183 # If amanda cannot find a tape on which to store backups, it will run
184 # as many backups as it can to the holding disks. In order to save
185 # space for unattended backups, by default, amanda will only perform
186 # incremental backups in this case, i.e., it will reserve 100% of the
187 # holding disk space for the so-called degraded mode backups.
188 # However, if you specify a different value for the `reserve'
189 # parameter, amanda will not degrade backups if they will fit in the
190 # non-reserved portion of the holding disk.
192 # reserve 30 # percent
193 # This means save at least 30% of the holding disk space for degraded
196 # The format for a ColumnSpec is a ',' seperated list of triples.
197 # Each triple consists of
198 # + the name of the column (as in ColumnNameStrings)
199 # + prefix before the column
200 # + the width of the column, if set to -1 it will be recalculated
201 # to the maximum length of a line to print.
203 # "Disk=1:17,HostName=1:10,OutKB=1:7"
205 # "Disk=1:-1,HostName=1:10,OutKB=1:7"
207 # You need only specify those colums that should be changed from
208 # the default. If nothing is specified in the configfile, the
209 # above compiled in values will be in effect, resulting in an
210 # output as it was all the time.
211 # The names of the colums are:
212 # HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime, DumpRate,
213 # TapeTime and TapeRate.
215 # columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
218 # Amanda needs a few Mb of diskspace for the log and debug files,
219 # as well as a database. This stuff can grow large, so the conf directory
220 # isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm.
221 # Create an amanda directory under there. You need a separate infofile and
222 # logdir for each configuration, so create subdirectories for each conf and
223 # put the files there. Specify the locations below.
225 # Note that, although the keyword below is infofile, it is only so for
226 # historic reasons, since now it is supposed to be a directory (unless
227 # you have selected some database format other than the `text' default)
228 infofile "@CONFIG_DIR@/@DEFAULT_CONFIG@/curinfo" # database DIRECTORY
229 logdir "@CONFIG_DIR@/@DEFAULT_CONFIG@" # log directory
230 indexdir "@CONFIG_DIR@/@DEFAULT_CONFIG@/index" # index directory
231 #tapelist "@CONFIG_DIR@/@DEFAULT_CONFIG@/tapelist" # list of used tapes
232 # tapelist is stored, by default, in the directory that contains amanda.conf
236 # Define the type of tape you use here, and use it in "tapetype"
237 # above. Some typical types of tapes are included here. The tapetype
238 # tells amanda how many MB will fit on the tape, how big the filemarks
239 # are, and how fast the tape device is.
241 # A filemark is the amount of wasted space every time a tape section
244 # For completeness Amanda should calculate the inter-record gaps too,
245 # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using
246 # 9 tracks for amanda and need IRG calculations? Drop me a note if
249 # If you want amanda to print postscript paper tape labels
250 # add a line after the comment in the tapetype of the form
251 # lbl-templ "/path/to/postscript/template/label.ps"
253 # if you want the label to go to a printer other than the default
254 # for your system, you can also add a line above for a different
255 # printer. (i usually add that line after the dumpuser specification)
257 # dumpuser "operator" # the user to run dumps under
258 # printer "mypostscript" # printer to print paper label on
260 # here is an example of my definition for an EXB-8500
262 # define tapetype EXB-8500 {
264 # lbl-templ "@CONFIG_DIR@/config/lbl.exabyte.ps"
267 define tapetype global {
272 define tapetype QIC-60 {
274 comment "Archive Viper"
276 filemark 100 kbytes # don't know a better value
277 speed 100 kbytes # dito
280 define tapetype DEC-DLT2000 {
282 comment "DEC Differential Digital Linear Tape 2000"
288 # goluboff@butch.Colorado.EDU
289 # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
290 define tapetype DLT {
292 comment "DLT tape drives"
293 length 20000 mbytes # 20 Gig tapes
294 filemark 2000 kbytes # I don't know what this means
295 speed 1536 kbytes # 1.5 Mb/s
298 define tapetype SURESTORE-1200E {
300 comment "HP AutoLoader"
306 define tapetype EXB-8500 {
308 comment "Exabyte EXB-8500 drive on decent machine"
314 define tapetype EXB-8200 {
316 comment "Exabyte EXB-8200 drive on decent machine"
322 define tapetype HP-DAT {
324 comment "DAT tape drives"
325 # data provided by Rob Browning <rlb@cs.utexas.edu>
331 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 {
341 comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
344 speed 170 kbytes # limited by the Emulex bus interface, ugh
347 define tapetype SEAGATE-ULTRIUM-LTO {
349 comment "SEAGATE ULTRIUM 06242 LTO, compression off"
357 # These are referred to by the disklist file. The dumptype specifies
358 # certain parameters for dumping including:
359 # auth - authentication scheme to use between server and client.
360 # Valid values are "bsd", "bsdudp", "bsdtcp", "krb5", "local",
362 # Default: [auth "bsd"]
363 # comment - just a comment string
364 # comprate - set default compression rate. Should be followed by one or
365 # two numbers, optionally separated by a comma. The 1st is
366 # the full compression rate; the 2nd is the incremental rate.
367 # If the second is omitted, it is assumed equal to the first.
368 # The numbers represent the amount of the original file the
369 # compressed file is expected to take up.
370 # Default: [comprate 0.50, 0.50]
371 # compress - specify compression of the backed up data. Valid values are:
372 # "none" - don't compress the dump output.
373 # "client best" - compress on the client using the best (and
374 # probably slowest) algorithm.
375 # "client fast" - compress on the client using fast algorithm.
376 # "client custom" - compress using your custom client compression program.
377 # use client_custom_compress "PROG" to specify
378 # the custom compression program.
379 # PROG must not contain white space.
380 # "server best" - compress on the tape host using the best (and
381 # probably slowest) algorithm.
382 # "server fast" - compress on the tape host using a fast
383 # algorithm. This may be useful when a fast
384 # tape host is backing up slow clients.
385 # "server custom" - compress using your server custom compression program.
386 # use server_custom_compress "PROG" to specify
387 # the custom compression program.
388 # PROG must not contain white space.
389 # Default: [compress client fast]
390 # dumpcycle - set the number of days in the dump cycle, ie, set how often a
391 # full dump should be performed. Default: from DUMPCYCLE above
392 # estimate Determine the way AMANDA does it's estimate.
393 # "client" - Use the same program as the dumping program,
394 # this is the most accurate way to do estimates,
395 # but it can take a long time.
396 # "calcsize" - Use a faster program to do estimates, but the
397 # result is less accurate.
398 # "server" - Use only statistics from the previous run to
400 # it takes only a few seconds but the result is not
401 # accurate if your disk usage changes from day to day.
403 # encrypt - specify encryption of the backed up data. Valid values are:
404 # "none" - don't encrypt the dump output.
405 # "client" - encrypt on the client using the program specified by
406 # client_encrypt "PROG".
407 # Use client_decrypt_option to specify the decrypt-
408 # parameter, default is "-d".
409 # PROG and decrypt-parameter must not contain white space.
410 # "server" - encrypt on the server using the program specified by
411 # server_encrypt "PROG".
412 # Use server_decrypt_option to specify the decrypt-
413 # parameter, default is "-d".
414 # PROG and decrypt-parameter must not contain white space.
416 # exclude - specify files and directories to be excluded from the dump.
417 # Useful with gnutar only; silently ignored by dump and samba.
419 # "pattern" - a shell glob pattern defining which files
421 # gnutar gets --exclude="pattern"
422 # list "filename" - a file (on the client!) containing patterns
423 # re's (1 per line) defining which files to
425 # gnutar gets --exclude-from="filename"
426 # Note that the `full pathname' of a file within its
427 # filesystem starts with `./', because of the way amanda runs
428 # gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
429 # the final dot!) Thus, if you're backing up `/usr' with a
430 # diskfile entry like ``host /usr gnutar-root', but you don't
431 # want to backup /usr/tmp, your exclude list should contain
432 # the pattern `./tmp', as this is relative to the `/usr' above.
433 # Please refer to the man-page of gnutar for more information.
434 # If a relative pathname is specified as the exclude list,
435 # it is searched from within the directory that is
436 # going to be backed up.
437 # Default: include all files
438 # holdingdisk - should the holding disk be used for this dump. Useful for
439 # dumping the holding disk itself. Default: [holdingdisk auto]
440 # "never" - Never use the holding disk.
441 # "auto" - Use the holding disk if possible.
442 # "required" - Always use the holding disk.
443 # ignore - do not back this filesystem up. Useful for sharing a single
444 # disklist in several configurations.
445 # index - keep an index of the files backed up. Default: [index no]
446 # kencrypt - encrypt the data stream between the client and server.
447 # Default: [kencrypt no]
448 # maxdumps - max number of concurrent dumps to run on the client.
449 # Default: [maxdumps 1]
450 # maxpromoteday - max number of day for a promotion, set it 0 if you don't
451 # want promotion, set it to 1 or 2 if your disk get
454 # priority - priority level of the dump. Valid levels are "low", "medium"
455 # or "high". These are really only used when Amanda has no
456 # tape to write to because of some error. In that "degraded
457 # mode", as many incrementals as will fit on the holding disk
458 # are done, higher priority first, to insure the important
459 # disks are at least dumped. Default: [priority medium]
460 # program - specify the dump system to use. Valid values are "DUMP",
461 # or "GNUTAR". Default: [program "DUMP"].
462 # record - record the backup in the time-stamp-database of the backup
463 # program (e.g. /var/lib/dumpdates for DUMP or
464 # @GNUTAR_LISTED_INCREMENTAL_DIRX@ for GNUTAR.).
465 # Default: [record yes]
466 # skip-full - skip the disk when a level 0 is due, to allow full backups
467 # outside Amanda, eg when the machine is in single-user mode.
468 # skip-incr - skip the disk when the level 0 is NOT due. This is used in
469 # archive configurations, where only full dumps are done and
471 # starttime - delay the start of the dump? Default: no delay
472 # strategy - set the dump strategy. Valid strategies are currently:
473 # "standard" - the standard one.
474 # "nofull" - do level 1 dumps every time. This can be used,
475 # for example, for small root filesystems that
476 # only change slightly relative to a site-wide
477 # prototype. Amanda then backs up just the
479 # "noinc" - do level 0 dumps every time.
480 # "skip" - skip all dumps. Useful for sharing a single
481 # disklist in several configurations.
482 # "incronly" - do only incremental dumps. This is similar
483 # to strategy 'nofull', but will increase
484 # the dump level as usual. Full dumps will
485 # only be performed when an 'amadmin force'
487 # Default: [strategy standard]
489 # Note that you may specify previously defined dumptypes as a shorthand way of
490 # defining parameters.
492 define dumptype global {
493 comment "Global definitions"
494 # This is quite useful for setting global parameters, so you don't have
495 # to type them everywhere. All dumptype definitions in this sample file
496 # do include these definitions, either directly or indirectly.
497 # There's nothing special about the name `global'; if you create any
498 # dumptype that does not contain the word `global' or the name of any
499 # other dumptype that contains it, these definitions won't apply.
500 # Note that these definitions may be overridden in other
501 # dumptypes, if the redefinitions appear *after* the `global'
503 # You may want to use this for globally enabling or disabling
504 # indexing, recording, etc. Some examples:
507 # split_diskbuffer "/raid/amanda"
508 # fallback_splitsize 64m
511 define dumptype always-full {
513 comment "Full dump of this filesystem always"
519 # Dumptypes for gnutar
520 define dumptype root-tar {
523 comment "root partitions dumped with tar"
526 # exclude list "@CONFIG_DIR@/exclude.gtar"
530 define dumptype user-tar {
532 comment "user partitions dumped with tar"
536 define dumptype user-tar-span {
538 comment "tape-spanning user partitions dumped with tar"
542 define dumptype high-tar {
544 comment "partitions dumped with tar"
548 define dumptype comp-root-tar {
550 comment "Root partitions with compression"
554 define dumptype comp-user-tar {
559 define dumptype comp-user-tar-span {
564 define dumptype holding-disk {
566 comment "The master-host holding disk itself"
567 holdingdisk never # do not use the holding disk
571 define dumptype comp-user {
573 comment "Non-root partitions on reasonably fast machines"
578 define dumptype comp-user-span {
580 comment "Tape-spanning non-root partitions on reasonably fast machines"
585 define dumptype nocomp-user {
587 comment "Non-root partitions on slow machines"
591 define dumptype nocomp-user-span {
593 comment "Tape-spanning non-root partitions on slow machines"
597 define dumptype comp-root {
599 comment "Root partitions with compression"
604 define dumptype nocomp-root {
606 comment "Root partitions without compression"
610 define dumptype comp-high {
612 comment "very important partitions on fast machines"
617 define dumptype nocomp-high {
619 comment "very important partitions on slow machines"
623 define dumptype nocomp-test {
625 comment "test dump without compression, no /var/lib/dumpdates recording"
631 define dumptype comp-test {
633 comment "test dump with compression, no /var/lib/dumpdates recording"
637 define dumptype custom-compress {
640 comment "custom client compression dumped with tar"
641 compress client custom
642 client_custom_compress "/usr/bin/bzip2"
645 define dumptype server-encrypt-fast {
648 comment "fast client compression and server symmetric encryption"
651 server_encrypt "/usr/sbin/amcrypt"
652 server_decrypt_option "-d"
655 define dumptype client-encrypt-nocomp {
658 comment "no compression and client symmetric encryption"
661 client_encrypt "/usr/sbin/amcrypt"
662 client_decrypt_option "-d"
666 # To use gpg public-key encryption, gpg does compress with zlib by default.
667 # Thus, no need to specify compress
669 #define dumptype gpg-encrypt {
672 # comment "server public-key encryption, dumped with tar"
675 # server_encrypt "/usr/sbin/amgpgcrypt"
676 # server_decrypt_option "-d"
682 # These are referred to by the disklist file. They define the attributes
683 # of the network interface that the remote machine is accessed through.
684 # Notes: - netusage above defines the attributes that are used when the
685 # disklist entry doesn't specify otherwise.
686 # - the values below are only samples.
687 # - specifying an interface does not force the traffic to pass
688 # through that interface. Your OS routing tables do that. This
689 # is just a mechanism to stop Amanda trashing your network.
691 # use - bandwidth above which amanda won't start
692 # backups using this interface. Note that if
693 # a single backup will take more than that,
694 # amanda won't try to make it run slower!
696 define interface local {
697 comment "a local disk"
701 #define interface le0 {
702 # comment "10 Mbps ethernet"
706 #define application-tool and dumptype for the amgtar application
707 define application-tool app_amgtar {
710 #property "GNUTAR-PATH" "/path/to/gtar"
711 #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
712 #default from gnutar_list_dir setting in amanda-client.conf
715 define dumptype dt_amgtar {
716 program "APPLICATION"
717 application "app_amgtar"
720 #define application-tool and dumptype for the amstar application
721 define application-tool app_amstar {
724 #property "STAR-PATH" "/path/to/star"
725 #property "STAR-TARDUMP" "/path/to/tardumps" # default /etc/tardumps
726 #property "STAR-DLE-TARDUMP" "no"
727 # if 'yes' then create a different tardump file for each DLE,
728 # it is required if you do many dump in parallel (maxdump>1)
731 define dumptype dt_amstar {
732 program "APPLICATION"
733 application "app_amstar"
736 #define a script-tool to send an email
737 define script-tool sc-email {
738 comment "script-email"
739 plugin "script-email"
740 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
741 execute_where server # or client
742 property "mailto" "martinea"
744 #your dumptype must include: script "sc-email"
747 # You may include other amanda configuration files, so you can share
748 # dumptypes, tapetypes and interface definitions among several
751 #includefile "@CONFIG_DIR@/amanda.conf.main"