NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- 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
- Managing MSDP Scaleout
- Section IV. Maintenance
- MSDP Scaleout 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
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Expanding log volumes for primary pods
To optimize and reduce the log sizes of the PV's of the decoupled services, execute the following steps:
To reduce the log size of the PV
- Stop the primary pods:
Untar the .tar for the kubernetes package, and within the untar folder, navigate to
scripts/
.Navigate to the scripts folder inside the build folder (For example: VRTSk8s-netbackup-<version>/scripts).
Run the script
cloudscale_restart.sh
, with stop (as the input for action) and the netbackup namespace (for namespace parameter).For example: ./cloudscale_restart.sh stop <namespace> This script will pause the primary server CR and stop all the decoupled services.
- Manually delete the statefulsets:
After all the pods are scaled down, get the required list of statefulsets using the command:
kubectl get sts -n <netbackup_namespace> | grep -e "nbatd" -e "nbmqbroker" -e "nbwsapp" -e "policyjob" -e "policyjobmgr" -e "primary"
Delete the statefulsets using the command:
kubectl delete statefulset <statefulset_names_obtained_above> -n <netbackup_namespace>
- List the log PVCs for primary pods:
Execute the command:
kubectl get pvc -n <netbackup_namespace> | grep log | grep -ve "catalog" -ve "uss" -ve "media"
For example: kubectl get pvc -n netbackup | grep log | grep -ve "catalog" -ve "uss" -ve "media"
- Expand the log PVCs
Expand the capacities of the above obtained log PVCs using the command:
kubectl patch pvc <pvc_names_obtained_above> -n <netbackup_namespace> -p '{"spec":{"resources":{"requests":{"storage":"<Expanded_capacity>Gi"}}}}'
For example: kubectl patch pvc logs-nbu-primary-0 -n netbackup -p '{"spec":{"resources":{"requests":{"storage":"35Gi"}}}}'
- Expand log volume size in primary server CR
Execute the command: kubectl patch environment <environment_name> -n <netbackup_namespace> --type=json --patch '[{"op": "replace", "path": "/spec/primary/storage/log/capacity", "value": "<Expanded_capacity>Gi"}]'
For example: kubectl patch environment nbu -n netbackup --type=json --patch '[{"op": "replace", "path": "/spec/primary/storage/log/capacity", "value": "35Gi"}]'
- Start decoupled services using the
cloudscale_restart.sh
script:Navigate to the scripts folder inside the build folder (For example: VRTSk8s-netbackup-10.5-0053/scripts).
Run the script
cloudscale_restart.sh
with start (as the input for action) and the netbackup namespace (for namespace parameter).For example: ./cloudscale_restart.sh start <namespace>