Monitoring Backups
The Backup dashboard gives you a real-time view of protection coverage, job activity, and storage consumption across your organization. Navigate to Backup > Device Backup to access it.
Overview Tab
Section titled “Overview Tab”The Overview tab is your primary monitoring surface. It includes:
Metrics Cards
Section titled “Metrics Cards”At the top of the dashboard, summary cards show:
| Metric | What it means |
|---|---|
| Total Jobs | Number of backup jobs created |
| Snapshots | Total point-in-time snapshots stored |
| Success Rate (24h) | Percentage of jobs in the last 24 hours that produced a restore point (Completed or Completed with errors). Color-coded: green (90%+), yellow (70–89%), red (below 70%) |
| Devices Protected | Devices assigned to at least one backup policy |
| Storage Used | Total storage consumed across all providers |
Recent Jobs
Section titled “Recent Jobs”A live feed of the latest backup activity. Each job card shows:
- Device name and configuration
- Status: Completed (green), Partial (amber), Running (blue), Failed (red), Queued (gray), Canceled
- Start time, duration, and data size
Click View all to see the full job history with filters for status, device, and date range.
Storage by Provider
Section titled “Storage by Provider”A breakdown of storage usage per provider (S3, Local) with usage bars and a 14-day trend chart. Useful for tracking growth and planning capacity.
Devices Needing Backup
Section titled “Devices Needing Backup”Cards highlighting devices with overdue backups, showing the device name, when it was last backed up, and how many days overdue it is. Address these first.
Attention Items
Section titled “Attention Items”Issues requiring admin action — failed jobs, configuration errors, or policy gaps — listed with severity indicators.
Running Backups On Demand
Section titled “Running Backups On Demand”All Devices
Section titled “All Devices”Click the Run all backups button at the top of the Overview tab. A confirmation dialog shows how many devices will be included and lists any jobs already in progress. Confirm to trigger immediate backups across your fleet.
Single Device
Section titled “Single Device”To back up one device:
- Navigate to the device’s detail page.
- Open the Backup tab.
- Click Run Backup Now.
The job appears immediately in the dashboard’s Recent Jobs feed.
If the device is offline, Breeze returns an error immediately and does not create a backup job. If queue dispatch fails after job creation, the job is marked Failed with the dispatch error so the history stays accurate.
Per-Device Backup Status
Section titled “Per-Device Backup Status”Each device’s detail page includes a Backup tab showing:
| Field | Description |
|---|---|
| Protection status | Whether the device is assigned to a backup policy |
| Last successful backup | Timestamp of the most recent completed job |
| Next scheduled backup | Computed from the policy schedule |
| Recent jobs | List of recent backup/restore jobs for this device |
| VSS writer status (Windows) | Health of Volume Shadow Copy writers — Stable, Failed, or Waiting |
Job Lifecycle
Section titled “Job Lifecycle”Backup and restore jobs move through these statuses:
| Status | Meaning |
|---|---|
| Pending / Queued | Created and waiting to be dispatched to the agent |
| Running | Actively in progress on the device |
| Completed | Finished and every file was read; a snapshot was created |
| Completed with errors | A snapshot was created and can be restored from, but one or more files could not be read or uploaded (for example, permission denied or a locked file). The failures stayed within 10% of the run. The job shows how many files failed and which ones, so check it before relying on the snapshot for those files. |
| Partial | A snapshot was created and can be restored from, but a disproportionate share of the run failed — more than 10% of the scanned bytes, or more than 10% of the attempted files. Check the error log for which files were skipped. |
| Failed | Encountered an error (check the error details) |
| Canceled | Explicitly stopped by a user before completion |
Jobs are triggered either automatically by a policy schedule, manually via the Run Backup button, or as part of a restore operation.
Completed with errors is new in v0.118.0; earlier releases reported these runs as Completed. API consumers see the status value completed_with_errors. It counts as a successful backup for “no successful backup” checks and is not a failure for “consecutive failures” checks. To be alerted on it, add a Backup continuity monitor with the Completed with file errors check, which fires when a device’s latest backup ended in that state.
Storage Usage History
Section titled “Storage Usage History”Track storage growth over time from the Overview tab’s storage section. The usage chart shows cumulative storage by provider over the past 14 days (configurable from 3 to 90 days via the API).
If storage is growing faster than expected, check whether large datasets were recently added to backup scope. Expired restore points are removed from Breeze immediately and their storage is reclaimed by the periodic reclamation sweep (see the storage page for timing and safety windows) — allow for the grace period and the next scheduled sweep before usage reflects the drop.
Audit Trail
Section titled “Audit Trail”All backup operations are recorded in the audit log:
| Event | When it’s logged |
|---|---|
| Configuration created/updated/deleted | Storage target changes |
| Configuration tested | Connectivity checks |
| Policy created/updated/deleted | Schedule or targeting changes |
| Manual backup triggered | On-demand backup runs |
| Job canceled | Admin stops a running/queued job |
| Restore initiated | Data recovery operations |
Each entry includes the organization, resource, and user who performed the action.