On 2006-07-03 13:11, Luis Rodrigues wrote:
On Mon, 03 Jul 2006 12:40:24 +0200
Alexander Jolk <alexj AT buf DOT com> wrote:
Luis Rodrigues wrote:
One something more weird:
You seem to have 2 entries for those DLE's: one succeeded, one missing.
How did you get 2 lines for one DLE???
Thats what I would like to know.
autoflush, by any chance?
autoflush? I did't set in any place.
Luis
My config for this is:
org "ess" # your organization name for reports
mailto "backup" # space separated list of operators at your site
dumpuser "backup" # the user to run dumps under
#
inparallel 8 # maximum dumpers that will run in parallel
netusage 80000 # maximum net bandwidth for Amanda, in KB per sec
displayunit "m"
# a filesystem is due for a full backup once every <dumpcycle> days
dumpcycle 7 days # a week cycle
runspercycle 1 # only run once a week (full dump)
tapecycle 31 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 * (level-1)**bumpmult
runtapes 4 #a backup run should not take more than 2 tapes
tapedev "/dev/nst0" # Linux @ tuck, important: norewinding
tpchanger "chg-zd-mtx" # the tape-changer glue script, see TAPE.CHANGERS
changerfile "/etc/amanda/weekly/changer"
changerdev "/dev/sg4"
tapetype LT01 # what kind of tape it is (see tapetypes below)
labelstr "^ESSDUMP[0-9][0-9]*$" # label constraint regex: all tapes must match
diskdir "/BACKUP/holding" # where the holding disk is
infofile "/var/lib/amanda/weekly/curinfo" # database filename
logfile "/var/log/amanda/weekly/log" # log filename
# where the index files live
indexdir "/var/lib/amanda/weekly/index"
This seems to be a veeeeeeerrrrry old config.
It still uses parameter "diskdir" which is deprecated for
over 8 years now. Moreover in 2.5.0 is does't exist anymore.
Also the comments about infofile being a database filename (which
is was in Amanda 2.3 or so -- it is a directory now), seems to
indicate that.
On the other hand, you are using "displayunit" which exists only
in very recent releases :-)
That said, you should inspect the debug files on the client
and see at which time each of those "double" backups is created.
And how that is possible???
Also in the server log file "amdump.X", you should find more info
where those double backup images are coming from.
--
Paul Bijnens, xplanation Technology Services Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
