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. Assessing cluster configuration before deployment
  4. How does the Config-Checker utility work
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

How does the Config-Checker utility work

The Config-Checker utility performs checks on the deployment environment to verify that the environment meets the requirements, before starting the primary server and media server deployments.

How does the Config-Checker works:

  • RetainReclaimPolicy check:

    This check verifies that the storage classes used for PVC creation in the CR have reclaim policy as Retain. The check fails if any of the storage classes do not have the Retain reclaim policy.

    Persistent Volumes Reclaiming

  • MinimumVolumeSize check:

    This check verifies that the PVC storage capacity meets the minimum required volume size for each volume in the CR. The check fails if any of the volume capacity sizes does not meet the requirements.

    Following are the minimum volume size requirements:

    • Primary server:

      • Catalog volume size: 100Gi

      • Log volume size: 30Gi

      • Data volume size: 30Gi

    • Media server:

      • Data volume size: 50Gi

      • Log volume size: 30Gi

  • Provisioner check:

    This check verifies that the provisioner type used in defining the storage class is Azure disk, for the volumes in Media servers. If not the config-checker will fail. This check verifies that the provisioner type used in defining the storage class is not Azure files for the volumes in Media servers. That is data and log volumes in case of Media server.

  • Volume expansion check: This check verifies the storage class name given for Primary server log, data and catalog volume and for Media server data and log volumes has AllowVolumeExpansion = true. If config check fails with this check then it gives a warning message and continues with deployment of NetBackup media and primary servers.

Feedback

Was this page helpful?
Previous

Assessing cluster configuration before deployment

Next

Config-Checker execution and status details

Feedback

Was this page helpful?