NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Introducing NetBackup
- Administering NetBackup licenses
- Registering with Veritas Alta View
- Introducing NetBackup
- Section II. Monitoring and notifications
- Monitoring NetBackup activity
- Activity monitor
- Job monitoring
- Troubleshooting the viewing and managing of jobs
- Device monitor
- Notifications
- Monitoring NetBackup activity
- Section III. Configuring hosts
- Managing host properties
- Managing credentials for workloads and systems that NetBackup accesses
- Add a credential for CyberArk
- Managing deployment
- Section IV. Configuring storage
- Overview of storage options
- Configuring storage units
- Configuring disk storage
- Integrating MSDP Cloud and CMS
- Managing media servers
- Managing tape drives
- Staging backups
- Troubleshooting storage configuration
- Section V. Configuring backups
- Overview of backups in the NetBackup web UI
- Managing protection plans
- Managing classic policies
- Protecting the NetBackup catalog
- Catalog backups
- Managing backup images
- Pausing data protection activity
- Section VI. Managing security
- Security events and audit logs
- Managing security certificates
- Managing host mappings
- Configuring multi-person authorization
- Managing user sessions
- Configuring multi-factor authentication
- Managing the global security settings for the primary server
- About trusted primary servers
- Using access keys, API keys, and access codes
- Configuring authentication options
- Managing role-based access control
- Disabling access to NetBackup interfaces for OS Administrators
- Section VII. Detection and reporting
- Section VIII. NetBackup workloads and NetBackup Flex Scale
- Section IX. Disaster recovery and troubleshooting
- Section X. Other topics
- Additional NetBackup catalog information
- About the NetBackup database
How a backup anomaly is detected
Consider the following example:
In an organization, around 1 GB of data is backed up every day for a given client and backup policy with the schedule type FULL. On a particular day, 10 GB of data is backed up. This instance is captured as an image size anomaly and notified. The anomaly is detected because the current image size (10 GB) is much greater than the usual image size (1 GB).
Significant deviation in the metadata is termed as an anomaly based on its anomaly score.
An anomaly score is calculated based on how far the current data is from the cluster of similar observations of the data in the past. In this example, a cluster is of 1 GB of data backups. You can determine the severity of anomalies based on their scores.
For example:
Anomaly score of Anomaly_A = 7
Anomaly score of Anomaly_B = 2
Conclusion - Anomaly_A is severer than Anomaly_B
NetBackup takes anomaly detection configuration settings (default and advanced if available) into account during anomaly detection.