Home
Administering
This documentation provides information about the administration tools for HCL Domino.
Administering with Domino Administrator
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.
Overview of server maintenance
As a Domino® administrator, a major part of your job is maintaining each server that you administer.
Backing up servers that participate in attachment consolidation (DAOS)
When databases on a server are set to participate in attachment consolidation, backing up the server requires an additional step of backing up all .NLO files stored in the Domino® Attachment and Object Service repository. Such files are never modified after creation, so after an initial backup, you need only perform incremental backups.

Administering
This documentation provides information about the administration tools for HCL Domino.
- Administering with AdminCentral
  The AdminCentral application (admincentral.nsf) is automatically created by adminP on the Domino administration server. You can open AdminCentral directly from your Notes Standard or Nomad web client, without the need to start Domino Administrator. This application provides a simplified and easy-to-use way of managing fully functional Notes users and groups in a Domino deployment.
- Administering with Domino Administrator
  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.
    - 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.
      - Server maintenance checklist
        This table lists the server maintenance tasks that you should complete daily, weekly, or monthly to ensure that a server runs efficiently.
      - Backing up the Domino® server
        Back up all Domino® server data files including databases, template files, the NOTES.INI file, and ID files. Following your company's standardized backup procedures, back up files directly to tape or to a file server and then to tape. Never rely only on replication as your method of database backup. A damaged or accidentally changed database may replicate, and then your only recourse is to recover the database from a server backup tape.
      - Backing up servers that participate in attachment consolidation (DAOS)
        When databases on a server are set to participate in attachment consolidation, backing up the server requires an additional step of backing up all .NLO files stored in the Domino® Attachment and Object Service repository. Such files are never modified after creation, so after an initial backup, you need only perform incremental backups.
    - 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 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.

Backing up servers that participate in attachment consolidation (DAOS)

When databases on a server are set to participate in attachment consolidation, backing up the server requires an additional step of backing up all .NLO files stored in the Domino® Attachment and Object Service repository. Such files are never modified after creation, so after an initial backup, you need only perform incremental backups.

About this task

This procedure assumes that, in case of failure, you plan to restore the files to the originating Domino® server. If .NLO files have been encrypted with the originating server's key, they will be readable only when restored to the originating Domino® server. In addition, make sure that the file-access permissions and file ownership rights in the operating system to the DAOS directory remain unchanged after you run the backup utility; the Domino® and Attachment Object Service cannot continue working with an .NLO file if the original owner no longer has access to it.

Procedure

If you are using deferred deletion with DAOS, set the interval to longer than the interval between your backups. For example, if you back up weekly, specify 8 days for the setting "Defer deletion of DAOS objects n days" in the Server document.
Back up .NSF files on the server using a backup utility that is compatible with NSF files. The utility must be able to use the backup and recovery methods of the Domino® C API Toolkit.
Back up the DAOSCAT.NSF and DAOS.CF2 files. These files are located in the data directory.
Back up all .NLO files in your DAOS repository. You can use any flat file backup utility of your choice (such as Tivoli® Storage Manager). If DAOS has created subdirectories, maintain the directory hierarchy in your backup.
After the first backup of the DAOS repository, perform incremental or full backups as desired of both .NSF and .NLO files.
Optional: It is highly recommended that you archive any transaction logs so that changes that occurred after the last backup can be replayed for the most complete restoration of data.