NetBackup IT Analytics Data Collector Installation and Configuration Guide
- Section I. Introduction
- Introduction
- Install and configure a Data Collector
- Step-1: Choose operating system and complete prerequisites
- Installing the Data Collector software
- Configure SSL
- Section II. Data Protection
- Configuration for Veritas Backup Exec
- Configuration for Cohesity DataProtect
- Configuration for Commvault Simpana
- Open TCP/IP access to the Commvault database
- Set up a read-only user in the CommServe server
- Configuration for EMC Avamar
- Import EMC Avamar server information
- Configuration for EMC Data Domain backup
- Configuration for Dell EMC NetWorker backup & recovery
- Importing generic backup data
- Configuration for generic backup
- CSV format specification
- Configuration for HP Data Protector
- Architecture overview (HP Data Protector)
- Configure the Data Collector server in Cell Manager (HP Data Protector)
- Configuration for IBM Spectrum Protect (TSM)
- Architecture overview (IBM Spectrum Protect -TSM)
- Import IBM Spectrum Protect (TSM) information
- Configuration for NAKIVO Backup & Replication
- Configuration for Oracle Recovery Manager (RMAN)
- Configuration for Rubrik Cloud Data Management
- Configuration for Veeam Backup & Replication
- 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
- 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
- Configuring a Hitachi Device manager user
- Configuration for Hitachi Content Platform (HCP)
- 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
- Configure host Discovery policies to populate the host Inventory
- Validate host connectivity
- Host Inventory search and host Inventory export
- 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
- Configuration for Microsoft Hyper-V
- Section V. Cloud
- Configuration for Amazon Web Services (AWS)
- Mandatory probe user privileges
- Link AWS accounts for Collection of consolidated billing data
- Configuration for Google Cloud Platform
- Configuration for OpenStack Ceilometer
- Configuration for OpenStack Swift
- Configuration for Microsoft Azure
- Configuration for Amazon Web Services (AWS)
- Section VI. Fabric
- Configuration for Brocade switch
- Configuration for Cisco switch
- Configuration for Brocade Zone alias
- Configuration for Cisco Zone alias
- Configuration for Brocade switch
- Section VII. File Analytics
- Configuration for File Analytics
- Host Discovery and Collection File Analytics probe
- Adding a File Analytics Data Collector policy
- 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
- Host resources: Check host connectivity using standard SSH
- Host resources: Generating host resource configuration files
- Configuring parameters for SSH
- Uninstalling the Data Collector
- Appendix A. Firewall Configuration: Default Ports
- Appendix B. Load historic events
- Load Veritas NetBackup events
- Appendix C. CRON Expressions for Policy and Report Schedules
- Appendix D. Maintenance Scenarios for Message Relay Server Certificate Generation
Host access requirements
This section lists the access requirements for host resource data collection. You will use this information to populate the configurations used by the Host Discovery, Validation, and Collection processes.
Create a list of the name or IP address for each host for which you want to collect data.
User ID & Password Credentials: Root-level, read-only access is required for host data collection.
See Manage credentials.
Access Control: For security reasons, most enterprise environments mandate access control where a new non-root account is created, with temporarily elevated access to the required commands provided via an access control command, such as sudo. Otherwise, the root user is required for host access. For Linux Hosts in access control environments, if a command such as sudo is used and the absolute path is not in the interactive ssh, identify the absolute path of the access control command.
See Verify command paths.
See Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements.
Path: NetBackup IT Analytics must have knowledge of the correct paths to access commands. An overview of the requirements is listed here, with the details provided in
See Verify command paths.
For Windows hosts, a path is required for fcinfo, hbacmd, and scli commands. For Linux hosts, if the Data Collector is installed on a Windows server, use plink.exe to determine the path; if the Data Collector is installed on a Linux server, determine the path by executing ssh.
HBA Prerequisites: NetBackup IT Analytics uses an internal probing mechanism to gather Host Bus Adapter (HBA) data from Windows hosts. It is critical for the Data Collector to probe the HBA in order to establish a host's relationship with storage. Without the HBA information, all storage for a host will be listed as local storage.
Note:
Do not enable HBA probes for VMware guest host collection.
Windows: One of the following mechanisms is required to collect Windows HBA information. The Data Collector actually uses all of the mechanisms that are available and then merges the data collected from all. A collection error is reported only if all of the following methods fail.
hbaverify is provided by default with the Data Collector WMI Proxy installation.
scli - SANsurfer Command Line Interface (SCLI) for Windows from QLogic (SCLI is a separate install from the base install of SANsurfer and often is not installed with the SANsurfer utility).
hbacmd (HBAnyware from Emulex) is required for both LUN Mapping and HBA data collection. This is typically provided by default as part of the driver software.
fcinfo - Fibre Channel Information Tool from Microsoft is not typically used, as the previously listed methods are preferred.
Linux: scli or hbacmd (required only for HBA information)
Solaris: scli or hbacmd (required only for HBA information)