Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2023-04-24
Product(s):
NetBackup (10.2)
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Primary and media server CR
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
The issue can be because of one of the following reasons:
The
mentioned in custom resource is not unique and valid.The static IP is provided in
section in CR but it is not created in Azure/AWS.The subnet or resource group is mentioned in annotations of
section in CR spec, the IP address is not available in given subnet or resource group.The RBAC permissions in your cluster for the given subnet or resource group are not assigned properly for allocating IP addresses.
To resolve an issue where external IP address is not assigned to a NetBackup server's load balancer services
- Check the event logs of load balancer service using the kubectl describe service <svc-name> -n <namespace> command for detailed error information.
- Run the kubectl edit Environment <environmentCR-name> -n <namespace> command.
- Depending on the output of the command and the reason for the issue, perform the required steps and update the environment CR to resolve the issue.