NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Section II. Monitoring and notifications
- Monitoring NetBackup activity
- Activity monitor
- Job monitoring
- Troubleshooting the viewing and managing of jobs
- Device monitor
- Notifications
- Registering the data collector
- Monitoring NetBackup activity
- Section III. Configuring hosts
- Managing host properties
- Busy file settings properties
- Client attributes properties
- Client settings properties for UNIX clients
- Client settings properties for Windows clients
- Data Classification properties
- Default job priorities properties
- Encryption properties
- Exchange properties
- Exclude list properties
- Fibre transport properties
- General server properties
- Global attributes properties
- Logging properties
- Media properties
- Network settings properties
- Port ranges properties
- Preferred network properties
- Resilient network properties
- Restore failover properties
- Retention periods properties
- Scalable Storage properties
- Servers properties
- SharePoint properties
- SLP settings properties
- Managing credentials for workloads and systems that NetBackup accesses
- Managing deployment
- Managing host properties
- Section IV. Configuring storage
- Overview of storage options
- Configuring disk storage
- Integrating MSDP Cloud and CMS
- About configuring disk pool storage
- About the MSDP object store
- Managing media servers
- Configuring storage units
- Managing robots and tape drives
- Add a robot to NetBackup manually
- Managing robots
- Managing tape drives
- Managing tape media
- About adding volumes
- Managing volumes
- About recycling a volume
- About injecting and ejecting volumes
- Managing volume pools
- Managing volume groups
- Inventorying robots
- 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
- Minimizing security configuration risk
- Configuring multi-person authorization
- Managing user sessions
- Configuring multifactor 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
- Detecting anomalies
- About backup anomaly detection
- Malware scanning
- Usage reporting and capacity licensing
- Detecting anomalies
- Section VIII. NetBackup workloads and NetBackup Flex Scale
- Section IX. Administering NetBackup
- Management topics
- Managing client backups and restores
- About client-redirected restores
- Section X. Disaster recovery and troubleshooting
- Section XI. Other topics
- Additional NetBackup catalog information
- About the NetBackup database
- About the NetBackup database installation
- Post-installation tasks
- Using the NetBackup Database Administration utility on Windows
- Using the NetBackup Database Administration utility on UNIX
View backup anomalies
NetBackup can now detect anomalies in backup metadata. It can detect any unusual job data in the data backup flow. For example, it can detect a file count or a file size that is different than the usual count or size.
Consider the following example:
An anomaly of the image size type is displayed as 100MB (Usual 350MB, 450MB). This information implies that the current image size that is reported as anomaly is 100 MB. However, the usual image size range is 350 MB - 450 MB that is derived from the analysis of past data. Because of the significant difference between the current image size and usual image size range, NetBackup notifies it as an anomaly.
See About backup anomaly detection.
Note:
Anomaly count of 0
indicates that there are no anomalies generated or that the anomaly detection services are not running.
To view backup anomalies
- On the left, select Detection and reporting > Anomaly detection > Backup anomalies.
The following columns are displayed:
Job ID - ID of the job for which the anomaly is detected
All child jobs and the associated anomaly details are also shown when you expand the parent job.
Severity - Severity of the anomalies that are notified for this job
Asset name - Name of the NetBackup client where the anomaly is detected
Summary - For the parent job, details like types of anomalies, number of anomalies, and increase or decrease in the number of anomalies are shown.
For child jobs, types of anomalies are shown.
Anomaly type - Type of the anomaly such as Image entropy, Job metadata, Suspicious file extension, Client offline
Backup selection - The backup selection (client or file to be backed up) that is specified in the policy
Policy name - The policy name of the associated backup job
Policy type - The policy type of the associated backup job
Schedule type - The schedule type of the associated backup job
Impacted number of jobs - The number jobs for which anomalies are detected
Review status - The anomaly status that indicates whether the detected anomaly is reported as a false positive or an actual anomaly, or it can be ignored.
Last updated - The date and time when the anomaly status is updated
- Select the job ID to see the job details in the Activity monitor. Expand a parent job to see the details of each child job.
- You can perform the following actions on the anomaly record:
Select Report as false positive if the anomaly is a false positive. Similar anomalies are not shown in the future.
The Review status of the anomaly record appears as False positive.
Select Confirm as anomaly when you want to take some action on the anomaly condition.
The Review status of the anomaly record appears as Anomaly.
Select Mark as ignore when you can ignore the anomaly condition.
The Review status of the anomaly record appears as Ignore.