Seems some compatibility issue persist between Solaris SD<>Linux SD when
using BSCrypto,
might be some encoding or SCSI layer incompatibility.
scsi-crypto works fine between LINUX <> LINUX SD, and SOLARIS<>SOLARIS SD,
each SD can read ecrypted data written by itself and the same OS, but
Solaris<>Linux
decrypt fails.
On 2015-01-06 09:06, Karoly CZOVEK wrote:
Hi All, i faced into the following problem:
On main site, i have an MSL2024 loader, working fine with LTO5 tapes.
We have to implement tape encryption, so just started to test
scenarios...
The MSL2024 encrypted and labeled tapes can read fine by itself,
but could not by the standalone SAS drive placed on DR location on
different SD.
The DR drive reognizing the encrypted tape, but seems the decrypt is
problematic.
The MSL2024 is hooked to a Solaris 11 (NexentaStor CE 3.1.5), the DR
drive is plugged into an
standard Ubuntu linux. On both sides i can see the encrypt keys
hitting the drives.
Restore fails with the following:
05-Jan 17:07 bacula-dir JobId 32003: Start Restore Job
filebased_restore.2015-01-05_17.07.37_07
05-Jan 17:07 bacula-dir JobId 32003: Using Device "drlto5drive" to read.
05-Jan 17:07 bacula-dr JobId 32003: Ready to read from volume
"ERW124L5" on device "drlto5drive" (/dev/nst0).
05-Jan 17:07 bacula-dr JobId 32003: Forward spacing Volume "ERW124L5"
tofile:block 0:1.
05-Jan 17:07 bacula-dr JobId 32003: Error: scsicrypto-sd.c:512 Read
error on fd=7 atfile:blk 0:1 on device "drlto5drive" (/dev/nst0).
ERR=Input/output error.
Probably due to reading encrypted data from volume
05-Jan 17:07 bacula-dr JobId 32003: Fatal error: fd_cmds.c:226 Command
error with FD, hanging up.
05-Jan 17:07 bacula-dir JobId 32003: Error: Bareos bacula-dir 13.2.2
(12Nov13):
Do You have any idea? Any test cases to play with on both sides,
instead of burning tapes?
Thanks.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
