Search <book_title>...

NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

Last Published: 2022-09-08

Product(s): NetBackup & Alta Data Protection (10.1)

Introduction to NetBackup on AKS
1. About NetBackup deployment on Azure Kubernetes Services (AKS) 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 Config-Checker utility work
2. Config-Checker execution and status details
3. How Data-Migration works
4. Data-Migration execution and status details
Deploying NetBackup
1. Preparing the environment for NetBackup installation on AKS
2. Recommendations of NetBackup deployment on AKS
3. Limitations of NetBackup deployment on AKS
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 pool for primary or media servers
Upgrading NetBackup
1. Preparing for NetBackup upgrade
2. Upgrading NetBackup operator
3. Upgrading Snapshot Manager operator
4. Upgrading NetBackup application
5. Upgrading Snapshot Manager
6. Post-migration tasks
7. Upgrade NetBackup during data migration
8. 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 upgrade 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 Media pods
Monitoring MSDP Scaleout
1. About MSDP Scaleout status and events
2. Monitoring with Azure Container insights
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 pool
Uninstalling MSDP Scaleout from AKS
1. Cleaning up MSDP Scaleout
2. Cleaning up the MSDP Scaleout operator
Uninstalling Snapshot Manager
1. Uninstalling Snapshot Manager from AKS
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. Data migration unsuccessful even after changing the storage class through the storage yaml file
26. Host validation failed on the target host
27. Primary pod is in pending state for a long duration
28. Taint, Toleration, and Node affinity related issues in cpServer
29. Operations performed on cpServer in environment.yaml file are not reflected
30. Host mapping conflict in NetBackup
31. NetBackup messaging queue broker take more time to start
32. Local connection is getting treated as insecure connection
33. Issue with capacity licensing reporting which takes longer time
34. Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
35. Primary pod goes in non-ready state
Appendix A. CR template
1. Secret
2. MSDP Scaleout CR

Deploying NetBackup and Snapshot Manager manually

After the operators are deployed as mentioned in the following section, you can deploy the NetBackup and Snapshot Manager environment:

To deploy NetBackup primary, media and Snapshot Manager components

Create a Kubernetes namespace where your new NetBackup environment will run. Run the following command:
kubectl create namespace nb-example
Where, nb-example is the name of the namespace. The Primary, Media, and Snapshot Manager application namespace must be different from the one used by the operators. It is recommended to use two namespaces. One for the operators, and a second one for the applications.
Create a secret to hold the Snapshot Manager credentials. The secret must include fields for username and password. If you are creating the secret by YAML, the type should be opaque or basic-auth.
For example:
```
apiVersion: v1
stringData:
  password: p@ssw0rd
  username: cpuser
kind: Secret
metadata:  
  name: cp-creds
  namespace: ns-155
type: Opaque
```
You can also use this command to create a secret.
kubectl create secret generic cp-credentials --namespace nb-example --from-literal=username='cpuser' --from-literal=password='p@ssw0rd'
Configure the samples/environment.yaml file according to your requirements. This file defines a primary server, media servers, and Snapshot Manager servers. See Configuring the environment.yaml file. for details.

Apply the environment.yaml file, using the same application namespace created in the above step.

kubectl apply --namespace nb-example --filename environment.yaml

Use this command to verify the new environment resource in your cluster:

kubectl get --namespace nb-example environments

After a few minutes, NetBackup finishes starting up the primary server, media servers and Snapshot Manager servers in the sequence that you configured in the environment resource.

Run the following command:

kubectl get --namespace nb-example all,environments,primaryservers,mediaservers, cpservers

The output would be displayed as follows:

azureuser@demo-vm-aks:~$ kubectl get all,environments,
primaryservers,mediaservers,cpservers -n nb-namespace
NAME                                             READY   STATUS    RESTARTS      AGE
pod/environment-sample-primary-0                 1/1     Running   0             2h
pod/flexsnap-agent-66d59855d4-kdkvh              1/1     Running   0             2h
pod/flexsnap-api-gateway-7c7f75ddc-nlgrq         1/1     Running   0             2h
pod/flexsnap-certauth-b84c985f6-tq5jx            1/1     Running   0             2h
pod/flexsnap-coordinator-597fc94884-bph2l        1/1     Running   0             2h
pod/flexsnap-fluentd-26wfl                       1/1     Running   0             2h
pod/flexsnap-fluentd-7kg96                       1/1     Running   0             2h
pod/flexsnap-fluentd-9h7sq                       1/1     Running   0             2h
pod/flexsnap-fluentd-9zzth                       1/1     Running   0             2h
pod/flexsnap-fluentd-collector-6dbfcc74f-tmxdh   1/1     Running   0             2h
pod/flexsnap-fluentd-n7r6s                       1/1     Running   0             2h
pod/flexsnap-fluentd-stfsz                       1/1     Running   0             2h
pod/flexsnap-idm-6ccb4cc695-kwnxj                1/1     Running   0             2h
pod/flexsnap-listener-58f5dc744c-hvdh5           1/1     Running   0             2h
pod/flexsnap-mongodb-7c7dbd9486-gdf28            1/1     Running   0             2h
pod/flexsnap-nginx-66cf654846-pdczx              1/1     Running   0             2h
pod/flexsnap-notification-69fb444b85-4fq5l       1/1     Running   0             2h
pod/flexsnap-rabbitmq-0                          1/1     Running   0             2h
pod/flexsnap-scheduler-6665cbf757-cwq87          1/1     Running   0             2h
pod/media1-media-0                               1/1     Running   0             2h

