Hi
I use Amanda 2.4.5 with FreeBSD 4.10, a tapetype DAT72 and a holding
disk. It works smoothly since several years.
But since yesterday I've got some problem with the holding disk and
amanda flush. We forget to flush the disk for several days.
I tried several amanda flush (ALL, A, B
Thomas Vogt wrote:
I use Amanda 2.4.5 with FreeBSD 4.10, a tapetype DAT72 and a holding
disk. It works smoothly since several years.
But since yesterday I've got some problem with the holding disk and
amanda flush. We forget to flush the disk for several days.
I tried several amanda flush
On Fri, 30 Nov 2001 at 10:29pm, Dan Swartzendruber wrote
speaking of which, what have people found to be a good value for
'reserve'? my main
motivation originally was that the original behavior (as you noted) was to
never take any
full dumps if the tape wasn't functional. to avoid
On Fri, 30 Nov 2001 at 1:31pm, BRINER Cedric wrote
the idea that I had is the following
-run amdump without inserting the tape so the data will be stored in
the holding disk
-run amflsuh only if the amount of data on the holdingdisk is higher
than what the tape can store
On Fri, Nov 30, 2001 at 01:31:12PM +0100, BRINER Cedric wrote:
hi,
1)the problem is that each time that I use amdump it use 1.1 tape so
actually it use 2 tapes each time.
Look for the new autoflush option of the tapeio branch.
amdump will flush what is on the holding disk first.
If you set
At 09:32 AM 11/30/01 -0500, Joshua Baker-LePain wrote:
If you do implement this, be sure to set the reserve parameter
accordingly -- the default is 100%, meaning that 100% of the holding disk
is reserved for incremental dumps in degraded modes, i.e. you won't get
*any* full dumps.
speaking of
