HP 8/40 Fabric OS Encryption Administrator's Guide v6.4.0 (53-1001864-01, June - Page 191

Tape key expiry 5 Tape key expiry When the tape key expires in the middle of a write operation on the tape, the key is used for the duration of any write operation to append the data on the tape media. On any given tape medium, the same key is used for all written blocks, regardless of the time in between append operations. With the exception of native pools, whenever you rewind a tape and write to block zero, a new key will be generated, unique to that tape. Only with native pools will the same key be used to write to multiple media. This key has a user-determined lifespan, which applies to the elapsed time between write operations to new tapes (after rewind). Key expiration does not apply to append operations, no matter how long in the future. Key expiration never applies to reads. DF compatibility for tapes Only DF version 2.x- and 3.x-compatible NetApp DataFort (DF) tape metaheaders and block formats are supported for reading, decrypting, and decompressing the tapes. Only DF version 2.x- and 3.x-compatible tape block formats and metaheaders are supported for writing and encrypting tapes in DF-compatible format. A DF-compatible license is required. DF compatibility for disk LUNs Most versions of NetApp DataFort (DF) disk metaheaders and block formats are supported for reading, decrypting, and decompressing the disk LUNs. DF 1.x version disks are not supported for reading. Only DF version 3.x-compatible disk block formats and metaheaders are supported for writing and encrypting disk LUNs in DF-compatible format. A DF-compatible license is required. Fabric OS Encryption Administrator's Guide 173 53-1001864-01