Dell EqualLogic PS6210XS EqualLogic Group Manager Administrator s Guide PS Ser - Page 301

SyncActive Volume Unavailable, Volume In Sync, Volume Out of Sync

Page 301 highlights

• Until all tracked changes are written, the data in the SyncAlternate volume is valid only up to the point in time when the volume went out of sync. • While changes are being tracked or when tracked changes are being written back to the SyncAlternate volume, performance might be temporarily degraded. Figure 34. Tracked Changes Written to SyncAlternate Volume 5. When all tracked changes are written, the volume goes back in sync. 6. New writes are simultaneously written to both the SyncActive and SyncAlternate volumes, and normal synchronous replication operations resume. SyncActive Volume Unavailable If a malfunction occurs in the SyncActive pool, or some other event has occurred causing the volume to go offline, you can safely switch or fail over to the SyncAlternate volume. See the following sections. Volume In Sync If the volume is in sync, you can switch to the SyncAlternate volume. Although host access to the volume is disrupted during the switch, no initiator changes are required. Volume Out of Sync 1. Log in to the Group Manager GUI using an IP address that belongs to a group member in the pool containing the SyncActive volume. Do not use the group IP address. 2. Set the volume offline. 3. Verify that no initiators are attempting to reconnect to the volume. 4. Attempt to fail over the volume. CAUTION: Failovers should be performed only under extraordinary circumstances, or in cases where you can be sure that the failover will not destroy any data. If you fail over to the SyncAlternate while the volume is out of sync, any changes written to the volume since it went out of sync will be written to a snapshot. As with other snapshots, this snapshot can be cloned or restored, but is also subject to deletion by the group's snapshot retention policy. If the snapshot is deleted, its data will be lost and cannot be recovered. If the failover was successful: • Log in to the Group Manager GUI using an IP address that belongs to a group member in the pool containing the SyncAlternate volume. Do not use the group IP address. If the failover was not successful: About Synchronous Replication 301

  • 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

Until all tracked changes are written, the data in the SyncAlternate volume is valid only up to the point in time when the
volume went out of sync.
While changes are being tracked or when tracked changes are being written back to the SyncAlternate volume,
performance might be temporarily degraded.
Figure 34. Tracked Changes Written to SyncAlternate Volume
5.
When all tracked changes are written, the volume goes back in sync.
6.
New writes are simultaneously written to both the SyncActive and SyncAlternate volumes, and normal synchronous replication
operations resume.
SyncActive Volume Unavailable
If a malfunction occurs in the SyncActive pool, or some other event has occurred causing the volume to go
offline,
you can safely
switch or fail over to the SyncAlternate volume. See the following sections.
Volume In Sync
If the volume is in sync, you can switch to the SyncAlternate volume. Although host access to the volume is disrupted during the
switch, no initiator changes are required.
Volume Out of Sync
1.
Log in to the Group Manager GUI using an IP address that belongs to a group member in the pool containing the SyncActive
volume. Do not use the group IP address.
2.
Set the volume
offline.
3.
Verify that no initiators are attempting to reconnect to the volume.
4.
Attempt to fail over the volume.
CAUTION: Failovers should be performed only under extraordinary circumstances, or in cases where you can be
sure that the failover will not destroy any data.
If you fail over to the SyncAlternate while the volume is out of sync, any changes written to the volume since it went out of
sync will be written to a snapshot. As with other snapshots, this snapshot can be cloned or restored, but is also subject to
deletion by the group’s snapshot retention policy. If the snapshot is deleted, its data will be lost and cannot be recovered.
If the failover was successful:
Log in to the Group Manager GUI using an IP address that belongs to a group member in the pool containing the
SyncAlternate volume. Do not use the group IP address.
If the failover was not successful:
About Synchronous Replication
301