HP Surestore Disk Array 12h System Administrator's Guide for HP-UX, MPE, and W - Page 18

HP-UX

Page 18 highlights

HP-UX Managing the HP SureStore E Disk Array 12H on HP-UX Tips for Configuring the Disk Array On HP-UX Configuration Option Number of disk drives Unallocated disk array capacity LVM configuration Impact on Performance and Capacity Performance. Increase the number of disk mechanisms in the disk array for maximum performance. As the number of individual disks is increased, the number of potential I/Os that can be performed simultaneously increases as well. This will improve performance in environments that place heavy I/O demand on the disk array. Capacity. The capacity of a disk array that is fully populated with disk mechanisms can only be increased by replacing lower capacity disks with higher capacity disks. Performance. Unallocated capacity is used as additional RAID 0/1 space. The amount of RAID 0/1 space required to maintain optimal performance is determined by the write working set parameter. Capacity. To create the maximum amount of storage capacity, allocate all available capacity to LUNs. Performance. To improve performance, configure LVM as follows: • Stripe logical volumes across LUNs on different disk arrays. Including LUNs on different disk arrays will improve throughput by spreading I/Os across arrays. • Divide LUN access between both disk array controllers. Mapping every LUN to the same controller does not utilize the two data paths available on the disk array. The default path is through the primary disk array controller, but this can be changed to the secondary controller when adding the physical volume to an LVM volume group. The process for changing the path differs for each version of HP-UX: HP-UX 10.1. From the Disk Devices list, select the disk hardware path through the secondary controller before adding the disk to a volume group. HP-UX 10.2. When adding the disk to a volume group, in the "Creating A Volume Group" dialog change the hardware path to the secondary controller Capacity. These LVM configurations have no impact on disk array capacity configuration. 18

  • 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

Managing the HP SureStore E Disk Array 12H on HP-UX
Tips for Configuring the Disk Array On HP-UX
18
HP-UX
Configuration
Option
Impact on Performance and Capacity
Number of disk
drives
Performance
. Increase the number of disk mechanisms in the disk array
for maximum performance. As the number of individual disks is
increased, the number of potential I/Os that can be performed
simultaneously increases as well. This will improve performance in
environments that place heavy I/O demand on the disk array.
Capacity
. The capacity of a disk array that is fully populated with disk
mechanisms can only be increased by replacing lower capacity disks with
higher capacity disks.
Unallocated disk
array capacity
Performance
. Unallocated capacity is used as additional RAID 0/1
space. The amount of RAID 0/1 space required to maintain optimal
performance is determined by the write working set parameter.
Capacity
. To create the maximum amount of storage capacity, allocate
all available capacity to LUNs.
LVM configuration
Performance
. To improve performance, configure LVM as follows:
Stripe logical volumes across LUNs on different disk arrays.
Including LUNs on different disk arrays will improve throughput by
spreading I/Os across arrays.
Divide LUN access between both disk array controllers. Mapping
every LUN to the same controller does not utilize the two data paths
available on the disk array. The default path is through the primary
disk array controller, but this can be changed to the secondary
controller when adding the physical volume to an LVM volume group.
The process for changing the path differs for each version of HP-UX:
HP-UX 10.1
. From the Disk Devices list, select the disk hardware
path through the secondary controller before adding the disk to
a volume group.
HP-UX 10.2
. When adding the disk to a volume group, in the
“Creating A Volume Group” dialog change the hardware path to
the secondary controller
Capacity
. These LVM configurations have no impact on disk array
capacity configuration.