Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup IT Analytics Data Collector Notes and Troubleshooting
- Data Collector Troubleshooting
- Verify the Data Collector configuration
- Verify Connectivity
- Configuring web proxy updates
- Collecting missed events for Veritas Backup Exec
- Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
- Useful Data Collection scripts for capacity
- Host resources troubleshooting
- Host resources: Check the status of the WMI proxy server
- Host resources: Post-Installation verification
- Host resources: Check host connectivity using standard SSH
- Host resources: Check host connectivity
- Host resources: Check host connectivity using Host Resource Configuration file
- Host resources: Generating host resource configuration files
- Host resources: Check the execution of a command on a remote server
- Host resources Data Collection
- Host resources: Collection in stand-alone mode
- Configuring parameters for SSH
- Identifying Windows file system access errors (File Analytics)
- Collect from remote shares (File Analytics)
- Adding a certificate to the Java keystore
- Firewall Configuration: Default Ports
- CRON Expressions and Probe Schedules
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL 7)
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Firewall Configuration: Default Ports
- Maintenance Scenarios for Message Relay Server Certificate Generation
Authenticate new database with existing SSL certificates
When you install a new database, the SSL certificate entry is lost on the database host. Since the data collector runs on a separate system, it is unaware about the DB import and does not update certificate to the DB.
Perform the following steps to regenerate the aptare_message_relay_certificate.pem file and authenticate the new database:
- Login to the data collector system and navigate to its installation path:
/Aptare/mbs/conf. - Login to the data collector system and stop the Aptare Agent service on the data collector system.
On a Windows system, you can stop the service from the Services Console, whereas you can use ./aptareagent stop command on Unix.
- Delete
aptare_message_relay_certificate.pem - Start the Aptare Agent service on the data collector system.
Note:
The aptare_message_relay_certificate.pem file need not be copied on the data sender as the same certificate file is just regenerated.