Search <book_title>...

NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Last Published: 2022-12-19

Product(s): NetBackup (10.1.1)

Introduction to NetBackup on EKS
1. About NetBackup deployment on Amazon Elastic Kubernetes (EKS) cluster
2. Required terminology
3. User roles and permissions
4. About MSDP Scaleout
5. About MSDP Scaleout components
6. Limitations in MSDP Scaleout
Deployment with environment operators
1. About deployment with the environment operator
2. Deploying the operators manually
3. Deploying NetBackup and MSDP Scaleout manually
4. Deploying NetBackup and Snapshot Manager manually
5. Configuring the environment.yaml file
6. Uninstalling NetBackup environment and the operators
7. Applying security patches
Assessing cluster configuration before deployment
1. How does the webhook validation works
2. Webhooks validation execution details
3. How does the Config-Checker utility work
4. Config-Checker execution and status details
Deploying NetBackup
1. Preparing the environment for NetBackup installation on EKS
2. Recommendations of NetBackup deployment on EKS
3. Limitations of NetBackup deployment on EKS
4. About primary server CR and media server CR
  1. After installing primary server CR
  2. After Installing the media server CR
5. Monitoring the status of the CRs
6. Updating the CRs
7. Deleting the CRs
8. Configuring NetBackup IT Analytics for NetBackup deployment
9. Managing NetBackup deployment using VxUpdate
10. Migrating the node group for primary or media servers
Upgrading NetBackup
1. Preparing for NetBackup upgrade
2. Upgrading NetBackup operator
3. Upgrading NetBackup application
4. Upgrade NetBackup from previous versions
5. Procedure to rollback when upgrade fails
Deploying Snapshot Manager
1. Overview
2. Prerequisites
3. Installing the docker images
Migration and upgrade of Snapshot Manager
1. Migration and updating of Snapshot Manager
Deploying MSDP Scaleout
1. Deploying MSDP Scaleout
2. Prerequisites
3. Installing the docker images and binaries
4. Initializing the MSDP operator
5. Configuring MSDP Scaleout
6. Using MSDP Scaleout as a single storage pool in NetBackup
7. Configuring the MSDP cloud in MSDP Scaleout
Upgrading MSDP Scaleout
1. Upgrading MSDP Scaleout
Monitoring NetBackup
1. Monitoring the application health
2. Telemetry reporting
3. About NetBackup operator logs
4. Expanding storage volumes
5. Allocating static PV for Primary and Media pods
Monitoring MSDP Scaleout
1. About MSDP Scaleout status and events
2. Monitoring with Amazon CloudWatch
3. The Kubernetes resources for MSDP Scaleout and MSDP operator
Monitoring Snapshot Manager deployment
1. Overview
2. Logs of Snapshot Manager
3. Configuration parameters
Managing the Load Balancer service
1. About the Load Balancer service
2. Notes for Load Balancer service
3. Opening the ports from the Load Balancer service
Performing catalog backup and recovery
1. Backing up a catalog
2. Restoring a catalog
Managing MSDP Scaleout
1. Adding MSDP engines
2. Adding data volumes
3. Expanding existing data or catalog volumes
  1. Manual storage expansion
4. MSDP Scaleout scaling recommendations
5. MSDP Cloud backup and disaster recovery
  1. About the reserved storage space
  2. Cloud LSU disaster recovery
6. MSDP multi-domain support
7. Configuring Auto Image Replication
8. About MSDP Scaleout logging and troubleshooting
  1. Collecting the logs and the inspection information
