1 inparallel 4 # maximum dumpers that will run in parallel (max 63)
2 # this maximum can be increased at compile-time,
3 # modifying MAX_DUMPERS in server-src/driverio.h
5 dumporder "sssS" # specify the priority order of each dumper
10 # b -> smallest bandwidth
11 # B -> biggest bandwitdh
12 # try "BTBTBTBTBTBT" if you are not holding
15 taperalgo first # The algorithm used to choose which dump image to send
18 # Possible values: [first|firstfit|largest|largestfit|smallest|last]
21 # first First in - first out.
22 # firstfit The first dump image that will fit on the current tape.
23 # largest The largest dump image.
24 # largestfit The largest dump image that will fit on the current tape.
25 # smallest The smallest dump image.
26 # last Last in - first out.
27 displayunit "g" # Possible values: "k|m|g|t"
29 # The unit used to print many numbers.
30 # k=kilo, m=mega, g=giga, t=tera
31 netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per sec
33 bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
34 bumppercent 20 # minimum savings (threshold) to bump level 1 -> 2
35 bumpdays 1 # minimum days at each level
37 # By default, Amanda can only track at most one run per calendar day. When
38 # the usetimestamps option is enabled, however, Amanda can track as many
39 # runs as you care to make.
40 # WARNING: This option is not backward-compatible. Do not enable it if you
41 # intend to downgrade your server installation to any version
42 # earlier than Amanda 2.5.1
45 device_output_buffer_size 1280k
46 # amount of buffer space to use when writing to devices
48 # If you want Amanda to automatically label any non-Amanda tapes it
49 # encounters, uncomment the line below. Note that this will ERASE any
50 # non-Amanda tapes you may have, and may also ERASE any near-failing tapes.
52 ## autolabel "DailySet1-%%%" empty
54 maxdumpsize -1 # Maximum total size the planner will schedule
55 # for a run (default: runtapes * tape_length) (kbytes).
56 bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
60 amrecover_changer "changer" # amrecover will use the changer if you restore
61 # from this device. It could be a string like 'changer' and amrecover will use your
62 # changer if you set your tape to 'changer' with 'setdevice changer' or via
63 # 'tapedev "changer"' in amanda-client.conf
68 # If amanda cannot find a tape on which to store backups, it will run
69 # as many backups as it can to the holding disks. In order to save
70 # space for unattended backups, by default, amanda will only perform
71 # incremental backups in this case, i.e., it will reserve 100% of the
72 # holding disk space for the so-called degraded mode backups.
73 # However, if you specify a different value for the `reserve'
74 # parameter, amanda will not degrade backups if they will fit in the
75 # non-reserved portion of the holding disk.
77 # reserve 30 # percent
78 # This means save at least 30% of the holding disk space for degraded
82 # if autoflush is set to yes, then amdump will schedule all dump on
83 # holding disks to be flush to tape during the run.
85 # Amanda needs a few Mb of diskspace for the log and debug files,
86 # as well as a database. This stuff can grow large, so the conf directory
87 # isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm.
88 # Create an amanda directory under there. You need a separate infofile and
89 # logdir for each configuration, so create subdirectories for each conf and
90 # put the files there. Specify the locations below.
92 # Note that, although the keyword below is infofile, it is only so for
93 # historic reasons, since now it is supposed to be a directory (unless
94 # you have selected some database format other than the `text' default)
95 infofile "@CONFIG_DIR@/@DEFAULT_CONFIG@/curinfo" # database DIRECTORY
96 logdir "@CONFIG_DIR@/@DEFAULT_CONFIG@" # log directory
97 indexdir "@CONFIG_DIR@/@DEFAULT_CONFIG@/index" # index directory
98 #tapelist "@CONFIG_DIR/DailySet1/tapelist" # list of used tapes
99 # tapelist is stored, by default, in the directory that contains amanda.conf
101 # Specify holding disks. These are used as a temporary staging area for
102 # dumps before they are written to tape and are recommended for most sites.
103 # The advantages include: tape drive is more likely to operate in streaming
104 # mode (which reduces tape and drive wear, reduces total dump time); multiple
105 # dumps can be done in parallel (which can dramatically reduce total dump time.
106 # The main disadvantage is that dumps on the holding disk need to be flushed
107 # (with amflush) to tape after an operating system crash or a tape failure.
108 # If no holding disks are specified then all dumps will be written directly
109 # to tape. If a dump is too big to fit on the holding disk than it will be
110 # written directly to tape. If more than one holding disk is specified then
111 # they will all be used based on activity and available space.
114 # comment "main holding disk"
115 # directory "/dumps/amanda" # where the holding disk is
116 # use -100 Mb # how much space can we use on it
117 # # a non-positive value means:
118 # # use all space but that value
119 # chunksize 1Gb # size of chunk if you want big dump to be
120 # # dumped on multiple files on holding disks
121 # # N Kb/Mb/Gb split images in chunks of size N
122 # # The maximum value should be
123 # # (MAX_FILE_SIZE - 1Mb)
124 # # 0 same as INT_MAX bytes
127 # directory "/dumps2/amanda"
133 # These are referred to by the disklist file. They define the attributes
134 # of the network interface that the remote machine is accessed through.
135 # Notes: - netusage above defines the attributes t
136 # disklist entry doesn't specify otherwise.
137 # - the values below are only samples.
138 # - specifying an interface does not force the traffic to pass
139 # through that interface. Your OS routing tables do that. This
140 # is just a mechanism to stop Amanda trashing your network.
142 # use - bandwidth above which amanda won't start
143 # backups using this interface. Note that if
144 # a single backup will take more than that,
145 # amanda won't try to make it run slower!
147 define interface local {
148 comment "a local disk"
152 #define interface le0 {
153 # comment "10 Mbps ethernet"