Viewing cluster replication events and statistics

You can view cluster replication events and statistics from the Domino® Administrator, from the Web Administrator, or in the server log file. You can see information on cluster replication activity, workload, and status, and use statistics to find replication backlogs.

Viewing cluster replication events

About this task

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.

From the Domino Administrator or the Web Administrator

Procedure

  1. In the Server pane, expand either All Servers or 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 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

Procedure

  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

About this task

The following example shows two databases successfully replicated by the Cluster Replicator from the server Sales/Acme to the server Sales2/Renovations. A third database, CUSTOMER.NSF, was modified on Sales/Renovations but was not replicated to Sales2/Renovations because the server became unavailable.

Sales/Renovations
09/04 03:50 PM - 09/04 03:50 PM

Remote Server:   Sales2/Renovations
Initiated By:    CLUSTER REPLICATOR ON SALES/RENOVATIONS
Elapsed Time:    0 minutes

Events
Unable to replicate from customer.nsf to Sales2/Renovations customer.nsf: Remote system no longer responding

Database      Access  Added  Deleted  Updated  KBrec  KBsent  From

Sales2        Manager 34      0       1        3      15      cldbdir.nsf
cldbdir.nsf

Sales2        Manager 0       2       2        1      13      names.nsf
names.nsf	
	
Tip: Run Log Analysis to search the log file (LOG.NSF) and gather all of the replication events into a database.

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

About this task

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.

Before using this procedure, you must enable statistic reporting in the Monitoring Results database.

From the Domino Administrator or the Web Administrator

Procedure

  1. In the Server pane of the Domino Administrator or the Web Administrator, expand either All Servers or Clusters.
  2. Select the server you want.
  3. Click the Server > Analysis tab.
  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.

Results

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

About this task

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.

Procedure

  1. In the Server pane, expand either All Servers or Clusters.
  2. Select the server you want.
  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

Procedure

  1. In the Server pane, expand either All Servers or Clusters.
  2. Select the server you want.
  3. Click the Server > Statistics tab.
  4. In the statistics list, expand Replica, and then expand Cluster.

From the server console

About this task

Send the following Domino command from the server console:

show stat replica.cluster*

The cluster replication statistics begin with "Replica.Cluster." They give you information about cluster replication events, such as the number of documents updated, the number of times the Cluster Replicator retried pending replication, and the number of bytes received during cluster replication.

Using cluster replication statistics to find replication backlogs

About this task

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.