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
Upgrade fluentbit
For more information on how to save and modify any values during upgrade, refer to the following section:
Parameters for logging (fluentbit)
Note the following
It is recommended to back up all logs before upgrading from NetBackup versions prior to 10.5 (versions prior to the unified fluentbit based logging).
It is recommended to copy and check the differences between the sample and the default
fluentbit-values.yamlfile.When upgrading from versions prior to 10.5 to NetBackup version 10.5 or later, the logs would be collected in the fluentbit collector from up to two days prior to the date of the upgrade.
When upgrading from NetBackup 10.5 or later, the logs that exist in the fluentbit collector from the previous release will remain in the fluentbit collector and would continue to be cleaned up as per the configured fluentbit collector cleanup policy.
Perform the following steps to install/upgrade fluentbit:
Use the following command to save the fluentbit chart values to a file:
helm show values fluentbit-<version>.tgz > fluentbit-values.yaml
Use the following command to edit the chart values:
vi fluentbit-values.yaml
Following is an example for
fluentbit-values.yamlfile:global: environmentNamespace: "netbackup" containerRegistry: "<EKS Container Registry Name>" timezone: null fluentbit: image: name: "netbackup/fluentbit" tag: 10.5-0036 pullPolicy: IfNotPresent volume: pvcStorage: "100Gi" storageClassName: nb-disk-premium metricsPort: 2020 cleanup: image: name: "netbackup/fluentbit-log-cleanup" tag: 10.5-0036 retentionDays: 7 retentionCleanupTime: '04:00' # Frequency in minutes utilizationCleanupFrequency: 60 # Storage % filled highWatermark: 90 lowWatermark: 60 # Collector node selector value collectorNodeSelector: node_selector_key: agentpool node_selector_value: nbupool # Toleraions Values (key=value:NoSchedule) tolerations: - key: agentpool value: nbupool - key: agentpool value: mediapool - key: agentpool value: primarypool - key: storage-pool value: storagepool - key: data-plane-pool value: dataplanepoolExecute the following command to upgrade the fluentbit deployment:
helm upgrade --install fluentbit fluentbit-<version>.tgz -f fluentbit-values.yaml -n netbackup
Or
If using the OCI container registry, use the following command:
helm install --upgrade fluentbit oci://abcd.veritas.com:5000/helm-charts/fluentbit --version <version> -f fluentbit-values.yaml -n netbackup