Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2024-06-17
Product(s):
NetBackup & Alta Data Protection (10.4.0.1)
- 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
Reinstalling MSDP Scaleout operator
When you undeploy MSDP Scaleout operator, the MSDP Scaleout CRD is removed from the cluster. It also deletes all the existing MSDP Scaleout on the cluster. The PVC for the operator logs is also deleted. However, the MSDP Scaleout critical data and metadata is not deleted.
To reinstall MSDP Scaleout operator
- Run the following command to delete the MSDP Scaleout operator:
kubectl msdp delete [-k] [-n <sample-operator-namespace>]
- Run the following command to redeploy the operator.
# helm upgrade --install operators operators-<version>.tgz \ --create-namespace \ --namespace netbackup-operator-system \ --set global.platform=${platform} \ --set global.operatorNamespace=netbackup-operator-system \ --set global.containerRegistry="$REGISTRY" \ --set global.storage.eks.fileSystemId=${EFS_ID} \ --set msdp-operator.image.name="$MSDP_OPERATOR_IMAGE_NAME" \ --set msdp-operator.image.tag="$MSDP_OPERATOR_IMAGE_TAG" \ --set msdp-operator.storageClass.name=nb-disk-standardssd \ --set msdp-operator.storageClass.size=5Gi \ --set msdp-operator.logging.debug=false \ --set msdp-operator.logging.age=28 \ --set msdp-operator.logging.num=20 \ --set msdp-operator.nodeSelector."${MSDP_NODE_SELECTOR_KEY//./\\.}"="${MSDP_NODE_SELECTOR_VALUE}" \ --set nb-operator.image.name="$OPERATOR_IMAGE_NAME" \ --set nb-operator.image.tag="$OPERATOR_IMAGE_TAG" \ --set nb-operator.loglevel.value="0" \ --set nb-operator.nodeSelector.node_selector_key="$MEDIA_NODE_SELECTOR_KEY" \ --set nb-operator.nodeSelector.node_selector_value="$MEDIA_NODE_SELECTOR_VALUE" \ --set flexsnap-operator.image.name="$FLEXSNAP_OPERATOR_IMAGE_NAME" \ --set flexsnap-operator.image.tag="$FLEXSNAP_OPERATOR_IMAGE_TAG" \ --set flexsnap-operator.nodeSelector.node_selector_key="$MEDIA_NODE_SELECTOR_KEY" \ --set flexsnap-operator.nodeSelector.node_selector_value="$MEDIA_NODE_SELECTOR_VALUE"
- If the reclaim policy of the storage class is Retain, run the following command to restart the existing MSDP Scaleout. MSDP Scaleout starts with the existing data/metadata.
kubectl apply -f <your-cr-yaml>