NetBackup IT Analytics Data Collector Installation and Configuration Guide
- Section I. Introduction
- Introduction
- Install and configure a Data Collector
- Overview
- Step-1: Choose operating system and complete prerequisites
- Step-2: HTTPS requirement
- Step-3: Add Data Collector on NetBackup IT Analytics Portal
- Step-4: Install the Data Collector
- Step-5: Verify the Data Collector is online from the Portal
- Step-6: Confirm that the Data Collector is updated
- Step-7: Configure the data collection policy
- Step-8: Confirm that the data collection policy is collecting data
- Installing the Data Collector software
- Introduction
- Considerations to install Data Collector on non-English systems
- Install Data Collector Software on Windows
- Install Data Collector software on Linux
- Configure Data Collector manually for Cohesity NetBackup
- Install Data Collector binaries on Windows (without configuration)
- Install Data Collector binaries on Linux host (without configuration)
- Configure SSL
- SSL/TLS certificate configuration
- SSL implementation overview
- Obtain an SSL certificate
- Update the web server configuration to enable SSL on the Portal server
- Enable / Disable SSL for a Data Collector
- Enable / Disable SSL for emailed reports
- Test and troubleshoot SSL configurations
- Keystore file locations on the Data Collector server
- Import a certificate into the Data Collector Java keystore
- Keystore on the portal server
- Add a virtual interface to a Linux server
- Add a virtual / secondary IP address on Windows
- Section II. Data Protection
- Configuration for Veritas Backup Exec
- Introduction
- Architecture overview (Veritas Backup Exec)
- Backup Exec terminology
- Prerequisites for adding data collectors (Veritas Backup Exec)
- Installation overview (Veritas Backup Exec)
- Enable TCP/IP for the SQL server
- Configure a Windows user
- Add Backup Exec servers
- Importing Backup Exec Server information
- Add a Veritas Backup Exec Data Collector policy
- Configuration for Cohesity DataProtect
- Configuration 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
- Configuration 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
- Configuration 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
- Configuration for Dell EMC NetWorker backup & recovery
- Configuration of Dell EMC PowerProtect Data Manager (PPDM)
- Importing generic backup data
- Configuration 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
- Configuration 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
- Configuration 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
- Configuration for NAKIVO Backup & Replication
- Configuration for Oracle Recovery Manager (RMAN)
- Configuration for Rubrik Cloud Data Management
- Configuration 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
- Configuration for Veritas Backup Exec
- Section III. Storage (Capacity)
- Configuration for Compute Resources
- Configuration for DELL EMC Elastic Cloud Storage (ECS)
- Configuration for Dell EMC Unity
- Pre-installation setup for Dell PowerStore
- Configuration for EMC data domain storage
- Configuration for EMC Isilon
- Configuration for EMC Symmetrix
- Configuration for EMC VNX Celerra
- Configuration for EMC VNX CLARiiON
- Configuration for EMC VPLEX
- Configuration for EMC XtremIO
- Configuration for FUJITSU ETERNUS Data Collector
- Configuration for Hitachi Block
- Pre-Installation setup for Hitachi Block
- Prerequisites for adding Data Collectors (Hitachi Block)
- Installation overview (Hitachi Block Storage)
- Adding a Hitachi Block Storage Data Collector policy
- Configuring a Hitachi Device manager user
- Configuring a Collector for Hitachi NAS block storage
- Adding an HP command view advanced Data Collector policy
- Configuration for Hitachi Content Platform (HCP)
- Pre-Installation setup for Hitachi Content Platform (HCP)
- Prerequisites for adding Data Collectors (Hitachi Content Platform)
- Installation overview (Hitachi Content Platform)
- Add a Hitachi Content Platform (HCP) Data Collector policy
- Setting up permissions for an HCP local user or active directory user
- Hitachi content platform system management console
- Hitachi content platform tenant management console
- Configuration for Hitachi NAS
- Configuration for Hitachi Vantara All-Flash and Hybrid Flash Storage
- Configuration of Host inventory
- Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements
- Host Inventory pre-installation setup
- Plan host Data Collection
- WMI Proxy requirements for Windows host Data Collection
- Host access requirements
- Verify command paths
- Host Inventory configuration steps
- Host Inventory setup overview
- Host Inventory maintenance overview
- Before discovering hosts
- Configure / Search the host Inventory
- Manage credentials
- Manage WMI proxy
- Manage paths
- Manage access control
- Host Inventory management
- Configure host Discovery policies to populate the host Inventory
- Execute and monitor host Discovery
- Validate host connectivity
- Show errors
- Filter the host Inventory - hide / un-hide, remove
- Host Inventory search and host Inventory export
- Export the host Inventory
- Configure and edit host probes
- Propagate Probe Settings: Copy Probes, Paste Probes
- Configuration for HP 3PAR
- Configuration for HP EVA
- Configuration for HPE Nimble Storage
- Configuration for HPE StoreOnce
- Configuration for IBM Enterprise
- Configuration for IBM COS
- Configuration for IBM SVC
- Configuration for IBM XIV
- Configuration for Microsoft Windows server
- Configuration for NetApp-7
- Configuration for NetApp StorageGRID
- Configuration for NetApp Cluster
- Configuration for NetApp E-Series
- Configuration for NEC HYDRAstor
- Configuration for Pure Storage FlashArray
- Section IV. Compute (Virtualization and Host Collection)
- Configuration for VMware
- Configuration for IBM VIO
- Pre-Installation setup for IBM VIO
- Prerequisites for adding data collectors (IBM VIO)
- Installation overview (IBM VIO)
- Adding servers for the IBM VIO Data Collector policy
- VIO servers (IBM Virtual I/O Servers)
- LPAR clients (IBM Logical Partitioning Clients) managed by VIO servers
- HMC (IBM Hardware Management Console)
- Add an IBM VIO Data Collector policy
- Configuration for Microsoft Hyper-V
- Section V. Cloud
- Configuration for Amazon Web Services (AWS)
- Pre-Installation setup for Amazon Web services (AWS)
- Prerequisites for adding Data Collectors (Amazon Web services)
- Prerequisite Amazon Web services (AWS) configurations
- Configure an S3 bucket to receive billing reports
- Select cost allocation tags
- Create an AWS IAM user
- Mandatory probe user privileges
- Link AWS accounts for Collection of consolidated billing data
- Installation overview (Amazon Web Services - AWS)
- Add an Amazon Web Services (AWS) policy
- Configuration for Google Cloud Platform
- Configuration for OpenStack Ceilometer
- Configuration for OpenStack Swift
- Configuration for Microsoft Azure
- Pre-Installation setup for Microsoft Azure
- Setting up credentials for Microsoft Azure Data Collection
- Install the Azure PowerShell client on a Windows computer
- Find your tenant and subscription ID
- Register a new application for the Data Collector
- Create a principal and assign role to the application
- Prerequisites for Adding Data Collectors (Microsoft Azure)
- Installation overview (Microsoft Azure)
- Add a Microsoft Azure Data Collector policy
- Configuration for Amazon Web Services (AWS)
- Section VI. Fabric
- Configuration for Brocade switch
- Pre-Installation setup for Brocade switch
- Prerequisites for adding Data Collectors (Brocade switch)
- Upgrade troubleshooting: Brocade BNA SMI-S (CIM) server and Java 11
- Supported switches
- Brocade switches: Default ports and firewall considerations
- Installation overview (Brocade switch)
- Brocade switch Data Collector policy
- Configuration for Cisco switch
- Pre-Installation setup for Cisco switch
- Prerequisites for adding Data Collectors (Cisco switch)
- Upgrade troubleshooting: Cisco DCNM SMI-S (CIM) server and Java 11
- Cisco switches: Default ports and firewall considerations
- Installation overview (Cisco switch)
- Cisco switch Data Collection policy
- Before you start Cisco switch Data Collection
- Configuration for Brocade Zone alias
- Configuration for Cisco Zone alias
- Configuration for Brocade switch
- Section VII. File Analytics
- Configuration for File Analytics
- Pre-Installation setup for File Analytics
- File Analytics Data Collection overview
- File Analytics Data Collection architecture
- File Analytics Data Collector policies
- Prerequisites for adding Data Collectors (File Analytics)
- CIFS shares
- Host Discovery and Collection File Analytics probe
- Adding a File Analytics Data Collector policy
- Set up FIPS compliant Data Collector for File Analytics
- File Analytics Export Folder Size and Folder Depth
- Configuration for File Analytics
- Section VIII. Data Collection Validation and Troubleshooting
- Validate data collection
- Data Collector Troubleshooting
- Resolving Data Collectors connections issues - Linux specific
- Resolving Data Collectors connections issues - Windows specific
- Portal upgrade performance issues
- Verify the Data Collector configuration
- Verify Connectivity
- Configuring web proxy updates
- Collecting missed events for Veritas Backup Exec
- Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
- Useful Data Collection scripts for capacity
- Host resources troubleshooting
- Host resources: Check the status of the WMI proxy server
- Host resources: Post-Installation verification
- Host resources: Check host connectivity using standard SSH
- Host resources: Check host connectivity
- Host resources: Check host connectivity using Host Resource Configuration file
- Host resources: Generating host resource configuration files
- Host resources: Check the execution of a command on a remote server
- Host resources Data Collection
- Host resources: Collection in stand-alone mode
- Configuring parameters for SSH
- Identifying Windows file system access errors (File Analytics)
- Collect from remote shares (File Analytics)
- Adding a certificate to the Java keystore
- Uninstalling the Data Collector
- Appendix A. Firewall Configuration: Default Ports
- Appendix B. Load historic events
- Introduction
- Load Commvault Simpana events
- Load Dell PowerProtect Data Manager jobs
- 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 C. CRON Expressions for Policy and Report Schedules
- Appendix D. Maintenance Scenarios for Message Relay Server Certificate Generation
Brocade switch 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.
If the Collection method is REST API / Command Line Interface:
Collection Method using Brocade Switch supports Fabric OS version v8.2.1 and above.
Collection Method using Command Line Interface supports Brocade Switch version is v7.4.2h and above.
If the Indications Probe checkbox is selected, SNMP traps are collected instead of Brocade CIM indications. The following four SW traps are supported:
swFCPortScn
swStateChangeTrap
swDeviceStatusTrap
swEventTrap
Once the Indications Probe is running, any change in the SNMP fields of the policy will take about 2 minutes to reflect in the probe.
In Brocade REST API Server Address(es), in Brocade Switch Data Collector policy, configure switch IP address / fully qualified switch name.
Configured switch should be accessible. If switch is not accessible, collection fails. When any switch in the fabric is not accessible, collector collects basic information of that switch which it can collect without connecting to the switch.
Note:
For Configured Switch, Collector also collects Switch information from all other Switches in the Fabric. Collector uses the same User ID and Password, as configured in the Policy, to connect to other Switches.
When the Collection Method is Command Line Interface, add switch IP Address / fully qualified switch name of Principal switch in Brocade Server Address field.
When collection method is Command Line Interface, TCP port 22 and UDP port 161 on Brocade Switch must be open, and those must be accessible to Data Collector.
While retrieving logical switches, if a switch is not accessible, collector logs a warning message for that switch.
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.
Best Practices: Interconnected switches should be configured in the same Data Collector policy.
- Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*):
Field
Description
Sample Value
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.
yourdomain
Collection Method
The Collection Method sets the interface to connect to Brocade Switch.
The available options are:
SMI-S: If SMI-S options is selected, specify Brocade SMI agent Address.
REST API: If REST API option is selected, specify Brocade REST API Server Address(es).
Command Line Interface: If Command Line Interface is selected, then specify Brocade Switch Server Address.
Brocade Server Address*:
This field is enabled if Collection Method is Command Line Interface.
Specify only one Principal Switch IP address or fully qualified one Switch name for the Brocade Switch.
Note:
The port number is optional. The format should be: <ip_address>[:port_number].
Brocade SMI agent address*
This field is enabled if Collection Method is SMI-S.
Enter the IP address of the Brocade SMI agent and port number in the format: <ip_address>:port_number The port number is NOT required if you want to use the default port numbers: 5988 (http) or 5989 (https).
192.1.1.1
Brocade REST API Server Address(es)*
This field is enabled if Collection Method is REST API.
Specify the Principal Switch IP address or fully qualified Switch name for the Brocade Switch.
Note:
Port number is optional. The format should be: <ip_address>[:port_number]
192.1.1.1:8080
User ID*
Use the User ID and passcode for accessing the switch. This typically would be an administrator privilege, but must be a minimum privilege of a view-only user.
Administrator
Password*
Specify the password.
Note:
The password is encrypted prior to saving in the database and is never visible in any part of the application.
Password1
Repeat Password
Re-type the password you have specified in the Password field.
Exclude Switches
Enter a switch WWN - e.g., 10:00:00:60:69:90:04:9F, 100000606990049F
Colons within the WWN are NOT required. A comma-separated list is supported.
Note:
For the REST API, principal switch cannot be excluded.
10:00:00:60:69:90:04:9F, 100000606990049F
SNMP Version
SNMP version is enabled if the Collection Method is REST API and Indications Probe / FC Port Statistics Active is selected.
Select the SNMP version configured on the switch to receive SNMP traps. The available options are:
v1
v2c
v3
Indications Probe
If collection method is REST API, SNMP traps details are collected.
If collection method is SMI-S, CIM indication details are collected.
Community Name/Security Name
This field is enabled if the Collection Method is REST API and Indications Probe is turned on.
Specify the SNMP community name if the SNMP Version is v1/v2c or the SNMP security name if SNMP Version is v3, as configured on the switch.
public, snmpadmin1
Switch Details
Click the check box to collect switch details.
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.
FC Port statistics Active
Click the check box to collect FC Port statistics. This may have a performance impact, which can be optimized with the FC Port statistics schedule.
Click the clock icon to create a schedule.
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.
SNMP Port
SNMP port is enabled if the Collection Method is REST API and Indications Probe is turned on.
Specify the UDP port number of the collector configured on the switch at which SNMP traps will be received.
8163
Security Level
This field is enabled if the Collection Method is REST API, Indications Probe is turned on and SNMP version is v3.
Select the SNMP security level as configured on the switch. The available options are:
noAuthNoPriv: If noAuthNoPriv option is selected, authentication and privacy are disabled.
authNoPriv: If authNoPriv option is selected, specify the Authentication Protocol and Authentication Password. Privacy is disabled.
authPriv: If authPriv option is selected, specify the Authentication Protocol, Authentication Password, Privacy Protocol and Privacy Password.
Authentication Protocol
This field is enabled if the Collection Method is REST API, Indications Probe is turned on and Security Level is authNoPriv or authPriv.
Select the SNMP authentication protocol. The available options are: MD5 and SHA
Authentication Password
This field is enabled if Collection Method is REST API, Indications Probe is turned on and Security Level is authNoPriv.
Specify the SNMP authentication password.
Password1
Privacy Protocol
This field is enabled if Indications Probe is turned on and if Security Level is authPriv.
Select the SNMP privacy protocol. The available options are: DES and AES128
Privacy Password
This field is enabled if Indications Probe is turned on and if Security Level is authPriv.
Specify the SNMP privacy password.
Password1
Credentials Override
Configure switches to override the default credentials. Click Add to add credentials for a switch. Select a switch and click Edit to update the credentials.
Note:
To delete the switch credentials, select the appropriate switch and click Delete to delete the credentials.
Test Connection
Test Connection is supported if REST API option is selected as Collection Method.
Test connection message displays the details of the Data Collector connected to the switches as configured in the policy.
- If the collection method is Command Line Interface (CLI), then the Credentials Override can be added to the policy. Click Add or Edit and specify the parameters.
Field
Description
Sample Value
Server Address
Specify the IP address or fully qualified switch name for the Brocade switch
Override SSH credentials
Select to enable override for SSH credentials.
User ID
Specify the User ID.
Administrator
Password / Repeat password
Specify the password. Repeat the same password in the Repeat password field.
Note:
The password is encrypted.
Override SNMP credentials
Select to enable overriding of the SNMP credentials.
SNMP version
Select the appropriate SNMP version from the following:
V1
V2c
V3
Community name / Security name
Community name: Specify if the version selected is V1 / V2c.
Security name: Specify is the version select is V3.
public
snmpadmin1
Security level
The field is enabled only if the SNMP version selected is V3.
Select the appropriate security level as configured on the switch. Following are the available options:
noAuthNoPriv: If noAuthNoPriv option is selected, authentication and privacy are disabled.
authNoPriv: If authNoPriv option is selected, specify the Authentication Protocol and Authentication Password. Privacy is disabled.
authPriv: If authPriv option is selected, specify the Authentication Protocol, Authentication Password, Privacy Protocol and Privacy Password.
Authentication protocol
The field is enabled if the security level authNoPriv or authPriv is selected.
Select the appropriate SNMP authentication protocol from the following options:
MD5
SHA
Authentication password
Once the authentication protocol is configured, specify the SNMP authentication password.
password1
Privacy protocol
The field is enabled if the security level authPriv is selected.
Select the appropriate SNMP privacy protocol from the following options:
DES
AES128
Privacy password
Once the privacy protocol is configured, specify the SNMP privacy protocol password.
password1