Hi, On 4/3/2007 5:14 PM, James Cort wrote: > Arno Lehmann wrote: >> Hi, >> >> On 4/3/2007 11:31 AM, James Cort wrote: >> >>> Ryan Novosielski wrote: >>> >>>> If I'm not mistaken, if you prune the job, it will take the files with >>>> it (as there will be nothing to restore from). >>>> >>> I think you may be. >>> >> I think Ryan is right :-) >> >> You can find an explanation of the recycling algorithm in the manual: >> Look at the sections explaining the Retention settings in the DIR >> configuration. >> > Yes. As far as I can tell, I should never have had the problem I did in > the first place: > > Note, even if all the File and Job records are pruned from a Volume, > the Volume will not be marked Purged until the Volume retention period > expires.
Right. I thought it was different... > Given my original configuration, I'd have expected a bunch of volumes > which, while not recycled, were effectively "in limbo" as there would > have been no jobs or file records referencing them but they'd still have > been stuck on their volume retention. Therefore, I would have expected > Bacula to take a tape from the scratch pool. Particularly as the volume > it sat around waiting for wasn't in the autochanger. Here, too, I think your assumptions are correct. > Unless the volume retention information wasn't updated when the volumes > were moved to their relevant pool from the Scratch pool. Which is quite a common mistake :-) >> What you want sounds like setting the File and Job Retention to a longer >> time than the Volume Retention period. >> >> I prefer a Job Retention of 30 years in such a case, and limiting the >> Volume retention to the actual time you want to keep your data. >> > > AIUI, if, like me, you want to keep all the file/job data until the > volume itself is recycled, you'd suggest setting file and job retention > periods to be longer than the longest volume retention period. > > I've done that. Guess all I can do now is wait and see a few months. Looks like this... >>> It will be interesting to see if the volumes in the Daily pool are still >>> recycled when I'd expect with a rather shorter Volume retention than >>> File/Job retention period. >>> >> Keep in mind that you have to update the existing volumes to reflect a >> modified configuration! >> > Volumes, yes. But the volume retention period hasn't changed - it's the > file/job retention periods that are changing. I didn't think they > needed to be updated. No, as far as I know this information is not stored in the catalog. A reload might help when you modified the pool definition, but I don't think this is the problem here. Good luck, and keep us informed! Arno > -- > U4EA Technologies > http://www.u4eatech.com > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > ------------------------------------------------------------------------ > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
