Deleting the CRs
If you must delete any of the CRs for a valid reason such as for the troubleshooting purpose, or because any of the specs provided were incorrect; you can reinstall the deleted CR after resolving the issues.
Note:
Once installed, deleting a CR is not recommended as it will stop the deployment and NetBackup will not work.
Notes:
Deleting a CR will delete all its child resources like pod, statefulset, services, configmaps, config checker job, config checker pod.
Deleting operator with kubectl delete -k <operator_folder_path> will delete the CRs and its resources except the PVC.
Persistent volume claim (PVC) will not be deleted upon deleting a CR so that the data is retained in the volumes. Then if you create a new CR with the same name as the deleted one, the existing PVC with that same name will be automatically linked to the newly created pods.
Do not delete
/mnt/nbdata,/mnt/nblogsand/mnt/nbdbfolders manually from primary server and media pods. The NetBackup deployment will go into an inconsistent state and will also result in data loss.