Adaptec 5325301507 Administration Guide - Page 69

Automatic Incorporation of Hot-Swapped Drives, Background Disk Scan, Storage > RAID Sets

Page 69 highlights

Item Identifying RAIDs Description Hot spares are identified on the Storage > Disks/Units screen using the following icons: Interaction Each icon will be associated with a disk in the RAID, identifying that disk as either a local hot spare or a global hot spare. When a drive in a RAID fails, the system looks for a hot spare in the following order: 1 If a local hot spare dedicated to the RAID exists, use the local hot spare. 2 If no local hot spare is available, and there is a single hot spare of sufficient capacity, use the global hot spare. 3 If no local hot spare is available, and two global hot spares of different capacity are available, use the smaller hot spare with sufficient capacity. Automatic Incorporation of Hot-Swapped Drives If a RAID (except RAID 0) is running in degraded mode and a raw drive, a nonGuardianOS drive, or an unassigned GuardianOS-partitioned drive is "hotinserted" into a SnapServer, it can be automatically assigned as a local spare and used to rebuild the degraded RAID. If there are no degraded RAIDs, a hot-inserted non-GuardianOS or unassigned drive will be automatically configured as a global hot spare. To enable the automatic incorporation of an unassigned drive, go to the Storage > RAID Sets screen and click the RAID Settings button. Background Disk Scan The background disk scan checks the integrity of RAID data by continuously scanning the disk drives for errors. Each RAID (except RAID 0) has its own background disk scan that is set to run when the I/O activity falls to a very low disk activity. Once the activity rises above the idle threshold, the background scan stops and waits for the activity to fall to the idle threshold again before resuming. As a result, there should be minimal to no impact on performance. Once the disk scan has completed a pass on a given RAID set, it waits a certain period of time before starting again. Chapter 4 Storage Configuration and Expansion 53

  • 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

RAIDs
Chapter 4
Storage Configuration and Expansion
53
Automatic Incorporation of Hot-Swapped Drives
If a RAID (except RAID 0) is running in degraded mode and a raw drive, a non-
GuardianOS drive, or an unassigned GuardianOS-partitioned drive is “hot-
inserted” into a SnapServer, it can be automatically assigned as a local spare and
used to rebuild the degraded RAID. If there are no degraded RAIDs, a hot-inserted
non-GuardianOS or unassigned drive will be automatically configured as a global
hot spare. To enable the automatic incorporation of an unassigned drive, go to the
Storage > RAID Sets
screen and click the
RAID Settings
button.
Background Disk Scan
The background disk scan checks the integrity of RAID data by continuously
scanning the disk drives for errors. Each RAID (except RAID 0) has its own
background disk scan that is set to run when the I/O activity falls to a very low disk
activity. Once the activity rises above the
idle threshold
, the background scan stops
and waits for the activity to fall to the
idle threshold again before resuming. As a
result, there should be minimal to no impact on performance.
Once the disk scan
has completed a pass on a given RAID set, it waits a certain period of time before
starting again.
Identifying
Hot spares are identified on the
Storage > Disks/Units
screen using
the following icons:
Each icon will be associated with a disk in the RAID, identifying that
disk as either a local hot spare or a global hot spare.
Interaction
When a drive in a RAID fails, the system looks for a hot spare in the
following order:
1
If a local hot spare dedicated to the RAID exists, use the local hot
spare.
2
If no local hot spare is available, and there is a single hot spare of
sufficient capacity, use the global hot spare.
3
If no local hot spare is available, and two global hot spares of
different capacity are available, use the smaller hot spare with
sufficient capacity.
Item
Description