Bacula is a great backup solution for any company. I had it running here for that last 1.5 years and I recently moved it to a better server, A poweredge SC1425 with a ultra 160 scsi card which is inturn attached to a Quantum SDLT 320 Autoloader. I’m using the 1.36.x version (standard sarge debs) there has been alot of changes to how autoloaders are handled in new versions 1.38.x which could have prolly have solved most of my problems that I encoundered when switching the system over.
Here are a list of issues encountered.
1. Debian defaults to the user bacula for director/sd.(but does not have permissions to
(R/W) /dev/sgx or /dev/nstx)
2. bacula wasn’t issuing the unload command for the autoloader.
After some amount of messing around trying to get bacula to issue the unload command… I was just about to give up and go about compiling 1.38.x when it started to work.Thats just weird, broken on minute and fixed the next.
I took the lazy way out and edited the /etc/init.d/bacula-dir + /etc/init.d/bacula-sd and changed the user (-u) to root (-g) to root. Not the most secure, but it works 
Other than these little issues bacula has never let me down. The irc channel is a good place to get help and there is also a mailing list but i do think that it has too much traffic… (I have 6000+ unread mails)
Have you ever figured out what didn’t work? I’m trying with a Dell PowerVault 132T and the fill test just did the same thing… google isn’t giving me much love on the issue either.
On of the problems I was having was that when setting “set -x” so that i could get debug output was cause some of the problems(it was messing up the changer script). Talking withe the quys on irc, bacula seemed to think that the tape didn’t need to get unloaded so it was’nt issuing the unload command. I’ts working perfectly now.