On Friday 09 March 2018 12:20:29 Gene Heskett wrote:
> On a rock64 TBE. Locally built 3.3.7p1 here as master, client is
> whatever is in the debian stretch repo's.
>
> I will reboot it, and compose an excludes file by the time another
> dump starts. There is an excludes file now, but it exists bec
On Wed, Nov 22, 2017 at 11:58:12 -0500, Jean-Louis Martineau wrote:
> On 22/11/17 12:56 AM, Nathan Stratton Treadway wrote:
> >> I applied this patch and ran the test again, and "amdump --no-dump
> >>
> > --no-flush" worked just as well as with the previous patch,
And so it turns out that if you turn off autoflush, Amanda will never
flush existing dumps to tape regardless of the flush-threshold-*
settings. Which I guess makes sense. And with "autoflush yes", it
seems to simply flush everything currently on the holding disk
regardless of other settings. So
Hi Jason,
* Jason L Tibbitts III [20180314 11:33]:
> And so it turns out that if you turn off autoflush, Amanda will never
> flush existing dumps to tape regardless of the flush-threshold-*
> settings. Which I guess makes sense. And with "autoflush yes", it
> seems to s
Thanks Paddy. I also had to restart the ZWC service to make the log level
change effective.
So maybe someone who works on the ZWC code can explain what operation might
account for the following differences in log entries. Both are from the
same machine. The backup began failing with the 18/1/2018
> "JM" == Jean-Francois Malouin
> writes:
JM> This is not was I have experienced, at least with 3.3.x.
For the record, my server is 3.5.1.
JM> I've been using the following in some configs with the expected
JM> result:
OK, it's good to know that at some point it's worked for someone.