Search <book_title>...

NetBackup IT Analytics Data Collector Installation Guide for Backup Manager

Last Published: 2023-03-01

Product(s): NetBackup IT Analytics (11.0)

Introduction
1. Overview
2. Backup Manager Collection of Backup and Restore Data
Pre-Installation setup for Commvault Simpana
1. Introduction
2. Architecture overview (Commvault Simpana)
3. Prerequisites for adding Data Collectors (Commvault Simpana)
4. Upgrade troubleshooting: Microsoft SQL Server and Java 11
5. Installation overview (Commvault Simpana)
6. Open TCP/IP access to the Commvault database
  1. Additional Static Port Configuration Steps
7. Set up a read-only user in the CommServe server
  1. Option 1: Execute SQL commands in the CommServe database
  2. Option 2: Use MSSQL Management Studio
8. Load historical data prior to initial data collection
9. Add Commvault Simpana servers
10. Add a Commvault Simpana Data Collector policy
Pre-Installation setup for Cohesity DataProtect
1. Introduction
2. Prerequisites for adding Data Collectors (Cohesity DataProtect)
3. Installation overview (Cohesity DataProtect)
4. Add a Cohesity DataProtect Data Collector policy
Pre-Installation setup for EMC Avamar
1. Introduction
2. Architecture overview (EMC Avamar)
3. Prerequisites for adding Data Collectors (EMC Avamar)
4. Installation overview (EMC Avamar)
5. Add EMC Avamar servers
6. Adding an EMC Avamar Data Collector policy
7. Testing the collection
8. Add/Configure an Avamar Server within the Data Collector policy window
9. Import EMC Avamar server information
  1. CSV Format Specifications
  2. Import Notes
10. Export EMC Avamar server information
Pre-Installation setup for EMC Data Domain backup
1. Architecture overview (EMC Data Domain Backup)
2. Prerequisites for adding Data Collectors (EMC Data Domain Backup)
3. Installation overview (EMC data domain Backup)
4. Add EMC data domain servers
5. Add an EMC data domain backup Data Collector policy
6. Adding/Configuring an EMC data domain server within the Data Collector policy window
7. Configure a data domain server for file-level compression collection
Pre-Installation setup for EMC NetWorker
1. Introduction
2. Architecture overview (EMC NetWorker)
  1. EMC NetWorker Terminology
3. Prerequisites for adding Data Collectors (EMC NetWorker)
4. Installation overview (EMC NetWorker)
5. Add EMC NetWorker servers
6. Adding an EMC NetWorker Data Collector policy
7. Adding/Editing a EMC NetWorker server within the Data Collector policy
8. Configure a notification action in EMC NetWorker
Pre-Installation setup for Dell EMC NetWorker backup & Recovery
1. Introduction
2. Prerequisites for adding data collectors (Dell EMC NetWorker Backup & Recovery)
3. Installation overview (Dell EMC Networker Backup & Recovery)
4. Adding a Dell EMC Networker Backup & Recovery Data Collector policy
Pre-Installation setup for generic backup
1. Introduction
2. Generic backup data collection
3. Prerequisites for adding Data Collectors (Generic Backup)
4. Installation overview (generic backup)
5. Add generic backup servers
6. Add a generic backup Data Collector policy
7. Adding/Editing a generic backup server within the Data Collector policy
8. Manually load the CSV file (generic backup)
9. CSV format specification
  1. EXAMPLE: genericBackupJobs.csv
Pre-Installation setup for HP Data Protector
1. Introduction
2. Architecture overview (HP Data Protector)
3. Prerequisites for adding Data Collectors (HP Data Protector)
4. Installation overview (HP Data Protector)
5. Identify HP Data Protector collection requirements
6. Cell Manager commands for data collection
7. Preparing for centralized data collection on a remote Cell Manager
8. Configure the Data Collector server in Cell Manager (HP Data Protector)
  1. Requirements for the Data Collector (Windows)
  2. Steps to Configure the Data Collector Server in Cell Manager
9. Configure an HP Data Protector admin user
10. Validate HP Data Protector setup
11. Add HP Cell Manager servers to NetBackup IT Analytics
12. Add an HP Data Protector Data Collector policy
13. Add/Edit a HP Data Protector server within the Data Collector policy
14. Tune the configuration
Pre-Installation setup for IBM Spectrum Protect (TSM)
1. Introduction
2. Architecture overview (IBM Spectrum Protect -TSM)
  1. IBM Spectrum Protect (TSM) - servers and instances defined
3. Prerequisites for adding data collectors (IBM Spectrum Protect - TSM)
4. Installation overview (IBM Spectrum Protect - TSM)
5. Add IBM Spectrum Protect (TSM) servers
6. Adding an IBM Spectrum Protect (TSM) Data Collector policy
7. Add/Configure an IBM Spectrum Protect (TSM) server within the Data Collector policy
8. Import IBM Spectrum Protect (TSM) information
  1. CSV format specifications
