NetBackup IT Analytics Data Collector Installation Guide for Backup Manager
- Introduction
- Pre-Installation setup for Commvault Simpana
- Introduction
- Architecture overview (Commvault Simpana)
- Prerequisites for adding Data Collectors (Commvault Simpana)
- Upgrade troubleshooting: Microsoft SQL Server and Java 11
- Installation overview (Commvault Simpana)
- Open TCP/IP access to the Commvault database
- Set up a read-only user in the CommServe server
- Load historical data prior to initial data collection
- Add Commvault Simpana servers
- Add a Commvault Simpana Data Collector policy
- Pre-Installation setup for Cohesity DataProtect
- Pre-Installation setup for EMC Avamar
- Introduction
- Architecture overview (EMC Avamar)
- Prerequisites for adding Data Collectors (EMC Avamar)
- Installation overview (EMC Avamar)
- Add EMC Avamar servers
- Adding an EMC Avamar Data Collector policy
- Testing the collection
- Add/Configure an Avamar Server within the Data Collector policy window
- Import EMC Avamar server information
- Export EMC Avamar server information
- Pre-Installation setup for EMC Data Domain backup
- Architecture overview (EMC Data Domain Backup)
- Prerequisites for adding Data Collectors (EMC Data Domain Backup)
- Installation overview (EMC data domain Backup)
- Add EMC data domain servers
- Add an EMC data domain backup Data Collector policy
- Adding/Configuring an EMC data domain server within the Data Collector policy window
- Configure a data domain server for file-level compression collection
- Pre-Installation setup for EMC NetWorker
- Introduction
- Architecture overview (EMC NetWorker)
- Prerequisites for adding Data Collectors (EMC NetWorker)
- Installation overview (EMC NetWorker)
- Add EMC NetWorker servers
- Adding an EMC NetWorker Data Collector policy
- Adding/Editing a EMC NetWorker server within the Data Collector policy
- Configure a notification action in EMC NetWorker
- Pre-Installation setup for Dell EMC NetWorker backup & Recovery
- Pre-Installation setup for generic backup
- Introduction
- Generic backup data collection
- Prerequisites for adding Data Collectors (Generic Backup)
- Installation overview (generic backup)
- Add generic backup servers
- Add a generic backup Data Collector policy
- Adding/Editing a generic backup server within the Data Collector policy
- Manually load the CSV file (generic backup)
- CSV format specification
- Pre-Installation setup for HP Data Protector
- Introduction
- Architecture overview (HP Data Protector)
- Prerequisites for adding Data Collectors (HP Data Protector)
- Installation overview (HP Data Protector)
- Identify HP Data Protector collection requirements
- Cell Manager commands for data collection
- Preparing for centralized data collection on a remote Cell Manager
- Configure the Data Collector server in Cell Manager (HP Data Protector)
- Configure an HP Data Protector admin user
- Validate HP Data Protector setup
- Add HP Cell Manager servers to NetBackup IT Analytics
- Add an HP Data Protector Data Collector policy
- Add/Edit a HP Data Protector server within the Data Collector policy
- Tune the configuration
- Pre-Installation setup for IBM Spectrum Protect (TSM)
- Introduction
- Architecture overview (IBM Spectrum Protect -TSM)
- Prerequisites for adding data collectors (IBM Spectrum Protect - TSM)
- Installation overview (IBM Spectrum Protect - TSM)
- Add IBM Spectrum Protect (TSM) servers
- Adding an IBM Spectrum Protect (TSM) Data Collector policy
- Add/Configure an IBM Spectrum Protect (TSM) server within the Data Collector policy
- Import IBM Spectrum Protect (TSM) information
- Export IBM Spectrum Protect (TSM) server information
- Pre-Installation setup for NAKIVO Backup & Replication
- Pre-Installation setup for Veritas Backup Exec
- Introduction
- Architecture overview (Veritas Backup Exec)
- Backup Exec terminology
- Prerequisites for adding data collectors (Veritas Backup Exec)
- Upgrade troubleshooting: Microsoft SQL Server and Java 10
- Installation overview (Veritas Backup Exec)
- Enable TCP/IP for the SQL server
- Configure a Windows user
- Add Veritas Backup Exec servers
- Importing Backup Exec Server information
- Add a Veritas Backup Exec Data Collector policy
- Pre-Installation setup for Veritas NetBackup
- Introduction
- General prerequisites for adding Data Collectors (Veritas NetBackup)
- Prerequisites to use SSH and WMI (Veritas NetBackup)
- Configure NetBackup Access Control (NBAC) for NetBackup Data Collection
- Configure NetBackup sudo access for NetBackup data collection
- Configure NetBackup Appliances for Data Collection
- Configure NetBackup Flex Appliances for Data Collection
- Configure custom RBAC for FETB collection
- Veritas NetBackup SSH: Changing the Linux Temporary Directory for Collection
- Prerequisites for NetBackup collection over SSH (Kerberos option)
- Prerequisites for collection from Veritas NetBackup deployed on Kubernetes clusters
- Distributed NetBackup data collection
- Before you install the Data Collector (Veritas NetBackup)
- Add a Veritas NetBackup Data Collector policy
- Add/Edit NetBackup Primary Servers within the Data Collector policy
- 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
- Introduction
- Prerequisites for adding data collectors (Veeam Backup & Replication)
- Verifying Data Collector servers can connect to Veeam servers
- Known issues and limitations (Veeam Backup & Replication)
- Installation overview (Veeam Backup & Replication)
- Add a Veeam Backup & Replication Data Collector policy
- Discovery policies for Veritas NetBackup
- Task overview: Configure and monitor discovery policies
- Discovery policies overview
- About Discovery types
- Activate a Discovery license
- Exclude devices from Discovery policies
- Activate Discovery probes in the NetBackup Data Collector policy
- Monitor Discovery processes
- View client protection status
- Reset Discovery data
- Why enable SNMP?
- About SNMP probes
- Example--Installing Net-SNMP
- Troubleshoot Net-SNMP installations
- Installing the Data Collector software
- Introduction
- Installing the WMI Proxy service (Windows host resources only)
- Testing WMI connectivity
- Considerations to install Data Collector on non-English systems
- Install Data Collector Software on Windows
- Install Data Collector software on Linux
- Deploy Data Collector in native Kubernetes environment
- Configure Data Collector manually for Veritas NetBackup
- Install Data Collector binaries on Windows (without configuration)
- Install Data Collector binaries on Linux host (without configuration)
- Validate data collection
- Manually start the Data Collector
- Uninstall the Data Collector
- Appendix A. Load historic events
- Introduction
- Load Commvault Simpana events
- Load EMC Avamar events
- Load EMC NetWorker events
- Load HP Data Protector events
- Load IBM Spectrum Protect (TSM) events
- Load Oracle Recovery Manager (RMAN) events
- Load Veeam Backup & Replication events
- Load Veritas NetBackup events
- Load Veritas Backup Exec events
- Corrections in duplication of clients
- Cohesity
- Dell EMC NetWorker Backup & Recovery
- Appendix B. Firewall configuration: Default ports
Configure a data domain server for file-level compression collection
In addition to the Names and Backup Type that were entered when an EMC Data Domain server was created, credentials are required to access and collect from the server. Also, if File-Level Compression collection from NetBackup systems is desired, MTree data must be listed.
File-Level Compression information can be instrumental in determining efficient storage strategies and identifying storage that can be reclaimed, thereby reducing archive storage expenses. This data can be used to identify clients with inefficient de-duplication ratios, highlighting where de-deduplication is not an effective approach for certain backed-up files. For example, some hosts may be running database applications that are constantly producing unique bits of data. These hosts can consume much of the expensive Data Domain storage. Data Domain collection now can identify the largest offenders, which can then be moved to less expensive storage to avoid paying premium rates for de-duplication. Use the following report templates to take advantage of this collected data: Data Domain NetBackup File Compression Summary and the Data Domain NetBackup File Compression Detail.
Enter the following details and click .
Field
Description
Data Domain Server Name*
In order for Data Domain Servers to be listed in the policy window, they must be configured with a of .
SSH User ID*
The command-line interface (CLI) via SSH is used to gather Data Domain system data. This requires the SSH Service to be enabled and a Data Domain user that has a management role of 'user'. This User ID must be the same for all addresses listed in the System Addresses entry field for the Data Domain systems.
Password
The password associated with the User ID.
Repeat Password
The password associated with the User ID.
File-Level Compression - MTrees Attached to Backup Systems
This selection is relevant only when the File-Level Compression probe is selected in the EMC Data Domain Backup Policy.
Select the option to either include or exclude collection from the MTrees entered in the list. If the exclude option is selected with an empty MTree list, data from all MTrees will be collected. If the include option is selected with an empty MTree list, no file-level compression data will be collected.
Note:
Warning: Choosing to exclude file-level collection with an empty MTree list may cause collection to take several hours to complete.
Exclude from collection the MTrees entered below
OR
Collect only from MTrees entered below
Enter one or more MTree names to be included in collection or to be excluded from collection, depending on the selected option. When compression information is collected from the MTree, an attempt is made to connect the file with a backup job that has previously been collected. A 'hint' must be specified to allow this to occur. Currently Oracle RMAN, Veritas NetBackup, and EMC Avamar are supported. For this probe to collect data, the RMAN / NetBackup / Avamar jobs must have been previously collected and all RMAN or NetBackup collection probes must have been run.
Note:
The Exclude from collection the MTrees entered below field will not collect for Avamar.
To specify an MTree to which RMAN is sending backup files to, enter:
RMAN:[MTree Name].
For NetBackup, enter:
NBU:[MTree Name].
For Avamar, enter:
AVM:[MTree Name].
Example of a comma-separated MTree list: RMAN:/data/col1/rman_su1, NBU:/data/col1/nbu_ddm1
AVM:/data/col1/avamar-1629802442
If you do not specify a hint, it is assumed that the Data Domain MTree contains files created by Veritas NetBackup.
To run File-Level compression across all Mtrees on a Data Domain system, with a 'hint' to specify that the database attempt to link files with Backup jobs, enter:
RMAN:*
or
NBU:*
or
AVM:*
depending on the Backup system using the MTree. Mixed use of wildcards is not supported.
Aggregated global and local compression rates for all NetBackup backup images are collected for all MTrees that are connected to the Active Data Domain servers via DDBOOST and where the NetBackup Data Collector is active and has successfully completed an initial data collection.
Warning:
Choosing to exclude collection with an empty MTree list may cause collection to take several hours to complete.
Click to save the policy.
On the Data Collector server, add entries to the local hosts file, both resolving to the Portal server IP address.