How to manage your Domino Replication?

Why is replication monitoring important?

How would you know if the replication task is taking too long? That’s not reported in the log file. But then again the replicator task could hang or just fail and you wouldn’t know until users who are complaining about changes not being displayed are calling the service desk.

How can GSX Monitor & Analyzer help?

GSX Monitor can determine the speed of an updated document on one server to be replicated to other servers in the network. This powerful capability provides the administrator a clear vision of how information is being propagated within their enterprise.


Replication can be monitored for any database selected, including templates. There are several areas where the status is reported:

  • Emailed Reports.
  • The replication LED located in the Main View. The color indicates the severity of the most critical and most current error.
  • The Domino Replication view.
  • The Domino Statistics view.

To further enhance the value provided of Replication Monitoring features, GSX Monitor also provides useful and complimentary reporting information:

  • The time taken for an update to replicate to all other servers.
  • If replication is enabled or disabled for a database.
  • The average and maximum time for an update to replicate to another server.
  • The time of last replication for a database.
  • If remote servers are set to the correct time.
  • The server's time zone.
  • The quantity of documents in a database at the time of inspection.
  • The error message reported when a server or database is not accessible.
  • The number of replication conflicts.

Example Replication information GSX Monitor provides:
A change is made at 10:00 on server X. At 11:00 server X is scheduled to replicate with server Y and at 12:00 with server Z. However, the actual replication times are 11:05 and 12:03, respectively. The replication time reported by GSX Monitor is the reason GSX Monitor is capable of reporting this information with precision. GSX Monitor checks the replication has occurred at the document level. If GSX Monitor were to rely on log documents for this data, the level of information found below is unobtainable.

  • 65 minutes to reach server Y
  • 123 minutes to reach server Z

Another place where GSX Monitor can help out is when you need to know if the Lotus Domino server task for replication is still running. That is where task scanning will let you know what happening with your tasks. You can configure it to monitor the 25 most critical tasks on your Lotus Domino server and have it warn you if they are not running or are in a hung or frozen state.


You can select the server and pick from a list of tasks that are currently running on that server and then just leave GSX Monitor to do the rest for you.


It’s all very well having this great replication technology from IBM/Lotus but you need to make sure that it’s being used to best effect. Keeping a regular eye on how long it takes for documents to get around your Domino domain is very useful. Possibly of more importance is the understanding that the replicator server task has not stopped for any reason and being alerted if it is.

GSX Monitor has good features to offer in terms of looking after your Domino replication, but that’s just the start of what GSX Monitor can do for you. Please look at the other features that are available to you and you will see that GSX Monitor and Analyzer are the perfect companion to your IBM Lotus Domino environment.