Netgear RDD516 ReadyDATA OS 1.4 Software Manual - Page 195

About Replication, Resume Local Replication, Monitor and Manage Local Replication

Get Netgear RDD516 PDF manuals and user guides View all Netgear RDD516 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 195 highlights

ReadyDATA OS 1.4 • Resume Local Replication • Monitor and Manage Local Replication The ReadyDATA supports backup and recovery operations through its advanced snapshot functionality. For information about snapshots, see Manage Snapshots for Shares and LUNs on page 177. Replication is specifically between two ReadyDATA storage systems on which shares and LUN can be mirrored. About Replication Replication capabilities are integrated into the ReadyDATA, and you do not need to install a replication add-on. You can enable replication with the simple click of a button. You have the choice of managing replication locally or accessing the NETGEAR ReadyDATA Replicate™ software application so that you can use its centralized management console to configure the replication settings (see Access ReadyDATA Replicate and Register Systems on page 197). ReadyDATA replication supports two types of replication: • Periodic replication This type of replication is driven by the clock. Data is replicated periodically, from once per hour to once per month, based on how you schedule replication. This configuration collects changes that occur over the selected time period and replicates them in line with the replication schedule. • Continuous replication This type of replication is driven by activity at the source system. Data is replicated to the destination device constantly. Whenever new blocks are written on the source system, they are immediately sent to the destination system. If a disaster occurs, the most current data possible is in a secondary location. For optimum protection, use continuous replication rather than periodic replication. You can configure replication only per individual share or LUN, that is, you cannot configure replication at the system level. You select a share or LUN as the source of the replication, and a volume on the remote system as the destination for the replication. The replication process leverages the information that is contained in special hidden snapshots to minimize the time it takes to determine what block-based data needs to be moved between the systems. These hidden snapshots are not the same as the regular snapshots that you create manually or set up to be created automatically. Replication of an incomplete hidden snapshot resumes from the point where it failed, that is, if a 200 MB snapshot fails to replicate at 90 percent completion, replication resumes at 90 percent completion to replicate the remaining 20 MB. If you use the ReadyDATA Replicate™ software application, you do not use an explicit destination IP address. Data that is replicated over the Internet is automatically encrypted for increased safety. If you manage replication locally, you must establish the destination by using an IP address or domain name, and you must exchange access keys between both systems. Backup, Replication, and Recovery 195

  • 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
Backup, Replication, and Recovery
195
ReadyDATA OS 1.4
•
Resume Local Replication
•
Monitor and Manage Local Replication
The ReadyDATA supports backup and recovery operations through its advanced snapshot
functionality. For information about snapshots, see
Manage Snapshots for Shares and LUNs
on page
177. Replication is specifically between two ReadyDATA storage systems on which
shares and LUN can be mirrored.
About Replication
Replication capabilities are integrated into the ReadyDATA, and you do not need to install a
replication add-on. You can enable replication with the simple click of a button. You have the
choice of managing replication locally or accessing the NETGEAR ReadyDATA Replicate™
software application so that you can use its centralized management console to configure the
replication settings (see
Access ReadyDATA Replicate and Register Systems
on page
197).
ReadyDATA replication supports two types of replication:
•
Periodic replication
This type of replication is driven by the clock. Data is replicated periodically, from once
per hour to once per month, based on how you schedule replication. This configuration
collects changes that occur over the selected time period and replicates them in line with
the replication schedule.
•
Continuous replication
This type of replication is driven by activity at the source system. Data is replicated to the
destination device constantly. Whenever new blocks are written on the source system,
they are immediately sent to the destination system. If a disaster occurs, the most current
data possible is in a secondary location. For optimum protection, use continuous
replication rather than periodic replication.
You can configure replication only per individual share or LUN, that is, you cannot configure
replication at the system level. You select a share or LUN as the source of the replication,
and a volume on the remote system as the destination for the replication.
The replication process leverages the information that is contained in special hidden
snapshots to minimize the time it takes to determine what block-based data needs to be
moved between the systems. These hidden snapshots are not the same as the regular
snapshots that you create manually or set up to be created automatically.
Replication of an incomplete hidden snapshot resumes from the point where it failed, that is,
if a 200 MB snapshot fails to replicate at 90 percent completion, replication resumes at
90
percent completion to replicate the remaining 20 MB.
If you use the ReadyDATA Replicate™ software application, you do not use an explicit
destination IP address. Data that is replicated over the Internet is automatically encrypted for
increased safety.
If you manage replication locally, you must establish the destination by using an IP address
or domain name, and you must exchange access keys between both systems.