Please enter search query.
Search <book_title>...
Veritas NetBackup™ Read This First Guide for Secure Communications
Last Published:
2018-05-10
Product(s):
NetBackup (8.1)
- NetBackup Read This First for Secure Communications
- About secure communications in NetBackup
- How host ID-based certificates are deployed during installation
- How certificates are deployed on hosts during upgrades
- How secure communication works with master server cluster nodes
- When an authorization token is required during certificate deployment
- Why do you need to map host names (or IP addresses) to host IDs
- How to reset host attributes or host communication status
- What has changed for catalog recovery
- What has changed with Auto Image Replication
- How the hosts with revoked certificates work
- How communication happens when a host cannot directly connect to the master server
- Are security certificates backed up
- How communication with legacy media servers happens in the case of cloud configuration
- How NetBackup 8.1 hosts communicate with NetBackup 8.0 and earlier hosts
- Communication failure scenarios
- Secure communication support for other hosts in NetBackup domain
Failure during communication with 8.0 or earlier hosts
If insecure communication is not allowed in NetBackup, communication with 8.0 and earlier hosts fails. For successful communication with 8.0 and earlier NetBackup hosts, use one of the following methods:
In the NetBackup Administration Console on the master server host, select the Security Management > Global Security > Hosts > Enable insecure communication with NetBackup 8.0 and earlier hosts option.
On the master server host, run the following command: nbseccmd -setsecurityconfig -insecurecommunication on.