Hi, i have the problem, that amanda always flushes its holding-disk, no matter what i do. I tried 2.5.2 and 2.5.2-flush-1. I tried with different reserves and holdingdisk set to auto and required.
-- Harald Schioeberg Technische Universitaet Berlin | T-Laboratories | FG INET www: http://www.net.t-labs.tu-berlin.de
# amanda.conf - sample Amanda configuration file. See amanda.conf(5) for # details org "Test" # your organization name for reports mailto "[EMAIL PROTECTED]" # space separated list of operators at your site dumpuser "amanda" # the user to run dumps under inparallel 1 # maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h dumporder "sssS" # specify the priority order of each dumper # s -> smallest size # S -> biggest size # t -> smallest time # T -> biggest time # b -> smallest bandwitdh # B -> biggest bandwitdh # try "BTBTBTBTBTBT" if you are not holding # disk constrained taperalgo first # The algorithm used to choose which dump image to send # to the taper. # Possible values: # [first|firstfit|largest|largestfit|smallest|last] # Default: first. # first First in - first out. # firstfit The first dump image that will fit # on the current tape. # largest The largest dump image. # largestfit The largest dump image that will fit # on the current tape. # smallest The smallest dump image. # last Last in - first out. displayunit "k" # Possible values: "k|m|g|t" # Default: k. # 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 dumpcycle 1 weeks # the number of days in the normal dump cycle runspercycle 6 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 6 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2 bumppercent 20 # minimum savings (threshold) to bump level 1 -> 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300 # number of seconds per filesystem for estimates. 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). # krb5keytab "/etc/amanda.keytab" krb5principal "amanda" debug_auth 9 debug_event 9 debug_holding 9 debug_protocol 9 debug_planner 9 debug_driver 9 debug_dumper 9 debug_chunker 9 debug_taper 9 # 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 # 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 usetimestamps yes # 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. runtapes 2 # number of tapes to be used in a single run of amdump # tpchanger "chg-manual" # the tape-changer glue script # tapedev "/dev/null" # the no-rewind tape device to be used # rawtapedev "/dev/null" # the raw device to be used (ftape only) #changerfile "/opt/amanda/etc/amanda/Daily/changer" #changerfile "/opt/amanda/etc/amanda/Daily/changer-status" #changerfile "/opt/amanda/etc/amanda/Daily/changer.conf" # changerdev "/dev/null" tpchanger "chg-disk" # vtape driver tapedev "file:/amanda/Daily" changerfile "/amanda/Daily/changer" # 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 "Daily-%%%" maxdumpsize -1 # Maximum number of bytes the planner will schedule # for a run (default: runtapes * tape_length). tapetype Disk10G # what kind of tape it is (see tapetypes below) labelstr "TST[0-9][0-9][0-9]L0$" # 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 with 'settape changer' # 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. # The advantages include: tape drive is more likely to operate in streaming # mode (which reduces tape and drive wear, reduces total dump time); multiple # dumps can be done in parallel (which can dramatically reduce total dump time. # The main disadvantage is that dumps on the holding disk need to be flushed # (with amflush) to tape after an operating system crash or a tape failure. # If no holding disks are specified then all dumps will be written directly # to tape. If a dump is too big to fit on the holding disk than it will be # written directly to tape. If more than one holding disk is specified then # they will all be used based on activity and available space. holdingdisk hd1 { comment "main holding disk" directory "/amanda/holding" # where the holding disk is use 50 Gb # how much space can we use on it # a non-positive value means: # use all space but that value chunksize 2 Gb # size of chunk if you want big dump to be # dumped on multiple files on holding disks # N Kb/Mb/Gb split images in chunks of size N # The maximum value should be # (MAX_FILE_SIZE - 1Mb) # 0 same as INT_MAX bytes } #holdingdisk hd2 { # directory "/dumps2/amanda" # use 1000 Mb # } #holdingdisk hd3 { # directory "/mnt/disk4" # use 1000 Mb # } # If amanda cannot find a tape on which to store backups, it will run # as many backups as it can to the holding disks. In order to save # space for unattended backups, by default, amanda will only perform # incremental backups in this case, i.e., it will reserve 100% of the # holding disk space for the so-called degraded mode backups. # However, if you specify a different value for the `reserve' # parameter, amanda will not degrade backups if they will fit in the # non-reserved portion of the holding disk. reserve 30 # reserve 30 # percent # This means save at least 30% of the holding disk space for degraded # mode backups. autoflush off # # 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) # + prefix before the column # + the width of the column, if set to -1 it will be recalculated # to the maximum length of a line to print. # Example: # "Disk=1:17,HostName=1:10,OutKB=1:7" # or # "Disk=1:-1,HostName=1:10,OutKB=1:7" # # You need only specify those colums that should be changed from # the default. If nothing is specified in the configfile, the # above compiled in values will be in effect, resulting in an # output as it was all the time. # The names of the colums are: # HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime, DumpRate, # TapeTime and TapeRate. # ElB, 1999-02-24. # columnspec "Disk=1:18,HostName=0:10,OutKB=1:7" # Amanda needs a few Mb of diskspace for the log and debug files, # as well as a database. This stuff can grow large, so the conf directory # isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm. # Create an amanda directory under there. You need a separate infofile and # logdir for each configuration, so create subdirectories for each conf and # put the files there. Specify the locations below. # Note that, although the keyword below is infofile, it is only so for # historic reasons, since now it is supposed to be a directory (unless # you have selected some database format other than the `text' default) infofile "/opt/amanda/var/amanda/Daily/curinfo" # database DIRECTORY logdir "/opt/amanda/var/amanda/log" # log directory indexdir "/opt/amanda/var/amanda/Daily/index" # index directory tapelist "/opt/amanda/var/amanda/Daily/tapelist" # list of used tapes # tapelist is stored, by default, in the directory that contains amanda.conf # tapetypes # Define the type of tape you use here, and use it in "tapetype" # above. Some typical types of tapes are included here. The tapetype # tells amanda how many MB will fit on the tape, how big the filemarks # 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. # For completeness Amanda should calculate the inter-record gaps too, # but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using # 9 tracks for amanda and need IRG calculations? Drop me a note if # so. # If you want amanda to print postscript paper tape labels # add a line after the comment in the tapetype of the form # lbl-templ "/path/to/postscript/template/label.ps" # if you want the label to go to a printer other than the default # for your system, you can also add a line above for a different # printer. (i usually add that line after the dumpuser specification) # dumpuser "operator" # the user to run dumps under # printer "mypostscript" # printer to print paper label on # here is an example of my definition for an EXB-8500 # define tapetype EXB-8500 { # ... # lbl-templ "/opt/amanda/etc/amanda/config/lbl.exabyte.ps" # } define tapetype Disk10G { comment "Disk-pseudo-tape" length 10 gbytes filemark 1 kbytes speed 100 mbytes } # dumptypes # # 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] # 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 # the full compression rate; the 2nd is the incremental rate. # If the second is omitted, it is assumed equal to the first. # The numbers represent the amount of the original file the # compressed file is expected to take up. # Default: [comprate 0.50, 0.50] # compress - specify compression of the backed up data. Valid values are: # "none" - don't compress the dump output. # "client best" - compress on the client using the best (and # probably slowest) algorithm. # "client fast" - compress on the client using fast algorithm. # "client custom" - compress using your custom client compression program. # use client_custom_compress "PROG" to specify # the custom compression program. # PROG must not contain white space. # "server best" - compress on the tape host using the best (and # probably slowest) algorithm. # "server fast" - compress on the tape host using a fast # algorithm. This may be useful when a fast # tape host is backing up slow clients. # "server custom" - compress using your server custom compression program. # use server_custom_compress "PROG" to specify # the custom compression program. # PROG must not contain white space. # Default: [compress client fast] # dumpcycle - set the number of days in the dump cycle, ie, set how often a # full dump should be performed. Default: from DUMPCYCLE above # estimate 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. # "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. # Default: [client] # encrypt - specify encryption of the backed up data. Valid values are: # "none" - don't encrypt the dump output. # "client" - encrypt on the client using the program specified by # client_encrypt "PROG". # Use client_decrypt_option to specify the decrypt- # parameter, default is "-d". # PROG and decrypt-parameter must not contain white space. # "server" - encrypt on the server using the program specified by # server_encrypt "PROG". # Use server_decrypt_option to specify the decrypt- # parameter, default is "-d". # PROG and decrypt-parameter must not contain white space. # Default: [none] # exclude - specify files and directories to be excluded from the dump. # Useful with gnutar only; silently ignored by dump and samba. # Valid values are: # "pattern" - a shell glob pattern defining which files # to exclude. # gnutar gets --exclude="pattern" # list "filename" - a file (on the client!) containing patterns # re's (1 per line) defining which files to # exclude. # gnutar gets --exclude-from="filename" # Note that the `full pathname' of a file within its # filesystem starts with `./', because of the way amanda runs # gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note # the final dot!) Thus, if you're backing up `/usr' with a # diskfile entry like ``host /usr gnutar-root', but you don't # want to backup /usr/tmp, your exclude list should contain # the pattern `./tmp', as this is relative to the `/usr' above. # Please refer to the man-page of gnutar for more information. # If a relative pathname is specified as the exclude list, # it is searched from within the directory that is # going to be backed up. # Default: include all files # holdingdisk - should the holding disk be used for this dump. Useful for # dumping the holding disk itself. Default: [holdingdisk auto] # "never" - Never use the holding disk. # "auto" - Use the holding disk if possible. # "required" - Always use the holding disk. # ignore - do not back this filesystem up. Useful for sharing a single # disklist in several configurations. # index - keep an index of the files backed up. Default: [index no] # kencrypt - encrypt the data stream between the client and server. # Default: [kencrypt no] # maxdumps - max number of concurrent dumps to run on the client. # Default: [maxdumps 1] # maxpromoteday - max number of day for a promotion, set it 0 if you don't # want promotion, set it to 1 or 2 if your disk get # overpromoted. # Default: [10000] # priority - priority level of the dump. Valid levels are "low", "medium" # or "high". These are really only used when Amanda has no # tape to write to because of some error. In that "degraded # mode", as many incrementals as will fit on the holding disk # are done, higher priority first, to insure the important # disks are at least dumped. Default: [priority medium] # 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 # /opt/amanda/var/amanda/gnutar-lists for GNUTAR.). # Default: [record yes] # skip-full - skip the disk when a level 0 is due, to allow full backups # outside Amanda, eg when the machine is in single-user mode. # skip-incr - skip the disk when the level 0 is NOT due. This is used in # archive configurations, where only full dumps are done and # the tapes saved. # starttime - delay the start of the dump? Default: no delay # strategy - set the dump strategy. Valid strategies are currently: # "standard" - the standard one. # "nofull" - do level 1 dumps every time. This can be used, # for example, for small root filesystems that # only change slightly relative to a site-wide # prototype. Amanda then backs up just the # changes. # "noinc" - do level 0 dumps every time. # "skip" - skip all dumps. Useful for sharing a single # disklist in several configurations. # "incronly" - do only incremental dumps. This is similar # to strategy 'nofull', but will increase # the dump level as usual. Full dumps will # 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. define dumptype global { comment "Global definitions" # This is quite useful for setting global parameters, so you don't have # to type them everywhere. All dumptype definitions in this sample file # do include these definitions, either directly or indirectly. # There's nothing special about the name `global'; if you create any # dumptype that does not contain the word `global' or the name of any # other dumptype that contains it, these definitions won't apply. # Note that these definitions may be overridden in other # dumptypes, if the redefinitions appear *after* the `global' # dumptype name. # You may want to use this for globally enabling or disabling # indexing, recording, etc. Some examples: # index yes # record no # split_diskbuffer "/raid/amanda" # fallback_splitsize 64m index yes record yes auth "krb5" holdingdisk required } define dumptype disk-nocomp { global comment "Disk to Tape" compress client fast } define dumptype disk-comp { disk-nocomp comment "Disk to Disk" compress client fast } define dumptype afs-nocomp { global comment "afs to Tape" program "GNUTAR" } define dumptype afs-comp { afs-nocomp comment "afs to disk" compress client fast } # network interfaces # # These are referred to by the disklist file. They define the attributes # of the network interface that the remote machine is accessed through. # Notes: - netusage above defines the attributes that are used when the # disklist entry doesn't specify otherwise. # - the values below are only samples. # - specifying an interface does not force the traffic to pass # through that interface. Your OS routing tables do that. This # is just a mechanism to stop Amanda trashing your network. # Attributes are: # use - bandwidth above which amanda won't start # backups using this interface. Note that if # a single backup will take more than that, # amanda won't try to make it run slower! define interface local { comment "a local disk" use 10000000 kbps } define interface eth { comment "GBit ethernet" use 1000000 kbps } # You may include other amanda configuration files, so you can share # dumptypes, tapetypes and interface definitions among several # configurations. #includefile "/opt/amanda/etc/amanda/amanda.conf.main"
amdump: start at Fr 1. Jun 19:48:57 CEST 2007 amdump: datestamp 20070601 amdump: starttime 20070601194857 planner: pid 12584 executable /opt/amanda/libexec/planner version 2.5.2 planner: build: VERSION="Amanda-2.5.2" planner: BUILT_DATE="Fr 1. Jun 16:32:17 CEST 2007" planner: BUILT_MACH="Linux kerberos 2.6.16 #1 SMP Thu Aug 3 12:46:53 CEST 2006 x86_64 GNU/Linux" planner: CC="gcc" planner: CONFIGURE_COMMAND="'./configure' '--with-user=amanda' '--with-group=amanda' '--without-bsd-security' '--without-ipv6' '--with-krb5-security' '--with-buffered-dump' '--with-maxtapeblocksize=32' '--with-gnuplot' '--prefix=/opt/amanda' '--with-config=Daily' '--enable-threads=posix' '--with-gnutar=/opt/amanda/sbin/gtar-wrapper.pl'" planner: paths: bindir="/opt/amanda/bin" sbindir="/opt/amanda/sbin" planner: libexecdir="/opt/amanda/libexec" mandir="/opt/amanda/man" planner: AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" planner: CONFIG_DIR="/opt/amanda/etc/amanda" DEV_PREFIX="/dev/" planner: RDEV_PREFIX="/dev/" DUMP="/sbin/dump" planner: RESTORE="/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF planner: XFSDUMP="/sbin/xfsdump" XFSRESTORE="/sbin/xfsrestore" planner: VXDUMP=UNDEF VXRESTORE=UNDEF SAMBA_CLIENT=UNDEF planner: GNUTAR="/opt/amanda/sbin/gtar-wrapper.pl" planner: COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip" planner: LPRCMD="/usr/bin/lpr" MAILER="/usr/bin/Mail" planner: listed_incr_dir="/opt/amanda/var/amanda/gnutar-lists" planner: defs: DEFAULT_SERVER="kerberos" DEFAULT_CONFIG="Daily" planner: DEFAULT_TAPE_SERVER="kerberos" HAVE_MMAP NEED_STRSTR planner: HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE planner: AMANDA_DEBUG_DAYS=4 KRB5_SECURITY RSH_SECURITY planner: CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP planner: COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" planner: COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" READING CONF FILES... driver: pid 12585 executable /opt/amanda/libexec/driver version 2.5.2 planner: timestamp 20070601194857 planner: time 0.002: startup took 0.002 secs SENDING FLUSHES... ENDFLUSH SETTING UP FOR ESTIMATES... planner: time 0.002: setting up estimates for kerberos:afs:user.testuser driver: tape size 10485760 setup_estimate: kerberos:afs:user.testuser: command 0, options: none last_level 1 next_level0 7 level_days 6 getting estimates 0 (-2) 1 (-2) -1 (-2) planner: time 0.002: setting up estimates took 0.000 secs GETTING ESTIMATES... driver: adding holding disk 0 dir /amanda/holding size 52428800 chunksize 2097152 reserving 0 out of 52428800 for degraded-mode dumps driver: send-cmd time 0.088 to taper: START-TAPER 20070601194857 driver: started dumper0 pid 12588 driver: send-cmd time 0.088 to dumper0: START 20070601194857 driver: start time 0.089 inparallel 1 bandwidth 11000600 diskspace 52428800 dir OBSOLETE datestamp 20070601194857 driver: drain-ends tapeq FIRST big-dumpers sssS taper: pid 12587 executable taper version 2.5.2 taper: page size = 4096 taper: buffer size is 32768 dumper: pid 12588 executable dumper0 version 2.5.2 changer: opening pipe to: /opt/amanda/libexec/chg-disk -info changer: opening pipe to: /opt/amanda/libexec/chg-disk -slot current changer: opening pipe to: /opt/amanda/libexec/chg-disk -slot next planner: time 0.236: got partial result for host kerberos disk afs:user.testuser: 0 -> -2K, 1 -> -2K, -1 -> -2K taper: slot: 1 wrote label `TST001L0' date `20070601194857' driver: result time 0.237 from taper: TAPER-OK driver: state time 0.237 free kps: 11000600 space: 52428800 taper: idle idle-dumpers: 1 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle driver: interface-state time 0.237 if default: free 600 if local: free 10000000 if eth: free 1000000 driver: hdisk-state time 0.237 hdisk 0: free 52428800 dumpers 0 planner: time 0.298: got partial result for host kerberos disk afs:user.testuser: 0 -> 1616K, 1 -> -2K, -1 -> -2K planner: time 0.390: got partial result for host kerberos disk afs:user.testuser: 0 -> 1616K, 1 -> 150K, -1 -> -2K planner: time 0.391: got result for host kerberos disk afs:user.testuser: 0 -> 1616K, 1 -> 150K, -1 -> -2K planner: time 0.392: getting estimates took 0.389 secs FAILED QUEUE: empty DONE QUEUE: 0: kerberos afs:user.testuser ANALYZING ESTIMATES... pondering kerberos:afs:user.testuser... next_level0 7 last_level 1 (not due for a full dump, picking an incr level) pick: size 150 level 1 days 6 (thresh 323K, 1 days) curr level 1 nsize 150 csize 54 total size 153 total_lev0 0 balanced-lev0size 35 INITIAL SCHEDULE (size 153): kerberos afs:user.testuser pri 1 lev 1 nsize 150 csize 54 DELAYING DUMPS IF NEEDED, total_size 153, tape length 20971520 mark 1 delay: Total size now 153. PROMOTING DUMPS IF NEEDED, total_lev0 0, balanced_size 35... planner: time 0.392: analysis took 0.000 secs GENERATING SCHEDULE: -------- DUMP kerberos ffffffff9ffeffffffff00 afs:user.testuser 20070601194857 1 1 2007:6:1:14:6:13 150 54 0 1024 -------- driver: flush size 0 driver: started chunker0 pid 12661 driver: send-cmd time 0.393 to chunker0: START 20070601194857 driver: send-cmd time 0.393 to chunker0: PORT-WRITE 00-00001 /amanda/holding/20070601194857/kerberos.afs:user.testuser.1 kerberos ffffffff9ffeffffffff00 afs:user.testuser 1 2007:6:1:14:6:13 2097152 GNUTAR 128 |;auth=krb5;compress-fast;index; chunker: pid 12661 executable chunker0 version 2.5.2 driver: result time 0.399 from chunker0: PORT 51526 driver: send-cmd time 0.399 to dumper0: PORT-DUMP 00-00001 51526 kerberos ffffffff9ffeffffffff00 afs:user.testuser NODEVICE 1 2007:6:1:14:6:13 GNUTAR X X X |;auth=krb5;compress-fast;index; send request: ---- SERVICE sendbackup OPTIONS features=ffffffff9ffeffffffff00;hostname=kerberos;config=Daily; GNUTAR afs:user.testuser 1 2007:6:1:14:6:13 OPTIONS |;auth=krb5;compress-fast;index; ---- got response: ---- CONNECT DATA 499999 MESG 499998 INDEX 499997 OPTIONS features=ffffffff9ffeffffffff00; ---- driver: state time 0.584 free kps: 10999576 space: 52428672 taper: idle idle-dumpers: 0 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 0.584 if default: free 0 if local: free 10000000 if eth: free 1000000 driver: hdisk-state time 0.584 hdisk 0: free 52428672 dumpers 1 driver: result time 0.584 from dumper0: DONE 00-00001 150 54 0 "[sec 0.088 kb 54 kps 609.5 orig-kb 150]" driver: finished-cmd time 0.585 dumper0 dumped kerberos:afs:user.testuser driver: send-cmd time 0.585 to chunker0: DONE 00-00001 driver: state time 0.585 free kps: 10999576 space: 52428672 taper: idle idle-dumpers: 0 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 0.585 if default: free 0 if local: free 10000000 if eth: free 1000000 driver: hdisk-state time 0.585 hdisk 0: free 52428672 dumpers 1 driver: result time 0.585 from chunker0: DONE 00-00001 54 "[sec 0.184 kb 54 kps 467.4]" driver: finished-cmd time 0.585 chunker0 chunked kerberos:afs:user.testuser driver: send-cmd time 0.586 to taper: FILE-WRITE 00-00002 /amanda/holding/20070601194857/kerberos.afs:user.testuser.1 kerberos ffffffff9ffeffffffff00 afs:user.testuser 1 20070601194857 0 taper: r: [buf 0:=E]: state 0-19:E driver: startaflush: FIRST kerberos afs:user.testuser 86 10485760 taper: r: [buf 0:=f]: state 0:f 1-19:E taper: r: [buf 0:=F32768]: state 0:F 1-19:E taper: r: [buf 1:=f]: state 0:F 1:f 2-19:E taper: r: [buf 2:=f]: state 0-1:F 2:f 3-19:E taper: w: [buf 0:=E]: state 0:E 1-2:F 3-19:E taper: w: [buf 1:=E]: state 0-1:E 2:F 3-19:E taper: w: [buf 2:=E]: state 0-19:E taper: reader-side: got label TST001L0 filenum 1 driver: state time 0.588 free kps: 11000600 space: 52428714 taper: writing idle-dumpers: 1 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 0.588 if default: free 600 if local: free 10000000 if eth: free 1000000 driver: hdisk-state time 0.588 hdisk 0: free 52428714 dumpers 0 driver: result time 0.588 from taper: DONE 00-00002 TST001L0 1 "[sec 0.002 kb 64 kps 30403.8 {wr: writers 3 rdwait 0.000 wrwait 0.000 filemark 0.000}]" driver: finished-cmd time 0.589 taper wrote kerberos:afs:user.testuser driver: state time 0.589 free kps: 11000600 space: 52428800 taper: idle idle-dumpers: 1 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 0.589 if default: free 600 if local: free 10000000 if eth: free 1000000 driver: hdisk-state time 0.589 hdisk 0: free 52428800 dumpers 0 driver: QUITTING time 0.589 telling children to quit driver: send-cmd time 0.589 to dumper0: QUIT driver: send-cmd time 0.589 to taper: QUIT taper: DONE [idle wait: 0.349 secs] taper: writing end marker. [TST001L0 OK kb 96 fm 1] driver: FINISHED time 1.595 amdump: end at Fr 1. Jun 19:48:58 CEST 2007 0 0 0 0 0 0 0
DISK planner kerberos afs:user.testuser START planner date 20070601194857 WARNING planner tapecycle (6) <= runspercycle (6) START driver date 20070601194857 STATS driver hostname kerberos WARNING planner Last full dump of kerberos:afs:user.testuser on tape TST006L0 overwritten in 2 runs. STATS driver startup time 0.088 START taper datestamp 20070601194857 label TST001L0 tape 0 FINISH planner date 20070601194857 time 0.392 SUCCESS dumper kerberos afs:user.testuser 20070601194857 1 [sec 0.088 kb 54 kps 609.5 orig-kb 150] SUCCESS chunker kerberos afs:user.testuser 20070601194857 1 [sec 0.184 kb 54 kps 467.4] STATS driver estimate kerberos afs:user.testuser 20070601194857 1 [sec 0 nkb 182 ckb 96 kps 1024] SUCCESS taper kerberos afs:user.testuser 20070601194857 1 [sec 0.002 kb 64 kps 30403.8 {wr: writers 3 rdwait 0.000 wrwait 0.000 filemark 0.000}] INFO taper tape TST001L0 kb 96 fm 1 [OK] FINISH driver date 20070601194857 time 1.595