On Thursday 09 February 2006 03:54, uwe.kaufmann AT infoconsult DOT nu wrote:
>Dear Listers,
>
>I have a general question concerning the vtapes mechanisms and vtape
> length.
>
>I configured an amanda server ("minerva", amanda-2.4.5-2, SuSE 10.0)
> with "chg-disk" and 14 slots.
>
>In the beginning there are a lot of "lev 0 failed", obviously, because
> I am dealing with >100G data and each slot has only 18G (to fit on
> tape later on).
>
>But where does the "lev 0 FAILED [out of tape]" comes from?. I thought
> that amanda would calculate properly the relation between data and
> tapelength.
>
Because amanda will try anyway. WHen using vtapes, amanda doesn't wite
till an EOT signal is obtained frrom the drive. Its actually derived
from a comparison of the amount of data written and the size given in
the 'tapetype'.
This another way of saying that one can define a tapetype whose size is
considerably larger than what would fit on the drive if all vtapes were
filled to that given size.
I think the common way around that is to give it enough room in the
tapetype for it to do the level 0, but only expose one such 'needs a
level 0' per nightly run until they have all been exposed. This is a
way to help amanda achieve a somwehat workable initial 'balance'. In
any event, there must be room enough in the tapetype size setting for
it to actually do the level 0 at some point in the dumpcycle. If the
drive holding the vtapes becomes full, which it did on me when I first
started, then I simply removed the oldest backup that was not in the
current dumpcycle by hand and from the tapelist until such time as
you've hit the optimum point of having the longest backup history that
will fit on the vtapes partition. I started with 30 vtapes, and wound
up with 21, and current usage is about 81% of that partition, with a 4
day dumpcycle. Way overkill in terms of retained history, but then I'm
not a business, just a paranoid old coot with a small home network.
The sizes of the level 0's can be curtailed by a considerable amount by
simply breaking them up into subdir entries in the disklist. My
largest single level 0 last night was a bit over 10GB un-compressed,
and about 3.1GB compressed, my /usr/src dir on this box. I need to go
play space patrol again, too many kernel trees since I build and run
the latest of linus's releases as they are released. So thats a new
one every 10 days to 2 weeks. :)
>Thank you for any enlightenment of my poor spirit.
>
>BTW: Great wiki and docs, thanks to all who spent effort, really
> helpful!
>
>Cheers
>Uwe
>
>
>Additional info
>--------------------
>The report:
>
>These dumps were to tape slot3.
>*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
>Some dumps may have been left in the holding disk.
>Run amflush to flush them to tape.
>The next tape Amanda expects to use is: a new tape.
>The next new tape already labelled is: slot4.
>
>FAILURE AND STRANGE DUMP SUMMARY:
> hercules /samba/LAGERVERSAND lev 0 FAILED [dumps too big, 109335
> KB, but cannot incremental dump new disk]
> hercules //Edi/TC4000/IBDasi lev 0 FAILED [dumps too big, 111909
> KB, but cannot incremental dump new disk]
> hercules /KT_EIN_PRO lev 0 FAILED [dumps too big, 576825 KB, but
> cannot incremental dump new disk]
> hercules /US_LE lev 0 FAILED [dumps too big, 584480 KB, but cannot
>incremental dump new disk]
> hercules /K_EIN_NO4 lev 0 FAILED [dumps too big, 596835 KB, but
> cannot incremental dump new disk]
> hercules /KONST lev 0 FAILED [out of tape]
>
>
>STATISTICS:
> Total Full Incr.
> -------- -------- --------
>Estimate Time (hrs:min) 0:01
>Run Time (hrs:min) 4:14
>Dump Time (hrs:min) 4:09 4:09 0:00
>Output Size (meg) 18852.6 18851.7 0.9
>Original Size (meg) 36786.0 36780.9 5.1
>Avg Compressed Size (%) 51.2 51.3 16.7 (level:#disks
> ...) Filesystems Dumped 24 16 8 (1:8)
> Avg Dump Rate (k/s) 1290.8 1291.0 412.0
>
>Tape Time (hrs:min) 0:10 0:10 0:00
>Tape Size (meg) 16074.0 16073.1 0.9
>Tape Used (%) 87.3 87.3 0.0 (level:#disks
> ...) Filesystems Taped 23 15 8)
>Avg Tp Write Rate (k/s) 28260.4 28271.6 3385.5
>
>USAGE BY TAPE:
> Label Time Size % Nb
> slot3 0:10 16459733k 87.3 23
>
>
>NOTES:
> planner: Adding new disk hercules:/samba/CONTROLLING.
> planner: Adding new disk hercules:/samba/EINVERKAUF.
> planner: Adding new disk hercules:/samba/FIBU.
> planner: Adding new disk hercules:/samba/LAGERVERSAND.
> planner: Adding new disk hercules:/samba/LOGISTIK.
> planner: Adding new disk hercules:/samba/PERSONAL.
> planner: Adding new disk hercules:/samba/PUBLIC.
> planner: Adding new disk hercules:/samba/QM.
> planner: Adding new disk hercules:/samba/SPDATEN.
> planner: Adding new disk hercules:/US_LE.
> planner: Adding new disk hercules:/US_SP.
> planner: Adding new disk hercules:/US_ALL.
> planner: Adding new disk hercules://Edi/TC4000/IBDasi.
> planner: Adding new disk hercules:/KONST.
> planner: Adding new disk hercules:/KT_EIN_PRO.
> planner: Adding new disk hercules:/K_EIN_DAT.
> planner: Adding new disk hercules:/K_EIN_YAZ.
> planner: Adding new disk hercules:/K_EIN_NO3.
> planner: Adding new disk hercules:/K_EIN_NO4.
> planner: Adding new disk hercules:/K_EIN_NO5.
> planner: Adding new disk hercules:/K_EIN_REST.
> taper: tape slot3 kb 18874336 fm 24 writing file: No space left on
> device driver: going into degraded mode because of tape error.
>
>
>DUMP SUMMARY:
> DUMPER STATS
> TAPER STATS
>HOSTNAME DISK L ORIG-kB OUT-kB COMP% MMM:SS KB/s
> MMM:SS KB/s
>----------------------- ------------------------------------------
>--------------
>hercules -00/IBDasi 0 FAILED
>--------------------------------------------------
>hercules /KONST 0 7004350 2845316 40.6 48:12 984.0
> FAILED ------
>hercules -T_EIN_PRO 0 FAILED
>--------------------------------------------------
>hercules /K_EIN_DAT 0 2420200 668636 27.6 13:25 830.8
> 0:25 26947.6
>hercules /K_EIN_NO3 0 4808620 2728822 56.7 48:53 930.3
> 1:31 29971.7
>hercules /K_EIN_NO4 0 FAILED
>--------------------------------------------------
>hercules /K_EIN_NO5 0 1376530 928100 67.4 11:24 1357.8
> 0:42 22017.1
>hercules -_EIN_REST 0 5091500 2850241 56.0 37:29 1267.3
> 1:38 29178.6
>hercules /K_EIN_YAZ 0 1532850 431798 28.2 7:25 970.3
> 0:12 35824.0
>hercules /US_ALL 0 1724670 1096114 63.6 7:04 2586.7
> 0:41 26437.9
>hercules /US_LE 0 FAILED
>--------------------------------------------------
>hercules /US_SP 0 3272150 1987199 60.7 20:16 1634.5
> 1:15 26461.3
>hercules /US_ZE 1 680 56 8.2 0:00 208.2
> 0:00 1653.4
>hercules -CKUP_FIBU 1 10 1 10.0 0:00 0.0
> 0:00 982.3
>hercules -NTROLLING 0 94230 28912 30.7 0:50 579.4
> 0:00 65303.9
>hercules -INVERKAUF 0 94900 29058 30.6 0:35 834.8
> 0:00 99588.0
>hercules -a/EMPFANG 1 390 28 7.2 0:00 164.8
> 0:00 955.5
>hercules -amba/FIBU 0 253400 108144 42.7 1:38 1108.7
> 0:01 91501.7
>hercules /samba/GL 1 10 1 10.0 0:00 0.0
> 0:00 1168.2
>hercules -/Projekte 1 480 480 100.0 0:00 3401.6
> 0:00 5424.3
>hercules -ERVERSAND 0 FAILED
>--------------------------------------------------
>hercules -/LOGISTIK 0 383070 190077 49.6 2:05 1523.7
> 0:03 68083.1
>hercules -/PERSONAL 0 1815850 325692 17.9 13:58 388.8
> 0:08 42102.1
>hercules -RODUKTION 1 130 12 9.2 0:00 125.0
> 0:00 451.3
>hercules -ba/PUBLIC 0 5012140 3568604 71.2 22:57 2591.8
> 2:13 26848.2
>hercules /samba/QM 0 1461410 1212718 83.0 5:23 3752.8
> 0:45 26729.4
>hercules /samba/QS 1 3510 307 8.7 0:01 237.3
> 0:00 4631.8
>hercules -a/SPDATEN 0 1317740 304731 23.1 7:42 660.0
> 0:07 42685.4
>hercules -RKZEUGBAU 1 60 2 3.3 0:00 17.0
> 0:00 104.8
>
>(brought to you by Amanda version 2.4.5)
>
>
>--------------------
>My amanda.conf:
>
>org "normal" # your organization name for reports
>dumpuser "amanda" # the user to run dumps under
>inparallel 2 # maximum dumpers that will run in parallel (max 63)
>netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per sec
>dumpcycle 1 week # the number of days in the normal dump cycle
>runspercycle 5 # the number of amdump runs in dumpcycle days
>tapecycle 14 tapes # the number of tapes in rotation
>bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
>bumpdays 1 # minimum days at each level
>bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
>etimeout 1800 # 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
>tapebufs 20
>#runtapes 1 # number of tapes to be used in a single run of
>amdump
>tpchanger "chg-disk" # the tape-changer glue script
>tapedev "file:/amandatapes/normal" # vtapes configuration
>changerfile "/var/lib/amanda/normal/changer"
>tapetype HARD-DISK # vtapes configuration
>labelstr "^slot[0-9][0-9]*$" # label constraint regex: all tapes must
>match
>
>holdingdisk hd1 {
> comment "main holding disk"
> directory "/dumps/amanda" # where the holding disk is
> use 100 Gb # how much space can we use on it
> # a non-positive value means:
> # use all space but that value
> chunksize 1Gb # 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
>reserve 30 # percent
>infofile "/var/lib/amanda/normal/curinfo" # database DIRECTORY
>logdir "/var/lib/amanda/normal" # log directory
>indexdir "/var/lib/amanda/normal/index" # index directory
>
># vtape length 18 gbytes
>define tapetype HARD-DISK {
> comment "Dump onto hard disk vtapes"
> length 18432 mbytes
>}
>
>define dumptype global {
> comment "Global definitions"
> index yes
> # record no
>}
>
>define dumptype comp-high-tar {
> global
> comment "very important partitions on fast machines"
> program "GNUTAR"
> compress client best
> priority high
>}
>
>define interface local {
> comment "a local disk"
> use 1000 kbps
>}
>
>define interface eth0 {
> comment "100 Mbps ethernet"
> use 8000 kbps
>}
>
>--------------------
>The slots so far:
>
>minerva:/amandatapes/normal # du -hx --max-depth=1 .
>19G ./slot1 <= first amdump
>8.5G ./slot2 <= amflush
>19G ./slot3 <= second amdump
>2.8G ./slot4 <= amflush
>76K ./slot5
>76K ./slot6
>76K ./slot7
>76K ./slot8
>76K ./slot9
>76K ./slot10
>76K ./slot11
>76K ./slot12
>76K ./slot13
>76K ./slot14
>
>
>____________
>Virus checked by G DATA AntiVirusKit
>Version: AVK 16.5417 from 09.02.2006
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
|
