Start/notes.ini Parameters/FTBasePath

FTBasePath

Parameter: FTBasePath
Short description: Relocates the base directory for full-text indexes to an alternative, typically faster volume.

Profile

Parameter
FTBasePath
Category
Performance / Memory
Component
Server
Available since
8.5.3 (older)
Supported versions
9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1
GUI equivalent
notes.ini only (no GUI)
Possible values
Absolute path to a writable directory (e.g. D:\full_text on Windows or /local/ftindex on Linux)

Description

By default, Domino stores the full-text index (*.ft directory) directly next to the corresponding NSF file in the data directory. With large mail, archive, or application databases this creates significant I/O loads and fragmentation on the data drives — indexing and data access compete for the same spindles or SSDs.
With FTBasePath, an alternative base directory for the FT indexes can be specified. Domino then creates the index structures below this path (mirroring the NSF directory hierarchy). Typical use: relocating the FT indexes to a separate, fast volume (SSD/NVMe) or a separate I/O channel, decoupled from the NSF data directory and the transaction log.
The parameter is a classic performance-tuning switch for servers with many or large full-text indexed databases. It does not affect the indexing logic itself, only the storage location.

Example configuration

Default behavior (parameter not set) — FT indexes live next to the NSFs:
# FTBasePath not set
Windows example — FT indexes on a dedicated fast drive:
FTBasePath=D:\full_text
Linux example — FT indexes on a mounted fast volume:
FTBasePath=/local/ftindex
Runtime variant via the server console:
set config FTBasePath=D:\full_text

Notes & pitfalls

  • The specified directory must exist and be writable for the Domino service account — otherwise indexes cannot be created.
  • On Linux, pay attention to correct mountpoint and permission setup (see HCL KB0116222 — typical pitfall with mounted disks).
  • Existing FT indexes do not automatically migrate to the new directory. They must either be rebuilt (Updall -F) or moved manually.
  • The path applies server-wide for all FT indexes — no per-database configuration is possible.
  • Adjust the backup/restore concept: the alternative directory must be included in the backup.
  • Changes take effect after a server restart or after set config FTBasePath=… followed by a restart of the affected tasks (Updall/Update); HCL recommends a server restart for clean initialization.

Sources (HCL Product Documentation)