Amanda-Users

Re: More than one tape per run

2003-10-23 10:03:06
Subject: Re: More than one tape per run
From: Toralf Lund <toralf AT procaptura DOT com>
To: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Thu, 23 Oct 2003 15:53:23 +0200
Paul Bijnens wrote:

Toralf Lund wrote:

I'm thinking about using more than one tape, i.e. set "runtapes" parameter to a value > 1, for my updated archival setup. Is there anything special I need to keep in mind when doing this? Also, how do I set up runspercycle in this case? Is it the total number of tapes runspercycle * runtapes, or just runspercycle?


runspercycle does not need to be changed.  The "runtapes" means that
for each run up to that number of tapes may be used (note: not "must").

You have to increase your tapecycle probably to cover the same dumpcycle(s), because you'll burn twice as much tapes for each run.
(well, "burn", hopefully not litteraly).

I'm still not sure I understand. If I have

runspercycle 2

and

runtapes 2

will amanda try to distribute the full dumps across 4 tapes, or just 2?

When I think about it, the first answer makes most sense, as the parameter otherwise ought to have been called "tapespercycle".


The parameter "taperalgo largestfit" will help to fill the first
tape(s) to 100%.  (New since amanda 2.4.3.)

I'm using that already.


This works better when also using:

dumporder "SSSSSS"      # as many S's as you have dumpers

(or use "TTTTTT", which is a good approximation of SSSS, but optimises
the total runtime of your backups better; I use TTTTT).

For a complete explanation why this works better, see:


http://groups.yahoo.com/group/amanda-users/message/46327

This is very helpful indeed. Thanks.

I've been wondering how I might avoid having the largest image left on the holding disk when the total size is only just larger than the tape (like you say, taperalgo often doesn't help), but never noticed this parameter, or the message you are referring to.

--
- Toralf