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
Deploy Data Collector in native Kubernetes environment
This procedure provides the steps to deploy Data Collector Docker image on a Kubernetes cluster through an operator with the required configuration on Linux hosts. This method enables efficient Data Collector installation and reduces the human errors caused during manual or ISO-based installations.
System requirements and installation dependencies for the system on which Data Collector will be installed are listed below:
Obtain the Docker image generated from the CI/CD build.
Kubernetes must be pre-installed on the system.
Assume root role on the host system.
Kubernetes cluster must be accessible on the system.
Ensure that the file system supporting the
/data
directory has enough free space as recommended in the NetBackup IT Analytics Certified Configurations Guide for Data Collector.The
/data
directory in the host system will be mounted inside the container as/usr/openv/analyticscollector
.Obtain the following Data Collector details. You are required to supply these details to the installer during the installation process.
Registry: The name of the registry to which you want to push the installer images.
Absolute path of Data Receiver Certificate file: Absolute path of the data receiver certificate file downloaded from NetBackup IT Analytics Portal.
Absolute path of the Data Collector Registration File: Absolute path of the Data Collector registration file downloaded from the NetBackup IT Analytics Portal.
Proxy settings:
Portal IP address: IP address of the system hosting the NetBackup IT Analytics Portal.
Portal HostName: aptareportal.<DOMAIN> or itanalyticsportal.<DOMAIN>
Agent HostName: aptareagent.<DOMAIN> or itanalyticsagent.<DOMAIN>
StorageClass Name: Name of the Kubernetes storage class to be used.
Obtain the
itanalytics_k8s_artificats.tar
from the Cohesity Download Center. The tarball has the container image, operater image, set of.yaml
files, and the scripts.
To deploy the Data Collector in Kubernetes environment:
- Login to the Kubernetes cluster.
- Run this command on the primary node and label the node on which you want to deploy the Data Collector.
kubectl label node <worker_node_name> itaDcNodeKey=itaDcDeploymentNode
- From the
itanalytics_k8s_artifacts.tar
location, run this command to initiate the Data Collector installation.tar -xvf itanalytics_k8s_artifacts.tar scripts
This saves a
scripts
folder at theitanalytics_k8s_artifacts.tar
file location,. - From the
scripts
folder, run this script.cd scripts/ sh itanalytics_dc_installer.sh
Note:
The installation logs are saved to
itanalytics_dc_installer_<time_stamp>.log
. - Provide the Data Collector configuration details when asked by the installer in the following order.
Registry
The installer asks for a confirmation after providing the registry name to proceed with pushing the images. You need to enter y for a fresh installation. If for any reason, you are required to re-run the installation and this step was successfully completed anytime before for the same cluster node, you can enter n to avoid a rewrite and bypass this step.
Absolute path of Data Receiver Certificate file (if you have set an https:// URL for the data receiver)
Absolute path of the Data Collector registration file
Proxy settings
Portal IP address
Portal HostName
Agent HostName
StorageClass Name
- The installer asks to confirm the configuration details before proceeding with the installation. Enter y to proceed with the data collector installation
After a successful installation, verify whether the Data Collector status appears Online on the NetBackup IT Analytics Portal.
Run this command to connect to the pod instance and also to facilitate debugging when required.
# kubectl exec -it<pod ID> -- bash