NetBackup™ Deployment Guide for Kubernetes Clusters
- 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 (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
- Section IV. 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 feature for Cloud Scale
- The flexsnap-listener pod is unable to communicate with RabbitMQ
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting issue for bootstrapper pod
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
- Appendix B. MSDP Scaleout
- About MSDP Scaleout
- Prerequisites for MSDP Scaleout (AKS\EKS)
- Limitations in MSDP Scaleout
- MSDP Scaleout configuration
- Installing the docker images and binaries for MSDP Scaleout (without environment operators or Helm charts)
- Deploying MSDP Scaleout
- Managing MSDP Scaleout
- MSDP Scaleout maintenance
Steps to deploy Cloud Scale in single node
To deploy the Cloud Scale Technology on a single node in the Kubernetes cluster, perform the following steps:
Deploy operators: To deploy operators, perform points mentioned in step 1.
Deploy fluentbit: To deploy fluentbit, perform points mentioned in step 2.
Deploy postgresql: To deploy postgresql, perform points mentioned in step 3.
Deploy environment: To perform settings in the environment, check for points mentioned in step 4.
Steps for deployment
- In the
operators-values.yaml file, do the following changes:Set 'replicas' to 1 in
msdp-operator.Set value to
examplepoolfor everynode_selector_valuein the nodeSelector section.Set value to
agentpoolfor everynode_selector_keyin the nodeSelector section.To deploy the operators, refer to the section See Deploying the operators.
- In the
fluentbit, do the following:Set value to
examplepoolfornode_selector_valuein the collectorNodeSelector section.To deploy fluentbit, refer to the section See Deploying fluentbit for logging.
- In the postgresql, do the following:
Set value to examplepool for value in the nodeSelector section.
To deploy PostgreSQL database, refer to the section See Deploying Postgres.
- Do the following in the environment to deploy the Cloud Scale Technology:
Set value to examplepool for every node_selector_value and labelValue in the nodeSelector section.
Set value to "agentpool" for every
node_selector_keyandlabelKeyin the nodeSelector section.Set 'replicas' to 1 for
mediaServersandmsdpScaleoutssection.Add the section in the
msdpScaleoutssection:
resources: requests: cpu: 6000m memory: 16384Mi limits: cpu: 9000m memory: 16384Mi# save environment chart values to a file helm show values environment-10.5.tgz > environment-values.yaml # edit chart values to fit your environment vi environment-values.yaml # generate environment.yaml helm template environment-10.5.tgz -f environment-values.yaml > environment.yaml # apply environment.yaml kubectl apply -n netbackup -f environment.yaml