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 - 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.