amanda.conf
-Prev Chapter 35. The AMANDA Manual Pages. Next
+Prev Chapter 36. The Amanda Manual Pages. Next
-------------------------------------------------------------------------------
Name
-amanda.conf \14 Main configuration file for AMANDA, the Advanced Maryland
+amanda.conf \14 Main configuration file for Amanda, the Advanced Maryland
Automatic Network Disk Archiver
DESCRIPTION
-amanda.conf is the main configuration file for AMANDA. This manpage lists the
+amanda.conf is the main configuration file for Amanda. This manpage lists the
relevant sections and parameters of this file for quick reference.
PARAMETERS
There are a number of configuration parameters that control the behavior of the
-AMANDA programs. All have default values, so you need not specify the parameter
+Amanda programs. All have default values, so you need not specify the parameter
in amanda.conf if the default is suitable.
Lines starting with # are ignored, as are blank lines. Comments may be placed
on a line with a directive by starting the comment with a #. The remainder of
- org string
- Default: daily. A descriptive name for the configuration. This string
- appears in the Subject line of mail reports. Each AMANDA configuration
- should have a different string to keep mail reports distinct.
-
- mailto string
- Default: operators. A space separated list of recipients for mail
- reports.
-
- dumpcycle int
- Default: 10 days. The number of days in the backup cycle. Each disk will
- get a full backup at least this often. Setting this to zero tries to do a
- full backup each run.
-
- Note
-
- This parameter may also be set in a specific dumptype (see below). This
- value sets the default for all dumptypes so must appear in amanda.conf
- before any dumptypes are defined.
-
- runspercycle int
- Default: same as dumpcycle. The number of amdump runs in dumpcycle days.
- A value of 0 means the same value as dumpcycle. A value of -1 means guess
- the number of runs from the tapelist file, which is the number of tapes
- used in the last dumpcycle days / runtapes.
-
- tapecycle int
- Default: 15 tapes. Typically tapes are used by AMANDA in an ordered
- rotation. The tapecycle parameter defines the size of that rotation. The
- number of tapes in rotation must be larger than the number of tapes
- required for a complete dump cycle (see the dumpcycle parameter).
- This is calculated by multiplying the number of amdump runs per dump
- cycle (runspercycle parameter) times the number of tapes used per run
- (runtapes parameter). Typically two to four times this calculated number
- of tapes are in rotation. While AMANDA is always willing to use a new
- tape in its rotation, it refuses to reuse a tape until at least
- 'tapecycle -1' number of other tapes have been used.
- It is considered good administrative practice to set the tapecycle
- parameter slightly lower than the actual number of tapes in rotation.
- This allows the administrator to more easily cope with damaged or
- misplaced tapes or schedule adjustments that call for slight adjustments
- in the rotation order.
-
- dumpuser string
- Default: amanda. The login name AMANDA uses to run the backups. The
- backup client hosts must allow access from the tape server host as this
- user via .rhosts or .amandahosts, depending on how the AMANDA software
- was built.
-
- printer string
- Printer to use when doing tape labels. See the lbl-templ tapetype option.
-
- tapedev string
- Default: /dev/nst0. The path name of the non-rewinding tape device. Non-
- rewinding tape device names often have an 'n' in the name, e.g. /dev/rmt/
- 0mn, however this is operating system specific and you should consult
- that documentation for detailed naming information.
- If a tape changer is configured (see the tpchanger option), this option
- might not be used.
- If the null output driver is selected (see the section OUTPUT DRIVERS in
- the amanda(8) manpage for more information), programs such as amdump will
- run normally but all images will be thrown away. This should only be used
- for debugging and testing, and probably only with the record option set
- to no.
-
- rawtapedev string
- Default: /dev/null. The path name of the raw tape device. This is only
- used if AMANDA is compiled for Linux machines with floppy tapes and is
- needed for QIC volume table operations.
-
- tpchanger string
- Default: none. The name of the tape changer. If a tape changer is not
- configured, this option is not used and should be commented out of the
- configuration file.
- If a tape changer is configured, choose one of the changer scripts (e.g.
- chg-scsi) and enter that here.
-
- changerdev string
- Default: /dev/null. A tape changer configuration parameter. Usage depends
- on the particular changer defined with the tpchanger option.
-
- changerfile string
- Default: /usr/adm/amanda/log/changer-status. A tape changer configuration
- parameter. Usage depends on the particular changer defined with the
- tpchanger option.
-
- runtapes int
- Default: 1. The maximum number of tapes used in a single run. If a tape
- changer is not configured, this option is not used and should be
- commented out of the configuration file.
- If a tape changer is configured, this may be set larger than one to let
- AMANDA write to more than one tape.
- Note that this is an upper bound on the number of tapes, and AMANDA may
- use less.
- Also note that as of this release, AMANDA does not support true tape
- overflow. When it reaches the end of one tape, the backup image AMANDA
- was processing starts over again on the next tape.
-
- maxdumpsize int
- Default: runtapes*tape_length. Maximum number of bytes the planner will
- schedule for a run.
-
- taperalgo [first|firstfit|largest|largestfit|smallest|last]
- Default: first. The algorithm used to choose which dump image to send to
- the taper.
-
-
- first
- First in, first out.
-
- firstfit
- The first dump image that will fit on the current tape.
-
- largest
- The largest dump image.
-
- largestfit
- The largest dump image that will fit on the current tape.
-
- smallest
- The smallest dump image.
-
- last
- Last in, first out.
-
-
- labelstr string
- Default: .*. The tape label constraint regular expression. All tape
- labels generated (see amlabel(8)) and used by this configuration must
- match the regular expression. If multiple configurations are run from the
- same tape server host, it is helpful to set their labels to different
- strings (for example, "DAILY[0-9][0-9]*" vs. "ARCHIVE[0-9][0-9]*") to
- avoid overwriting each other's tapes.
-
- tapetype string
- Default: EXABYTE. The type of tape drive associated with tapedev or
- tpchanger. This refers to one of the defined tapetypes in the config file
- (see below), which specify various tape parameters, like the length,
- filemark size, and speed of the tape media and device.
-
- ctimeout int
- Default: 30 seconds. Maximum amount of time that amcheck will wait for
- each client host.
-
- dtimeout int
- Default: 1800 seconds. Amount of idle time per disk on a given client
- that a dumper running from within amdump will wait before it fails with a
- data timeout error.
-
- etimeout int
- Default: 300 seconds. Amount of time per disk on a given client that the
- planner step of amdump will wait to get the dump size estimates. For
- instance, with the default of 300 seconds and four disks on client A,
- planner will wait up to 20 minutes for that machine. A negative value
- will be interpreted as a total amount of time to wait per client instead
- of per disk.
-
- netusage int
- Default: 300 Kbps. The maximum network bandwidth allocated to AMANDA, in
- Kbytes per second. See also the interface section.
-
- inparallel int
- Default: 10. The maximum number of backups that AMANDA will attempt to
- run in parallel. AMANDA will stay within the constraints of network
- bandwidth and holding disk space available, so it doesn't hurt to set
- this number a bit high. Some contention can occur with larger numbers of
- backups, but this effect is relatively small on most systems.
-
- displayunit "k|m|g|t"
- Default: "k". The unit used to print many numbers, k=kilo, m=mega,
- g=giga, t=tera.
-
- dumporder string
- Default: tttTTTTTTT. The priority order of each dumper:
-
- * s: smallest size
- * S: largest size
- * t: smallest time
- * T: largest time
- * b: smallest bandwidth
- * B: largest bandwidth
-
-
- maxdumps int
- Default: 1. The maximum number of backups from a single host that AMANDA
- will attempt to run in parallel. See also the inparallel option.
- Note that this parameter may also be set in a specific dumptype (see
- below). This value sets the default for all dumptypes so must appear in
- amanda.conf before any dumptypes are defined.
-
- bumpsize int
- Default: 10 Mbytes. The minimum savings required to trigger an automatic
- bump from one incremental level to the next, expressed as size. If AMANDA
- determines that the next higher backup level will be this much smaller
- than the current level, it will do the next level. The value of this
- parameter is used only if the parameter bumppercent is set to 0.
- The global setting of this parameter can be overwritten inside of a
- dumptype-definition.
- See also the options bumppercent, bumpmult and bumpdays.
-
- bumppercent int
- Default: 0 percent. The minimum savings required to trigger an automatic
- bump from one incremental level to the next, expressed as percentage of
- the current size of the DLE (size of current level 0). If AMANDA
- determines that the next higher backup level will be this much smaller
- than the current level, it will do the next level.
- If this parameter is set to 0, the value of the parameter bumpsize is
- used to trigger bumping.
- The global setting of this parameter can be overwritten inside of a
- dumptype-definition.
- See also the options bumpsize, bumpmult and bumpdays.
-
- bumpmult float
- Default: 1.5. The bump size multiplier. AMANDA multiplies bumpsize by
- this factor for each level. This prevents active filesystems from bumping
- too much by making it harder to bump to the next level. For example, with
- the default bumpsize and bumpmult set to 2.0, the bump threshold will be
- 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level
- three, and so on.
- The global setting of this parameter can be overwritten inside of a
- dumptype-definition.
-
- bumpdays int
- Default: 2 days. To insure redundancy in the dumps, AMANDA keeps
- filesystems at the same incremental level for at least bumpdays days,
- even if the other bump threshold criteria are met.
- The global setting of this parameter can be overwritten inside of a
- dumptype-definition.
-
- diskfile string
- Default: disklist. The file name for the disklist file holding client
- hosts, disks and other client dumping information.
-
- infofile string
- Default: /usr/adm/amanda/curinfo. The file or directory name for the
- historical information database. If AMANDA was configured to use DBM
- databases, this is the base file name for them. If it was configured to
- use text formated databases (the default), this is the base directory and
- within here will be a directory per client, then a directory per disk,
- then a text file of data.
-
- logdir string
- Default: /usr/adm/amanda. The directory for the amdump and log files.
-
- indexdir string
- Default /usr/adm/amanda/index. The directory where index files (backup
- image catalogues) are stored. Index files are only generated for
- filesystems whose dumptype has the index option enabled.
-
- tapelist string
- Default: tapelist. The file name for the active tapelist file. AMANDA
- maintains this file with information about the active set of tapes.
-
- tapebufs int
- Default: 20. The number of buffers used by the taper process run by
- amdump and amflush to hold data as it is read from the network or disk
- before it is written to tape. Each buffer is a little larger than 32
- KBytes and is held in a shared memory region.
-
- reserve number
- Default: 100. The part of holding-disk space that should be reserved for
- incremental backups if no tape is available, expressed as a percentage of
- the available holding-disk space (0-100). By default, when there is no
- tape to write to, degraded mode (incremental) backups will be performed
- to the holding disk. If full backups should also be allowed in this case,
- the amount of holding disk space reserved for incrementals should be
- lowered.
-
- autoflush bool
- Default: off. Whether an amdump run will flush the dump already on
- holding disk to tape.
-
- amrecover_do_fsf bool
- Default: off. Amrecover will call amrestore with the -f flag for faster
- positioning of the tape.
-
- amrecover_check_label bool
- Default: off. Amrecover will call amrestore with the -l flag to check the
- label.
-
- amrecover_changer string
- Default: ''. Amrecover will use the changer if you use 'settape <string>'
- and that string is the same as the amrecover_changer setting.
-
- columnspec string
- Defines the width of columns amreport should use. String is a comma (',')
- separated list of triples. Each triple consists of three parts which are
- separated by a equal sign ('=') and a colon (':') (see the example).
- These three parts specify:
-
- * the name of the column, which may be:
-
- o Compress (compression ratio)
- o Disk (client disk name)
- o DumpRate (dump rate in KBytes/sec)
- o DumpTime (total dump time in hours:minutes)
- o HostName (client host name)
- o Level (dump level)
- o OrigKB (original image size in KBytes)
- o OutKB (output image size in KBytes)
- o TapeRate (tape writing rate in KBytes/sec)
- o TapeTime (total tape time in hours:minutes)
-
- * the amount of space to display before the column (used to get
- whitespace between columns).
- * the width of the column itself. If set to a negative value, the width
- will be calculated on demand to fit the largest entry in this column.
-
- Here is an example:
-
- columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
-
- The above will display the disk information in 18 characters and put one
- space before it. The hostname column will be 10 characters wide with no
- space to the left. The output KBytes column is seven characters wide with
- one space before it.
-
includefile string
- Default: none. The name of an AMANDA configuration file to include within
+ Default: none. The name of an Amanda configuration file to include within
the current file. Useful for sharing dumptypes, tapetypes and interface
definitions among several configurations.
use int
Default: 0 Gb. Amount of space that can be used in this holding disk
area. If the value is zero, all available space on the file system is
- used. If the value is negative, AMANDA will use all available space minus
+ used. If the value is negative, Amanda will use all available space minus
that value.
chunksize int
chunk will not exceed the specified value. However, even though dump
images are split in the holding disk, they are concatenated as they are
written to tape, so each dump image still corresponds to a single
- continuous tape section.
- If 0 is specified, AMANDA will create holding disk chunks as large as (
- (INT_MAX/1024)-64) Kbytes.
- Each holding disk chunk includes a 32 Kbyte header, so the minimum chunk
- size is 64 Kbytes (but that would be really silly).
- Operating systems that are limited to a maximum file size of 2 Gbytes
- actually cannot handle files that large. They must be at least one byte
- less than 2 Gbytes. Since AMANDA works with 32 Kbyte blocks, and to
- handle the final read at the end of the chunk, the chunk size should be
- at least 64 Kbytes (2 * 32 Kbytes) smaller than the maximum file size,
- e.g. 2047 Mbytes.
+ continuous tape section. If 0 is specified, Amanda will create holding
+ disk chunks as large as ((INT_MAX/1024)-64) Kbytes. Each holding disk
+ chunk includes a 32 Kbyte header, so the minimum chunk size is 64 Kbytes
+ (but that would be really silly). Operating systems that are limited to a
+ maximum file size of 2 Gbytes actually cannot handle files that large.
+ They must be at least one byte less than 2 Gbytes. Since Amanda works
+ with 32 Kbyte blocks, and to handle the final read at the end of the
+ chunk, the chunk size should be at least 64 Kbytes (2 * 32 Kbytes)
+ smaller than the maximum file size, e.g. 2047 Mbytes.
DUMPTYPE SECTION
auth string
Default: bsd. Type of authorization to perform between tape server and
- backup client hosts. May be krb4 to use Kerberos-IV authorization.
+ backup client hosts.
+ bsd, bsd authorization with udp initial connection and one tcp connection
+ by data stream.
+ bsdtcp, bsd authorization but use only one tcp connection.
+ bsdudp, like bsd, but will use only one tcp connection for all data
+ stream.
+ krb4 to use Kerberos-IV authorization.
+ krb5 to use Kerberos-V authorization.
+ rsh to use rsh authorization.
+ ssh to use OpenSSH authorization.
+
+ amandad_path string
+ Default: $libexec/amandad. Specify the amandad path of the client, only
+ use with rsh/ssh authentification.
+
+ client_username string
+ Default: CLIENT_LOGIN. Specify the username to connect on the client,
+ only use with rsh/ssh authentification.
bumpsize int
Default: 10 Mbytes. The minimum savings required to trigger an automatic
- bump from one incremental level to the next, expressed as size. If AMANDA
+ bump from one incremental level to the next, expressed as size. If Amanda
determines that the next higher backup level will be this much smaller
than the current level, it will do the next level. The value of this
parameter is used only if the parameter bumppercent is set to 0.
bumppercent int
Default: 0 percent. The minimum savings required to trigger an automatic
bump from one incremental level to the next, expressed as percentage of
- the current size of the DLE (size of current level 0). If AMANDA
+ the current size of the DLE (size of current level 0). If Amanda
determines that the next higher backup level will be this much smaller
than the current level, it will do the next level.
If this parameter is set to 0, the value of the parameter bumpsize is
See also the options bumpsize, bumpmult and bumpdays.
bumpmult float
- Default: 1.5. The bump size multiplier. AMANDA multiplies bumpsize by
+ Default: 1.5. The bump size multiplier. Amanda multiplies bumpsize by
this factor for each level. This prevents active filesystems from bumping
too much by making it harder to bump to the next level. For example, with
the default bumpsize and bumpmult set to 2.0, the bump threshold will be
three, and so on.
bumpdays int
- Default: 2 days. To insure redundancy in the dumps, AMANDA keeps
+ Default: 2 days. To insure redundancy in the dumps, Amanda keeps
filesystems at the same incremental level for at least bumpdays days,
even if the other bump threshold criteria are met.
comprate float [, float ]
Default: 0.50, 0.50. The expected full and incremental compression factor
- for dumps. It is only used if AMANDA does not have any history
+ for dumps. It is only used if Amanda does not have any history
information on compression rates for a filesystem, so should not usually
need to be set. However, it may be useful for the first time a very large
filesystem that compresses very little is backed up.
compress [client|server] string
- Default: client fast. If AMANDA does compression of the backup images, it
+ Default: client fast. If Amanda does compression of the backup images, it
can do so either on the backup client host before it crosses the network
or on the tape server host as it goes from the network into the holding
disk or to tape. Which place to do compression (if at all) depends on how
well the dump image usually compresses, the speed and load on the client
or server, network capacity, holding disk capacity, availability of tape
hardware compression, etc.
- For either type of compression, AMANDA also allows the selection of two
+ For either type of compression, Amanda also allows the selection of three
styles of compression. Best is the best compression available, often at
the expense of CPU overhead. Fast is often not as good a compression as
- best, but usually less CPU overhead.
+ best, but usually less CPU overhead. Or to specify Custom to use your own
+ compression method. (See dumptype custom-compress in example/amanda.conf
+ for reference)
So the compress options line may be one of:
* compress none
* compress [client] fast
* compress [client] best
+ * compress client custom
+ Specify client_custom_compress "PROG"
+ PROG must not contain white space and it must accept -d for uncompress.
* compress server fast
* compress server best
+ * compress server custom
+ Specify server_custom_compress "PROG"
+ PROG must not contain white space and it must accept -d for uncompress.
Note that some tape devices do compression and this option has nothing to
do with whether that is used. If hardware compression is used (usually
- via a particular tape device name or mt option), AMANDA (software)
+ via a particular tape device name or mt option), Amanda (software)
compression should be disabled.
dumpcycle int
Default: 10 days. The number of days in the backup cycle. Each disk using
- this set of options will get a full backup at least this often. Setting
+ this set of options will get a full backup at least this of ten. Setting
this to zero tries to do a full backup each run.
+ encrypt [none|client|server]
+ Default: none. To encrypt backup images, it can do so either on the
+ backup client host before it crosses the network or on the tape server
+ host as it goes from the network into the holding disk or to tape.
+ So the encrypt options line may be one of:
+
+ * encrypt none
+ * encrypt client
+ Specify client_encrypt "PROG"
+ PROG must not contain white space.
+ Specify client_decrypt_option "decryption-parameter" Default: "-d"
+ decryption-parameter must not contain white space.
+ (See dumptype server-encrypt-fast in example/amanda.conf for reference)
+ * encrypt server
+ Specify server_encrypt "PROG"
+ PROG must not contain white space.
+ Specify server_decrypt_option "decryption-parameter" Default: "-d"
+ decryption-parameter must not contain white space.
+ (See dumptype client-encrypt-nocomp in example/amanda.conf for
+ reference)
+
+
estimate client|calcsize|server
- Default: client. Determine the way AMANDA does it's estimate.
+ Default: client. Determine the way Amanda does it's estimate.
* client:
Use the same program as the dumping program, this is the most accurate
Default: file. There are two exclude lists, exclude file and exclude
list. With exclude file , the string is a GNU-tar exclude expression.
With exclude list , the string is a file name on the client containing
- GNU-tar exclude expressions.
+ GNU-tar exclude expressions. The path to the specified exclude list file,
+ if present (see description of 'optional' below), must be readable by the
+ Amanda user.
All exclude expressions are concatenated in one file and passed to GNU-
tar as an --exclude-from argument.
+ Exclude expressions must always be specified as relative to the head
+ directory of the DLE.
With the append keyword, the string is appended to the current list,
without it, the string overwrites the list.
If optional is specified for exclude list, then amcheck will not complain
holdingdisk boolean
Default: yes. Whether a holding disk should be used for these backups or
whether they should go directly to tape. If the holding disk is a portion
- of another file system that AMANDA is backing up, that file system should
+ of another file system that Amanda is backing up, that file system should
refer to a dumptype with holdingdisk set to no to avoid backing up the
holding disk into itself.
list. With include file , the string is a glob expression. With include
list , the string is a file name on the client containing glob
expressions.
- All include expressions are expanded by AMANDA, concatenated in one file
+ All include expressions are expanded by Amanda, concatenated in one file
and passed to GNU-tar as a --files-from argument. They must start with
"./" and contain no other "/".
+ Include expressions must always be specified as relative to the head
+ directory of the DLE.
+
+ Note
+
+ For globbing to work at all, even the limited single level, the top level
+ directory of the DLE must be readable by the Amanda user.
With the append keyword, the string is appended to the current list,
without it, the string overwrites the list.
If optional is specified for include list, then amcheck will not complain
server host.
maxdumps int
- Default: 1. The maximum number of backups from a single host that AMANDA
+ Default: 1. The maximum number of backups from a single host that Amanda
will attempt to run in parallel. See also the main section parameter
inparallel.
overpromoted.
priority string
- Default: medium. When there is no tape to write to, AMANDA will do
+ Default: medium. When there is no tape to write to, Amanda will do
incremental backups in priority order to the holding disk. The priority
may be high (2), medium (1), low (0) or a number of your choice.
skip-full boolean
Default: no. If true and planner has scheduled a full backup, these disks
will be skipped, and full backups should be run off-line on these days.
- It was reported that AMANDA only schedules level 1 incrementals in this
+ It was reported that Amanda only schedules level 1 incrementals in this
configuration; this is probably a bug.
skip-incr boolean
standard
- The standard AMANDA schedule.
+ The standard Amanda schedule.
nofull
Never do full backups, only level 1 incrementals.
incronly
Only do incremental dumps. amadmin force should be used to tell
- AMANDA that a full dump has been performed off-line, so that it
+ Amanda that a full dump has been performed off-line, so that it
resets to level 1. It is similar to skip-full, but with incronly
full dumps may be scheduled manually. Unfortunately, it appears
- that AMANDA will perform full backups with this configuration,
+ that Amanda will perform full backups with this configuration,
which is probably a bug.
-The following dumptype entries are predefined by AMANDA:
+ tape_splitsize int
+ Default: none. Split dump file on tape into pieces of a specified size.
+ This allows dumps to be spread across multiple tapes, and can potentially
+ make more efficient use of tape space. Note that if this value is too
+ large (more than half the size of the average dump being split),
+ substantial tape space can be wasted. If too small, large dumps will be
+ split into innumerable tiny dumpfiles, adding to restoration complexity.
+ A good rule of thumb, usually, is 1/10 of the size of your tape.
+
+ split_diskbuffer string
+ Default: none. 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.
+
+ fallback_splitsize int
+ Default: 10M. When dumping a split dump in PORT-WRITE mode, if no
+ split_diskbuffer is specified (or if we somehow fail to use our
+ split_diskbuffer), we must buffer split chunks in memory. This specifies
+ the maximum size split chunks can be in this scenario, and thus the
+ maximum amount of memory consumed for in-memory splitting. The size of
+ this buffer can be changed from its (very conservative) default to a
+ value reflecting the amount of memory that each taper process on the dump
+ server may reasonably consume.
+
+The following dumptype entries are predefined by Amanda:
define dumptype no-compress {
compress none
record no
}
-AMANDA provides a dumptype named global in the sample amanda.conf file that all
+Amanda provides a dumptype named global in the sample amanda.conf file that all
dumptypes should reference. This provides an easy place to make changes that
will affect every dumptype.
length int
Default: 2000 kbytes. How much data will fit on a tape.
- Note that this value is only used by AMANDA to schedule which backups
- will be run. Once the backups start, AMANDA will continue to write to a
+ Note that this value is only used by Amanda to schedule which backups
+ will be run. Once the backups start, Amanda will continue to write to a
tape until it gets an error, regardless of what value is entered for
length (but see the section OUTPUT DRIVERS in the amanda(8) manpage for
exceptions).
Default: 32. How much data will be written in each tape record expressed
in KiloBytes. The tape record size (= blocksize) can not be reduced below
the default 32 KBytes. The parameter blocksize can only be raised if
- AMANDA was compiled with the configure option --with-maxtapeblocksize=N
+ Amanda was compiled with the configure option --with-maxtapeblocksize=N
set with "N" greater than 32 during configure.
file-pad boolean
Default: true. If true, every record, including the last one in the file,
- will have the same length. This matches the way AMANDA wrote tapes prior
+ will have the same length. This matches the way Amanda wrote tapes prior
to the availability of this parameter. It may also be useful on devices
that only support a fixed blocksize.
Note that the last record on the tape probably includes trailing null
speed int
Default: 200 bps. How fast the drive will accept data, in bytes per
- second. This parameter is NOT currently used by AMANDA.
+ second. This parameter is NOT currently used by Amanda.
lbl-templ string
A PostScript template file used by amreport to generate labels. Several
- sample files are provided with the AMANDA sources in the example
+ sample files are provided with the Amanda sources in the example
directory. See the amreport(8) man page for more information.
In addition to options, another tapetype name may be entered, which makes this
disklist file.
Note that these sections define network interface characteristics, not the
actual interface that will be used. Nor do they impose limits on the bandwidth
-that will actually be taken up by AMANDA. AMANDA computes the estimated
+that will actually be taken up by Amanda. Amanda computes the estimated
bandwidth each file system backup will take based on the estimated size and
time, then compares that plus any other running backups with the limit as
another of the criteria when deciding whether to start the backup. Once a
-backup starts, AMANDA will use as much of the network as it can leaving
+backup starts, Amanda will use as much of the network as it can leaving
throttling up to the operating system and network hardware.
The interface options and values are:
AUTHOR
James da Silva, <jds@amanda.org>: Original text
-Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the AMANDA-documentation:
+Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the Amanda-documentation:
XML-conversion, major update, splitting
SEE ALSO
-amanda(8),
+amanda(8), amanda-client.conf(5), amcrypt(8), aespipe(1),
-------------------------------------------------------------------------------
-Prev Up Next
-amanda Home amcheck
+Prev Up Next
+amanda Home amanda-client.conf
projects / debian / amanda / blobdiff