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. Veritas NetBackup™ Security and Encryption Guide
  3. Security management in NetBackup
  4. About global security settings
  5. About communication with 8.0 or earlier host in multiple NetBackup domains
Veritas NetBackup™ Security and Encryption Guide

About communication with 8.0 or earlier host in multiple NetBackup domains

This section provides information on what is the impact of the Enable insecure communication with 8.0 and earlier hosts option on the host communication when one of the NetBackup hosts is in multiple domains.

Consider the following scenario:

  • Host A is of version 8.1, which is present in multiple NetBackup domains called M1 and M2.

  • Host B is of version 8.0, which is present in a NetBackup domain called M3.

  • The Enable insecure communication with 8.0 and earlier hosts option is cleared on master server M1, which means hosts that are associated with M1 cannot communicate with hosts that are 8.0 or earlier.

  • The Enable insecure communication with 8.0 and earlier hosts option is selected on master server M2, which means hosts that are associated with M2 can communicate with hosts that are 8.0 or earlier.

  • The configuration file (bp.conf file on UNIX or registry keys on Windows) for Host A contains 'M2' as the first entry in the master server list.

When Host A initiates communication with Host B, the status of the Enable insecure communication with 8.0 and earlier hosts option is verified for the first master server that appears in the configuration file of Host A, which is M2. As per the option set for M2, communication with 8.0 or earlier hosts is allowed. Therefore, communication between Host A and Host B is successful.

Feedback

Was this page helpful?
Previous

About insecure communication with 8.0 and earlier hosts

Next

Automatically mapping host ID to host names and IP addresses

Feedback

Was this page helpful?