--On Wednesday, October 09, 2002 22:41:05 -0500 "Craig Hancock
[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> John please forgive my assumptions. But I still don't understand.
> If tapecycles are defined by number of tapes. How is possible to double
> runspercycle if its meaurement is in weeks.
Runspercycle isn't measured in weeks, it is a number (I don't know
if Amanda ignores words after it or not).
Your dumpcycle was 28 days (if I remember correctly). So if you
run amanda every night your runspercycle is 28, and if you only
run it 5 nights a week then runspercycle is 20. If you only run
it once a week it is 4. The number is used by planner to figure
out how many runs there are to fit in all the full backups. For
a simplistic example, with runspercycle of 28 and if there just
happened to be 28 equal sized partitions in your disklist, then
Amanda would try to to a full dump on one of them each day. If
runspercycle were 4 (once per week in your 28 day dumpclycle)
then Amanda would have to do a full of 7 filesystems each run
to get them all done during your dumpcycle.
As an addenda to your original question, Amanda is asking for
a new tape because your tapecycle is set to 25 but you only
have 18 tapes, so Amanda is looking for one of the remaining
7.
A few definitions to review:
dumpcycle - Amanda will do a level 0 backup of each disklist
entry at least once during this time period
runspercycle - how many times during the dumpcycle Amanda
will be run. It shouldn't be more than dumpcycle or some
parts of Amanda will get confused since only the date is
used for many Amanda files
runtapes - maximum number of tapes to use for each run
tapecycle - minimum number of tapes to use before overwriting
the oldest tape. As Gene pointed out, Amanda doesn't append
but always overwrites whatever tapes it uses on a run
Good luck,
Frank
>
> *Relizes that he will get slammed for this but still confused*
>
> Craig Hancock
>
--
Frank Smith [EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
