It’s been an interesting few days with my bacula system.
Thanks for all the help and the suggestions; I think I’m over the major hurdle
of having a non-functioning system. I’ll get to the current config, but first
let me answer the questions that were asked:
My freebsd version is 10.2-RELEASE-p
Simon Templar wrote (2016/03/01):
> Perhaps I should have included this information in the first email,
> but I???ve tried several combinations of parameters in the
> bacula-sd.conf, and it failed each time. Here are the parts I???ve changed:
And perhaps include latest output of btape -c... /dev/n
Hello, and thank you all for your suggestions.
Just to make sure my hardware is still working I installed gtar and dumped
about 10tb to tape, and it completed without errors.
Perhaps I should have included this information in the first email, but I’ve
tried several combinations of parameters in
> On Tue, 1 Mar 2016 14:07:55 +0100, Cejka Rudolf said:
>
> Simon Templar wrote (2016/02/29):
> > I've set up bacula 7.2 on my FreeBSD server using Postgres as the
> > backend database.
>
> Which FreeBSD version? According to the mt status it seems to be
> sufficiently fresh.
>
> > Device {
Simon Templar wrote (2016/02/29):
> I've set up bacula 7.2 on my FreeBSD server using Postgres as the
> backend database.
Which FreeBSD version? According to the mt status it seems to be
sufficiently fresh.
> Device {
> ...
>Hardware End of Medium = no # Noted as FreeBSD specific
>
Hello Simon,
I´m not a FreeBSD expert, but from here:
http://lists.freebsd.org/pipermail/freebsd-scsi/2003-June/000190.html, it
seems you should configure BSF at EOM = yes (if I am not misunderstanding).
Best regards,
Ana
On Mon, Feb 29, 2016 at 5:19 PM, Simon Templar
wrote:
> Or perhaps a mor
Or perhaps a more accurate subject would be "Trouble successfully using
Bacula on FreeBSD"...
I've set up bacula 7.2 on my FreeBSD server using Postgres as the
backend database.
My tape drive info:
mt -f /dev/nsa0 status
Drive: sa0: Serial Number: ##
---
