Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Help
  3. Section XVI. System Administration
  4. Working with Log Files
  5. Portal and data collector log files - reduce logging
  6. Portal Log Files

Portal Log Files

For Portal Tomcat, edit this file:

Linux: /opt/aptare/portalconf/systemlogger.xml

Windows: C:\opt\aptare\portalconf\systemlogger.xml

<param name="MaxFileSize" value="10MB" />
<param name="MaxBackupIndex" value="10" />

For the Data Receiver Tomcat, edit this file:

Linux: /opt/aptare/datarcvrconf/systemlogger.xml

Windows: C:\opt\aptare\datarcvrconf\systemlogger.xml

<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>/opt/tomcat/logs/datarcvr_%i.log</fileNamePattern>
	<minIndex>1</minIndex>
	<maxIndex>10</maxIndex>
</rollingPolicy>
<triggeringPolicy class="com.aptare.dc.util.LogbackSizeBasedTriggeringPolicy">
            <maxFileSize>20MB</maxFileSize>
</triggeringPolicy>
<!--The Threshold param can either be debug/info/warn/error/fatal.-->
<param name="Threshold" value="debug"/>

Feedback

Was this page helpful?
Previous

Portal and data collector log files - reduce logging

Next

Data Collector Log Files

Feedback

Was this page helpful?