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