On Sat, Nov 10, 2018 at 5:03 PM Nathan Stratton Treadway <natha...@ontko.com> 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 may just be an artifact. > > With a 5-day dumpcycle that would mean Amanda thinks the last dump took > place 17846-ish days ago: > $ date --date="17846 days ago" > Wed Dec 31 14:24:39 EST 1969 > ... and the date of 1969/12/13 is the "no data saved" placeholder date > within Amanda's info database. > > Anyway, you should be able to identify the three DLEs in question with > amadmin campus due | grep "Overdue" > and then use "amadmin campus info [...]" to see what amanda has recorded > about them. > > 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 was missing backups from it. If I had been paying attention to the nightly reports, I would have investigated it sooner. However, it does beg the question: That DLE is NOT 49 years overdue... So where in the world did the planner get that idea from? I'll check the balance again after tonight's run. Kind regards, Chris
