Summary: I added "Max Run Time = 27h" and "Max Start Delay = 61h" to my job definitions and scheduled my weekend "Full" backup to begin Friday at 7:00 PM. As a result, five jobs got canceled and my spooling size changed from 5.0GB to 2.6GB after the first job was canceled. But why?
Details: I have this one machine running Windows NT 4.0. It's backup is very inconsistent. The first time I backed it up it completed 70GB in 12 hours. Then I fixed a bunch of permission denied warnings by granting permissions to the denied directories. Now the backups take anywhere from 19 to 55 hours to backup 80GB, which really screws up my scheduling. Until I can sort things out with this machine, I added "Max Run Time = 27h" and "Max Start Delay = 61h" to my job definitions. I did this so that no job will run for more than 27 hours and if a job has not started by Monday morning, forget about it. I normally run 15 jobs (generally one job per machine) over the weekend, all of which were scheduled to run at 7:00 PM. The first four jobs ran great. Then my problem child (my NT 4.0 machine) began its job. Sure enough, after 27 hours, Bacula marked the job to be canceled. So far so good. Things worked as planned. But then, the next four jobs that were queued after the NT 4.0 job were cancelled too. They didn't even start. They were just indicated as cancelled. Why? Weird though, the last six jobs that were queued ran and completed successfully. Why did the cancellation of the NT 4.0 job take down the four jobs that were lined up behind it? After I discovered those four jobs were canceled, I manually ran them and all four completed OK. Another oddity, as soon as the NT 4.0 job was canceled by Bacula, the spooling sized dropped from 5.0GB to 2,621,416,235 bytes for all remaining jobs. Why did the spooling size change? Thanks in advance for any comments. I can post additional information as requested. I just realized those four jobs that were strangely canceled had a priority of 11. All the jobs but the last six have a priority of 11 (and one job as a priority of 10, but that one finish early, in fourth place). The last six have priorities of 13, 13, 13, 13, 14, and 15. Is this a bug? Since eight jobs with a priority of 11 were all scheduled to run Friday at 7:00 PM, did Bacula think these eight jobs actually started at 7:00 PM Friday and then killed all remaining jobs after 27 hours. I'm under the impression the "Max Start Delay" option counts when a job actually started and not from when the job was scheduled to start. -Dave
bacula-dir.conf
Description: bacula-dir.conf
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
