Backup Exec service

The Backup Exec service monitors the status of backups that have been performed by Symantec Backup Exec. Using the Open Database Connectivity (ODBC) protocol, the Backup Exec service can monitor up to 50 jobs. 

Backup Exec can discover the following job types by N-able N-central and monitored by the Backup Exec service:

  • Backup
  • Catalog
  • Duplicate to Tape
  • Report
  • Restore
  • TestRun
  • Utility
  • Verify
Service Type ODBC
Instances on a Device 50
Supported Systems/Applications
  • Backup Exec version 9.x to 12.x
  • Backup Exec 2010 to 2012
  • Backup Exec 16
Device Class Server - Windows
Monitored By Windows agent or Windows probe
Timeout Value The time in seconds that the N-able N-central server waits before considering the ODBC connection a failure. The default is 5 seconds.
Failed Job Status List The list of Backup Exec job status codes that will make the service transition to a failed state.
Warning Job Status List The list of Backup Exec job status codes that will make the service transition to a warning state.
Job Timeout Job Timeout measured in hours. If the Backup Exec job has not run in the specified time, the Backup Exec service will transition to a failed status.
Scan Interval in Minutes The time between each scan. The default scan interval for Backup Exec is 30 minutes.
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.


Metric Name Description
Backup Exec Job Return Code A numeric value that indicates the status of the backup.
Elapsed Time The amount of time taken to perform the backup.
Number of directories backed up The details of the backup.
Number of files backed up
Number of files skipped
Number of files corrupted
Number of files in use
Total bytes backed up
Byte rate (MB per minute) The speed of the backup.

Backup Exec job status codes

You can view the return values for the associated job status on the status screen for the Backup Exec service. These values represent specific critical issues.

1 Job is terminal due to cancellation.
2 Job has been completed by the engine and is waiting on final disposition.
3 Job is terminal with success but there are some exceptions.
4 Job has been sent for execution.
5 Job is in a hold state.
6 Job is terminal with an error.
7 The schedule for the task is invalid.
8 The time window is mutually exclusive thus job will never run.
9 Job is eligible for dispatch and is late.
10 Date of job makes it eligible to run, but time is not in window.
11 DEPRECATE: Set as sub-status on READY job now.
12 The job needs to be dispositioned to an actual state.
13 The system forced recovery of the job.
14 Job has been disabled in the system.
15 The job will be restarted with checkpoint restart enabled, this value is only set in job history summary.
16 Job is currently running on server.
17 Job is eligible for dispatch.
18 The job has a due date in the future.
19 Job is terminal with success.
20 Job is ready, but another higher precedence task is eligible to run.
21 The job was aborted due to AbortThreshold timeout.
22 The job needs to have the due date calculated.
23 The job is linked to another job so will not start until the primary job is finished.
24 The job failed somewhere between RunJob() and before it was inserted on remote machine.
25 The job's scheduled start time has passed but a dependent job has not yet completed.