NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
- Introduction to NetBackup on AKS
- Deployment with environment operators
- Assessing cluster configuration before deployment
- Deploying NetBackup
- Preparing the environment for NetBackup installation on AKS
- Recommendations of NetBackup deployment on AKS
- Limitations of NetBackup deployment on AKS
- About primary server CR and media server CR
- Monitoring the status of the CRs
- Updating the CRs
- Deleting the CRs
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the node pool for primary or media servers
- Upgrading NetBackup
- Deploying Snapshot Manager
- Migration and upgrade of Snapshot Manager
- Deploying MSDP Scaleout
- Upgrading MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager deployment
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- Uninstalling Snapshot Manager
- Troubleshooting
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Pod restart failure due to liveness probe time-out
- Socket connection failure
- Resolving an invalid license key issue
- 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
- Data migration unsuccessful even after changing the storage class through the storage yaml file
- Host validation failed on the target host
- Primary pod is in pending state for a long duration
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Host mapping conflict in NetBackup
- NetBackup messaging queue broker take more time to start
- Local connection is getting treated as insecure connection
- Issue with capacity licensing reporting which takes longer time
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Primary pod goes in non-ready state
- Appendix A. CR template
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. |