Search <book_title>...

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

Last Published: 2022-09-08

Product(s): NetBackup (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

Allocating static PV for Media pods

When you want to use a disk with specific performance parameters, you can statically create the PV and PVC. You must allocate static PV and PVC before deploying the NetBackup server for the first time.

To allocate static PV for Media pods

Create storage class in cluster as per recommendations.
See How does the Config-Checker utility work. for storage class recommendation.
This newly created storage class name is used while creating PV and PVC's and should be mentioned for Catalog, Log, Data volume in the environment CR in mediaServer section at the time of deployment.
For more information on creating storage class, see Create a custom storage class.
For example,
```
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: managed-premium-retain
provisioner: disk.csi.azure.com
reclaimPolicy: Retain
allowVolumeExpansion: true
volumeBindingMode: Immediate
parameters:
  storageaccounttype: Premium_LRS
  kind: Managed
```

Calculate number of disks required.

The following persistent volumes are required by Media pods:

Data and Log volume disk per replica of media server.

Use the following format to form PVC names.

For media server

data-<resourceNamePrefix_of_media>-media-<media server replica number. Count starts from 0>
logs-<resourceNamePrefix_of_media>-media-<media server replica number. Count starts from 0>

Example 1

If user wants to deploy a media server with replica count 3.

Names of the Media PVC assuming resourceNamePrefix_of_media is testmedia.

For this scenario, you must create total 8 disks, 8 PV and 8 PVCs.

6 disks, 6 PV and 6 PVCs for media server.

Following will be the names for media server volumes

For data:

data-testmedia-media-0
data-testmedia-media-1
data-testmedia-media-10
data-testmedia-media-2

For log:

logs-testmedia-media-0
logs-testmedia-media-1
logs-testmedia-media-2

Example 2

If user wants to deploy a media server with replica count 5

Names of the Media PVC assuming resourceNamePrefix_of_media is testmedia.

For this scenario, you must create 12 disks, 12 PV and 12 PVCs

10 disks, 10 PV and 10 PVCs for media server.

Following will be the names for media server volumes

For data:

data-testmedia-media-0
data-testmedia-media-1
data-testmedia-media-2
data-testmedia-media-3
data-testmedia-media-4

For log:

logs-testmedia-media-0
logs-testmedia-media-1
logs-testmedia-media-2
logs-testmedia-media-3
logs-testmedia-media-4

Create required number of Azure disks and save the ID of newly created disk.
For more information, see Azure Disk - Static

Create PVs for each disk and link the PVCs to respective PVs.

To create the PVs, specify the created storage class and diskURI (ID of the disk received in step 3). The PV must be created using the claimRef field and provide PVC name for its corresponding namespace.

For example, if you are creating PV for catalog volume, storage required is 128GB, diskName is primary_catalog_pv and namespace is test. PVC named catalog-testprimary-primary-0 is linked to this PV when PVC is created in the namespace test.

apiVersion: v1
      kind: PersistentVolume
      metadata:
        name: catalog
           spec:
               capacity:
                       storage: 128Gi
               accessModes:
                       - ReadWriteOnce
               azureDisk:
                        kind: Managed
                        diskName: primary_catalog_pv
                        diskURI:  /subscriptions/3247febe-4e28-467d-a65c-10ca69bcd74b/
resourcegroups/MC_NBU-k8s-network_xxxxxx_eastus/providers/Microsoft.Compute/disks/deepak_s_pv
               claimRef:
                          apiVersion: v1
                          kind: PersistentVolumeClaim
                          name: catalog-testprimary-primary-0
                          namespace: test

Create PVC with correct PVC name (step 2), storage class and storage.

For example,

apiVersion: v1
               kind: PersistentVolumeClaim
               metadata:
                 name: catalog-testprimary-primary-0
                 namespace: test
               spec:
                 storageClassName: "managed-premium-retain"
                 accessModes:
                        - ReadWriteOnce
                 resources:
                        requests:
                          storage: 128Gi

Deploy the Operator.
Use previously created storage class names for the volumes in mediaServers section in environment CR spec and deploy environment CR.