> > I would be interested in seeing why jobs are crashing and possibly
> > submit bug reports for that. I have run 30 thousand or so jobs at work
> > and I do not see very many job crashes.
> 
> That one is easy, and not very interesting actually. The two most
> frequent causes are:
> a) network outages (we do some backups over WAN VPN connections)
> b) clients crashing during backup, either coincidentally or because the
> additional load from the backup pushes an already flakey machine over
> the brink.

Same here - I tend to see the occasional backup timeout waiting for the FD in 
mid-job, for example when a client suddenly gets overloaded.  Afterwards, there 
are no orphaned spool files.  None of the jobs fail due to a Bacula bug as far 
as I can see, it's always a client-side issue.  A job failing due to a timeout 
shouldn't reduce the total usable SD spool space though :)

Sean


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users