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
Corrections in duplication of clients
This section applies to those clients that are being reported by Veritas NetBackup's VMware policy.
A VMware backup policy in NetBackup can be configured in several ways with Virtual Machine (VM) Primary identifier set to one of
Hostname
Display Name
DNS Name
Instance UUID
BIOS UUID
Due to which the name of the same VM reported by NetBackup may differ depending on how the policy is created, which may result in the same VM getting persisted in Aptare database with different name resulting in duplicates.
To fix the historic data having duplicate clients, execute the following command-line scripts on Data Collector.
Warning:
The command should be executed only after upgrading to version 10.6 P14 or 11.0.02.
Windows:
C:\Program Files\Aptare\mbs\bin\veritas\correct_vm_dup_clients.bat <metaDataCollectorId> <primaryServerName>
Linux:
<APTARE HOME>/mbs/bin/symantec/correct_vm_dup_clients.sh <metaDataCollectorId> <primaryServerName>
Where: The MetadataCollectorID can be found by executing the following utility:
For Windows: C:\opt\Aptare\mbs\bin\listcollectors.bat
For Linux: /opt/aptare/mbs/bin/listcollectors.sh