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
Log File Names Based on Data Collector Generation
Throughout the NetBackup IT Analytics life cycle, some collectors have been upgraded to include new functionality and new Data Collectors have been designed with an improved architecture. The log file naming convention depends on the generation of the Data Collector that you are using. You do not need to know the generation of the Data Collector to find relevant log files.
When running a scheduled data collection, the following log files are created, depending on the generation of the Data Collector. For technical reasons, the following naming conventions are used for data collection logs:
older-generation collectors follow the convention, {scheduled,validation}/vendor.product/#META_ or {scheduled,validation}/vendor.product/EVENT_,where EVENT_ or META_ is prepended to the collector policy ID; for example, META_CA6EC7685A9E6330EC3BBFC0DD4811E4.
newer-generation collectors share a single file named with the main collector ID, for example, {scheduled,validation}/vendor.product/#<Collector_PolicyID>
Several log file names include a specific ID. This ID can be found in a System Administration report, Data Collection Schedule Summary.
See Find the event / meta collector ID.
/opt/aptare/mbs/logs/scheduled/dell.compellent /#META_EA1BA380E95F73C72A72B3B0792111E5 /META_EA1BA380E95F73C72A72B3B0792111E5.log
/opt/aptare/mbs/logs/scheduled/emc.avamar /#HQBackupCollector/HQBackupCollector.log