Reports & analytics

The NGBackup Web Console ships a full reporting engine on top of the catalog. Every report can be viewed on-line in the console, generated on a schedule, and delivered automatically by e-mail — no external BI tool is required. When the built-in reports are not enough, the same data is open to unrestricted custom reporting through read-only SQL and the REST API.

Backup size trend analysis

Trend reports chart the growth of the protected estate over time:

• Protected data — total and per-client/per-job bytes backed up (JobBytes) per day, week or month, so you can see which clients and jobs are growing and project future capacity.
• Stored volume data — the on-disk/on-tape footprint of the volumes (VolBytes) per pool and media type, tracking how retention, compression and deduplication translate protected bytes into stored bytes.

Both series are drawn per client, per job or aggregated, over any period you pick, and both export to CSV/PDF for capacity-planning reviews.

Data distribution across media

Distribution reports break the stored data down by where it lives:

• volumes and their utilization per pool;
• bytes per media type — disk, cloud and tape side by side;
• bytes per storage daemon / device, highlighting imbalanced or nearly-full destinations.

Use these to verify that copy/migration policies actually place data on the intended tier and to spot pools that need more volumes before jobs start waiting on media.

Backup status & success rate

Status reports summarize job outcomes over a chosen period (last 24 h, 7 days, 30 days, or a custom range):

• counts of successful, failed, canceled and warning-terminated jobs, per client and per job;
• the success-rate percentage for the period, overall and per client — the number most service-level reviews ask for;
• drill-down from any summary row to the individual job records and their full logs.

RPO compliance report

The RPO report compares the actual most recent recovery point of every node (or group of nodes) against its target RPO. Each row shows the client, its newest successful backup, the elapsed time since, the configured target, and a compliant/violated verdict — so a 24-hour-RPO client whose last good backup is 30 hours old is flagged immediately. Grouping rolls the verdicts up per department, site or policy, giving a one-line compliance figure per group.

RTO report

The RTO report tracks how long recovery actually takes. It records the measured duration of restore jobs and restore-verification runs per client/job and compares them with the defined RTO target, so you can prove — with measured numbers, not estimates — that the environment restores within the committed window, and catch restore times drifting upward before they breach the objective.

Job status report

The task report lists every run in the period with its operational metrics:

Column	Meaning
Job / Client / Level	What ran and where.
Status	Termination status (OK, OK with warnings, Error, Canceled).
Start / End / Run time	Scheduled vs actual timing and elapsed duration.
Data processed	Files and bytes read from the client (JobFiles, JobBytes).
Footprint	Bytes written to volumes for the run.

On-line viewing, scheduling & e-mail delivery

Every report renders on-line in the Web Console with interactive filters. Any report can also be scheduled: pick the report, the period it should cover, the recurrence (daily/weekly/monthly) and a recipient list, and NGBackup generates it and delivers it by e-mail automatically — typically as a PDF or CSV attachment. Event-driven notifications (job failures, low disk space, threshold breaches) are handled by the messaging layer; see Automatic alerts & notifications.

Custom reports

The custom-report builder assembles reports from the catalog’s information categories — alerts, configuration, jobs, media, devices and policies — with your choice of columns, filters, grouping and period. Saved custom reports behave exactly like built-in ones: view them on-line, schedule them, e-mail them.

Unrestricted reporting: SQL and REST

There is no reporting ceiling. The catalog is a documented, open PostgreSQL schema — see the catalog schema reference — so any question the built-in reports don’t answer can be asked directly with read-only SQL (the console’s .sql verb, psql, Grafana, or any BI tool that speaks PostgreSQL). The same data is exposed programmatically through the REST API for dashboards and monitoring integrations.