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 MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- Section IV. Maintenance
- MSDP Scaleout Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for Primary and Media servers
- 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
Uninstalling NetBackup environment and the operators
You can uninstall the NetBackup primary, media, MSDP Scaleout environment, Snapshot Manager server and the operators as required. You need to uninstall the NetBackup environment before you uninstall the operators.
Note:
Replace the environment custom resource names as per your configuration in the steps below.
To uninstall the NetBackup environment
- To remove the environment components from the application namespace, run:
$ kubectl delete environment.netbackup.veritas.com/environment-sample --namespace <namespce_name>
- Wait for all the pods, services and resources to be terminated. To confirm, run
$ kubectl get --namespace <namespce_name> all,environments,primaryservers,mediaservers,msdpscaleouts,cpservers
You should get a message that no resources were found in the nb-example namespace.
- To identify and delete any outstanding persistent volume claims, run the following:
$ kubectl get pvc --namespace <namespace_name>
$ kubectl delete pvc <pvc-name>
To delete all PVCs under the same namespace, run the following command:
kubectl delete pvc -n <namespace> --all
- To locate and delete any persistent volumes created by the deployment, run:
$ kubectl get pv
$ kubectl delete pv <pv-name> --grace-period=0 --force
Note:
Certain storage drivers may cause physical volumes to get stuck in the terminating state. To resolve this issue, remove the finalizer, using the command: $ kubectl patch pv <pv-name> -p '{"metadata":{"finalizers":null}}
Note:
(EKS-specific) Navigate to mounted EFS directory and delete the content from
primary_catalog
folder by running the rm -rf /efs/ command. - To delete the application namespace, run:
$ kubectl delete ns <namespace name>
To uninstall the operators
- To uninstall the NetBackup operator using helm charts, run the following command from the installation directory.
helm uninstall -n netbackup-operator-system operators
- To uninstall the NetBackup operator and remove the operator's namespace, run the following command:
kubectl delete ns netbackup-operator-system
For more information on uninstalling the Snapshot Manager, refer to the following section:
More Information