NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Preparing the environment for NetBackup installation on Kubernetes cluster
- Recommendations of NetBackup deployment on Kubernetes cluster
- Limitations of NetBackup deployment on Kubernetes cluster
- Primary and media server CR
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the cloud node for primary or media servers
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying MSDP Scaleout
- Prerequisites for AKS
- Prerequisites for EKS
- Installing the docker images and binaries
- Initializing the MSDP operator
- Configuring MSDP Scaleout
- Using MSDP Scaleout as a single storage pool in NetBackup
- Configuring the MSDP cloud in MSDP Scaleout
- Using S3 service in MSDP Scaleout for AKS
- Enabling MSDP S3 service after MSDP Scaleout is deployed for AKS
- 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
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- 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
- 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
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Using S3 service in MSDP Scaleout for AKS
Ensure that S3 credential secret field is updated in the environment YAML file or MSDP Scaleout CR YAML file.
See Enabling MSDP S3 service after MSDP Scaleout is deployed for AKS.
To use S3 service in MSDP Scaleout
- Check S3 service status.
Run the following command to check if S3 service is configured or not:
$ kubectl get msdpscaleouts.msdp.veritas.com/<MSDP Scaleout CR name> -n <sample-namespace> -o=jsonpath={.status.s3srvConfigured}
If the command output is true, S3 service is configured and ready for use. Otherwise wait for the flag to be true. The flag changes to true automatically after all MSDP Scaleout resources are ready.
- Restart S3 service in the first MSDP engine.
Use the following command to restart pdde-s3srv service in the first MSDP engine.
$ kubectl exec <first-MSDP-engine-FQDN> -n <sample-namespace> -c uss-engine -- systemctl restart pdde-s3srv
- Use the following URL to access S3 service in MSDP Scaleout:
https://<first-MSDP-engine-FQDN>:8443
Limitations:
S3 service in MSDP Scaleout only supports NBCA certificates.
You can use the CA certificate in NetBackup's primary server (the CA certificate file path is /usr/openv/var/webtruststore/cacert.pem) to bypass SSL warnings when accessing S3 service.
For example, when using AWS CLI you can use - ca-bundle parameter to specify CA certificate file path to bypass SSL warnings.
The region name of MSDP S3 service is the LSU name that is used to store S3 data. Set the default region name to PureDiskVolume to use the MSDP local LSU to store the S3 data.
The access point of S3 service is at the first MSDP Scaleout engine. If the first engine is down, S3 service is unavailable until MSDP Scaleout operator restarts it.
The S3 service process s3srv resides in the engines when S3 service is being configured. If more engines are added after S3 service is configured, the process s3srv does not run on new added engines.
If you have configured Disaster Recovery for cloud LSU and enabled S3 service, the IAM users in the cloud LSU need to be recreated using the S3 root user.