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 XV. Data Collection Validation and Troubleshooting
  4. Data Collector Troubleshooting
  5. Resolving Data Collectors connections issues - Windows specific

Resolving Data Collectors connections issues - Windows specific

Perform the following steps to resolves the data connections issues:

  1. Verify that the tomcat-agent and apache services are running on the portal

  2. Verify that the key file generated when the data collector was created.

  3. On the portal, access a web browser to the URL of the data receiver. Expected response: Veritas NetBackup IT Analytics Data Receiver.

    Note:

    This step bypasses the network and validates that the data receiver is up and running.

  4. On the data collector, verify the data receiver URL resolves via NSLOOKUP. If not, specify the data receiver IP address and name to the data collector's host file.

  5. Verify the response by a browser session on the data collector to the URL. If not, verify if firewall is blocking access to port 80/443, based on the configuration.

  6. Execute <DC HOME>\mbs\bin\updateconfig. The expected response is, quick return to the command prompt. If not, verify that the <APTARE PORTAL HOME>datarcvrconf\collectorConfig.global.properties on the portal has the correct URL.

  7. Execute checkinstall. If there is initial communication with errors, verify the data collector name, passcode, and URL are correct.

  8. Examine the <Data Collector home>\mbs\conf\collector.properties file and confirm the collector name, collector password, and URL were keyed in correctly at installation.

  9. Verify that the collector service is started and running.

  10. Ensure the understanding that if the portal is running a later upgrade than the GA data collector that upgrade will initiate right after DC connects, and the data collector will go offline for a period during the upgrade.

Feedback

Was this page helpful?
Previous

Resolving Data Collectors connections issues - Linux specific

Next

Portal upgrade performance issues

Feedback

Was this page helpful?