Backup Monitoring for Veeam, Hyper-V and SyncBack

What it does

Everything between the job and the client report

One ledger for every backup engine you manage, with the evidence to show a client.

🛡️

No result on every missed day

A backup that was due and did not run is shown as No result on that day, every time it happens. A monthly job that misses its second month is flagged on that Thursday, and again the month after, until it runs or is retired.

🗓️

Schedules read, not typed

What a job was due to do comes from the offline schedule recorded for the client, the schedule Veeam reports for the job, or the pattern in its own history. Nothing is entered by hand for each job, and a job is never flagged on a day it was not due.

🧾

Backup coverage audit

Every VM on every Hyper-V and ESXi host is checked against backup and replica jobs. Unprotected VMs surface in one click, with client-ready PDF evidence.

🧩

Disk exclusions

See which VM disks a Veeam job leaves out of the backup, per job and per client, so a partial backup is never mistaken for a full one.

💾

Offline disk rotation

Run external-disk backups on a schedule, or start them when the disk is plugged in, matched by the disk's own serial. The disk is ejected safely and the client is emailed when the whole chain has finished.

☁️

Cloud workloads in the same ledger

Provider-native backups for cloud VMs on Linode, AWS, Azure, GCP, DigitalOcean, Vultr, Hetzner and Oracle Cloud, tracked beside on-premise jobs with one read-only API token per account.

Proof for your clients

Backup reports you can hand to a client

Every result is searchable by client, job and day, and exports as PDF, Excel or CSV. A combined Excel report covers every backup type over a date range, with a summary by client, and any report can be scheduled to arrive by email.

Per-client PDF and Excel with the full result history
A monthly VM inventory audit that records VMs added, removed or resized
Alerts per job through email, Telegram, WhatsApp and webhooks
Retire a job that no longer exists, so it stops being reported

COVERAGE AUDITIllustrative data

VM-APP01Backup and replica

VM-SQL02Backup only

VM-FS03 · disk 2 excludedPartial backup

VM-NEW07Not protected

Supported engines

Works with the backup tools you already run

Veeam Backup & Replication

Veeam Agent

Hyper-V Replica

SyncBack

External offline disks

Linode

AWS

Microsoft Azure

Google Cloud

DigitalOcean

Vultr

Hetzner Cloud

Oracle Cloud

FAQ

Questions teams
ask us first

Anything else? Ask on the demo.

How does monytr.ai know a backup never ran?

It reads each job's expected schedule from the offline schedule recorded for the client, the schedule Veeam reports for the job, or the pattern in the job's own run history. When a job was due on a day and nothing arrived, that day is marked No result, and it stays marked every time it happens until the job runs again or is retired.

Which backup products are supported?

Veeam Backup & Replication, Veeam Agent, Hyper-V Replica, SyncBack, offline external-disk rotations and provider-native cloud VM backups on Linode, AWS, Azure, GCP, DigitalOcean, Vultr, Hetzner and Oracle Cloud.

Does it read my backup data or open ports on a client network?

No. A lightweight agent on the backup server reports job results outbound over HTTPS with a per-server API key. It reads job status and configuration, never the backed-up data, and no inbound connection or firewall change is needed.

Can it find VMs that have no backup at all?

Yes. The Coverage Audit cross-checks every VM on every Hyper-V and ESXi host against backup and replica jobs, and the Disk Exclusions report shows which disks of a protected VM a Veeam job leaves out.

How do I show a client that their backups are healthy?

Results export per client as PDF, Excel or CSV, a combined report covers every backup type over a date range, and any report can be scheduled to arrive by email.

Keep going