Deb  (from phone)

On Jul 14, 2013, at 5:21 AM, "Stefan G. Weichinger" <[email protected]> wrote:

> 
> Your mail got tagged as spam by Todd's amanda.org-server:
> 
> Content analysis details:   (6.2 points, 5.0 required)
> 
> pts rule name              description
> ---- ----------------------
> --------------------------------------------------
> 0.2 MR_NOT_ATTRIBUTED_IP   Beta rule: an non-attributed IPv4 found in
>                            headers
> -0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
>                            trust
>                            [206.46.173.7 listed in list.dnswl.org]
> 1.0 MR_DIFF_MID            MR_DIFF_MID
> 4.0 HDRS_LCASE             Odd capitalization of message header
> 1.0 MANY_HDRS_LCASE        Odd capitalization of multiple message headers
> 
> 
> The actual mail was:
> 
> 
> Am 14.07.2013 06:44, schrieb Jon LaBadie:
>> On Sat, Jul 13, 2013 at 01:34:53PM +0200, Stefan G. Weichinger wrote:
>>> 
>>> Is there a parameter to make amanda wait with writing to tape until all
>>> the dumps are on the holding list?
>>> 
>>> I have played with flush-threshold-dumped & flush-threshold-scheduled
>>> ... so far no success. The LTO4 starts to stop and go while there are
>>> multiple dumps coming in .. which is to be avoided.
>> 
>> I've not used them, but I'm surprised that something
>> like this doesn't work.
>> 
>> autoflush all
>> flush-threshold-scheduled 100
>> flush-threshold-dumped     98
>> taperflush 5
> 
> gotta play some more with those parameters
> 
>> 

How about this (just guessing):
Flush- threshold-scheduled 100x (# tapes you normally use)
Flush-threshold-dumped. Same number. 
Taperflush 0

My interpretation would imply that it waits to start taping till there is 
enough dumped to fill normal tapes. But when all dumps have finished, the 
taperflush 0 says "send it all to tape; don't save any for the next run".  
   I don't know if Amanda will interpret it that way, but it's what I would 
try. 
Deb Baddorf
Fermilab
> 

Reply via email to