NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- Categorize host operating systems by platform and version
- Bulk load utilities
- Automate NetBackup utilities
- Scheduling utilities to run automatically
- Attribute management
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the Portal
- Custom parameters
- Performance profile schedule customization
- LDAP and SSO authentication for Portal access
- Change Oracle database user passwords
- Integrate with CyberArk
- Tuning NetBackup IT Analytics
- Working with log files
- Portal and data collector log files - reduce logging
- Data collector log file naming conventions
- Portal log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- Configure virtual hosts for portal and / or data collection SSL
- Keystore on the portal server
- Portal properties: Format and portal customizations
- Data retention periods for SDK database objects
- Data aggregation
- Troubleshooting
- Appendix A. Kerberos based proxy user's authentication in Oracle
- Appendix B. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
- Appendix C. NetBackup IT Analytics for NetBackup on Kubernetes and appliances
TLS in Oracle environment
A network connection that is initiated over TLS requires a TLS handshake between the client and server before performing the authentication. The handshake process includes the following:
The client and server choose the cipher suites and the encryption algorithms to use for data transfers.
To verify the identity of the server, the server sends its certificate to the client and the client verifies whether it was signed by a trusted CA.
If a client authentication is required, the client sends its certificate to the server, which the server verifies whether it was signed by a trusted CA.
The client and server use public key cryptography to exchange key information and each generates a session key. Both the keys are generally used for data encryption during a single communication session. Session keys are typically used to encrypt network traffic. A client and a server can negotiate a session key at the beginning of a session and that key is used to encrypt all the network traffic between the parties of that session. A new session key is generated if the client and server communicate over a new session. The subsequent communications between the client and server are encrypted and decrypted with the use of the session key and the negotiated cipher suite.
Authentication process includes the following:
The user initiates a Oracle Net connection from the client to the server using TLS.
TLS performs the handshake between the client and the server.
After a successful handshake, the server verifies whether the user has appropriate authorization to access the database.