25.06.2013 Views

Lotus Domino Administrator 7 Help - Lotus documentation

Lotus Domino Administrator 7 Help - Lotus documentation

Lotus Domino Administrator 7 Help - Lotus documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The following two statistics record the causes of data loss.<br />

Statistic Explanation<br />

server.RemoteConsole.AsyncQueueOverrun Number of times that the asynchronous queue request<br />

was lost.<br />

server.RemoteConsole.BufferOverrun Number of times that data was lost because more<br />

console output was generated than was sent over the<br />

wire.<br />

Replication -- Troubleshooting<br />

These topics describe how to troubleshoot replication.<br />

v Tools for troubleshooting replication describes tools you can use for troubleshooting replication<br />

problems.<br />

v Replication - Problems and error messages describes problems and errors that users or <strong>Domino</strong> servers<br />

may experience during replication.<br />

You can also search for solutions to common problems on the IBM <strong>Lotus</strong> Support Services Web site at<br />

www.ibm.com/software/lotus/support/.<br />

Tools for troubleshooting replication: Database access control list problems, server crashes, protocol<br />

problems, and incorrectly configured Connection documents are common causes of replication errors. Use<br />

these tools to troubleshoot replication.<br />

Cluster replication: The log file (LOG.NSF) provides helpful information for troubleshooting replication<br />

problems within a cluster.<br />

Log file: To access the log, from the <strong>Domino</strong> <strong>Administrator</strong>, click the Servers - Analysis tab and select<br />

the log file for the server you want to check. Then check for replication problems in these views:<br />

v Miscellaneous events<br />

v Phone calls<br />

v Replication events<br />

Tip: You can also check replication events from the Replication tab in the <strong>Domino</strong> <strong>Administrator</strong>.<br />

Edit the NOTES.INI file to include the Log_Replication setting, which allows you to display detailed<br />

replication information in the log.<br />

Monitoring Configuration: The Monitoring Results database (STATREP.NSF) is a repository for<br />

pre-configured and custom statistics. It is created when you load the Collect task, if it doesn’t already<br />

exist. You can set alarms for some of these statistics. For example, you might set an alarm to generate a<br />

Failure report when more than three attempted replications generate an error. You can also report<br />

statistics to any database designed for this purpose, although typically the database is the Monitoring<br />

Results database (STATREP.NSF).<br />

Note that you can edit the NOTES.INI file to include the Repl_Error_Tolerance setting, which increases<br />

the number of identical replication errors between two databases that a server tolerates before it<br />

terminates replication. The default tolerance is 2 errors. The higher the value, the more often messages<br />

such as ″Out of disk space″ appear.<br />

If you run the Event task on a server, you can set up an Event Monitor document to report replication<br />

problems. You can also create a Replication Monitor document that notifies you if a specific database fails<br />

to replicate within a certain time. To view events from the <strong>Domino</strong> <strong>Administrator</strong>, click the Server -<br />

Analysis tab, click Statistics - Events, and then view the desired report.<br />

1488 <strong>Lotus</strong> <strong>Domino</strong> <strong>Administrator</strong> 7 <strong>Help</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!