Hello Kern-
Thanks for the reply. Something like that may be at the root of the problem,
but the drive does not report being in SysV mode. It shows only these options
set: buffer-writes, async-writes, read-ahead, can-bsr and scsi2logical.
The Tape Testing Tools and their debug modes were
Hello,
In looking at your patch, I would guess that your tape drive is set in
SysV mode, which Bacula does not support. Bacula only supports Berkeley
tape conventions.
Have you worked through the Tape Testing chapter of the main manual? If
you have, I would find it very strange that the
Just to follow up, I did find a workaround for the I/O errors with LTO hardware
encryption: At the end of a tape file, space a record forward, then a record
back (code below).
I have not found the actual cause of the problem. It is most likely with the
vendor firmware for that particular IBM
> On Tue, 20 Oct 2015 15:02:23 -0700, Mark D Strohm said:
>
> Hello Patti and Martin-
>
> Thank you for the replies.
>
> As I understand it, Bacula should have no problem with LTO hardware
> encryption because (once set) it is supposed to be transparent at the user
> level, the same as
Mark,
Bacula is not involved in hardware (tape drive) encryption.
The encryption dialog is an exchange of key information between the drive
and the encryption key manager, in your case stenc. If your tapes were
initially written to prior to using the encryption capability, the tapes
can never
> On Mon, 19 Oct 2015 15:47:01 -0700, Mark D Strohm said:
>
> Hello-
>
> Is there a trick to using Bacula with LTO hardware encryption enabled?
>
> With drive encryption turned on, verify jobs are hitting an I/O error reading
> the first record of a tape file.
>
> On a test job that went
Hello Patti and Martin-
Thank you for the replies.
As I understand it, Bacula should have no problem with LTO hardware encryption
because (once set) it is supposed to be transparent at the user level, the same
as hardware compression. But apparently it is not perfectly transparent.
I’m
Hello-
Is there a trick to using Bacula with LTO hardware encryption enabled?
With drive encryption turned on, verify jobs are hitting an I/O error reading
the first record of a tape file.
On a test job that went to files 78, 79 and 80, the error looks like this:
19-Oct 14:03 ccnback-sd JobId
