Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section III. Monitoring and Management
  4. Monitoring NetBackup
  5. About NetBackup operator logs
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

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.

    To change the log level modify the operators-values.yaml file and upgrade the operators using the following command:

    helm upgrade --install operators operators-<version>.tgz -f operators-values.yaml -n netbackup-operator-system

  • 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.log file:

      kubectl exec -it <PrimaryServer/MediaServer-Pod-Name> -n <PrimaryServer/MediaServer-namespace> -- bash

  • (AKS-specific) 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, MediaServer and Request Router:

    • For primary server: kubectl describe PrimaryServer <PrimaryServer name> -n <PrimaryServer-namespace>

    • For media server: kubectl describe MediaServer<MediaServername> -n<MediaServer-namespace>

    • For request router: kubectl describe pod <request-router-pod-name> -n <PrimaryServer-namespace>

Feedback

Was this page helpful?
Previous

Telemetry reporting

Next

Monitoring Primary/Media server CRs

Feedback

Was this page helpful?