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. Data collector log file organization

Data collector log file organization

Data Collector logs are organized into two directory hierarchies:

Checkinstall and Validation Probes
  • /opt/aptare/mbs/logs/validation/

  • C:\Program Files\Aptare\mbs\logs\validation\

Scheduled Probes (running as a service)
  • /opt/aptare/mbs/logs/scheduled/

  • C:\Program Files\Aptare\mbs\logs\scheduled\

Within this directory structure, there is a framework sub-directory. The framework sub-directory is used in the beginning of the collection process, before the Data Collector type has been identified. Once IT Analytics knows the type of collector (for example, EMC Isilon), logging is recorded in the main scheduled directory using the naming convention described in the following section.

See Data collector log file naming conventions.

Feedback

Was this page helpful?
Previous

Data collector log files

Next

Data collector log file naming conventions

Feedback

Was this page helpful?