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. NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
  3. Deploying NetBackup
  4. About primary server CR and media server CR
  5. After installing primary server CR
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

After installing primary server CR

Note the following points:

  • The primary server CR will create a pod, a statefulset, a load balancer service, a configmap, a persistent volume claim for log volume, and a persistent volume claim for catalog volume.

  • Initially pod will be in not ready state (0/1) when installation is going on in the background. Check the pod logs for installation progress using the following command:

    kubectl logs <primary-pod-name> -n <namespace>

    Primary server can be considered as successfully installed and running when the primary server pod's state is ready (1/1) and the Statefulset is ready (1/1).

  • You can access the NetBackup webUI using the primary server hostname that was specified in the primary server CR status in Primary server details section.

    For example, if the primary server hostname is nbu-primary, then you can access the webUI at https://nbu-primary/webui/login.

Feedback

Was this page helpful?
Previous

About primary server CR and media server CR

Next

After Installing the media server CR

Feedback

Was this page helpful?