NetBackup IT Analytics Data Collector Installation and Configuration Guide for Veritas NetBackup
- Introduction
- Configure a NetBackup IT Analytics Distributed Data Collector on a NetBackup Primary Server
- Configure Data Collector on non-clustered NetBackup 10.4 and later primary server
- Configure Data Collector on non-clustered NetBackup 10.1.1, 10.2, 10.2.01, 10.3 or 10.3.0.1 primary server
- Configure a Veritas NetBackup Data Collector Policy
- Configuring file analytics in NetBackup Data Collector policy
- Installing the Data Collector software
- Configure SSL
- Centralized Data Collector for NetBackup - Prerequisites, Installation, and Configuration
- Step-1: Choose operating system and complete prerequisites
- Step-5: SSH/WMI
- Upgrading Data Collector Locally
- 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
- Data Collector Policy Migration
- Pre-Installation setup for Veritas NetBackup appliance
- Pre-installation setup for Veritas Flex Appliance
- Data Collector Troubleshooting
- Host resources: Check host connectivity using standard SSH
- Host resources: Generating host resource configuration files
- Configuring parameters for SSH
- Appendix A. Configure Appliances
- Appendix B. Load historic events
- Load Veritas NetBackup events
- Appendix C. Firewall configuration: Default ports
- Appendix D. CRON Expressions for Policy and Report Schedules
- Appendix E. Maintenance Scenarios for Message Relay Server Certificate Generation
Resolving Data Collectors connections issues - Linux 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 is generated when the data collector was created.
On the portal, perform wget to the URL of the data receiver. The expected response is:
Index.html
file.Note:
This step bypasses the network and validates that the data receiver is up and running.
On the data collector, verify that the data receiver URL resolves via NSLOOKUP. If not then specify the data receiver IP address and name to the data collector's host file.
Verify using wget from the data collector that a response back, index.html page, is received. If not then ,verify if the firewall is blocking the access to port 80/443, depending upon configurations.
Execute the command /usr/openv/analyticscollector/mbs/bin/updateconfig. The expected response is: quick return to the command prompt. If not then: verify that the /opt/aptare/datarcvrconf/collectorConfig.global.properties on the portal has the correct URL.
Execute the checkinstall. If there is initial communication but errors, confirm the data collector name, passcode, and URL are correct.
Examine the
<Data Collector home>/mbs/conf/collector.properties
file and verify that the collector name, collector password, and URL were specified appropriately during the installation.Verify that the collector service is started, and Watchdog is running.