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 Cloud Scale
To install NetBackup using Helm charts on Kubernetes cluster, perform the following:
- Download the NetBackup TAR package from Veritas download centre which contains the container images and the Helm chart for NetBackup Kubernetes application.
- Create NetBackup namespace by using the following command:
kubectl create ns netbackup - Install cert-manager and trust-manager as follows:
Install cert-manager by using the following command:
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.13.3/cert-manager.yaml
For details, see cert-manager Documentation.
Install trust-manager by using the following command:
helm repo add jetstack https://charts.jetstack.io --force-update
kubectl create namespace trust-manager
helm upgrade -i -n trust-manager trust-manager jetstack/trust-manager --set app.trust.namespace=netbackup --version v0.7.0 --wait
- Deploy the operators. For more information on deploying the operators, refer to the following section:
- Deploy the PostgreSQL database. For more information on deploying the PostgreSQL database, refer to the following section:
See Deploying Postgres.
- Perform the following steps to deploy the
environment.yamlfile:Use the following command to save the environment chart values to a file:
helm show values environment-10.4.tgz > environment-values.yaml
Edit the chart values to fit the required environment:
vi environment-values.yaml
Generate the
environment.yamlfile as follows:helm template environment-10.4.tgz -f environment-values.yaml > environment.yaml
Use the following command to apply the
environment.yamlfile:kubectl apply -n netbackup -f environment.yaml
For example,
helm show values environment-10.4.tgz > environment-values.yaml $ $ vi environment-values.yaml $ $ helm template environment-10.4.tgz -f environment-values.yaml > environment.yaml $ $ kubectl apply -n netbackup -f environment.yaml secret/primary-credential-secret created secret/kms-secret created secret/example-key-secret created secret/msdp-secret1 created bundle.trust.cert-manager.io/db-cert created environment.netbackup.veritas.com/<userName>-nb created