NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Preparing the environment for NetBackup installation on Kubernetes cluster
- Prerequisites for Snapshot Manager (AKS/EKS)
- Prerequisites for Kubernetes cluster configuration
- Prerequisites for Cloud Scale configuration
- Prerequisites for deploying environment operators
- Prerequisites for using private registry
- 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)
- Managing media server configurations in Web UI
- Prerequisites
- 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 logging
- 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 issues when media server PVs are deleted
- Resolving an issue related to insufficient storage
- Resolving an issue related to invalid nodepool
- 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
- 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
- Job remains in queue for long time
- Extracting logs if the nbwsapp or log-viewer pods are down
- 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
Decoupling of NetBackup Policy and Job Management from primary server
In Cloud Scale Technology, policy execution and job management (NBPEM and NBJM) is implemented as StatefulSet which can be deployed through the operators. Policy and job management capabilities are decoupled from the primary server and run as separate service in Kubernetes cluster.
NBPEM/NBJM is dependent on primary, web services and mqbroker pods. NBPEM/NBJM cluster comprises of one or more policyjobmgr pods and one or more policyjob pods. StatefulSet policyjobmgr represents the leaders whereas StatefulSet policyjob is associated with the followers. You can consider adding a secondary leader to guarantee continuous job execution if the primary leader is unavailable.
Note:
In the above figure, is a decoupled component. For more information refer to Decoupling of NetBackup web services from primary server.
A NBPEM/NBJM pod consists of following containers:
The main container for core policy and job management
PBX sidecar
Vnetd sidecar
Fluentbit sidecar
Housekeeping sidecar
The nbpemreq (NetBackup Policy Execution Manager Requisition) command shows the distribution of policy/clients across the follower pods.
For Cloud Scale, it is recommended to run the nbpemreq command on the primary pod or on the policyjob leader.
It is recommended to use -M option with the pod name to direct the request to the specific pod. When -M option is not specified, the default target is one of the leaders.
For more information on nbpemreq command, refer to the NetBackup™ Commands Reference Guide.
Multiplexing (MPX): MPX is not supported in NBPEM/NBJM scale-out environment.
Supporting MPX in any format could lead to unpredictable/unexpected/undesired behaviors. Hence it is recommended to disable the MPX support.
Session end and catalog backup: For scale-out deployments (Kubernetes cluster), session end catalog backup schedules are not supported.
For non scale-out deployments, session end catalog backup schedules and persistence would be moved to a Json formatted file.
Secondary leader: The secondary leader's role is limited to forwarding media server calls to the follower pods. All communication from the media server is load balanced between primary and secondary leaders, ensuring uninterrupted job execution in case the primary leader is unavailable.
Scale-out/Scale-in:
Auto-scaling is not supported. However, manual scaling of follower and leader is allowed.
By default, Cloud Scale starts with a single follower pod; you can scale this out up to a maximum of 12 pods.
By default, Cloud Scale starts with a single leader pod; you can scale this out up to a maximum of 6 pods.
Warning:
The users are advised to scale out the leader and follower services only if necessary, as this would consume more resources.
Run the following command to control the follower replica count:
kubectl -n <namespace> patch environment nbux --type merge --patch '{"spec": {"primary": {"replicas":{"policyjob":'<COUNT>'}}}}'
Run the following command to control the leader replica count:
kubectl -n <namespace> patch environment nbux --type merge --patch '{"spec": {"primary": {"replicas":{"policyjobmgr":'<COUNT>'}}}}'