Splitting Configuration Parameters and Behavior

From wiki.zmanda.com
Revision as of 04:01, 25 June 2010 by Dustin (talk | contribs) (results for all current cases)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This table describes the configuration parameters that affect splitting (tape_splitsize, split_diskbuffer, and fallback_splitsize), the relevant conditions for a particular dump, and the results. See the key, below, for more information

Configuration Parameter Table

conditionconfigurationresult
tape
splitsize
split
diskbuffer
fallback
splitsize
part sizecaching
FILE_WRITE -??none
0??none
999??tpnone
PORT_WRITE
datapath Amanda
-??none
0??none
999--10Mmemory
999-0tpmemory
999-999fbmemory
999inval-10Mmemory
999inval0tpmemory
999inval999fbmemory
999/...?tpdisk
PORT_WRITE
datapath DirectTCP
-??none
0??none
999--10Mnone
999-0tpnone
999-999fbnone
999inval-10Mnone
999inval0tpnone
999inval999fbnone
999/...?tpnone

Key

For parameters:

?
parameter is ignored
-
parameter is not given in amanda.conf
0
parameter has zero value
999
parameter has nonzero value
/...
a valid value for split_diskbuffer
inval
in invalid value for split_diskbuffer (nonexistent, or less than tape_splitsize bytes available)

For results:

tp
tape_splitsize KB parts
fb
fallback_splitsize KB parts
10M
default fallback_splitsize of 10M
no splitting (DirectTCP devices will still successfully span from volume to volume; others will not)