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

NVRAM, Data Maps and Array Recovery

Page 94 highlights

Concepts and Management Disk Array Hardware NVRAM Each controller contains NVRAM (non-volatile RAM) used to store vital operating parameters and mapping information used in managing the array. Because data is spread across the disks, the array controller must have some means of determining where each block of data is located. It accomplishes this using a logical-to-physical data map stored in controller NVRAM. This map is vital to managing data-without it, all data on the array is unrecoverable. The contents of the NVRAM is maintained by dual battery backup if power to the disk array is off. Each controller module has its own dual set of batteries. If the batteries fail or lose their charge while power is off, the NVRAM contents will be lost. To protect against this, the Shutdown operation copies the contents of the NVRAM to each disk when power to the array is turned off by the power switch. This allows reconstruction of the data in NVRAM memory if the original map in NVRAM is lost or corrupted. The process of copying the contents of NVRAM to the disks makes the disk set independent of its controller. Because all the necessary mapping information is on the disks, it is possible to install a new controller or move the entire disk set to another controller. The new controller will determine that it has a new disk set, and the controller will attach itself to those disks. Data Maps and Array Recovery Two of the disks in the disk array are used to store data recovery map information. If the data maps in NVRAM memory are lost, you may be able to recover them with the arrayrecover utility. The arrayrecover utility and the data recovery map settings and parameters are described in more detail in the System Administrator's Guide, which is shipped with each disk array. The data resiliency feature for HP AutoRAID provides a means of recovering data after loss of NVRAM when the disk array is not shut down properly. Such a loss can only occur due to: dead battery, battery mishandling, a single failure in single controller configuration, or a multiple failure in dual controller configuration. The data maps in NVRAM memory are reconstructed using the latest copy of mapping information stored on the disk drives. This reconstruction includes a combination of the maps which were written during Shutdown, and the data recovery maps which are written at regular intervals. Part of the recovery operation includes performing a parity scan on the contents of the entire disk array to validate the accuracy of the maps and to correct any parity inconsistencies. This process can take up to several hours depending on the amount of data on the disk array. Controller firmware places a limit on the amount of time either data or map information can reside in battery-backed RAM before the process of writing that information to disk is begun. The firmware can optionally eliminate this limited exposure, which it automatically does during single controller operation. If the data maps in NVRAM memory are lost, all data except that retained only in NVRAM can be recovered using the Recover command via the front panel or the arrayrecover utility. In single-controller operation, the write cache is disabled, resulting in no data exposure to NVRAM loss. Disabling of the write cache is accompanied by a very serious degradation in performance under some workloads. This feature is supported on controller firmware versions later than HP40. 94 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 Hardware
94
Concepts
NVRAM
Each controller contains NVRAM (non-volatile RAM) used to store vital operating parameters and
mapping information used in managing the array.
Because data is spread across the disks, the array controller must have some means of determining where
each block of data is located. It accomplishes this using a logical-to-physical data map stored in controller
NVRAM. This map is vital to managing data—without it, all data on the array is unrecoverable.
The contents of the NVRAM is maintained by dual battery backup if power to the disk array is off. Each
controller module has its own dual set of batteries. If the batteries fail or lose their charge while power is
off, the NVRAM contents will be lost. To protect against this, the Shutdown operation copies the contents
of the NVRAM to each disk when power to the array is turned off by the power switch. This allows
reconstruction of the data in NVRAM memory if the original map in NVRAM is lost or corrupted.
The process of copying the contents of NVRAM to the disks makes the disk set independent of its
controller. Because all the necessary mapping information is on the disks, it is possible to install a new
controller or move the entire disk set to another controller. The new controller will determine that it has a
new disk set, and the controller will attach itself to those disks.
Data Maps and Array Recovery
Two of the disks in the disk array are used to store data recovery map information. If the data maps in
NVRAM memory are lost, you may be able to recover them with the
arrayrecover
utility. The
arrayrecover
utility and the data recovery map settings and parameters are described in more detail in the
System Administrator’s Guide
, which is shipped with each disk array.
The data resiliency feature for HP AutoRAID provides a means of recovering data after loss of NVRAM
when the disk array is not shut down properly. Such a loss can only occur due to: dead battery, battery
mishandling, a single failure in single controller configuration, or a multiple failure in dual controller
configuration. The data maps in NVRAM memory are reconstructed using the latest copy of mapping
information stored on the disk drives. This reconstruction includes a combination of the maps which were
written during Shutdown, and the data recovery maps which are written at regular intervals. Part of the
recovery operation includes performing a parity scan on the contents of the entire disk array to validate the
accuracy of the maps and to correct any parity inconsistencies. This process can take up to several hours
depending on the amount of data on the disk array.
Controller firmware places a limit on the amount of time either data or map information can reside in
battery-backed RAM before the process of writing that information to disk is begun. The firmware can
optionally eliminate this limited exposure, which it automatically does during single controller operation.
If the data maps in NVRAM memory are lost, all data except that retained only in NVRAM can be
recovered using the Recover command via the front panel or the
arrayrecover
utility. In single-controller
operation, the write cache is disabled, resulting in no data exposure to NVRAM loss. Disabling of the write
cache is accompanied by a very serious degradation in performance under some workloads. This feature is
supported on controller firmware versions later than HP40.