X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=example%2Famanda.conf.in;h=158f9614fb517a7351e91dd058dacfc1cea783c6;hb=b221e8dc16f345f8c8d7df8df71f4d36daaabb4c;hp=5e9df2bc155be3b35bd79221d8b694360461d6a4;hpb=94a044f90357edefa6f4ae9f0b1d5885b0e34aee;p=debian%2Famanda diff --git a/example/amanda.conf.in b/example/amanda.conf.in index 5e9df2b..158f961 100644 --- a/example/amanda.conf.in +++ b/example/amanda.conf.in @@ -111,47 +111,35 @@ 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 -# amdump, just comment out the definition of tpchanger. - -# Some tape changers require tapedev to be defined; others will use -# their own tape device selection mechanism. Some use a separate tape -# changer device (changerdev), others will simply ignore this -# parameter. Some rely on a configuration file (changerfile) to -# obtain more information about tape devices, number of slots, etc; -# others just need to store some data in files, whose names will start -# with changerfile. - -# At most one changerfile entry must be defined; select the most -# appropriate one for your configuration. If you select man-changer, -# keep the first one; if you decide not to use a tape changer, you may -# comment them all out. +# Specify tape device or tape changer. 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 +tapedev "@EXAMPLE_TAPEDEV@" # tape changer or device to use -#changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer" -#changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer-status" -changerfile "@CONFIG_DIR@/@DEFAULT_CONFIG@/changer.conf" -changerdev "@DEFAULT_CHANGER_DEVICE@" +# To use vtapes, create some slotN directories (slot0, slot1, etc.) under +# /var/amanda/vtapes and use this tapedev: +## tapedev "chg-disk:/var/amanda/vtapes" + +# To use a tape library, uncomment this definition. See amanda-changers(7) +# for more configuration options. +# +# define changer myrobot { +# tpchanger "chg-robot:/dev/sg0" # your changer device file +# tapedev "tape:@EXAMPLE_TAPEDEV@" # your tape drive device file +# } +# tapedev "myrobot" # If you want Amanda to automatically label any non-Amanda tapes it # encounters, uncomment the line below. Note that this will ERASE any # non-Amanda tapes you may have, and may also ERASE any near-failing tapes. # Use with caution. -## label_new_tapes "@DEFAULT_CONFIG@-%%%" +## autolabel "@DEFAULT_CONFIG@-%%%" empty maxdumpsize -1 # Maximum number of bytes the planner will schedule # for a run (default: runtapes * tape_length). tapetype HP-DAT # what kind of tape it is (see tapetypes below) labelstr "^@DEFAULT_CONFIG@-[0-9][0-9]*$" # label constraint regex: all tapes must match -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 "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 @@ -251,11 +239,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 @@ -280,8 +264,13 @@ indexdir "@CONFIG_DIR@/@DEFAULT_CONFIG@/index" # index directory # lbl-templ "@CONFIG_DIR@/config/lbl.exabyte.ps" # } +define tapetype global { + part_size 3G + part_cache_type none +} define tapetype QIC-60 { + global comment "Archive Viper" length 60 mbytes filemark 100 kbytes # don't know a better value @@ -289,6 +278,7 @@ define tapetype QIC-60 { } define tapetype DEC-DLT2000 { + global comment "DEC Differential Digital Linear Tape 2000" length 15000 mbytes filemark 8 kbytes @@ -298,6 +288,7 @@ define tapetype DEC-DLT2000 { # goluboff@butch.Colorado.EDU # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996) define tapetype DLT { + global comment "DLT tape drives" length 20000 mbytes # 20 Gig tapes filemark 2000 kbytes # I don't know what this means @@ -305,6 +296,7 @@ define tapetype DLT { } define tapetype SURESTORE-1200E { + global comment "HP AutoLoader" length 3900 mbytes filemark 100 kbytes @@ -312,6 +304,7 @@ define tapetype SURESTORE-1200E { } define tapetype EXB-8500 { + global comment "Exabyte EXB-8500 drive on decent machine" length 4200 mbytes filemark 48 kbytes @@ -319,6 +312,7 @@ define tapetype EXB-8500 { } define tapetype EXB-8200 { + global comment "Exabyte EXB-8200 drive on decent machine" length 2200 mbytes filemark 2130 kbytes @@ -326,6 +320,7 @@ define tapetype EXB-8200 { } define tapetype HP-DAT { + global comment "DAT tape drives" # data provided by Rob Browning length 1930 mbytes @@ -334,6 +329,7 @@ define tapetype HP-DAT { } define tapetype DAT { + global comment "DAT tape drives" length 1000 mbytes # these numbers are not accurate filemark 100 kbytes # but you get the idea @@ -341,6 +337,7 @@ define tapetype DAT { } define tapetype MIMSY-MEGATAPE { + global comment "Megatape (Exabyte based) drive through Emulex on Vax 8600" length 2200 mbytes filemark 2130 kbytes @@ -348,10 +345,11 @@ define tapetype MIMSY-MEGATAPE { } define tapetype SEAGATE-ULTRIUM-LTO { - comment "SEAGATE ULTRIUM 06242 LTO, compression off" - length 99584 mbytes - filemark 0 kbytes - speed 11288 kps + global + comment "SEAGATE ULTRIUM 06242 LTO, compression off" + length 99584 mbytes + filemark 0 kbytes + speed 11288 kps } # dumptypes @@ -359,8 +357,9 @@ define tapetype SEAGATE-ULTRIUM-LTO { # These are referred to by the disklist file. The dumptype specifies # certain parameters for dumping including: # auth - authentication scheme to use between server and client. -# Valid values are "bsd", "krb4", "krb5" and "ssh". -# Default: [auth bsd] +# Valid values are "bsd", "bsdudp", "bsdtcp", "krb5", "local", +# "rsh" and "ssh". +# Default: [auth "bsdtcp"] # comment - just a comment string # comprate - set default compression rate. Should be followed by one or # two numbers, optionally separated by a comma. The 1st is @@ -461,7 +460,7 @@ define tapetype SEAGATE-ULTRIUM-LTO { # program - specify the dump system to use. Valid values are "DUMP", # or "GNUTAR". Default: [program "DUMP"]. # record - record the backup in the time-stamp-database of the backup -# program (e.g. /etc/dumpdates for DUMP or +# program (e.g. /var/lib/dumpdates for DUMP or # @GNUTAR_LISTED_INCREMENTAL_DIRX@ for GNUTAR.). # Default: [record yes] # skip-full - skip the disk when a level 0 is due, to allow full backups @@ -486,25 +485,6 @@ define tapetype SEAGATE-ULTRIUM-LTO { # only be performed when an 'amadmin force' # has been issued # Default: [strategy standard] -# tape_splitsize - (optional) split dump file 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. Default: [disabled] -# split_diskbuffer - (optional) 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. -# Default: [none] -# fallback_splitsize - (optional) 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. Default: [10m] # # Note that you may specify previously defined dumptypes as a shorthand way of # defining parameters. @@ -524,8 +504,7 @@ define dumptype global { # indexing, recording, etc. Some examples: # index yes # record no - # split_diskbuffer "/raid/amanda" - # fallback_splitsize 64m + # auth "bsdtcp" } define dumptype always-full { @@ -555,7 +534,6 @@ define dumptype user-tar { define dumptype user-tar-span { root-tar - tape_splitsize 3 Gb comment "tape-spanning user partitions dumped with tar" priority medium } @@ -598,7 +576,6 @@ define dumptype comp-user { define dumptype comp-user-span { global - tape_splitsize 5 Gb comment "Tape-spanning non-root partitions on reasonably fast machines" compress client fast priority medium @@ -644,7 +621,7 @@ define dumptype nocomp-high { define dumptype nocomp-test { global - comment "test dump without compression, no /etc/dumpdates recording" + comment "test dump without compression, no /var/lib/dumpdates recording" compress none record no priority medium @@ -652,7 +629,7 @@ define dumptype nocomp-test { define dumptype comp-test { nocomp-test - comment "test dump with compression, no /etc/dumpdates recording" + comment "test dump with compression, no /var/lib/dumpdates recording" compress client fast } @@ -725,6 +702,80 @@ define interface local { # 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 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 + +define interactivity inter_tty { + plugin "tty" +} +define interactivity inter_email { + plugin "email" + property "mailto" "admin1" "admin2" + property "resend-delay" "10" + property "check-file" "/tmp/email_input" + property "check-file-delay" "10" +} +define interactivity inter_tty_email { + plugin "tty_email" + property "mailto" "admin1" "admin2" + property "resend-delay" "10" + property "check-file" "/tmp/email_input" + property "check-file-delay" "10" +} +interactivity "inter_tty_email" + +define taperscan taper_traditional { + comment "traditional" + plugin "traditional" +} +define taperscan taper_oldest { + comment "oldest" + plugin "oldest" +} +define taperscan taper_lexical { + comment "lexical" + plugin "lexical" +} +taperscan "taper_lexical" + # You may include other amanda configuration files, so you can share # dumptypes, tapetypes and interface definitions among several # configurations.