HP StorageWorks 2/140 FW 08.01.00 McDATA Products in a SAN Environment Plannin - Page 180

BC/DR applications., Synchronous remote data replication RDR/S

Page 180 highlights

Implementing SAN Internetworking Solutions 4 • Synchronous remote data replication (RDR/S) - This operational mode ensures a remote data copy (identical to the primary copy) is created at the time the primary data is created. An update operation does not complete until confirmed at both the primary and mirrored sites. An incomplete operation rolls back at both locations, ensuring the remote copy is a mirror image of the primary copy. RDR/S is synonymous with disk mirroring. The advantage to using RDR/S is quick data recovery. Operation at a remote, mirrored site begins immediately if operation at the primary site is disrupted. The problem with RDR/S is distance limitation. Although propagation of laser light pulses can theoretically extend to infinity, latency is an issue because propagation delays lengthen with increased link distance. These delays adversely impact performance by forcing an application to wait for confirmation of I/O operation at local and remote sites. This means RDR/S operation is distance-limited, depending on application response time tolerance and other factors. RDR/S is ideal for shorter metropolitan distances and real-time disk mirroring and is an appropriate BC/DR solution for enterprises requiring fast data recovery, minimal data loss, and protection against database integrity problems. • Asynchronous remote data replication (RDR/A) - This operational mode does not require a response indicating completion of a remote transaction before local I/O operations resume. Replication software on the remote storage array controller ensures data is successfully written to the remote site. Standard disk backup and tape vaulting are RDR/A operations. RDR/A may lose data transactions during an unplanned failover to a remote site. However, after post-outage transaction logs are applied to the remote data image, operations can usually resume. Catastrophic events can occur anywhere. However, it is unlikely an event will span a large geographical area or two exclusive events will simultaneously occur in two locations. Therefore, to protect critical data (required for business continuance), it is prudent to replicate the data at a remote site thousands of miles from the primary site. Because there is no propagation delay involved in confirming remote transactions, RDR/A can span virtually any geographical distance and is ideal for long-distance BC/DR applications. 4-38 McDATA Products in a SAN Environment - Planning Manual

  • 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

4
4-38
McDATA Products in a SAN Environment - Planning Manual
Implementing SAN Internetworking Solutions
Synchronous remote data replication (RDR/S) -
This operational
mode ensures a remote data copy (identical to the primary copy)
is created at the time the primary data is created. An update
operation does not complete until confirmed at both the primary
and mirrored sites. An incomplete operation rolls back at both
locations, ensuring the remote copy is a mirror image of the
primary copy. RDR/S is synonymous with disk mirroring.
The advantage to using RDR/S is quick data recovery. Operation
at a remote, mirrored site begins immediately if operation at the
primary site is disrupted. The problem with RDR/S is distance
limitation. Although propagation of laser light pulses can
theoretically extend to infinity, latency is an issue because
propagation delays lengthen with increased link distance. These
delays adversely impact performance by forcing an application to
wait for confirmation of I/O operation at local and remote sites.
This means RDR/S operation is distance-limited, depending on
application response time tolerance and other factors.
RDR/S is ideal for shorter metropolitan distances and real-time
disk mirroring and is an appropriate BC/DR solution for
enterprises requiring fast data recovery, minimal data loss, and
protection against database integrity problems.
Asynchronous remote data replication (RDR/A) -
This
operational mode does not require a response indicating
completion of a remote transaction before local I/O operations
resume. Replication software on the remote storage array
controller ensures data is successfully written to the remote site.
Standard disk backup and tape vaulting are RDR/A operations.
RDR/A may lose data transactions during an unplanned failover
to a remote site. However, after post-outage transaction logs are
applied to the remote data image, operations can usually resume.
Catastrophic events can occur anywhere. However, it is unlikely
an event will span a large geographical area or two exclusive
events will simultaneously occur in two locations. Therefore, to
protect critical data (required for business continuance), it is
prudent to replicate the data at a remote site thousands of miles
from the primary site. Because there is no propagation delay
involved in confirming remote transactions, RDR/A can span
virtually any geographical distance and is ideal for long-distance
BC/DR applications.