NetBackup IT Analytics Data Collector Installation Guide for Backup Manager
- Introduction
- Pre-installation setup for Veritas Flex Appliance
- 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
Add a Veritas Flex Appliance 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 NetBackup IT Analytics 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.
The data collection form the appliances depends on the availability of the components that expose the appliance stats to the policy probes. The data collection supported for each Flex Appliance version is as indicated below. You need to create an RTD report to view the data. Collection is performed via REST APIs exposed by the Flex Appliance.
Table: Data collection based on appliance version
Policy probe | Collection type | Supported Veritas Flex Appliance version |
|---|---|---|
Appliance Details | Hardware details of appliance and its nodes | 2.0, 2.1, 3.0 , 3.2, 4.0 |
Performance Statistics | Node and container details | 2.0, 2.1, 3.0, 3.2, 4.0 |
Storage Statistics | Storage consumption details | 2.0.1, 2.1, 3.0, 3.2, 4.0 |
To add the policy
- Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
- Search for a collector if required or select a Data Collector from the list.
- Click Add Policy, and then select Veritas Flex Appliance entry in the menu.
- Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*):
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 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.
Add
Click to add a Veritas Flex Appliance to the policy. Provide valid Appliance Address, User ID, and Password for a successful connection.
Appliance Address*
Fully qualified domain name (FQDN) of the Veritas Flex Appliance. This FQDN enables the policy to collect from all the appliance nodes that are up-and-running. The data persisted is distinguished by the node ID as registered on the appliance.
Note:
Flex appliance connector supports only FQDN in Appliance Address.
Username*
Username required to access the Flex Appliance.
Password*
Password required to access the Flex Appliance.
Appliance Details
Collects hardware and software details of Flex Appliance added in the policy. The collected details include:
For appliance: appliance name, UUID, appliance type, and more.
For node: Node name, serial number, firmware version, Flex version and so on.
The probe is selected by default and has a default schedule and its data collection is independent of other probes, irrespective of the data and the execution order.
Performance Statistics
Collects resource utilization and performance statistics from each appliance node and the containers running on the Flex Appliance. The data is collected for each container and is segregated on the basis of appliance and host node on which the container is running. You must create custom reports to view the collection from the nodes and containers.
Note:
Flex v3.0 supports per user active session limited to 10 sessions. Veritas recommends to create a dedicated user for ITA Flex Appliances policy and utilize those credentials for data collection.
Note:
In Flex v3.0, container metrics are restricted due to vulnerabilities in cAdvisor exporter. For this reason, Performance Probe will only collect node metrics from flex appliance with flex version 3.0. No data will be available for container metrics
Storage statistics
Collects storage utilization specific to the entire Flex Appliance, irrespective of its nodes. Collection is performed via REST APIs exposed by the Flex Appliance.
Schedules
By default, collection for Performance Statistics is run performed every 5 minutes and for Storage Statistics, collection is performed daily at 03:33 hours.
Click the clock icon to create a schedule.
Every Minute, Hourly, Daily, Weekly, and Monthly schedules may be created. Advanced use of native CRON strings is also available.
Examples of CRON expressions:
*/30 * * * * means every 30 minutes
*/20 9-18 * * * means every 20 minutes between the hours of 9am and 6pm
*/10 * * * 1-5 means every 10 minutes Mon - Fri.
Note:
Explicit schedules set for a Collector policy are relative to the time on the Collector server. Schedules with frequencies are relative to the time that the Data Collector was restarted.
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.
Test Connection
Test Connection initiates a Data Collector process that attempts to connect to all the appliances added to the policy using the FQDN and credentials supplied in the policy. Agent Services must be running for the Test Connection to succeed.
Several factors affect the response time of the validation request, causing some requests to take longer than others. For example, there could be a delay when connecting to the subsystem. Likewise, there could be a delay when getting the response, due to other processing threads running on the Data Collector.
You can also test the collection of data using the Run functionality available in Admin > Data Collection > Collector Administration. This On-Demand data collection run initiates a high-level check of the installation at the individual policy level, including a check for the domain, host group, URL, Data Collector policy and database connectivity. You can also select individual probes to test the collection run.
- Click OK to save the policy configuration.
Note:
Do not delete the swap directory (
<APTARE_HOME>\mbs\swap\veritas\flexappliance) from the data collector server as it is used by the Veritas Flex Appliance policy.
The data collected from Flex Appliances is visible in the Host CPU Utilization, Host Memory Utilization, and Host Network Packets Sent/Received reports. See NetBackup IT Analytics Report Reference Guide for more information on the reports.