Home
Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Monitoring servers
This section describes how to use the tools and features that help you monitor a Domino® system.
Monitoring databases
You can monitor database activity, replication, and document deletions.
Monitoring replication of a database
If there are replicas of a database, you can use any of these methods to monitor replication daily.
Replication or save conflicts
Multiple users can simultaneously edit the same document in one copy of a database or edit the same document in different replicas between replication sessions. When these conditions occur, Domino® stores the results of one editing session in a main document and stores the results of additional editing sessions as response documents. These response documents have the title Replication or Save Conflict.
Consolidating replication or save conflicts
Regularly look for and consolidate replication or save conflicts.

Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Administration tools
  Topics in this section describe the tools you can use to administer a Domino® server.
- Managing users
  The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
- Monitoring servers
  This section describes how to use the tools and features that help you monitor a Domino® system.
  - Monitoring the Domino® system
    You can monitor system activity and platform use using the Domino® Administrator or the server console.
  - Server Health Monitor
    You can monitor and troubleshoot performance issues using a number of different tools.
  - Entitlement tracking
    As of Domino 12.0, a new internal mechanism is provided for collecting the highest entitlement that individual users have across a Domino domain. When a user appears in the ACL of a database with Reader access or above and that person has the right to access the server, the user is said to be an entitled user.
  - Domino® domain monitoring (DDM)
    Domino® domain monitoring (DDM) provides one location in the Domino Administrator client that you can use to view the overall status of multiple servers across one or more domains, and then use the information provided by DDM to quickly resolve problems.
  - The Domino® SNMP Agent
    The Domino® SNMP Agent enhances the monitoring and control features of Domino by enabling third-party management stations, which use industry standard SNMP, to manage aspects of the Domino server.
  - Overview of server maintenance
    As a Domino® administrator, a major part of your job is maintaining each server that you administer.
  - Tools for mail monitoring
    Domino® provides three tools that you can use to monitor mail. Message tracking allows you to track specific mail messages to determine if the intended recipients received them. Mail usage reports provide the information you need to resolve mail problems and improve the efficiency of your mail network. Mail probes test and gather statistics on mail routes.
  - Monitoring directory assistance
    You can monitor directory assistance by using Show Xdir command to display information about all the directories a server uses for directory services. You can also view directory assistance statistics.
  - Monitoring databases
    You can monitor database activity, replication, and document deletions.
    - Monitoring database activity using Statlog
      Monitor database activity regularly. If database activity is high and users report performance problems, you can take a number of steps to improve performance.
    - Monitoring replication of a database
      If there are replicas of a database, you can use any of these methods to monitor replication daily.
      - The database replication history
        In the Basics tab of the Database Properties box, there is a Replication History button that opens the window of the same name. The first time one server replica successfully replicates with a replica on another server, Domino® creates an entry in the replication history. The entry contains the name of the other server, as well as the date and time of the replication.
      - Displaying and clearing the replication history
        You can view the replication history. When the replication history displays, if the Action column contains an asterisk (*) next to the action, such as Send* or Receive*, the replication is complete. The presence of the asterisk (*) indicates that replication is complete.
      - Forcing a full database replication
        You can use the Replicate command with the -F option to force a full database replication when replicas of a database get out of sync. The replication occurs on the side and allows users to continue to see replication updates during the full replication.
      - Viewing replication events in the log file
        The Replication Log entries in the Replication Events view of the log file (LOG.NSF) display detailed information about the replication of specific databases.
      - Replication or save conflicts
        Multiple users can simultaneously edit the same document in one copy of a database or edit the same document in different replicas between replication sessions. When these conditions occur, Domino® stores the results of one editing session in a main document and stores the results of additional editing sessions as response documents. These response documents have the title Replication or Save Conflict.
        Consolidating replication or save conflicts
        Regularly look for and consolidate replication or save conflicts.
    - Monitoring deleted documents
      Run the Compact task with the -dl argument to enable logging of data about deleted documents in databases that you specify. The data is logged to entries in deletion log files that are added to the IBM_TECHNICAL_SUPPORT directory on a server. For example, you can log when documents are deleted from mail files to help troubleshoot if users report missing documents.
  - Monitoring a cluster
    Domino® provides several ways to find out what is happening in a cluster and make adjustments to keep the cluster running smoothly and efficiently, so that no server is overloaded. You can monitor failover, workload balancing, and cluster replication to see how efficiently the cluster is running.
  - Monitoring slow or unresponsive servers with the Domino® Diagnostic Probe
    Use the Domino® Diagnostic Probe (DDP), a Java™ utility provided by Support, to monitor servers that have been intermittently slow or unresponsive. The probe is a Java process (dbopen.jar) that runs in the background. The utility probes a specific Domino server over time by invoking database open transactions. If the probe detects a slow response, it will invoke Notes® System Diagnostic (NSD) to gather diagnostic data. This data is used by Support to troubleshoot and determine the cause or causes of the performance degradation.
  - Monitoring Smart Server Startup
    With Smart Server Startup, users are prevented from connecting to a Domino server until it is fully up and ready to accept user requests. For example, during startup of the Domino server after a crash, users can connect to the Domino server only after the server has fully recovered.
  - Monitoring quality of service
    Quality of Service, or QoS, is designed to react to the general operation of a Domino® server in order to keep that server functioning reliably and always available. If QoS detects that a server is not responding or hung, QoS probing can be configured to email an administrator about the problem and/or automatically terminate the server and restart it. QoS log information can also be useful for analysis by Support.
  - Understanding Quality of Service (QoS) behavior and logging
    This topic covers details of QoS including server and server controller behavior during kill events, failover trigger, and log file content.
- Managing servers
  Manage Domino® servers by performing any of these tasks.
- Managing databases
  Topics in this section describe how to set up and manage Domino® databases.

Consolidating replication or save conflicts

Regularly look for and consolidate replication or save conflicts.

About this task

To consolidate a conflict, merge information into one document and remove the other document. Conflicts are easiest to consolidate immediately after they occur, since the conflict document is still closely synchronized with the information in the main document. It is important to consolidate replication or save conflicts quickly, so users access the correct information.

Tip: To locate replication or save conflicts, create a view that displays only conflict documents. Then, to see a conflict document in context with its main document, select the Replication or Save Conflict document in the view that displays conflicts, hold down the CTRL key, and switch to the view that shows the main document.

To consolidate replication or save conflicts, you can save the main document or save the Replication or Save Conflict document

To save the main document

Procedure

Copy any information you want to save from the Replication or Save Conflict document into the main document.
Delete the conflict document.

To save the Replication or Save Conflict document

Procedure

Do one of the following:
- Copy any information you want to save from the main document into the Replication or Save Conflict document.
- If you do not need to save any information from the main document, perform a minor edit in the replication or save conflict document -- for example, delete a space.
Save the conflict document. The conflict document becomes a main document.
Delete the original main document.