Configure NetBackup IT Analytics for NetBackup deployment on Kubernetes
You can configure Data Collector on the primary server. Following are the steps for respective configurations.
Note:
From NetBackup version 10.3 Cloud Scale release, Data Collector on primary server is supported.
The following steps to configure the IT Analytics Data Collector need to be performed as root user. Connect to the primary server pod and then switch to root user using sudo.
To configureNetBackup IT Analytics for NetBackup deployment
- Create a DNS server entry in such a way that IP of the Portal must be resolvable to a single FQDN. IP of the NetBackup IT Analytics Portal must resolve to:
itanalyticsagent.<yourdomain>
Note the following:
If the Portal URL is
itanalyticsportal.<yourdomain>, then ensure to add the DNS entries for the following hostnames:itanalyticsagent.<yourdomain>
If the \ URL is
aptareportal.<yourdomain>, then ensure to add the DNS entries for the following hostnames:aptareagent.<yourdomain>
- Collect
<your-collector-name>.keyfile for the new Data Collector by accessing the Portal link and creating a collector and copy it to the host machine from where Kubernetes cluster is accessed.For more information, see Data Collector Encryption section in NetBackup IT Analytics User Guide.
- Copy the
<your-collector-name>.keyfile to/mnt/nbdata/analyticscollectorinside hte NBU Primary pod using the command kubectl cp <keyfile-name> <namespace>/<primary-pod-name>:/mnt/nbdata/analyticscollector. - In case if the data-receiver is configured with self-signed certificate (https). User must add the certificate in the Data Collector.
- Execute the following command on the primary server pod:
kubectl exec -it -n <namespace> <primaryServer-pod-name> -- bash
- Navigate to
/usr/openv/analyticscollector/installer/location and perform the following:Open the
responsefile.sampleand add the following parameters:COLLECTOR_NAME=name_of_the_data_collector COLLECTOR_PASSCODE=passcode_for_the_data_collector DR_URL=data_receiver_URL COLLECTOR_KEY_PATH=path_to_the_key_file HTTP_PROXY_CONF=N HTTP_PROXY_ADDRESS= HTTP_PROXY_PORT= HTTPS_PROXY_ADDRESS= HTTPS_PROXY_PORT= PROXY_USERNAME= PROXY_PASSWORD= PROXY_EXCLUDE=
Run /usr/openv/analyticscollector/installer/dc_installer.sh -c /usr/openv/analyticscollector/installer/responsefile.sample command to configure Data Collector with IT Analytics portal.
- Validate Data Collector integration with IT Analytics by performing the following:
Navigate to /usr/openv/analyticscollector/mbs/bin/ location.
Run the following command:
./checkinstall.sh
If Data Collector is configured with portal, it will display as SUCCESSFUL.
Note:
If there is a version mismatch of
aptare.jarbetween Data Collector and Portal, execution of checkinstall.sh command will trigger an auto-update of the Data Collector. - Check the Data Collector services status by running the following command and ensure that the following Data Collector services are up and running:
/usr/openv/analyticscollector/mbs/bin/aptare_agent status
Output of the above command:
IT Analytics WatchDog is running (pid: 13312). IT Analytics MetaDataCollector is stopped. IT Analytics EventDataCollector is stopped. IT Analytics DataCollector process is running (pid: 13461). IT Analytics On-demand process is running (pid: 13463). IT Analytics Message Relay Server process is running (pid: 13471)
For more information about IT Analytics Data Collector policy, see NetBackup IT Analytics User Guide.
NetBackup IT Analytics can be configured to use with NetBackup primary server in this Kubernetes environment.NetBackup IT Analyticscan be configured at the time of primary server deployment or user can update the primary server custom resource to configure NetBackup IT Analytics.
To configure NetBackup IT Analytics for NetBackup deployment
- Using the ssh-keygen command, generates public key and private key on NetBackup IT Analytics Data Collector.
NetBackup IT Analytics Data Collector uses passwordless ssh login.
- Update the primary server custom resource, copy public key generated in previous steps to "itAnalyticsPublicKey" section.
Apply the primary server custom resource changes using kubectl apply -f environment.yaml -n <namespace>.
On successfully deployment of primary server, describe the primary server custom resource using kubectl describe PrimaryServer <primary-server-name> -n <namespace>
In the Status section, verify IT Analytics Configured is set to true.
For more information, refer to the NetBackup™ Web UI Administrator's Guide.
- Create and copy NetBackup API key from NetBackup web UI.
- On NetBackup IT Analytics Portal:
Navigate to Admin > Collector Administration > Select respective Data Collector > Add policy > Veritas NetBackup > Add.
Add required options, specify the NetBackup API in the API Key field, and then click OK.
Select newly added primary server from NetBackup Primary Servers and provide nbitanalyticsadmin as Primary Server User ID.
Provide privateKey=<path-of-private-key>|password=<passphrase> as Primary Server Password and Repeat Password whereas <path-of-private-key> is the private key created using ssh-keygen in earlier steps and <passphrase> is the passphrase used while creating private key via ssh-keygen.
Provide appropriate data to Data Collector policy fields and select collection method as SSH or WMI protocol to NetBackup Primary Server.
Configuring the primary server with NetBackup IT Analytics tools is supported only once from primary server custom resource.
For more information about NetBackup IT Analytics Data Collector policy, see Add a Veritas NetBackup Data Collector policy section.
For more information about adding NetBackup Primary Servers within the Data Collector policy, see Add/Edit NetBackup Primary Servers within the Data Collector policy section in NetBackup IT Analytics Data Collector Installation Guide for Backup Manager.
To change the already configured public key
- Execute the following command in the primary server pod:
kubectl exec -it -n <namespace> <primaryServer-pod-name> -- /bin/bash
- Copy the new public keys in the
/home/nbitanalyticsadmin/.ssh/authorized_keysand/mnt/nbdata/.ssh/nbitanalyticsadmin_keysfiles. - Restart the sshd service using the systemctl restart sshd command.