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: 8439
Explanation: The config-checker job runs before the primary or the media server deployment when configCheckMode = default or configCheckMode = dryrun in the CR spec. This config-checker job has not been created in the cluster.
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>
Verify that the RBAC permissions for the Job are correct. Refer to the NetBackup Deployment on Azure Kubernetes Cluster (AKS) Administrator's Guide.
If this issue happens with a fresh deployment, perform the following:
If the issue is the primaryServer CR, perform the following:
Delete the environment CR using the command: kubectl delete -f <environment.yaml>
Redeploy the environment again using the command: kubectl apply -f <environment.yaml>
If the issue is the mediaServer CR, delete the CR by removing the mediaServers section in
environment.yaml
. Save the mediaServers data somewhere so that it can be used at the time of redeployment. Apply changes using the command: kubectl apply -f <environment.yaml>After deleting the mediaServer, update the
environment.yaml
with the mediaServers data that was deleted earlier. Redeploy it again using the command: kubectl apply -f <environment.yaml>
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.