Hello Daniel,
You are welcome :-).
I see you are using /dev/sgX and /dev/nstX device names for the autochanger
configuration. This is not recommended since they can be modified after
server reboots.
Please use /dev/tape/by-id values or even udev rules. Also, I noticed you
have a pool configured
Hello Steve,
Great it worked!
You are right, it is not a good idea to have both tape libraries share the
same pool/media type. Mainly because LTO-6 is more than 2 generations ahead
LTO-3. This means your LTO-6 drives will not be able to even read the LTO-3
tapes.
I would recommend you to have a
Thank you!
This solved my problem. I was starting to worry that we had purchased a fairly
expensive drive that wasn't going to work -- tough to explain to my boss.
I had copied my configuration from our older instance of bacula, which is using
the same kind of library, but with the LTO3 versi
Thanks for the reply Ana.
Here is most of the info you asked. I will work on running btape again but now
it is just timing out and saying that the device cannot be accessed when I try
to run the fill test.
[root@server ~]# lsscsi -g
[0:2:0:0]diskLSI MR9260-8i2.13 /
Hello,
We are pleased to announce that we have just released Bacula version
9.0.2
This is a minor bug fix release, but a few of the bugs are
important. The main items fixed are:
– Postgresql should now work with Postgresql prior to 9.0 Note:
Hello Marcin,
thanks for your answer. I tried Baculum 7.4.7 with a plain configuration
and auth user file "baculum.users" but got the same "Error 6". Baculum
9.0.1 is working on the same host without any problems. So it seems like
the problem isn't related to LDAP based authentication.
Regar
