NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
- Introduction to NetBackup on EKS
- Deployment with environment operators
- Assessing cluster configuration before deployment
- Deploying NetBackup
- Preparing the environment for NetBackup installation on EKS
- Recommendations of NetBackup deployment on EKS
- Limitations of NetBackup deployment on EKS
- 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 group 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 EKS
- 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
- Resolving the primary server connection issue
- Primary pod is in pending state for a long duration
- 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
- Wrong EFS ID is provided in environment.yaml file
- Primary pod is in ContainerCreating state
- Webhook displays an error for PV not found
- Appendix A. CR template
Primary pod is in ContainerCreating state
Primary pod is in ContainerCreating state for a long period due to the following reasons:
Wrong EFS ID
Format of the EFS ID is incorrect
To resolve this issue, perform the following:
- Describe primary pod using the following command:
kubectl describe <name of primary server pod> -n <namespace>
- Depending on the following appropriate scenario, fix the error from the output under the Event section:
If the event log has an error related to incorrect EFS ID or incorrect format, then update the
environment.yamlfile with the correct EFS ID and perform the below steps.Or
If the event log has an error other than the error related to incorrect EFS ID, then analyze and fix the error and perform the below steps.
- After fixing the error, clean the environment using the following command:
kubectl delete -k operator/
- Delete PV and PVC created for primary server only by using the following command:
Kubectl get pvc -n <namespace>
Describe the PVC for primary server which has the following format and obtain the corresponding PV name:
catalog-<resource name prefix of primary>-primary-0 data-<resource name prefix of primary>-primary-0 logs-<resource name prefix of primary>-primary-0
Delete PVC and PV names using the following commands: For PVC: kubectl delete pvc <pvc name> -n <namespace> For PV: kubectl delete pv <pv name>
PVC: kubectl delete pvc <pvc name> -n <namespace>
PV: kubectl delete pv <pv name>
- Deploy NetBackup operator again and then apply the
environment.yamlfile.