Am 2017-10-24 um 19:07 schrieb Austin S. Hemmelgarn: > Based on what you're saying you want, I think you want the following in > your config: > > flush-threshold-dumped 400 > flush-threshold-scheduled 400 > taperflush 400 > autoflush yes > > The first two control flushing during a run, while taperflush controls > flushing at the end of a run. To get the flushing to actually happen, > you then need autoflush set to yes (and amanda will complain if it's not > set to yes and taperflush is more than zero). > > Now, I'm not 100% certain that will work, as I've not done this type of > thing myself (at work, we just use the holding disk as a cache so that > we can finish dumps as quickly as possible without our (slow, > parity-raid backed) persistent storage being the bottleneck, and at home > I don't use it since I don't need parallelization and I don't have any > disks that are faster than any others), but based on what I understand > from the documentation, I'm pretty sure this should do it.
thanks for the explanation, I have that setup there and just let the normal amdump-cronjob run tonight. And see what happens. The admin forgot to swap tapes, so degraded mode only anyway for now ;-)
