----- Original Message -----
From: "Jon LaBadie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 17, 2003 12:22 PM
Subject: Re: more doubts
> I don't think your assumption is correct. I think runspercycle
> "ignores" the units part. So it was thinking you had a total of
> 5 runs per dumpcycle.
I read it somewhere it this mailing list that runspercycle does
compute based on units specified. Also, amadmin balance command
showed "estimated 35 runs per dumpcycle" in the last line when
I had runspercycle as 5 weeks. When I removed 'weeks' from that
line -- then it showed correct value -- 5 runs per dumpcycle.
> No, I think you have a problem there. A problem that has little,
> if anything, to do with the policies you were using.
>
> I suspect things like:
>
> - those DLE's are simply too big to ever fit on a single tape,
> an absolute requirement for amanda to do the initial, and
> future, level 0's
I checked those DLE's they are not that big. All of them average
around 5 GB in compressed state.
> - a connection problem to those systems if all DLE's are failing
> for particular hosts
I don't think I have connection issues here. All the hosts were
accessable (because I could see clients sending estimates in the
log files etc.)
> Time to get deeper into the reports, logs, and in /tmp/amanda, debug
files.
Attached to this email is snippet of amdump log file. Amanda identified
total size of approx 25 GB to be backed up. Whereas by tape could could
only take in approx 19 GB (though it is 12/24 GB tape??) and it had to
drop certain partitions. But why is amanda dropping just those partitions
regularly..I fail to understand and they are not that big as I said before.
I can send you full amdump file if you require.
Thanks again!
INITIAL SCHEDULE (size 25877861):
machine2 /h2 pri 12344 lev 0 size 4665330
machine2 //windows/users pri 12344 lev 0 size 4568817
machine2 //windows/UsersG3 pri 12344 lev 0 size 3165049
machine2 /h pri 12343 lev 0 size 2707285
machine2 /h3 pri 12342 lev 0 size 4665330
localhost /h pri 12342 lev 0 size 2451490
machine2 //windows/UsersG2 pri 2 lev 1 size 3468640
machine1 /vm pri 2 lev 1 size 11227
machine1 /vw pri 2 lev 1 size 7229
localhost /rp pri 2 lev 1 size 2695
machine2 /vw pri 1 lev 1 size 1412
localhost /vw pri 1 lev 1 size 1348
machine1 /vl pri 0 lev 2 size 104474
machine1 /h pri 0 lev 2 size 45821
machine2 /vl pri 0 lev 1 size 8921
localhost /vl pri 0 lev 1 size 219
DELAYING DUMPS IF NEEDED, total_size 25877861, tape length 1976320 mark 111
planner: FAILED machine2 /h2 20031017 0 [dump larger than tape, but cannot incremental
dump new disk]
planner: FAILED machine2 //windows/users 20031017 0 [dump larger than tape, but cannot
incremental dump new disk]
planner: FAILED machine2 //windows/UsersG3 20031017 0 [dump larger than tape, but
cannot incremental dump new disk]
planner: FAILED machine2 /h 20031017 0 [dump larger than tape, but cannot incremental
dump new disk]
planner: FAILED machine2 /h3 20031017 0 [dump larger than tape, but cannot incremental
dump new disk]
planner: FAILED localhost /h 20031017 0 [dump larger than tape, but cannot incremental
dump new disk]
planner: FAILED machine2 //windows/UsersG2 20031017 1 [dump larger than tape, skipping
incremental]
delay: Total size now 184919.
