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
Database administration: database
Large index number leaf blocks: In large environments, to improve the performance of index builds, a system parameter can be configured to define the number of leaf blocks for a large index. The default value is 10,000 leaf blocks. This parameter configures the number of leaf blocks in a database index.
Maximum number of large indexes for rebuild: To improve the performance of index recreation, modify this parameter to change the number of large database indexes that will be processed in a single run. The default value is 10.
Rebuild indexes schedule (days): In large environments, if report generation performance begins to degrade, database indexes can be built more frequently. The default is to rebuild indexes every 60 days.
Maximum time in minutes for large index rebuilds: To improve the performance of index recreation, configure this parameter to define the number of minutes the index rebuild should run. The default value is 10 minutes. If the rebuild takes longer than this time, the job will stop. In very large environments, it may be necessary to increase this time to accommodate large indexes.