> On Jan 26, 2016, at 2:45 PM, jflack <[email protected]> wrote:
>
> Hi,
>
> First time -users question, I have inherited an amanda installation.
>
> My question might be a FAQ.
>
> I notice that if I run 'amadmin daily info' after a daily run,
> I see a bunch of entries I feel comfortable with, like this one:
>
> Dumps: lev datestmp tape file origK compK secs
> 0 20160120 D03015 13 25990880 25990880 2610
> 1 20160125 D03001 51 17900 17900 1133
>
> Ok, so this DLE had a full dump on 1/20 and an increment on 1/25
> and both are on tape. I like that.
>
> Dumps: lev datestmp tape file origK compK secs
> 0 20160122 D03018 21 62438810 62438810 10453
> 1 20160125 0 50230 50230 1048
>
> Here's one where the 1/22 full dump is taped, and the 1/25 increment
> is still in the holdingdisk waiting for flush-threshold-dumped.
> Right? Eh, ok. The tape alone would get me back to 1/22, anyway.
>
> Dumps: lev datestmp tape file origK compK secs
> 0 20160124 0 10375270 10375270 291
> 1 20160125 D03001 67 810 810 18
>
> For this one, am I seeing that amanda's fit algorithm decided to
> ship the 1/25 increment off to tape, while the 1/24 level 0
> *that it needs to be restorable* is still on the holding disk only?
> So, if I had only my tapes, this would be useless to me?
>
> Or am I not reading this output correctly?
>
> How about this one then:
>
> Dumps: lev datestmp tape file origK compK secs
> 0 20160124 0 20550680 20550680 369
> 1 20160125 0 680 680 11
> 2 19691231 D03001 69 0 0 0
>
> Check out the datestmp on that last one. I've seen several
> like that, they seem to all have size 0, so maybe when there
> has been no change to back up, the empty increment has a zero
> datestmp?
>
> So for this DLE, I've got a level 0 and level 1 still waiting to
> move off the holding disk, and a level 2 that has been taped but
> wouldn't do me any good without them (even if it weren't empty)?
>
> If I am reading these things right, I guess my next question is,
> is there some simple configuration option we have overlooked? Is
> there a way to have the tape scheduling algorithm try harder to
> get the lower-level dumps onto tape ahead of the increments that
> depend on them?
>
> This is not the latest version by the way, it's 3.2.3, in case
> any of this already works differently in the current version.
>
> Thanks!
> Chapman Flack
Check out these lines in your config file. The first are the included
comments (from a version or two ago; they may have changed the comments a bit
since. Or not.)
The second set, below the line, is MY setup based on those. Along with lots
of comments meant ONLY FOR MYSELF, but which you might find instructional
as you decide how to set yours up.
Deb Baddorf
#====================================================#
# New amanda includes these explanatory paragraphs:
# flush-threshold-dumped, flush-threshold-scheduled, taperflush, and autoflush
# are used to control tape utilization. See the amanda.conf (5) manpage for
# details on how they work. Taping will not start until all criteria are
# satisfied. Here are some examples:
#
# You want to fill tapes completely even in the case of failed dumps, and
# don't care if some dumps are left on the holding disk after a run:
# flush-threshold-dumped 100 # (or more)
# flush-threshold-scheduled 100 # (or more)
# taperflush 100
# autoflush yes
#
# You want to improve tape performance by waiting for a complete tape of data
# before writing anything. However, all dumps will be flushed; none will
# be left on the holding disk.
# flush-threshold-dumped 100 # (or more)
# flush-threshold-scheduled 100 # (or more)
# taperflush 0
#
# You don't want to use a new tape for every run, but want to start writing
# to tape as soon as possible:
# flush-threshold-dumped 0 # (or more)
# flush-threshold-scheduled 100 # (or more)
# taperflush 100
# autoflush yes
# maxdumpsize 100k # amount of data to dump each run; see above.
#
# You want to keep the most recent dumps on holding disk, for faster recovery.
# Older dumps will be rotated to tape during each run.
# flush-threshold-dumped 300 # (or more)
# flush-threshold-scheduled 300 # (or more)
# taperflush 300
# autoflush yes
#
# Defaults:
# (no restrictions; flush to tape immediately; don't flush old dumps.)
#flush-threshold-dumped 0
#flush-threshold-scheduled 0
#taperflush 0
#autoflush no
#
#====================================================#
## with LTO5 tapes, as of 2/27/2015, I still only USE one tape.
## Don't faff around; just write to the silly tape. But to avoid
## shoe shining, let some amount accumulate. Else we'd be writing
## the first tiny file and then waiting .....
## Do I even HAVE 20% of a tape's full, on a daily basis? NO!!
## On a normal Thursday 2/27/15 I had 153G of data on spool before
## any writing occurred. (Since I was at that point accumulating all
## on disk before allowing writing to start.) That might only be
## 10% of an LTO5 tape, at a guess. 1450G is what we measured with
## amtapetype, below under the LTO5mine definition.
## 153G is less than 10% of that.
## OK -- set to 5% ??
#flush-threshold-dumped 05 #Default: 0.
# Amanda will not begin writing data to a new tape
volume
# until the amount of data on the holding disk is at
least this percentage
# of the volume size. The idea is to accumulate a
bunch of files,
# so the fill algorithm "Greedy Algorithm" has some
choices to work with.
# The value of this parameter may not exceed than that
of the
# flush-threshold-scheduled parameter.
flush-threshold-scheduled 05 #Default: 0.
# Amanda will not begin writing data to a new volume
until the sum of
# the amount of data on the holding disk and the
estimated amount of data
# remaining to be dumped during this run is at least
this percentage of
# the volume size.
# The value of this parameter may not be less than
that of the
# flush-threshold-dumped or taperflush parameters.
taperflush 0 # Default: 0.
# At the end of a run, Amanda will start a new tape to
flush remaining data
# if there is more data on the holding disk at the end
of a run than this
# setting allows; the amount is specified as a
percentage of the capacity
# of a single volume.
#### dsbdsb ie. 0 == start a new tape if any data
is still on holding disk.
#### Good.
## taperflush <= flush-threshold-scheduled
## flush-threshold-dumped <= flush-threshold-scheduled
#autoflush yes # only flushes those NAMED on the command line. Use
ALL. 6/28/13
autoflush all # flush leftovers from a crash, or a ran-out-of-tape
condition