About MSDP Scaleout maintenance
1. Pausing the MSDP Scaleout operator for maintenance
2. Logging in to the pods
3. Reinstalling MSDP Scaleout operator
4. Migrating the MSDP Scaleout to another node group
Uninstalling MSDP Scaleout from EKS
1. Cleaning up MSDP Scaleout
2. Cleaning up the MSDP Scaleout operator
Uninstalling Snapshot Manager
1. Uninstalling Snapshot Manager from EKS
Troubleshooting
1. View the list of operator resources
2. View the list of product resources
3. View operator logs
4. View primary logs
5. Pod restart failure due to liveness probe time-out
6. Socket connection failure
7. Resolving an invalid license key issue
8. Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
9. Resolving the issue where the NetBackup server pod is not scheduled for long time
10. Resolving an issue where the Storage class does not exist
11. Resolving an issue where the primary server or media server deployment does not proceed
12. Resolving an issue of failed probes
13. Resolving token issues
14. Resolving an issue related to insufficient storage
15. Resolving an issue related to invalid nodepool
16. Resolving a token expiry issue
17. Resolve an issue related to KMS database
18. Resolve an issue related to pulling an image from the container registry
19. Resolving an issue related to recovery of data
20. Check primary server status
21. Pod status field shows as pending
22. Ensure that the container is running the patched image
23. Getting EEB information from an image, a running container, or persistent data
24. Resolving the certificate error issue in NetBackup operator pod logs
25. Resolving the primary server connection issue
26. Primary pod is in pending state for a long duration
27. Host mapping conflict in NetBackup
28. NetBackup messaging queue broker take more time to start
29. Local connection is getting treated as insecure connection
30. Issue with capacity licensing reporting which takes longer time
31. Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
32. Wrong EFS ID is provided in environment.yaml file
33. Primary pod is in ContainerCreating state
34. Webhook displays an error for PV not found
Appendix A. CR template
1. Secret
2. MSDP Scaleout CR

Socket connection failure

Socket connection failure can happen because of the following reasons:

Long processing delays
AWS connection reset (default 4 minutes)
Load on CPU or Memory pressure
IO saturation and throttling under load

If there are problems with the TCP stacks on the hosts, network between the hosts, or unusual long processing delays, then the connection may drop and the TCP stack on the host is unaware of the situation.

The following error is displayed in the web UI under job details:

db_FLISTsend failed: unexpected message received (43)
 *** - Error bptm (pid=14599) get_string() failed, 
Connection reset by peer (104), network read error
*** - Info bptm (pid=14599) EXITING with status 42 <----------
*** - Info nbux-systest-media-1 (pid=14599) 
StorageServer=PureDisk:nbux-systest-media-1; 
Report=PDDO Stats for (nbux-systest-media-1): 
scanned: 4195521 KB, CR sent: 171002 KB, CR sent over FC: 0 KB, 
dedup: 95.9%, cache disabled, where dedup space saving:6.6%, 
compression space saving:89.3%
*** - Info bpbkar (pid=19109) done. status: 42: network read failed

To resolve this issue, update the sysctl.conf values for NetBackup servers deployed on the EKS cluster.

NetBackup image sets following values in sysctl.conf during EKS deployment:

net.ipv4.tcp_keepalive_time = 180
net.ipv4.tcp_keepalive_intvl = 10
net.ipv4.tcp_keepalive_probes = 20
net.ipv4.ip_local_port_range = 14000 65535

These settings are persisted at the location /mnt/nbdata/etc/sysctl.conf.

There are two ways to modify these values:

Modify the value in both /etc/sysctl.conf and /mnt/nbdata/etc/sysctl.conf and run the sysctl -p command to load the modified values.
Modify the values in /mnt/nbdata/etc/sysctl.conf and restart the pod. The new values are reflected after the pod restart.

If external media servers are used, perform the steps in the following order:

Add the following in /usr/openv/netbackup/bp.conf:
HOST_HAS_NAT_ENDPOINTS = YES
Add the following sysctl configuration values in etc/sysctl.conf on external media servers to avoid any socket connection issues:
- net.ipv4.tcp_keepalive_time = 180
- net.ipv4.tcp_keepalive_intvl = 10
- net.ipv4.tcp_keepalive_probes = 20
- net.ipv4.ip_local_port_range = 14000 65535
- net.core.somaxconn = 4096
Save the setting using the sysctl -p command.