cancel
Showing results for 
Search instead for 
Did you mean: 

Unencryption with BES or DataFort and then encryption with NBU question

If a customer is unencrypting all their tapes using NetApp DataFort and a Brocade Encryption Switch (these platforms did the initial encryption and both are EOL), and then if the customer encrypts these tapes using NBU, will the new encrypting of these tapes affect the NBU catalogue. Will the re-indexing happen properly?

(I hope the question makes sense)

1 Solution

Accepted Solutions
Accepted Solution!

In a word, no - it will be

In a word, no - it will be fine.

The unencryption via the '3rd' party software/ hardware, NBU knows nothing about this, and quite frankly doesn't care.  If you then backup, or duplicate the tapes to a NBU encrypted tape, then you'll just end up with a NBU encrypted tape ...

You don't say which NBU method you plan to use, two options:

1.  MSEO - software encryption, has zero effect on the catalog.

2.  KMS (hardware encryption) - has almost zero effect on the catalog ....  A KMS encrpypted tape has one filed written into the ImageCopy table (from memory) which is the KMS key tag.  This is how NBU knows how to unencpypt the tape, which key to use.

For MSEO, this doesn't happen, the MSEO 'tape driver' spots an encrypted tape, and the details it needs are written to the tape, so it just reads it from there.

View solution in original post

1 Reply
Accepted Solution!

In a word, no - it will be

In a word, no - it will be fine.

The unencryption via the '3rd' party software/ hardware, NBU knows nothing about this, and quite frankly doesn't care.  If you then backup, or duplicate the tapes to a NBU encrypted tape, then you'll just end up with a NBU encrypted tape ...

You don't say which NBU method you plan to use, two options:

1.  MSEO - software encryption, has zero effect on the catalog.

2.  KMS (hardware encryption) - has almost zero effect on the catalog ....  A KMS encrpypted tape has one filed written into the ImageCopy table (from memory) which is the KMS key tag.  This is how NBU knows how to unencpypt the tape, which key to use.

For MSEO, this doesn't happen, the MSEO 'tape driver' spots an encrypted tape, and the details it needs are written to the tape, so it just reads it from there.

View solution in original post