NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Primary and media server CR
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Resolving an invalid license key issue
The NetBackup is not installed because the license key is invalid.
Pod remains in running state for long time and the installation log at /mnt/nblogs/setup-server.log
displays the following error:
ERROR: No valid license key for NetBackup Server or Enterprise Server
When you deploy NetBackup for the first time, perform the steps for primary CR and media CR.
To resolve an invalid license key issue for Primary CR
- Get the configmap name created for primary CR or media CR using the following command:
kubectl get configmap -n <namespace>
- Edit the license key stored in configmap using the following command:
kubectl edit configmap <primary-configmap-name> -n <namespace>
- Update value for ENV_NB_LICKEY key in the configmap with correct license key and save.
- Delete respective primary/media pod using the following command:
kubectl delete pod <primary-pod-name> -n <namespace>
New pod is auto created with updated license key value.
- Edit environment CR with updated license key and save using the following command:
kubectl edit environments.netbackup.veritas.com -n <namespace>
To resolve an invalid license key issue for Media CR
- Delete the media server CR by removing the mediaServer section in
environment.yaml
and save the changes.Note:
Ensure that you copy spec information of the media server CR. The spec information is used to reapply the media server CR.
- Apply the new changes using the kubectl apply -f <environment.yaml> command.
- Delete respective persistent volume claim using the kubectl delete pvc <pvc_name> -n <namespace> command. Any available persisted data is deleted.
- Add the mediaServer section, update the license key, and reapply the
environment.yaml
using the kubectl apply -f <environment.yaml> command.