NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Primary and media server CR
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Data-Migration execution and status details
Data migration is carried out in form of
in NetBackup Kubernetes cluster for only the primary server CR. There will be a migration job per primary volume for data migration which will be part of NetBackup environment namespace. Each job creates a pod in the cluster.Execution summary of the Data migration can be retrieved from the migration pod logs using the following command:
kubectl logs <migration-pod-name> -n <netbackup-environment-namespace>
This summary can also be retrieved from the operator pod logs using the following command:
kubectl logs <netbackup-operator-pod-name> -n <netbackup-environment-namespace>
Status of the data migration can be retrieved from the primary server CR by using the following command:
kubectl describe <PrimaryServer> <CR name> -n <netbackup-environment-namespace>
Following are the data migration statuses:
Success: Indicates all necessary conditions for the migration of the Primary server are passed.
Failed: Indicates some or all necessary conditions for the migration the Primary server are failed.
Running: Indicates migration is in running state for the Primary server.
If the Data migration execution status is failed, you can check the migration job logs using the following command:
kubectl logs <migration-pod-name> -n <netbackup-environment-namespace>
Review the error codes and error messages pertaining to the failure and update the primary server CR with the correct configuration details to resolve the errors.
For more information about the error codes, refer to NetBackup™ Status Codes Reference Guide.