Excluding logs from onlinebackup | Community
Skip to main content
siddhartha252
June 28, 2019
Solved

Excluding logs from onlinebackup

  • June 28, 2019
  • 5 replies
  • 2891 views

Dear Experts,

Instance version: AEM 6.3.3 with separated datastore (not shared just separated).

I am trying to see a way to eliminate backing up logs during online backup. Is there a way to do it? If there is one could you please point me in the right direction?

Kind regards

Sid

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by siddhartha252

Yes, I understand. Once you modify the path from /logs/custom log to different location, try reloading the http://<HOST>:<PORT>/system/console/slinglog page. Page becomes inaccessible. Page will be accessible only when you revert back the changes.

Thanks

Sid

5 replies

Adobe Employee
July 1, 2019

By Default, AEM will backup everything under the crx-quickstart directory. You can achieve this by moving the log file location outside of crx-quickstart directory. Change the log location by going to slinglog under the "appender" section as shown below:

joerghoh
Adobe Employee
Adobe Employee
July 2, 2019

Other ways to change the location of the logfiles (besides reconfiguring all loggers, as mentioned before):

* make crx-quickstart/logs a symlink and let it point to a directory of your convenience

* set the system property "sling.log.root" to a directory of your convenience (see [1])

Jörg

[1] https://sling.apache.org/documentation/development/logging.html#initial-configuration

siddhartha252
July 3, 2019

But this way, we can no more access log support page. http://localhost:4502/system/console/slinglog

Thanks

Sid

Adobe Employee
July 4, 2019

http://localhost:4502/system/console/slinglog .   This is not a support page. You need to replace the HOST and PORT from your instance. It should be read as below:

http://<HOST>:<PORT>/system/console/slinglog

siddhartha252
siddhartha252AuthorAccepted solution
July 9, 2019

Yes, I understand. Once you modify the path from /logs/custom log to different location, try reloading the http://<HOST>:<PORT>/system/console/slinglog page. Page becomes inaccessible. Page will be accessible only when you revert back the changes.

Thanks

Sid