AEM version 6.4 introduces new enhancements that provide greater flexibility and efficiency for AEM maintenance tasks.
In previous versions of AEM and AEM 6.4, you can schedule the Version Purge maintenance task to delete old versions automatically. As a result, this minimizes the need to manually execute the version Purge tools.
You can schedule and configure the Version Purge task by accessing Tools > Operations > Maintenance > Weekly Maintenance Window and following these steps:
The default values are the recommended configuration values for the Version Purge task. Adjusting these values is necessary in the case of version retention requirements.
AEM also has a Version Purge tool that can run ad hoc version purges. The configurations for the Version Purge task and the Version Purge tool are unrelated.
In AEM 6.4, you can now stop the Version Purge maintenance task as follows:
- Automatically - If the scheduled maintenance window closes before the task can complete, the task stops automatically. It will resume when the next maintenance window opens.
- Manually - To manually stop the task, on the Version Purge maintenance card, click the Stop icon. On the next execution, the task will gracefully resume.
In AEM 6.3, if the scheduled maintenance window closes before the Audit Log Purge Task can complete, the task stops automatically. It will resume when the next maintenance window opens.
With AEM 6.4, you can manually stop a running Audit Log Purge Task by going to: Tools > Operations > Maintenance and clicking the Stop icon. On the next execution the task will gracefully resume.
By default, the status ZIP contains instance configurations, a list of bundles, OSGI, Sling metrics and statistics and this can result in a large file. With AEM 6.4, you can now reduce the impact of large status files by using the Download Status ZIP window. The window can be accessed from: AEM > Tools > Operations > Diagnosis > Download Status ZIP.
From this window you can select what to export (log files and or thread dumps) and the number of days of logs included in the download relative to the current date.
By using the Lucene Binaries Cleanup task, you can purge lucene binaries and reduce the running data store size requirement significantly. This is because the lucene's binary churn would be re-claimed daily instead of the earlier dependency on a successful DSGC run.
Though the maintenance task was developed to reduce Lucene related revision garbage, there is other general efficiency gains to AEM when running this Maintenance Task:
- The weekly execution of the DSGC task will complete more quickly
- It may also have slight overall AEM performance improvements
You can access the Lucene Binaries Cleanup task from: AEM > Tools > Operations > Maintenance > Daily Maintenance Window > Lucene Binaries Cleanup.
The settings for the "Lucene Binaries Cleanup" task do not require configuration.
Maintenance tasks are now logged out of the box in a new more information rich format at the INFO level. This new format allows for better visiblity into the state of the maintenance tasks.
While AEM does not provide a log monitoring and notification framework, 3rd party tools (such as Splunk, and others) can be used to monitor and react more accurately to maintenance task activity based on the following log statements.
Log level: INFO DATE+TIME [MaintanceLogger] Name=<MT_NAME>, Status=<MT_STATUS>, Time=<MT_TIME>, Error=<MT_ERROR>, Details=<MT_DETAILS>