Troubleshooting Cluster Replication Issues

Some database changes are not replicating quickly to other servers.

Use the following checklist to troubleshoot problems related to slow replication between servers in a cluster. Check that the following conditions exist:

• The Cluster Replicator is started on the server where the modified database is located. You can check this on the Servers - Status tab of the IBM^® Lotus^® Domino^® Administrator or by sending the following command from the server console:

   show tasks

• The modified database and its replicas on other servers are listed in all the Cluster Database Directories.
• All replicas of the modified databases have the same Replica ID. To check this, open the Databases by Replica ID view in the Cluster Database Directory.
• The Cluster Replicator is not encountering errors when it attempts to replicate to other servers in the cluster. Check the Replica.Cluster.Failed and Replica.Cluster.Retry.Waiting statistics to see if error conditions exist. Also, examine the Replication Events log documents generated by the Cluster Replicator.
• The Cluster Replicator is able to keep up with the current server replication workload. Check the Replica.Cluster.WorkQueueDepth and Replica.Cluster.SecondsOnQueue statistics to determine if there is a backlog of replication requests. If so, consider starting an additional Cluster Replicator.
• Cluster replication is enabled for all replicas of the database. Open the Cluster Database Directory, and check the left column for the letter "X." Databases with the letter "X" in the left column have cluster replication disabled.
• CLREPL_OBEYS_QUOTAS is set to 0 (zero) if you used this setting in the Configurations Settings document or in the NOTES.INI file. When this setting is set to 1, cluster replication obeys the database size quotas that were set by the database administrator. The Cluster Replicator will not push changes to a replica if the changes would result in the replica exceeding its size quota. If CLREPL_OBEYS_QUOTAS is set to 0 or is not present at all, the Cluster Replicator ignores database size quotas.