When provisioning a new AEM 6.0-6.2 environment, one of the first things you should configure is a TarMK compaction process. This process will remove deleted content from the underlying data store and compress the size of the AEM repository on the disk. This is especially important in the lower environments up front as they will be heavily utilized for development and testing activities which can generate a lot of content churn. A recent project I was on had a catastrophic issue in a lower environment because compaction was not enabled and the server simply ran out of disk. Don't let this happen to you! Compacting Servers AEM requires offline compaction for these versions, so this will require downtime. I've found the easiest way to do this is to schedule an automatic job to run off hours to stop AEM, run the compaction and then restart AEM when complete. To do...
I'm based out of Cincinnati, OH
I work as the Adobe Digital Marketing Solution Lead at Perficient