Skip to content

Monitoring Backups

The Backup dashboard gives you a real-time view of protection coverage, job activity, and storage consumption across your organization. Navigate to Operations > Backup to access it.


The Overview tab is your primary monitoring surface. It includes:

At the top of the dashboard, summary cards show:

MetricWhat it means
Total JobsNumber of backup jobs created
SnapshotsTotal point-in-time snapshots stored
Success Rate (24h)Percentage of jobs that completed successfully in the last 24 hours. Color-coded: green (90%+), yellow (70–89%), red (below 70%)
Devices ProtectedDevices assigned to at least one backup policy
Storage UsedTotal storage consumed across all providers

A live feed of the latest backup activity. Each job card shows:

  • Device name and configuration
  • Status: Completed (green), 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.

A breakdown of storage usage per provider (S3, Azure, Local, etc.) with usage bars and a 14-day trend chart. Useful for tracking growth and planning capacity.

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.

Issues requiring admin action — failed jobs, configuration errors, or policy gaps — listed with severity indicators.


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.

To back up one device:

  1. Navigate to the device’s detail page.
  2. Open the Backup tab.
  3. 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.


Each device’s detail page includes a Backup tab showing:

FieldDescription
Protection statusWhether the device is assigned to a backup policy
Last successful backupTimestamp of the most recent completed job
Next scheduled backupComputed from the policy schedule
Recent jobsList of recent backup/restore jobs for this device
VSS writer status (Windows)Health of Volume Shadow Copy writers — Stable, Failed, or Waiting

Backup and restore jobs move through these statuses:

StatusMeaning
Pending / QueuedCreated and waiting to be dispatched to the agent
RunningActively in progress on the device
CompletedFinished successfully; a snapshot was created
FailedEncountered an error (check the error details)
CanceledExplicitly 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.


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 retention policies are cleaning up old snapshots as intended, or whether large datasets were recently added to backup scope.


All backup operations are recorded in the audit log:

EventWhen it’s logged
Configuration created/updated/deletedStorage target changes
Configuration testedConnectivity checks
Policy created/updated/deletedSchedule or targeting changes
Manual backup triggeredOn-demand backup runs
Job canceledAdmin stops a running/queued job
Restore initiatedData recovery operations

Each entry includes the organization, resource, and user who performed the action.