[Bacula-users] new jobs blocked when despooling

Hi,

I'm having some problems with spooling and despooling system. Essentially a job that gets queued while another job is already despooling will wait until despooling is finished and then only will it start spooling.

The backup process is as follows:
*run a ClientRunBeforeJob script, which creates an LVM snapshot of the system
*spool to a fast storage, to be able to free the snapshot as soon as possible
*run a ClientRunAfterJob
*despool to LTO-4 tape

What happens when another job is currently despooling:
*ClientRunBeforeJob will run (creating a snapshot)
*job will wait until the other has stopped despooling
*spool data
*run a ClientRunAfterJob
*despool to LTO-4 tape

This is quite frustrating, since the blocked job already created a snapshot, which degrades the performance quite a bit.
I found some references searching the mailng lists:

http://sourceforge.net/mailarchive/message.php?msg_id=f78dcdaf404373210c8a5bed1237ec59%40bugs.bacula.org
http://sourceforge.net/mailarchive/message.php?msg_id=487CEB1A.5%40lordsfam.net

which indicate that this is a known issue, but I was wondering if a proper bugreport is submitted already (if not i'll submit it) and if there's a valid workaround for this problem.
I'm using a 2.4.2 version of bacula.

Kind regards,

Jakob

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

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