HP Surestore Disk Array FC60 HP SureStore E Disk Array 12H User's and Service - Page 90

Auto Rebuild

Page 90 highlights

Concepts and Management Disk Array Features Auto Rebuild Auto Rebuild works in conjunction with Active Hot Spare to provide maximum protection against disk failure. Auto Rebuild allows the disk array to automatically begin rebuilding a failed disk drive, thus restoring data redundancy as quickly as possible. A rebuild priority setting allows you to balance array performance with rebuild speed. If a disk fails with Auto Rebuild enabled, the disk array immediately begins rebuilding the contents of the failed disk on the Active Hot Spare (or other available unallocated capacity). The disk array uses redundant information stored on the remaining disks to reconstruct the data that was on the failed disk. Until the rebuild is complete, the array is vulnerable to another disk failure and performance will be impacted. If you want more control over the rebuild process, you can disable Auto Rebuild and start a rebuild manually. This allows you to control when the rebuild is performed, but it can leave your data vulnerable to a second disk failure until the rebuild is complete. To perform a rebuild (automatic or manual), the disk array must have adequate available capacity. The best way to make this capacity available is by enabling the Active Hot Spare. This ensures that the disk array always has enough capacity to rebuild even the largest disk in the array. Rebuild Priority During a rebuild, the disk array is trying to do two things at once: perform the rebuild and service I/O requests from the host. A rebuild priority allows you to define which of these operations is more important. High rebuild priority allows the disk array to complete the rebuild as quickly as possible, but system performance may suffer because host I/Os are delayed. Low rebuild priority instructs the array to give precedence to server I/Os, thus maintaining system performance, but delaying the completion of the rebuild. Interrupted Rebuild Removing a disk from the array with Auto Rebuild enabled will cause the array controller to immediately begin a rebuild (assuming there is an Active Hot Spare or enough unallocated capacity available). If the disk is reinstalled before the rebuild is complete, the array controller will recognize the missing disk and stop the rebuild. It is not necessary for the rebuild to continue because any data on the disk that has not changed in its absence is still valid. However, data that gets written while the disk is missing must be rebuilt, so the rebuild operation might not stop. The rebuild must continue if there were any write I/Os while the disk was missing from the array. 90 Concepts

  • 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

Concepts and Management
Disk Array Features
90
Concepts
Auto Rebuild
Auto Rebuild works in conjunction with Active Hot Spare to provide maximum protection against disk
failure. Auto Rebuild allows the disk array to automatically begin rebuilding a failed disk drive, thus
restoring data redundancy as quickly as possible. A rebuild priority setting allows you to balance array
performance with rebuild speed.
If a disk fails with Auto Rebuild enabled, the disk array immediately begins rebuilding the contents of the
failed disk on the Active Hot Spare (or other available unallocated capacity). The disk array uses redundant
information stored on the remaining disks to reconstruct the data that was on the failed disk. Until the
rebuild is complete, the array is vulnerable to another disk failure and performance will be impacted.
If you want more control over the rebuild process, you can disable Auto Rebuild and start a rebuild
manually. This allows you to control when the rebuild is performed, but it can leave your data vulnerable to
a second disk failure until the rebuild is complete.
To perform a rebuild (automatic or manual), the disk array must have adequate available capacity. The best
way to make this capacity available is by enabling the Active Hot Spare. This ensures that the disk array
always has enough capacity to rebuild even the largest disk in the array.
Rebuild Priority
During a rebuild, the disk array is trying to do two things at once: perform the rebuild and service I/O
requests from the host. A rebuild priority allows you to define which of these operations is more important.
High rebuild priority allows the disk array to complete the rebuild as quickly as possible, but system
performance may suffer because host I/Os are delayed. Low rebuild priority instructs the array to give
precedence to server I/Os, thus maintaining system performance, but delaying the completion of the
rebuild.
Interrupted Rebuild
Removing a disk from the array with Auto Rebuild enabled will cause the array controller to immediately
begin a rebuild (assuming there is an Active Hot Spare or enough unallocated capacity available). If the
disk is reinstalled before the rebuild is complete, the array controller will recognize the missing disk and
stop the rebuild. It is not necessary for the rebuild to continue because any data on the disk that has not
changed in its absence is still valid. However, data that gets written while the disk is missing must be
rebuilt, so the rebuild operation might not stop. The rebuild must continue if there were any write I/Os
while the disk was missing from the array.