> On Nov 16, 2018, at 1:28 PM, Alan Hodgson <ahodg...@lists.simkin.ca> wrote:
>
> On Fri, 2018-11-16 at 11:00 -0800, Chris Miller wrote:
>> Hi Alan,
>>> From: "Alan Hodgson" <ahodg...@lists.simkin.ca>
>>> To: "amanda-users" <amanda-users@amanda.org>
>>> Sent: Friday, November 16, 2018 9:59:29 AM
>>> Subject: Re: Manually flush the holding disk
>>> On Fri, 2018-11-16 at 09:42 -0800, Chris Miller wrote:
>>> # man amflush
>>> amflush [-b] [-f] [--exact-match] [-s] [-D datestamp] [-o
>>> configoption...] config [host [disk...]...]
>>>
>>> .. the first argument to most amanda commands is the configuration name
>> I think that is what I am doing, but I would be happy to learn that I am
>> mistaken. My backup command was "amdump aequitas.tclc.org", so I expect my
>> flush command should be "amflush aequitas.tclc.org". Am I wrong?
>>
>>
>
> If that's the config name then I apologize, it sure looks like a host name.
>
> Maybe try amflush -b aequitas.tclc.org, I know I always use -b but reading
> the man page again now I'm not sure why.
>
> Otherwise, I guess make sure it's using the right config to match the holding
> disk you're looking at.
>
> That's the only ideas I'm having.
>
I usually find about half a dozen abandoned items in my holding disk, over a
year.
If they haven’t flushed themselves automatically after a month or two
(autoflush all),
I just manually delete them
rm -fr /spool1/amanda/daily/201808*
for instance
They seem to come from aborted jobs. Amcleanup cleans log files, but
perhaps it doesn’t touch the holding disk areas?
Deb Baddorf
