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

Migration and upgrade of Snapshot Manager

Migrating Snapshot Manager

Users can manually migrate Snapshot Manager registered with NetBackup to Kubernetes Service cluster environment by performing the following steps:

Disable Snapshot Manager from NetBackup.
Stop services on the Snapshot Manager VM.

Create and attach a disk to the VM which will be used as PV for mongoDB:

Copy contents from /cloudpoint/mongodb to the new disk .
Copy flexsnap.conf and bp.conf configuration files to the VM from where cluster is accessible.
Detach the disk from VM and move it to cluster resources group (RG): MC_<clusterRG>_<cluster name>_<cluster_region>

From VM perform the following steps:

Create configuration maps using the following command:
kubectl create cm agentconf --from-file=<path to flexsnap.conf > -n <application namespace>
kubectl create cm nbuconf --from-file=<path to bp.conf>  -n <application namespace>
Create Snapshot Manager Secrets using the following command:
kubectl create secret generic cp-creds --from-literal=username='<username>' --from-literal=password='<password>'

Create mongodb Persistent Volume and Persistent Volume Claim as follows:

mongodb pv: 
 
apiVersion: v1 
kind: PersistentVolume 
metadata: 
  name: pv-azuredisk 
spec: 
  capacity: 
    storage: <Size of the disk> 
  accessModes: 
    - ReadWriteOnce 
  persistentVolumeReclaimPolicy: Retain 
  storageClassName: <Storage class name> 
  csi: 
    driver: disk.csi.azure.com 
    readOnly: false 
    volumeHandle: <Resource ID of the disk> 
    volumeAttributes: 
      fsType: <FS type> 
 
mongodb-pvc: 
apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: mongo-persistent-storage-flexsnap-mongodb-0 
spec: 
  accessModes: 
    - ReadWriteOnce 
  resources: 
    requests: 
      storage: <Disk size> 
  volumeName: pv-azuredisk 
  storageClassName: managed-csi

Edit the environment.yaml file to upgrade NetBackup (primary/media/MSDP) and add section for Snapshot Manager as follows:

cpServer: 
  - name: cp-cluster-deployment  
    containerRegistry: acr.azurecr.io 
    credential: 
      secretName: cp-creds 
    networkLoadBalancer: 
      annotations: 
        service.beta.kubernetes.io/azure-load-balancer-internal: "true" 
      ipAddr: 1.2.3.4 
      fqdn: cpserver.example.com 
  
    storage: 
      log: 
        capacity: 10Gi 
        storageClassName: standard 
      data: 
        capacity: <Disk size mentioned in mongodb pv> 
        storageClassName: <<Storage class name mentioned in mongodb pv> 
    nodeSelector: 
      controlPlane: 
        nodepool: cpcontrol1 
        labelKey: cp-node-label 
        labelValue: cpcontrol1 
      dataPlane: 
        nodepool: cpdata1 
        labelKey: cp-node-label 
        labelValue: cpdata1

Apply the environment.yaml file using the following command:
kubectl apply -f <path to environment.yaml>
Re-register the Snapshot Manger from WebUI if the Snapshot Manager name (fqdn/ip) is same as VM deployment.

Updating/Upgrading Snapshot Manager

Update:
User can update few parameters on the existing deployed Snapshot Manager by making changes in the cpServer section of environment.yaml file and apply it.
Only log size and data size fields can be changed in cpServer section of CR. For update operation to work, set the value of allowVolumeExpansion parameter to true in the storage classes used.
Upgrade:
If there is a change in the cpServer tag, then it would be considered as a Snapshot Manager upgrade. For upgrade only few parameters related to Snapshot Manager can be modified.

The following table lists the parameters that can be modified during update/upgrade of Snapshot Manager:

Parameters	Edit during update	Edit during upgrade
resourceNamePrefix	No	No
tag	No	Yes
containerRegistry	No	Yes
credential: secretName	No	No
networkLoadBalancer: annotations	No	Yes
networkLoadBalancer: fqdn	No	No
networkLoadBalancer: ipAddr	No	Yes
data.capacity	Yes	Yes
data.storageClassName	No	No
log.capacity	Yes	Yes
log.storageClassName	No	No
cpServer.NodeSelector.ControlPlane	No	Yes
cpServer.NodeSelector.DataPlane	No	Yes