Skip to content

A missed backup is a ticket, not a surprise.

Backup monitoring and reporting is the backup oversight module in the Backup system of The One Stack, the platform MSPs run their whole business on. It watches each protected device and cloud tenant, opens a ticket when backups stop, and sets schedules and retention by policy. It produces reports a client can read, for the MSP that answers for those backups.

Monitoring and reporting is part of Backup, one of the six systems of The One Stack.

Illustration, sample data. Every client’s backups on one page: device health, cloud connections, open alerts and the latest jobs.

What it does.

Stopped-reporting checks

Each device and tenant has an expected interval, and when successful backups stop arriving past it, the check records a missed backup and opens a ticket. A run of failures on one device does the same.

Alert rules

Rules cover no backup within a window, consecutive failures, storage thresholds, failed restores, stale integrity checks and coverage gaps.

Schedule and retention by policy

A policy sets how often a workload backs up and how long recovery points are kept, and the schedule and retention follow wherever you assign it. A retention change does not remove a device’s last recovery point.

Coverage gaps

Coverage compares the devices you manage for a client with the devices that are protected, and lists the ones that are not.

Reports a client can read

Generate service-level and summary reports per client, and a review report for the period with jobs, restores and storage.

Inside monitoring and reporting.

More of the product, screen by screen.

A missed backup becomes an alert and a ticket

When a device or tenant goes past its schedule without a good backup, the alert names it and the hours since the last success, and a ticket opens in the service desk. A repeat of the same problem reuses the open ticket.

Illustration, sample data. Missed backups and failure runs across clients, each with its source, severity and state.

How it connects.

Monitoring and reporting reads and writes the same record as the rest of the platform.

The ticket has the facts on it

The ticket names the client, the device, the policy and the last successful backup. A repeat of the same problem reuses the open ticket.

Service desk

Co-managed IT hears about its own failures

When a client with its own IT team has a backup fail, the people on that team are notified by email.

Co-managed IT

Usage per client

Stored data is tracked per client and exports as a spreadsheet file. Backup storage is metered.

Pricing

What THEO does here.

THEO has a runbook for a backup agent that has stopped. It checks the agent’s health, restarts the service, clears stale locks and confirms that the next backup runs. Outside the runbook it hands the ticket to a technician.

THEO

Questions

Questions about monitoring and reporting

What happens when a backup is missed?

A ticket opens in the service desk with the client, the device, the policy and the last successful backup on it. If the same device is missed again, the open ticket is reused.

Does a missed backup page the on-call technician?

No. A missed backup opens a ticket in the queue and does not page anyone.

How do backup reports reach a client?

You generate service-level and review reports per client and share them with the client.

Start

Run on One.

Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.