NetBackup IT Analytics Data Collector Installation Guide for Backup Manager
- Introduction
- Pre-Installation setup for Commvault Simpana
- Open TCP/IP access to the Commvault database
- Set up a read-only user in the CommServe server
- Pre-Installation setup for Cohesity DataProtect
- Pre-Installation setup for EMC Avamar
- Import EMC Avamar server information
- Pre-Installation setup for EMC Data Domain backup
- Pre-Installation setup for EMC NetWorker
- Architecture overview (EMC NetWorker)
- Pre-Installation setup for Dell EMC NetWorker backup & Recovery
- Pre-Installation setup for generic backup
- CSV format specification
- Pre-Installation setup for HP Data Protector
- Architecture overview (HP Data Protector)
- Configure the Data Collector server in Cell Manager (HP Data Protector)
- Pre-Installation setup for IBM Spectrum Protect (TSM)
- Architecture overview (IBM Spectrum Protect -TSM)
- Import IBM Spectrum Protect (TSM) information
- Pre-Installation setup for NAKIVO Backup & Replication
- Pre-Installation setup for Veritas Backup Exec
- Pre-Installation setup for Veritas NetBackup
- Prerequisites to use SSH and WMI (Veritas NetBackup)
- Prerequisites for NetBackup collection over SSH (Kerberos option)
- Configuring file analytics in NetBackup Data Collector policy
- Pre-Installation setup for Oracle Recovery Manager (RMAN)
- Pre-Installation setup for Rubrik Cloud Data Management
- Pre-Installation setup for Veeam Backup & Replication
- Discovery policies for Veritas NetBackup
- About Discovery types
- About SNMP probes
- Installing the Data Collector software
- Validate data collection
- Manually start the Data Collector
- Uninstall the Data Collector
- Appendix A. Load historic events
- Load Veritas NetBackup events
- Appendix B. Firewall configuration: Default ports
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