Starting on August 11, Bacula 3.0.1 suddenly decided that the director needs to 
crash after it runs random incremental backups and lock up the storage 
director. I tried upgrading to 3.0.2 on all clients and directors, but that 
didn't fix the problem. The director and storage directors run on Gentoo and 
the clients are a Gentoo/Red Hat/Windows/Ubuntu mix. I should mention that I 
have two storage directors and both exhibit the same behavior. 


For example, I can have Client1, Client2, and Client3. Incremental backups will 
run fine for Client1 and Client2, but the incremental backup for Client3 will 
cause the director to crash. It also locks up the storage director with a 
message like "JobId=16459 wants Pool="Client1-Pool" but have 
Pool="Client3-Pool" nreserve=1 on drive "My-Device" (/bacula/vtapes). 


I can fix the issue for the storage director by restarting it, but that's the 
only way I've found to fix the bacula-sd problem. I have to restart the 
director as well because it crashes when this happens. If I then do a full 
backup of Client3, it will work and so will subsequent incremental backups. 
However, later Client2 will start doing the same thing until a full backup is 
run. 






Any ideas that people can shed on the subject would be very helpful. Using gdb, 
I tried to get some debugging information, but it didn't give me anything at 
all. 
_____________________ 
Corey Shaw 
Technology Specialist 
O. 801.491.0705 (x. 157) 
F. 801.491.8774 

Winner of the 2009 Utah Work/Life Award 
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to