HP Surestore Disk Array FC60 HP SureStore E Disk Array FC60 Service Manual (A5 - Page 193

Assigning Volume Group Ownership, Selecting a RAID Level, RAID Technology

Page 193 highlights

Assigning Volume Group Ownership When a volume group is bound, you must identify which disk array controller (A or B) owns the volume group. The controller that is assigned ownership serves as the primary I/O path to the volume group. The other controller serves as the secondary or alternate path to the volume group. If there is a failure in the primary I/O path and alternate links are configured, ownership of the volume group automatically switches to the alternate path, maintaining access to all data on the volume group. When assigning volume group ownership, consider the following: • To ensure optimum performance, volume group ownership should be balanced between controllers. This ensures that one controller is not overloaded with I/O requests, while the other is idle. • Controller ownership can be changed on an existing volume group without impacting its operation. If you find that there is an imbalance between I/O path loads, you can change the ownership of one or more volume groups to solve the problem. Selecting a RAID Level The RAID level you select for each volume group determines the method used to store data on the disks. The RAID level assigned to the volume group can be changed dynamically if it is determined that a different RAID level would be more appropriate. With the exception of RAID 0, all RAID levels supported by the disk array provide protection against disk failure. However, there are differences in performance and storage efficiency between RAID levels. For more information on RAID levels and their comparative operating characteristics, see "RAID Technology" on page 45. The two factors that will influence the RAID level you select are performance and storage efficiency. • Performance - The performance characteristics differ for each RAID level. The types of applications you are running and the I/O activity associated with them should influence the RAID level you select for a volume group. The performance characteristics for each RAID level are summarized in "RAID Level Comparisons" on page 55. Managing Disk Array Capacity 193 Managing the Disk Array

  • 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
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416

Managing Disk Array Capacity
193
Managing the Disk Array
Assigning Volume Group Ownership
When a volume group is bound, you must identify which disk array controller (A or B)
owns the volume group. The controller that is assigned ownership serves as the primary
I/O path to the volume group. The other controller serves as the secondary or alternate
path to the volume group. If there is a failure in the primary I/O path and alternate links are
configured, ownership of the volume group automatically switches to the alternate path,
maintaining access to all data on the volume group.
When assigning volume group ownership, consider the following:
To ensure optimum performance, volume group ownership should be balanced between
controllers. This ensures that one controller is not overloaded with I/O requests, while
the other is idle.
Controller ownership can be changed on an existing volume group without impacting
its operation. If you find that there is an imbalance between I/O path loads, you can
change the ownership of one or more volume groups to solve the problem.
Selecting a RAID Level
The RAID level you select for each volume group determines the method used to store data
on the disks. The RAID level assigned to the volume group can be changed dynamically if it
is determined that a different RAID level would be more appropriate.
With the exception of RAID 0, all RAID levels supported by the disk array provide
protection against disk failure. However, there are differences in performance and storage
efficiency between RAID levels. For more information on RAID levels and their
comparative operating characteristics, see
"RAID Technology" on page 45
.
The two factors that will influence the RAID level you select are performance and storage
efficiency.
Performance
- The performance characteristics differ for each RAID level. The types
of applications you are running and the I/O activity associated with them should
influence the RAID level you select for a volume group. The performance
characteristics for each RAID level are summarized in
"RAID Level Comparisons" on
page 55
.