NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
- Introduction to NetBackup on AKS
- Deployment with environment operators
- Assessing cluster configuration before deployment
- Deploying NetBackup
- Preparing the environment for NetBackup installation on AKS
- Recommendations of NetBackup deployment on AKS
- Limitations of NetBackup deployment on AKS
- About primary server CR and media server CR
- Monitoring the status of the CRs
- Updating the CRs
- Deleting the CRs
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the node pool for primary or media servers
- Deploying MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- Troubleshooting
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Pod restart failure due to liveness probe time-out
- Socket connection failure
- Resolving an invalid license key issue
- Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
- Resolving the issue where the NetBackup server pod is not scheduled for long time
- Resolving an issue where the Storage class does not exist
- Resolving an issue where the primary server or media server deployment does not proceed
- Resolving an issue of failed probes
- Resolving token issues
- Resolving an issue related to insufficient storage
- Resolving an issue related to invalid nodepool
- Resolving a token expiry issue
- Resolve an issue related to inconsistency in file ownership
- Resolve an issue related to KMS database
- Resolve an issue related to pulling an image from the container registry
- Resolving an issue related to recovery of data
- Check primary server status
- Pod status field shows as pending
- Ensure that the container is running the patched image
- Getting EEB information from an image, a running container, or persistent data
- Appendix A. CR template
Backing up a catalog
You can back up a catalog.
To back up a catalog
- Execute the following command in the primary server pod:
kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash
- Create a directory DRPackages at persisted location using
mkdir /mnt/nblogs/DRPackages. - Change ownership of DRPackages folder to service user using
chown nbsvcusr:nbsvcusr /mnt/nblogs/DRPackages. - Set the passphrase to be used at time of catalog recovery.
Open NetBackup Administrator Console (Java UI).
Navigate to Security Management > Global Security Setting > Disaster Recovery.
In Encryption for Disaster Recovery section, add the passphrase, confirm passphrase, and save it.
- Add respective external media server entry in host properties through NetBackup Management > Host properties > Master Server > Add Additional server.
Note:
It is recommended to use an external media server for catalog backup and recovery.
- Restart the NetBackup services in primary and external media server.
Execute the following command in the primary server pod:
kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash
Deactivate NetBackup health probes using the /opt/veritas/vxapp-manage/nbu-health deactivate command.
Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the services using the /usr/openv/netbackup/bin/bp.start_all command.
Activate NetBackup health probes using the /opt/veritas/vxapp-manage/nbu-health activate command.
Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the services using the /usr/openv/netbackup/bin/bp.start_all command on the external media server.
- Configure storage unit on earlier added external media server.
For more information, refer to the NetBackup™ Administrator's Guide,Volume I
Note:
It is recommended to use AdvancedDisk or BasicDisk storage unit.
- Configure NetBackup catalog backup policy.
Add package path as
/mnt/nblogs/DRPackageswhile configuring the catalog backup policy. - Run the catalog backup job.