NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Section II. Deployment
- Section III. Monitoring and Management
- Monitoring NetBackup
- Monitoring Snapshot Manager
- Monitoring MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- Section IV. Maintenance
- MSDP Scaleout Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for Primary and Media servers
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Socket connection failure
- 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
- Pod restart failure due to liveness probe time-out
- NetBackup messaging queue broker take more time to start
- Host mapping conflict in NetBackup
- Issue with capacity licensing reporting which takes longer time
- Local connection is getting treated as insecure connection
- Primary pod is in pending state for a long duration
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Storage server not supporting Instant Access capability on Web UI after upgrading NetBackup
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Elastic media server related issues
- Failed to register Snapshot Manager with NetBackup
- Post Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods were unable to connect to flexsnap-rabbitmq
- Post Kubernetes cluster restart, issues observed in case of containerized Postgres deployment
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Installing the docker images for NetBackup
The NetBackup package VRTSk8s-netbackup-<version>.tar.gz for Kubernetes includes the following:
A docker image for NetBackup operator
3 docker images for NetBackup: operator, main, media and requestrouter
To install the docker images
- Download
VRTSk8s-netbackup-<version>.tar.gzfrom the Veritas site. - Run the following commands to load the docker images to the local docker instance:
$ docker load -i netbackup-main-<version>.tar.gz
$ docker load -i netbackup-media-<version>.tar.gz
$ docker load -i netbackup-operator-<version>.tar.gz
$ docker load -i netbackup-requestrouter-<version>.tar.gz
Run the command docker image ls command to confirm that the NetBackup images are loaded properly to the docker cache.
<version>: Represents the NetBackup product version.
- Run the following commands to re-tag the images to associate them with your container registry, keep the image name and version same as original:
(AKS-specific): $ REGISTRY=<example.azurecr.io> (Replace with your own container registry name)
(EKS-specific): $ REGISTRY=<<AccountID>.dkr.ecr.<region>.amazonaws.com
$ docker tag netbackup/main:<version> ${REGISTRY}/netbackup/main:<version>
$ docker tag netbackup/media:<version> ${REGISTRY}/netbackup/media:<version>
$ docker tag netbackup/operator:<version> ${REGISTRY}/netbackup/operator:<version>
$ docker tag netbackup/requestrouter:<version> ${REGISTRY}/netbackup/requestrouter:<version>
- (EKS-specific) Login using the following command:
docker login -u AWS -p $(aws ecr get-login-password --region <region-name>) <account-id>.dkr.ecr.<region-name>.amazonaws.com
If the repository is not created, then create the repository using the following command:
aws ecr create-repository --repository-name <image-name> --region <region-name>
For example, aws ecr create-repository --repository-name veritas/flexsnap-datamover --region us-east-2
- Run the following commands to push the images to the container registry:
$ docker push ${REGISTRY}/netbackup/main:<version>
$ docker push ${REGISTRY}/netbackup/media:<version>
$ docker push ${REGISTRY}/netbackup/operator:<version>
$ docker push {REGISTRY}/netbackup/requestrouter:<version>