9. Export IBM Spectrum Protect (TSM) server information
Pre-Installation setup for NAKIVO Backup & Replication
1. Introduction
2. Prerequisites for adding data collectors (NAKIVO Backup & Replication)
3. Installation overview (NAKIVO Backup & Replication)
4. Add a NAKIVO Backup & Replication Data Collector policy
Pre-Installation setup for Veritas Backup Exec
1. Introduction
2. Architecture overview (Veritas Backup Exec)
3. Backup Exec terminology
4. Prerequisites for adding data collectors (Veritas Backup Exec)
5. Upgrade troubleshooting: Microsoft SQL Server and Java 10
6. Installation overview (Veritas Backup Exec)
7. Enable TCP/IP for the SQL server
8. Configure a Windows user
9. Add Veritas Backup Exec servers
10. Importing Backup Exec Server information
11. Add a Veritas Backup Exec Data Collector policy
Pre-Installation setup for Veritas NetBackup
1. Introduction
2. General prerequisites for adding data collectors (Veritas NetBackup)
3. Centralized or distributed deployment (Veritas NetBackup)
4. Centralized NetBackup data collection (Recommended)
5. Prerequisites to use SSH and WMI (Veritas NetBackup)
6. Prerequisites for NetBackup collection over SSH (Kerberos option)
  1. Enable Kerberos authentication for NetBackup SSH collection
7. Prerequisites for centralized NetBackup data collection (using NetBackup software)
8. Prerequisites for collection from Veritas NetBackup deployed as a Docker image
9. Veritas NetBackup 8.1 (or later) requirements for centralized collection
10. Distributed NetBackup data collection
11. Enable access to the Veritas NetBackup Master Server
12. Before you install the Data Collector (Veritas NetBackup)
13. Collecting from NetBackup clusters
14. Clustered NetBackup upgrade procedure
15. Add a Veritas NetBackup Data Collector policy
16. Add/Edit NetBackup Master Servers within the Data Collector policy
17. Configuring file analytics in NetBackup Data Collector policy
Pre-Installation setup for Veritas SaaS backup
1. Introduction
2. Prerequisites for adding data collectors (Veritas SaaS Backup)
3. Installation overview (Veritas SaaS Backup)
4. Add a generic backup Data Collector policy
Pre-Installation setup for Oracle Recovery Manager (RMAN)
1. Introduction
2. Prerequisites for adding data collectors (Oracle Recovery Manager - RMAN)
3. Installation overview (Oracle Recovery Manager - RMAN)
4. Add an Oracle Recovery Manager (RMAN) Data Collector policy
Pre-Installation setup for Rubrik Cloud Data Management
1. Introduction
2. Prerequisites for adding Data Collectors (Rubrik Cloud Data Management)
3. Installation overview (Rubrik Cloud Data Management)
4. Add a Rubrik Cloud Data Management Data Collector policy
Pre-Installation setup for Veeam Backup & Replication
1. Introduction
2. Prerequisites for adding data collectors (Veeam Backup & Replication)
3. Verifying Data Collector servers can connect to Veeam servers
4. Known issues and limitations (Veeam Backup & Replication)
5. Installation overview (Veeam Backup & Replication)
6. Add a Veeam Backup & Replication Data Collector policy
Discovery policies for Veritas NetBackup
1. Task overview: Configure and monitor discovery policies
2. Discovery policies overview
3. About Discovery types
4. Activate a Discovery license
5. Exclude devices from Discovery policies
6. Activate Discovery probes in the NetBackup Data Collector policy
7. Monitor Discovery processes
8. View client protection status
9. Reset Discovery data
10. Why enable SNMP?
11. About SNMP probes
  1. First probe (sysObjectOID)
  2. Second probe (sysDescr OID)
12. Example--Installing Net-SNMP
13. Troubleshoot Net-SNMP installations
Installing the Data Collector software
1. Introduction
2. Installing the WMI Proxy service (Windows host resources only)
3. Testing WMI connectivity
4. Considerations to install Data Collector on non-English systems
5. Install Data Collector Software on Windows
6. Install Data Collector software on Linux
7. Install Data Collector in containerized environment
Validate data collection
1. Validation methods
2. Data Collectors: Vendor-Specific validation methods
3. Working with on-demand Data Collection
  1. View real-time logging during an on-demand collection
  2. Generating debug level logs during an on-demand collection
