Please enter search query.
Search <book_title>...
NetBackup IT Analytics System Administrator Guide
Last Published:
2023-08-01
Product(s):
NetBackup IT Analytics (11.1)
- 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
Configuring the cache time for reports
The cache retains reporting data and if it reaches capacity, it frees up space for new reports by purging the data for the least frequently used reports. Purging also occurs when a cached report is more than 24 hours old. You can change the value by adding a line to the portal.properties file.
Revise the cache purge time for reporting data using the portal.properties file:
Linux:
/opt/aptare/portalconf/portal.properties
Windows:
C:\opt\aptare\portalconf\portal.properties
Add the following line:
portal.reports.cache.timeOut
The unit of measure is seconds.
Restart the Tomcat Portal services.