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
  3. NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
  5. Deploying NetBackup
  7. Monitoring the status of the CRs
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

Monitoring the status of the CRs

You can view the status and other details of the primary server and media server CRs using the following commands:

  • kubectl get <PrimaryServer/MediaServer> -n <namespace> or

  • kubectl describe <PrimaryServer/MediaServer> <CR name> -n <namespace>

Following table describes the primary server CR and media server CR status fields:

Table:

Section

Field / Value

Description

Primary Server Details

Only one hostname and IP address for the respective primary server.

Host Name

Name of the primary server that should be used to access the web UI.

IP

IP address to access the primary server.

Version

This indicates that the NetBackup primary server version is installed.

Media Server Details

Number of hostname and IP address is equal to the replica count mentioned CR spec.

Host Name

Name of the media server.

IP

IP address to access the media server.

Version

This indicates that the NetBackup media server version is installed.

Attributes

Resource Name

Statefulset name of the respective server.

Primary/Media server name

Name of the primary server or media server deployed.

Config checker status

Indicates the status of the config checker as passed, failed, or skipped. For more information on the Config-Checker, See How does the Config-Checker utility work.

SHA Fingerprint

Represents the SHA key fingerprint of the NetBackup primary server.

Note:

SHAFingerprint represents the SHA256 CA certificate fingerprint of the primary server.

Error Details

Code

A code assigned to an error encountered during the CR deployment or during the config-check operation. For more information on the error, refer to the NetBackup Status Code Reference Guide.

Message

Message that describes the respective error code.

State

Success /Paused /Failed /Running

Current state of the custom resource, from one of the following:

  • Success: Indicates that the deployment of Primary/Media Custom Resource (CR) is successful. However, this does not mean that the installation of the NetBackup primary/media servers is successful. The primary or media server StatefulSets and/or the pods might or might not be in a ready state, irrespective of that the Primary/Media CR state will show as Success.

  • Paused: Indicates that the reconciler is in paused state and deployment of a CR is paused.

  • Failed: Indicates that the deployment of a CR failed with errors. However this does not mean failed installation of the NetBackup Server. Errors can be analyzed from the Operator logs or CR describe.

  • Running: Indicates that the CR deployment is in progress and the resources are getting created.

Events

INIT/FAILOVER/UPGRADE

The events like INIT, FAILOVER and UPGRADE are logged in here.

The details of these events can also be added.

Feedback

Was this page helpful?
Previous

After Installing the media server CR

Next

Updating the CRs

Feedback

Was this page helpful?