Veeam Backup Check Reference

Veeam Backup Check Reference

Configuration options and alert behaviour for the Veeam Backup & Replication check.

---

The Veeam Backup & Replication check monitors the jobs running on a Veeam Backup & Replication server. It runs hourly by default on the octoja agent installed on the Veeam server, queries the local Veeam installation for each job's latest session, and reports the last result and age of every job back to octoja. It covers backup, backup-copy, agent, and tape job types (agent jobs are included by default; tape jobs are opt-in), controlled by the job-type filter below.

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.

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 this check to a device that only runs Veeam Agent for Windows. Agent jobs that are managed by a Backup & Replication server are covered by this check on the server (option Include agent jobs); the Veeam Backup Agent check is only for standalone installations.

Prerequisites

• The octoja agent is installed on the Veeam Backup & Replication server itself. The check only queries the local Veeam installation — it cannot monitor a remote Veeam server.
• The Veeam PowerShell module is present. It is installed together with Veeam Backup & Replication; the check also finds it when the module is not registered on the PowerShell module path.
• The Veeam Backup Service is running on the device. The check signs in to the Veeam server on the same machine (localhost) and enumerates its jobs.
• The check signs in with the Windows account the octoja agent service runs under — no separate Veeam credentials are required or configurable. That account must be allowed to query jobs on the Veeam server.

When the check itself cannot run, it reports one of these errors:

Supported Veeam versions

The check supports Veeam Backup & Replication v12 (the Veeam module runs in Windows PowerShell) and v13 (the module runs in PowerShell 7, pwsh); it selects the matching PowerShell host automatically.

Configuration fields

Alert behaviour

Metrics collected

For each monitored job, the check reports:

• Job name and job type
• Last run status (Success, Warning, Failed, Never run, Running, Disabled, or Unknown)
• Last run timestamp and start time
• Session state (for example Working, Idle, Post-processing) and progress percent while running
• Backup type (Full, Active full, or Incremental), whether the schedule is enabled, compression level, VSS, encryption, dominant bottleneck (Source, Proxy, Network, or Target), and whether the last result came from a retry
• Failure or warning reason from the Veeam session log, when present
• Computed severity (OK, Warning, Critical, or Error) based on the last status and the configured age thresholds. Failed jobs and breaches of the critical age threshold both report as Critical; the Error severity covers cases where the check itself cannot run — the Veeam PowerShell module fails to load, the query times out or returns no usable output, or an unexpected error occurs.
• Across all jobs, the check also reports the total job count, per-category counts (failed, warning, never run, running, disabled), and the age of the most recent successful backup.

Platform support

Notes

• The check runs every 60 minutes on the agent. The interval is not user-configurable.
• The agent reads backup data through the local Veeam PowerShell module (installed with Veeam Backup & Replication). No REST API configuration or separate Veeam credentials are required.
• The agent auto-detects the PowerShell host: pwsh is tried first (required for Veeam 13+), and Windows PowerShell (powershell.exe) is used as a fallback when the Veeam module fails to load in pwsh. Mixed-version Veeam estates work without configuration.
• The check evaluates each job's latest session. Disabled jobs are listed but do not alarm unless Evaluate disabled jobs is on, and a job that has never completed a session raises a warning only when Warn on jobs that never ran is on.
• This check does not monitor third-party backup solutions. Use the Windows Backup check for native Windows Server Backup, or contact octoja support for other backup products.
• If you run multiple Veeam servers, install the octoja agent on each one and configure a separate Veeam Backup & Replication check on each device.

See also: Configure the Veeam Backup Check