>There are 4 day-tapes day1-day4 which are used every week from Monday to >Thursday in rotation, so only the tape with the oldest data is overwritten.
It would be a good idea to get out of the habit of associating specific tapes with specific days. Amanda will always use the oldest tape. If you miss a day, or have to use two tapes in a day (e.g. a flush and a normal run), it's still using the oldest tape, which is what you really want anyway. >My idea was to create 3 amanda tape sets: >day: dumpcycle 0, runspercycle 1 day ???, tapecycle 4 tapes >week: dumpcycle 0, runspercycle 1 day ???, tapecycle 5 tapes >month: dumpcycle 0,runspercycle 1 day ???, tapecycle 999 tapes Leave runspercycle alone. Doing full dumps all the time means you don't need it. In addition to "dumpcycle 0", you should also set: strategy noinc skip-incr yes This will be even more emphatic to Amanda that you only want to do full dumps, and will also reduce the time it takes to do estimates. >Would this configuration work as I described above? As far as you've described, it seems OK. >Another problems could be public holidays. Would it be save to just not call >amdump at this days? ... Yes. >Would amanda be upset and confuse the rotation-cycle(not >overwrite the oldest tape)? No. It will always use the oldest tape. >BTW, is it possible to browse through all index databases on the server with >amrecover or is it mandantory to specify exactly one? Not sure what you mean. There are amrecover commands to change the host (client) and disk as well as the date, so I would think those would let you move around pretty much wherever you wanted to go. >Georg John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
