I have a problem with bacula incorrectly running the schedule, at least as I
see it, and end up with two jobs getting scheduled for the same time.
Using bacula 2.0.1. I believe this has persisted as a problem since 1.36,
and has to do with using the week # in a schedule, and the result I'm
getting looks like a bug to me.
My schedule has Elm1 set to run:
Run = Level=Full Pool=pool1 w19 mon at 1:05
Elm3 has schedules to run:
Run = Level=Differential Pool=pool3 w18 mon at 1:05
Run = Level=Incremental Pool=pool3 w18 tue-sun at 1:05
However what I'm seeing on Monday May 7th, of week 19, is this on the
director status:
760 Differe Elm3.2007-05-07_01.05.01 is waiting for Client elm-fd to
connect to Storage carbon
762 Full Elm1.2007-05-07_01.05.03 is waiting on max Client jobs
Notice both are scheduled for the same day, which is impossible per the
above schedule. I should only see Elm1 scheduled, not Elm3.
Is this because the director's scheduling ran on Sunday May 6th, of week 18?
So it incorrectly made a match on the Elm3 schedule for Mon of week 18?
(that would be a bug)
regards,
Jamie
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
