<snipped a bit> >>> >> >>Hey Arno, >> >>I know the jobid and the volumes. I have the retention period set at a >>year, and it is less than a year ago, but when I attempt to restore the >>jobid it comes up with zero files. I assume that this means that the job >>has been pruned, but that there is still info about the volumes in the >>catalog, since they have a long retention time. > > > It looks like that, yes. > > >>So, if I want to restore >>at this point, I don't think I need to make the changes you were >>suggesting above to the dir config or to the volumes themselves, but I >>should just be able to scan the volumes into the catalog at this point. >>Is this correct? > > > I think so... but the job files will be pruned once the DIR triggers > the next round of pruning, which can happen effectively immediately. > > >>I'm a bit confused as to why you would ever need to >>change things in the dir config file, if the volumes still show up in >>list volumes. > > > In your case, just to ensure the job files are not pruned. > > Arno > >
Thanks a bunch Arno. Unfortunately, I'm still a bit confused. Doesn't the fact that the restore command comes up with zero files mean that the job files have already been pruned or do you just mean to ensure the job isn't pruned? I was confused earlier on the distinction between the job and the files, and I think I mispoke. I have the job still, but not the files. This does bring up an interesting question. From what you said earlier I got the idea that if you have the job info, and know the volumes you need, you could get the job files back without too much trouble using bscan. Well, I guess I'm about to find out. Long term though, if my interpretation of the situation is correct, I think what I would like to be able to do is have at least the job info around as long as the corresponding volumes are around. I assume that it is not pruning files that causes the database to grow out of control, and that the job info (were talking saving one job a month, and after 6 months, 4 jobs a year) shouldn't be too bad. I have plenty of space. So, if this is correct, is there a way to tell bacula to hold on to job directives as long as the corresponding volumes are around? Btw, is there a reason that the volume names aren't included in the job info? thanks, maria ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
