Veeam Agent Check Reference

All configuration fields, thresholds, and result states for the Veeam Agent for Windows backup check in octoja.

Written By Stefan Steuer

Last updated 25 days ago

Veeam Agent Check Reference

The Veeam Backup Agent check ("Veeam Agent check" for short) runs on the octoja agent installed on a Windows endpoint and reads Veeam Agent for Windows results from the Windows event log. It reports each backup job's outcome and age and the license state. It is distinct from the Veeam Backup & Replication check, which runs on the central Veeam Backup & Replication server.

Which Veeam check for which Veeam product?

octoja provides two separate Veeam checks. They read different data sources, so a check assigned to the wrong Veeam product fails permanently even while every job in Veeam is green.

Your Veeam product	Check to assign
Veeam Agent for Windows, standalone (for example backing up to a local USB disk)	Veeam Backup Agent check — this article, on the endpoint that runs the agent
Veeam Backup & Replication (central backup server)	Veeam Backup & Replication check — see the Veeam Backup Check Reference, on the Veeam server itself

Leading symptom of a wrong assignment: the check reports failed although all jobs in Veeam are green. Verify which of the two checks is assigned to the device — also when checks are assigned through tags, where an automatic tag can attach the wrong Veeam check to a device. Agent jobs that a Backup & Replication server manages centrally are monitored by the Veeam Backup & Replication check on that server; this check covers standalone installations that write to the local Veeam Agent event log.

Configuration fields

Field	Type	Required	Default	Description
Require the agent to be present	Boolean	No	On	When on, a machine without Veeam Agent is Critical. Turn off to pass on machines that do not run it
Evaluate license events	Boolean	No	On	Warn when a license-expired or grace-period event appears in the window
Warning after (hours)	Number	No	30	Warn when the last successful backup is older than this. `0` disables it. Advanced option
Critical after (hours)	Number	No	50	Critical when the last successful backup is older than this. `0` disables it. Advanced option
Event log lookback (days)	Number	No	14	How far back to read the Veeam Agent event log. Extended automatically to cover the critical-age threshold. Advanced option

Result states

Condition	Severity
Veeam Agent is absent and Require the agent to be present is on	Critical
No completed backup job in the lookback window	Critical
The latest run of a job ended in error	Critical
A successful backup is older than the critical threshold	Critical
The latest run of a job ended with a warning	Warning
A successful backup is older than the warning threshold	Warning
A license-expired or grace-period event is present (when evaluating license events)	Warning
The latest backups completed successfully within the thresholds	OK

The overall result is the worst per-job outcome, raised to at least Warning when a license event is present.

Collected metrics

Per job: name, last-run time, status (Success, Warning, or Error), age in hours, and result text
The age of the most recent backup overall
The license event id and date, when a license event is present

Platform support

Platform	Supported
Windows (endpoint with Veeam Agent for Windows)	Yes
Linux	No
macOS	No

Notes

The check detects Veeam Agent by its Windows service or its Veeam Agent event log, then reads the job-finished and license events.
It needs no administrator rights and no network access — it reads the local event log only.

See also: Configure a Veeam Agent Check — the step-by-step setup guide.