--On Friday, September 20, 2002 20:58:42 -0400 Gene Heskett <[EMAIL PROTECTED]> wrote:
> On Friday 20 September 2002 16:32, Frank Smith wrote: >> --On Friday, September 20, 2002 21:46:48 +0200 Marcus Schopen > <[EMAIL PROTECTED]> wrote: >>> Frank Smith wrote: >>>> --On Friday, September 20, 2002 17:46:28 +0200 Marcus Schopen > <[EMAIL PROTECTED]> wrote: >>>> > I'd like to set up a second set of tapes for making a full >>>> > backup each sunday. My daily set with a set of 24 tapes is >>>> > running from monday to saturday (dumpcycle 6 and tapecycle >>>> > 24). >>>> > >>>> > For the weekly full backuo I have a set of 20 tapes. Amanda >>>> > should write a full backup to each tape, so I have weekly >>>> > full backups for the last 20 weeks. Is this the right >>>> > configuration to force amanda to make a fullback each time: >>>> > >>>> > dumpcycle 0 >>>> > tapecycle 20 >>>> > maxcycle 0 >>>> > >>>> > Contab entry would be >>>> > >>>> > 0 8 * * 7 backup /usr/sbin/amdump DudeWeeklySet >>>> > >>>> > Thanks >>>> > Marcus >>>> >>>> Looks OK. Don't forget to use a dumptype with 'record no' >>>> for your weekly or you will hose your daily schedule. >>> >>> Thanks for answering that fast. But I don't understand the >>> 'record no' thing. The DudeWeeklySet is a totaly different >>> config. Why or how can it overwrite my daily stuff that runs on >>> a different config with a different set of tapes. >>> >>> Thanks >>> Marcus >> >> Dump keeps track of the times and levels of the last dump of each >> filesystem by saving the times in /etc/dumpdates. Since tar >> doesn't really have the same concept of levels, Amanda fakes it >> by writing similar information in /etc/amandates. >> Neither one has any idea of multiple configs, so the same file >> will get updated each time you run any of your configs. So when >> your 'weekly full' runs it will update the file, and then when >> your 'daily' runs, it will be expecting to back up files newer >> than the last 'daily' run, but dump or tar look for files newer >> than the times in the dumpdates/amandate file and will only be >> backing up files newer than the time of the 'weekly' run. >> The end result is that your daily set of tape may be unable to >> restore the entire filesystem. Your weekly set should be OK >> since its always a full. >> >> Frank >> that y > > Excellent explanation Frank, thanks, I needed that. But this also > points out that the fix would appear to be fairly simple, just a > matter of moving the location of this dumpdates/amandates file to > where ever that keyword points to in the individual amanda.conf. > > Or is this something thats carved into whatever stone dump/tar is > cut from, and not an amanda function? The latter case, amandates, > certainly seems to indicate its an actual amanda function and > therefore subject to being whatever the coders want it to be > including its location. I don't think amandates' location is configurable (unless its been added into the beta releases). It would be a nice feature to have though. Of course, dumpdates' location is set in stone in most dump programs. I guess you could compile your own, but it would still be the same for all configs unless you built multiple amandas each configured with a seperate dump executable. I think it would be nice if Amanda was friendlier to multiple configs so the run times could overlap as well, but I would suspect that would also be quite a bit of work. Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501