Storage layout requirements

Download PDF of this page

A typical IBM Domino environment has at least three Domino volumes, one each for Domino data, Domino transaction logs, and the plug-in changeinfo directory. Many sites also have volumes for Domino DAOS and for view rebuilds.

The IBM Domino plug-in uses the changeinfo directory for changes recorded during backup operations and for copies of transaction logs used in up-to-the-minute restore operations. It is a best practice to store the changeinfo directory on a separate volume, to avoid inadvertently overwriting the information and to make it easier to back up.

You may also find it useful to have separate volumes for Domino DAOS (if it is enabled) and for view rebuilds. When Domino rebuilds a view (for example, when a user opens a view whose index has been deleted or when updall --R is run), it may generate temporary files to sort the data for rapid view rebuilding.

By default, these temporary files are located in the system’s temporary folder or in the Domino data folder. IBM recommends changing the location of the temporary files to a different drive to distribute disk I/O and to ensure adequate space to rebuild views. To change the temporary folder used for view rebuilds, add the View_Rebuild_Dir setting to the notes.ini file.

The following table shows the preferred volume layout:

Volume Contents Notes

Volume 1

Domino data

FC, SAS, or SSD drives preferred.

Volume 2

Domino transaction logs

FC, SAS, or SSD drives preferred.

Volume 3


Stores changes recorded during backup operations and copies of transaction logs for use in up-to-the-minute restore operations.

Volume 4

View rebuild

Optional. Stores temp files created during index updates. Can use RAM disk. Add View_Rebuild_Dir setting to notes.ini file.

Volume 5

DAOS repository

Optional. Contains .dlo files from DAOS. Low I/O requirements make this a good candidate for SATA drives.

In virtual environments, guest-mounted disks are preferred.