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 IX. Data Protection
  4. Configuration for generic backup
  5. Manually load the CSV file (generic backup)

Manually load the CSV file (generic backup)

Use the following procedure to manually load the Generic Backup CSV file into the Portal database.

Pre-requisites:

  • These scripts must be run on the Data Collector server.

  • The checkinstall script must be run first to register the event collector ID.

  1. List the Data Collectors to get the Event Collector ID and the Host ID, which will be used in step 2.

    Windows:

    C:\opt\APTARE\mbs\bin\listcollectors.bat

    Linux:

    /opt/aptare/mbs/bin/listcollectors.sh

    In the output, look for the Event Collectors section associated with the Software Home - the location of the CSV file (the path that was specified when the Data Collector Policy was created). Find the Event Collector ID and Host ID.

    ==== Event Collectors ===
              Event Collector Id: EVENT_1029161_9
              Active: true
              Active: true
              Software Home: C:\gkgenericBackup.csv
              Server Address: 102961
              Domain: gkdomain
              Group Id: 102961
              Server Id: 102961
              Schedule: */10 * * * *
  2. Use the following commands to load the data from the CSV file into the Portal database.

    Windows:

    C:\opt\APTARE\mbs\bin\loadGenericBackupData.bat <EventCollectorID> <HostID>

    Linux:

    /opt/aptare/mbs/bin/loadGenericBackupData.sh <EventCollectorID> <HostID>

Note:

If you run the command with no parameters, it will display the syntax.

The load script will check if the backup server and client already exist; if not, they will be added to the database. The script then checks for a backup job with the exact same backup server, client, start date and finish date. If no matches are found, the job will be added; otherwise, it will be ignored. This prevents duplicate entries and allows the import of the script to be repeated, if it has not been updated. Once the load is complete, these clients and jobs will be visible via the IT Analytics Portal and the data will be available for reporting.

Feedback

Was this page helpful?
Previous

Adding/Editing a generic backup server within the Data Collector policy

Next

CSV format specification

Feedback

Was this page helpful?