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 databases
Topics in this section describe how to set up and manage Domino® databases.
Attachment consolidation
The Domino® server employs the Domino Attachment and Object Service (DAOS) to save significant space at the file level by sharing data identified as identical between databases (applications) on the same server. Document attachments are the first components to use the DAOS feature in Domino.
DAOS tier 2 storage
Domino Attachment Object Service (DAOS) tier 2 storage enables you to use an S3-compatible storage service to store older attachment objects that haven't been accessed within a specified number of days. This feature allows you to reduce the amount of data stored on Domino® servers that use DAOS. It can also improve the performance of any incremental file backups that you do for DAOS.
DAOS tier 2 best practices
Follow these best practices for DAOS tier 2 storage.
Amazon S3 security guidelines
The following guidelines apply if you are using AWS S3 for DAOS tier 2 storage.

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.
  - Managing databases
    Topics in this section describe how to set up and manage Domino® databases.
    - Database design, management, and administration
      The tasks involved with application design, database design, database management, and Domino® system administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino system administration.
    - Increase the document summary data limit to 16 MB
      You can increase the document summary data limit on Notes 9 databases to 16 MB.
    - Organizing databases on a server
      You can organize databases in folders.
    - Attachment consolidation
      The Domino® server employs the Domino Attachment and Object Service (DAOS) to save significant space at the file level by sharing data identified as identical between databases (applications) on the same server. Document attachments are the first components to use the DAOS feature in Domino.
      - Marking a database for attachment consolidation
        Enable the setting Use Domino Attachment and Object Service on the Advanced tab of the database properties to reduce the total cost of ownership of maintaining any Notes® database by storing attached files in a separate data repository on the Domino® server. This setting reduces document overhead for all participating databases on a server by maintaining a single copy of any attachment that can then be used in multiple documents in any database on the server.
      - Specifying server settings for attachment consolidation
        Before setting up attachment consolidation on a Domino® server by enabling the Domino Attachment and Object Service, decide where to place files and how large files should be before consolidation. On each server that uses attachment consolidation, you specify the directory where you want to create the resulting repository of shared file attachments. If the number of DAOS (.NLO) files in the directory becomes too large for your operating system limit, Domino creates additional subdirectories as needed.
      - How attachment consolidation works
        The information in this topic describes what happens to an attachment during consolidation.
      - The Domino® Attachment and Object Service (DAOS)
        In the Domino® Server document, the value in the Store file attachments in DAOS field on the DAOS tab disables or enables the operation of the Domino Attachment and Object Service as soon as the Server document is saved.
      - DAOS tier 2 storage
        Domino Attachment Object Service (DAOS) tier 2 storage enables you to use an S3-compatible storage service to store older attachment objects that haven't been accessed within a specified number of days. This feature allows you to reduce the amount of data stored on Domino® servers that use DAOS. It can also improve the performance of any incremental file backups that you do for DAOS.
        Configuring a credential store for DAOS tier 2 storage
        Before you enable DAOS tier 2 storage, configure a Domino® credential store to store the credentials that are used for connections to the storage service.
        Enabling DAOS tier 2 storage
        After you configure the credential store, enable DAOS tier 2 storage on Domino servers. Follow the procedure that corresponds to your storage service.
        Tell daosmgr commands for tier 2 storage
        The following tell daosmgr commands are available for DAOS tier 2 storage.
        DAOS tier 2 statistics
        Several Domino statistics are available for DAOS tier 2 storage.
        DAOS tier 2 best practices
        Follow these best practices for DAOS tier 2 storage.
        Backup of DAOS tier 2 objects
        Two options are available for backup of DAOS tier 2 objects.
        Changing the DAOS tier 2 configuration
        Use the following guidelines for changing the DAOS tier 2 configuration. Exercise caution when changing settings.
        Amazon S3 security guidelines
        The following guidelines apply if you are using AWS S3 for DAOS tier 2 storage.
        Reverting use of DAOS tier 2 storage
        HCL Domino does not currently provide an automated way to move DAOS objects from tier 2 storage to tier 1 storage. The following steps describe how to revert manually.
        Reverting to a previous version of Domino
        If you want to revert a Domino server with DAOS tier 2 enabled to an earlier Domino version that does not support DAOS tier 2, for example, Domino 10.x or 9.x, first move all tier 2 DAOS objects to tier 1. Otherwise, your reverted 10.x or 9.x server will be unable to access any objects stored in tier 2.
      - Managing the attachment storage repository
        On a Domino® server, as the Domino Attachment and Object Service (DAOS) repository grows to accommodate a greater number of attachments, multiple subdirectories are automatically created on the DAOS base path to balance the data load. You can move or store the repository and its data.
      - How using attachment consolidation affects a user's mail file quota
        When calculating the size of a mail file to determine whether it conforms to configured mail quota or warning threshold limits, Domino® treats attachments stored using the Domino Attachment and Object Service as though each user owned the entirety of the attachment file. Thus, the full size of every message delivered to a mail file that uses DAOS counts against the mail file quota.
      - Object copy optimization for DAOS
        The Notes® client recognizes that DAOS is enabled on the Domino® server, and DAOS is able to improve connection speed by refraining from transmitting unnecessary copies of attachments between clients and DAOS-enabled servers.
      - Encrypting consolidated attachments
        By default, the attachment files (.NLO files) created and stored by the Domino® Attachment and Object Service (DAOS) are encrypted. You can use a NOTES.INI setting to either disable or re-enable encryption for all .NLO files created thereafter in the repository.
      - Setting a time window for DAOS resynchronization
        The Domino® administrator can specify when Domino Attachment and Object Service (DAOS) resynchronization should run on a server, so that peak production hours can be avoided.
      - DAOS backup and restore
    - Full-text indexes for single databases
      You can create full-text indexes to allow users to quickly search for information in databases. To search in a database, users enter a word or phrase in the search bar of the database to locate all documents containing the word or phrase.
    - Database libraries
      You can create a database library that contains databases that pertain to a specific collection of users or to a specific topic. For example, a corporate database library might include all databases that deal with corporate policies and procedures, and a marketing database library might include databases that are useful to the marketing staff.
    - Database catalogs
      A database catalog provides a list of all databases on a server. You use the server Catalog task to create a database catalog. The Catalog task bases the catalog file (CATALOG.NSF) on the CATALOG.NTF template and adds the appropriate entries to the catalog's ACL.
    - The Files tab in the Domino® Administrator
      The Files tab in the Domino® Administrator provides an easy way for you to manage files in the Domino data folder.
    - Replicating unread marks
      Unread marks can be replicated for selected databases, most notably mail databases, by using the advanced database properties from the Domino® Administrator or from the database properties box. When you enable the replication of unread marks on mail databases, users can read their mail from a workstation on ServerA, and after replication, can read their mail from a workstation on ServerB, with unread mail clearly delineated from mail that has previously been read.
    - Using indirect files to run database maintenance tasks
      You can use indirect files to run the same maintenance task multiple times, resulting in significant time savings. The fixup, compact, updall, design and convert maintenance tasks support using indirect files. You can also create batch files or scripts that run several maintenance tasks serially against different indirect files to help complete them quickly. If you have multiple CPUs, you can run the same maintenance tasks against multiple indirect files so they run concurrently. It is recommended you only run as many concurrent maintenance tasks as you have CPUs, otherwise they will start competing for CPU resources and can take longer to complete.
    - Updating database indexes and views
      A view index is an internal filing system that Notes® uses to build the list of documents to display in a database view or folder.
    - Synchronizing databases with master templates
      To use a consistent design for multiple databases, database designers can associate databases or elements within databases with a master template.
    - Fixing corrupted databases
      Corrupted databases don't occur frequently when you use transaction logging. When you use transaction logging to log changes to databases, a server automatically uses the transaction log to restore and recover databases after a system failure -- for example, after server failures or power failures. If a disk failure occurs, you use the transaction log along with a certified backup utility to restore and recover the databases.
    - Moving databases
      It may be necessary to move a database from one server to another -- for example, to distribute databases evenly among servers. If there are replicas of the database, the server to which you move the database should have the appropriate Connection documents to replicate the database to other servers that store replicas. If you're moving a database to a server in a cluster, replication between the server and other servers in the cluster that have replicas of the database occurs without Connection documents.
    - Using load convert to convert non-mail databases
      You can use the server's mail convert utility to convert non-mail databases to another type of non-mail database. Non-mail databases are all databases that do not have a $Inbox folder.
    - Redirecting client references to databases
      You can redirect Notes® client references from deleted or moved databases to a database replica that you specify.
    - Running a database analysis
      A database analysis reveals changes in documents, user activity, and other details such as replication data.
- 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

Amazon S3 security guidelines

The following guidelines apply if you are using AWS S3 for DAOS tier 2 storage.

These are very broad guidelines; refer to the AWS S3 documentation for more details and to understand all your options.

Create an S3 bucket for the exclusive use of Domino.
For maximum security, enable bucket encryption.
Create a user identity for Domino to use (aws_access_key_id and aws_secret_access_key).
Configure access control for the bucket to restrict access to the Domino user.
(Recommended) Create a policy to whitelist which IP addresses can connect to the bucket.