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

About the Load Balancer service

Key features of the Load Balancer service:

Load balancer services are created in primary server and media server deployment that allows you to access the NetBackup application from public domains.
In primary server or media server CR spec, networkLoadBalancer section is used for handling the IP address and DNS name allocation for load balancer services. This section combines to sub fields type, annotations, and ipList whereas these fields are optional. If ipList is provided in CR spec, IP address count must match the replica count in case of media server CR whereas in case of primary server CR, only one IP address needs to be mentioned.
NetBackup supports the network load balancer with AWS Load Balancer scheme as internet-facing.
The networkLoadBalancer section can be used to provide static IP address and dns name allocation to the Load Balancer services.
FQDN must be created before being used. Refer below sections for different allowed annotations to be used in CR spec.
- User must add the following annotations:
  service.beta.kubernetes.io/aws-load-balancer-subnets: <subnet1 name>
  In addition to the above annotations, if required user can add more annotations supported by AWS. For more information, see AWS Load Balancer Controller Annotations.
  Example: CR spec in primary server,
```
networkLoadBalancer: 
type: Private
annotations:
  service.beta.kubernetes.io/aws-load-balancer-subnets: <subnet1 name> 
  ipList: 
  "10.244.33.27: abc.vxindia.veritas.com"
```
  CR spec in media server,
```
networkLoadBalancer: 
type: Private
annotations:
   service.beta.kubernetes.io/aws-load-balancer-subnets: <subnet1 name> 
   ipList: 
  "10.244.33.28: pqr.vxindia.veritas.com" 
  "10.244.33.29: xyz.vxindia.veritas.com"
```
  The IP address, the subnet provided in ipList and annotations in networkLoadBalancer section in CR spec must belong to same availability zone that of the node group.
  Note:
  The subnet provided here should be same as the one given in node pool used for primary server and media server.

If NetBackup client is outside VPC or to access Web UI from outside VPC, then client CIDR must be added with all NetBackup ports in security group rule of cluster. Run the following command, to obtain the cluster security group:

aws eks describe-cluster --name <my-cluster> --query cluster.resourcesVpcConfig.clusterSecurityGroupId

For more information on cluster security group, see Amazon EKS security group requirements and considerations.

Add inbound rule to security group. For more information, see Add rules to a security group.

Default ports used in the Load Balancer service

Primary server:
- 1556
  Used as bidirectional port. Primary server to/from media servers and primary server to/from client require this TCP port for communication.
- 8443
  Used to inbound to java nbwmc on the primary server.
- 443
  Used to inbound to vnet proxy tunnel on the primary server. Also, this is used Nutanix workload, communication from primary server to the deduplication media server.
- 13781
  The MQBroker is listening on TCP port 13781. NetBackup client hosts - typically located behind a NAT gateway - be able to connect to the message queue broker (MQBroker) on the primary server.
- 13782
  Used by primary server for bpcd process.
- Port 22
  Used by NetBackup IT Analytics data collector for data collection.
Media server:
- 1556
  Used as bidirectional port. Primary server to/from media servers and primary server to/from client require this TCP port for communication.
- 13782
  Used by media server for bpcd process.
- 443
  The Snapshot Manager user interface uses this port as the default HTTPS port.
- 5671
  The Snapshot Manager RabbitMQ server uses this port for internal service communications. This port must be open to support multiple agents, extensions, backup from snapshot, and restore from backup jobs.
- 2049
  It is used for Amazon EFS access.
  For more information, see Source ports for working with EFS.