I think the bug you describe is fixed in the new amanda 3.4.x. I am
preparing a new package for sid and for stretch-backports.
Are you interested in testing it?
On 26/07/17 16:18, Winston Sorfleet wrote:
>
> Tried this in yesterday's cron job, but turning autoflush to "yes" did
> not fix the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tried this in yesterday's cron job, but turning autoflush to "yes" did
not fix the problem. My understanding is that it shouldn't anyways;
autoflush must be set to "yes" if taperflush is greater than 0, but that
wasn't the case.
On 2017-07-24 11:29
I am not certain that I understand your problem, so beer with me.
From advanced.conf:
On 24/07/17 16:05, Winston Sorfleet wrote:
> # reserve 30 # percent
> # This means save at least 30% of the holding disk space for degraded
> # mode backups.
>
> autoflush no
> # if autoflush is set to yes,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2017-07-24 08:17 AM, Jose M Calhariz wrote:
> Hi, > > Can you please attach your amanda,conf file and a listing of the >
contents of your > holdingdisk? > > Kind regards > Jose M Calhariz Hi,
The holding disk is just a pile of TARs in DLE format,
Hi,
Can you please attach your amanda,conf file and a listing of the
contents of your
holdingdisk?
Kind regards
Jose M Calhariz
On 23/07/17 21:58, Winston Sorfleet wrote:
> Package: amanda-server
> Version: 1:3.3.9-5
> Severity: normal
> Tags: newcomer
>
> Dear Maintainer,
>
> Amdump leaves
Package: amanda-server
Version: 1:3.3.9-5
Severity: normal
Tags: newcomer
Dear Maintainer,
Amdump leaves dumps on holding disk despite taperflush being 0 (and thus
anything above 0% capacity of a single volume is supposed to be flushed
to tape).
E.g.
/usr/sbin/amdump vtl
Mailed output at job
6 matches
Mail list logo
