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.
+The file <CONFIG_DIR>/<config>/amanda.conf is loaded.
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
+ appears in the Subject line of mail reports. Each Amanda configuration
should have a different string to keep mail reports distinct.
mailto string
used in the last dumpcycle days / runtapes.
tapecycle int
- Default: 15 tapes. Typically tapes are used by AMANDA in an ordered
+ 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
+ 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
misplaced tapes or schedule adjustments that call for slight adjustments
in the rotation order.
+ usetimestamps bool
+ Default: No. By default, Amanda can only track at most one run per
+ calendar day. When this option is enabled, however, Amanda can track as
+ many runs as you care to make.
+ WARNING: This option is not backward-compatible. Do not enable it if you
+ intend to downgrade your server installation to Amanda community edition
+ 2.5.0
+
+ label_new_tapes string
+ Default: not set. When set, this directive will cause Amanda to
+ automatically write an Amanda tape label to any blank tape she
+ encounters. This option is DANGEROUS because when set, Amanda will ERASE
+ any non-Amanda tapes you may have, and may also ERASE any near-failing
+ tapes. Use with caution.
+ When using this directive, specify the template for new tape labels. The
+ template should contain some number of contiguous '%' characters, which
+ will be replaced with a generated number. Be sure to specify enough '%'
+ characters that you do not run out of tape labels. Example:
+ label_new_tapes "DailySet1-%%%"
+
dumpuser string
- Default: amanda. The login name AMANDA uses to run the backups. The
+ 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
+ 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-
+ Default: null:. 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.
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.
+ Default: 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
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
+ 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
+ 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
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.
+ First character of a tapetype string must be an alphabetic character
ctimeout int
Default: 30 seconds. Maximum amount of time that amcheck will wait for
will be interpreted as a total amount of time to wait per client instead
of per disk.
+ connect_tries int
+ Default: 3. How many times the server will try a connection.
+
+ req_tries int
+ Default: 3. How many times the server will resend a REQ packet if it
+ doesn't get the ACK packet.
+
netusage int
- Default: 300 Kbps. The maximum network bandwidth allocated to AMANDA, in
+ 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
+ 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.
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
+ 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
+ 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
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
dumptype-definition.
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.
The global setting of this parameter can be overwritten inside of a
infofile string
Default: /usr/adm/amanda/curinfo. The file or directory name for the
- historical information database. If AMANDA was configured to use DBM
+ 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,
filesystems whose dumptype has the index option enabled.
tapelist string
- Default: tapelist. The file name for the active tapelist file. AMANDA
+ Default: tapelist. The file name for the active tapelist file. Amanda
maintains this file with information about the active set of tapes.
tapebufs int
lowered.
autoflush bool
- Default: off. Whether an amdump run will flush the dump already on
- holding disk to tape.
+ Default: off. Whether an amdump run will flush the dumps from holding
+ disk to tape.
amrecover_do_fsf bool
- Default: off. Amrecover will call amrestore with the -f flag for faster
+ Default: on. 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
+ Default: on. Amrecover will call amrestore with the -l flag to check the
label.
amrecover_changer string
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.
+ 1. the name of the column, which may be:
+
+ Compress (compression ratio)
+ Disk (client disk name)
+ DumpRate (dump rate in KBytes/sec)
+ DumpTime (total dump time in hours:minutes)
+ HostName (client host name)
+ Level (dump level)
+ OrigKB (original image size in KBytes)
+ OutKB (output image size in KBytes)
+ TapeRate (tape writing rate in KBytes/sec)
+ TapeTime (total tape time in hours:minutes)
+
+
+ 2. the amount of space to display before the column (used to get
+ whitespace between columns).
+ 3. 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:
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.
+ debug_auth int
+ Default: 0. Debug level of the auth module
+
+ debug_event int
+ Default: 0. Debug level of the event module
+
+ debug_holding int
+ Default: 0. Debug level of the holdingdisk module
+
+ debug_protocol int
+ Default: 0. Debug level of the protocol module
+
+ debug_planner int
+ Default: 0. Debug level of the planner process
+
+ debug_driver int
+ Default: 0. Debug level of the driver process
+
+ debug_dumper int
+ Default: 0. Debug level of the dumper process
+
+ debug_chunker int
+ Default: 0. Debug level of the chunker process
+
+ debug_taper int
+ Default: 0. Debug level of the taper process
+
+ reserved-udp-port int,int
+ Default: --with-udpportrange or 512,1023. Reserved udp port that will be
+ used (bsd, bsdudp)
+
+ reserved-tcp-port int,int
+ Default: --with-low-tcpportrange or 512,1023. Reserved tcp port that will
+ be used (bsdtcp)
+
+ unreserved-tcp-port int,int
+ Default: --with-tcpportrange or 1025,65536. Unreserved tcp port that will
+ be used (bsd, bsdudp)
+
HOLDINGDISK SECTION
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
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 (
+ 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
+ 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.
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 server fast
- * compress server best
+
+ 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)
+
+ Note that current logic assumes compression then encryption during backup
+ (thus decrypt then uncompress during restore). So specifying client-
+ encryption AND server-compression is not supported. amcrypt which is a
+ wrapper of aespipe is provided as a reference symmetric encryption
+ program.
+
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 way to do estimates, but it can take a long time.
- * client:
- Use the same program as the dumping program, this is the most accurate
- way to do estimates, but it can take a long time.
- * calcsize:
- Use a faster program to do estimates, but the result is less accurate.
- * server:
- Use only statistics from the previous run to give an estimate, it takes
- only a few seconds but the result is not accurate if your disk usage
- changes from day to day.
+ calcsize
+ Use a faster program to do estimates, but the result is less
+ accurate.
+
+ server
+ Use only statistics from the previous run to give an estimate, it
+ takes only a few seconds but the result is not accurate if your
+ disk usage changes from day to day.
exclude [ list|file ][[optional][ append ][ string ]+]
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
the actual file used would be /var/.amanda.excludes for a backup of /var,
/usr/local/.amanda.excludes for a backup of /usr/local, and so on.
- holdingdisk boolean
- Default: yes. Whether a holding disk should be used for these backups or
+ holdingdisk [ never|auto|required ]
+ Default: auto. 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
- refer to a dumptype with holdingdisk set to no to avoid backing up the
+ of another file system that Amanda is backing up, that file system should
+ refer to a dumptype with holdingdisk set to never to avoid backing up the
holding disk into itself.
+
+ never|no|false|off
+ Never use a holdingdisk, the dump will always go directly to tape.
+ There will be no dump if you have a tape error.
+
+ auto|yes|true|on
+ 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)
+
+ required
+ Always dump to holdingdisk, never directly to tape. There will be
+ no dump if it doesn't fit on holdingdisk
+
+
ignore boolean
Default: no. Whether disks associated with this backup type should be
backed up or not. This option is useful when the disklist file is shared
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.
Default: none. A comment string describing this set of tape information.
filemark int
- Default: 1000 bytes. How large a file mark (tape mark) is, measured in
- bytes. If the size is only known in some linear measurement (e.g.
- inches), convert it to bytes using the device density.
+ Default: 1 kbytes. How large a file mark (tape mark) is, measured in
+ kbytes. If the size is only known in some linear measurement (e.g.
+ inches), convert it to kbytes using the device density.
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).
blocksize int
- 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
- set with "N" greater than 32 during configure.
+ Default: 32 kbytes. 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 set with "N" greater than 32 during configure.
+
+ readblocksize int
+ Default: (from configure --with-maxtapeblocksize). How much data will be
+ read in each tape record expressed in KiloBytes. Some hardware require a
+ value not too large, and some require it to be equal to the blocksize. It
+ is useful if you configured amanda with a big --with-maxtapeblocksize and
+ your hardware don't work with a value that big.
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