NetBackup and Veritas Appliances Hardening Guide
- Top recommendations to improve your NetBackup and Veritas appliances security posture
- Steps to protect Flex Appliance
- Managing single sign-on (SSO)
- About lockdown mode
- Configuring an isolated recovery environment on a WORM storage server
- 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
- Configure NetBackup for single sign-on (SSO)
- Configure user authentication with smart cards or digital certificates
- 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
- Configure the DTE mode on a client
- How DTE configuration settings work in various NetBackup operations
- Modify the DTE mode on a backup image
- 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
- Configuration options for external CA-signed certificates for a virtual name
- 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
Detecting backup anomalies on the media server
This topic provides the workflow and the procedure that enable the media server to detect backup anomalies.
By default, the anomaly detection algorithm runs on the NetBackup primary server. If you see any impact on the primary server because of the anomaly detection process, you can configure a media server to detect anomalies.
To enable the media server to detect backup anomalies
- Install the NetBackup media server software on your system (or upgrade the media server software).
- On the primary server, add anomaly proxy server details. The proxy server should be the media server where you want the anomaly algorithms to be run.
- (Optional) If you want to preserve the data that the primary server has gathered earlier, do the following:
Ensure that the nbanomalymgmt service is disabled using the web UI.
Ensure that the nbanomalymgmt service on the media server is stopped.
Go to the following directory:
On Windows: Install_Path\NetBackup\var\global
On UNIX: /usr/openv/var/global
The directory resides on the shared disk on a clustered primary server.
Copy the NB_Anomaly.db, NB_Anomaly.db-shm, and NB_Anomaly-wal files from the anomaly_detection folder on the primary server to the anomaly_detection folder on the media server.
You can copy the anomaly_config.conf file to preserve the automatic malware scan settings.
Start the nbanomalymgmt service on the media server.
- On the media server, start the nbanomalymgmt service manually. Use the following script:
- Configure the backup anomaly settings in the NetBackup web UI. NetBackup takes these settings into account during anomaly detection.
If any anomalies are detected, they are notified using the NetBackup web UI.
See View anomalies.