Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
Last Published:
2022-12-19
Product(s):
NetBackup (10.1.1)
- 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
Preparing for NetBackup upgrade
Note:
Ensure that you go through this section carefully before starting with the upgrade procedure.
During upgrade, ensure that the following sequence of upgrade is followed:
Upgrade MSDP operator
Upgrade NetBackup operator
Upgrade NetBackup application
In case the above sequence is not followed, user may face data loss.
Preparing for NetBackup upgrade
- Take a backup of all the NetBackup jobs and ensure that all the jobs are suspended.
- Take a catalog backup.
See Backing up a catalog.
- Copy DRPackages files (packages) located at
/mnt/nblogs/DRPackages/from the pod to the host machine from where EKS cluster is accessed.Run the following command:
kubectl cp <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages <Path_where_to_copy_on_host_machine>
- Preserve the data of
/mnt/nbdata and /mnt/nblogson host machine by creating tar and copying it using the following command:kubectl cp <primary-pod-namespace>/<primary-pod-name>:<tar_file_name> <path_on_host_machine_where_to_preserve_the_data>
- Preserve the environment CR object using the following command and operator directory that is used to deploy the NetBackup operator:
kubectl -n <namespace> get environment.netbackup.veritas.com <environment name> -o yaml > environment.yaml
Note:
Ensure that you upgrade MSDP operator first.
- In case of existing NetBackup deployments with EBS, change the storage class for catalog data of primary server to trigger data migration. For more information on changing the storage class, refer to the following section: