Menu
▾
▴
Re: [Bacula-users] bacula error at schedules
|
From: Kern S. <ke...@si...> - 2003-11-07 14:08:18
|
On Fri, 2003-11-07 at 14:28, Johan Decock wrote: > Hi Kern, > > What do you mean by 'inhibit' the pruning? I mean that I could prevent it from doing the pruning when being called from the status command. > When I run status dir, the side effect is that the volume that will be used next is pruned/purged from the database. I would like it only to be removed from the database right before the next backup is written to it. Is that possible? (I did say in my dir.conf that the oldest volume could be purged). But not days before it was going to be used for the new job. Would it be different, if I would be using pruning with good retention times? The problem I have in that case, is that I also don't want to loose the information in the database, when a volume is skipped. Hmmm. The PurgeCurrentVolume strikes again. In implementing the code to find the Volume for the status command, I did not consider PurgeCurrentVolume. I definitely have to keep it from doing a "purge" because as you point out, it should only do so at the very last moment. > > Basically, I would like to throw away the catalog information of a volume only at the moment it is going to be reused to write something else. Yes, I agree. I don't see a problem with doing pruning because the time period you have specified has passed, but it definitely should not do the purge. I'll take a look at it. > > Thanks for having created a great product, Thanks. I'm enjoying "creating" it. > > Johan > > > > > > From: Kern Sibbald <ke...@si...> on 07/11/2003 13:06 GMT > > To: Lutz Kittler <Lut...@ss...> > cc: bacula-users <bac...@li...> (bcc: Johan Decock/Abis) > Subject: Re: [Bacula-users] bacula error at schedules > > > > On Fri, 2003-11-07 at 12:42, Lutz Kittler wrote: > > Am Freitag, 7. November 2003 12:33 schrieben Sie: > > > Hello, > > > > > > Sorry my instructions for applying the patch didn't agree with the patch > > > I produced. To ensure that you don't have problems, I've a patch that > > > agrees with the instructions. > > > > > > Kern > > > > > > > Line numbers of patch are different to my 1.32d sources but I changed it > > manually and listing was now okay. > > OK, good. > > > But if it only changes the output , what about the pruning problem? > > Was pruning initiated by the "status dir"-command output ? > > Yes, the code that finds the Volume for the "status dir" command is the > same code as used for finding a Volume for a job. I could inhibit the > pruning during the "status dir", which is a bit annoying, but in doing > so I would almost guarantee the Volume would not be correct. > > > > > Lutz > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Bacula-users mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > > > > -------------------------------------------------------------------------- > ABIS Training & Consulting > website: http://www.abis.be - e-mail: tra...@ab... > tel: Belgium: (+32)-16-245610 - The Netherlands: (+31)-348-435570 > fax: Belgium: (+32)-16-245691 - The Netherlands: (+31)-348-432493 > -------------------------------------------------------------------------- > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Bacula-users mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-users |