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
Reset Discovery data
When Discovery processes execute, they collect information on discovered devices and store this information in the Reporting Database. When you reset the Discovery data, you purge all this information from the Reporting Database and reset the Client Protection Summary report. The data re-populates the next time the Discovery processes run.
Consider resetting your Discovery data if any of the following conditions are true:
If your initial Discovery policy was too broad, and included devices that were in a DHCP range. This policy configuration could result in potentially large numbers of IP addresses showing up in the Client Protection Summary report thereby diminishing the effectiveness of the report.
If previously discovered clients no longer exist in your environment, but are still showing in the Client Protection Summary report.
If a file system on a previously discovered client had subsequently been removed, and is still showing up in the Client Protection Summary report.
By resetting the Discovery data, you can start over and rebuild a fresh list of discovered devices and file systems. A reset only impacts the Client Protection Summary report. A reset does not affect any of the other collected backup data that is used in all other reports.