On Sat, 16 Mar 2002 at 9:52am, Robert SHEN wrote > >>> 3) if I want to apply the following strategy, what config should I put? > >>> Monday full backup for a directory /home/public > >>> Tuesday->Friday incremental backup of /home/public > >>> > >> ARRRRGH! :) Why? This has been discussed *many* times. You *can* > >> force amanda into your schedule. But, unless you have a very good > >> reason why, then it really is best to let amanda set the schedule. > >> It does a very good job at it. > >> > >> If you must do it, the canonical method is via two configs, one which > >> does the full (via a dumpcycle=0 dumptype) and one which does only > >> incrementals. > > > Sorry would you explain how amanda set the schedule.? would you post the > config?
dumpcycle, runspercycle, (and possibly runtapes) are the parameters you set. dumpcycle tells amanda the maximum time allowed between full dumps (level 0) of any particular filesystem. runspercycle tells amanda how many times per dumpcycle you are going to run amdump. You only need runtapes if you plan on using a changer of some sort and thus use more than one tape per amdump run. Using these parameters, amanda spreads the level 0 backups throughout the dumpcycle. The goal is "balanced backups", such that each night uses approximately the same amount of tape and takes the same amount of time. The chapter on amanda at www.backupcentral.com <http://www.backupcentral.com/amanda.html> makes very good reading... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
