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 fluentbit
- Monitoring MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Managing fluentbit
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- Section IV. Maintenance
- MSDP Scaleout Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for primary, media servers, fluentbit pods, and postgres pods
- Upgrading
- Cloud Scale Disaster Recovery
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- 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 Center which contains the container images and the Helm chart for NetBackup Kubernetes application.
- Install cert-manager by using the following command:
helm repo add jetstack https://charts.jetstack.io --force-update
helm upgrade -i -n cert-manager cert-manager jetstack/cert-manager \ --version 1.13.3 \ --set webhook.timeoutSeconds=30 \ --set installCRDs=true \ --wait --create-namespace
For details, see cert-manager Documentation.
- Create NetBackup namespace by using the following command:
kubectl create ns netbackup
- Install trust-manager by using the following command:
kubectl create namespace trust-manager
helm upgrade -i --create-namespace --namespace trust-manager trust-manager jetstack/trust-manager --set app.trust.namespace=netbackup --version v0.7.0 --wait
For details, see trust-manager Documentation.
- Deploy the operators. For more information on deploying the operators, refer to the following section:
- Deploy the fluentbit. For more information on deploying the fluentbit for logging strategy, 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.yaml
file:Use the following command to save the environment chart values to a file:
helm show values environment-10.5.tgz > environment-values.yaml
Edit the chart values to fit the required environment:
vi environment-values.yaml
Generate the
environment.yaml
file as follows:helm template environment-10.5.tgz -f environment-values.yaml > environment.yaml
Use the following command to apply the
environment.yaml
file:kubectl apply -n netbackup -f environment.yaml
For example,
helm show values environment-10.5.tgz > environment-values.yaml $ $ vi environment-values.yaml $ $ helm template environment-10.5.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
Note:
By default, Helm stores the input values in a Kubernetes secret. Hence to avoid the values being discovered by anyone, customers must reset the database password after Cloud Scale deployment.