Audit Entry Archiver (Cron Job)
In Pure, any change (any configuration change, create, update or delete any content) is recorded in a full audit log. This data is stored in XML format, so it can take up a large amount of space.
This job archives old audit entries to second level storage, so they do not slow down Pure.
Recommended frequency
Daily (at night)
Required on production server
Recommended for performance reasons
How it works
The job checks if there are more than 100.000 rows in the audit log database tables, and if there are, the audit data is moved to ZIP files in the file system.
The files will be stored in "Server data dir"/admin/audit, and you can see the "Server data dir" setting in Administrator > System settings > Core configuration, to find the exact location of the files.
If the ZIP files are stored on a slow disc or a network mounted drive, then performance in Pure can suffer, especially when you look at the comments and history tab on content.
Job Log
This job only creates a job log entry when there are enough audit entries to move to the disk. Do not worry if it does not appear in the job log entries, this just indicates that there was not enough audit activity to justify archiving this content.
Job configuration
This job has no configuration options.
Note
If the files are not copied with a database dump to a test server, then audit will be missing information about when the content was created, and there can be gaps in the history and comments on content in Pure.