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

DF-compatibility support for tape LUNs

Get HP 8/24 PDF manuals and user guides View all HP 8/24 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 237 highlights

DF-compatibility support for tape LUNs B DF-compatibility support for tape LUNs Table 21 and Table 22 may be used as a reference for establishing tape LUN policies in support of DataFort firmware versions. NOTE On tapes written in DataFort format, the encryption switch or blade cannot read and decrypt files with a block size of one MB or greater. TABLE 21 Compatibility matrix for Brocade and DataFort encryption modes for tape LUNs DataFort firmware versions Brocade handling for DataFort written tapes - Read Brocade handling for DataFort-compatible encryption - Write DF SAN version 1.x DF SAN version 2.x/3.x 1.x tape support in DF-compatible mode is not supported in Fabric OS v6.1.1_enc. The encryption switch supports reading and decrypting tapes of this format when a DF-compatible license is present. The encryption switch supports writing tapes in this version format when DF-compatible encryption mode is set and a DF-compatible license is present. TABLE 22 Compatibility support matrix for tape pools Tape pool encryption format Tape pool policy Metadata present Native (Brocade) Encrypt Brocade metadata Native (Brocade) Encrypt DF metadata Native (Brocade) Native (Brocade) Encrypt Cleartext No (new tape) Brocade metadata Native (Brocade) Cleartext DF metadata Native (Brocade) DF-compatible Cleartext Encrypt No (new tape) Brocade metadata DF-compatible Encrypt DF metadata Results No error. Both read and writes are allowed in Brocade format. The key from the metadata is used for read. A new key is generated for write if the key from the metadata has expired. Reads are allowed in DF-compatible format using the key from the metadata. Writes are rejected if the tape is not positioned at the beginning of the tape. Writes are allowed in Brocade format only. No error. A new key is generated and both read and write are allowed in Brocade format. Reads are allowed in Brocade format using the key from the metadata. Writes are rejected if the tape is not positioned at the beginning of the tape. Writes are allowed in cleartext format (no key generated) only when the tape is positioned at the beginning of the tape. Reads are allowed in DF-compatible format using the key from the metadata. Writes are rejected if the tape is not positioned at the beginning of the tape. Writes are allowed in cleartext format (no key generated) only when the tape is positioned at the beginning of the tape. No error. No key is generated, and both read and writes are allowed in cleartext format. Reads are allowed in Brocade format using the key from the metadata. Writes are rejected if the tape is not positioned at the beginning of the tape. Writes are allowed in DF-compatible format only when the tape is positioned at the beginning of the tape. No error. Both read and writes are allowed in DF-compatible format. The key from the metadata is used for read. A new key is used for write if the key from the metadata has expired. Fabric OS Encryption Administrator's Guide 219 53-1001864-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
Fabric OS Encryption Administrator’s Guide
219
53-1001864-01
DF-compatibility support for tape LUNs
B
DF-compatibility support for tape LUNs
Table 21
and
Table 22
may be used as a reference for establishing tape LUN policies in support of
DataFort firmware versions.
NOTE
On tapes written in DataFort format, the encryption switch or blade cannot read and decrypt files
with a block size of one MB or greater.
TABLE 21
Compatibility matrix for Brocade and DataFort encryption modes for tape LUNs
DataFort firmware versions
Brocade handling for DataFort written tapes - Read
Brocade handling for DataFort-compatible encryption - Write
DF SAN version 1.x
1.x tape support in DF-compatible mode is not supported in Fabric OS v6.1.1_enc.
DF SAN version 2.x/3.x
The encryption switch supports reading and
decrypting tapes of this format when a
DF-compatible license is present.
The encryption switch supports writing tapes in this version
format when DF-compatible encryption mode is set and a
DF-compatible license is present.
TABLE 22
Compatibility support matrix for tape pools
Tape pool encryption format
Tape pool policy
Metadata present
Results
Native (Brocade)
Encrypt
Brocade metadata
No error. Both read and writes are allowed in Brocade
format. The key from the metadata is used for read. A new
key is generated for write if the key from the metadata has
expired.
Native (Brocade)
Encrypt
DF metadata
Reads are allowed in DF-compatible format using the key
from the metadata. Writes are rejected if the tape is not
positioned at the beginning of the tape. Writes are allowed
in Brocade format only.
Native (Brocade)
Encrypt
No (new tape)
No error. A new key is generated and both read and write
are allowed in Brocade format.
Native (Brocade)
Cleartext
Brocade metadata
Reads are allowed in Brocade format using the key from
the metadata. Writes are rejected if the tape is not
positioned at the beginning of the tape. Writes are allowed
in cleartext format (no key generated) only when the tape is
positioned at the beginning of the tape.
Native (Brocade)
Cleartext
DF metadata
Reads are allowed in DF-compatible format using the key
from the metadata. Writes are rejected if the tape is not
positioned at the beginning of the tape. Writes are allowed
in cleartext format (no key generated) only when the tape is
positioned at the beginning of the tape.
Native (Brocade)
Cleartext
No (new tape)
No error. No key is generated, and both read and writes are
allowed in cleartext format.
DF-compatible
Encrypt
Brocade metadata
Reads are allowed in Brocade format using the key from
the metadata. Writes are rejected if the tape is not
positioned at the beginning of the tape. Writes are allowed
in DF-compatible format only when the tape is positioned
at the beginning of the tape.
DF-compatible
Encrypt
DF metadata
No error. Both read and writes are allowed in
DF-compatible format. The key from the metadata is used
for read. A new key is used for write if the key from the
metadata has expired.