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 I. Configurations
  4. Recommendations and Limitations
  5. Recommendations and limitations for Cloud Scale deployment
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Recommendations and limitations for Cloud Scale deployment

This section provides the list of recommendations and limitations for Cloud Scale to be noted.

Recommendations
  • Ensure that NetBackup clients or media servers outside AKS/EKS cluster are DNS resolvable with NetBackup Primary server load balancer FQDN:

    • For AKS: For the DNS name, you can add DNS entries in Private DNS.

    • For EKS: For the DNS name, you can use the Private IP DNS name amazon provided, or you can create DNS and Reverse DNS entries under Route53.

  • Ensure that you do not use primary server as a media server for use cases where data movement is required.

  • To use a cloud bucket as storage, it is recommended to create a new DiskPool with the cloud volume or bucket configured under the msdpscaleout storage server.

Limitations
  • Cloud Scale does not support Native Multifactor authentication.

  • DaemonSet scheduling:

    With NetBackup 10.5 or later, fluentbit DaemonSet's collect every pod's stdout/stderr logs for the nodes that the DaemonSets are scheduled on. However due to scheduling, some nodes would not get a DaemonSet pod on it due to the scheduling criteria (of having a major NetBackup pod on it). These pods on nodes without a schedule DaemonSet will not have their logs collected. These logs are non-crucial logs (but important to be aware of) such as infrastructure logs that you encounter in different configurations. However those logs are still available via standard Kubernetes log commands.

  • Fluentbit TLS errors:

    Following are the sample occasional logs that are commonly viewed on the fluentbit collector pod:

    [error] [input:forward:forward.0] could not accept new connection
    [error] [tls] error: unexpected EOF
    [error] [input:forward:forward.0] could not accept new connection
    [error] [tls] error: unexpected EOF
    [error] [input:forward:forward.0] could not accept new connection
    [error] [tls] error: unexpected EOF
    
    And this:
    [error] [/src/fluent-bit/src/tls/openssl.c:433 errno=104] Connection reset by peer
    [error] [tls] syscall error: error:00000005:lib(0):func(0):DH lib
    [error] [/src/fluent-bit/src/tls/openssl.c:433 errno=104] Connection reset by peer
    [error] [tls] syscall error: error:00000005:lib(0):func(0):DH lib
    [error] [/src/fluent-bit/src/tls/openssl.c:433 errno=104] Connection reset by peer
    [error] [tls] syscall error: error:00000005:lib(0):func(0):DH lib
    
  • Connection refused:

    Following are the sample occasional error messages that appear on startup of the fluentbit DaemonSet's and sidecars:

    [warn] [net] getaddrinfo(host='nb-fluentbit-collector-svc', err=4): Domain name not found
    [warn] [net] getaddrinfo(host='nb-fluentbit-collector-svc', err=4): Domain name not found
    [error] [output:forward:forward.0] no upstream connections available
    [error] [output:forward:forward.0] no upstream connections available
    

    The above error messages are due to collector having networking issues or not being fully up and accepting connections yet. These messages can be ignored if they are brief and not continuous.

  • Veritas Cloud Scale Technology deployment does not support DNAS.

Feedback

Was this page helpful?
Previous

Limitations of NetBackup deployment on Kubernetes cluster

Next

Configurations

Feedback

Was this page helpful?