[Bacula-users] Bacula and shared autochangers

Hi

I'm using bacula-2.2.8 on some centos-5 machines.

Essentially, the situation is as follows: we have a small SAN with a couple of file-servers sharing an Overland Neo tape changer: that is to say the SAN is zoned into two zones, the tape changer and tape devices being present in each. The file-servers servers mount different disk volumes from the SAN, and there is no one machine which can see all the volumes across both SAN zones.

Our intention was to have bacula-dir connect to each file-server in turn, acquire the (shared) autochanger and tape resources, and back-up the disk volumes specific to that host's zone.

Unfortunately this does not seem to be possible: it appears that once a bacula-sd running on a particular file-server has acquired the autochanger device it is not subsequently released when that machine's back-ups have been completed and the next machine's back-ups are scheduled: that is to say the second machine can never successfully issue 'mtx unload slot n' while bacula-sd is running on the first machine ('mtx status' does, however, work)

Clearly there is some sort of low-level SCSI locking mechanism here: does anyone know of a work-around for this, short of re-doing disk volumes as GFS, placing them in both zones and mounting all of them on a single host?

Thanks in advance,

[HV]

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

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