Backup monitoring.
Octotor reads the job history of your Veeam Backup & Replication server and turns it into alerts, and into information recorded on each computer. A backup that failed, ended with a warning, or did not run on time shows up the same morning. This page describes what you get and how to read it. Setting it up is on Set up backup monitoring.
What it does
- On every protected computer Octotor writes when its last successful backup ran and how the last run ended (Success, Warning, Failed, or Not protected). These values sit in a BACKUP attribute group on the computer, next to its disks, software and accounts.
- On the backup server Octotor writes how many jobs succeeded, ended with warnings, failed, are overdue, or are disabled, together with the names of the jobs behind each count, and lists the backed-up items it could not match to any asset.
- Six alert rules come with Octotor and are switched on already: a backup job failed recently on the server (critical), a backup job is failing on the server (critical), a backup job ended with a warning on the server (warning), the last backup of a computer failed (critical), the last backup of a computer ended with a warning (warning), and the backup of a computer is overdue (warning). They raise alerts inside Octotor straight away. To have them sent to you as well, add a notification channel to each rule you want to hear about — see Set up backup monitoring.
- A Backup jobs tab on the backup server shows every job run and every backed-up item with its result, a filter for Success / Warning / Failed, and the last log lines Veeam recorded for a failed or warning item.
- The collector only reads. It never starts, stops, edits, or deletes a backup job. A Veeam account with the Backup Viewer role is enough.
Who it is for
IT teams and managed service providers who run Veeam Backup & Replication for one or more customers and want backup state in the same place as the rest of the fleet, with the same alerts. Each Veeam server belongs to exactly one customer in Octotor, and the computers it protects are matched inside that customer only.
What you need
A Veeam Backup & Replication server on Windows (version 12 or 13), a Windows account on it that may read Veeam — the Backup Viewer role is enough — and Octotor v3.3.7 or later. Backup monitoring is part of the Pro and Enterprise plans. The full list, including what Veeam 13 needs, is on Set up backup monitoring.
How a backup problem reaches you
The task runs on its schedule, and when something is wrong it raises an alert. If you have added a notification channel to the rule, the alert is sent to you as well. From the alert, these are the steps to the reason.
1The alert names the machine
Open Alerts. A backup alert says which machine and which rule fired — for example the last backup of this computer failed. Open it and the Cause line carries two things: the value that crossed the threshold, and the message the backup software itself reported, such as Failed to connect to FS-02: The network path was not found.
2Go to the machine from the alert
The alert’s Show asset action opens that computer’s record. You do not have to find it in the list.
3Read its backup history
The Backup jobs tab on a protected computer opens with one line for the machine itself — when its last successful backup finished, what the most recent run returned, which job protects it and which backup server reported it — and, when the last run failed or warned, the message the backup software gave. Below it is every run recorded for that machine, newest first.
The four buttons filter by result. Failed leaves only the runs that did not complete. A failed or warning run keeps a Log button, and that opens the lines Veeam wrote about it: the reason for the failure, stored next to the machine it happened on, without opening the Veeam console.
4The same information, as attributes
The Attributes tab holds the same values in a group called BACKUP. These are ordinary attributes, so you can filter the asset list by them (for example, every computer whose backup is overdue) and write your own alert rules on them, in addition to the six that come switched on.
5The backup server’s own view
Open the machine you set as the backup server. Its Backup jobs tab shows the whole picture rather than one machine: how many jobs succeeded, warned, failed, are overdue or disabled, how many backed-up items matched no asset, and every run of every job with the same filters and log lines.
What you see
| Where | What |
|---|---|
| Protected computer ▸ Attributes ▸ BACKUP | Backup — Last Successful Run · Backup — Last Result · Backup Job Name · Backup Server · Backup Overdue · Backup Copy — Last Successful Run · Backup — Last Warning or Error Message |
| Backup server ▸ Attributes ▸ BACKUP | Backup Product · Backup Data — Last Collected · Backup Jobs — Total / Successful / With Warnings / Failed / No Last Result / Disabled / Overdue, each with the job names behind it · Backed-Up Items With No Asset |
| Backup server ▸ Backup jobs tab | One row per job run or backed-up item (the job name, with Backed-up item: name under it) with started / ended times, type, result chip SUCCESS WARNING FAILED, the matched asset, and a Log button with the last Veeam log lines of a failed or warning item |
| Alert Center | The six backup rules, their open alerts, and the message text of the failed run in the alert detail |
| AI assistant | Two read-only tools: get_backup_state (which computers are protected, their last result, days since a successful backup) and get_backup_sessions (the job run history with the log lines of failed items) |
Ask the AI assistant
The assistant reads the same data. Ask, for example, "Which computers at Tripleor have no successful backup in the last 2 days?" or "Why did the backup of FS-02 fail last night?" The answer comes from your own database.