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: 8415
Explanation: Error in creating the load balancer service for the MediaServer.
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 RBAC permissions are correct. Refer to the NetBackup Deployment on Azure Kubernetes Cluster (AKS) Administrator's Guide.
Check your cluster configuration and verify that it meets the expected prerequisites for NetBackup deployment. Refer to the NetBackup Deployment on Azure Kubernetes Cluster (AKS) Administrator's Guide.
Check the Kubernetes documentation for service details: https://kubernetes.io/docs/concepts/services-networking/service/
If the issue still doesn't resolve, perform the following steps:
Edit the environment CR and decrement the media server replicas. Change the replica count in the media section with the last successful count for which the load balancer service was created for the media replicas. Then, apply the changes using the following command:
kubectl apply -f <environment.yaml>
For example: The media replica count is set to three and services are successfully created for only two media servers replicas. However, there is an error in creating service for the third media server. You must change the replica count to two.
If there is an error in creating service for the first media replica, change the replica count to 0.
Verify if the media replica services are decremented as per provided replica count using the following command:
kubectl get service <service-name> -n <namespace>
Edit the environment CR and increment media replica count back to the original count and apply the changes. Verify if the service is now created for respective media server.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.