Lotus Domino Administrator 8.5 Help - Creating Replication probes

MONITORING

Creating Replication probes
1. From the IBM Lotus Domino Administrator, click the Files tab.

2. Open the Monitoring Configuration database (EVENTS4.NSF).

3. Choose DDM Configuration.

4. Choose any DDM probe view and then click New DDM Probe.

5. Choose Replication.

6. Complete these fields, and then click Save and Close. The actual fields and tabs that are available to be completed depends on the probe that you choose.

Field Action

Probe Subtype Choose one:

Errors
Replication Check

Probe Description Type a description of the probe.

Which server(s) should run this probe? Choose one:

All servers in the domain -- Runs the probe on all servers in the domain.
Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory.
Only the following servers -- Specify the servers on which the Replication probe will run.
Note You can specify a wild card but you cannot specify a server group.

Which server(s) should be probed? Choose one:

All servers in the domain -- Probes all servers in the domain.
Only the following servers: -- Probes the servers that you specify.
Note You can specify a wild card but you cannot specify a server group.

Select one or more databases to probe Specify the databases to probe. The default is * meaning that all databases are probed.

Select one or more databases not to probe Specify the databases which should not be probed.

Severity Specify the severity level that the probe generates.

Generate an event if the included databases have not replicated within the following interval Specify a number, and then select Minutes, Hours, or Days as the interval.

Check the following modes of replication Choose one or both:

Push -- Monitors the success of one-way replication from one database to one or more specified databases.
Pull -- Monitors the success of replication from one or more databases to another database.

Attempt to diagnose problems Select this check box to have Domino attempt to diagnose problems that the probe reports.

How often should this probe run? Choose one:

Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display.
Daily -- The probe runs once each day. Use the "On which days should this probe run" field to specify the days on which the probe is run.
Weekly -- The probe runs once each week. Use the "On which day of the week should this probe run?" field to specify the day on which the probe is run.
Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.

Defined schedule Specify the number of minutes between each run of the probe.

Should this probe run twenty-four hours per day, seven days per week? Choose one:

Yes -- Run the probe continuously.
No -- Run the probe only on the days and times that you specify. After you choose this option, complete the "On which days should this probe run" field.

On which days should this probe run? Choose the days on which to run the probe.

On which day of the week should this probe run? Choose the day of the week on which to run this probe.

On which day of the month should this probe run? Enter the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.

During which hours of the day should this probe run? Specify the start time in the From field, and the end time in the To field.

At what time should this probe run Choose the time to run the probe.

How should missed probes be handled? Choose one:

Ignore missed probe -- The missed probe is not run or rescheduled.
Run missed probe at startup -- The next time that the server starts, the missed probe runs.
Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.

Related topics

Replication probes

Maintaining DDM Probes

DDM probes

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary

Field	Action
Probe Subtype	Choose one: Errors Replication Check
Probe Description	Type a description of the probe.
Which server(s) should run this probe?	Choose one: All servers in the domain -- Runs the probe on all servers in the domain. Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory. Only the following servers -- Specify the servers on which the Replication probe will run. Note You can specify a wild card but you cannot specify a server group.
Which server(s) should be probed?	Choose one: All servers in the domain -- Probes all servers in the domain. Only the following servers: -- Probes the servers that you specify. Note You can specify a wild card but you cannot specify a server group.
Select one or more databases to probe	Specify the databases to probe. The default is * meaning that all databases are probed.
Select one or more databases not to probe	Specify the databases which should not be probed.
Severity	Specify the severity level that the probe generates.
Generate an event if the included databases have not replicated within the following interval	Specify a number, and then select Minutes, Hours, or Days as the interval.
Check the following modes of replication	Choose one or both: Push -- Monitors the success of one-way replication from one database to one or more specified databases. Pull -- Monitors the success of replication from one or more databases to another database.
Attempt to diagnose problems	Select this check box to have Domino attempt to diagnose problems that the probe reports.
How often should this probe run?	Choose one: Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display. Daily -- The probe runs once each day. Use the "On which days should this probe run" field to specify the days on which the probe is run. Weekly -- The probe runs once each week. Use the "On which day of the week should this probe run?" field to specify the day on which the probe is run. Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.
Defined schedule	Specify the number of minutes between each run of the probe.
Should this probe run twenty-four hours per day, seven days per week?	Choose one: Yes -- Run the probe continuously. No -- Run the probe only on the days and times that you specify. After you choose this option, complete the "On which days should this probe run" field.
On which days should this probe run?	Choose the days on which to run the probe.
On which day of the week should this probe run?	Choose the day of the week on which to run this probe.
On which day of the month should this probe run?	Enter the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.
During which hours of the day should this probe run?	Specify the start time in the From field, and the end time in the To field.
At what time should this probe run	Choose the time to run the probe.
How should missed probes be handled?	Choose one: Ignore missed probe -- The missed probe is not run or rescheduled. Run missed probe at startup -- The next time that the server starts, the missed probe runs. Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.