Verification & Recovery Readiness

A backup you can’t restore is worthless. The Verification tab helps you continuously validate that your backups are recoverable and measure how prepared each device is for a recovery scenario.

Verification Types

Go to Operations > Backup > Verification to access verification controls.

Type	Duration	What it checks	Impact
Integrity check	Fast (minutes)	Downloaded object size and SHA-256 checksum compared against the manifest, plus file counts and manifest consistency	None — no data is restored
Test restore	Medium (10+ min)	Extracts the full snapshot to a temporary location, verifies each object against the manifest, and measures restore time	Low — uses temp space, no production impact

Running a Verification

Go to Operations > Backup > Verification.
Click Run Integrity Check or Test Restore.
Confirm the action in the dialog.
The verification appears in the history table with a status of Running.
When complete, the status updates to Passed, Failed, or Partial.

If the device is offline, Breeze shows Device is offline. Verification requires a connected agent. and the verification buttons stay disabled. If command dispatch fails for another reason, Breeze shows the dispatch error and lets you retry after the underlying issue is fixed.

Verification History

The history table shows all past verifications with:

Verification type
Status (Pending, Running, Passed, Failed, Partial)
Start time and duration
Files verified and files failed
Total size checked

Automated Verification

Breeze runs verifications automatically on a schedule:

Check	Frequency	What it does
Post-backup integrity	Every 10 minutes	Validates the most recent completed backup when the device is available
Weekly test restore	Sundays at 03:00 UTC	Runs a restore test for recent backups when the device is available
Readiness score recalculation	Daily at 02:00 UTC	Updates recovery readiness scores for all devices
Timeout detection	Every 5 minutes	Flags verifications that have been running too long

No setup is needed — automated verifications run as soon as backup is configured. If a device is offline when a scheduled verification window arrives, Breeze skips that run and logs the skip instead of creating a synthetic verification record.

Recovery Readiness Score

Each device gets a readiness score from 0 to 100, visible on the Verification tab:

Score	Rating	Meaning
85–100	High	Device is well-protected and verified
70–84	Acceptable	Minor gaps — review risk factors
Below 70	Low	Significant recovery risk — take action

The score is calculated from:

Recency — how fresh the latest snapshot is (within 30 days)
Verification success rate — recent integrity and restore test results
RTO/RPO compliance — whether estimated recovery times meet SLA targets
Risk factor assessment — missing backups, failed verifications, or expired snapshots

Risk Factors

The Verification tab lists specific risk factors for each device, color-coded by severity:

Risk factor	Severity	What to do
No recent backups	High (red)	Check policy assignment and agent connectivity
Verification failures	High (red)	Investigate the failed verification — storage may be unreachable
SLA breaches	Medium (orange)	Review SLA targets or increase backup frequency
Data change accumulation	Medium (orange)	Large volume of unprotected changes — run a backup
Immutable backup gaps	Low (yellow)	Consider enabling immutability on your storage configuration

Organization Backup Health

The Verification tab also shows an organization-wide health summary:

Status	Meaning
Healthy	All devices have recent, verified backups
Degraded	Some devices have low readiness scores or recent failures
Critical	Multiple devices are unprotected or have failed verifications

Use this as a quick indicator of overall backup posture.

If the overview shows No verification history, that means Breeze has no completed live verification for the device yet. Run a real verification once the device is online to populate readiness and recent-failure history.