NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Best practices for disaster recovery
- Oracle database backups
- File system backups
- Oracle database: Cold backup
- Oracle database: Export backups
- Scheduling the oracle database export
- Oracle database: On demand backup
- Restoring the NetBackup IT Analytics system
- Import the oracle database
- Manual steps for database import / export using data pump
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- About automating host group management
- Task overview: managing host groups in bulk
- Preparing to use PL/SQL utilities
- General utilities
- Categorize host operating systems by platform and version
- Identifying a host group ID
- Move or copy clients
- Organize clients by attribute
- Move host group
- Delete host group
- Move hosts and remove host groups
- Organize clients into groups by backup server
- Merge duplicate backup clients
- Bulk load utilities
- Veritas NetBackup utilities
- Automate NetBackup utilities
- Organize clients into groups by management server
- Set up an inactive clients group
- Set up a host group for clients in inactive policies
- Set up clients by policy
- Set up clients by policy type
- IBM Tivoli storage manager utilities
- Set up clients by policy domain
- Set up clients by IBM Tivoli storage manager instance
- Scheduling utilities to run automatically
- Attribute management
- Attribute bulk load utilities
- Attribute naming rules
- Rename attributes before upgrading
- Load host attributes and values
- Load attributes and values and assign to hosts
- Load array attributes and values and assign to arrays
- Overview of application attributes and values
- Load application database attributes and values
- Load MS Exchange organization attributes and values
- Load LUN attributes and values
- Load switch attributes and values
- Load port attributes and values
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the portal
- System configuration in the portal
- System configuration: functions
- Navigation overview
- System configuration parameter descriptions: Additional info
- Anomaly detection
- Data collection: Capacity chargeback
- Database administration: database
- Host discovery: EMC Avamar
- Host discovery: Host
- Events captured for audit
- Custom parameters
- Adding/editing a custom parameter
- Portal customizations
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for File Analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- 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
- About debugging NetBackup IT Analytics
- Turn on debugging
- Database logging
- Portal and data collector log files - reduce logging
- Database SCON logging - reduce logging
- Refreshing the database SCON log
- Logging user activity in audit.log
- Logging only what a user deletes
- Logging all user activity
- Data collector log files
- Data collector log file organization
- Data collector log file naming conventions
- General data collector log files
- Find the event / meta collector ID
- Portal log files
- Database log files
- Installation / Upgrade log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- SSL certificate configuration
- SSL implementation overview
- Obtain an SSL certificate
- Update the web server configuration to enable SSL
- Configure virtual hosts for portal and / or data collection SSL
- Enable / Disable SSL for a Data Collector
- Enable / Disable SSL for emailed reports
- Test and troubleshoot SSL configurations
- Create a self-signed SSL certificate
- Configure the Data Collector to trust the certificate
- Keystore file locations on the Data Collector server
- Import a certificate into the Data Collector Java keystore
- Keystore on the portal server
- Add a virtual interface to a Linux server
- Add a virtual / secondary IP address on Windows
- Portal properties: Format and portal customizations
- Introduction
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for file analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- Configuring LDAP to use active directory (AD) for user group privileges
- Data retention periods for SDK database objects
- Data retention periods for SDK database objects
- Find the domain ID and database table names
- Retention period update for SDK user-defined objects example
- SDK user-defined database objects
- Capacity: default retention for basic database tables
- Capacity: default retention for EMC Symmetrix enhanced performance
- Capacity: Default retention for EMC XtremIO
- Capacity: Default retention for Dell EMC Elastic Cloud Storage (ECS)
- Capacity: Default retention for Windows file server
- Capacity: Default retention for Pure Storage FlashArray
- Cloud: Default retention for Amazon Web Services (AWS)
- Cloud: Default retention for Microsoft Azure
- Cloud: Default retention for OpenStack Ceilometer
- Configure multi-tenancy data purging retention periods
- Troubleshooting
- Appendix A. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
- About Transport Layer Security (TLS)
- TLS in Oracle environment
- Configure TLS in Oracle with NetBackup IT Analytics on Linux in split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Linux in non-split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Windows in split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Windows in non-split architecture
- Configure TLS in user environment
Portal log files
Key log files are managed by a logging subsystem, which manages the log size, and rolls and deletes old files. Log files are used only as an audit trail for troubleshooting, so they can be deleted safely.
Locations in this table represent the default locations, but these may have been modified for your environment.
Table: Portal Log Files
Log File Name | Default Location | Description |
|---|---|---|
access.log | C:\opt\apache\logs /opt/apache/logs | Standard Web server access log.Use this log to analyze request processing time, request method, page hit count, and session activity. |
aptareagent-access*.log | C:\opt\apache\logs /opt/apache/logs | Standard Web Server access log. Logs all http transactions between the Data Collector and the Web Server. |
aptareagent-error*.log | C:\opt\apache\logs /opt/apache/logs /opt/tomcat/logs | Standard Web Server error log file. Logs http transaction errors between the Data Collector and the Web Server. |
aptareportal-access*.log | C:\opt\apache\logs /opt/apache/logs | Standard Web Server access log. Logs all http transactions between the browser based Portal application and the Web Server. |
aptareportal-error*.log | C:\opt\apache\logs /opt/apache/logs | Standard Web Server error log file. Logs http transaction errors between the browser-based Portal application and the Web Server. |
aptareStartup.log | /opt/aptare/logs | Contains startup and shutdown information for the Portal services (e.g., from running /opt/aptare/bin/xxx start|stop), If a service fails to start, check this log file for details. |
audit.log | C:\opt\tomcat\logs\ /opt/tomcat/logs/ | By default, logs portal login requests and user impersonations in the Portal web browser window. Modifications can be made to log additional user activity. |
catalina.out | C:\opt\tomcat\aptare-instances\portal\logs /opt/tomcat/aptare-instances/portal/logs | For Tomcat, this is the standard destination log file for System.out and System.err console messaging. |
datarcvr*.log | C:\opt\tomcat\logs /opt/tomcat/logs | Detailed logging for the data receiver - the servlet that receives data from the Data Collectors on the Primary Server(s). Logs Data Collector connection requests/issues, data received, and database interaction. |
error.log | C:\opt\apache\logs /opt/apache/logs | Standard Web Server error log file. |
portal*.log | C:\opt\tomcat\logs\ /opt/tomcat/logs/ | Detailed logging for the Portal servlet. Logs portal login requests, user impersonations, portal reports that are run - basically all actions in the Portal web browser window. Database problems are displayed as SQL exceptions and often list the associated Oracle error number (ORA nnn). |
stderr.log | C:\opt\tomcat\logs\ /opt/tomcat/logs/ | High-level log messaging for Tomcat. |
Tomcat Standard Log Files (Portal) | ||
admin*.log | C:\opt\tomcat\aptare-instances\portal\logs /opt/tomcat/aptare-instances/portal/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to admin in the name of the file. |
catalina*.log | C:\opt\tomcat\aptare-instances\portal\logs /opt/tomcat/aptare-instances/portal/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to catalina in the name of the file. |
host-manager*.log | C:\opt\tomcat\aptare-instances\portal\logs /opt/tomcat/aptare-instances/portal/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to host-manager in the name of the file. |
manager*.log | C:\opt\tomcat\aptare-instances\portal\logs /opt/tomcat/aptare-instances/portal/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to manager in the name of the file. |
Tomcat Standard Log Files (Data Receiver) | ||
admin*.log | C:\opt\tomcat\aptare-instances\agent\logs /opt/tomcat/aptare-instances/agent/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to admin in the name of the file. |
catalina*.log | C:\opt\tomcat\aptare-instances\agent\logs /opt/tomcat/aptare-instances/agent/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to catalina in the name of the file. |
host-manager*.log | C:\opt\tomcat\aptare-instances\agent\logs /opt/tomcat/aptare-instances/agent/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to host-manager in the name of the file. |
manager*.log | C:\opt\tomcat\aptare-instances\agent\logs /opt/tomcat/aptare-instances/agent/logs | Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to manager in the name of the file. |