Please enter search query.
Search <book_title>...
NetBackup IT Analytics Data Collector Installation and Configuration Guide for Veritas NetBackup
Last Published:
2025-03-04
Product(s):
NetBackup IT Analytics (11.5)
- 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
Host resources troubleshooting
Use the following sequence of steps to determine the source of host resources data collection issues. All commands--except for the SSH commands and the WMI Proxy command--report errors to metadata.log. After executing a command, check the metadata.log file for error messages. If there is an error noted, correct the problem and then re-issue the command. If the command succeeds, proceed to the next command in this sequence: