NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Tuning touch files
- Setting maximum jobs per client
- Setting maximum jobs per media server
- Enabling intelligent catalog archiving
- Enabling security settings
- Configuring email server
- Reducing catalog storage management
- Configuring zone redundancy
- Enabling client-side deduplication capabilities
- Parameters for logging (fluentbit)
- 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
- Section IV. 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
- 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
- Request router logs
- Issues with NBPEM/NBJM
- Issues with logging feature for Cloud Scale
- The flexsnap-listener pod is unable to communicate with RabbitMQ
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting issue for bootstrapper pod
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
- Appendix B. MSDP Scaleout
- About MSDP Scaleout
- Prerequisites for MSDP Scaleout (AKS\EKS)
- Limitations in MSDP Scaleout
- MSDP Scaleout configuration
- Installing the docker images and binaries for MSDP Scaleout (without environment operators or Helm charts)
- Deploying MSDP Scaleout
- Managing MSDP Scaleout
- MSDP Scaleout maintenance
Enabling MSDP S3 service after MSDP Scaleout is deployed
If MSDP S3 service is not enabled during the initial deployment, you can enable it later.
Identify the MSDP Scaleout deployment method of your deployment. Some of the steps in this procedure differ based on the MSDP Scaleout deployment method.
MSDP Scaleout is deployed with environment YAML in the following scenarios:
NetBackup and MSDP are deployed together in the same cluster
Cloud Scale is deployment using the Terraform
Cloud Scale is deployment using the Maketplace
MSDP Scaleout is deployed with MSDP Scaleout YAML in the following scenarios:
NetBackup and MSDP are not deployed together in the same cluster
To enable MSDP S3 service
- Generate S3 root credential. Run the following command to generate the secret:
$ kubectl msdp generate-s3-secret --namespace <sample-namespace> --s3secret <s3-secret-name>
Ensure that you save the S3 credential at a secure place after it is generated for later use.
If MSDP kubectl plug-in is not installed, copy MSDP kubectl plug-in from the operator TAR folder to a directory from where you access the cluster host. This directory can be configured in the PATH environment variable so that kubectl can load MSDP kubectl as a plug-in automatically.
For example,
$ cp ./VRTSk8s-netbackup-<version>-0065/bin/kubectl-msdp /usr/local/bin/
- Input S3 credential field and S3 IP/FQDN fields in existing CR resources.
If the MSDP Scaleout is deployed with environment YAML, run the following command to update the spec.msdpScaleouts[<index>].s3Credential and spec.msdpScaleouts[<index>].s3Ip fields in the existing CR resources:
$ kubectl edit environments.netbackup.veritas.com <environmentCR_name> -n <sample-namespace>
Content format:
msdpScaleouts: - credential: autoDelete: true secretName: msdp-creds skipPrecheck: false s3Credential: secretName: <s3secretName> s3Ip: ipAddr: <s3IpAddress> fqdn: <s3Fqdn>If the MSDP Scaleout is deployed with MSDP Scaleout YAML, run the following command to update the spec.s3Credential and spec.s3ServiceIPFQDN fields in the existing CR resources:
$ kubectl edit msdpscaleouts.msdp.veritas.com.msdp.veritas.com <MSDP Scaleout CR name> -n <sample-namespace>
Content format:
spec: credential: autoDelete: true secretName: msdp-creds skipPrecheck: false s3Credential: secretName: <s3secretName> s3ServiceIPFQDN: ipAddr: <s3IpAddress> fqdn: <s3Fqdn>
- Provide the NetBackup token for MSDP S3.
If the MSDP Scaleout is deployed with environment YAML, skip this step. This step is done automatically by the environment operator.
If the MSDP Scaleout is deployed with MSDP Scaleout YAML, create a token from NetBackup web UI. Navigate to Security > Tokens > Add. Run the following command to create a token secret in Kubernetes:
$ kubectl create secret generic <S3-token-secret-name> --namespace <sample-namespace> --from-literal=token=<token-value>
Run the following command to update the spec.nbca.s3TokenSecret field in the existing CR resources:
$ kubectl edit msdpscaleout <MSDP Scaleout CR name> -n <sample-namespace>
Content format:
spec: nbca: s3TokenSecret: <S3-token-secret-name>Wait for a few minutes. MSDP operator enables S3 service automatically.
- Run the following command to check the S3 service status:
$ kubectl get msdpscaleouts.msdp.veritas.com/<MSDP Scaleout CR name> -o=jsonpath={.status.s3srvConfigured}
If the command output is true, S3 service is configured and ready for use.