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
General Reporting Issues
Certain reports that include graphs may result in a report failing to load due to an "out-of-memory: Java heap space" error. This may occur when generating a report for a large set of data or exporting it to a PDF. For example, the following reports are known to occasionally encounter this condition: Tape Library and Drive Utilization for one year grouped by hours, Job Volume Summary for three years of daily data, and Data Domain Filesystem Capacity & Forecast for two months grouped by hours.
To work around this condition, try these changes in the Report Designer:
reduce the number of selected objects (for example, servers or arrays)
limit the time period to a shorter timeframe
select a less granular "group by" option (for example, by days instead of by hours)
Typically, this is a Data Collector issue.
File system is out of disk space.