Home
Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Managing servers
Manage Domino® servers by performing any of these tasks.
Transaction logging
Domino® transaction logging captures changes made to a database and writes them to a transaction log. The logged transactions are then written to disk in a batch, either when resources are available or when scheduled.
Setting up a Domino® server for transaction logging
You can enable and set up transaction logging on any server.

Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
- Translated documentation
  The HCL Domino 11.0.1 documentation is currently available in the following languages.
- What's new in Domino® 11?
  Learn about all of the new features for administrators in HCL Domino® 11.
- Overview
  Welcome to HCL Domino® Administrator Help.
- Domino trial
  A trial version of HCL Domino® 11.0.1 is available free of charge.
- Installing
  Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Securing
  This section describes security features, including execution control lists, IDs, and SSL.
- 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.
  - Monitoring
    This section describes how to use the tools and features that help you monitor a Domino® system.
  - Managing servers
    Manage Domino® servers by performing any of these tasks.
    - Changing the server administrator
      If the name of the former administrator is explicitly listed in the access control list (ACL) for the Domino® Directory, delete the name of the former administrator from the ACL. Add the name of the new administrator and assign the administrator Manager access.
    - Setting and managing passwords for the server console
      Set server console passwords to protect against unauthorized use of the server console.
    - Decommissioning a Domain Search server
      If you want the server that creates full-text indexes of the Domino® domain to resume duty as a regular Domino server, remove it from the appropriate group in the Domino Directory, edit its Server document, and then delete some files from its directory structure.
    - Decommissioning a server
      You use the Decommission Server Analysis tool when you are consolidating existing servers and/or permanently removing a server from service. Whether you are combining two servers into one server or renaming a server, the result is the same -- the old server name is replaced with the new server name.
    - Deleting a server name
      You can use the Administration Process to delete references to a server from the Domino® Directory, and from database ACLs and Extended ACLs. The Administration Process automatically deletes mail-in database documents and cross-certificate documents as necessary during the Delete Server process.
    - Dropping user sessions on a server
      Dropping user sessions from a server may be useful when you need to make a database or server temporarily unavailable to correct a problem; users can reconnect after you are ready. You can drop one user session or all user sessions for the current database, or selected user sessions, from the server.
    - Finding a server name in the domain with the Domino® Administrator
      You can search for a server name in the domain and then view a log that includes document links and directory links to each occurrence of the server name.
    - Recertifying a server ID
      Use the original certifier to recertify a server ID that has a certificate that is about to expire.
    - Uninstalling a Domino® partitioned server
      You can remove all server partitions from a computer or you can remove just one server partition.
    - Reinstalling or moving a Domino® server from one computer to another
      Use this procedure to reinstall a server if an error occurs and the installer does not complete during the install of an incremental installer, or if the Domino® server is crashing and troubleshooting does not reveal the root cause.
    - Transaction logging
      Domino® transaction logging captures changes made to a database and writes them to a transaction log. The logged transactions are then written to disk in a batch, either when resources are available or when scheduled.
      - How transaction logging works
        Following is a general example of transaction logging from both the administrator's and the employees' points of view.
      - Preparing for transaction logging
        Transaction logging captures all the changes that are made to databases and writes them to a transaction log. The logged transactions are written to disk in a batch when resources are available or at specified intervals.
      - Setting up a Domino® server for transaction logging
        You can enable and set up transaction logging on any server.
      - Changing transaction logging settings
        You can change the transaction logging settings by editing the Server document.
      - Disabling transaction logging for a specific database
        After you set up transaction logging on a server, Domino® logs all databases on that server. You can disable transaction logging of specific databases, but this practice is not recommended because if unlogged databases are corrupted during a system or media failure, you must run the Fixup task to recover the database.
      - View logging
        View logging provides a way to maintain consistent views in failure conditions and allows media recovery to update those views.
      - Using transaction logging for recovery
        Transaction logging is an integral part of recovering from system and media failures. Using transaction logging provides insurance against system failure, but creating regular backups is essential so that you can recover data after a failure.
      - Fault recovery
        You can set up fault recovery to automatically handle server crashes.
      - Enabling fault recovery
        You can enable fault recovery.
      - Specifying a cleanup script for fault recovery
        You can create an optional script that runs before any other cleanup takes place. Use the file FAULT_RECOVERY.ATT to collect the information from the script.
    - Installing and running NSD as a Microsoft™ Windows™ service
      Installing and running NSD as a Microsoft Windows service is no longer available as of Domino 10.
    - Setting up a Fault Reports database
      The Notes/Domino Fault Reports database stores data that is collected at the time of a server crash. Data is collected from both the client and the server and can then be used to measure client reliability and determine the areas where problems exist.
    - Client and server diagnostics
      Use these tasks to perform client and server diagnostics to collect diagnostic information after a server or client crash.
    - Collecting diagnostic information after a server or client crash
      The automatic diagnostic collection tool collects diagnostic data after server and client crashes and sends the collected data to a mail-in database when the server or client restarts. You can then use the collected data to determine the cause of the crash.
    - Using the TECHNICAL_SUPPORT directory
      The IBM_TECHNICAL_SUPPORT database contains data that has been collected using the Domino® Configuration Collector and the Automatic Diagnostic Data Collection tool. It also includes system information files and documents that have been exported from the Domino Directory and saved as .dxl documents using the Save command entered at the Domino server console.
    - The Domino® server log file (LOG.NSF)
      Every Domino® server has a log file (LOG.NSF) that reports all server activity and provides detailed information about databases and users on the server. The log file is created automatically when you start a server for the first time.
    - Controlling the size of the log file
      By default, the log file (LOG.NSF) records information about the Domino® system.
    - The Domino® Web server log (DOMLOG.NSF)
      You can log your server activity and Web server requests to the Domino® Web server log (DOMLOG.NSF) database. This option may be preferable if you want to create views and view data in different ways.
    - Using console log mirroring
      Console log mirroring causes a new server thread to be created which monitors all messages written to the Console Log file and duplicates these messages into another file. When this new file is filled, the thread closes the mirrored file and creates a new file into which subsequent messages are written. You can delete the closed mirrored files at your discretion.
    - Using the Domino® Configuration Tuner to evaluate server settings
      The Domino® Configuration Tuner (DCT) evaluates server settings according to a growing catalog of best practices. All servers in a single domain can be evaluated together. DCT generates reports that explain the issues DCT uncovers, suggests mitigations, and provides references to supporting publications.
    - Activity Logging
      You use activity logging to collect information about the activity in your enterprise. You can use this information to charge users for the amount they use your system, monitor usage, conduct resource planning, and determine if clustering would improve the efficiency of your system.
    - Managing a cluster
      After you have set up a cluster, you can perform tasks to manage it.
  - Managing databases
    Topics in this section describe how to set up and manage Domino® databases.
