Dell PowerVault MD3260i CLI Guide - Page 67

Using The Remote Replication Premium Feature, How Remote Replication Works

Page 67 highlights

6 Using The Remote Replication Premium Feature The Remote Replication premium feature provides for online, real-time replication of data between storage arrays over a remote distance. In the event of a disaster or a catastrophic failure on one storage array, you can promote the second storage array to take over responsibility for computing services. Remote Replication is designed for extended storage environments in which the storage arrays that are used for Remote Replication are maintained at separate sites. Virtual disks on one storage array are replicated to virtual disks on another storage array across a fabric SAN. Data transfers can be synchronous or asynchronous. You choose the method when you set up the remote replicated pair. The data transfers occur at Fibre Channel speeds to maintain data on the different storage arrays. Because Remote Replication is storage based, it does not require any server overhead or application overhead. You can use Remote Replication for these functions: • Disaster recovery - Remote Replication lets you replicate data from one site to another site, which provides an exact duplicate at the remote (secondary) site. If the primary site fails, you can use replicated data at the remote site for failover and recovery. You can then shift storage operations to the remote site for continued operation of all of the services that are usually provided by the primary site. • Data vaulting and data availability - Remote Replication lets you send data off site where it can be protected. You can then use the off-site copy for testing or to act as a source for a full backup to avoid interrupting operations at the primary site. • Two-way data protection - Remote Replication provides the ability to have two storage arrays back up each other by duplicating critical virtual disks on each storage array to virtual disks on the other storage array. This action lets each storage array recover data from the other storage array in the event of any service interruptions. How Remote Replication Works When you create a remote replicated pair, the remote replicated pair consists of a primary virtual disk on a local storage array and a secondary virtual disk on a storage array at another site. A standard virtual disk might only be included in one replicated virtual disk pair. The primary virtual disk is the virtual disk that accepts host I/O activity and stores application data. When the replication relationship is first created, data from the primary virtual disk is copied in its entirety to the secondary virtual disk. This process is known as a full synchronization and is directed by the RAID controller module owner of the primary virtual disk. During a full synchronization, the primary virtual disk remains fully accessible for all normal I/O operations. The RAID controller module owner of the primary virtual disk initiates remote writes to the secondary virtual disk to keep the data on the two virtual disks synchronized. The secondary virtual disk maintains a replication (or copy) of the data on its associated primary virtual disk. The RAID controller module owner of the secondary virtual disk receives remote writes from the RAID controller module owner of the primary virtual disk but will not accept host write requests. Hosts are able to read from the secondary virtual disk, which appears as read-only. In the event of a disaster or a catastrophic failure at the primary site, you can perform a role reversal to promote the secondary virtual disk to a primary role. Hosts then are able to read from and write to the newly promoted virtual disk, and business operations can continue. 67

  • 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

6
Using The Remote Replication Premium Feature
The Remote Replication premium feature provides for online, real-time replication of data between storage arrays over a
remote distance. In the event of a disaster or a catastrophic failure on one storage array, you can promote the second
storage array to take over responsibility for computing services. Remote Replication is designed for extended storage
environments in which the storage arrays that are used for Remote Replication are maintained at separate sites. Virtual
disks on one storage array are replicated to virtual disks on another storage array across a fabric SAN. Data transfers
can be synchronous or asynchronous. You choose the method when you set up the remote replicated pair. The data
transfers occur at Fibre Channel speeds to maintain data on the different storage arrays. Because Remote Replication is
storage based, it does not require any server overhead or application overhead.
You can use Remote Replication for these functions:
Disaster recovery – Remote Replication lets you replicate data from one site to another site, which provides an
exact duplicate at the remote (secondary) site. If the primary site fails, you can use replicated data at the remote
site for failover and recovery. You can then shift storage operations to the remote site for continued operation of
all of the services that are usually provided by the primary site.
Data vaulting and data availability – Remote Replication lets you send data off site where it can be protected.
You can then use the off-site copy for testing or to act as a source for a full backup to avoid interrupting
operations at the primary site.
Two-way data protection – Remote Replication provides the ability to have two storage arrays back up each
other by duplicating critical virtual disks on each storage array to virtual disks on the other storage array. This
action lets each storage array recover data from the other storage array in the event of any service
interruptions.
How Remote Replication Works
When you create a remote replicated pair, the remote replicated pair consists of a primary virtual disk on a local storage
array and a secondary virtual disk on a storage array at another site. A standard virtual disk might only be included in
one replicated virtual disk pair.
The primary virtual disk is the virtual disk that accepts host I/O activity and stores application data. When the replication
relationship is first created, data from the primary virtual disk is copied in its entirety to the secondary virtual disk. This
process is known as a full synchronization and is directed by the RAID controller module owner of the primary virtual
disk. During a full synchronization, the primary virtual disk remains fully accessible for all normal I/O operations.
The RAID controller module owner of the primary virtual disk initiates remote writes to the secondary virtual disk to keep
the data on the two virtual disks synchronized.
The secondary virtual disk maintains a replication (or copy) of the data on its associated primary virtual disk. The RAID
controller module owner of the secondary virtual disk receives remote writes from the RAID controller module owner of
the primary virtual disk but will not accept host write requests. Hosts are able to read from the secondary virtual disk,
which appears as read-only.
In the event of a disaster or a catastrophic failure at the primary site, you can perform a role reversal to promote the
secondary virtual disk to a primary role. Hosts then are able to read from and write to the newly promoted virtual disk,
and business operations can continue.
67