if you spread the full backups out as AMANDA is inclined to do, you can probably go to "runtapes 1" and she will make every effort to fill that tape with backup goodness every night. Since you have "runtapes 6", she will try to fill six tapes every night. This doesn't sound like what you want.
>From what you've said, you have more than 7 tapes. Tapecycle should be the total number of tapes you have to use, plus maybe a couple spares. (I like to keep it at exactly the number I rotate, and have blanks ready to amlabel in case of trouble.) runspercycle should probably be 6 if you want to use all six tapes and change them once a week. dumpcycle is how often you want a guaranteed set of level 0 backups. One week is probably good for now. I think runspercycle * runtapes * dumpcycle (in days) == tapecycle is a good starting point. As for the flush, it didn't happen because AMANDA didn't find the number (runtapes) of empty tapes she was expecting. You can use amflush after changing runtapes to flush the backups. There is more info on-line at http://www.backupcentral.com/amanda.html. > Amanda is configured to use my changer thusly: > -- snip -- > runtapes 6 # explained in WHATS.NEW > tpchanger "chg-zd-mtx" # the tape-changer glue script, see > TAPE.CHANGERS > changerdev "/dev/sg0" > tapetype HP-CHANGER > labelstr "^GH-((I)?(F)?)-[0-9][0-9]-[0-9]$" > -- snip -- > > And for rotations: > -- snip -- > dumpcycle 1 weeks # the number of days in the normal dump cycle > tapecycle 7 tapes # the number of tapes in rotation > > bumpsize 20 MB # minimum savings (threshold) to bump > level 1 -> 2 > bumpdays 1 # minimum days at each level > bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult > -- snip -- >
