Search <book_title>...

NetBackup™ Release Notes

Last Published: 2022-02-03

Product(s): NetBackup (9.1)

NetBackup anomaly detection management service may not start after a full catalog restore

The NetBackup anomaly detection management (nbanomalymgmt) service may not start after a full catalog restore. This is typically observed when the service is up and running during the full catalog restore.

You may see the following errors in the nbanomalymgmt service log:

14:27:13.807 [8100.9844] <16> nbanomalymgmt: Error occurred while
 gathering data
14:27:13.808 [8100.9844] <2> nbanomalymgmt: State:[3], ExitCode:[0],
 WaitHint:[300000], CheckPoint:[2]
14:27:13.808 [8100.9844] <8> WaitForChildProc: Process [DETECTION]
 event handle is NULL
14:27:13.808 [8100.9844] <2> nbanomalymgmt: State:[3], ExitCode:[0],
 WaitHint:[300000], CheckPoint:[3]
14:27:13.808 [8100.9844] <8> WaitForChildProc: Process [ALERT]
 event handle is NULL
14:27:13.809 [8100.23948] <4> nbanomalymgmt: Worker thread exited.
 So shutting down the service.

During a full catalog restore, the nbanomalymgmt service is running, the anomaly detection database (NB_Anomaly.db) may get corrupted, and that can cause the issue.

Workaround:

If the catalog restore is already complete with the nbanomalymgmt service in the running state and that has caused the database to be corrupted and in turn the service cannot start, you need to do the following as a workaround:

Stop the nbanomalymgmt service before you restore the catalog to an alternate location or during disaster recovery (DR).
Run the following command:
On Linux: /usr/openv/netbackup/bin/nbanomalymgmt -stop
On Windows: <install_path>\\NetBakcup\\bin\\nbanomalymgmt -stop
Or from the Windows Service Control Manager, Stop "NetBackup Anomaly Detection Management Service".
Delete all files under the anomaly_detection folder. The location of the folder is as follows:
On Linux: /usr/openv/var/global/anomaly_detection
On Windows: <install_path>\\NetBackup\\var\\global\\anomaly_detection
Restore the catalog to an alternate location and copy all files under the anomaly_detection folder to the following locations.
On Linux: /usr/openv/var/global/anomaly_detection
On Windows: <install_path>\\NetBackup\\var\\global\\anomaly_detection
After the restore completes, start the nbanomalymgmt service using the following command:
On Linux: /usr/openv/netbackup/bin/nbanomalymgmt -start
On Windows: <install_path>\\NetBakcup\\bin\\nbanomalymgmt -start
Alternatively, do the following: Go to Windows Service Control Manager and start NetBackup Anomaly Detection Management Service.

To avoid the anomaly detection database corruption during catalog restore:

Stop the nbanomalymgmt service before performing full catalog restore or disaster recovery. Run the following command:
For Linux:/usr/openv/netbackup/bin/nbanomalymgmt -stop
For Windows:<NetBackup Install Location>\\NetBakcup\\bin\\nbanomalymgmt -stop
Alternatively, do the following: From the Windows Service Control Manager, stop NetBackup Anomaly Detection Management Service.
Delete all files under the anomaly_detection folder. The location of the folder is as follows:
On Linux: /usr/openv/var/global/anomaly_detection
On Windows: <install_path>\\NetBackup\\var\\global\\anomaly_detection
After the restore completes, start the nbanomalymgmt service using the following command:
On Linux: /usr/openv/netbackup/bin/nbanomalymgmt -start
On Windows: <install_path>\\NetBakcup\\bin\\nbanomalymgmt -start
Alternatively, do the following: Go to Windows Service Control Manager and start NetBackup Anomaly Detection Management Service.