On Tue, May 07, 2002 at 07:52:10AM -0400, Jean-Louis Martineau wrote: > > > That's BAD, you can't use the same logdir for two configurations, logfile > > > will get erased. You will get the same problem with indexdir if you have > > > a disk in both config. > > > > I don't understand why ... note that both configs won't run at the same day > > (one day for backup to tape, next day a degraded backup). > > When I use 'history' in amrecover I get all the backups in the list, > > with the proper tapes. Also the log files are all there. > > It works now because it's a new config, After tapecycle days, one config > will erase the log and index of the other config.
Ha OK. Hum, I can see a problem even with one config then: I think I should have dumpcycle=2 weeks and runspercycle=14, (one run per day) but I'll have only have half the expected tapes (as one run out of 2 will go to holding disk and will be flushed with the dump of the next run). I'm not sure how amanda will handle it. I already planned to have 14 tapes to have 2 cycles of tapes, so it should be OK. > > > > Why not use one config and edit your amanda.conf everyday, that could > > > be easily done by cron. > > > > I though at this, but I prefer static config files. This avoids problems > > in case the server goes down in the middle of a backup. > > I think that running a small sed script to patch a static config > file template before every amdump run is easier than using two configs. OK, I'll look at this. My problem with this approach is that if the server crashes in the middle of a degraded dump, then the wrong config will be in place until the next run, and amtape won't work (for use with amrecover for example). I agree this would be very bad luck. Also it has to be changed for amcheck too. -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] --
