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

    For more information, see Persistent Volumes Reclaiming

  • Provisioner check:

    • Primary server: This will verify that the PV created using the storage class is provisioned using the efs.csi.aws.com driver, that is, AWS Elastic file system (EFS) for catalog volume. This will verify that the storage type provided is Amazon Elastic Block Store(Amazon EBS) for data and log volume. If any other driver type is used, the Config-Checker fails.

    • Media server: This will verify that the storage type provided is Amazon Elastic Block Store (Amazon EBS) for data and log volume. Config-Checker fails if this requirement is not met for media server.

  • 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:

      • Data volume size: 30Gi

      • Catalog volume size: 100Gi

      • Log volume size: 30Gi

    • Media server:

      • Data volume size: 50Gi

      • Log volume size: 30Gi

  • AWS Load Balancer Controller add-on check:

    This check verifies if the AWS Load Balancer Controller add-on is installed in the cluster. This load balancer controller is required for load balancer in the cluster. If this check fails, user must deploy the AWS Load Balancer Controller add-on

  • Volume expansion check:

    This check verifies the storage class name given for Primary server data and log volume and for Media server data and log volumes has AllowVolumeExpansion = true. If Config-Checker fails with this check then it gives a warning message and continues with deployment of NetBackup media servers.

Feedback

Was this page helpful?
Previous

Webhooks validation execution details

Next

Config-Checker execution and status details

Feedback

Was this page helpful?