NetBackup IT Analytics Data Collector Notes and Troubleshooting
- Data Collector Troubleshooting
- Host resources: Check host connectivity using standard SSH
- Host resources: Generating host resource configuration files
- Configuring parameters for SSH
- Firewall Configuration: Default Ports
- CRON Expressions for Policy and Report Schedules
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Install and configure NetBackup IT Analytics Data Collector on MSCS environment
- Firewall Configuration: Default Ports
- Maintenance Scenarios for Message Relay Server Certificate Generation
Resolving Data Collectors connections issues - Windows specific
Perform the following steps to resolves the data connections issues:
Verify that the tomcat-agent and apache services are running on the portal
Verify that the key file generated when the data collector was created.
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.
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.
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.
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.
Execute checkinstall. If there is initial communication with errors, verify the data collector name, passcode, and URL are correct.
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.Verify that the collector service is started and running.
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.