Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2023-10-23
Product(s):
NetBackup & Alta Data Protection (10.3.0.1, 10.3)
- 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
- Verifying Cloud Scale deployment
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Managing PostrgreSQL DBaaS
- Performing catalog backup and recovery
- Setting key parameters in Cloud Scale deployments
- Section III. Maintenance
- MSDP Scaleout Maintenance
- PostgreSQL DBaaS 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 token issues
Media server installation log displays the following error in /mnt/nblogs/setup-server.logs:
nbcertcmd: The -getCertificate operation failed for server <primaryServerName>, EXIT STATUS 5940: Reissue token is mandatory, please provide a reissue token
NetBackup media server and NetBackup primary server were in running state. Media server persistent volume claim or media server pod is deleted. In this case, reinstallation of respective media server can cause the issue.
To resolve token issues
- Open the NetBackup web UI using primary server hostname given in the primary server CR status.
- Navigate to Security > Host Mappings.
- Click Actions > Allow auto reissue certificate for the respective media server name.
- Pause the media server reconciler by setting the value as paused: true in mediaServer section in environment CR using the following command:
kubectl edit environment <environment-name> -n <namespace>
Save the changes.
- Delete the media server statefulset using the following command:
kubectl delete sts --cascade=orphan <statefulsetName>
- Delete respective media server pod using kubectl delete <pod-name> -n <namespace> command.
- Delete data and logs PVC for respective media server only using the kubectl delete pvc <pvc-name> -n <namespace> command.
- Un pause the media server reconciler by changing the value as paused: false in mediaServer section in environment CR using the following command:
kubectl edit environment <environment-name> -n <namespace>
Save the changes.