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 the media server CR
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

After Installing the media server CR

Note the following points:

  • The media server CR will create a pod, a statefulset, a configmap, a loadbalancer service, a persistent volume claim for data volume, and a persistent volume claim for log volume.

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

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

    Media server can be considered as successfully installed and running when the media server pod's state is ready (1/1), and the Statefulset is ready (1/1), for each replica count.

  • Details of media server name for each replica can be obtained from media server CR status by running the following command:

    kubectl describe <MediaServer_cr_name> -n <namespace>

Feedback

Was this page helpful?
Previous

After installing primary server CR

Next

Monitoring the status of the CRs

Feedback

Was this page helpful?