Configuring safe trash purge
When a user deletes a node (document, folder, mail, or record) from OpenKM, it goes to the user's trash. Periodically, users should empty their trash to free repository space.
When the user empties the trash, the documents are permanently lost.
That means if the trash has been accidentally emptied, the nodes can only be restored from a previous backup. This usually requires restoring a full database and repository backup, which is a tedious task.
An administrator can clean all application trash with the Purge trashes utility.
You can configure a place where the documents will go after being purged from the trash.
If you need to recover an accidentally deleted node, it will not be necessary to restore the entire application from backup.
You can configure a directory in the server file system where an export of the trash will be placed, using the "repository.purgatory.home" configuration parameter. Each time before a node is permanently removed from the trash, the application exports it (using the Repository export feature) to the purgatory home folder, creating a subfolder structure "YEAR/MONTH/DAY" which can help the administrator to locate the data to be recovered. To recover the data, use the Repository import feature with the Metadata option checked.
| Field / Property | Type | Description |
|---|---|---|
|
repository.purgatory.home |
String |
Set the safe trash purge destination folder. /mnt/backup/trash |
It is good practice to back up the purgatory home folder, at least for a prudent period (1-2 months depending on your company policy).
