AEM Maintenance activities cadence for cold stanby and Publisher clusters
Hello there,
I am optimising my maintenance activities and got some questions around as I am not able to get the information from the adobe docs
My AEM Setup :
1. File Datastore TarMK system - on-prem in AWS
2. Have cold standby on author
3. Have AWS based backup mechanism running at 5am in the morning everyday.
As per my understanding from the documentation at [1], we need to configure maintenance jobs as below
Daily (2AM-5AM):
a. Revision cleanup with full.gc.day as Sun
b. Lucene binaries cleanup
Weekly (1AM-2AM) :
a. Datastore GC
b. Workflow purge
Monthly :
a. Audit log purging
b. Version purging
The doubts I have are
1. Is there a cadence we need to work between Daily and Monthly to get best result
2. Do we need to enable it in cold standby or will it auto synchronise. (Essentially disable the jobs in cold stand by)
3. Should we configure different timings for different publishers OR is it fine to run it on all the publishers at the same time.
4. Is there a recommended size for the disk size based on base size and daily content footprint size to optimise the disk size to stay below the threshold level. There is some hint in [2], but is it just for revision cleanup alone.