HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 252

Best practices for replication, replication can successfully complete

Page 252 highlights

Best practices for replication To tune your system for best replication performance (and lowest load on the replicating systems), HP recommends the following: 1. The replication destination filesystem must be larger than the filesystem being replicated on the source. HP recommends that the destination be 15% larger than the source. This is necessary to accommodate the temporary files that replication uses while ensuring replication is complete. Note that this increase in size is related to the total size of the files being replicated, not the filesystem they reside on. For instance, if the directories you are replicating represent 100GB of a 5TB filesystem, your destination filesystem need only be 115GB, not almost 6TB. 2. The administrative filesystem should be placed on a high-performance LUN, such as a RAID1 or VRAID1 LUN. 3. Ideally, replication should be the only load resident on the preferred sentinel node. 4. Physical memory for a system being used as the preferred sentinel for a high peak-load replication should have at least 12GB of physical memory and a swap file configured to Linux best practices. This would imply a swap file size of 18-24GB for a 12GB system (1.5 to 2 times physical memory). Note that this should be regarded as a lower limit; if your system is under loads from other activities, system memory may need to go to 16GB or higher. 5. Replication should always use a dedicated network interface and line to the replication destination. Physical separation of the replication load from other network traffic, especially the cluster administrative network, is highly desirable. 6. Monitoring the bandwidth use for the replication link is important to ensure that replication can successfully complete, especially as replication loads change over time. 7. If your data loads permit, replication is most efficient when the replication interval is longer. If possible, a replication interval of five or more minutes will decrease the overall load on the system due to replication. Longer is almost always better from a system load standpoint. 8. If possible, reduce the number of replication mount points and spread the load across multiple filesystems. This will tend to reduce the load on both the individual storage components and the individual nodes in the cluster. This may mean changing the organization of the directories on your cluster, and/or changing the layout of your storage and filesystems. 9. Reducing the number of files that are candidates for being replicated will reduce the load on the source and destination systems. 252 Configure and manage replication

  • 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
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435

Best practices for replication
To tune your system for best replication performance (and lowest load on the
replicating systems), HP recommends the following:
1.
The replication destination filesystem must be larger than the filesystem being
replicated on the source. HP recommends that the destination be 15% larger
than the source. This is necessary to accommodate the temporary files that rep-
lication uses while ensuring replication is complete. Note that this increase in
size is related to the total size of the files being replicated, not the filesystem
they reside on. For instance, if the directories you are replicating represent
100GB of a 5TB filesystem, your destination filesystem need only be 115GB,
not almost 6TB.
2.
The administrative filesystem should be placed on a high-performance LUN, such
as a RAID1 or VRAID1 LUN.
3.
Ideally, replication should be the only load resident on the preferred sentinel
node.
4.
Physical memory for a system being used as the preferred sentinel for a high
peak-load replication should have at least 12GB of physical memory and a
swap file configured to Linux best practices. This would imply a swap file size
of 18-24GB for a 12GB system (1.5 to 2 times physical memory). Note that this
should be regarded as a lower limit; if your system is under loads from other
activities, system memory may need to go to 16GB or higher.
5.
Replication should always use a dedicated network interface and line to the
replication destination. Physical separation of the replication load from other
network traffic, especially the cluster administrative network, is highly desirable.
6.
Monitoring the bandwidth use for the replication link is important to ensure that
replication can successfully complete, especially as replication loads change
over time.
7.
If your data loads permit, replication is most efficient when the replication interval
is longer. If possible, a replication interval of five or more minutes will decrease
the overall load on the system due to replication. Longer is almost always better
from a system load standpoint.
8.
If possible, reduce the number of replication mount points and spread the load
across multiple filesystems. This will tend to reduce the load on both the individual
storage components and the individual nodes in the cluster. This may mean
changing the organization of the directories on your cluster, and/or changing
the layout of your storage and filesystems.
9.
Reducing the number of files that are candidates for being replicated will reduce
the load on the source and destination systems.
Configure and manage replication
252