On Thu, Apr 5, 2012 at 8:18 AM, Wolfgang Denk <w...@denx.de> wrote: > > Hi, > > I wonder why I see situations that a client is waiting for another job > to complete, that is only despooling, i. e. that does not block any > resources on the client: > > 53100 Increme <job 1> SD despooling Data > 53101 Increme <job 2> is waiting on max Client jobs > > This is with bacula 5.0.3 as distributed with Fedora 15. > > Settings: > > - in FD and SD: Maximum Concurrent Jobs = 20 > - in Job: Maximum Concurrent Jobs = 6 > - in Client: Maximum Concurrent Jobs = 1 > > I am aware that I'm limiting the number of jobs on the client to 1, > and this is intentional. But the "SD despooling Data" is something > that involves the DIR and the SD only, so it should not block the > client from starting the next backup job. > > Seems I'm missing something here. Any ideas are highly welcome. > > Thanks in advance. > Do you have any restrictions on how many jobs go per volume?
John ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
