About NetBackup operator logs
Note the following about the NetBackup operator logs.
NetBackup operator logs can be checked using the operator pod logs using the kubectl logs <Netbackup-operator-pod-name> -c netbackup-operator -n <netbackup-opertaor-namespace> command.
NetBackup operator provides different log levels that can be changed before deployment of NetBackup operator.
The following log levels are provided:
-1 - Debug
0 - Info
1 - Warn
2 - Error
By default, the log level is 0.
It is recommended to use 0, 1, or 2 log level depending on your requirement.
Before you deploy NetBackup operator, you can change the log levels using
operator_patch.yaml.After deployment if user changes operator log level, to reflect it, user has to perform the following steps:
Apply the operator changes using the kubectl apply -k <operator-folder> command.
Restart the operator pod. Delete the pod using the kubectl delete pod/<netbackup-opertaor-pod-name> -n <namespace> command. Kubernetes will recreate the NetBackup operator pod again after deletion.
Config-Checker jobs that run before deployment of primary server and media server creates the pod. The logs for config checker executions can be checked using the kubectl logs <configchecker-pod-name> -n <netbackup-operator-namespace> command.
Installation logs of NetBackup primary server and media server can be retrieved using any of the following methods:
Run the kubectl logs <PrimaryServer/MediaServer-Pod-Name> -n <PrimaryServer/MediaServer namespace> command.
Execute the following command in the primary server/media server pod and check the
/mnt/nblogs/setup-server.logfile:kubectl exec -it <PrimaryServer/MediaServer-Pod-Name> -n <PrimaryServer/MediaServer-namespace> -- bash
Data migration jobs create the pods that run before deployment of primary server. The logs for data migration execution can be checked using the following command:
kubectl logs <migration-pod-name> -n <netbackup-environment-namespace>
Execute the following respective commands to check the event logs that shows deployment logs for PrimaryServer and MediaServer:
For primary server: kubectl describe PrimaryServer <PrimaryServer name> -n <PrimaryServer-namespace>
For media server: kubectl describe MediaServer<MediaServername> -n<MediaServer-namespace>