NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Tuning touch files
- Setting maximum jobs per client
- Setting maximum jobs per media server
- Enabling intelligent catalog archiving
- Enabling security settings
- Configuring email server
- Reducing catalog storage management
- Configuring zone redundancy
- Enabling client-side deduplication capabilities
- Parameters for logging (fluentbit)
- Section II. Deployment
- Section III. Monitoring and Management
- Monitoring NetBackup
- Monitoring Snapshot Manager
- Monitoring fluentbit
- Monitoring MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Managing fluentbit
- Performing catalog backup and recovery
- Section IV. Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for primary, media servers, fluentbit pods, and postgres pods
- Upgrading
- Cloud Scale Disaster Recovery
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Socket connection failure
- Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
- Resolving the issue where the NetBackup server pod is not scheduled for long time
- Resolving an issue where the Storage class does not exist
- Resolving an issue where the primary server or media server deployment does not proceed
- Resolving an issue of failed probes
- Resolving token issues
- Resolving an issue related to insufficient storage
- Resolving an issue related to invalid nodepool
- Resolving a token expiry issue
- Resolve an issue related to KMS database
- Resolve an issue related to pulling an image from the container registry
- Resolving an issue related to recovery of data
- Check primary server status
- Pod status field shows as pending
- Ensure that the container is running the patched image
- Getting EEB information from an image, a running container, or persistent data
- Resolving the certificate error issue in NetBackup operator pod logs
- Pod restart failure due to liveness probe time-out
- NetBackup messaging queue broker take more time to start
- Host mapping conflict in NetBackup
- Issue with capacity licensing reporting which takes longer time
- Local connection is getting treated as insecure connection
- Primary pod is in pending state for a long duration
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Storage server not supporting Instant Access capability on Web UI after upgrading NetBackup
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Elastic media server related issues
- Failed to register Snapshot Manager with NetBackup
- Post Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods were unable to connect to flexsnap-rabbitmq
- Post Kubernetes cluster restart, issues observed in case of containerized Postgres deployment
- Request router logs
- Issues with NBPEM/NBJM
- Issues with logging feature for Cloud Scale
- The flexsnap-listener pod is unable to communicate with RabbitMQ
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting issue for bootstrapper pod
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
- Appendix B. MSDP Scaleout
- About MSDP Scaleout
- Prerequisites for MSDP Scaleout (AKS\EKS)
- Limitations in MSDP Scaleout
- MSDP Scaleout configuration
- Installing the docker images and binaries for MSDP Scaleout (without environment operators or Helm charts)
- Deploying MSDP Scaleout
- Managing MSDP Scaleout
- MSDP Scaleout maintenance
Configuring NetBackup IT Analytics for NetBackup deployment
We can configure data collector on the primary server pod or on a separate host machine. Following are the steps for respective configurations.
Note:
From NetBackup version 10.3 or later, Cloud Scale release data collector on primary server pod is supported.
Configure data collector on the primary server pod.
To configure NetBackup IT Analytics for NetBackup deployment
- Create DNS server entry in such a way that single IP must be resolvable to two FQDNs.
IP: 1.2.3.4 must be resolved to the following FQDNs:
itanalyticsportal.<yourdomain> itanalyticsagent.<yourdomain>
Note the following:
If the IT Analytics Portal URL is
itanalyticsportal.<yourdomain>, then ensure to add the DNS entries for the following hostnames:itanalyticsportal.<yourdomain> itanalyticsagent.<yourdomain>
If the IT Analytics Portal URL is
aptareportal.<yourdomain>, then ensure to add the DNS entries for the following hostnames:aptareportal.<yourdomain> aptareagent.<yourdomain>
- Collect the
<your-collector-name>.keyfile for the new data collector by accessing the IT Analytics portal link and creating a collector and copy it to the host machine from where Kubernetes cluster is accessed.For more information, refer to the NetBackup IT Analytics User Guide.
- Execute the following command in the primary server pod:
kubectl exec -it -n <namespace> <primaryServer-pod-name> -- bash
- In case if the data-receiver is configured with self-signed certificate (https). User must add the certificate in the data collector.
For more information, refer to the Configure the Data Collector to trust the certificate.
- Create a new folder analyticscollector at persisted location (for example,
/mnt/nbdata/) using the following commands:cd "/mnt/nbdata/" mkdir analyticscollector
- Exit from the container and copy the
<your-collector-name>.keyfile to/mnt/nbdata/analyticscollectorusing the kubectl cp <keyfile-name> <namespace>/<primary-pod-name>:/mnt/nbdata/analyticscollector command. - Execute the following command to exec into 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:Configuration for reference: NetBackup.docx COLLECTOR_NAME=<your-collector-name> COLLECTOR_PASSCODE=<your-password> DR_URL=<http>/<https>://itanalyticsagent.<yourdomain> COLLECTOR_KEY_PATH=/mnt/nbdata/analyticscollector/<your-collector-name>.key HTTP_PROXY_CONF=N HTTP_PROXY_ADDRESS= HTTP_PROXY_PORT= HTTPS_PROXY_ADDRESS= HTTPS_PROXY_PORT= PROXY_USERNAME= PROXY_PASSWORD= PROXY_EXCLUDE=
Run ./dc_installer.sh -c /usr/openv/analyticscollector/installer/responsefile.sample command to connect 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.
- 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.