> I found another person with the very same symptoms and they resolved the 
> problem by changing out the SAS host adapter....

Wow that's weird that a SAS controller would be to blame!  My library
and drive are HP and they supply "HP Tape Tools" which you can use to
run tests on the library (and drive) to see if they are working
properly.  Are there any vendor diagnostics for your library that you
could run to confirm it is working correctly?

It seems a bit odd it would be the SAS controller if it worked before
upgrading to the latest Bacula version.  Perhaps it's an issue with a
kernel driver, assuming you upgraded the whole OS at the same time?

> I Note that both my bacula-dir and my bacula-sd conf files have a 
> Storage section, with a Device section only in bacula-sd.
> 
> Is this correct or should the Storage and Device be in one or the other 
> confs? If they or one or the other sections should  be in both confs, 
> should they be identical???

This is correct.  The entries in bacula-dir tell it to connect to
the bacula-sd daemon, and the entries in bacula-sd tell it which
hardware device to use.  This is because you can have multiple
bacula-sd instances on different machines, so the Director needs to
know which device is controlled by which machine.

You should have both the autochanger and the drive listed in both
config files, however the one listed in bacula-dir.conf will be much
shorter as it won't have any of the configuration, basically just the
password for the bacula-sd daemon.

I am not sure whether it is necessary to list both the drive and the
autochanger (from your config files it looks like you only include the
autochanger and not the drive) but since Bacula is calling the
mtx-changer script it would seem to be fine the way you have it now.

In case it's helpful, here are the full Storage sections from my own
bacula-dir.conf:

  Autochanger {
    Name = peapod-x
    Address = localhost
    SDPort = 9103
    Password = "xxx"
    Device = peapod-x
    Media Type = LTO-4
    Maximum Concurrent Jobs = 10
  }

  Storage {
    Name = peapod-d1
    Address = localhost
    SDPort = 9103
    Password = "xxx"
    Device = peapod-d1
    Media Type = LTO-4
    Autochanger = peapod-x
    Maximum Concurrent Jobs = 10
  }

Your Storage section with "Autochanger = yes" is equivalent to the
Autochanger section, this is just a newer way of writing it that
works with recent Bacula versions.  (Definitely 9.x, not sure
about 7.x though.)

Cheers,
Adam.


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

Reply via email to