My environment currently have four servers in a cluster. 2 servers located in two different geographical locations. ex… 2servers west coast, 2servers east coast. Is there a way to streamline replication so that only one of the servers on the west coast will replicate across the network to one of the servers on the east rather than all servers replicating with each other. I would like to set this up to minimize the amount of traffic going across our WAN. Thanks
Subject: Cluster Replication
You can stop the cluster replicator threads and use scheduled replication instead.
If you haven’t enabled port compression I recommend to do so since the small CPU overhead is well worth the bandwidth savings.
Subject: Cluster Replication
Streaming cluster replication in R8 was designed for this type of scenario.
Subject: Cluster Replication
If you have Esat coast (server A and server B) and West coast (server C and D) and the connection bewtween east and west is at least 100Mb, then you should be OK to cluster all servers, anything below this and you may start to see the Cluster Manager cannot keep up. If you look at stats Replica.Cluster, SecondsOnQueue and WorkQueueDepth…you will see if the Cluster is “kepping up”. If the cluster is not 100Mb, then it might be better to cluster A + B and C+D, especially if you want to reduce bandwidth across WAN. Then create 1 connection doc from server A and make the destination server the name of the C + D cluster. A will try to replicate with the servers listed in cluster C+ D alphabetically, so in this instance it will repl’ with C first, if that is not available then it will try with D. Create another connection from C to the A+B cluster. For full redudancy, you should also create a connection doc from C and D to the respective other cluster. It would also be prudent to create a doc between A and B and C and D. You then have 6 connection docs, still better than 1 from each server, to each other server, whjich would be 10 docs.
Set the replication schedule to something sensible (check in log how long each replication event is taking).