Specifications

Lotus Redbooks Wiki – IBM Lotus Notes and Domino V8.5 Deployment Guide
161
This tool is compatible with Domino 6.x and higher, meaning that you can run this tool and get a detailed
listing of the above information for every Domino 6.x and higher server in your environment.
To download the DAOS Estimator tool, please follow the instructions in IBM Technote 4021920 “Download
the Domino Attachment and Object Service Estimator Tool version 1.4”
Now that we know how to get DAOS estimates, let's continue with our planning!
To plan for DAOS disk space needs, we need to understand the following concepts:
• DAOS only supports a single base path and it manages subdirectories below this base path. The
base path can be anywhere, but it is recommended to be in a location other than under the Domino
data directory. The base path should have enough capacity to hold all existing attachments and
some projected growth. Use the information provided by the DAOS Estimator. It is recommended to
use flexible, configurable and expandable disk storage to avoid running out of disk space for the
base path.
• Since the typical I/O rates to DAOS are very low, it is a good candidate for low-cost storage.
Because typical users are not constantly opening or detaching attachments all the time, there's no
need for high-speed disks. One exceptions would be if you are using Full-text indexing on
attachments, or if you are running third-party applications that may run agents or scan attachments
like anti-virus softwares.
DAOS Configuration
Now that we meet the requirements and have our plan in place, we can configure the DAOS feature on a
Domino 8.5 server.
The settings we need are the following:
• Minimum size of object before Domino will store in DAOS - This is the minimum size (bytes) of
attachments that will be stored in DAOS. Anything below this size will remain as a fully independent
attachment in the Notes database.
• DAOS base path - This is the base path where the DAOS store will be located.
• Defer object deletion for - Once the last reference is deleted, this is the number of days that the
NLO file will remain in the DAOS store until it is purged.
For the minimum size of object, use the DAOS Estimator to choose your best cost/benefit model. Based on
feedback from early adopters, 64KB (64000 bytes) is a good starting minimum, but keep in mind that this
value can be changed anytime later.
For larger deployments, we recommend to set a higher value first, and later decrease ( and compact again)
For defer object deletion, this interval should be tuned to your restore frequency. For example, if your
average database restore frequency is once a month or less, use 30 days (default). If it's more than once a
month, evaluate your own cost/benefit ratio of keeping NLOs versus restoring them on an as-needed basis.
To configure and activate DAOS on a server:
• Modify the server's NOTES.INI file (or change the servers configuration document / notes.ini
section) by adding the following setting:
CREATE_R85_DATABASES=1
• Edit the Server document, go under the DAOS tab and set the following settings: