NetBackup IT Analytics Data Collector Installation Guide for Backup Manager
- Introduction
- Pre-Installation setup for Commvault Simpana
- Open TCP/IP access to the Commvault database
- Set up a read-only user in the CommServe server
- Pre-Installation setup for Cohesity DataProtect
- Pre-Installation setup for EMC Avamar
- Import EMC Avamar server information
- Pre-Installation setup for EMC Data Domain backup
- Pre-Installation setup for EMC NetWorker
- Architecture overview (EMC NetWorker)
- Pre-Installation setup for Dell EMC NetWorker backup & Recovery
- Pre-Installation setup for generic backup
- CSV format specification
- Pre-Installation setup for HP Data Protector
- Architecture overview (HP Data Protector)
- Configure the Data Collector server in Cell Manager (HP Data Protector)
- Pre-Installation setup for IBM Spectrum Protect (TSM)
- Architecture overview (IBM Spectrum Protect -TSM)
- Import IBM Spectrum Protect (TSM) information
- Pre-Installation setup for NAKIVO Backup & Replication
- Pre-Installation setup for Veritas Backup Exec
- Pre-Installation setup for Veritas NetBackup
- Prerequisites to use SSH and WMI (Veritas NetBackup)
- Prerequisites for NetBackup collection over SSH (Kerberos option)
- 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
- Discovery policies for Veritas NetBackup
- About Discovery types
- About SNMP probes
- Installing the Data Collector software
- Validate data collection
- Manually start the Data Collector
- Uninstall the Data Collector
- Appendix A. Load historic events
- Load Veritas NetBackup events
- Appendix B. Firewall configuration: Default ports
Prerequisites for collection from Veritas NetBackup deployed as a Docker image
This section describes the portal configurations required, before adding a Veritas NetBackup policy, when Veritas NetBackup is deployed as a Docker image in the cloud and it is using the cloud resources to perform backups.
Since Veritas NetBackup is deployed as a Docker image, it must communicate with the Data Collector using SSH key-based authentication.
- Generate an SSH public/private key pair. This key will be required later during configuration. To generate this key pair, run the ssh-keygen command on a Linux system or an equivalent command on Windows.
Save the public and private key pair along with the passphrase used while generating the key, as you will need to provide the private key path and the passphrase while creating the NetBackup Collection policy in NetBackup IT Analytics Portal.
- Copy the public key to the itAnalyticsPublicKey spec of the Environment Custom Resource
environment.yaml
. You can find this file on the jumpserver that was used to create the initial NetBackup setup on Kubernetes cluster. - Apply the update to itAnalyticsPublicKey spec using kubectl apply -f environment.yaml. The
environment.yaml
file is available on the jumpserver used to create the NetBackup primary server setup on Kubernetes cluster.Alternatively, if the jumpserver is not accessible, use kubectl edit environment <environment_name> -n <namespace> command to edit the environment to add the public key to the itAnalyticsPublicKey sec
- On a successful deployment, describe the Environment Custom Resource using kubectl describe PrimaryServer <primary-server-name> -n <namespace>.
This API key is required when you add or edit a Veritas NetBackup primary server for the Veritas NetBackup policy configuration. This API key is essential especially when NetBackup IT Analytics has to collect metrics from NetBackup deployed as a Docker image in the cloud.
See the Manage API keys section from the NetBackup Web UI Security Administrator's Guide for steps to get the API key.
If the Firewall of the NetBackup primary server is turn on, follow these steps to communicate through the Firewall port:
- Open and edit the file
/etc/firewalld/zones/public.xml
. - Add the following lines in the file:
<service-name="https"/> <port protocol = "tcp" port="1556">
- Save the file.