Hi Jason, * Jason L Tibbitts III <[email protected]> [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 simply flush everything currently on the holding disk > regardless of other settings. So as far as I can tell, the > flush-threshold-* settings are simply not working as designed. > > What can I tweak to get more insight into how Amanda decides when to > flush existing dumps? I will continue to play with the thresholds to > see if I can get behavior closer to I'm looking for but it would be good > to have some insight into the decision process. > > - J<
This is not was I have experienced, at least with 3.3.x. I've been using the following in some configs with the expected result: flush-threshold-dumped 100 flush-threshold-scheduled 100 taperflush 100 autoflush yes As stated in the amanda.conf manpage, those will force amanda to start writing to a new volume only if the data in the hold disk plus the scheduled data are at least 100% of the volume capacity. If anything is left in the hold disk after a run, it will be flushed the next time amdump runs. Those constraints only apply when a new volume is requested. Note that if you manually flush using amflush, you must override those values with something like: amflush -oflush-threshold-dumped=0 -oflush-threshold-scheduled=0 -otaperflush=0 ... otherwise the flush constraints might not be met and the flush won't complete entirely or at all. Of course, I might be wrong so take this with a grain of salt! cheers, jf
