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
- Configuring AD/LDAP
- Configuring single sign-on (SSO) using security assertion markup language (SAML)
- 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
- Troubleshooting
- Appendix A. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
Support LDAP over SSL
If you are using a self-signed certificate or an AD certificate from a non-standard certificate authority (CA), you need a keystore having the AD certificate and update the LDAP configuration in the portal.properties
file.
You can skip this procedure if you are using a standard certificate from a CA.
- To generate the keystore file:
On Linux run:
/usr/java/bin/keytool -import -file certificate_file -alias alias_name -keystore keystore_file
On Windows run:
C:\opt\jdk\bin\keytool -import -file certificate_file -alias alias_name -keystore keystore_file
In the above commands:
certificate_file is the file path for the AD/LDAP certificate.
alias_name is the unique alias explicitly assigned to the certificate to ensure there are no conflicts with the existing aliases. This is an essential parameter when importing multiple certificates.
keystore_file is the target file path for the keystore file being generated.
Sample commands for keystore file generation:
Linux:
/usr/java/bin/keytool -import -file HQLDAP.crt -alias HQCertAlias -keystore /opt/aptare/portalconf/portal.keystore
Windows:
C:\opt\jdk\bin\keytool.exe -import -file HQLDAP.crt -alias HQCertAlias -keystore C:\opt\aptare\portalconf\portal.keystore
- This step applies only to Linux systems.
Change the permission of
/opt/aptare/portalconf/portal.keystore
to 750, ownership to aptare, and group ownership to Tomcat user.# chmod 750 /opt/aptare/portalconf/portal.keystore # chown aptare:tomcat /opt/aptare/portalconf/portal.keystore
- On the Portal Server, change the following configuration settings in the
portal.properties
file located at:Windows:
C:\opt\aptare\portalconf\portal.properties
Linux:
/opt/aptare/portalconf/portal.properties
ldap.url=ldaps://<AD_URL>:636 ldap.keystore=<KEYSTORE_PATH_CREATED_IN_STEP_1> ldap.keystore.password=<KEYSTORE_PASSWORD> ldap.keystore.password.encrypted=
Note:
After restarting Portal Tomcat Service,
ldap.keystore.password
becomes empty and encrypted password is set intoldap.keystore.password.encrypted
. - Restart the Portal Tomcat service.
In Linux environment run # /opt/aptare/bin/tomcat-portal restart.
In Windows environment, use the Windows Services Console to locate and restart the Portal Tomcat service.