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 naming conventions
  6. Sample Vendor.Product Naming Convention

Sample Vendor.Product Naming Convention

Examples of vendor.product folder names within this directory structure include:

cisco.cisco
commvault.simpana
dell.compellent
emc.avamar
emc.clariion
generic.host (Valid for a host resources discovery policy)
hp.3par
veritas.bue

Additionally, each Java Virtual Machine (JVM) creates its own logging file(s) when starting up. This is necessary because multiple processes logging to the same file could overwrite each other's log messages. These log files can be found in the framework sub-directory.

See Data collector log file organization.

See Checkinstall Log.

Feedback

Was this page helpful?
Previous

Data collector log file naming conventions

Next

Log File Names Based on Data Collector Generation

Feedback

Was this page helpful?