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
Monitoring with Azure Container insights
You can use Azure Container insights to collect Prometheus metrics to monitor pods in MSDP Scaleout.
To configure Azure Container insights
- Enable Azure Container insights.
See Azure documentation.
- Download the template ConfigMap YAML file and save it as
container-azm-ms-agentconfig.yaml. - Add the YAML file with the following sample configuration:
prometheus-data-collection-settings: |- [prometheus_data_collection_settings.cluster] interval = "1m" fieldpass = ["msdpoperator_reconcile_total", "msdpoperator_reconcile_failed", "msdpoperator_operator_run", "msdpoperator_diskFreeLess5GBEngines_total", "msdpoperator_diskFreeMiBytesInEngine", "msdpoperator_diskFreeLess10GBClusters_total", "msdpoperator_totalDiskFreePercentInCluster", "msdpoperator_diskFreePercentInEngine", "msdpoperator_pvcFreePercentInCluster", "msdpoperator_unhealthyEngines_total", "msdpoperator_createdPods_total"] monitor_kubernetes_pods = true # Add the namespace of MSDP operator in the follow list. It's "msdp-operator-system" by default. monitor_kubernetes_pods_namespaces = ["msdp-operator-system"]Table: Supported Prometheus metrics list in MSDP Scaleout lists the Prometheus metrics that MSDP Scaleout supports.
- Apply the ConfigMap.
kubectl apply -f container-azm-ms-agentconfig.yaml
The configuration change takes a few minutes and all omsagent pods in the cluster restart.
The default namespace of prometheus metrics is prometheus.
- Add alert rules for the integrated metrics.
Add related log query, add new alert rule for the selected query, and alert group/action for it.
For example,
If the free space size of the MSDP Scaleout engines is lower than 1 GB in past 5 minutes, alert the users.
Log query:
InsightsMetrics | where Name == "msdpoperator_diskFreeMiBytesInEngine" | where Namespace == "prometheus" | where TimeGenerated > ago(5m) | where Val <= 1000000 | where Val > 0
If multiple MSDP Scaleouts are deployed in the same AKS cluster, use the filter to search the results. For example, search the MSDP engines with the free space size lower than 1GB in the namespace sample-cr-namespace
Log query:
InsightsMetrics | where Name == "msdpoperator_diskFreeMiBytesInEngine" | where Namespace == "prometheus" | where TimeGenerated > ago(5m) | where Val <= 1000000 | where Val > 0 | extend Tags = parse_json(Tags) | where Tags.msdpscalout_ns == "sample-cr-namespace"
MSDP Scaleout supports the following Prometheus metrics:
Table: Supported Prometheus metrics list in MSDP Scaleout
Metrics | Type | Filters | Description |
|---|---|---|---|
msdpoperator_reconcile_total | Counter | N/A | The total of the reconcile loops msdp-operator run. |
msdpoperator_reconcile_failed | Counter | N/A | The total of the reconcile loops msdp-operator failed to run. |
msdpoperator_operator_run | Counter | N/A | The total of the running operator. |
msdpoperator_diskFreeLess5GBEngines_total | Gauge | InsightsMetrics.Tags.msdpscalout_ns | The checked number of the engines which have free spaces lower than 5GB. |
msdpoperator_diskFreeMiBytesInEngine | Gauge | InsightsMetrics.Tags.msdpscalout_ns | The free space of current engine in MiBytes. |
msdpoperator_diskFreeLess10GBClusters_total | Gauge | InsightsMetrics.Tags.msdpscalout_ns | The checked number of the msdpscaleout apps which have free spaces lower than 10GB. |
msdpoperator_totalDiskFreePercentInCluster | Gauge | InsightsMetrics.Tags.msdpscalout_ns | The percent of the msdpscaleout apps that have free spaces. For example, 0.95 means 95% |
msdpoperator_diskFreePercentInEngine | Gauge | InsightsMetrics.Tags.msdpscalout_ns | The percent of the current engines, which have free spaces. |
msdpoperator_pvcFreePercentInCluster | Gauge | InsightsMetrics.Tags.msdpscalout_ns, InsightsMetrics.Tags.component | The percent of the used PVC, which have free spaces. |
msdpoperator_unhealthyEngines_total | Gauge | InsightsMetrics.Tags.msdpscalout_ns | The total of unhealthy engines. |
msdpoperator_createdPods_total | Gauge | InsightsMetrics.Tags.msdpscalout_ns, InsightsMetrics.Tags.component | The total of created msdpscaleout pods. |