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
Centralized Data Collector
A centralized Data Collector can collect data from all backup products. You can also include other enterprise objects, such as storage arrays, SAN switches, Compute, and Cloud assets for a Centralized Data Collector. A centralized Data Collector resides on a separate Windows or Linux Server and remotely connects to NetBackup Primaries using Secure Shell Protocol (SSH), Windows Management Instrumentation (WMI), or via REST APIs.
If you are collecting data from Veritas Backup Exec, third-party Data Protection Vendors, Storage Arrays, SAN switches and cloud assets, then you must choose a centralized Data Collector. Note that there can be situations where you can also use a centralized Data Collector to collect from NetBackup, but Cohesity typically recommends using a distributed Data Collector for NetBackup and a centralized Data Collector for all other subsystems you are collecting the data from.
NetBackup security hardening, such as implementing Multifactor Authentication and using a non-privileged service account, adds complexity and additional configuration steps, leveraging the centralized Data Collector for NetBackup collections. There are also additional networking / firewall considerations with a centralized Data Collector for NetBackup.
You can have a mix of distributed and centralized Data Collectors. In the illustration below, a centralized Data Collector is installed in a data center and it collects data from many different subsystems.
A single instance of a centralized Data Collector can support any number of enterprise objects. However, each environment has its own unique deployment configuration requirements, so it is important to understand where the Data Collector software must be installed to determine how many Data Collectors must be installed and which servers are best suited for the deployment. It is also important to understand that you might want a combination of distributed and centralized Data Collectors, particularly if you are collecting data from other third-party subsystems. A distributed Data Collector embedded by default on a NetBackup Primary Server can only be used to collect data from NetBackup or Veritas Alta Data Protection.
Whether you need to install the Data Collector software depends on the NetBackup version and whether NetBackup is clustered. For NetBackup 10.1.1 or later, the distributed Data Collector binary is already pre-installed provided it is not deployed in a clustered environment. You have the option to configure the data collector to point to NetBackup IT Analytics or Alta View. Note that from NetBackup 10.4 onwards, Data Collector is optional to install. If you are planning to use NetBackup IT Analytics or Alta View, you must opt to install Data Collector while installing/upgrading NetBackup. But if you did not install the Data Collector initially, and later decided to use Alta, then you must install it manually.
For clustered NetBackup Primary Servers or NetBackup Primary Servers on a NetBackup release prior to 10.1.1, a Data Collector is not installed by default and the Data Collector binaries must be manually installed.