]>
Commit | Line | Data |
---|---|---|
1 | # | |
2 | # amanda.conf - sample Amanda configuration file. This started off life as | |
3 | # the actual config file in use at CS.UMD.EDU. | |
4 | # | |
5 | # If your configuration is called, say, "csd", then this file normally goes | |
6 | # in /etc/amanda/csd/amanda.conf. | |
7 | # | |
8 | ||
9 | org "DailySet1" # your organization name for reports | |
10 | mailto "amanda" # space separated list of operators at your site | |
11 | dumpuser "amanda" # the user to run dumps under | |
12 | ||
13 | inparallel 4 # maximum dumpers that will run in parallel | |
14 | netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec | |
15 | ||
16 | dumpcycle 4 weeks # the number of days in the normal dump cycle | |
17 | runspercycle 20 # the number of amdump runs in dumpcycle days | |
18 | # (4 weeks * 5 amdump runs per week -- just weekdays) | |
19 | tapecycle 25 tapes # the number of tapes in rotation | |
20 | # 4 weeks (dumpcycle) times 5 tapes per week (just | |
21 | # the weekdays) plus a few to handle errors that | |
22 | # need amflush and so we do not overwrite the full | |
23 | # backups performed at the beginning of the previous | |
24 | # cycle | |
25 | ### ### ### | |
26 | # WARNING: don't use `inf' for tapecycle, it's broken! | |
27 | ### ### ### | |
28 | ||
29 | bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2 | |
30 | bumpdays 1 # minimum days at each level | |
31 | bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) | |
32 | ||
33 | etimeout 300 # number of seconds per filesystem for estimates. | |
34 | #etimeout -600 # total number of seconds for estimates. | |
35 | # a positive number will be multiplied by the number of filesystems on | |
36 | # each host; a negative number will be taken as an absolute total time-out. | |
37 | # The default is 5 minutes per filesystem. | |
38 | ||
39 | ||
40 | # Specify tape device and/or tape changer. If you don't have a tape | |
41 | # changer, and you don't want to use more than one tape per run of | |
42 | # amdump, just comment out the definition of tpchanger. | |
43 | ||
44 | # Some tape changers require tapedev to be defined; others will use | |
45 | # their own tape device selection mechanism. Some use a separate tape | |
46 | # changer device (changerdev), others will simply ignore this | |
47 | # parameter. Some rely on a configuration file (changerfile) to | |
48 | # obtain more information about tape devices, number of slots, etc; | |
49 | # others just need to store some data in files, whose names will start | |
50 | # with changerfile. For more information about individual tape | |
51 | # changers, read docs/TAPE.CHANGERS. | |
52 | ||
53 | # At most one changerfile entry must be defined; select the most | |
54 | # appropriate one for your configuration. If you select man-changer, | |
55 | # keep the first one; if you decide not to use a tape changer, you may | |
56 | # comment them all out. | |
57 | ||
58 | runtapes 1 # number of tapes to be used in a single run of amdump | |
59 | tpchanger "chg-manual" # the tape-changer glue script | |
60 | tapedev "/dev/null" # the no-rewind tape device to be used | |
61 | rawtapedev "/dev/null" # the raw device to be used (ftape only) | |
62 | changerfile "/usr/adm/amanda/DailySet1/changer" | |
63 | changerfile "/usr/adm/amanda/DailySet1/changer-status" | |
64 | changerfile "/etc/amanda/DailySet1/changer.conf" | |
65 | changerdev "/dev/null" | |
66 | ||
67 | tapetype HP-DAT # what kind of tape it is (see tapetypes below) | |
68 | labelstr "^DailySet1[0-9][0-9]*$" # label constraint regex: all tapes must match | |
69 | ||
70 | # Specify holding disks. These are used as a temporary staging area for | |
71 | # dumps before they are written to tape and are recommended for most sites. | |
72 | # The advantages include: tape drive is more likely to operate in streaming | |
73 | # mode (which reduces tape and drive wear, reduces total dump time); multiple | |
74 | # dumps can be done in parallel (which can dramatically reduce total dump time. | |
75 | # The main disadvantage is that dumps on the holding disk need to be flushed | |
76 | # (with amflush) to tape after an operating system crash or a tape failure. | |
77 | # If no holding disks are specified then all dumps will be written directly | |
78 | # to tape. If a dump is too big to fit on the holding disk than it will be | |
79 | # written directly to tape. If more than one holding disk is specified then | |
80 | # they will all be used round-robin. | |
81 | ||
82 | holdingdisk hd1 { | |
83 | comment "main holding disk" | |
84 | directory "/dumps/amanda" # where the holding disk is | |
85 | use 290 Mb # how much space can we use on it | |
86 | # a negative value mean: | |
87 | # use all space except that value | |
88 | chunksize -1 # size of chunk if you want big dump to be | |
89 | # dumped on multiple files on holding disks | |
90 | # N Kb/Mb/Gb split disks in chunks of size N | |
91 | # 0 split disks in INT_MAX/1024 Kb chunks | |
92 | # -1 same as -INT_MAX/1024 (see below) | |
93 | # -N Kb/Mb/Gb dont split, dump larger | |
94 | # filesystems directly to tape | |
95 | # (example: -2 Gb) | |
96 | # chunksize 2 Gb | |
97 | } | |
98 | #holdingdisk hd2 { | |
99 | # directory "/dumps2/amanda" | |
100 | # use 1000 Mb | |
101 | # } | |
102 | #holdingdisk hd3 { | |
103 | # directory "/mnt/disk4" | |
104 | # use 1000 Mb | |
105 | # } | |
106 | ||
107 | ||
108 | # If amanda cannot find a tape on which to store backups, it will run | |
109 | # as many backups as it can to the holding disks. In order to save | |
110 | # space for unattended backups, by default, amanda will only perform | |
111 | # incremental backups in this case, i.e., it will reserve 100% of the | |
112 | # holding disk space for the so-called degraded mode backups. | |
113 | # However, if you specify a different value for the `reserve' | |
114 | # parameter, amanda will not degrade backups if they will fit in the | |
115 | # non-reserved portion of the holding disk. | |
116 | ||
117 | # reserve 30 # percent | |
118 | ||
119 | ||
120 | # This means save at least 30% of the holding disk space for degraded | |
121 | # mode backups. | |
122 | ||
123 | # Amanda needs a few Mb of diskspace for the log and debug files, | |
124 | # as well as a database. This stuff can grow large, so the conf directory | |
125 | # isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm. | |
126 | # Create an amanda directory under there. You need a separate infofile and | |
127 | # logdir for each configuration, so create subdirectories for each conf and | |
128 | # put the files there. Specify the locations below. | |
129 | ||
130 | # Note that, although the keyword below is infofile, it is only so for | |
131 | # historic reasons, since now it is supposed to be a directory (unless | |
132 | # you have selected some database format other than the `text' default) | |
133 | infofile "/var/lib/amanda/DailySet1/curinfo" # database DIRECTORY | |
134 | logdir "/var/lib/amanda/DailySet1" # log directory | |
135 | indexdir "/var/lib/amanda/DailySet1/index" # index directory | |
136 | #tapelist "/usr/adm/amanda/DailySet1/tapelist" # list of used tapes | |
137 | # tapelist is stored, by default, in the directory that contains amanda.conf | |
138 | ||
139 | ||
140 | # tapetypes | |
141 | ||
142 | # Define the type of tape you use here, and use it in "tapetype" | |
143 | # above. Some typical types of tapes are included here. The tapetype | |
144 | # tells amanda how many MB will fit on the tape, how big the filemarks | |
145 | # are, and how fast the tape device is. | |
146 | ||
147 | # A filemark is the amount of wasted space every time a tape section | |
148 | # ends. If you run `make tapetype' in tape-src, you'll get a program | |
149 | # that generates tapetype entries, but it is slow as hell, use it only | |
150 | # if you really must and, if you do, make sure you post the data to | |
151 | # the amanda mailing list, so that others can use what you found out | |
152 | # by searching the archives. | |
153 | ||
154 | # For completeness Amanda should calculate the inter-record gaps too, | |
155 | # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using | |
156 | # 9 tracks for amanda and need IRG calculations? Drop me a note if | |
157 | # so. | |
158 | ||
159 | # If you want amanda to print postscript paper tape labels | |
160 | # add a line after the comment in the tapetype of the form | |
161 | # lbl-templ "/usr/share/amanda/label.ps" | |
162 | ||
163 | # if you want the label to go to a printer other than the default | |
164 | # for your system, you can also add a line above for a different | |
165 | # printer. (i usually add that line after the dumpuser specification) | |
166 | ||
167 | # dumpuser "operator" # the user to run dumps under | |
168 | # printer "mypostscript" # printer to print paper label on | |
169 | ||
170 | # here is an example of my definition for an EXB-8500 | |
171 | ||
172 | # define tapetype EXB-8500 { | |
173 | # ... | |
174 | # lbl-templ "/usr/share/amanda/lbl.exabyte.ps" | |
175 | # } | |
176 | ||
177 | ||
178 | define tapetype QIC-60 { | |
179 | comment "Archive Viper" | |
180 | length 60 mbytes | |
181 | filemark 100 kbytes # don't know a better value | |
182 | speed 100 kbytes # dito | |
183 | } | |
184 | ||
185 | define tapetype DEC-DLT2000 { | |
186 | comment "DEC Differential Digital Linear Tape 2000" | |
187 | length 15000 mbytes | |
188 | filemark 8 kbytes | |
189 | speed 1250 kbytes | |
190 | } | |
191 | ||
192 | # goluboff@butch.Colorado.EDU | |
193 | # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996) | |
194 | define tapetype DLT { | |
195 | comment "DLT tape drives" | |
196 | length 20000 mbytes # 20 Gig tapes | |
197 | filemark 2000 kbytes # I don't know what this means | |
198 | speed 1536 kbytes # 1.5 Mb/s | |
199 | } | |
200 | ||
201 | define tapetype SURESTORE-1200E { | |
202 | comment "HP AutoLoader" | |
203 | length 3900 mbytes | |
204 | filemark 100 kbytes | |
205 | speed 500 kbytes | |
206 | } | |
207 | ||
208 | define tapetype EXB-8500 { | |
209 | comment "Exabyte EXB-8500 drive on decent machine" | |
210 | length 4200 mbytes | |
211 | filemark 48 kbytes | |
212 | speed 474 kbytes | |
213 | } | |
214 | ||
215 | define tapetype EXB-8200 { | |
216 | comment "Exabyte EXB-8200 drive on decent machine" | |
217 | length 2200 mbytes | |
218 | filemark 2130 kbytes | |
219 | speed 240 kbytes | |
220 | } | |
221 | ||
222 | define tapetype HP-DAT { | |
223 | comment "DAT tape drives" | |
224 | # data provided by Rob Browning <rlb@cs.utexas.edu> | |
225 | length 1930 mbytes | |
226 | filemark 111 kbytes | |
227 | speed 468 kbytes | |
228 | } | |
229 | ||
230 | define tapetype DAT { | |
231 | comment "DAT tape drives" | |
232 | length 1000 mbytes # these numbers are not accurate | |
233 | filemark 100 kbytes # but you get the idea | |
234 | speed 100 kbytes | |
235 | } | |
236 | ||
237 | define tapetype MIMSY-MEGATAPE { | |
238 | comment "Megatape (Exabyte based) drive through Emulex on Vax 8600" | |
239 | length 2200 mbytes | |
240 | filemark 2130 kbytes | |
241 | speed 170 kbytes # limited by the Emulex bus interface, ugh | |
242 | } | |
243 | ||
244 | ||
245 | # dumptypes | |
246 | # | |
247 | # These are referred to by the disklist file. The dumptype specifies | |
248 | # certain parameters for dumping including: | |
249 | # auth - authentication scheme to use between server and client. | |
250 | # Valid values are "bsd" and "krb4". Default: [auth bsd] | |
251 | # comment - just a comment string | |
252 | # comprate - set default compression rate. Should be followed by one or | |
253 | # two numbers, optionally separated by a comma. The 1st is | |
254 | # the full compression rate; the 2nd is the incremental rate. | |
255 | # If the second is omitted, it is assumed equal to the first. | |
256 | # The numbers represent the amount of the original file the | |
257 | # compressed file is expected to take up. | |
258 | # Default: [comprate 0.50, 0.50] | |
259 | # compress - specify compression of the backed up data. Valid values are: | |
260 | # "none" - don't compress the dump output. | |
261 | # "client best" - compress on the client using the best (and | |
262 | # probably slowest) algorithm. | |
263 | # "client fast" - compress on the client using fast algorithm. | |
264 | # "server best" - compress on the tape host using the best (and | |
265 | # probably slowest) algorithm. | |
266 | # "server fast" - compress on the tape host using a fast | |
267 | # algorithm. This may be useful when a fast | |
268 | # tape host is backing up slow clients. | |
269 | # Default: [compress client fast] | |
270 | # dumpcycle - set the number of days in the dump cycle, ie, set how often a | |
271 | # full dump should be performed. Default: from DUMPCYCLE above | |
272 | # exclude - specify files and directories to be excluded from the dump. | |
273 | # Useful with gnutar only; silently ignored by dump and samba. | |
274 | # Valid values are: | |
275 | # "pattern" - a shell glob pattern defining which files | |
276 | # to exclude. | |
277 | # gnutar gets --exclude="pattern" | |
278 | # list "filename" - a file (on the client!) containing patterns | |
279 | # re's (1 per line) defining which files to | |
280 | # exclude. | |
281 | # gnutar gets --exclude-from="filename" | |
282 | # Note that the `full pathname' of a file within its | |
283 | # filesystem starts with `./', because of the way amanda runs | |
284 | # gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note | |
285 | # the final dot!) Thus, if you're backing up `/usr' with a | |
286 | # diskfile entry like ``host /usr gnutar-root', but you don't | |
287 | # want to backup /usr/tmp, your exclude list should contain | |
288 | # the pattern `./tmp', as this is relative to the `/usr' above. | |
289 | # Please refer to the man-page of gnutar for more information. | |
290 | # Default: include all files | |
291 | # holdingdisk - should the holding disk be used for this dump. Useful for | |
292 | # dumping the holding disk itself. Default: [holdingdisk yes] | |
293 | # ignore - do not back this filesystem up. Useful for sharing a single | |
294 | # disklist in several configurations. | |
295 | # index - keep an index of the files backed up. Default: [index no] | |
296 | # kencrypt - encrypt the data stream between the client and server. | |
297 | # Default: [kencrypt no] | |
298 | # maxdumps - max number of concurrent dumps to run on the client. | |
299 | # Default: [maxdumps 1] | |
300 | # priority - priority level of the dump. Valid levels are "low", "medium" | |
301 | # or "high". These are really only used when Amanda has no | |
302 | # tape to write to because of some error. In that "degraded | |
303 | # mode", as many incrementals as will fit on the holding disk | |
304 | # are done, higher priority first, to insure the important | |
305 | # disks are at least dumped. Default: [priority medium] | |
306 | # program - specify the dump system to use. Valid values are "DUMP" and | |
307 | # "GNUTAR". Default: [program "DUMP"]. | |
308 | # record - record the dump in /etc/dumpdates. Default: [record yes] | |
309 | # skip-full - skip the disk when a level 0 is due, to allow full backups | |
310 | # outside Amanda, eg when the machine is in single-user mode. | |
311 | # skip-incr - skip the disk when the level 0 is NOT due. This is used in | |
312 | # archive configurations, where only full dumps are done and | |
313 | # the tapes saved. | |
314 | # starttime - delay the start of the dump? Default: no delay | |
315 | # strategy - set the dump strategy. Valid strategies are currently: | |
316 | # "standard" - the standard one. | |
317 | # "nofull" - do level 1 dumps every time. This can be used, | |
318 | # for example, for small root filesystems that | |
319 | # only change slightly relative to a site-wide | |
320 | # prototype. Amanda then backs up just the | |
321 | # changes. | |
322 | # "noinc" - do level 0 dumps every time. | |
323 | # Unfortunately, this is not currently | |
324 | # implemented. Use `dumpcycle 0' | |
325 | # instead. | |
326 | # "skip" - skip all dumps. Useful for sharing a single | |
327 | # disklist in several configurations. | |
328 | # Default: [strategy standard] | |
329 | # | |
330 | # Note that you may specify previously defined dumptypes as a shorthand way | |
331 | # of defining parameters. | |
332 | ||
333 | define dumptype global { | |
334 | comment "Global definitions" | |
335 | # This is quite useful for setting global parameters, so you don't have | |
336 | # to type them everywhere. All dumptype definitions in this sample file | |
337 | # do include these definitions, either directly or indirectly. | |
338 | # There's nothing special about the name `global'; if you create any | |
339 | # dumptype that does not contain the word `global' or the name of any | |
340 | # other dumptype that contains it, these definitions won't apply. | |
341 | # Note that these definitions may be overridden in other | |
342 | # dumptypes, if the redefinitions appear *after* the `global' | |
343 | # dumptype name. | |
344 | # You may want to use this for globally enabling or disabling | |
345 | # indexing, recording, etc. Some examples: | |
346 | # index yes | |
347 | # record no | |
348 | } | |
349 | ||
350 | define dumptype always-full { | |
351 | global | |
352 | comment "Full dump of this filesystem always" | |
353 | compress none | |
354 | priority high | |
355 | dumpcycle 0 | |
356 | } | |
357 | ||
358 | define dumptype root-tar { | |
359 | global | |
360 | program "GNUTAR" | |
361 | comment "root partitions dumped with tar" | |
362 | compress none | |
363 | index | |
364 | exclude list "/usr/local/lib/amanda/exclude.gtar" | |
365 | priority low | |
366 | } | |
367 | ||
368 | define dumptype user-tar { | |
369 | root-tar | |
370 | comment "user partitions dumped with tar" | |
371 | priority medium | |
372 | } | |
373 | ||
374 | define dumptype high-tar { | |
375 | root-tar | |
376 | comment "partitions dumped with tar" | |
377 | priority high | |
378 | } | |
379 | ||
380 | define dumptype comp-root-tar { | |
381 | root-tar | |
382 | comment "Root partitions with compression" | |
383 | compress client fast | |
384 | } | |
385 | ||
386 | define dumptype comp-user-tar { | |
387 | user-tar | |
388 | compress client fast | |
389 | } | |
390 | ||
391 | define dumptype holding-disk { | |
392 | global | |
393 | comment "The master-host holding disk itself" | |
394 | holdingdisk no # do not use the holding disk | |
395 | priority medium | |
396 | } | |
397 | ||
398 | define dumptype comp-user { | |
399 | global | |
400 | comment "Non-root partitions on reasonably fast machines" | |
401 | compress client fast | |
402 | priority medium | |
403 | } | |
404 | ||
405 | define dumptype nocomp-user { | |
406 | comp-user | |
407 | comment "Non-root partitions on slow machines" | |
408 | compress none | |
409 | } | |
410 | ||
411 | define dumptype comp-root { | |
412 | global | |
413 | comment "Root partitions with compression" | |
414 | compress client fast | |
415 | priority low | |
416 | } | |
417 | ||
418 | define dumptype nocomp-root { | |
419 | comp-root | |
420 | comment "Root partitions without compression" | |
421 | compress none | |
422 | } | |
423 | ||
424 | define dumptype comp-high { | |
425 | global | |
426 | comment "very important partitions on fast machines" | |
427 | compress client best | |
428 | priority high | |
429 | } | |
430 | ||
431 | define dumptype nocomp-high { | |
432 | comp-high | |
433 | comment "very important partitions on slow machines" | |
434 | compress none | |
435 | } | |
436 | ||
437 | define dumptype nocomp-test { | |
438 | global | |
439 | comment "test dump without compression, no /etc/dumpdates recording" | |
440 | compress none | |
441 | record no | |
442 | priority medium | |
443 | } | |
444 | ||
445 | define dumptype comp-test { | |
446 | nocomp-test | |
447 | comment "test dump with compression, no /etc/dumpdates recording" | |
448 | compress client fast | |
449 | } | |
450 | ||
451 | # network interfaces | |
452 | # | |
453 | # These are referred to by the disklist file. They define the attributes | |
454 | # of the network interface that the remote machine is accessed through. | |
455 | # Notes: - netusage above defines the attributes that are used when the | |
456 | # disklist entry doesn't specify otherwise. | |
457 | # - the values below are only samples. | |
458 | # - specifying an interface does not force the traffic to pass | |
459 | # through that interface. Your OS routing tables do that. This | |
460 | # is just a mechanism to stop Amanda trashing your network. | |
461 | # Attributes are: | |
462 | # use - bandwidth above which amanda won't start | |
463 | # backups using this interface. Note that if | |
464 | # a single backup will take more than that, | |
465 | # amanda won't try to make it run slower! | |
466 | ||
467 | define interface local { | |
468 | comment "a local disk" | |
469 | use 1000 kbps | |
470 | } | |
471 | ||
472 | define interface le0 { | |
473 | comment "10 Mbps ethernet" | |
474 | use 400 kbps | |
475 | } | |
476 | ||
477 | # You may include other amanda configuration files, so you can share | |
478 | # dumptypes, tapetypes and interface definitions among several | |
479 | # configurations. | |
480 | ||
481 | #includefile "/usr/local/amanda.conf.main" |