Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2023-04-24
Product(s):
NetBackup (10.2)
- 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 issue related to insufficient storage
Setup-server.logs of NetBackup primary server displays an error.
Insufficient storage on the node can cause this issue. Minimum hardware requirements for NetBackup may not be completed. During fresh deployment of primary server, the following error is displayed in /mnt/nblogs/setup-server.logs
:
DBSPAWN ERROR: -86 Not enough memory to start
To resolve an issue related to insufficient storage
- Create a new nodepool with the hardware specifications as mentioned in the NetBackup Deployment Guide for Kubernetes Clusters Administrator's Guide.
- Run the kubectl get nodes command to ensure that the nodes from the newly created nodepool are used in your cluster.
- Delete the primary server CR using the kubectl delete -f <environment.yaml> command.
- Update nodeSelector spec in primary section and apply the
environment.yaml
again using the kubectl apply -f <environment.yaml> command.