X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=man%2Fxml-source%2Famanda.conf.5.xml;h=f322c1ff3b3bfa604b45a1957632ec5e3bcec823;hb=94a044f90357edefa6f4ae9f0b1d5885b0e34aee;hp=adcae4f97b83f6a3b6c33617630d134a2032cfdd;hpb=34197d9f46a5f4e944378cbb65fca32ee0eec7b9;p=debian%2Famanda
diff --git a/man/xml-source/amanda.conf.5.xml b/man/xml-source/amanda.conf.5.xml
index adcae4f..f322c1f 100644
--- a/man/xml-source/amanda.conf.5.xml
+++ b/man/xml-source/amanda.conf.5.xml
@@ -232,15 +232,10 @@ with damaged or misplaced tapes or schedule adjustments that call for slight adj
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
+ Default: Yes.
+This option allows Amanda to track multiple runs per calendar
+day. The only reason one might disable it is that Amanda versions before 2.5.1
+can't read logfiles written when this option was enabled.
@@ -288,6 +283,7 @@ See the
option.
+
tapedev string
@@ -323,15 +319,27 @@ option set to
- rawtapedev string
+ device_property string string
-Default:
-null:.
-The path name of the raw tape device.
-This is only used if &A; is compiled for Linux machines with floppy tapes
-and is needed for QIC volume table operations.
+These options can set various device properties, including block size,
+maximum volume usage, authentication information, hardware feature support,
+and more.Specifics of how properties are used are device-dependent, though
+some common properties are supported across multiple device drivers.
+
+ Both strings are quoted; the first string contains the name of
+the property to set, and the second contains its value. For example, to set
+a fixed block size of 128k, do:device_property "BLOCK_SIZE" "131072"
+
+The order in which device properties are set is as follows:
+Tapetype parameters, including length, blocksize,
+readblocksize, file-pad, are translated into device properties and set
+accordingly.
+Device properties from any device_property configuration directives
+are set, in the order they appear in the configuration file.
+
+
tpchanger string
@@ -501,28 +509,47 @@ running from within
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
+Amount of time per estimate on a given client that the
+planner step of
+amdump will wait to get the dump size estimates
+(note: Amanda runs up to 3 estimates for each DLE). For instance,
+with the default of 300 seconds and four DLE's, each estimating level
+0 and level 1 on client A, planner
+will wait up to 40 minutes for that machine. A negative value 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.
+8000 Kbps.
The maximum network bandwidth allocated to &A;, in Kbytes per second.
See also the
interface
@@ -744,6 +771,17 @@ The file name for the active
tapelist
file.
&A; maintains this file with information about the active set of tapes.
+
+
+
+ device_output_buffer_size int
+
+Default:
+640k.
+Controls the amount of memory used by &A;
+to hold data as it is read from the network or disk before it is written to
+the output device. Higher values may be
+useful on fast tape drives and optical media.
@@ -751,14 +789,11 @@ file.
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.
+This option is deprecated; use
+the device_output_buffer_size directive
+instead. tapebufs works the same way,
+but the number specified is multiplied by the device blocksize prior
+to use.
@@ -863,9 +898,204 @@ with one space before it.
Default:
none.
The name of an &A; configuration file to include within the current file.
-Useful for sharing dumptypes, tapetypes and interface definitions among several configurations.
+Useful for sharing dumptypes, tapetypes and interface definitions among several configurations.
+Relative pathnames are relative to the configuration directory.
+
+
+
+
+
+ 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
+
+
+
+
+ flush-threshold-dumped int
+
+Default: 0.
+ &A; will not begin writing data to a new volume until the amount of
+ data on the holding disk is at least this percentage of the volume
+ size. In other words, &A; will not begin until the
+ inequality h < t ×
+ d is satisfied,
+ where h is the amount of data on the
+ holding disk, t is the capacity of a
+ volume, and d is this parameter, expressed as a
+ percentage.
+ Needless to say, your holding disk must be big enough
+ that this criterion could be satisfied. If the holding disk cannot
+ be used for a particular dump (because, for example, there is no
+ remaining holding space) then &A; will disregard the constraint
+ specified by this setting and start a new volume anyway. Once
+ writing to a volume has begun, this constraint is not applied unless
+ and until a new volume is needed.
+ The value of this parameter may not exceed than that of
+ the flush-threshold-scheduled
+ parameter.
+
+
+
+
+ flush-threshold-scheduled int
+
+Default: 0.
+ &A; will not begin writing data to a new volume until the sum of the
+ amount of data on the holding disk and the estimated amount of data
+ remaining to be dumped during this run is at least this percentage
+ of the volume size. In other words, &A; will not begin until the
+ inequality h + s < t ×
+ d is satisfied,
+ where h is the amount of data on the
+ holding disk, s is the total amount of
+ data scheduled for this run but not dumped
+ yet, t is the capacity of a volume,
+ and d is this parameter, expressed as a
+ percentage.
+ Needless to say, your holding disk must be big enough
+ that this criterion could be satisfied. If the holding disk cannot
+ be used for a particular dump (because, for example, there is no
+ remaining holding space) then &A; will disregard the constraint
+ specified by this setting and start a new volume anyway. Once
+ writing to a volume has begun, this constraint is not applied unless
+ and until a new volume is needed.
+ The value of this parameter may not be less than that of
+ the flush-threshold-dumped
+ or taperflush parameters.
+
+
+
+
+
+ taperflush int
+
+Default: 0.
+ At the end of a run, &A; will start a new tape to flush remaining
+ data if there is more data on the holding disk at the end of a run
+ than this setting allows; the amount is specified as a percentage of
+ the capacity of a single
+ volume. In other words, at the end of a run, &A; will begin
+ a new tape if the
+ inequality h < t ×
+ f is satisfied,
+ where h is the amount of data remaining on the
+ holding disk from this or previous runs, t
+ is the capacity of a volume,
+ and f is this parameter, expressed as a
+ percentage.
+ The value of this parameter may not exceed that of
+ the flush-threshold-scheduled
+ parameter.; autoflush must be set to 'yes' if
+ taperflush is greater than 0.
+
+
+
+
+ reserved-udp-port int,int
+
+Default: --with-udpportrange or
+512,1023.
+Reserved udp port that will be used (bsd, bsdudp).
+Range is inclusive.
+
+
+
+
+ reserved-tcp-port int,int
+
+Default: --with-low-tcpportrange or
+512,1023.
+Reserved tcp port that will be used (bsdtcp).
+Range is inclusive.
+
+
+
+
+ unreserved-tcp-port int,int
+
+Default: --with-tcpportrange or
+1024,65535.
+Unreserved tcp port that will be used (bsd, bsdudp).
+Range is inclusive.
+
+
+
@@ -1004,6 +1234,8 @@ tcp connection for all data stream.
authorization.
krb5 to use Kerberos-V
authorization.
+local, if the client is the server, it
+doesn't require authencation setup.
rsh to use rsh
authorization.
ssh to use OpenSSH
@@ -1742,6 +1974,18 @@ The tape record size (= blocksize) can not be reduced below the default 32 KByte
The parameter blocksize can only be raised if &A; 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.
@@ -1862,7 +2106,7 @@ A comment string describing this set of network information.
use int
Default:
-300 Kbps.
+8000 Kbps.
The speed of the interface in Kbytes per second.
@@ -1888,6 +2132,11 @@ At the moment, this is of little use.
amanda-client.conf5,
amcrypt8,
aespipe1,
+http://wiki.zmanda.com
+
+
+
+An updated version of this man page may be available at http://wiki.zmanda.com/index.php/Amanda.conf.