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
Upgrading NetBackup individual components
This section describes upgrading of the following individual components:
NetBackup operators
NetBackup application
MSDP Scaleout
Snapshot Manager
Note:
Ensure that you go through this section carefully before starting with the upgrade procedure.
During upgrade, ensure that the following sequence of upgrade is followed:
Upgrade NetBackup operator
Upgrade NetBackup application
Upgrade MSDP operator
Upgrading Snapshot Manager
In case the above sequence is not followed, user may face data loss.
Preparing for NetBackup upgrade
- Take a backup of all the NetBackup jobs and ensure that all the jobs are suspended.
- Take a catalog backup.
See Backing up a catalog.
- Copy DRPackages files (packages) located at
/mnt/nblogs/DRPackages/from the pod to the host machine from where Kubernetes Service cluster is accessed.Run the following command:
kubectl cp <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages <Path_where_to_copy_on_host_machine>
- Preserve the data of
/mnt/nbdata and /mnt/nblogson host machine by creating tar and copying it using the following command:kubectl cp <primary-pod-namespace>/<primary-pod-name>:<tar_file_name> <path_on_host_machine_where_to_preserve_the_data>
- Preserve the environment CR object using the following command and operator directory that is used to deploy the NetBackup operator:
kubectl -n <namespace> get environment.netbackup.veritas.com <environment name> -o yaml > environment.yaml
Note:
Ensure that you upgrade MSDP operator first.
- (AKS-specific) In case of existing NetBackup deployments with Azure disks, change the storage class for catalog and log data of primary server to trigger data migration. For more information on changing the storage class, refer to the AKS-specific requirements sub-section of the following section:
See Preparing the environment for NetBackup installation on Kubernetes cluster.
- (EKS-specific) In case of existing NetBackup deployments with EBS, change the storage class for catalog data of primary server to trigger data migration. For more information on changing the storage class, refer to the following section: