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
Post Kubernetes cluster restart, issues observed in case of containerized Postgres deployment
After Kubernetes cluster restart in case of containerized Postgres deployment, couple of flexsnap pods went into state and primary pod was not started successfully.
This issue arises due to certificate expiration when the cluster was down. Perform the following to ensure that the issue occurred was due to certificate expiration:
Run the following command to exec into the
nb-postgresqlpod:kubectl -n <namespace> exec pod/nb-postgresql-0 -it bash
Run the following command from within the Postgres pod
psql "host=nb-postgresql port=13787 dbname=postgres user=postgres sslmode=verify-full sslcert='/netbackup/postgresql/keys/server/tls.crt' sslkey='/netbackup/postgresql/keys/server/tls.key' sslrootcert=/netbackup/postgresql/keys/server/ca.crt"
Following error message is displayed:
psql: error: connection to server at "nb-postgresql" (10.240.3.27), port 13787 failed: SSL error: certificate verify failed.
Run the following command to check the
ca.crtserver certificate:Get the
ca.crtof :kubectl -n <namespace> get secret postgresql-server-crt -o "jsonpath={.data['ca\.crt']}" | base64 -d > server_ca.crt
Get the
ca.crtof :kubectl -n <namespace> get secret postgresql-netbackup-ca -o "jsonpath={.data['ca\.crt']}" | base64 -d > ca.crt
Get current date on the system:
date
Following message is displayed:
Tue Feb 27 17:07:14 UTC 2024
Check expiry of
ca.crt:openssl x509 -enddate -noout -in ca.crt
Following message is displayed:
notAfter=Feb 27 17:52:58 2024 GMT
Check expiry of
server_ca.crt:openssl x509 -enddate -noout -in server_ca.crt
Following message is displayed:
notAfter=Feb 27 16:57:58 2024 GMT
The above displayed messages indicate that
ca.crtof is referring to an expired certificate.
Resolution:
Perform the following to resolve the certificate issue:
Delete the certificate secrets:
kubectl -n <namespace> delete secret postgresql-netbackup-ca postgresql-server-crt postgresql-client-crt
Execute the following commands to ensure that the correct certificate is referred:
Get the
ca.crtof :kubectl -n <namespace> get secret postgresql-server-crt -o "jsonpath={.data['ca\.crt']}" | base64 -d > server_ca.crt
Get the
ca.crtof :kubectl -n <namespace> get secret postgresql-netbackup-ca -o "jsonpath={.data['ca\.crt']}" | base64 -d > ca.crt
Get current date on the system:
date
Following message is displayed:
Tue Feb 27 17:11:59 UTC 2024
Check expiry of
ca.crt:openssl x509 -enddate -noout -in ca.crt
Following message is displayed:
notAfter=Feb 27 18:11:38 2024 GMT
Check expiry of
server_ca.crt:openssl x509 -enddate -noout -in server_ca.crt
Following message is displayed:
notAfter=Feb 27 18:11:38 2024 GMT
The above displayed messages indicate that
ca.crtof is referring to the correct certificate.Run the following command to exec into the
nb-postgresqlpod:kubectl -n <namespace> exec pod/nb-postgresql-0 -it bash
Run the following command from within the Postgres pod
psql "host=nb-postgresql port=13787 dbname=postgres user=postgres sslmode=verify-full sslcert='/netbackup/postgresql/keys/server/tls.crt' sslkey='/netbackup/postgresql/keys/server/tls.key' sslrootcert=/netbackup/postgresql/keys/server/ca.crt"
Following message is displayed:
Password for user postgres: