On 05/28/2015 12:37 PM, Dimitri Maziuk wrote:
> ... because the spool in on the (smaller)

root

> drive.

PS. Looking at the logs, on #1 all 10 client jobs start within the same
couple of minutes after scheduled time and then backupcatalog job starts
2 hours later when they're done. Times are out of sequence and
overlapping, e.g.

JobId:                  1845
Scheduled time:         27-May-2015 21:05:00
Start time:             27-May-2015 21:09:21
End time:               27-May-2015 21:09:50
...
JobId:                  1846
Scheduled time:         27-May-2015 21:05:00
Start time:             27-May-2015 21:10:12
End time:               27-May-2015 21:10:42
...
JobId:                  1849
Scheduled time:         27-May-2015 21:05:01
Start time:             27-May-2015 21:05:11
End time:               27-May-2015 21:09:38
...
JobId:                  1852
Scheduled time:         27-May-2015 21:05:01
Start time:             27-May-2015 21:05:17
End time:               27-May-2015 21:05:27

On #2 I can't find one pair of jobs with overlapping runtimes like the
above. All I have is like

JobId:                  141
Scheduled time:         25-May-2015 20:05:01
Start time:             26-May-2015 23:02:34
End time:               27-May-2015 16:44:12
...
JobId:                  142
Scheduled time:         25-May-2015 20:05:01
Start time:             27-May-2015 16:44:12
End time:               27-May-2015 16:44:16

and so on. Strictly sequential with no concurrency. Any idea what gives?

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users