NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 8456
Explanation: This error occurs when migration pod remains in pending state for more than five minutes.
Recommended Action: Perform the following as appropriate:
Check the NetBackup operator logs for details using the following command:
kubectl logs <netbackup-operator-pod-name> netbackup-operator -n <netbackup-operator-namespace>
Ensure that the nodes are available to schedule the pod in the cluster with respective labels.
Review the events of the migration pod using the following command:
kubectl describe <migration-pod-name> -n <operator-namespace>
Delete the new PVC with the Azure files that the failed data migration creates using the following command:
kubectl delete pvc <pvc_name> -n <netbackup-environment-namespace>
Reapply the environment.yaml
file to reinitiate the data migration. For other migration details, refer to the NetBackup Deployment for Azure Kubernetes Cluster (AKS) Administrator's Guide.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.