CLUSTERS
Viewing cluster replication events
The Cluster Replicator generates Notes Log Replication documents once an hour and records information about all replication performed during that hour. Each Notes Log Replication document provides information about database replication and any errors that currently exist. An error indicates that an item couldn't be replicated. This is often due to the destination server being unavailable. When an error occurs, the Cluster Replicator retries the replication periodically until it is successful. After the replication is successful, the error is no longer recorded. The Cluster Replicator generates one Notes Log Replication document for each server with which it replicates.
You can view cluster replication events that the Cluster Replicator generates. Do one of the following.
From the Domino Administrator or the Web Administrator
1. In the Server pane, expand All Servers or expand Clusters.
2. Select the server that stores the log file you want to view.
3. Click the Server - Analysis tab.
4. In the Task pane, expand Notes Log or server name's Log, and then click Replication Events.
5. In the Results pane, open the replication document you want to view.
From the Domino server log file
1. Open the Domino server log file.
2. Open the Replication Events view.
3. Open the Notes Log Replication document you want to view.
Example of viewing cluster replication events
The following example shows two databases successfully replicated by the Cluster Replicator from the server Sales/Acme to the server Sales2/Acme. A third database, CUSTOMER.NSF, was modified on Sales/Acme but was not replicated to Sales2/Acme because the server became unavailable.
Sales/Acme
09/04 03:50 PM - 09/04 03:50 PM
Initiated By:
Elapsed Time:
CLUSTER REPLICATOR ON SALES/ACME
0 minutes
Unable to replicate from customer.nsf to Sales2/Acme customer.nsf: Remote system no longer responding.
Viewing cluster replication statistics
You can view cluster replication statistic reports, or you can view a list of cluster replication statistics.
Viewing cluster replication statistic reports
You can use the Domino Administrator or the Web Administrator to view replication statistic reports in the Monitoring Results database. In addition, you can use the Web Administrator to monitor several important cluster replication statistics.
From the Domino Administrator or the Web Administrator Before using this procedure, you must enable statistic reporting in the Monitoring Results database.
1. In the Server pane of the Domino Administrator or the Web Administrator, expand All Servers or expand Clusters.
2. Select the server you want.
4. In the Task pane, expand Monitoring Results, and then expand Statistics Reports.
5. Click Clusters.
6. In the Results pane, open the document you want, and then look in the "Replica cluster statistics" section of the document.
Note If you prefer, you can view these reports directly in the Monitoring Results database (STATREP.NSF). Open the database, expand Statistics Reports, and then click Clusters.
From the Web Administrator only You can use the Web Administrator to monitor a predetermined set of cluster replication statistics. These statistics show cluster replication activity, workload, and status. These statistics refresh automatically every minute.
3. Click the Replication tab.
4. In the Task pane, click Replication Statistics.
Viewing a list of cluster replication statistics
You can view a list of cluster replication statistics from the Domino Administrator, the Web Administrator, or the server console.
From the Domino Administrator or the Web Administrator 1. In the Server pane, expand All Servers or expand Clusters.
3. Click the Server - Statistics tab.
4. In the statistics list, expand Replica, and then expand Cluster.
From the server console Send the following Domino command from the server console:
Using cluster replication statistics to find replication backlogs
During peak activity periods, servers may show an especially high frequency of replication events. Replication backlogs may occur if the Cluster Replicator is unable to handle all replication requests.
Examine the Replica.Cluster.WorkQueueDepth statistic. This statistic shows the number of modified databases awaiting replication. In addition, examine the Replica.Cluster.SecondsOnQueue statistic. This statistic shows how long a database waited to be replicated. If the number of databases waiting to be replicated is consistently much greater than zero, or if the amount of time a database waits to be replicated is consistently longer than you would like, consider using multiple Cluster Replicators to help decrease the replication backlog. You could also decrease the server workload by removing very active databases from the server or by decreasing the number of users who can access the server.
Related topics