>Could you let me know how shall i set the following parameters in each >instance of amanda.conf considering that i shall be creating 5 sets of >amanda config ( one per server ) . > >1) inparallel
I'd leave this at the default. The extra dumper processes won't hurt anything. If your servers (Amanda clients) can handle the load, and you have enough holding disk space and network bandwidth, you might set maxdumps up from 1 to 2 (or more) so more than one filesystem can be dumped at the same time. >2) dumpcycle As you noted, with a seven day tapecycle, dumpcycle should be (at most) six (days). >3) runspercycle Since your backups will run every day, leave this alone. >4) tapecycle This would be 14 (7 days * 2 tapes/day). >5) tpchanger ( shold i hash it or keep chg-manual ) If you want to use (up to) two tapes per day, you will need to set runtapes to 2. That, in turn, means you *have* to have a tape changer defined. If you don't have a "real" tape changer (i.e. a robot or stacker), and you only have one tape drive, chg-manual is probably the way to go, unless you want to write your own (it's not very hard). If you have more than one tape drive, chg-multi would also work. You would load both tapes for the next run and it would automatically switch from the first to the second, if needed. The chg-manual changer is meant to be used when amdump is run interactively, i.e. when someone starts amdump by hand and watches for tape mount requests on the tty. If you're going to run it from cron or in the background some other way, look at the comments in the chg-manual script itself to see how to set up the notification (via E-mail, or console log messages, etc). >B.N.C John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