4. Collect historic data on-demand
5. Using the CLI check install utility
6. List Data Collector configurations
Manually start the Data Collector
1. Introduction
Uninstall the Data Collector
1. Uninstall the Data Collector on Linux
2. Uninstall the Data Collector on Windows
Appendix A. Load historic events
1. Introduction
2. Load Commvault Simpana events
3. Load EMC Avamar events
4. Load EMC NetWorker events
5. Load HP Data Protector events
6. Load IBM Spectrum Protect (TSM) events
7. Load Oracle Recovery Manager (RMAN) events
8. Load Veeam Backup & Replication events
9. Load Veritas NetBackup events
  1. Load events for individual NetBackup clients
  2. Load events for a group of NetBackup clients
10. Load Veritas Backup Exec events
11. Corrections in duplication of clients
12. Cohesity
13. Dell EMC NetWorker Backup & Recovery
Appendix B. Firewall configuration: Default ports
1. Firewall configuration: Default ports

Add an HP Data Protector Data Collector policy

Before adding the policy: A Data Collector must exist in the Portal, to which you will add Data Collector Policies.
For specific prerequisites and supported configurations for a specific vendor, see the Certified Configurations Guide.
After adding the policy: For some policies, collections can be run on-demand using the Run button on the Collector Administration page action bar. The Run button is only displayed if the policy vendor is supported.
On-demand collection allows you to select which probes and devices to run collection against. This action collects data the same as a scheduled run, plus logging information for troubleshooting purposes. For probe descriptions, refer to the policy.

To add the policy

Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
Search for a Collector if required.
Select a Data Collector from the list.
Click Add Policy, and then select the vendor-specific entry in the menu.
Optionally add an HP Data Protector Backup Server from the policy screen. This action can also be completed in the Inventory.
See Add/Edit a HP Data Protector server within the Data Collector policy.
Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*):

Table:

Field	Description
Collector Domain	The domain of the collector to which the collector backup policy is being added. This is a read-only field. By default, the domain for a new policy will be the same as the domain for the collector. This field is set when you add a collector.
Policy Domain	The Collector Domain is the domain that was supplied during the Data Collector installation process. The Policy Domain is the domain of the policy that is being configured for the Data Collector. The Policy Domain must be set to the same value as the Collector Domain. The domain identifies the top level of your host group hierarchy. All newly discovered hosts are added to the root host group associated with the Policy Domain. Typically, only one Policy Domain will be available in the drop-down list. If you are a Managed Services Provider, each of your customers will have a unique domain with its own host group hierarchy. To find your Domain name, click your login name and select My Profile from the menu. Your Domain name is displayed in your profile settings. Example: `yourdomain`
Backup Management Server*	Select the Cell Manager server. Verify that the IP address and OS information are correct.
Add	Click Add to add a Cell Manager server. Added servers are also displayed in the Inventory. Note: If the hosts already exists, APTARE IT Analytics displays a confirmation dialog box to update the Host Details (including the Host Type). Click Ok to update Host details / Host Type.
Edit	Select a Cell Manager server and click Edit to update the values.
Cell Manager*	The Cell Manager is the server that runs session managers and core software to manage the backup details in the HP Data Protector database. Enter the name or IP address of the HPDP Cell Manager server. In the majority of cases, this field should contain the same server that you selected from the above Backup Management Server list; however, for special-case situations, an alias may be entered. Example: HPSERVER
Backup Software Location*	On the Data Collector server, this is the home directory of the HP Data Protector Admin Client software - that is, the location of the omni commands, such as omnicellinfo and omnireport - to be used by the Data Collector server.
Remote Access Configuration The following parameters are required only when the Data Collector server is different from the Cell Manager server.
Remote Software Location	The home directory on the HP Data Protector server where Cell Manager is installed. Typically C:\Program Files\Omniback for Windows, or /opt/omni for Linux; only required for remote access to Cell Manager.
Operating System	The operating system on which the HP Data Protector Data Collector is running; only required for remote access to Cell Manager.
Cell Manager User ID	An Admin User that the Cell Manager server recognizes--either a local user account or a Windows domain user account--that has execute rights to the omnidbutil command. This command is used to obtain drive status. Required only when the Data Collector is on a server that is different from the Cell Manager server.
Password/Repeat Password	Password for the Cell Manager User ID on the remote system.
Access Control Command	For Linux hosts: If the user ID is not root, provide the full path to access control; Example: /usr/bin/sudo
WMI Proxy Server	Enter the server name or IP address where the WMI Proxy is installed. Only needed if collecting from Windows hosts and when the Data Collector is on a server that is different from the Cell Manager server. If the Data Collector is installed on a Linux OS, a WMI Proxy Server must be installed on a Windows system in order to collect data from a Cell Manager that is installed on a Windows system.
Windows Domain	The Windows domain, if applicable.
Notes	Enter or edit notes for your data collector policy. The maximum number of characters is 1024. Policy notes are retained along with the policy information for the specific vendor and displayed on the Collector Administration page as a column making them searchable as well.