The SAS controller was working with an IBM library with LTO-4 with
another computer running bacula 5.xxx. When the IBM died we decided that
it was time to upgrade rather than repair as the LTO-4 was no longer
large enough to backup everything. We never really looked into whether
it was the HBA or the library of both...
I noted when connecting the new library to the HBA that it hung at boot
for 3 - 5 minutes before continuing, which gave me pause, but it finally
continued without displaying any error. I reset the HBA to factory as
well as changing many settings like not trying to boot and with each
change the HBA hung at boot for a LONG time, so I am somewhat suspicious
of the HBA.
Richard
On 1/11/19 6:27 PM, Adam Nielsen wrote:
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.
--
LinuxCabal Asociación Civil
Ing. Richard Couture
Novell CNE, ECNE, MCNE
HP/Compaq ASE
Tel.: (+52) (333) 145-2638
Cel.: (+52) (044) 333 377-7505
Web: http://www.LinuxCabal.org
E-Mail: r...@linuxcabal.org
Hosted en la nube Cloud Sigma - www.CloudSigma.com
AVISO DE CONFIDENCIALIDAD: Este correo electrónico, incluyendo en su
caso, los archivos adjuntos al mismo, pueden contener información de
carácter confidencial y/o privilegiada, y se envían a la atención única
y exclusivamente de la persona y/o entidad a quien va dirigido. La
copia, revisión, uso, revelación y/o distribución de dicha información
confidencial sin la autorización por escrito de LinuxCabal está
prohibida. Si usted no es el destinatario a quien se dirige el presente
correo, favor de contactar al remitente respondiendo al presente correo
y eliminar el correo original incluyendo sus archivos, así como
cualesquiera copia del mismo. Mediante la recepción del presente correo
usted reconoce y acepta que en caso de incumplimiento de su parte y/o de
sus representantes a los términos antes mencionados, LinuxCabal tendrá
derecho a los daños y perjuicios que esto le cause.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
