Hello all, 

I found a workaround for my problem I asked the list about earlier. I
created another Pool and moved the volumes from the faulty Pool to the
new one. I reconfigured the jobs to write to the new Pool and restarted
the Storage daemon. 
I'm not sure what this does to my backuphistory, so the next couple of
days I will be scheduling all full backups to make sure i'm safe. At
least the backups are working again. 

Best regards,
Peter van der Meulen

========================

Hello all, 

I'm new to the list and have searched other resources before turning to
you. I'm experiencing the bug described in bug 00001578, except I'm
(still) using version Bacula 2.0.3., running on RHEL 5.4 (i386). 

I went through the bugreport (http://bugs.bacula.org/view.php?id=1578)
and had to conclude that I caused this myself: starting to many full
backupjobs at once. And now this blocking the newly scheduled jobs.

I found the bugfix (bug-1578.patch) and was wondering if this will work
on my older Bacula version and how do I apply such a fix? 

Should there be another solution, I'm all ears. Thanks in advance! 

Best regards,

Peter van der Meulen
The Netherlands

------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users