HP Brocade 8/12c Fabric OS Encryption Administrator's Guide - Page 181

LUN modification considerations, Impact of tape LUN configuration changes

Page 181 highlights

Impact of tape LUN configuration changes 3 LUN modification considerations Make sure you understand the ramifications of modifying LUN policy parameters (such as encrypt/cleartext) for LUNs that are online and already being utilized. The following restrictions apply when modifying LUN policy parameters for disk LUNs: • When you change LUN policy from encrypt to cleartext, you wipe out all encrypted data stored on the LUN the next time data is written to that LUN. The following policy parameters are disabled: -enable_encexistingdata, -enable_rekey. • When you change the LUN policy back to encrypt, for example, by force-enabling the LUN, -enable_encexistingdata and -enable_rekey are disabled by default, and you must configure both options again. • When you add a LUN as cleartext and later you want to change the LUN policy from cleartext to encrypt, you must set the -enable_encexistingdata option. If you do not, all data on that LUN is lost, and cannot be recovered. For tape LUNs, the -enable_encexistingdata, -enable_rekey, and -key_lifespan options are not valid and therefore cannot be modified. When you attempt to execute these parameters while modifying a tape LUN, the system returns an error. Disabling -write_early ack or -read_ahead for tape LUN will result in lower total throughput depending on the number of flows per encryption engine. NOTE Make sure all the outstanding backup and recovery operations on the media are completed before changing the LUN configuration. For Disk LUNs -write_early_ack and -read_ahead are not valid and therefore cannot be modified. When you attempt to execute these parameters while modifying a disk LUN, the system returns an error. Impact of tape LUN configuration changes LUN-level policies apply when no policies are configured at the tape pool level. The following restrictions apply when modifying tape LUN configuration parameters: • If you change a tape LUN policy from encrypt to cleartext or from cleartext to encrypt while data is written to or read from a tape backup device, the policy change is not enforced until the current process completes and the tape is unmounted, rewound, or overwritten. This mechanism prevents the mixing of cleartext data to cipher-text data on the tape. • Make sure you understand the ramifications of changing the tape LUN encryption policy from encrypt to cleartext or from cleartext to encrypt. • You cannot modify the key lifespan value. If you wish to modify the key lifespan, delete and recreate the LUN with a different key lifespan value. Key lifespan values only apply to native-mode pools. Fabric OS Encryption Administrator's Guide 161 53-1002159-03

  • 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
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282

Fabric OS Encryption Administrator’s Guide
161
53-1002159-03
Impact of tape LUN configuration changes
3
LUN modification considerations
Make sure you understand the ramifications of modifying LUN policy parameters (such as
encrypt/cleartext) for LUNs that are online and already being utilized. The following restrictions
apply when modifying LUN policy parameters for disk LUNs:
When you change LUN policy from
encrypt
to
cleartext
, you wipe out all encrypted data stored
on the LUN the next time data is written to that LUN. The following policy parameters are
disabled:
-enable_encexistingdata
,
-enable_rekey
.
When you change the LUN policy back to
encrypt
, for example, by force-enabling the LUN,
-enable_encexistingdata
and
-enable_rekey
are disabled by default, and you must configure
both options again.
When you add a LUN as
cleartext
and later you want to change the LUN policy from
cleartext
to
encrypt
, you must set the
-enable_encexistingdata
option. If you do not, all data on that LUN is
lost, and cannot be recovered.
For tape LUNs, the
-enable_encexistingdata, -enable_rekey
, and
-key_lifespan
options are not valid
and therefore cannot be modified. When you attempt to execute these parameters while modifying
a tape LUN, the system returns an error. Disabling
-write_early ack
or
-read_ahead
for tape LUN will
result in lower total throughput depending on the number of flows per encryption engine.
NOTE
Make sure all the outstanding backup and recovery operations on the media are completed before
changing the LUN configuration.
For Disk LUNs
-write_early_ack
and
-read_ahead
are not valid and therefore cannot be modified.
When you attempt to execute these parameters while modifying a disk LUN, the system returns an
error.
Impact of tape LUN configuration changes
LUN-level policies apply when no policies are configured at the tape pool level. The following
restrictions apply when modifying tape LUN configuration parameters:
If you change a tape LUN policy from
encrypt
to
cleartext
or from
cleartext
to
encrypt
while data
is written to or read from a tape backup device, the policy change is not enforced until the
current process completes and the tape is unmounted, rewound, or overwritten. This
mechanism prevents the mixing of cleartext data to cipher-text data on the tape.
Make sure you understand the ramifications of changing the tape LUN encryption policy from
encrypt
to
cleartext
or from
cleartext
to
encrypt
.
You cannot modify the key lifespan value. If you wish to modify the key lifespan, delete and
recreate the LUN with a different key lifespan value. Key lifespan values only apply to
native-mode pools.