2 # amanda.conf - sample Amanda configuration file.
4 # If your configuration is called, say, "DailySet1", then this file
5 # normally goes in /etc/amanda/DailySet1/amanda.conf.
7 # You need to edit this file to suit your needs. See the documentation in
8 # this file, in the "man amanda" man page, in the /usr/share/docs/amanda*
9 # directories, and on the web at www.amanda.org for more information.
12 org "DailySet1" # your organization name for reports
13 mailto "root" # space separated list of operators at your site
14 dumpuser "backup" # the user to run dumps under
16 inparallel 4 # maximum dumpers that will run in parallel (max 63)
17 # this maximum can be increased at compile-time,
18 # modifying MAX_DUMPERS in server-src/driverio.h
19 dumporder "sssS" # specify the priority order of each dumper
24 # b -> smallest bandwitdh
25 # B -> biggest bandwitdh
26 # try "BTBTBTBTBTBT" if you are not holding
29 taperalgo first # The algorithm used to choose which dump image to send
33 # [first|firstfit|largest|largestfit|smallest|last]
36 # first First in - first out.
37 # firstfit The first dump image that will fit on
39 # largest The largest dump image.
40 # largestfit The largest dump image that will fit on
42 # smallest The smallest dump image.
43 # last Last in - first out.
45 displayunit "k" # Possible values: "k|m|g|t"
47 # The unit used to print many numbers.
48 # k=kilo, m=mega, g=giga, t=tera
50 netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec
52 dumpcycle 4 weeks # the number of days in the normal dump cycle
53 runspercycle 20 # the number of amdump runs in dumpcycle days
54 # (4 weeks * 5 amdump runs per week -- just weekdays)
55 tapecycle 25 tapes # the number of tapes in rotation
56 # 4 weeks (dumpcycle) times 5 tapes per week (just
57 # the weekdays) plus a few to handle errors that
58 # need amflush and so we do not overwrite the full
59 # backups performed at the beginning of the previous
62 bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
63 bumppercent 20 # minimum savings (threshold) to bump level 1 -> 2
64 bumpdays 1 # minimum days at each level
65 bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
67 etimeout 300 # number of seconds per filesystem for estimates.
68 #etimeout -600 # total number of seconds for estimates.
69 # a positive number will be multiplied by the number of filesystems on
70 # each host; a negative number will be taken as an absolute total time-out.
71 # The default is 5 minutes per filesystem.
73 dtimeout 1800 # number of idle seconds before a dump is aborted.
75 ctimeout 30 # maximum number of seconds that amcheck waits
76 # for each client host
79 # A positive integer telling taper how many 32k buffers to allocate.
80 # WARNING! If this is set too high, taper will not be able to allocate
81 # the memory and will die. The default is 20 (640k).
84 # Specify tape device and/or tape changer. If you don't have a tape
85 # changer, and you don't want to use more than one tape per run of
86 # amdump, just comment out the definition of tpchanger.
88 # Some tape changers require tapedev to be defined; others will use
89 # their own tape device selection mechanism. Some use a separate tape
90 # changer device (changerdev), others will simply ignore this
91 # parameter. Some rely on a configuration file (changerfile) to
92 # obtain more information about tape devices, number of slots, etc;
93 # others just need to store some data in files, whose names will start
94 # with changerfile. For more information about individual tape
95 # changers, read docs/TAPE.CHANGERS.
97 # At most one changerfile entry must be defined; select the most
98 # appropriate one for your configuration. If you select man-changer,
99 # keep the first one; if you decide not to use a tape changer, you may
100 # comment them all out.
102 runtapes 1 # number of tapes to be used in a single run of amdump
103 tpchanger "chg-manual" # the tape-changer glue script
104 tapedev "@DEFAULT_TAPE_DEVICE@" # the no-rewind tape device to be used
105 rawtapedev "@DEFAULT_RAW_TAPE_DEVICE@" # the raw device to be used (ftape only)
106 #changerfile "/etc/amanda/DailySet1/changer"
107 #changerfile "/etc/amanda/DailySet1/changer-status"
108 changerfile "/etc/amanda/DailySet1/changer.conf"
109 changerdev "@DEFAULT_CHANGER_DEVICE@"
111 # If you want Amanda to automatically label any non-Amanda tapes it
112 # encounters, uncomment the line below. Note that this will ERASE any
113 # non-Amanda tapes you may have, and may also ERASE any near-failing tapes.
115 ## label_new_tapes "DailySet1-%%%"
117 # maxdumpsize -1 # Maximum number of bytes the planner will schedule
118 # for a run (default: runtapes * tape_length).
119 tapetype HP-DAT # what kind of tape it is (see tapetypes below)
120 labelstr "^DailySet1-[0-9][0-9]*$" # label constraint regex: all tapes must match
122 amrecover_do_fsf yes # amrecover will call amrestore with the
123 # -f flag for faster positioning of the tape.
124 amrecover_check_label yes # amrecover will call amrestore with the
125 # -l flag to check the label.
126 amrecover_changer "@DEFAULT_TAPE_DEVICE@" # amrecover will use the changer if you restore
128 # It could be a string like 'changer' and
129 # amrecover will use your changer if you
130 # set your tape with 'settape changer'
132 # Specify holding disks. These are used as a temporary staging area for
133 # dumps before they are written to tape and are recommended for most sites.
134 # The advantages include: tape drive is more likely to operate in streaming
135 # mode (which reduces tape and drive wear, reduces total dump time); multiple
136 # dumps can be done in parallel (which can dramatically reduce total dump time.
137 # The main disadvantage is that dumps on the holding disk need to be flushed
138 # (with amflush) to tape after an operating system crash or a tape failure.
139 # If no holding disks are specified then all dumps will be written directly
140 # to tape. If a dump is too big to fit on the holding disk than it will be
141 # written directly to tape. If more than one holding disk is specified then
142 # they will all be used based on activity and available space.
145 comment "main holding disk"
146 directory "/dumps/amanda" # where the holding disk is
147 use -100 Mb # how much space can we use on it
148 # a non-positive value means:
149 # use all space but that value
150 chunksize 1Gb # size of chunk if you want big dump to be
151 # dumped on multiple files on holding disks
152 # N Kb/Mb/Gb split images in chunks of size N
153 # The maximum value should be
154 # (MAX_FILE_SIZE - 1Mb)
155 # 0 same as INT_MAX bytes
158 # directory "/dumps2/amanda"
162 # directory "/mnt/disk4"
167 # If amanda cannot find a tape on which to store backups, it will run
168 # as many backups as it can to the holding disks. In order to save
169 # space for unattended backups, by default, amanda will only perform
170 # incremental backups in this case, i.e., it will reserve 100% of the
171 # holding disk space for the so-called degraded mode backups.
172 # However, if you specify a different value for the `reserve'
173 # parameter, amanda will not degrade backups if they will fit in the
174 # non-reserved portion of the holding disk.
176 # reserve 30 # percent
177 # This means save at least 30% of the holding disk space for degraded
181 # if autoflush is set to yes, then amdump will schedule all dump on
182 # holding disks to be flush to tape during the run.
184 # The format for a ColumnSpec is a ',' seperated list of triples.
185 # Each triple consists of
186 # + the name of the column (as in ColumnNameStrings)
187 # + prefix before the column
188 # + the width of the column, if set to -1 it will be recalculated
189 # to the maximum length of a line to print.
191 # "Disk=1:17,HostName=1:10,OutKB=1:7"
193 # "Disk=1:-1,HostName=1:10,OutKB=1:7"
195 # You need only specify those colums that should be changed from
196 # the default. If nothing is specified in the configfile, the
197 # above compiled in values will be in effect, resulting in an
198 # output as it was all the time.
199 # The names of the colums are:
200 # HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime, DumpRate,
201 # TapeTime and TapeRate.
203 # columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
206 # Amanda needs a few Mb of diskspace for the log and debug files,
207 # as well as a database. This stuff can grow large, so the conf directory
208 # isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm.
209 # Create an amanda directory under there. You need a separate infofile and
210 # logdir for each configuration, so create subdirectories for each conf and
211 # put the files there. Specify the locations below.
213 # Note that, although the keyword below is infofile, it is only so for
214 # historic reasons, since now it is supposed to be a directory (unless
215 # you have selected some database format other than the `text' default)
216 infofile "/etc/amanda/DailySet1/curinfo" # database DIRECTORY
217 logdir "/etc/amanda/DailySet1" # log directory
218 indexdir "/etc/amanda/DailySet1/index" # index directory
219 #tapelist "@CONFIG_DIR/DailySet1/tapelist" # list of used tapes
220 # tapelist is stored, by default, in the directory that contains amanda.conf
224 # Define the type of tape you use here, and use it in "tapetype"
225 # above. Some typical types of tapes are included here. The tapetype
226 # tells amanda how many MB will fit on the tape, how big the filemarks
227 # are, and how fast the tape device is.
229 # A filemark is the amount of wasted space every time a tape section
230 # ends. If you run `make tapetype' in tape-src, you'll get a program
231 # that generates tapetype entries, but it is slow as hell, use it only
232 # if you really must and, if you do, make sure you post the data to
233 # the amanda mailing list, so that others can use what you found out
234 # by searching the archives.
236 # For completeness Amanda should calculate the inter-record gaps too,
237 # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using
238 # 9 tracks for amanda and need IRG calculations? Drop me a note if
241 # If you want amanda to print postscript paper tape labels
242 # add a line after the comment in the tapetype of the form
243 # lbl-templ "/path/to/postscript/template/label.ps"
245 # if you want the label to go to a printer other than the default
246 # for your system, you can also add a line above for a different
247 # printer. (i usually add that line after the dumpuser specification)
249 # dumpuser "operator" # the user to run dumps under
250 # printer "mypostscript" # printer to print paper label on
252 # here is an example of my definition for an EXB-8500
254 # define tapetype EXB-8500 {
256 # lbl-templ "/etc/amanda/config/lbl.exabyte.ps"
260 define tapetype QIC-60 {
261 comment "Archive Viper"
263 filemark 100 kbytes # don't know a better value
264 speed 100 kbytes # dito
267 define tapetype DEC-DLT2000 {
268 comment "DEC Differential Digital Linear Tape 2000"
274 # goluboff@butch.Colorado.EDU
275 # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
276 define tapetype DLT {
277 comment "DLT tape drives"
278 length 20000 mbytes # 20 Gig tapes
279 filemark 2000 kbytes # I don't know what this means
280 speed 1536 kbytes # 1.5 Mb/s
283 define tapetype SURESTORE-1200E {
284 comment "HP AutoLoader"
290 define tapetype EXB-8500 {
291 comment "Exabyte EXB-8500 drive on decent machine"
297 define tapetype EXB-8200 {
298 comment "Exabyte EXB-8200 drive on decent machine"
304 define tapetype HP-DAT {
305 comment "DAT tape drives"
306 # data provided by Rob Browning <rlb@cs.utexas.edu>
312 define tapetype DAT {
313 comment "DAT tape drives"
314 length 1000 mbytes # these numbers are not accurate
315 filemark 100 kbytes # but you get the idea
319 define tapetype MIMSY-MEGATAPE {
320 comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
323 speed 170 kbytes # limited by the Emulex bus interface, ugh
329 # These are referred to by the disklist file. The dumptype specifies
330 # certain parameters for dumping including:
331 # auth - authentication scheme to use between server and client.
332 # Valid values are "bsd", "krb4", "krb5" and "ssh".
333 # Default: [auth bsd]
334 # comment - just a comment string
335 # comprate - set default compression rate. Should be followed by one or
336 # two numbers, optionally separated by a comma. The 1st is
337 # the full compression rate; the 2nd is the incremental rate.
338 # If the second is omitted, it is assumed equal to the first.
339 # The numbers represent the amount of the original file the
340 # compressed file is expected to take up.
341 # Default: [comprate 0.50, 0.50]
342 # compress - specify compression of the backed up data. Valid values are:
343 # "none" - don't compress the dump output.
344 # "client best" - compress on the client using the best (and
345 # probably slowest) algorithm.
346 # "client fast" - compress on the client using fast algorithm.
347 # "client custom" - compress using your custom client compression program.
348 # use client_custom_compress "PROG" to specify
349 # the custom compression program.
350 # PROG must not contain white space.
351 # "server best" - compress on the tape host using the best (and
352 # probably slowest) algorithm.
353 # "server fast" - compress on the tape host using a fast
354 # algorithm. This may be useful when a fast
355 # tape host is backing up slow clients.
356 # "server custom" - compress using your server custom compression program.
357 # use server_custom_compress "PROG" to specify
358 # the custom compression program.
359 # PROG must not contain white space.
360 # Default: [compress client fast]
361 # dumpcycle - set the number of days in the dump cycle, ie, set how often a
362 # full dump should be performed. Default: from DUMPCYCLE above
363 # estimate Determine the way AMANDA does it's estimate.
364 # "client" - Use the same program as the dumping program,
365 # this is the most accurate way to do estimates,
366 # but it can take a long time.
367 # "calcsize" - Use a faster program to do estimates, but the
368 # result is less accurate.
369 # "server" - Use only statistics from the previous run to
371 # it takes only a few seconds but the result is not
372 # accurate if your disk usage changes from day to day.
374 # encrypt - specify encryption of the backed up data. Valid values are:
375 # "none" - don't encrypt the dump output.
376 # "client" - encrypt on the client using the program specified by
377 # client_encrypt "PROG".
378 # Use client_decrypt_option to specify the decrypt-
379 # parameter, default is "-d".
380 # PROG and decrypt-parameter must not contain white space.
381 # "server" - encrypt on the server using the program specified by
382 # server_encrypt "PROG".
383 # Use server_decrypt_option to specify the decrypt-
384 # parameter, default is "-d".
385 # PROG and decrypt-parameter must not contain white space.
387 # exclude - specify files and directories to be excluded from the dump.
388 # Useful with gnutar only; silently ignored by dump and samba.
390 # "pattern" - a shell glob pattern defining which files
392 # gnutar gets --exclude="pattern"
393 # list "filename" - a file (on the client!) containing patterns
394 # re's (1 per line) defining which files to
396 # gnutar gets --exclude-from="filename"
397 # Note that the `full pathname' of a file within its
398 # filesystem starts with `./', because of the way amanda runs
399 # gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
400 # the final dot!) Thus, if you're backing up `/usr' with a
401 # diskfile entry like ``host /usr gnutar-root', but you don't
402 # want to backup /usr/tmp, your exclude list should contain
403 # the pattern `./tmp', as this is relative to the `/usr' above.
404 # Please refer to the man-page of gnutar for more information.
405 # If a relative pathname is specified as the exclude list,
406 # it is searched from within the directory that is
407 # going to be backed up.
408 # Default: include all files
409 # holdingdisk - should the holding disk be used for this dump. Useful for
410 # dumping the holding disk itself. Default: [holdingdisk yes]
411 # ignore - do not back this filesystem up. Useful for sharing a single
412 # disklist in several configurations.
413 # index - keep an index of the files backed up. Default: [index no]
414 # kencrypt - encrypt the data stream between the client and server.
415 # Default: [kencrypt no]
416 # maxdumps - max number of concurrent dumps to run on the client.
417 # Default: [maxdumps 1]
418 # maxpromoteday - max number of day for a promotion, set it 0 if you don't
419 # want promotion, set it to 1 or 2 if your disk get
422 # priority - priority level of the dump. Valid levels are "low", "medium"
423 # or "high". These are really only used when Amanda has no
424 # tape to write to because of some error. In that "degraded
425 # mode", as many incrementals as will fit on the holding disk
426 # are done, higher priority first, to insure the important
427 # disks are at least dumped. Default: [priority medium]
428 # program - specify the dump system to use. Valid values are "DUMP" and
429 # "GNUTAR". Default: [program "DUMP"].
430 # record - record the backup in the time-stamp-database of the backup
431 # program (e.g. /etc/dumpdates for DUMP or
432 # @GNUTAR_LISTED_INCREMENTAL_DIRX@ for GNUTAR.).
433 # Default: [record yes]
434 # skip-full - skip the disk when a level 0 is due, to allow full backups
435 # outside Amanda, eg when the machine is in single-user mode.
436 # skip-incr - skip the disk when the level 0 is NOT due. This is used in
437 # archive configurations, where only full dumps are done and
439 # starttime - delay the start of the dump? Default: no delay
440 # strategy - set the dump strategy. Valid strategies are currently:
441 # "standard" - the standard one.
442 # "nofull" - do level 1 dumps every time. This can be used,
443 # for example, for small root filesystems that
444 # only change slightly relative to a site-wide
445 # prototype. Amanda then backs up just the
447 # "noinc" - do level 0 dumps every time.
448 # "skip" - skip all dumps. Useful for sharing a single
449 # disklist in several configurations.
450 # "incronly" - do only incremental dumps. This is similar
451 # to strategy 'nofull', but will increase
452 # the dump level as usual. Full dumps will
453 # only be performed when an 'amadmin force'
455 # Default: [strategy standard]
456 # tape_splitsize - (optional) split dump file into pieces of a specified size.
457 # This allows dumps to be spread across multiple tapes, and can
458 # potentially make more efficient use of tape space. Note that
459 # if this value is too large (more than half the size of the
460 # average dump being split), substantial tape space can be
461 # wasted. If too small, large dumps will be split into
462 # innumerable tiny dumpfiles, adding to restoration complexity.
463 # A good rule of thumb, usually, is 1/10 of the size of your
464 # tape. Default: [disabled]
465 # split_diskbuffer - (optional) When dumping a split dump in PORT-WRITE
466 # mode (usually meaning "no holding disk"), buffer the split
467 # chunks to a file in the directory specified by this option.
469 # fallback_splitsize - (optional) When dumping a split dump in PORT-WRITE
470 # mode, if no split_diskbuffer is specified (or if we somehow
471 # fail to use our split_diskbuffer), we must buffer split
472 # chunks in memory. This specifies the maximum size split
473 # chunks can be in this scenario, and thus the maximum amount
474 # of memory consumed for in-memory splitting. Default: [10m]
476 # Note that you may specify previously defined dumptypes as a shorthand way of
477 # defining parameters.
479 define dumptype global {
480 comment "Global definitions"
481 # This is quite useful for setting global parameters, so you don't have
482 # to type them everywhere. All dumptype definitions in this sample file
483 # do include these definitions, either directly or indirectly.
484 # There's nothing special about the name `global'; if you create any
485 # dumptype that does not contain the word `global' or the name of any
486 # other dumptype that contains it, these definitions won't apply.
487 # Note that these definitions may be overridden in other
488 # dumptypes, if the redefinitions appear *after* the `global'
490 # You may want to use this for globally enabling or disabling
491 # indexing, recording, etc. Some examples:
494 # split_diskbuffer "/raid/amanda"
495 # fallback_splitsize 64m
498 define dumptype always-full {
500 comment "Full dump of this filesystem always"
506 define dumptype root-tar {
509 comment "root partitions dumped with tar"
512 # exclude list "/etc/amanda/exclude.gtar"
516 define dumptype user-tar {
518 comment "user partitions dumped with tar"
522 define dumptype user-tar-span {
525 comment "tape-spanning user partitions dumped with tar"
529 define dumptype high-tar {
531 comment "partitions dumped with tar"
535 define dumptype comp-root-tar {
537 comment "Root partitions with compression"
541 define dumptype comp-user-tar {
546 define dumptype comp-user-tar-span {
551 define dumptype holding-disk {
553 comment "The master-host holding disk itself"
554 holdingdisk no # do not use the holding disk
558 define dumptype comp-user {
560 comment "Non-root partitions on reasonably fast machines"
565 define dumptype comp-user-span {
568 comment "Tape-spanning non-root partitions on reasonably fast machines"
573 define dumptype nocomp-user {
575 comment "Non-root partitions on slow machines"
579 define dumptype nocomp-user-span {
581 comment "Tape-spanning non-root partitions on slow machines"
585 define dumptype comp-root {
587 comment "Root partitions with compression"
592 define dumptype nocomp-root {
594 comment "Root partitions without compression"
598 define dumptype comp-high {
600 comment "very important partitions on fast machines"
605 define dumptype nocomp-high {
607 comment "very important partitions on slow machines"
611 define dumptype nocomp-test {
613 comment "test dump without compression, no /etc/dumpdates recording"
619 define dumptype comp-test {
621 comment "test dump with compression, no /etc/dumpdates recording"
625 define dumptype custom-compress {
628 comment "test dump with custom client compression"
629 compress client custom
630 client_custom_compress "/usr/bin/bzip2"
633 define dumptype encrypt-fast {
636 comment "test dump with fast client compression and server symmetric encryption"
639 server_encrypt "/usr/local/sbin/amcrypt"
640 server_decrypt_option "-d"
645 # These are referred to by the disklist file. They define the attributes
646 # of the network interface that the remote machine is accessed through.
647 # Notes: - netusage above defines the attributes that are used when the
648 # disklist entry doesn't specify otherwise.
649 # - the values below are only samples.
650 # - specifying an interface does not force the traffic to pass
651 # through that interface. Your OS routing tables do that. This
652 # is just a mechanism to stop Amanda trashing your network.
654 # use - bandwidth above which amanda won't start
655 # backups using this interface. Note that if
656 # a single backup will take more than that,
657 # amanda won't try to make it run slower!
659 define interface local {
660 comment "a local disk"
664 define interface le0 {
665 comment "10 Mbps ethernet"
669 # You may include other amanda configuration files, so you can share
670 # dumptypes, tapetypes and interface definitions among several
673 #includefile "/etc/amanda/amanda.conf.main"