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

Replicate to Another Container in a Cluster, About NAS Replica Containers

Page 287 highlights

• Both groups must be running PS Series firmware version 7.0 or later, and the clusters on those groups must be running FS Series firmware version 3.0 or later. To perform single-step failback to primary: 1. Click NAS, expand NAS Cluster, and expand Local Containers. 2. Select the recovery container. 3. Click Failback to primary. The Failback to Primary message is displayed. 4. Click Yes. The Replicate Recovery Container message is displayed. 5. Type the account name and password for the array on the primary site and click OK. To monitor the failback operation on the recovery container, display the Alarms and Operations toolbar and click the Failback Operations tab. About NAS Replica Containers NAS replica containers reside on the remote (destination) replication partner cluster and contain replicated data from the source container. As with replica volumes, you can temporarily or permanently promote replica containers to recovery containers and grant hosts access to recovery container data. Unlike source containers, you cannot create snapshots of replica containers. However, any replicas of the source container are replicated to the destination partner. The following considerations apply to replica containers: • The NAS container reserve on the replication partner must have enough free space to store the replica. • Unlike volume replication, which retains a replica set of previously created replicas, the system retains only the current replica of the source container in a NAS container replication configuration. To roll back to a previous point in time, you must use snapshots. • You can either replicate the container to a new replica container or you can specify that the container be replicated to an existing replica container. • The system assigns names to new replica containers as follows: - The group gives the replica container the name of the source container, with a randomly generated four-digit string appended to the end of its name. For example, if you replicate a container named ContainerA, the replica might be named ContainerA_8970. - If the length of the container name, combined with that of the appended string, is more than 229 characters, the system shortens the replica container name to be 229 characters long. Fewer characters are accepted for this field if you type the value as a Unicode character string, which takes up a variable number of bytes, depending on the specific character. • If you replicate to an existing container: - The destination container must either be an empty container containing no data, or a container to which the source container has previously replicated. - The source and replica containers do not need to be the same size. Whenever replication occurs, the group automatically adjusts the size of the replica container so that it either shrinks or grows to match that of the source container. - All data previously residing on the container is overwritten and cannot be recovered. • If read-only access is enabled on a replica container, it appears in the list of containers on the destination cluster. NOTE: Replica containers count toward the total number of containers in the group. See the Dell EqualLogic PS Series Storage Arrays Release Notes for the maximum number of containers allowed in a group. • Container Replication of configuration information about SMB shares and NFS exports from a NAS container to a replica container might be delayed for several minutes. This delay will have no effect on the replication of the data itself, but might affect your ability to access the data because you might have to recreate recent configuration updates. If you replicate immediately, the first replication might not have all the data, but subsequent replications will. Replicate to Another Container in a Cluster If the original source container is no longer available, you can configure the recovery container to replicate to another container in the original source cluster. However, if the original source container is available, Dell recommends failing back to it. Failing back to the original source container takes less time than failing back to a new container. About Data Recovery 287

  • 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

Both groups must be running PS Series
firmware
version 7.0 or later, and the clusters on those groups must be running FS Series
firmware
version 3.0 or later.
To perform single-step failback to primary:
1.
Click
NAS
, expand
NAS Cluster
, and expand
Local Containers
.
2.
Select the recovery container.
3.
Click
Failback to primary
. The Failback to Primary message is displayed.
4.
Click
Yes
. The Replicate Recovery Container message is displayed.
5.
Type the account name and password for the array on the primary site and click
OK
.
To monitor the failback operation on the recovery container, display the Alarms and Operations toolbar and click the
Failback
Operations
tab.
About NAS Replica Containers
NAS replica containers reside on the remote (destination) replication partner cluster and contain replicated data from the source
container. As with replica volumes, you can temporarily or permanently promote replica containers to recovery containers and grant
hosts access to recovery container data.
Unlike source containers, you cannot create snapshots of replica containers. However, any replicas of the source container are
replicated to the destination partner.
The following considerations apply to replica containers:
The NAS container reserve on the replication partner must have enough free space to store the replica.
Unlike volume replication, which retains a replica set of previously created replicas, the system retains only the current replica of
the source container in a NAS container replication
configuration.
To roll back to a previous point in time, you must use
snapshots.
You can either replicate the container to a new replica container or you can specify that the container be replicated to an existing
replica container.
The system assigns names to new replica containers as follows:
The group gives the replica container the name of the source container, with a randomly generated four-digit string
appended to the end of its name. For example, if you replicate a container named
ContainerA
, the replica might be named
ContainerA_8970
.
If the length of the container name, combined with that of the appended string, is more than 229 characters, the system
shortens the replica container name to be 229 characters long. Fewer characters are accepted for this
field
if you type the
value as a Unicode character string, which takes up a variable number of bytes, depending on the
specific
character.
If you replicate to an existing container:
The destination container must either be an empty container containing no data, or a container to which the source container
has previously replicated.
The source and replica containers do not need to be the same size. Whenever replication occurs, the group automatically
adjusts the size of the replica container so that it either shrinks or grows to match that of the source container.
All data previously residing on the container is overwritten and cannot be recovered.
If read-only access is enabled on a replica container, it appears in the list of containers on the destination cluster.
NOTE: Replica containers count toward the total number of containers in the group. See the
Dell EqualLogic PS
Series Storage Arrays Release Notes
for the maximum number of containers allowed in a group.
Container Replication of
configuration
information about SMB shares and NFS exports from a NAS container to a replica
container might be delayed for several minutes. This delay will have no
effect
on the replication of the data itself, but might
affect
your ability to access the data because you might have to recreate recent
configuration
updates. If you replicate immediately, the
first
replication might not have all the data, but subsequent replications will.
Replicate to Another Container in a Cluster
If the original source container is no longer available, you can
configure
the recovery container to replicate to another container in the
original source cluster. However, if the original source container is available, Dell recommends failing back to it. Failing back to the
original source container takes less time than failing back to a new container.
About Data Recovery
287