[Bacula-users] When does bacula use multiple tape drives

Hi,

I am trying to configure a dual drive tape library. My challenge is that bacula seems to only use one drive. What determines in bacula when it is optimal to use two drives? I am using bacula Version: 5.2.13. Additionally I have set "Maximum Concurrent Jobs = 4" in all the relevant places, but all this seems to do is allow multiple concurrent jobs run, which I have tested and seems to work, but strangely, I was under the impression that one job could write to one tape exclusively. But in this case, it seems multiple jobs can write to the same tape concurrently or is this not correct? Lastly I have specified spool directory, however it is never used. Any ideas here would be appreciated or clarity.

I have included the relevant sections below for the bacula-sd.conf

# An autochanger device with two drives

Autochanger {

Name = Qualstar

Device = Drive-1

Device = Drive-2

Changer Command = "/opt/bacula/etc/mtx-changer %c %o %S %a %d"

Changer Device = /dev/changer-sg2

}

Device {

Name = Drive-1 #

Drive Index = 0

Media Type = LTO6

Archive Device = /dev/nst1

AutomaticMount = yes; # when device opened, read it

AlwaysOpen = yes;

RemovableMedia = yes;

RandomAccess = no;

AutoChanger = yes

Maximum Spool Size = 100G

Maximum Block Size = 1032192

Maximum Network Buffer Size = 65536

Spool Directory = /var/spool/bacula

# Enable the Alert command only if you have the mtx package loaded

# Note, apparently on some systems, tapeinfo resets the SCSI controller

# thus if you turn this on, make sure it does not reset your SCSI

# controller. I have never had any problems, and smartctl does

# not seem to cause such problems.

Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"

# If you have smartctl, enable this, it has more info than tapeinfo

# Alert Command = "sh -c 'smartctl -H -l error %c'"

}