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
How the hosts with revoked certificates work
Host ID-based certificates can be revoked by the master server administrator for various reasons. A Certificate Revocation List (CRL) containing information about the revoked certificates is created by the master server and is periodically fetched by all hosts. The time interval to update the CRLs is determined by the certificate deployment security level on the master server.
During communication between hosts, CRLs are verified. The host that uses a revoked certificate is no longer trusted. Communication with such hosts is terminated.
For more information on CRLs, refer to the NetBackup Security and Encryption Guide.