>... I wish to implement a backup
>starts at a friday with the full backup, then Monday - Thursday the smaller
>backups. ...
Why do you want such a rigid schedule? Amanda normally does things by
balancing the load (which means shifting full and partial dumps around)
through the dumpcycle. Is there some reason you need to force it into
a particular pattern?
This is a very common issue for new Amanda users to have trouble with (I
certainly did when I started). The traditional method of "it's Tuesday
so this is what's going to happen" is based on ease of implementation,
a major goal of all administrators :-). But Amanda, being a computer
program, can be much smarter than an administrator (scary, but true :-)
and so do things a "better" way.
>So one cycle runs a week and need 5 dumps. For security i want to
>use two cycles, so i need 10 tapes before overwriting old tapes.
OK.
>I thought i can configure that in amanda.conf (dumpcycle 2 weeks,
>runspercycle 10, typecycle 12 because 10 are needed and 2 as reserve).
If you want a full dump every week, dumpcycle should be 1 week, not two,
and runspercycle would then be 5. I assume you really have 12 tapes?
Whether you do or not, tapecycle should be the actual number of tapes.
>I have to test it and so i tried the following:dumpcycle 3 days,
>runspercycle 3, typecycle 3.
>My intention by this was i have 3 tapes called csd01,csd02,csd03. The first
>backup had to be full on csd01, the next 2 should me smaller (on first on
>csd02 then on csd03). The fourth backup should be a full backup on tape
>csd01 again. ...
See above about the rigid schedule. What Amanda probably tried to do
was move some of the full dumps to the other tapes.
>... Sometimes e.g. tape csd06 has
>to be used were tape csd03 is expected. ...
Amanda would only have asked for csd06 (or anything beyond csd03)
if you told it about those tapes, i.e. did an amlabel and/or set the
tapecyle higher than three. For your testing, you may need to wipe out
the tapelist file as part of making Amanda forget what you tried before.
>Frank
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
