HP P3410A HP NetRAID 1M/2M Installation & Configuration - Page 40

Plan Hot Spares Optional, Decide the Rebuild Rate

Page 40 highlights

Chapter 4 Planning Plan Hot Spares (Optional) ! On Worksheet A for each adapter, log any hot spare disk modules and indicate whether each is global or dedicated to a particular array. A hot spare is a powered-on, stand-by disk that is ready for use should another disk fail. When a disk fails, the disk array controller's firmware can automatically rebuild the data from the failed disk onto the hot spare. Unless a rebuild occurs, a hot spare does not contain user data. When planning hot spares, keep these considerations in mind: • Hot spares are useful only for logical drives with RAID levels of 1, 5, 10, or 50. • Hot spares cannot rebuild logical drives of RAID 0, because this RAID level does not provide a means of recovering data. • A dedicated hot spare is assigned to a specific array. Only one hot spare can be dedicated to each individual array. • Global hot spares stand ready to rebuild any physical drive for any array with redundancy controlled by the adapter. • A hot spare does not count toward the usable capacity of any array. • A hot spare must have capacity equal to or greater than the capacity of the physical drive it would replace. • An adapter can support up to eight hot spares. Decide the Rebuild Rate ! During a rebuild, the contents of a complete physical drive is rewritten. Normal operations can go on during a rebuild, but performance may be degraded. The Rebuild Rate controls the rate at which a rebuild is done by specifying what percentage of IOP resources will be dedicated to rebuilding the data on a failed physical drive. A high Rebuild Rate (over 50%) speeds up the rebuild, but slows system performance. A low Rebuild Rate (under 50%) slows the rebuild process, but speeds up system performance. The default is 50%. RAID 0 data cannot be rebuilt because it has no redundancy. Log the Rebuild Rate on Worksheet A. 32

  • 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

Chapter 4
Planning
32
Plan Hot Spares (Optional)
On Worksheet A for each adapter, log any hot spare disk modules and indicate
whether each is global or dedicated to a particular array.
A hot spare is a powered-on, stand-by disk that is ready for use should another
disk fail. When a disk fails, the disk array controller’s firmware can automatically
rebuild the data from the failed disk onto the hot spare. Unless a rebuild occurs, a
hot spare does not contain user data. When planning hot spares, keep these
considerations in mind:
Hot spares are useful only for logical drives with RAID levels of 1, 5, 10,
or 50.
Hot spares
cannot
rebuild logical drives of RAID 0, because this RAID
level does not provide a means of recovering data.
A dedicated hot spare is assigned to a specific array. Only one hot spare
can be dedicated to each individual array.
Global hot spares stand ready to rebuild any physical drive for any array
with redundancy controlled by the adapter.
A hot spare does not count toward the usable capacity of any array.
A hot spare must have capacity equal to or greater than the capacity of the
physical drive it would replace.
An adapter can support up to eight hot spares.
Decide the Rebuild Rate
During a rebuild, the contents of a complete physical drive is rewritten. Normal
operations can go on during a rebuild, but performance may be degraded. The
Rebuild Rate controls the rate at which a rebuild is done by specifying what
percentage of IOP resources will be dedicated to rebuilding the data on a failed
physical drive.
A high Rebuild Rate (over 50%) speeds up the rebuild, but slows system
performance. A low Rebuild Rate (under 50%) slows the rebuild process, but
speeds up system performance. The default is 50%.
RAID 0 data cannot be rebuilt because it has no redundancy.
Log the Rebuild Rate on Worksheet A.
!
!