Dell PowerVault MD3200 Owner's Manual - Page 158

Failed Virtual Disk Copy, Preferred RAID Controller Module Ownership, Failed RAID Controller Module

Page 158 highlights

Operation in Progress icons appear on the source virtual disk and the target virtual disk while the virtual disk copy has a status of In Progress or Pending. Failed Virtual Disk Copy A virtual disk copy can fail due to these conditions: • A read error from the source virtual disk • A write error to the target virtual disk • A failure in the storage array that affects the source virtual disk or the target virtual disk. When the virtual disk copy fails, a critical event is logged in the Event Log, and a Needs Attention icon appears in the Array Management Window. While a virtual disk copy has this status, the host has read-only access to the source virtual disk. Read requests from and write requests to the target virtual disk do not take place until the failure is corrected by using the Recovery Guru. Preferred RAID Controller Module Ownership During a virtual disk copy, the same RAID controller module must own both the source virtual disk and the target virtual disk. If both virtual disks do not have the same preferred RAID controller module when the virtual disk copy starts, the ownership of the target virtual disk is automatically transferred to the preferred RAID controller module of the source virtual disk. When the virtual disk copy is completed or is stopped, ownership of the target virtual disk is restored to its preferred RAID controller module. If ownership of the source virtual disk is changed during the virtual disk copy, ownership of the target virtual disk is also changed. Failed RAID Controller Module You must manually change RAID controller module ownership to the alternate RAID controller module to allow the virtual disk copy to complete under all of these conditions: • A virtual disk copy has a status of In Progress • The preferred RAID controller module of the source virtual disk fails • The ownership transfer does not occur automatically in the failover 158 Configuration: Premium Feature-Virtual Disk Copy

  • 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

158
Configuration: Premium Feature—Virtual Disk Copy
Operation in Progress icons appear on the source virtual disk and the target
virtual disk while the virtual disk copy has a status of In Progress or Pending.
Failed Virtual Disk Copy
A virtual disk copy can fail due to these conditions:
A read error from the source virtual disk
A write error to the target virtual disk
A failure in the storage array that affects the source virtual disk or the
target virtual disk.
When the virtual disk copy fails, a critical event is logged in the Event Log,
and a Needs Attention icon appears in the Array Management Window.
While a virtual disk copy has this status, the host has read-only access to the
source virtual disk. Read requests from and write requests to the target virtual
disk do not take place until the failure is corrected by using the Recovery
Guru.
Preferred RAID Controller Module Ownership
During a virtual disk copy, the same RAID controller module must own both
the source virtual disk and the target virtual disk. If both virtual disks do not
have the same preferred RAID controller module when the virtual disk copy
starts, the ownership of the target virtual disk is automatically transferred to
the preferred RAID controller module of the source virtual disk. When the
virtual disk copy is completed or is stopped, ownership of the target virtual
disk is restored to its preferred RAID controller module. If ownership of the
source virtual disk is changed during the virtual disk copy, ownership of the
target virtual disk is also changed.
Failed RAID Controller Module
You must manually change RAID controller module ownership to the
alternate RAID controller module to allow the virtual disk copy to complete
under all of these conditions:
A virtual disk copy has a status of In Progress
The preferred RAID controller module of the source virtual disk fails
The ownership transfer does not occur automatically in the failover