I’ve clustered two servers and made replicas of a suite of databases on both machines. When I make a change to a document on cluster machine A, how long should it take before the cluster replicator pushes that change to machine B? Also, for this to work at all, does there need to be a connection document from machine A to B? Thanks.
Subject: clustering
The servers should be listed in the same cluster in the Admin console, Configuration tab, Cluster dropdown.
You should have a connection document with a replication schedule enabled. This will catch up your replication if one or the other server has been down.
The server tasks for Clsuter Directory and Cluster Replicator must be running.
Subject: Cluster replication
Jack, to answer your question:
Cluster replication is event-driven, rather than schedule-driven. When the Cluster Replicator learns of a change to a database, it immediately pushes that change to other replicas in the cluster.
If there is a backlog of replication events, the Cluster Replicator stores these in memory until it can push them to the other cluster servers. If a change to the same database occurs before a previous change has been sent, the Cluster Replicator pools these changes and sends them together to save processing time.
Because Domino stores replication events in memory only, both the source and destination servers must be available for the replication to complete successfully.
If a destination server is not available, the Cluster Replicator continues to store the events in memory until the destination server becomes available. The Cluster Replicator attempts periodically to push these replication events to the destination server. The interval between these attempts starts at one hour and increases over time to a maximum of one day.
If the source server shuts down before the replication completes, the replication events in memory are lost. For this reason, you should use standard replication (the REPLICA task) to perform immediate replication with all members of the cluster whenever you restart a cluster server. It is also a good idea to schedule replication between cluster servers on a regular basis, such as several times per day, to ensure that databases remain synchronised.
HTH
Cheers
Paul