>>>> So, if you want to do the deep dive to try to debug that quirk...
> >>>> the next step will be to look through the
> >>>> /var/log/amanda/Daily/amdump.20181112*
> >>>> log file (assuming the run in question started after midnight
> &
>>>> the next step will be to look through the
>>>> /var/log/amanda/Daily/amdump.20181112*
>>>> log file (assuming the run in question started after midnight this
>>>> morning; if not the datetime-stamp would be 2018* of course).
>>>
>&
On Monday 12 November 2018 15:44:04 Nathan Stratton Treadway wrote:
> On Mon, Nov 12, 2018 at 15:18:05 -0500, Gene Heskett wrote:
> > > So, if you want to do the deep dive to try to debug that quirk...
> > > the next step will be to look through the
> > > /var/lo
On Mon, Nov 12, 2018 at 16:29:45 -0500, Jon LaBadie wrote:
> On Mon, Nov 12, 2018 at 03:44:04PM -0500, Nathan Stratton Treadway wrote:
> > (Look at the top of the output of "amadmin Daily status"; the very first
> > line should be
> > Using: [PATH...]/amdump.1
> > , where [PATH...] is the path t
/var/log/amanda/Daily/amdump.20181112*
> > > log file (assuming the run in question started after midnight this
> > > morning; if not the datetime-stamp would be 2018* of course).
> >
> > It did, I have some other stuff so it isn't started till about 03:05.
> &
On Mon, Nov 12, 2018 at 15:18:05 -0500, Gene Heskett wrote:
> > So, if you want to do the deep dive to try to debug that quirk... the
> > next step will be to look through the
> > /var/log/amanda/Daily/amdump.20181112*
> > log file (assuming the run in question sta
g to do an incremental on
> that run, but only tells you what level it would plann to do if it
> ends up deciding to do an incremental for that DLE.
>
> However, off hand I would have expected colyote:/var to be mentioned
> in the "promoted from N days ahead" lines, but it&#
On Mon, Nov 12, 2018 at 13:56:33 -0500, Chris Nighswonger wrote:
> backup@scriptor:~ amadmin campus info host dev
>
> Current info for host dev:
> Stats: dump rates (kps), Full: 6015.9, 5898.2, 5771.4
> Incremental: 1658.2, 1456.6, 343.4
> compressed size, Full:
Was "All level 0 on the same run?"
The old thread was getting a bit stranded...
On Sat, Nov 10, 2018 at 5:03 PM Nathan Stratton Treadway
wrote:
> On Sat, Nov 10, 2018 at 11:39:58 -0500, Chris Nighswonger wrote:
> > I think that is output from one of Gene's systems, but here is the latest
> > fr
On Mon, Nov 12, 2018 at 1:50 PM Nathan Stratton Treadway
wrote:
> On Mon, Nov 12, 2018 at 13:28:15 -0500, Chris Nighswonger wrote:
> > I found the long overdue culprit... It was a windows client using the ZWC
> > community client. The ZWC service had hung (not an uncommon problem) and
> > Amanda
On Mon, Nov 12, 2018 at 13:28:15 -0500, Chris Nighswonger wrote:
> On Sat, Nov 10, 2018 at 5:03 PM Nathan Stratton Treadway
> wrote:
>
> > On Sat, Nov 10, 2018 at 11:39:58 -0500, Chris Nighswonger wrote:
> > > (3 filesystems overdue. The most being overdue 17841 days.)
> > >
> > > Not sure what'
On Sat, Nov 10, 2018 at 5:03 PM Nathan Stratton Treadway
wrote:
> On Sat, Nov 10, 2018 at 11:39:58 -0500, Chris Nighswonger wrote:
> > (3 filesystems overdue. The most being overdue 17841 days.)
> >
> > Not sure what's up with the overdues. There were none prior to breaking
> up
> > the DLEs. It
to do if it ends
up deciding to do an incremental for that DLE.
However, off hand I would have expected colyote:/var to be mentioned in
the "promoted from N days ahead" lines, but it's not there (and all 21
promoted DLEs are listed, so it seems something else is up).
So, if you want
On Mon, Nov 12, 2018 at 06:40:56AM -0500, Gene Heskett wrote:
> amanda@coyote:/root$ /usr/local/sbin/amadmin Daily balance
>
> due-date #fsorig MB out MB balance
> --
> 11/12 Mon1 32963 7875-53.6%
> 11/13 Tue1 768
amanda@coyote:/root$ /usr/local/sbin/amadmin Daily balance
due-date #fsorig MB out MB balance
--
11/12 Mon1 32963 7875-53.6%
11/13 Tue1 7688 7688-54.7%
11/14 Wed2 22109 22109+30.3%
11/1
15 matches
Mail list logo
