HP EVA P6550 HP P6300/P6500 EVA User Guide (5697-2486, September 2013) - Page 38

Changing virtual disk failover/failback setting, Implicit LUN transition

Get HP EVA P6550 PDF manuals and user guides View all HP EVA P6550 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 38 highlights

Table 8 Failback settings by operating system (continued) Operating system Default behavior OpenVMS Host follows the unit1 Oracle Solaris VMware Host follows the unit1 Host follows the unit1 Supported settings Path A/B - Failover only Path A/B - Failover/Failback No preference Path A/B - Failover only Path A/B - Failover/Failback (recommended) No preference Path A/B - Failover only Path A/B - Failover/Failback No preference Path A/B - Failover only Path A/B - Failover/Failback Windows Failback performed on the host No preference Path A/B - Failover only Path A/B - Failover/Failback 1 If preference has been configured to ensure a more balanced controller configuration, the Path A/B -Failover/Failback setting is required to maintain the configuration after a single controller reboot. Changing virtual disk failover/failback setting Changing the failover/failback setting of a virtual disk may impact which controller presents the disk. Table 9 (page 38) identifies the presentation behavior that results when the failover/failback setting for a virtual disk is changed. NOTE: If the new setting moves the presentation of the virtual disk to a new controller, any snapshots or snapclones associated with the virtual disk are also moved. Table 9 Impact on virtual disk presentation when changing failover/failback setting New setting No Preference Path A Failover Impact on virtual disk presentation None. The disk maintains its original presentation. If the disk is currently presented on Controller 2, it is moved to Controller 1. If the disk is on Controller 1, it remains there. Path B Failover If the disk is currently presented on Controller 1, it is moved to Controller 2. If the disk is on Controller 2, it remains there. Path A Failover/Failback If the disk is currently presented on Controller 2, it is moved to Controller 1. If the disk is on Controller 1, it remains there. Path B Failover/Failback If the disk is currently presented on Controller 1, it is moved to Controller 2. If the disk is on Controller 2, it remains there. Implicit LUN transition Implicit LUN transition automatically transfers management of a virtual disk to the array controller that receives the most read requests for that virtual disk. This improves performance by reducing the overhead incurred when servicing read I/Os on the non-managing controller. Implicit LUN transition is enabled in all versions of XCS. 38 P63x0/P65x0 EVA operation

  • 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
Table 8 Failback settings by operating system
(continued)
Supported settings
Default behavior
Operating system
Path A/B – Failover only
Path A/B – Failover/Failback
No preference
Host follows the unit
1
OpenVMS
Path A/B – Failover only
Path A/B – Failover/Failback
(recommended)
No preference
Host follows the unit
1
Oracle Solaris
Path A/B – Failover only
Path A/B – Failover/Failback
No preference
Host follows the unit
1
VMware
Path A/B – Failover only
Path A/B – Failover/Failback
No preference
Failback performed on the host
Windows
Path A/B – Failover only
Path A/B – Failover/Failback
1
If preference has been configured to ensure a more balanced controller configuration, the Path A/B –Failover/Failback
setting is required to maintain the configuration after a single controller reboot.
Changing virtual disk failover/failback setting
Changing the failover/failback setting of a virtual disk may impact which controller presents the
disk.
Table 9 (page 38)
identifies the presentation behavior that results when the failover/failback
setting for a virtual disk is changed.
NOTE:
If the new setting moves the presentation of the virtual disk to a new controller, any
snapshots or snapclones associated with the virtual disk are also moved.
Table 9 Impact on virtual disk presentation when changing failover/failback setting
Impact on virtual disk presentation
New setting
None. The disk maintains its original presentation.
No Preference
If the disk is currently presented on Controller 2, it is moved to Controller 1.
Path A Failover
If the disk is on Controller 1, it remains there.
If the disk is currently presented on Controller 1, it is moved to Controller 2.
Path B Failover
If the disk is on Controller 2, it remains there.
If the disk is currently presented on Controller 2, it is moved to Controller 1.
Path A Failover/Failback
If the disk is on Controller 1, it remains there.
If the disk is currently presented on Controller 1, it is moved to Controller 2.
Path B Failover/Failback
If the disk is on Controller 2, it remains there.
Implicit LUN transition
Implicit LUN transition automatically transfers management of a virtual disk to the array controller
that receives the most read requests for that virtual disk. This improves performance by reducing
the overhead incurred when servicing read I/Os on the non-managing controller. Implicit LUN
transition is enabled in all versions of XCS.
38
P63x0/P65x0 EVA operation