Backups generates backup coverage, SLA compliance, and summary reports that you can run on demand or save for client reviews. Reports are built from the same job records you see in the Jobs list, so the numbers are consistent with what you can verify yourself.
Reports are stored and can be retrieved any time after they are saved.
Available Report Types
| Report | What It Shows |
|---|---|
| SLA | Backup success rate against your defined SLA target for a given period and set of clients |
| Summary | Job counts, failure counts, missed counts, and storage consumed across a period |
| Coverage | Devices with no successful backup in a window, grouped by client |
Running an SLA Report
- Go to Reports -> SLA.
- Select the period (start and end date).
- Select the clients to include, or leave blank to include all.
- Click Calculate. The live calculation runs against the job records and returns SLA percentages per client.
- Click Save to persist the report to the Reports list for later retrieval.
SLA is calculated from the ratio of successful jobs to expected jobs within the period, based on each device's policy schedule. A device that missed a backup counts as a failed expected job.
Running a Summary Report
- Go to Reports -> Summary.
- Select the period.
- Review the aggregated counts: total jobs, successes, failures, missed, and storage used.
- Filter by client to see the breakdown for a specific client.
Viewing Coverage Gaps
Coverage gap data is available in two places:
- Coverage -> Gaps — live view, filtered by the window you choose (number of days). Shows every device with no successful backup.
- Coverage -> Anomaly — flags devices with unusual patterns: sudden drops in backup size or new failure streaks that do not match prior behavior.
Retrieving Saved Reports
- Go to Reports.
- The list shows all persisted reports with their type, period, and the user who created them.
- Click a report to view the stored data.
Restore History
Restore history is available in the Restores list rather than the Reports section. Every restore request is logged with the source job, target device, requested-by user, status, and any error message. Use the Restores list as your restore audit trail.
SLA Tracking Considerations
- SLA calculations depend on policies having an accurate expected interval. If the interval is set too loosely, the SLA percentage will appear higher than reality.
- Devices without a policy are not counted in SLA calculations. Assign policies to all devices you want to track.
- Saved SLA reports are point-in-time snapshots. If job records are updated after a report is saved, the saved report does not update automatically. Run a new calculation and save it to get current numbers.
Default Report Templates
On setup, Backups seeds three report templates:
- Monthly Summary -- aggregate job and storage summary for the past month
- SLA Compliance -- per-client SLA against targets
- Failure Report -- all failed and missed jobs in the period
These templates are pre-configured starting points. Adjust the period and client scope as needed before running.
FAQ
The SLA percentage is lower than expected. Check the expected interval on each policy. If the interval is shorter than the actual backup frequency, more missed-window events will be counted. Also confirm that all devices have policies assigned.
How far back can I report? Job records are retained according to the retention days set on your policies. Reports can only cover periods within the retained data window.
Can I see a per-client storage breakdown in reports? Yes. Run a Summary report and filter by client. Each client's job records include size data, so storage consumed per client is reflected in the filtered summary.