Replication bandwidth

[budy]

Yes, I do think that as well. Removing a replication task does not remove the metadata. I do also think, that I have read this somewhere else on the forum already.

Use one replication task to initially sync local and remote and then use another to keep them in sync.

Cheers,
budy

[the_nipper]

Thank you all for the hints! I'll test the issue of kept metadata.


And what do you know about my other issue: It is possible to define an own bandwidth value for each volume. Thus, is it recommended to choose the maximum for all, or is it better to split/grade these?

Best,

Robert

[the_nipper]

Yes, I do think that as well. Removing a replication task does not remove the metadata. I do also think, that I have read this somewhere else on the forum already.

Use one replication task to initially sync local and remote and then use another to keep them in sync.

Cheers,
budy

I tested this and, indeed, it works:

- have a replication task using bandwith X
- volumes are consistent
- stop replication task
- remove replication task
- remove reverse(!) replication task on the mirror
- create new replication task for same volume with different bandwidth Y
- start new replication task
- volumes are consistent _immediately_, no new initial sync necessary!

This is fine.

Robert

[gregg_hughes]

Good afternoon!

We also have had poor performance on replication over a WAN/slow T1 connection. After perusing several postings relating to replication performance, I still don't have a clear picture on what the bandwidth parameter does in setting up a replication job. According to everything I've seen, the whole system, end-to-end, is limited by the slowest link.

So what does this bandwidth parameter do?

Gregg

[Lev]

So what does this bandwidth parameter do?

My experience:

Suppose that the volume replication is running over 100 Mb/ network connection.
Usually DSS can provide the transfer speed much higher than 100 Mb/s.
That means that volume replication will take all available bandwidth of the network
connection, thus considerably slowing down any other possible traffic.

So, in this case setting bandwith to 5 MB/s will be a good solution. In this case replication
will only take 50% of the available bandwidth, leaving enough space for other network activity.

A note: It is only important during initial replication (or in other similar situations when a big amount of changed data must be replicated).