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
Upgrading Snapshot Manager
Edit the
field in the CR to upgrade Snapshot Manager using environment CR. MODIFY event will be sent to Snapshot Manager operator which will trigger upgrade workflow.To upgrade Snapshot Manager
- Update the variables appropriately:
NB_VERSION=10.1.0 OPERATOR_NAMESPACE="netbackup-operator-system" ENVIRONMENT_NAMESPACE="ns-155" NB_DIR=/home/azureuser/VRTSk8s-netbackup-${NB_VERSION}/
- Edit the
operator/kustomization.yaml
file as follows:KUSTOMIZE_FILE=${NB_DIR}operator/kustomization.yaml nano $KUSTOMIZE_FILE
Update the newName and newTag under
cloudpointoperator
. - Upgrade the operator using the following command:
cd $NB_DIR kubectl apply -k operator sleep 20s
- Check (Wait for) if the operator is upgraded and running:
kubectl describe pod $(kubectl get pods -n $OPERATOR_NAMESPACE | grep flexsnap-operator | awk '{printf $1" " }') | grep Image: kubectl get all -n $OPERATOR_NAMESPACE
- Once the operator is upgraded successfully and it is running, update the cpServer.tag in
environment.yaml
file as follows:nano ${NB_DIR}environment.yaml
- Apply
environment.yaml
file to start upgrading Snapshot Manager services using the following command:kubectl apply -f ${NB_DIR}environment.yaml -n $ENVIRONMENT_NAMESPACE
- Check upgrade logs in flexsnap-operator using the following command:
kubectl logs -f $(kubectl get pods -n $OPERATOR_NAMESPACE | grep flexsnap-operator | awk '{printf $1" " }')
- Check Snapshot Manager status using the following command:
kubectl get cpserver -n $ENVIRONMENT_NAMESPACE