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. Troubleshooting
  4. Local connection is getting treated as insecure connection
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Local connection is getting treated as insecure connection

The following error message is displayed when un-necessary audit events are get logged only when reverse dns lookup is enabled for primary and media Load Balancer service:

Host 'eaebbef2-57bc-483b-8146-1f6616622276' is trying to connect to host '<serverName>.abc.com'. The connection is dropped, because the host '<serverName>.abc.com' now appears to be NetBackup 8.0 or earlier

Primary and media servers are referred with multiple IP's inside the pod (pod IP/LoadBalancer IP). With reverse name lookup of IP enabled, NetBackup treats the local connection as remote insecure connection.

To resolve the audit events issue, disable the reverse name lookup of primary and media Load Balancer IP.

Feedback

Was this page helpful?
Previous

NetBackup messaging queue broker take more time to start

Next

Issue with capacity licensing reporting which takes longer time

Feedback

Was this page helpful?