1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"
5 <!-- entities files to use -->
6 <!ENTITY % global_entities SYSTEM '../entities/global.entities'>
10 <refentry id='amanda.conf.5'>
13 <refentrytitle>amanda.conf</refentrytitle>
14 <manvolnum>5</manvolnum>
17 <refname>amanda.conf</refname>
18 <refpurpose>Main configuration file for &A;, the Advanced Maryland Automatic Network Disk Archiver</refpurpose>
20 <!-- body begins here -->
22 <refsect1><title>DESCRIPTION</title>
23 <para>&amconf; is the main configuration file for &A;. This manpage lists the
24 relevant sections and parameters of this file for quick reference.</para>
25 <para> The file <emphasis remap='B'><CONFIG_DIR>/<config>/amanda.conf</emphasis> is loaded.</para>
28 <refsect1><title>PARAMETERS</title>
30 <para>There are a number of configuration parameters that control the
31 behavior of the &A; programs.
32 All have default values,
33 so you need not specify the parameter in
34 <emphasis remap='B'>amanda.conf</emphasis>
35 if the default is suitable.</para>
37 <para>Lines starting with # are ignored, as are blank lines.
38 Comments may be placed on a line with a directive by starting
40 The remainder of the line is ignored.</para>
42 <para>Keywords are case insensitive, i.e.
43 <emphasis remap='B'>mailto</emphasis>
45 <emphasis remap='B'>MailTo</emphasis>
46 are treated the same.</para>
48 <para>Integer arguments may have one of the following (case insensitive) suffixes,
49 some of which have a multiplier effect:</para>
51 <refsect2><title>POSSIBLE SUFFIXES</title>
53 <variablelist remap='TP'>
55 <term><emphasis remap='B'>b byte bytes</emphasis></term>
57 <para>Some number of bytes.</para>
61 <term><emphasis remap='B'>bps</emphasis></term>
63 <para>Some number of bytes per second.</para>
67 <term><emphasis remap='B'>k kb kbyte kbytes kilobyte kilobytes</emphasis></term>
69 <para>Some number of kilobytes (bytes*1024).</para>
73 <term><emphasis remap='B'>kps kbps</emphasis></term>
75 <para>Some number of kilobytes per second (bytes*1024).</para>
79 <term><emphasis remap='B'>m mb meg mbyte mbytes megabyte megabytes</emphasis></term>
81 <para>Some number of megabytes (bytes*1024*1024).</para>
85 <term><emphasis remap='B'>mps mbps</emphasis></term>
87 <para>Some number of megabytes per second (bytes*1024*1024).</para>
91 <term><emphasis remap='B'>g gb gbyte gbytes gigabyte gigabytes</emphasis></term>
93 <para>Some number of gigabytes (bytes*1024*1024*1024).</para>
97 <term><emphasis remap='B'>tape tapes</emphasis></term>
99 <para>Some number of tapes.</para>
103 <term><emphasis remap='B'>day days</emphasis></term>
105 <para>Some number of days.</para>
109 <term><emphasis remap='B'>week weeks</emphasis></term>
111 <para>Some number of weeks (days*7).</para>
114 <emphasis remap='B'>inf</emphasis>
115 may be used in most places where an integer is expected
116 to mean an infinite amount.
118 <para>Boolean arguments may have any of the values
119 <emphasis remap='B'>y</emphasis>,
120 <emphasis remap='B'>yes</emphasis>,
121 <emphasis remap='B'>t</emphasis>,
122 <emphasis remap='B'>true</emphasis>
124 <emphasis remap='B'>on</emphasis>
125 to indicate a true state, or
126 <emphasis remap='B'>n</emphasis>,
127 <emphasis remap='B'>no</emphasis>,
128 <emphasis remap='B'>f</emphasis>,
129 <emphasis remap='B'>false</emphasis>
131 <emphasis remap='B'>off</emphasis>
132 to indicate a false state.
133 If no argument is given,
134 <emphasis remap='B'>true</emphasis>
144 <title>PARAMETERS</title>
146 <variablelist remap='TP'>
148 <term><emphasis remap='B'>org</emphasis> <emphasis remap='I'> string</emphasis></term>
151 <emphasis remap='I'>daily</emphasis>.
152 A descriptive name for the configuration.
153 This string appears in the Subject line of mail reports.
154 Each &A; configuration should have a different string to keep
155 mail reports distinct.</para>
159 <term><emphasis remap='B'>mailto</emphasis> <emphasis remap='I'> string</emphasis></term>
162 <emphasis remap='I'>operators</emphasis>.
163 A space separated list of recipients for mail reports.</para>
167 <term><emphasis remap='B'>dumpcycle</emphasis> <emphasis remap='I'> int</emphasis></term>
170 <emphasis remap='I'>10 days</emphasis>.
171 The number of days in the backup cycle.
172 Each disk will get a full backup at least this often.
173 Setting this to zero tries to do a full backup each run.</para>
174 <note>This parameter may also be set in a specific
175 <emphasis remap='B'>dumptype</emphasis>
177 This value sets the default for all
178 <emphasis remap='B'>dumptype</emphasis>s
180 <emphasis remap='B'>amanda.conf</emphasis>
182 <emphasis remap='B'>dumptype</emphasis>s
188 <term><emphasis remap='B'>runspercycle</emphasis> <emphasis remap='I'> int</emphasis></term>
191 <emphasis remap='I'>same as dumpcycle</emphasis>.
192 The number of amdump runs in
193 <emphasis remap='B'>dumpcycle</emphasis>
195 A value of 0 means the same value as
196 <emphasis remap='B'>dumpcycle</emphasis>.
197 A value of -1 means guess the number of runs from the
198 <emphasis remap='I'>tapelist</emphasis>
200 which is the number of tapes used in the last
201 <emphasis remap='B'>dumpcycle</emphasis>
203 <emphasis remap='B'>runtapes</emphasis>.</para>
207 <term><emphasis remap='B'>tapecycle</emphasis> <emphasis remap='I'> int</emphasis></term>
210 <emphasis remap='I'>15 tapes</emphasis>.
211 Typically tapes are used by &A; in an ordered rotation. The <emphasis remap='B'>tapecycle</emphasis> parameter
212 defines the size of that rotation. The number of tapes in rotation must be larger than the number of tapes
213 required for a complete dump cycle (see the <emphasis remap='B'>dumpcycle</emphasis> parameter).
216 This is calculated by multiplying the number of &amdump; runs per dump cycle
217 (<emphasis remap='B'>runspercycle</emphasis> parameter) times the number of tapes used per run
218 (<emphasis remap='B'>runtapes</emphasis> parameter). Typically two to four times this calculated number of tapes are in rotation.
219 While &A; is always willing to use a new tape in its rotation, it refuses to reuse a tape until at
220 least '<emphasis remap='B'>tapecycle</emphasis> -1' number of other tapes have been used.
223 It is considered good administrative practice to set the <emphasis remap='B'>tapecycle</emphasis> parameter
224 slightly lower than the actual number of tapes in rotation. This allows the administrator to more easily cope
225 with damaged or misplaced tapes or schedule adjustments that call for slight adjustments in the rotation order.
231 <term><emphasis remap='B'>usetimestamps</emphasis>
232 <emphasis remap='I'> bool</emphasis></term>
234 <para>Default: <emphasis remap='B'>No</emphasis>.
235 By default, Amanda can only track at most one run per calendar day. When
236 this option is enabled, however, Amanda can track as many runs as you care
240 <emphasis remap='B'>WARNING</emphasis>: This option is not backward-compatible.
241 Do not enable it if you intend to downgrade your server installation to
242 Amanda community edition 2.5.0
248 <term><emphasis remap='B'>label_new_tapes</emphasis>
249 <emphasis remap='I'> string</emphasis></term>
251 <para>Default: not set.
252 When set, this directive will cause &A; to automatically write an &A;
253 tape label to any blank tape she encounters. This option is DANGEROUS
254 because when set, &A; will ERASE any non-&A; tapes you may have, and may
255 also ERASE any near-failing tapes. Use with caution.</para>
256 <para>When using this directive, specify the template for new tape
257 labels. The template should contain some number of contiguous '%'
258 characters, which will be replaced with a generated number. Be sure to
259 specify enough '%' characters that you do not run out of tape labels.
261 <markup>label_new_tapes "DailySet1-%%%"</markup>
267 <term><emphasis remap='B'>dumpuser</emphasis> <emphasis remap='I'> string</emphasis></term>
270 <emphasis remap='I'>amanda</emphasis>.
271 The login name &A; uses to run the backups.
272 The backup client hosts must allow access
273 from the tape server host as this user via
274 <markup>.rhosts</markup>
276 <markup>.amandahosts</markup>,
277 depending on how the &A; software was built.</para>
281 <term><emphasis remap='B'>printer</emphasis> string</term>
283 <para>Printer to use when doing tape labels.
285 <emphasis remap='B'>lbl-templ</emphasis>
286 <emphasis remap='B'>tapetype</emphasis>
291 <term><emphasis remap='B'>tapedev</emphasis> string</term>
294 <filename>null:</filename>.
295 The path name of the non-rewinding tape device.
296 Non-rewinding tape device names often have an 'n' in the name,
298 <filename>/dev/rmt/0mn</filename>,
299 however this is operating system specific and you should consult
300 that documentation for detailed naming information.</para>
302 <para>If a tape changer is configured
304 <emphasis remap='B'>tpchanger</emphasis>
305 option), this option might not be used.</para>
308 <emphasis remap='B'>null</emphasis>
309 output driver is selected
310 (see the section OUTPUT DRIVERS in the
311 <citerefentry><refentrytitle>amanda</refentrytitle><manvolnum>8</manvolnum></citerefentry>
312 manpage for more information),
315 will run normally but all images will be thrown away.
316 This should only be used for debugging and testing,
317 and probably only with the
318 <emphasis remap='B'>record</emphasis>
320 <emphasis remap='I'>no</emphasis>.</para>
325 <term><emphasis remap='B'>rawtapedev</emphasis> string</term>
328 <filename>null:</filename>.
329 The path name of the raw tape device.
330 This is only used if &A; is compiled for Linux machines with floppy tapes
331 and is needed for QIC volume table operations.</para>
335 <term><emphasis remap='B'>tpchanger</emphasis> string</term>
338 <emphasis remap='I'>none</emphasis>.
339 The name of the tape changer.
340 If a tape changer is not configured, this option is not used
341 and should be commented out of the configuration file.</para>
342 <para>If a tape changer is configured, choose one of the changer scripts
343 (e.g. <emphasis remap='B'>chg-scsi</emphasis>)
344 and enter that here.</para>
349 <term><emphasis remap='B'>changerdev</emphasis> string</term>
352 <filename>/dev/null</filename>.
353 A tape changer configuration parameter.
354 Usage depends on the particular changer defined with the
355 <emphasis remap='B'>tpchanger</emphasis>
360 <term><emphasis remap='B'>changerfile</emphasis> string</term>
363 <filename>/usr/adm/amanda/log/changer-status</filename>.
364 A tape changer configuration parameter.
365 Usage depends on the particular changer defined with the
366 <emphasis remap='B'>tpchanger</emphasis>
371 <term><emphasis remap='B'>runtapes</emphasis> int</term>
374 <literal>1</literal>.
375 The maximum number of tapes used in a single run.
376 If a tape changer is not configured, this option is not used
377 and should be commented out of the configuration file.</para>
378 <para>If a tape changer is configured, this may be set larger than one to
379 let &A; write to more than one tape.</para>
380 <para>Note that this is an upper bound on the number of tapes,
381 and &A; may use less.</para>
382 <para>Also note that as of this release, &A; does not support true tape overflow.
383 When it reaches the end of one tape,
384 the backup image &A; was processing starts over again on the next tape.</para>
389 <term><emphasis remap='B'>maxdumpsize</emphasis> int</term>
392 <emphasis remap='I'>runtapes</emphasis>*<emphasis remap='I'>tape_length</emphasis>.
393 Maximum number of bytes the planner will schedule for a run.</para>
397 <term><emphasis remap='B'>taperalgo</emphasis> [first|firstfit|largest|largestfit|smallest|last]</term>
400 <emphasis remap='I'>first</emphasis>.
401 The algorithm used to choose which dump image to send to the taper.</para>
403 <variablelist remap='TP'>
405 <term><emphasis remap='B'>first</emphasis></term>
407 <para>First in, first out.</para>
411 <term><emphasis remap='B'>firstfit</emphasis></term>
413 <para>The first dump image that will fit on the current tape.</para>
417 <term><emphasis remap='B'>largest</emphasis></term>
419 <para>The largest dump image.</para>
423 <term><emphasis remap='B'>largestfit</emphasis></term>
425 <para>The largest dump image that will fit on the current tape.</para>
429 <term><emphasis remap='B'>smallest</emphasis></term>
431 <para>The smallest dump image.</para>
435 <term><emphasis remap='B'>last</emphasis></term>
437 <para>Last in, first out.</para>
445 <term><emphasis remap='B'>labelstr</emphasis> <emphasis remap='I'> string</emphasis></term>
448 <emphasis remap='I'>.*</emphasis>.
449 The tape label constraint regular expression.
450 All tape labels generated (see
451 <citerefentry><refentrytitle>amlabel</refentrytitle><manvolnum>8</manvolnum></citerefentry>)
452 and used by this configuration must match the regular expression.
453 If multiple configurations are run from the same tape server host,
454 it is helpful to set their labels to different strings
455 (for example, "DAILY[0-9][0-9]*" vs.
456 "ARCHIVE[0-9][0-9]*")
457 to avoid overwriting each other's tapes.</para>
461 <term><emphasis remap='B'>tapetype</emphasis> <emphasis remap='I'> string</emphasis></term>
464 <emphasis remap='I'>EXABYTE</emphasis>.
465 The type of tape drive associated with
466 <emphasis remap='B'>tapedev</emphasis>
468 <emphasis remap='B'>tpchanger</emphasis>.
469 This refers to one of the defined <emphasis remap='B'>tapetype</emphasis>s
470 in the config file (see below), which specify various tape parameters,
472 <emphasis remap='B'>length</emphasis>,
473 <emphasis remap='B'>filemark</emphasis>
475 <emphasis remap='B'>speed</emphasis>
476 of the tape media and device.</para>
477 <para>First character of a <emphasis remap='B'>tapetype</emphasis> string must
478 be an alphabetic character</para>
482 <term><emphasis remap='B'>ctimeout</emphasis> int</term>
485 <emphasis remap='I'>30 seconds</emphasis>.
486 Maximum amount of time that
487 <emphasis remap='B'>amcheck</emphasis>
488 will wait for each client host.</para>
492 <term><emphasis remap='B'>dtimeout</emphasis> int</term>
495 <emphasis remap='I'>1800 seconds</emphasis>.
496 Amount of idle time per disk on a given client that a
497 <emphasis remap='B'>dumper</emphasis>
499 <command>amdump</command>
500 will wait before it fails with a data timeout error.</para>
504 <term><emphasis remap='B'>etimeout</emphasis> int</term>
507 <emphasis remap='I'>300 seconds</emphasis>.
508 Amount of time per disk on a given client that the
509 <emphasis remap='B'>planner</emphasis>
511 <command>amdump</command>
512 will wait to get the dump size estimates.
513 For instance, with the default of 300 seconds and four disks on client A,
514 <emphasis remap='B'>planner</emphasis>
515 will wait up to 20 minutes for that machine.
516 A negative value will be interpreted as a total amount of time to wait
517 per client instead of per disk.</para>
521 <term><emphasis remap='B'>netusage</emphasis> int</term>
524 <emphasis remap='I'>300 Kbps</emphasis>.
525 The maximum network bandwidth allocated to &A;, in Kbytes per second.
527 <emphasis remap='B'>interface</emphasis>
532 <term><emphasis remap='B'>inparallel</emphasis> int</term>
535 <literal>10</literal>.
536 The maximum number of backups that &A; will attempt to run in parallel.
537 &A; will stay within the constraints of network bandwidth and
538 holding disk space available, so it doesn't hurt to set
539 this number a bit high. Some contention can occur with larger numbers
540 of backups, but this effect is relatively small on most systems.</para>
545 <term><emphasis remap='B'>displayunit</emphasis> "k|m|g|t"</term>
548 <literal>"k"</literal>.
549 The unit used to print many numbers, k=kilo, m=mega, g=giga, t=tera.
555 <term><emphasis remap='B'>dumporder</emphasis> string</term>
558 <emphasis remap='I'>tttTTTTTTT</emphasis>.
559 The priority order of each dumper:</para>
562 <listitem><para>s: smallest size</para></listitem>
563 <listitem><para>S: largest size</para></listitem>
564 <listitem><para>t: smallest time</para></listitem>
565 <listitem><para>T: largest time</para></listitem>
566 <listitem><para>b: smallest bandwidth</para></listitem>
567 <listitem><para>B: largest bandwidth</para></listitem>
574 <term><emphasis remap='B'>maxdumps</emphasis> int</term>
577 <literal>1</literal>.
578 The maximum number of backups from a single host that &A; will
579 attempt to run in parallel. See also the
580 <emphasis remap='B'>inparallel</emphasis>
583 <para>Note that this parameter may also be set in a specific
584 <emphasis remap='B'>dumptype</emphasis>
586 This value sets the default for all
587 <emphasis remap='B'>dumptype</emphasis>s
589 <emphasis remap='B'>amanda.conf</emphasis>
591 <emphasis remap='B'>dumptype</emphasis>s
597 <term><emphasis remap='B'>bumpsize</emphasis> int</term>
600 <emphasis remap='I'>10 Mbytes</emphasis>.
601 The minimum savings required to trigger an automatic
602 bump from one incremental level to the next, expressed as size.
603 If &A; determines that the next higher backup level
604 will be this much smaller than the current level,
605 it will do the next level.
606 The value of this parameter is used only if the parameter
607 <emphasis>bumppercent</emphasis> is set to 0.
610 The global setting of this parameter can be overwritten inside of a
615 <emphasis remap='B'>bumppercent</emphasis>,
616 <emphasis remap='B'>bumpmult</emphasis> and
617 <emphasis remap='B'>bumpdays</emphasis>.</para>
622 <term><emphasis remap='B'>bumppercent</emphasis> int</term>
625 <emphasis remap='I'>0 percent</emphasis>.
626 The minimum savings required to trigger an automatic
627 bump from one incremental level to the next, expressed as percentage of the
628 current size of the DLE (size of current level 0).
629 If &A; determines that the next higher backup level
630 will be this much smaller than the current level,
631 it will do the next level.
634 If this parameter is set to 0, the value of the
635 parameter <emphasis>bumpsize</emphasis> is used to trigger bumping.
638 The global setting of this parameter can be overwritten inside of a
643 <emphasis remap='B'>bumpsize</emphasis>,
644 <emphasis remap='B'>bumpmult</emphasis> and
645 <emphasis remap='B'>bumpdays</emphasis>.</para>
650 <term><emphasis remap='B'>bumpmult</emphasis> <emphasis remap='I'> float</emphasis></term>
653 <literal>1.5</literal>.
654 The bump size multiplier.
656 <emphasis remap='B'>bumpsize</emphasis>
657 by this factor for each level.
658 This prevents active filesystems from
659 bumping too much by making it harder to bump to the next level.
660 For example, with the default
661 <emphasis remap='B'>bumpsize</emphasis>
663 <emphasis remap='B'>bumpmult</emphasis>
664 set to 2.0, the bump threshold will be 10 Mbytes for level one, 20
665 Mbytes for level two, 40 Mbytes for level three, and so on.</para>
667 The global setting of this parameter can be overwritten inside of a
673 <term><emphasis remap='B'>bumpdays</emphasis> <emphasis remap='I'> int</emphasis></term>
676 <emphasis remap='I'>2 days</emphasis>.
677 To insure redundancy in the dumps, &A; keeps filesystems at the
678 same incremental level for at least
679 <emphasis remap='B'>bumpdays</emphasis>
680 days, even if the other bump threshold criteria are met.</para>
682 The global setting of this parameter can be overwritten inside of a
689 <term><emphasis remap='B'>diskfile</emphasis> <emphasis remap='I'> string</emphasis></term>
692 <emphasis remap='I'>disklist</emphasis>.
693 The file name for the
694 <emphasis remap='I'>disklist</emphasis>
695 file holding client hosts, disks and other client dumping information.</para>
699 <term><emphasis remap='B'>infofile</emphasis> <emphasis remap='I'> string</emphasis></term>
702 <filename>/usr/adm/amanda/curinfo</filename>.
703 The file or directory name for the historical information database.
704 If &A; was configured to use DBM databases, this is the base file
706 If it was configured to use text formated databases (the default),
707 this is the base directory and within here will be a directory per
708 client, then a directory per disk, then a text file of data.</para>
712 <term><emphasis remap='B'>logdir</emphasis> <emphasis remap='I'> string</emphasis></term>
715 <filename>/usr/adm/amanda</filename>.
716 The directory for the
717 <command>amdump</command>
719 <emphasis remap='B'>log</emphasis>
724 <term><emphasis remap='B'>indexdir</emphasis> <emphasis remap='I'> string</emphasis></term>
727 <filename>/usr/adm/amanda/index</filename>.
728 The directory where index files (backup image catalogues) are stored.
730 only generated for filesystems whose
731 <emphasis remap='B'>dumptype</emphasis>
733 <emphasis remap='B'>index</emphasis>
734 option enabled.</para>
738 <term><emphasis remap='B'>tapelist</emphasis> <emphasis remap='I'> string</emphasis></term>
741 <emphasis remap='I'>tapelist</emphasis>.
742 The file name for the active
743 <emphasis remap='I'>tapelist</emphasis>
745 &A; maintains this file with information about the active set of tapes.</para>
749 <term><emphasis remap='B'>tapebufs</emphasis> <emphasis remap='I'> int</emphasis></term>
752 <literal>20</literal>.
753 The number of buffers used by the
754 <emphasis remap='B'>taper</emphasis>
756 <command>amdump</command>
758 <emphasis remap='B'>amflush</emphasis>
759 to hold data as it is read from the network or disk before it is written to tape.
760 Each buffer is a little larger than 32 KBytes and is held in a shared memory region.</para>
764 <term><emphasis remap='B'>reserve</emphasis> <emphasis remap='I'> number</emphasis></term>
767 <literal>100</literal>.
768 The part of holding-disk space that should be reserved for incremental
769 backups if no tape is available, expressed as a percentage of the
770 available holding-disk space (0-100).
771 By default, when there is no tape to write to, degraded mode (incremental) backups
772 will be performed to the holding disk. If full backups should also be allowed in this case,
773 the amount of holding disk space reserved for incrementals should be lowered.</para>
777 <term><emphasis remap='B'>autoflush</emphasis> <emphasis remap='I'> bool</emphasis></term>
780 <emphasis remap='I'>off</emphasis>.
781 Whether an amdump run will flush the dumps from holding disk to tape.</para>
785 <term><emphasis remap='B'>amrecover_do_fsf</emphasis> <emphasis remap='I'> bool</emphasis></term>
788 <emphasis remap='I'>on</emphasis>.
789 Amrecover will call amrestore with the -f flag for faster positioning of the tape.</para>
793 <term><emphasis remap='B'>amrecover_check_label</emphasis> <emphasis remap='I'> bool</emphasis></term>
796 <emphasis remap='I'>on</emphasis>.
797 Amrecover will call amrestore with the -l flag to check the label.</para>
801 <term><emphasis remap='B'>amrecover_changer</emphasis> <emphasis remap='I'> string</emphasis></term>
804 Amrecover will use the changer if you use 'settape <string>' and that string
805 is the same as the amrecover_changer setting.</para>
809 <term><emphasis remap='B'>columnspec</emphasis> <emphasis remap='I'> string</emphasis></term>
811 <para>Defines the width of columns <emphasis remap='B'>amreport</emphasis>
813 <emphasis remap='I'>String</emphasis>
814 is a comma (',') separated list of triples. Each triple consists
815 of three parts which are separated by a equal sign ('=') and a colon (':') (see the example).
816 These three parts specify:</para>
820 <para>the name of the column, which may be:</para>
823 <listitem><para>Compress (compression ratio)</para></listitem>
824 <listitem><para>Disk (client disk name)</para></listitem>
825 <listitem><para>DumpRate (dump rate in KBytes/sec)</para></listitem>
826 <listitem><para>DumpTime (total dump time in hours:minutes)</para></listitem>
827 <listitem><para>HostName (client host name)</para></listitem>
828 <listitem><para>Level (dump level)</para></listitem>
829 <listitem><para>OrigKB (original image size in KBytes)</para></listitem>
830 <listitem><para>OutKB (output image size in KBytes)</para></listitem>
831 <listitem><para>TapeRate (tape writing rate in KBytes/sec)</para></listitem>
832 <listitem><para>TapeTime (total tape time in hours:minutes)</para></listitem>
838 <para>the amount of space to display before the column (used to get whitespace between columns).</para>
841 <para>the width of the column itself.
842 If set to a negative value, the width will be calculated on demand to fit the largest entry in
847 <para>Here is an example:</para>
850 <para>columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"</para>
852 The above will display the disk information in 18 characters
853 and put one space before it. The hostname column will be 10 characters wide with
854 no space to the left. The output KBytes column is seven characters wide
855 with one space before it.
860 <term><emphasis remap='B'>includefile</emphasis> <emphasis remap='I'> string</emphasis></term>
863 <emphasis remap='I'>none</emphasis>.
864 The name of an &A; configuration file to include within the current file.
865 Useful for sharing dumptypes, tapetypes and interface definitions among several configurations.</para>
872 <refsect1><title>HOLDINGDISK SECTION</title>
873 <para>The <emphasis remap='B'>amanda.conf</emphasis>
874 file may define one or more holding disks used as buffers to hold
875 backup images before they are written to tape.
876 The syntax is:</para>
879 holdingdisk <emphasis remap='I'>name</emphasis> {
880 <emphasis remap='I'>holdingdisk-option</emphasis> <emphasis remap='I'>holdingdisk-value</emphasis>
881 <literal>...</literal>
885 <para><emphasis remap='I'>Name</emphasis>
886 is a logical name for this holding disk.</para>
888 <para>The options and values are:</para>
890 <variablelist remap='TP'>
892 <term><emphasis remap='B'>comment</emphasis> <emphasis remap='I'> string</emphasis></term>
895 <emphasis remap='I'>none</emphasis>.
896 A comment string describing this holding disk.</para>
900 <term><emphasis remap='B'>directory</emphasis> <emphasis remap='I'> disk</emphasis></term>
903 <filename>/dumps/amanda</filename>.
904 The path to this holding area.</para>
908 <term><emphasis remap='B'>use</emphasis> <emphasis remap='I'> int</emphasis></term>
911 <emphasis remap='I'>0 Gb</emphasis>.
912 Amount of space that can be used in this holding disk area.
913 If the value is zero, all available space on the file system is used.
914 If the value is negative, &A; will use all available space minus that value.
918 <term><emphasis remap='B'>chunksize</emphasis> <emphasis remap='I'> int</emphasis></term>
921 <emphasis remap='I'>1 Gb</emphasis>.
922 Holding disk chunk size. Dumps larger than the specified size will be stored in multiple
923 holding disk files. The size of each chunk will not exceed the specified value.
924 However, even though dump images are split in the holding disk, they are concatenated as
925 they are written to tape, so each dump image still corresponds to a single continuous
928 If 0 is specified, &A; will create holding disk chunks as large as
929 ((INT_MAX/1024)-64) Kbytes.
931 Each holding disk chunk includes a 32 Kbyte header, so the minimum
932 chunk size is 64 Kbytes (but that would be really silly).
934 Operating systems that are limited to a maximum file size of 2 Gbytes
935 actually cannot handle files that large.
936 They must be at least one byte less than 2 Gbytes.
937 Since &A; works with 32 Kbyte blocks, and
938 to handle the final read at the end of the chunk, the chunk size
939 should be at least 64 Kbytes (2 * 32 Kbytes) smaller than the maximum
940 file size, e.g. 2047 Mbytes.
946 <refsect1><title>DUMPTYPE SECTION</title>
947 <para>The &amconf; file may define multiple sets of backup options
948 and refer to them by name from the &disklist; file.
949 For instance, one set of options might be defined for file systems
950 that can benefit from high compression, another set that does not compress well,
951 another set for file systems that should always get a full backup and so on.</para>
953 <para>A set of backup options are entered in a
954 <emphasis remap='B'>dumptype</emphasis>
955 section, which looks like this:</para>
958 define dumptype <emphasis remap='I'>name</emphasis> {
959 <emphasis remap='I'>dumptype-option</emphasis> <emphasis remap='I'>dumptype-value</emphasis>
960 <literal>...</literal>
964 <para><emphasis remap='I'>Name</emphasis>
965 is the name of this set of backup options.
966 It is referenced from the &disklist; file.</para>
968 <para>Some of the options in a
969 <emphasis remap='B'>dumptype</emphasis>
970 section are the same as those in the main part of &amconf;.
971 The main option value is used to set the default for all
972 <emphasis remap='B'>dumptype</emphasis>
973 sections. For instance, setting
974 <emphasis remap='B'>dumpcycle</emphasis>
975 to 50 in the main part of the config file causes all following
976 <emphasis remap='B'>dumptype</emphasis>
977 sections to start with that value,
978 but the value may be changed on a section by section basis.
979 Changes to variables in the main part of the config file must be
980 done before (earlier in the file) any
981 <emphasis remap='B'>dumptype</emphasis>s
984 <para>The dumptype options and values are:</para>
986 <variablelist remap='TP'>
988 <term><emphasis remap='B'>auth</emphasis> <emphasis remap='I'> string</emphasis></term>
991 <emphasis remap='I'>bsd</emphasis>.
992 Type of authorization to perform between tape server and backup client hosts.</para>
993 <para><emphasis remap='B'>bsd</emphasis>, bsd authorization with udp initial
994 connection and one tcp connection by data stream.</para>
995 <para><emphasis remap='B'>bsdtcp</emphasis>, bsd authorization but use only
996 one tcp connection.</para>
997 <para><emphasis remap='B'>bsdudp</emphasis>, like bsd, but will use only one
998 tcp connection for all data stream.</para>
999 <para><emphasis remap='B'>krb4</emphasis> to use Kerberos-IV
1000 authorization.</para>
1001 <para><emphasis remap='B'>krb5</emphasis> to use Kerberos-V
1002 authorization.</para>
1003 <para><emphasis remap='B'>rsh</emphasis> to use rsh
1004 authorization.</para>
1005 <para><emphasis remap='B'>ssh</emphasis> to use OpenSSH
1006 authorization.</para>
1012 <term><emphasis remap='B'>amandad_path</emphasis> <emphasis remap='I'> string</emphasis></term>
1015 <emphasis remap='I'>$libexec/amandad</emphasis>.
1016 Specify the amandad path of the client, only use with rsh/ssh authentification.
1022 <term><emphasis remap='B'>client_username</emphasis> <emphasis remap='I'> string</emphasis></term>
1025 <emphasis remap='I'>CLIENT_LOGIN</emphasis>.
1026 Specify the username to connect on the client, only use with rsh/ssh authentification.
1031 <!-- bumping parameters yanked from the global section above -->
1034 <term><emphasis remap='B'>bumpsize</emphasis> int</term>
1037 <emphasis remap='I'>10 Mbytes</emphasis>.
1038 The minimum savings required to trigger an automatic
1039 bump from one incremental level to the next, expressed as size.
1040 If &A; determines that the next higher backup level
1041 will be this much smaller than the current level,
1042 it will do the next level.
1043 The value of this parameter is used only if the parameter
1044 <emphasis>bumppercent</emphasis> is set to 0.
1047 See also the options
1048 <emphasis remap='B'>bumppercent</emphasis>,
1049 <emphasis remap='B'>bumpmult</emphasis> and
1050 <emphasis remap='B'>bumpdays</emphasis>.</para>
1055 <term><emphasis remap='B'>bumppercent</emphasis> int</term>
1058 <emphasis remap='I'>0 percent</emphasis>.
1059 The minimum savings required to trigger an automatic
1060 bump from one incremental level to the next, expressed as percentage of the
1061 current size of the DLE (size of current level 0).
1062 If &A; determines that the next higher backup level
1063 will be this much smaller than the current level,
1064 it will do the next level.
1067 If this parameter is set to 0, the value of the
1068 parameter <emphasis>bumpsize</emphasis> is used to trigger bumping.
1071 See also the options
1072 <emphasis remap='B'>bumpsize</emphasis>,
1073 <emphasis remap='B'>bumpmult</emphasis> and
1074 <emphasis remap='B'>bumpdays</emphasis>.</para>
1079 <term><emphasis remap='B'>bumpmult</emphasis> <emphasis remap='I'> float</emphasis></term>
1082 <literal>1.5</literal>.
1083 The bump size multiplier.
1085 <emphasis remap='B'>bumpsize</emphasis>
1086 by this factor for each level.
1087 This prevents active filesystems from
1088 bumping too much by making it harder to bump to the next level.
1089 For example, with the default
1090 <emphasis remap='B'>bumpsize</emphasis>
1092 <emphasis remap='B'>bumpmult</emphasis>
1093 set to 2.0, the bump threshold will be 10 Mbytes for level one, 20
1094 Mbytes for level two, 40 Mbytes for level three, and so on.</para>
1098 <term><emphasis remap='B'>bumpdays</emphasis> <emphasis remap='I'> int</emphasis></term>
1101 <emphasis remap='I'>2 days</emphasis>.
1102 To insure redundancy in the dumps, &A; keeps filesystems at the
1103 same incremental level for at least
1104 <emphasis remap='B'>bumpdays</emphasis>
1105 days, even if the other bump threshold criteria are met.</para>
1110 <term><emphasis remap='B'>comment</emphasis> <emphasis remap='I'> string</emphasis></term>
1113 <emphasis remap='I'>none</emphasis>.
1114 A comment string describing this set of backup options.</para>
1118 <term><emphasis remap='B'>comprate</emphasis> <emphasis remap='I'>float</emphasis> [, <emphasis remap='I'>float</emphasis> ]</term>
1121 <literal>0.50</literal>,
1122 <literal>0.50</literal>.
1123 The expected full and incremental compression factor for dumps.
1124 It is only used if &A; does not have any history information on
1125 compression rates for a filesystem, so should not usually need to be set.
1126 However, it may be useful for the first time a very large filesystem that
1127 compresses very little is backed up.</para>
1131 <term><emphasis remap='B'>compress [client|server]</emphasis> <emphasis remap='I'> string</emphasis></term>
1134 <emphasis remap='I'>client fast</emphasis>.
1135 If &A; does compression of the backup images, it can do so either on the backup client
1136 host before it crosses the network or on the tape server host as it goes from the
1137 network into the holding disk or to tape. Which place to do compression (if at all) depends on how well the
1138 dump image usually compresses, the speed and load on the client or server, network capacity,
1139 holding disk capacity, availability of tape hardware compression, etc.</para>
1141 <para>For either type of compression, &A; also allows the selection
1142 of three styles of compression.
1143 <emphasis remap='B'>Best</emphasis>
1144 is the best compression available, often at the expense of CPU overhead.
1145 <emphasis remap='B'>Fast</emphasis>
1146 is often not as good a compression as
1147 <emphasis remap='B'>best</emphasis>,
1148 but usually less CPU overhead. Or to specify <emphasis remap='B'>Custom</emphasis>
1149 to use your own compression method. (See dumptype custom-compress in example/amanda.conf for reference)</para>
1153 <para>So the <emphasis remap='B'>compress</emphasis> options line may be one of:</para>
1156 <listitem><para>compress none</para></listitem>
1157 <listitem><para>compress [client] fast</para></listitem>
1158 <listitem><para>compress [client] best</para></listitem>
1159 <listitem><para>compress client custom</para>
1160 <para>Specify client_custom_compress "PROG"</para>
1161 <para>PROG must not contain white space and it must accept -d for uncompress.</para></listitem>
1162 <listitem><para>compress server fast</para></listitem>
1163 <listitem><para>compress server best</para></listitem>
1164 <listitem><para>compress server custom</para>
1165 <para>Specify server_custom_compress "PROG"</para>
1166 <para>PROG must not contain white space and it must accept -d for uncompress.</para></listitem>
1169 <para>Note that some tape devices do compression and this option has nothing
1170 to do with whether that is used. If hardware compression is used (usually via a particular tape device name
1171 or <emphasis remap='B'>mt</emphasis> option), &A; (software) compression should be disabled.</para>
1175 <term><emphasis remap='B'>dumpcycle</emphasis> <emphasis remap='I'> int</emphasis></term>
1177 <para>Default: <emphasis remap='I'>10 days</emphasis>.
1178 The number of days in the backup cycle. Each disk using this set of options will get a full
1179 backup at least this of
1180 ten. Setting this to zero tries to do a full backup each run.</para>
1185 <term><emphasis remap='B'>encrypt [none|client|server]</emphasis></term>
1187 <para>Default: <emphasis remap='I'>none</emphasis>.
1188 To encrypt backup images, it can do so either on the backup client host before it crosses the network or on the tape
1189 server host as it goes from the network into the holding disk or to tape.</para>
1191 <para>So the <emphasis remap='B'>encrypt</emphasis> options line may be one
1195 <listitem><para>encrypt none</para></listitem>
1196 <listitem><para>encrypt client</para>
1197 <para>Specify client_encrypt "PROG"</para>
1198 <para>PROG must not contain white space.</para>
1199 <para>Specify client_decrypt_option "decryption-parameter" Default: "-d"</para>
1200 <para>decryption-parameter must not contain white space.</para>
1201 <para>(See dumptype server-encrypt-fast in example/amanda.conf for reference)</para>
1203 <listitem><para>encrypt server</para>
1204 <para>Specify server_encrypt "PROG"</para>
1205 <para>PROG must not contain white space.</para>
1206 <para>Specify server_decrypt_option "decryption-parameter" Default: "-d"</para>
1207 <para>decryption-parameter must not contain white space.</para>
1208 <para>(See dumptype client-encrypt-nocomp in example/amanda.conf for reference)</para>
1212 <para>Note that current logic assumes compression then encryption during
1213 backup(thus decrypt then uncompress during restore). So specifying
1214 client-encryption AND server-compression is not supported.
1215 <emphasis remap='I'>amcrypt</emphasis> which is a wrapper of
1216 <emphasis remap='I'>aespipe</emphasis> is provided as a reference
1217 symmetric encryption program.</para>
1222 <term><emphasis remap='B'>estimate</emphasis> <emphasis remap='I'>client|calcsize|server</emphasis></term>
1224 <para>Default: <emphasis remap='I'>client</emphasis>.
1225 Determine the way &A; does it's estimate.</para>
1228 <para>client:</para>
1230 Use the same program as the dumping program, this is the most accurate way to do estimates, but it can take a long time.
1234 <para>calcsize:</para>
1235 <para>Use a faster program to do estimates, but the result is less accurate.</para>
1238 <para>server:</para>
1239 <para>Use only statistics from the previous run to give an estimate,
1240 it takes only a few seconds but the result is not accurate if your disk
1241 usage changes from day to day.
1250 <term><emphasis remap='B'>exclude</emphasis> [ <emphasis remap='I'>list|file</emphasis> ][[optional][ <emphasis remap='I'>append</emphasis> ][ <emphasis remap='I'> string</emphasis> ]+]</term>
1253 <emphasis remap='I'>file</emphasis>.
1254 There are two exclude lists,
1255 <emphasis remap='B'>exclude file</emphasis>
1257 <emphasis remap='B'>exclude list.</emphasis>
1259 <emphasis remap='B'>exclude file</emphasis>
1261 <emphasis remap='I'>string</emphasis>
1262 is a &gnutar; exclude expression. With
1263 <emphasis remap='B'>exclude list</emphasis>
1265 <emphasis remap='I'>string</emphasis>
1266 is a file name on the client containing &gnutar; exclude expressions.
1267 The path to the specified exclude list file, if present (see description of
1268 'optional' below), must be readable by the &A; user.</para>
1270 <para>All exclude expressions are concatenated in one file and passed to &gnutar;
1271 as an <option>--exclude-from</option> argument.</para>
1273 <para>Exclude expressions must always be specified as relative to the
1274 head directory of the DLE.</para>
1277 <emphasis remap='B'>append</emphasis> keyword, the
1278 <emphasis remap='I'>string</emphasis> is appended to the current list, without it, the
1279 <emphasis remap='I'>string</emphasis> overwrites the list.</para>
1281 <para>If <emphasis remap='B'>optional</emphasis>
1282 is specified for <emphasis remap='B'>exclude list</emphasis>,
1283 then amcheck will not complain if the file doesn't exist or is not readable.</para>
1285 <para>For <emphasis remap='B'>exclude list</emphasis>,
1286 if the file name is relative, the disk name being backed up is prepended.
1287 So if this is entered:</para>
1290 exclude list ".amanda.excludes"
1293 <para>the actual file used would be
1294 <filename>/var/.amanda.excludes</filename>
1295 for a backup of <filename>/var</filename>,
1296 <filename>/usr/local/.amanda.excludes</filename> for a backup of
1297 <filename>/usr/local</filename>, and so on.</para>
1302 <term><emphasis remap='B'>holdingdisk</emphasis> [ <emphasis remap='I'>never|auto|required]</emphasis> ]</term>
1305 <emphasis remap='I'>auto</emphasis>.
1306 Whether a holding disk should be used for these backups or whether they should go directly to tape.
1307 If the holding disk is a portion of another file system that &A;
1308 is backing up, that file system should refer to a dumptype with
1309 <emphasis remap='B'>holdingdisk</emphasis>
1311 <emphasis remap='I'>never</emphasis>
1312 to avoid backing up the holding disk into itself.</para>
1314 <variablelist remap='TP'>
1316 <term><emphasis remap='B'>never</emphasis>|no|false|off</term>
1318 <para>Never use a holdingdisk, the dump will always go directly to tape. There will be no dump if you have a tape error.</para>
1322 <term><emphasis remap='B'>auto</emphasis>|yes|true|on</term>
1324 <para>Use the holding disk, unless there is a problem with the holding disk, the dump won't fit there or the medium doesn't require spooling (e.g., VFS device)</para>
1328 <term><emphasis remap='B'>required</emphasis></term>
1330 <para>Always dump to holdingdisk, never directly to tape. There will be no dump if it doesn't fit on holdingdisk</para>
1339 <term><emphasis remap='B'>ignore</emphasis> <emphasis remap='I'> boolean</emphasis></term>
1342 <emphasis remap='I'>no</emphasis>.
1343 Whether disks associated with this backup type should be backed up or not.
1344 This option is useful when the
1345 <emphasis remap='I'>disklist</emphasis>
1346 file is shared among several configurations,
1347 some of which should not back up all the listed file systems.</para>
1351 <term><emphasis remap='B'>include</emphasis> [ <emphasis remap='I'>list|file</emphasis> ][[optional][ <emphasis remap='I'>append</emphasis> ][ <emphasis remap='I'> string</emphasis> ]+]</term>
1354 <emphasis remap='I'>file</emphasis>
1356 There are two include lists,
1357 <emphasis remap='B'>include file</emphasis>
1359 <emphasis remap='B'>include list.</emphasis>
1361 <emphasis remap='B'>include file</emphasis>
1363 <emphasis remap='I'>string</emphasis>
1364 is a glob expression. With
1365 <emphasis remap='B'>include list</emphasis>
1367 <emphasis remap='I'>string</emphasis>
1368 is a file name on the client containing glob expressions.</para>
1370 <para>All include expressions are expanded by &A;, concatenated in one file and passed to &gnutar; as a
1371 <option>--files-from</option> argument. They must start with "./" and contain no other "/".</para>
1373 <para>Include expressions must always be specified as relative to the
1374 head directory of the DLE.</para>
1376 <note>For globbing to work at all, even the limited single level,
1377 the top level directory of the DLE must be readable by the &A; user.</note>
1379 <para>With the <emphasis remap='B'>append</emphasis> keyword, the
1380 <emphasis remap='I'>string</emphasis> is appended to the current list, without it, the
1381 <emphasis remap='I'>string</emphasis> overwrites the list.</para>
1384 <emphasis remap='B'>optional</emphasis> is specified for
1385 <emphasis remap='B'>include list,</emphasis> then amcheck will not complain if the file
1386 doesn't exist or is not readable.</para>
1388 <para>For <emphasis remap='B'>include list</emphasis>,
1389 If the file name is relative, the disk name being backed up is prepended.</para>
1394 <term><emphasis remap='B'>index</emphasis> <emphasis remap='I'> boolean</emphasis></term>
1396 <para>Default: <emphasis remap='I'>no</emphasis>.
1397 Whether an index (catalogue) of the backup should be generated and saved in
1398 <emphasis remap='B'>indexdir</emphasis>.
1399 These catalogues are used by the <emphasis remap='B'>amrecover</emphasis> utility.</para>
1404 <term><emphasis remap='B'>kencrypt</emphasis> <emphasis remap='I'> boolean</emphasis></term>
1407 <emphasis remap='I'>no</emphasis>.
1408 Whether the backup image should be encrypted by Kerberos as it is sent
1409 across the network from the backup client host to the tape server host.</para>
1413 <term><emphasis remap='B'>maxdumps</emphasis> <emphasis remap='I'> int</emphasis></term>
1416 <literal>1</literal>.
1417 The maximum number of backups from a single host that &A; will attempt to run in parallel.
1418 See also the main section parameter <emphasis remap='B'>inparallel</emphasis>.</para>
1422 <term><emphasis remap='B'>maxpromoteday</emphasis> <emphasis remap='I'> int</emphasis></term>
1425 <literal>10000</literal>.
1426 The maximum number of day for a promotion, set it 0 if you don't want
1427 promotion, set it to 1 or 2 if your disks get overpromoted.</para>
1431 <term><emphasis remap='B'>priority</emphasis> <emphasis remap='I'> string</emphasis></term>
1433 <para>Default: <emphasis remap='I'>medium</emphasis>.
1434 When there is no tape to write to, &A; will do incremental backups
1435 in priority order to the holding disk. The priority may be
1436 high (2), medium (1), low (0) or a number of your choice.</para>
1440 <term><emphasis remap='B'>program</emphasis> <emphasis remap='I'> string</emphasis></term>
1443 <emphasis remap='I'>DUMP</emphasis>.
1444 The type of backup to perform. Valid values are
1445 <emphasis remap='B'>DUMP</emphasis>
1446 for the native operating system backup program, and
1447 <emphasis remap='B'>GNUTAR</emphasis>
1448 to use &gnutar; or to do PC backups using Samba.</para>
1452 <term><emphasis remap='B'>record</emphasis> <emphasis remap='I'> boolean</emphasis></term>
1455 <emphasis remap='I'>yes</emphasis>.
1456 Whether to ask the backup program to update its database (e.g. <filename>/etc/dumpdates</filename>
1457 for DUMP or <filename>/usr/local/var/amanda/gnutar-lists</filename> for GNUTAR) of time stamps.
1458 This is normally enabled for daily backups and turned off for periodic archival runs.</para>
1462 <term><emphasis remap='B'>skip-full</emphasis> <emphasis remap='I'> boolean</emphasis></term>
1465 <emphasis remap='I'>no</emphasis>. If <emphasis remap='I'>true</emphasis> and
1466 <emphasis remap='B'>planner</emphasis> has scheduled a full backup, these disks will be skipped, and
1467 full backups should be run off-line on these days. It was reported that &A; only schedules
1468 level 1 incrementals in this configuration; this is probably a bug.</para>
1472 <term><emphasis remap='B'>skip-incr</emphasis> <emphasis remap='I'> boolean</emphasis></term>
1475 <emphasis remap='I'>no</emphasis>. If <emphasis remap='I'>true</emphasis> and
1476 <emphasis remap='B'>planner</emphasis> has scheduled an incremental backup, these disks will be skipped.</para>
1480 <term><emphasis remap='B'>starttime</emphasis> <emphasis remap='I'> int</emphasis></term>
1483 <emphasis remap='I'>none</emphasis>.
1484 Backups will not start until after this time of day.
1485 The value should be hh*100+mm, e.g. 6:30PM (18:30) would be entered as
1486 <literal>1830</literal>.</para>
1490 <term><emphasis remap='B'>strategy</emphasis> <emphasis remap='I'> string</emphasis></term>
1492 <para>Default: <emphasis remap='I'>standard</emphasis>.
1493 Strategy to use when planning what level of backup to run next. Values are:</para>
1495 <variablelist remap='TP'>
1497 <term><emphasis remap='B'>standard</emphasis></term>
1499 <para>The standard &A; schedule.</para>
1503 <term><emphasis remap='B'>nofull</emphasis></term>
1505 <para>Never do full backups, only level 1 incrementals.</para>
1509 <term><emphasis remap='B'>noinc</emphasis></term>
1511 <para>Never do incremental backups, only full dumps.</para>
1515 <term><emphasis remap='B'>skip</emphasis></term>
1517 <para>Never do backups (useful when sharing the <emphasis remap='I'>disklist</emphasis> file).</para>
1521 <term><emphasis remap='B'>incronly</emphasis></term>
1523 <para>Only do incremental dumps. <command>amadmin force</command> should be used to tell
1524 &A; that a full dump has been performed off-line, so that it resets to level 1.
1525 It is similar to skip-full, but with incronly full dumps may be scheduled manually.
1526 Unfortunately, it appears that &A; will perform full backups with this configuration,
1527 which is probably a bug.</para>
1535 <term><emphasis remap='B'>tape_splitsize</emphasis> <emphasis remap='I'> int</emphasis></term>
1538 <emphasis remap='I'>none</emphasis>.
1539 Split dump file on tape into pieces of a specified size.
1540 This allows dumps to be spread across multiple tapes, and can potentially
1541 make more efficient use of tape space.
1542 Note that if this value is too large (more than half the size of the
1543 average dump being split), substantial tape space can be wasted.
1544 If too small, large dumps will be split into innumerable tiny dumpfiles,
1545 adding to restoration complexity.
1546 A good rule of thumb, usually, is 1/10 of the size of your tape.</para>
1551 <term><emphasis remap='B'>split_diskbuffer</emphasis> <emphasis remap='I'> string</emphasis></term>
1554 <emphasis remap='I'>none</emphasis>.
1555 When dumping a split dump in PORT-WRITE mode (usually meaning "no holding disk"), buffer the split chunks to a file in the directory specified by this option.
1561 <term><emphasis remap='B'>fallback_splitsize</emphasis> <emphasis remap='I'> int</emphasis></term>
1564 <emphasis remap='I'>10M</emphasis>.
1565 When dumping a split dump in PORT-WRITE mode, if no split_diskbuffer is
1566 specified (or if we somehow fail to use our split_diskbuffer), we must
1567 buffer split chunks in memory.
1568 This specifies the maximum size split chunks can be in this scenario,
1569 and thus the maximum amount of memory consumed for in-memory splitting.
1570 The size of this buffer can be changed from its (very conservative) default
1571 to a value reflecting the amount of memory that each taper process on
1572 the dump server may reasonably consume.
1578 <para>The following <emphasis remap='B'>dumptype</emphasis> entries are predefined by &A;:</para>
1580 <programlisting remap='.nf'>
1581 define dumptype no-compress {
1584 define dumptype compress-fast {
1585 compress client fast
1587 define dumptype compress-best {
1588 compress client best
1590 define dumptype srvcompress {
1591 compress server fast
1593 define dumptype bsd-auth {
1596 define dumptype krb4-auth {
1599 define dumptype no-record {
1602 define dumptype no-hold {
1605 define dumptype no-full {
1610 <para>In addition to options in a
1611 <emphasis remap='B'>dumptype</emphasis>
1612 section, one or more other
1613 <emphasis remap='B'>dumptype</emphasis>
1614 names may be entered, which make this
1615 <emphasis remap='B'>dumptype</emphasis>
1616 inherit options from other previously defined
1617 <emphasis remap='B'>dumptype</emphasis>s.
1618 For instance, two sections might be the same except for the
1619 <emphasis remap='B'>record</emphasis> option:</para>
1621 <programlisting remap='.nf'>
1622 define dumptype normal {
1623 comment "Normal backup, no compression, do indexing"
1628 define dumptype testing {
1629 comment "Test backup, no compression, do indexing, no recording"
1635 <para>&A; provides a
1636 <emphasis remap='B'>dumptype</emphasis>
1638 <emphasis remap='I'>global</emphasis>
1640 <emphasis remap='B'>amanda.conf</emphasis>
1642 <emphasis remap='B'>dumptype</emphasis>s
1644 This provides an easy place to make changes that will affect every
1645 <emphasis remap='B'>dumptype</emphasis>.</para>
1648 <refsect1><title>TAPETYPE SECTION</title>
1649 <para>The <emphasis remap='B'>amanda.conf</emphasis>
1650 file may define multiple types of tape media and devices.
1651 The information is entered in a
1652 <emphasis remap='B'>tapetype</emphasis>
1653 section, which looks like this in the config file:</para>
1656 define tapetype <emphasis remap='I'>name</emphasis> {
1657 <emphasis remap='I'>tapetype-option</emphasis> <emphasis remap='I'>tapetype-value</emphasis>
1658 <literal>...</literal>
1662 <para><emphasis remap='I'>Name</emphasis>
1663 is the name of this type of tape medium/device.
1664 It is referenced from the
1665 <emphasis remap='B'>tapetype</emphasis>
1666 option in the main part of the config file.</para>
1668 <para>The tapetype options and values are:</para>
1669 <variablelist remap='TP'>
1671 <term><emphasis remap='B'>comment</emphasis> <emphasis remap='I'> string</emphasis></term>
1674 <emphasis remap='I'>none</emphasis>.
1675 A comment string describing this set of tape information.</para>
1679 <term><emphasis remap='B'>filemark</emphasis> <emphasis remap='I'> int</emphasis></term>
1682 <emphasis remap='I'>1000 bytes</emphasis>.
1683 How large a file mark (tape mark) is, measured in bytes.
1684 If the size is only known in some linear measurement (e.g. inches),
1685 convert it to bytes using the device density.</para>
1689 <term><emphasis remap='B'>length</emphasis> <emphasis remap='I'> int</emphasis></term>
1692 <emphasis remap='I'>2000 kbytes</emphasis>. How much data will fit on a tape.</para>
1694 <para>Note that this value is only used by &A; to schedule which backups will be run.
1695 Once the backups start, &A; will continue to write to a tape until it gets an error,
1696 regardless of what value is entered for <emphasis remap='B'>length</emphasis>
1697 (but see the section OUTPUT DRIVERS in the
1698 <citerefentry><refentrytitle>amanda</refentrytitle><manvolnum>8</manvolnum></citerefentry>
1699 manpage for exceptions).
1704 <term><emphasis remap='B'>blocksize</emphasis> <emphasis remap='I'> int</emphasis></term>
1707 <emphasis remap='I'>32</emphasis>.
1708 How much data will be written in each tape record expressed in KiloBytes.
1709 The tape record size (= blocksize) can not be reduced below the default 32 KBytes.
1710 The parameter blocksize can only be raised if &A; was compiled with the configure option
1711 --with-maxtapeblocksize=N set with "N" greater than 32 during
1717 <term><emphasis remap='B'>file-pad</emphasis> <emphasis remap='I'> boolean</emphasis></term>
1720 <emphasis remap='I'>true</emphasis>.
1721 If true, every record, including the last one in the file, will have the same length.
1722 This matches the way &A; wrote tapes prior to the availability of this parameter.
1723 It may also be useful on devices that only support a fixed blocksize.</para>
1725 <para>Note that the last record on the tape probably includes trailing
1726 null byte padding, which will be passed back to
1727 <emphasis remap='B'>gzip</emphasis>,
1728 <emphasis remap='B'>compress</emphasis>
1729 or the restore program. Most programs just ignore this (although possibly with a warning).</para>
1731 <para>If this parameter is false, the last record in a file may be shorter
1732 than the block size. The file will contain the same amount of data the dump program generated,
1733 without trailing null byte padding. When read, the same amount of data that was written
1734 will be returned.</para>
1739 <term><emphasis remap='B'>speed</emphasis> <emphasis remap='I'> int</emphasis></term>
1742 <emphasis remap='I'>200 bps</emphasis>.
1743 How fast the drive will accept data, in bytes per second.
1744 This parameter is NOT currently used by &A;.</para>
1748 <term><emphasis remap='B'>lbl-templ</emphasis> <emphasis remap='I'> string</emphasis></term>
1750 <para>A PostScript template file used by
1751 <emphasis remap='B'>amreport</emphasis>
1752 to generate labels. Several sample files are provided with the &A; sources in the
1753 <emphasis remap='I'>example</emphasis> directory.
1755 <citerefentry><refentrytitle>amreport</refentrytitle><manvolnum>8</manvolnum></citerefentry>
1756 man page for more information.</para>
1761 <para>In addition to options, another
1762 <emphasis remap='B'>tapetype</emphasis>
1763 name may be entered, which makes this
1764 <emphasis remap='B'>tapetype</emphasis>
1765 inherit options from another
1766 <emphasis remap='B'>tapetype</emphasis>.
1767 For instance, the only difference between a DLT4000 tape drive using
1768 Compact-III tapes and one using Compact-IV tapes is the length of the tape.
1769 So they could be entered as:</para>
1771 <programlisting remap='.nf'>
1772 define tapetype DLT4000-III {
1773 comment "DLT4000 tape drives with Compact-III tapes"
1774 length 12500 mbytes # 10 Gig tapes with some compression
1775 filemark 2000 kbytes
1778 define tapetype DLT4000-IV {
1780 comment "DLT4000 tape drives with Compact-IV tapes"
1781 length 25000 mbytes # 20 Gig tapes with some compression
1785 <!-- If anybody has read this, where do all those stupid
1786 pseudo-duplicate FOM-tapetype-entries come from??
1792 <refsect1><title>INTERFACE SECTION</title>
1794 <emphasis remap='B'>amanda.conf</emphasis>
1795 file may define multiple types of network interfaces.
1796 The information is entered in an <emphasis remap='B'>interface</emphasis>
1797 section, which looks like this:</para>
1800 define interface <emphasis remap='I'>name</emphasis> {
1801 <emphasis remap='I'>interface-option</emphasis> <emphasis remap='I'>interface-value</emphasis>
1802 <literal>...</literal>
1806 <para><emphasis remap='I'>name</emphasis>
1807 is the name of this type of network interface. It is referenced from the
1808 <emphasis remap='I'>disklist</emphasis> file.</para>
1810 <para>Note that these sections define network interface characteristics,
1811 not the actual interface that will be used. Nor do they impose limits on the bandwidth that will
1812 actually be taken up by &A;.
1813 &A; computes the estimated bandwidth each file system backup will take
1814 based on the estimated size and time, then compares that plus any other running
1815 backups with the limit as another of the criteria when deciding whether
1816 to start the backup. Once a backup starts, &A; will use as much of the network as it can
1817 leaving throttling up to the operating system and network hardware.</para>
1819 <para>The interface options and values are:</para>
1820 <variablelist remap='TP'>
1822 <term><emphasis remap='B'>comment</emphasis> <emphasis remap='I'> string</emphasis></term>
1825 <emphasis remap='I'>none</emphasis>.
1826 A comment string describing this set of network information.</para>
1830 <term><emphasis remap='B'>use</emphasis> <emphasis remap='I'> int</emphasis></term>
1833 <emphasis remap='I'>300 Kbps</emphasis>.
1834 The speed of the interface in Kbytes per second.</para>
1839 <para>In addition to options, another
1840 <emphasis remap='B'>interface</emphasis>
1841 name may be entered, which makes this
1842 <emphasis remap='B'>interface</emphasis>
1843 inherit options from another
1844 <emphasis remap='B'>interface</emphasis>.
1845 At the moment, this is of little use.</para>
1848 <refsect1><title>AUTHOR</title>
1849 <para>James da Silva, &email.jds;: Original text</para>
1850 <para>&maintainer.sgw;: XML-conversion, major update, splitting</para>
1853 <refsect1><title>SEE ALSO</title>
1855 <citerefentry><refentrytitle>amanda</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
1856 <citerefentry><refentrytitle>amanda-client.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1857 <citerefentry><refentrytitle>amcrypt</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
1858 <citerefentry><refentrytitle>aespipe</refentrytitle><manvolnum>1</manvolnum></citerefentry>,