Start/notes.ini Parameters/DAOSDeferredDeleteInterval

DAOSDeferredDeleteInterval

DAOSDeferredDeleteInterval defines how many days an NLO file remains in the DAOS repository after the loss of the last reference, before DAOSMgr Prune physically deletes it. The parameter is the notes.ini equivalent of the field „Deferred deletion interval“ in the Server document (tab „DAOS“).

Profile

Parameter
DAOSDeferredDeleteInterval
Component
Server
Category
DAOS
Available since
Domino 8.5; currently documented in HCL Domino 9.0.x–14.5.1
Value format
Integer in days
Typical value
30 (HCL practice docs, forum examples)
GUI equivalent
Server document → „DAOS“ → „Deferred deletion interval“

Description

DAOS deduplicates attachments at the NLO file level. As soon as the last reference is deleted from a database, the reference counter of the corresponding NLO in the catalog (daoscat.nsf) drops to 0. The NLO is not deleted physically right away, but only after DAOSDeferredDeleteInterval has elapsed. This is the central protection against data loss when restoring from a backup that still knew this reference.

Interplay with the backup strategy

The recommendation is:
  • DAOSDeferredDeleteInterval ≥ longest backup retention period + safety margin.
  • For a daily full-backup strategy with 30 days retention: 45 to 60 days.
  • For monthly rotating backups with 90 days retention: 90 to 120 days.
KB0079120 explicitly notes: „Review your backup schedule and accordingly set DAOS deferred deletion interval which will delete NLO files with 0 references.“

Mechanism

The actual deletion is performed by the DAOSMgr Prune run. It checks all NLOs with reference counter 0, compares the reference-loss date with the current date, and deletes NLOs whose reference-loss date is older than DAOSDeferredDeleteInterval days.

Examples

Server with moderate backup retention (30 days):
DAOSEnable=1
DAOSBasePath=D:\DAOS
DAOSMinObjSize=4096
DAOSDeferredDeleteInterval=30
Server with longer compliance retention (90 days):
DAOSEnable=1
DAOSBasePath=D:\DAOS
DAOSMinObjSize=4096
DAOSDeferredDeleteInterval=90

Notes

  • Too small (<14 days) shrinks the DAOS repository faster, but endangers restore scenarios.
  • Too large unnecessarily inflates the DAOS storage because NLOs with 0 references remain for a long time.
  • DAOS Prune Job – after changes, verify that the prune job (default schedule at 02:00) actually runs. After a server restart past midnight, the prune may be skipped (see HCL KB0125038).
  • Companion parameters – DAOSEnable, DAOSBasePath, DAOSMinObjSize, DAOS_ENCRYPT_NLO, DAOS_LOAD, DAOSCatalogState.

Sources (HCL Product Documentation)