On Wednesday 31 October 2018 06:32:41 Gene Heskett wrote:

> On Tuesday 30 October 2018 17:56:33 Gene Heskett wrote:
> > On Tuesday 30 October 2018 16:45:50 Nathan Stratton Treadway wrote:
> > > On Tue, Oct 30, 2018 at 15:51:36 -0400, Gene Heskett wrote:
> > > > I just changed the length of the dumpcycle and runs percycle up
> > > > to 10, about last friday while I was makeing the bump* stuff
> > > > more attractive, but the above command returns that the are 5
> > > > filesystens out of date: su amanda -c "/usr/local/sbin/amadmin
> > > > Daily balance"
> > > >
> > > >  due-date  #fs    orig MB     out MB   balance
> > > > ----------------------------------------------
> > > > 10/30 Tue    5          0          0      ---
> > > > 10/31 Wed    1      17355       8958    -45.3%
> > > > 11/01 Thu    2      10896      10887    -33.5%
> > > > 11/02 Fri    4      35944       9298    -43.2%
> > > > 11/03 Sat    4      14122      10835    -33.8%
> > > > 11/04 Sun    3      57736      57736   +252.7%
> > > > 11/05 Mon    2      39947      30635    +87.1%
> > > > 11/06 Tue    8       4235       4215    -74.3%
> > > > 11/07 Wed    4      19503      14732    -10.0%
> > > > 11/08 Thu   32      31783      16408     +0.2%
> > > > ----------------------------------------------
> > > > TOTAL       65     231521     163704     16370
> > > >   (estimated 10 runs per dumpcycle)
> > > >  (5 filesystems overdue. The most being overdue 20 days.)
> > > >
> > > > That last line is disturbing. Ideas anyone? I'll certainly keep
> > > > an eye on it.
> > >
> > > Did you already run today's (10/30's) dump?  Assuming you are
> > > running one dump per day, running the "balance" command after the
> > > dump has occurred generates confusing output, because the output
> > > includes a line for today's date but actually no (new) dumps will
> > > be happening today. So if you are able to run the balance command
> > > before a particular day's dump (but on the day in question), the
> > > output is a little bit more helpful....
> > >
> > > Anyway by "last line" are you talking about the "overdue" line?
> > > "amadmin ... due" should tell you which DLEs are overdue, and you
> > > can then look back through through your Amanda Mail Reports to see
> > > if there's any indication of why they are overdue (especially the
> > > one that's 20 days overdue...)
> > >
> > > Anyway, the other thing that jumps out from the above listing is
> > > the line for 11/4, with a balance of 250%.  We can't tell from the
> > > listing what the relatives sizes of the three DLEs in question
> > > are, though. Here's where a true Amanda expert could advise you
> > > better, but off hand I'd guess that one particule one of those
> > > three DLEs is much larger than all the rest of your DLEs and that
> > > fact is making it hard for the planner to come up with 10
> > > consecutive days of plans that when taken as a group actually work
> > > out to functional cycle....
> > >
> > > ("amadmin ... due" should help you figure out which three DLEs are
> > > scheduled for that day, if you don't already know off hand which
> > > one is super large.)
> > >
> > > Hmmm, it would be interesting to know if the the super-large DLE
> > > is also the one that's 20 days overdue.  Perhaps its so big it
> > > can't fit on a tape, or something?
> > >
> > >                                                   Nathan
> >
> > Its rigged to use 2 40GB vtapes if it has to.  But I found some
> > amandates problems in my kicking the tires so we'll see what it does
> > for tonight's after midnight run.
>
> And my perms & linkages fixes for amandates didn't help a bit, this
> morning after the run, its still showing the same 5 dle's as 21 days
> overdue.
>
> I'll see if I can find the logs, I assume on the clients marked
> guilty?
>
Apparently not on the client, I've read every 20181031 log 
containing /usr/local, no failures there. back to here I guess. Trawl 
thru another 20 megs of logs, no "fail" to be found by grep for this 
mornings date.  Humm, go look in /amandatapes/Dailys/data, and lo, and 
behold even, that backup was done!: Picked out of 65 files:
-rw------- 1 amanda amanda   13353012 Oct 31 03:44 
00064.GO704._usr_local.0

Sooo, lets backup a day, and to slot-26 in that tree.
did a level0 on the 30th
did a level1 on the 29th
did a level0 on the 28th
did a level1 on the 27th

yadda yadda. So just where the hell do I look for these?
root@coyote:/amandatapes/Dailys# su amanda -c "/usr/local/sbin/amadmin 
Daily due"|grep Overdue
Overdue 21 days: shop:/usr/local
Overdue 21 days: shop:/var/amanda
Overdue 21 days: lathe:/usr/local
Overdue 21 days: lathe:/var/amanda
Overdue 21 days: GO704:/var/amanda

So I look in the vtapes, and find its being done too.
Checking for lathe:/var/amanda, its there
Checking for lathe:/usr/local, they've been done too

I think I need a beer and its not even 8am yet...



> > Funny is that 5 machines are still running wheezy, but the default
> > names in both /etc/passwd and in /etc/group don't match! One of then
> > isn't a Wurlitzer, but since they were installed at different times
> > over the history here...  Who knows and I'm too lazy to lock
> > in /var/cache/apt/archives to check  versions. We'll see what
> > happens tonight.
> >
> > > ------------------------------------------------------------------
> > >-- -- ------ Nathan Stratton Treadway  -  natha...@ontko.com  -
> > > Mid-Atlantic region Ray Ontko & Co.  -  Software consulting
> > > services -
> > > http://www.ontko.com/ GPG Key:
> > > http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
> > > Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB
> > > 6239
> >
> > Copyright 2018 by Maurice E. Heskett
>
> Copyright 2018 by Maurice E. Heskett



Copyright 2018 by Maurice E. Heskett
-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Reply via email to