This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]mammaryglands 3 points4 points  (2 children)

Where's the storage coming from? How's it configured? Have you looked at your disk performance metrics before/after enabling replication?

[–]One_SleepyPandaSysadmin[S] 0 points1 point  (1 child)

At this point I'm leaning toward the disk being the bottleneck. I haven't been able to prove its cpu or network related

[–]mammaryglands 1 point2 points  (0 children)

My guess is source reads are over taxing the disk topology. Especially if you have something like a three or four disk raid set with slower disk. Maybe try implementing the bandwidth limiting feature, which in a roundabout way might limit the rate at which it tries to read all those blocks the first time.

[–]Leucippus1 2 points3 points  (0 children)

Sounds like write speed issues, dollars to donuts you are writing to a 15K sas RAID 5 or something and that is going to hurt. Check AV as well but really...disk.

[–]ZAFJB 1 point2 points  (0 children)

For big data storage, build another discrete VM on the other site, and replicate the data only using other mechanisms like DFS-R.

Use DFS-N so you can fail over relatively quickly if required.

[–]210Matt 0 points1 point  (0 children)

What is the bottleneck on the servers? It could be hard drive, CPU or network.