NAME                                 TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)            AGE
service/environment-sample-primary   LoadBalancer   10.0.218.235   10.244.204.203   13781:
                30748/TCP,13782:32042/TCP,1556:31727/TCP,443:30843/TCP,8443:32041/TCP,22:31321/TCP      2h
service/flexsnap-api-gateway         ClusterIP      10.0.156.177   <none>           8472/TCP            2h
service/flexsnap-certauth            ClusterIP      10.0.172.41    <none>           9000/TCP            2h      
service/flexsnap-fluentd-service     ClusterIP      10.0.126.162   <none>           24224/TCP           2h
service/flexsnap-idm                 ClusterIP      10.0.145.64    <none>           8452/TCP            2h
service/flexsnap-mongodb             ClusterIP      10.0.21.233    <none>           27017/TCP           2h
service/flexsnap-nginx               LoadBalancer   10.0.34.60     10.244.204.201   443:32306/
                                                                                    TCP,5671:30740/TCP  2h
service/flexsnap-rabbitmq            ClusterIP      10.0.125.225   <none>           5671/TCP               
service/media1-media-0               LoadBalancer   10.0.170.169   10.244.204.202   13782:30292/
                                                                                    TCP,1556:31976/TCP  2h
NAME                              DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/flexsnap-fluentd   6         6         6       6            6           <none>          2h

NAME                                         READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/flexsnap-agent               1/1     1            1           2h
deployment.apps/flexsnap-api-gateway         1/1     1            1           2h
deployment.apps/flexsnap-certauth            1/1     1            1           2h
deployment.apps/flexsnap-coordinator         1/1     1            1           2h
deployment.apps/flexsnap-fluentd-collector   1/1     1            1           2h
deployment.apps/flexsnap-idm                 1/1     1            1           2h
deployment.apps/flexsnap-listener            1/1     1            1           2h
deployment.apps/flexsnap-mongodb             1/1     1            1           2h
deployment.apps/flexsnap-nginx               1/1     1            1           2h
deployment.apps/flexsnap-notification        1/1     1            1           2h
deployment.apps/flexsnap-scheduler           1/1     1            1           2h

NAME                                                   DESIRED   CURRENT   READY   AGE
replicaset.apps/flexsnap-agent-66d59855d4              1         1         1       2h
replicaset.apps/flexsnap-api-gateway-7c7f75ddc         1         1         1       2h
replicaset.apps/flexsnap-certauth-b84c985f6            1         1         1       2h
replicaset.apps/flexsnap-coordinator-597fc94884        1         1         1       2h
replicaset.apps/flexsnap-fluentd-collector-6dbfcc74f   1         1         1       2h
replicaset.apps/flexsnap-idm-6ccb4cc695                1         1         1       2h
replicaset.apps/flexsnap-listener-58f5dc744c           1         1         1       2h
replicaset.apps/flexsnap-mongodb-7c7dbd9486            1         1         1       2h
replicaset.apps/flexsnap-nginx-66cf654846              1         1         1       2h
replicaset.apps/flexsnap-notification-69fb444b85       1         1         1       2h
replicaset.apps/flexsnap-scheduler-6665cbf757          1         1         1       2h

NAME                                          READY   AGE
statefulset.apps/environment-sample-primary   1/1     2h
statefulset.apps/flexsnap-rabbitmq            1/1     2h
statefulset.apps/media1-media                 1/1     2h

NAME                                     READY  AGE   STATUS
environment.netbackup.veritas.com/
environment-sample                        3/3   2h   Success

NAME                                     TAG    AGE   STATUS
primaryserver.netbackup.veritas.com/
environment-sample                     10.1.0   2h   Success

NAME                                     TAG    AGE   PRIMARY SERVER      STATUS
mediaserver.netbackup.veritas.com/
media1                                 10.1.0   2h   primary.
                                                    example.veritas.com   Success

NAME                                     TAG    AGE  STATUS
cpserver.netbackup.veritas.com/
cpserver-1                              10.1.0  2h   Success

More Information

Deploying the operators manually