Parameter:
DAOS_Defer_Object_Deletion_DaysShort description: Number of days a DAOS NLO is retained after dereferencing before it may be permanently deleted ("deferred deletion interval").
Profile
Parameter | DAOS_Defer_Object_Deletion_Days |
Category | DAOS |
Component | Server |
Available since | 9.0.1 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | Server document (Transactional Logging → DAOS) |
Possible values | Days as integer (typically 30–90) |
Description
When all references to an NLO have been removed (e.g. because the associated documents have been deleted and purged), the DAOS manager marks the NLO as deletable.
DAOS_Defer_Object_Deletion_Days defines how many days this file remains in the repository before tell daosmgr prune actually removes it. This grace period protects against restore-relevant attachments disappearing too early, for instance when an NSF is restored from backup.In the Server document, the same field is visible as Defer object deletion for n days;
notes.ini overrides this value.Example configuration
DAOS_Defer_Object_Deletion_Days=30
Notes & pitfalls
- Value in days.
- Align with the backup retention period – at least as long as the restore window plus a buffer.
- Too small a value: restore of older NSFs fails because the NLOs are already gone.
- Too large a value: the repository grows unnecessarily.
- Takes effect at the next prune operation (
tell daosmgr prune).
- Complementary to
DAOS_DELETE_TIME,DAOS_Base_Path,DAOS_Enabled.