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. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section IV. Maintenance
  4. Troubleshooting
  5. Troubleshooting EKS-specific issues
  6. Resolving the primary server connection issue
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Resolving the primary server connection issue

NetBackup operator pod logs displays the following error:

Failed to connect the Primary server. "error": 
"Get \"https://abc.xyz.com:*/netbackup/security/cacert\": 
dial tcp: i/o timeout

The above error appears due to the following reasons:

  • Operator, primary server and media server pod must have been started in different availability zones.

  • Load balancer IP address and node on which primary server pod have started are in different availability zones.

  • Load balancer created for NetBackup load balancer service is in failed state.

  • FQDN to IP address given in networkLoadBalancer section in CR spec is not DNS resolvable.

To resolve the primary server connection issue, perform the following

  1. Delete the primary server and media server CR instance using the following command:

    helm uninstall cloudscale -n <env_namespace>

    Caution:

    Be cautious while performing this step.

  2. Fix the issue and provide appropriate details in CR specs in cloudscale-values.yaml file.
  3. Redeploy the NetBackup by reapplying the cloudscale-values.yaml file using the following command:

    helm upgrade --install cloudscale cloudscale-<version>.tgz -f cloudscale-values.yaml --namespace <env_namespace>

Feedback

Was this page helpful?
Previous

Troubleshooting EKS-specific issues

Next

NetBackup Snapshot Manager deployment on EKS fails

Feedback

Was this page helpful?