Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2024-10-04
Product(s):
NetBackup (10.5)
- Introduction
- Section I. Configurations
- Prerequisites
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Tuning touch files
- Setting maximum jobs per client
- Setting maximum jobs per media server
- Enabling intelligent catalog archiving
- Enabling security settings
- Configuring email server
- Reducing catalog storage management
- Configuring zone redundancy
- Enabling client-side deduplication capabilities
- Parameters for logging strategy (fluentbit)
- 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
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Socket connection failure
- Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
- Resolving the issue where the NetBackup server pod is not scheduled for long time
- Resolving an issue where the Storage class does not exist
- Resolving an issue where the primary server or media server deployment does not proceed
- Resolving an issue of failed probes
- Resolving token issues
- Resolving an issue related to insufficient storage
- Resolving an issue related to invalid nodepool
- Resolving a token expiry issue
- Resolve an issue related to KMS database
- Resolve an issue related to pulling an image from the container registry
- Resolving an issue related to recovery of data
- Check primary server status
- Pod status field shows as pending
- Ensure that the container is running the patched image
- Getting EEB information from an image, a running container, or persistent data
- Resolving the certificate error issue in NetBackup operator pod logs
- Pod restart failure due to liveness probe time-out
- NetBackup messaging queue broker take more time to start
- Host mapping conflict in NetBackup
- Issue with capacity licensing reporting which takes longer time
- Local connection is getting treated as insecure connection
- Primary pod is in pending state for a long duration
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Storage server not supporting Instant Access capability on Web UI after upgrading NetBackup
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Elastic media server related issues
- Failed to register Snapshot Manager with NetBackup
- Post Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods were unable to connect to flexsnap-rabbitmq
- Post Kubernetes cluster restart, issues observed in case of containerized Postgres deployment
- Request router logs
- Issues with NBPEM/NBJM
- Issues with logging strategy for Cloud Scale
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting issue for bootstrapper pod
- 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
- Navigate to cd $NB_DIR/bin directory.
where NB_DIR is the directory where the tar file has been unzipped.
Run the following command to delete the MSDP Scaleout operator:
./kubectl-msdp delete -n netbackup-operator-system
-n: Namespace scope for this request.
- 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>