Can someone please clarify for me how the runspercycle parameter is used, when a cron job is actually kicking off amdump.
For example, if I have dumpcycle = runspercycle = 5 and cron runs amdump Mon - Fri, if the first amdump is run on Mon, everything is ok (5 runs in 5 days via cron). What happens if the dumpcycle starts on say Thurs ? Thurs and Friday amdump runs. Sat and Sun are skipped. Mon comes around, which is the end of the dumpcycle but only 2 tapes have been used so far. Amdump now attempts to complete the dumpcycle in only 3 tapes, correct ? What effect did runspercycle have on anything? It was my crontab that effected this dumpcycle. In this situation, I see why tapecycle should be greater than dumpcycle, and why we have amflush. If I amflush now, what tape do I amflush to ? If tape 3 is the tape that got filled up on Mon, does amflush expect a new tape, or tape 4 ? One last question, is there anyway to actually know that out of a tape cycle of 20 tapes, tape x - tape y contains a complete backup for all your hosts ? I suppose keeping track of when the dumpcycle starts, and when it ends, and what tapes were used would be the only way to know. beng
