Also if you have duplicate configs make sure to set "record no" in the global dumptype Joshua Baker-LePain wrote:
>On Fri, 15 Mar 2002 at 1:35pm, Robert SHEN wrote > >>1) how amanda records how many runs performed in a dumpcycle? Let's say >>if dumpcycle=7 and runspercycle = 5 and what happens if I configure 6 >>cron jobs to run from monday to friday >> > >Then you'll get extra backups -- I don't think it'll confuse amanda too >much. Note that dumpcycle has units -- I'm assuming you mean 7 days. > >>2) what happens if runspercycle > dumpcycle? >> > >Then you're telling amanda that you plan on running it more than once a >day (again, assuming your units on dumpcycle is days), and you'd better do >so or amanda will get very unhappy. > >>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. > >>4) What suggestion for disaster recovery? >> >A boot floppy/CD with, minimally, mt, dd, and tar/restore, and possibly >with the amanda tools. >
