Hello Morty, This is just to let you know that I have received these patches. The MaxDiff problem *should* now be fixed in the SVN. It took me several tries :-(.
Concerning the Poll, I like the concept, but I would like to think about this some more. What bothers me is that this is a very specific implementation. It seems to me that we should be able to do the same thing but perhaps a bit more general by making similar modifications to Admin jobs. My original idea (not yet fully implemented), was that an Admin job could be started, and it could then trigger any action. That is sort of possible by using RunScripts, but it is really not very eligant. I wonder if you have any ideas to take the concept of your code and to add it to Admin jobs in a way, that the next time we want to "poll" for something different, it would be easy to add so we can deal with any kind of poll request. I hope you see what I mean. Best regards, Kern On Wednesday 22 April 2009 10:12:30 Mordechai T. Abzug wrote: > On Wed, Apr 22, 2009 at 08:33:51AM +0200, Kern Sibbald wrote: > > I am sorry, but it is not clear what you are doing here, in > > particular why you are adding a maxincinterval and what a "POLL" job > > is. > > I was trying to improve handling for laptops and other devices that go > away for the night. > > MaxIncrInterval is intended to be the Incremental analog of > MaxDiffInterval. A "Poll" is a level that doesn't actually do > anything except check if MaxIncrInterval, MaxDiffInterval, or > MaxFullInterval have been exceeded, doing a promotion if necessary. > > The idea is that instead of just running a once-a-night backup that > might fail, one also runs a "poll" job every half hour or so, and sets > MaxIncrInterval to 1 day (or whatever.) If the nightly incremental > fails, when the laptop does show up the next day and the poll runs, > the poll is promoted to an Incremental. If the laptop was there and > got backed up, then the poll doesn't get promoted. > > While this is intended for laptops, I think it also has a use in 24x7 > server environments, where this is no ideal backup time and spreading > out the backup impact is good. In such an environment, one can set > MaxIncrInterval, MaxDiffInterval, and MaxFullInterval, and *just* run > polls, without explicitly scheduling incrementals, differentials, and > fulls. So if I specify MaxFullInterval of 1 week, and run a full > backup of serverA on Monday and serverB on Tuesday, bacula should > henceforth automatically separate serverA from serverB without me > having to explicitly specify this in the bacula config. > > > PS: All patches need to be submitted as attachments to avoid email > > wrapping. > > OK. Patches attached. > > - Morty ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
