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
Verify the Data Collector configuration
The Data Collector configuration file contains key information captured during the installation process. If the information was entered incorrectly, this may be the cause of the failure.
To check the configuration file
- Edit the configuration file.
Windows:
edit "C:\Program Files\Aptare\mbs\conf\wrapper.conf"
Linux:
edit "/opt/aptare/mbs/bin/startup.sh" and "/opt/aptare/mbs/bin/updateconfig.sh"
- Verify the values of the following parameters and update them, if necessary.
wrapper.app.parameter.2
Should match the Collector Name you specified when adding a collector policy.
wrapper.app.parameter.3
Should match the Passcode you specified when adding a collector policy.
wrapper.app.parameter.4
For IN-HOUSE installations:
http://itanalyticsagent.yourdomain.com
where: yourdomain.com has the appropriate value.
For third-party HOSTED installations:
http://itanalyticsagent.yourdomain.com
where: domain.com has the appropriate value.
- If you changed any of the configuration file parameters, you'll need to:
Restart the Data Collector service.
Re-run the installation validation utility.