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
- 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
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Cluster backup
Once NetBackup is up and running and the basic sanity test is done to ensure that the cluster is in a working state, then save the template of the cluster through CLI as follows:
Ensure that you are logged in through Azure CLI with subscription set to where the cluster is present:
az group export --resource-group <resource_group> --resource-ids <resourceID> --include-parameter-default-value
Or
az group export --resource-group <resource_group> --resource-ids /subscriptions/${subscription_id}/resourceGroups/$resource_group/providers/Microsoft.ContainerService/managedClusters/$cluster_name --include-parameter-default-value
Here,
Parameter
Description
resource_group
Resource group where the cluster is present.
resourceID
Cluster's resource ID. This can be obtained from the azure portal by navigating to the cluster and clicking on the JSON link present on the top corner of the Overview.
subscription_id
Subscription ID where cluster is present.
cluster_name
Cluster name that needs to be saved.
Copy the JSON output to a file and save it as a JSON file. For example,
template.jsonEnsure that
template.jsonfile is saved and is safe. This is required later to recover the cluster.Note the Azure Container Registry name which is attached to the cluster.
Note:
User must save the output of every command in different file.
Get the cluster details.
Use the following command to obtain the information of the cluster:
aws eks describe-cluster --name <cluster name>
Obtain the detailed information about each subnet which was received as output of the above command:
aws ec2 describe-subnets --subnet-ids <subnetID-1> <subnetID-2>
Obtain the IAM role name from describe-cluster command and using the following command save the policies attached to it:
aws iam list-attached-role-policies --role-name <role name>
Obtain the security group ID from describe-cluster command and using following command save the details of security-groups:
aws ec2 describe-security-groups --group-ids <Security group ID>
Get the nodegroup details.
Use the following command to get the list of all node groups:
aws eks list-nodegroups --cluster-name <cluster-name>
Obtain the information of a particular nodegroup from above list using the following command:
aws eks describe-nodegroup --nodegroup-name <nodegroup-name> --cluster-name <cluster-name>
User must execute this command for each node group in the cluster to obtain the details of each nodegroup.
Get the EFS ID details.
NetBackup uses two EFS IDs (Primary and Snapshot Manager server):
Get EFS ID of Primary server: spec > primary > storage > catalog > storageClassName
Get EFS ID of Snapshot Manager server: Get storage class name from spec > cpserver > storage > log > storageClassName.
Describe this storage class using the following command and note the fileSystemId:
kubectl describe sc storageClassName
Use following commands to describe EFS:
aws efs describe-file-systems --file-system-id <EFS ID>
Run the above EFS command for Primary and Snapshot Manager server EFS ID. The above EFS command does not describe the mount targets which was used while creating EFS. To get mount targets details use the following command:
aws efs describe-mount-targets --file-system-id <EFS ID>
Note the non-default parameters with which EFS was created.
Get the list of Add-on by using the following command:
aws eks list-addons --cluster-name <cluster-name>