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.

About this task

The attachment repository, by default, is created relative to the logical directory structure that is controlled by the server. You can create the directory anywhere on the server or a connected file drive by specifying a full path.

For information on use an S3-compatible storage service to store older attachment objects that haven't been accessed within a specified number of days, see DAOS tier 2 storage.

To set up and enable the Domino® Attachment and Object Service


  1. Make sure that transaction logging is enabled on the Domino® server.
  2. From the Domino® Administrator, click the Configuration tab and then expand the Server section.
  3. Select the Server document to be edited and then click Edit Server.
  4. Click the DAOS tab.
  5. Enable or disable the use of attachment consolidation by completing first field in the following table. If enabling, complete all the remaining fields.
    Table 1. DAOS tab
    Field name Enter
    Store file attachments in DAOS

    Choose one:

    • Enabled. The server consolidates attachments saved in any document in any database included in consolidation. A database is included when the database property Use Domino Attachment and Object Service is selected.
    • Disabled. The server stops using attachment consolidation and any new attachments in participating databases are stored in documents.
    Minimum size of object before Domino will store in DAOS

    The minimum total size, in bytes, of any attachment to be consolidated. Enter a number of bytes.

    Consolidating attachments of very small size is not worth the processing effort because it does not yield much disk space saving.

    DAOS base path

    The full or relative path to the attachment repository. If you enter a relative path, such as DAOS, the default is to a relative path within the Domino® data directory.

    Important: Despite the default, it is highly recommended that you specify a full path outside of the Domino® data directory.

    Example on Microsoft Windows:


    Example on Linux or IBM® i:


    If the directory you specify does not exist, Domino® creates it for you.

    Note: Make sure that the Domino® administrative user has file-access permissions in the directory appropriate to the server's operating system.
    Defer object deletion for n days

    Use this setting to keep objects in DAOS from being deleted for an additional number of days after the last reference to them from any document is deleted.

    Enter a number from 0 to 9999.

    This setting is useful if an unreferenced DAOS object is mistakenly deleted and needs to be restored.

    You can delete all unreferenced objects explicitly at any time by using the Tell DAOSMgr Prune command.

    DAOS object encryption
    Select an option for object encryption:
    • None (not recommended)
    • Private to this server
    • Shared
    DAOS encryption strength Select an object encryption strength:
    • Domino classic (For Domino 11.0.0 and earlier releases.)
    • AES-128
    • AES-256
    DAOS Tier 2 Enables use of an S3-compatible storage service to store older attachment objects that haven't been accessed in a specified number of days.
  6. Click Save & Close:

What to do next

If the server runs virus detection software, use the same virus scan policy for the DAOS directory as is set for .NSF files in the server data directory.

To put the new configuration into effect, restart the server.