What to check if Online Backup and Recovery Manager does not send status events for bare-metal backup jobs?

On this page

Summary

This problem may be caused either by Online Backup and Recovery Manager (OBRM) backup service or WMI (Windows Management Instrumentation) problems. Also, the problem may be caused by the precedence of starting these services. WMI service should always start before OBRM backup service.

What to check

  1. Check if service “Offsite Online Backup Service” (SAgentservice) runs under the proper user credentials.

    These should be either Local System credentials or credentials of a local administrator.

    • press Win+R, enter services.msc, and then click OK.

    • locate “Offsite Online Backup service” and click Properties (or check column “Log On As”)

      Service list

      Service properties

  2. Check if service “Windows Management Instrumentation” is running (in Services window opened at step 1):

    Service list

    If the service is not running, start it.

  3. Run the attached tool “ManagementEventWatcherTester” as Administrator to check if the WMI service works without issues.

    Run as administrator

    It will display a command line window with text “Started…”

    Event watcher

    • open Notepad, and the text “processStartEvent_EventArrived” should appear:

      Event start

    • close Notepad and the application will show processStopEvent_EventArrived.

      Event stop

      If the application does not show the above messages, there may be problems with WMI service on the machine.

      If everything works as described above, the problem may be caused by the precedence of starting these services. WMI service should always start before Offsite Online Backup Service.

  4. To change precedence (set dependency) of the starting services:

    1. Open the Command Prompt as administrator.

    2. Enter sc config 'sagentservice' depend=winmgmt, and then press Enter.

      The following message should appear: sc ChangeServiceConfig SUCCESS.

    3. More information is provided here.

  5. Restart the computer, and then check OBRM logs (SAgent.Service.log) if SAgentService does not return any errors.