I raised this a long time ago but I think it's timely to raise it again, given hassles we've had over the last few weeks here.
I'll have to point out that our original problems (unable to backup) was a hardware issue but it's been severely compounded by the decision to have Bacula escalate jobs from Incremental to Diff or Full (or "no prior job exists, running full backup") at the time a job is queued to be run rather than when it starts running. In a situation where a site is playing catchup and multiple duplicate jobs exist in the run queue it isn't helpful to have a XYZ full backup running and then have Bacula decide at next scheduled incremental that a full is required and escalate that to a Full because the existing one hasn't finished yet - having Full backups for the same job running back-to-back isn't "ideal" behaviour. Can the decision about level escalation be left until a job actually exits the hold queue & starts running? Thanks Alan ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
