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
Installing the docker images
The Snapshot Manager package netbackup-flexsnap-$(SNAPSHOT_MANAGER_VERSION).tar.gz for Kubernetes includes the following:
A docker image for Snapshot Manager operator
8 docker images for Snapshot Manager: flexsnap-certauth, flexsnap-rabbitmq, flexsnap-fluentd, flexsnap-datamover, flexsnap-nginx, flexsnap-mongodb, flexsnap-core, flexsnap-deploy
To install the docker images
- Download
netbackup-flexsnap-$(SNAPSHOT_MANAGER_VERSION).tar.gzfrom the Veritas site. - Load the docker images to your docker storage.
docker load -i netbackup-flexsnap-$(SNAPSHOT_MANAGER_VERSION).tar.gz
- Tag the images.
$ docker tag veritas/flexsnap-fluentd:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-fluentd:${SNAPSHOT_MANAGER_VERSION}
$ docker tag veritas/flexsnap-datamover:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-datamover:${SNAPSHOT_MANAGER_VERSION}
$ docker tag veritas/flexsnap-nginx:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-nginx:${SNAPSHOT_MANAGER_VERSION}
$ docker tag veritas/flexsnap-mongodb:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-mongodb:${SNAPSHOT_MANAGER_VERSION}
$ docker tag veritas/flexsnap-core:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-core:${SNAPSHOT_MANAGER_VERSION}
$ docker tag veritas/flexsnap-deploy:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-deploy:${SNAPSHOT_MANAGER_VERSION}
$ docker tag veritas/flexsnap-certauth:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-certauth:${SNAPSHOT_MANAGER_VERSION}
$ docker tag veritas/flexsnap-rabbitmq:${SNAPSHOT_MANAGER_VERSION} ${REGISTRY}/veritas/flexsnap-rabbitmq:${SNAPSHOT_MANAGER_VERSION}
Note:
Ensure that you use the same tag as that of Snapshot Manager image version. Custom tag cannot be used.
- Push the images.
$ docker push ${REGISTRY}/veritas/flexsnap-certauth:${SNAPSHOT_MANAGER_VERSION}
$ docker push ${REGISTRY}/veritas/flexsnap-rabbitmq:${SNAPSHOT_MANAGER_VERSION}
$ docker push ${REGISTRY}/veritas/flexsnap-fluentd:${SNAPSHOT_MANAGER_VERSION}
$ docker push ${REGISTRY}/veritas/flexsnap-datamover:${SNAPSHOT_MANAGER_VERSION}
$ docker push ${REGISTRY}/veritas/flexsnap-nginx:${SNAPSHOT_MANAGER_VERSION}
$ docker push ${REGISTRY}/veritas/flexsnap-mongodb:${SNAPSHOT_MANAGER_VERSION}
$ docker push ${REGISTRY}/veritas/flexsnap-core:${SNAPSHOT_MANAGER_VERSION}
$ docker push ${REGISTRY}/veritas/flexsnap-deploy:${SNAPSHOT_MANAGER_VERSION}
Configure Snapshot Manager
After you push the docker images to Amazon Elastic container registry, then initialize Snapshot Manager (flexsnap) operator and configure Snapshot Manager. The Snapshot Manager operator starts with NetBackup operator. For more information, refer to the following section:
Configure Snapshot Manager
- Use existing dedicated namespace for Snapshot Manager to run:
kubectl create ns <sample-namespace>
- Create a Snapshot Manager Secret. The Secret is used in CR.
kubectl create secret generic cp-creds --from-literal=username='admin' --from-literal=password='Cloudpoint@123' -n $ENVIRONMENT_NAMESPACE
- Edit the cpServer CR section of the
environment.yamlfile in the text editor. - Apply the CR file to the EKS cluster:
kubectl apply -f <sample-cr-yaml>
- Monitor the configuration process:
kubectl get all -n <namespace> -o wide
- Verify the status by running the following command:
kubectl get cpservers -n <sample-namespace>
Note:
If Snapshot Manager is uninstalled and installed again with same NetBackup primary server, then generate reissue token and edit the Snapshot Manager after enabling it.
Reissue token
- Login to NetBackup Web UI.
- Navigate to Security > Host Mappings.
- On the Host mappings page, identify the Snapshot Manager IP and select Action.
- Click on Generate reissue token.
- Provide a name for the reissue token, number of days for validation and click on Generate.
- Note down the generated token number.
- Navigate to Workloads > Cloud.
- Select Snapshot Manager tab and click on Action.
- Select Enable option and click on Edit.
- Click on Validate and Accept the certificate.
- Provide Username, Password, and Token (noted down in the above step) credentials and click on Save.
More Information