X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=example%2Famanda.conf.in;h=57f1befc9baeb0032e2ec50b270c50acfc43bcfb;hb=2627875b7d18858bc1f9f7652811e4d8c15a23eb;hp=1cd99783b94e371480e1f7894aaedf87e0c30644;hpb=d3b2175e084f88c8736ad7073eacbf4670147aec;p=debian%2Famanda diff --git a/example/amanda.conf.in b/example/amanda.conf.in index 1cd9978..57f1bef 100644 --- a/example/amanda.conf.in +++ b/example/amanda.conf.in @@ -37,7 +37,7 @@ displayunit "k" # Possible values: "k|m|g|t" # The unit used to print many numbers. # k=kilo, m=mega, g=giga, t=tera -netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec +netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days @@ -59,8 +59,8 @@ dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host -tapebufs 20 # A positive integer telling taper how many - # 32k buffers to allocate. The default is 20 (640k). +device_output_buffer_size 1280k + # amount of buffer space to use when writing to devices # By default, Amanda can only track at most one run per calendar day. When # the usetimestamps option is enabled, however, Amanda can track as many @@ -70,6 +70,46 @@ tapebufs 20 # A positive integer telling taper how many # edition 2.5 usetimestamps yes +# flush-threshold-dumped, flush-threshold-scheduled, taperflush, and autoflush +# are used to control tape utilization. See the amanda.conf (5) manpage for +# details on how they work. Taping will not start until all criteria are +# satisfied. Here are some examples: +# +# You want to fill tapes completely even in the case of failed dumps, and +# don't care if some dumps are left on the holding disk after a run: +# flush-threshold-dumped 100 # (or more) +# flush-threshold-scheduled 100 # (or more) +# taperflush 100 +# autoflush yes +# +# You want to improve tape performance by waiting for a complete tape of data +# before writing anything. However, all dumps will be flushed; none will +# be left on the holding disk. +# flush-threshold-dumped 100 # (or more) +# flush-threshold-scheduled 100 # (or more) +# taperflush 0 +# +# You don't want to use a new tape for every run, but want to start writing +# to tape as soon as possible: +# flush-threshold-dumped 0 # (or more) +# flush-threshold-scheduled 100 # (or more) +# taperflush 100 +# autoflush yes +# maxdumpsize 100k # amount of data to dump each run; see above. +# +# You want to keep the most recent dumps on holding disk, for faster recovery. +# Older dumps will be rotated to tape during each run. +# flush-threshold-dumped 300 # (or more) +# flush-threshold-scheduled 300 # (or more) +# taperflush 300 +# autoflush yes +# +# Defaults: +# (no restrictions; flush to tape immediately; don't flush old dumps.) +flush-threshold-dumped 0 +flush-threshold-scheduled 0 +taperflush 0 +autoflush no # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of @@ -91,7 +131,7 @@ usetimestamps yes runtapes 1 # number of tapes to be used in a single run of amdump tpchanger "chg-manual" # the tape-changer glue script tapedev "@EXAMPLE_TAPEDEV@" # the no-rewind tape device to be used -rawtapedev "@DEFAULT_RAW_TAPE_DEVICE@" # the raw device to be used (ftape only) + #changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer" #changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer-status" changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer.conf" @@ -112,11 +152,10 @@ amrecover_do_fsf yes # amrecover will call amrestore with the # -f flag for faster positioning of the tape. amrecover_check_label yes # amrecover will call amrestore with the # -l flag to check the label. -amrecover_changer "@EXAMPLE_TAPEDEV@" # amrecover will use the changer if you restore - # from this device. - # It could be a string like 'changer' and - # amrecover will use your changer if you - # set your tape with 'settape changer' +amrecover_changer "changer" # amrecover will use the changer if you restore + # from this device. It could be a string like 'changer' and amrecover will use your + # changer if you set your tape to 'changer' with 'setdevice changer' or via + # 'tapedev "changer"' in amanda-client.conf # Specify holding disks. These are used as a temporary staging area for # dumps before they are written to tape and are recommended for most sites. @@ -166,10 +205,6 @@ holdingdisk hd1 { # This means save at least 30% of the holding disk space for degraded # mode backups. -autoflush no # -# if autoflush is set to yes, then amdump will schedule all dump on -# holding disks to be flush to tape during the run. - # The format for a ColumnSpec is a ',' seperated list of triples. # Each triple consists of # + the name of the column (as in ColumnNameStrings) @@ -216,11 +251,7 @@ indexdir "@CONFIG_DIR@/@DEFAULT_CONFIG@/index" # index directory # are, and how fast the tape device is. # A filemark is the amount of wasted space every time a tape section -# ends. If you run `make tapetype' in tape-src, you'll get a program -# that generates tapetype entries, but it is slow as hell, use it only -# if you really must and, if you do, make sure you post the data to -# the amanda mailing list, so that others can use what you found out -# by searching the archives. +# ends. # For completeness Amanda should calculate the inter-record gaps too, # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using @@ -312,6 +343,12 @@ define tapetype MIMSY-MEGATAPE { speed 170 kbytes # limited by the Emulex bus interface, ugh } +define tapetype SEAGATE-ULTRIUM-LTO { + comment "SEAGATE ULTRIUM 06242 LTO, compression off" + length 99584 mbytes + filemark 0 kbytes + speed 11288 kps +} # dumptypes # @@ -676,13 +713,54 @@ define dumptype client-encrypt-nocomp { define interface local { comment "a local disk" - use 1000 kbps + use 8000 kbps +} + +#define interface le0 { +# comment "10 Mbps ethernet" +# use 400 kbps +#} + +#define application-tool and dumptype for the amgtar application +define application-tool app_amgtar { + comment "amgtar" + plugin "amgtar" + #property "GNUTAR-PATH" "/path/to/gtar" + #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir" + #default from gnutar_list_dir setting in amanda-client.conf +} + +define dumptype dt_amgtar { + program "APPLICATION" + application "app_amgtar" +} + +#define application-tool and dumptype for the amstar application +define application-tool app_amstar { + comment "amstar" + plugin "amstar" + #property "STAR-PATH" "/path/to/star" + #property "STAR-TARDUMP" "/path/to/tardumps" # default /etc/tardumps + #property "STAR-DLE-TARDUMP" "no" + # if 'yes' then create a different tardump file for each DLE, + # it is required if you do many dump in parallel (maxdump>1) +} + +define dumptype dt_amstar { + program "APPLICATION" + application "app_amstar" } -define interface le0 { - comment "10 Mbps ethernet" - use 400 kbps +#define a script-tool to send an email +define script-tool sc-email { + comment "script-email" + plugin "script-email" + execute_on pre-dle-amcheck, pre-host-amcheck, post-dle-amcheck, post-host-amcheck, pre-dle-estimate, pre-host-estimate, post-dle-estimate, post-host-estimate, pre-dle-backup, pre-host-backup, post-dle-backup, post-host-backup + execute_where server # or client + property "mailto" "martinea" } +#your dumptype must include: script "sc-email" +#to use the script # You may include other amanda configuration files, so you can share # dumptypes, tapetypes and interface definitions among several