Tape drive doesn't support hardware encryption Read error 30

[fborup]

This week I got a very weird case here: Read error 30 (Tape drive doesn't support hardware encryption.)


In VBR V12, latest version, the GFS media pool has an encryption key set last year, checked/flagged to be used in tape encryption
Below, there is a warning regarding using hardware encryption if tape drives support it

We noticed that tapes are appearing inside the Library as ENCRYPTED
But the general status of the Dell/IBM ML3 LTO8 DRIVE is = DISABLED+Licensed
There is NO certifciate or passkey used to encrypt any tapes
In the logical library we can see: Encryption = Application Managed

As far as I know, no one ever touched the Lib, to change anything

why is that?
Why some tapes are "encrypted" and other "not encrypted" if the tape drive has status DISABLED?
IF VBR manges to encrypt, this should be seen in the ML3 LIB GUI?

Now:
I can retsore tapes with no problem in the smae environment
but
If I move the tape to another site, another environment, smae hardware, I can´t restore any tapes, despite being able to decrypt properly, import, catalog, etc.s still, I cna´t restore data due to

Read error 30 (Tape drive doesn't support hardware encryption.)

Tape is write-protected, but in my mind this is not a problem, or it s?

[david.domask]

Hi fborup,

At first blush, not able to fully explain it except that perhaps in the past an encryption module was installed / enabled and then later not enabled.

I would advise open a Support Case and let Veeam Support take a look at the debug logs.

Veeam supports both Hardware and Software encryption for tapes, but not quite getting why there would be an inconsistency here.

So start with a Support Case, as this sounds like a technical issue that needs investigation, and all such investigations must go through Support as noted when creating a topic.

Please share your case number once created, thanks!