NetBackup and Veritas Appliances Hardening Guide
- Top recommendations to improve your NetBackup and Veritas appliances security posture
- Steps to protect Flex Appliance
- Managing multifactor authentication
- Managing multifactor authentication on a primary or a media server instance
- Managing multifactor authentication on a WORM storage server
- Managing single sign-on (SSO)
- About lockdown mode
- Configuring an isolated recovery environment using the web UI
- Steps to protect NetBackup Appliance
- About single sign-on (SSO) authentication and authorization
- About authentication using smart cards and digital certificates
- About data encryption
- About forwarding logs to an external server
- Steps to protect NetBackup
- About multifactor authentication
- Configure NetBackup for single sign-on (SSO)
- Configure user authentication with smart cards or digital certificates
- Workflow to configure multi-person authorization for NetBackup operations
- Access codes
- Workflow to configure immutable and indelible data
- Add a configuration for an external CMS server
- Configuring an isolated recovery environment on a NetBackup BYO media server
- About FIPS support in NetBackup
- Workflow for external KMS configuration
- Workflow to configure data-in-transit encryption
- Workflow to use external certificates for NetBackup host communication
- About certificate revocation lists for external CA
- Configuring an external certificate for a clustered primary server
- Configuring a NetBackup host (media server, client, or cluster node) to use an external CA-signed certificate after installation
- Configuration options for external CA-signed certificates
- ECA_CERT_PATH for NetBackup servers and clients
- About protecting the MSDP catalog
- How to set up malware scanning
- About backup anomaly detection
- Steps to protect NetBackup Flex Scale
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Support for immutability in NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- About multifactor authentication
- About single sign-on (SSO) configuration
- Steps to protect Access Appliance
- FIPS 140-2 conformance for Access Appliance
- Managing the login banner using the UI
- Managing the password policy using the UI
- Support for immutability in Access Appliance
- About system certificates on Access Appliance
- About single sign-on (SSO) configuration
- Configuring user authentication using digital certificates or smart cards
- About multifactor authentication
- Configuring an isolated recovery environment using the command line
- Forwarding logs to an external server
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, such as Database corruption.
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.