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
- 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
Anomaly detection
Anomaly detection helps to detect suspicious activity in backup operation through analysis of various backup attributes such as:
Backup image size
Number of files backed up
Kilobytes transferred
Deduplication rate
Backup job completion time
Any significant change in the above parameters detected during a backup job are reported as anomalies. The General section lists all the data protection tools for which you can enable anomaly detection.
While anomaly detection is enabled within your environment, you can exclude individual clients and NetBackup server from the detection by specifying the client or server names in comma separated values. The client name must match with the name configured in the NetBackup policy.
You must restart the Anomaly service after any changes made to the following Anomaly Detection fields to make the changes effective:
Enable Anomaly detection for Veritas NetBackup
Exclude Clients from Anomaly Detection
Exclude NetBackup Primary from Anomaly Detection
A popup message similar to the one below is displayed suggesting to restart the portal.