MONITORING
Use the Replication - Replication Check probe to filter out replication of databases that do not require replication, and to closely monitor replication of those databases that require frequent replication. Critical system databases, such as NAMES.NSF, EVENTS4.NSF, and ADMIN4.NSF which are used across servers and that are required to be up-to-date, can be monitored more often than less-important databases. You can also define a lower tolerance for conditions that create events on system-critical databases than you would define for conditions that create events on non-critical databases.
Replication on selected servers and databases is monitored according to the schedule specified in the Probe document.
When you run the Replication -- Errors probe, replication occurs as it typically would, but events are reported to DDM. This probe may also report some conditions that are not errors, but that are not desired behavior. For example, this probe may report Replication Note Errors when the replication is successful but some notes are not replicated. If the destination database does not have the source database in its ACL, and there have been changes to the source database, the notes in the source database which are new or updated are not replicated to the destination server because of the ACL. The replication probe will report this and include a document link to the notes that did not replicate. The Replication -- Errors probe may also report replication conflicts in DDM and include a document link to the conflict document. This is not a true error condition for replication but it may not be desired behavior; therefore, it is reported.
The Replication -- Replication Check probe takes null replication into consideration. Null replication occurs when a database is up-to-date and no replication is required, but the replication is attempted. Null replication is not reported in the DDM database. Previously, IBM® Lotus® Domino® had similar functionality but it took into account only those replications which resulted in the replication history being updated (only successful replications and databases which were not up-to-date). In DDM, the replication check probe takes into account a replication attempt where the files are up-to-date. Including up-to-date replications removes many of the false reports indicating that replication on a database has not occurred.
Note In hub-and-spoke topologies, replication is typically one-way only. Do not monitor replication in a direction in which replication is disabled.
This table contains the names and descriptions of the Replication probes that you can define.