- Tuning
  Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with HCL Domino® server and Administrator client.
- Notices

Setting up a Domino® server for transaction logging

You can enable and set up transaction logging on any server.

Procedure

Make sure that all the databases you want to log are in the Domino® data directory, either at the root, or in a subdirectory.
From the Domino® Administrator, click the Configuration tab, expand the Server section, and click All Server Documents.
Select the Server document for the Domino® server you want to edit and then click Edit Server.

Click the Transactional Logging tab, complete these fields, and then save the document:

Table 1. Transaction Logging tab
Field	Action
Transactional Logging	Choose one: Enabled -- To start transaction logging Disabled (default) -- To not use transaction logging A server restart is required before the change takes effect.
Log path	Enter the path name location of the transaction log. For best results, use a separate mirrored device, such as a RAID (Redundant Array of Independent Disks) level 0 or 1 device with a dedicated controller. This provides better performance and data integrity than using the default path (\LOGDIR) in the Domino® data directory. Note: If the device is used solely for storing the transaction log, set the Use all available space on log device" field to Yes. A server restart is required before the change takes effect.
Use all available space on log device	For circular and linear logging only. Choose one: Yes -- To use all available space on the device for the transaction log. Choose Yes if you use a separate device dedicated to storing the log. No -- To use the default or specified value in the Maximum log space field.
Maximum log space	For circular and linear logging only. The maximum size, in MB, for the transaction log. Default is 500MB. Maximum is 4096MB (4GB). Allocate a separate disk with at least 1024MB (1GB) of disk space for the transaction log. Domino® formats at least 3 and up to 64 log files, depending on the maximum log space you allocate.
Automatic fixup of corrupt databases	Choose one: Enabled (default) -- To run the Fixup task automatically if a database is corrupted and Domino® cannot use the transaction log to recover it. Domino® assigns a new DBIID and notifies the administrator that a new database backup is required. Disabled -- To not run the Fixup task automatically. Domino® notifies the administrator to run the Fixup task with the -J parameter on corrupted logged databases.
Runtime/Restart performance	This field controls how often Domino® records a recovery checkpoint in the transaction log. This affects server performance as databases may be flushed from the cache to disk. To record a recovery checkpoint, Domino® evaluates each active logged database to determine how many transactions would be necessary to recover each database after a system failure. When Domino® completes this evaluation, it: Creates a recovery checkpoint record in the transaction log that lists each open database and the starting point transaction needed for recovery Forces database changes to be saved to disk if they have not been saved already Choose one: Standard (default and recommended) -- To record checkpoints regularly. Favor runtime -- To record fewer checkpoints. This option requires fewer system resources and improves server run-time performance but causes more of the log to be applied during restart. Favor restart recovery time -- To record more checkpoints. This option improves restart recovery time because fewer transactions are required for recovery.
Logging style	Choose one: Circular (default) -- To re-use the log files and overwrite old transactions. Archived (recommended) -- To re-use the log files after they are archived. A log file can be reused when it is inactive, which means that it does not contain any transactions necessary for a restart recovery. Use a third-party backup utility to copy and archive the existing log. When Domino® using the existing file again to Start, Domino® increments the log file name. If all the log files become inactive and are not archived, Domino® creates additional log files. Linear -- To re-use the log files and overwrite old transactions for log size greater than 4GB. After you change the logging style, Domino® assigns a new DBIID to each database. You must restart the server and perform another full backup