Backup integrity

What this feature is for

Backup integrity checks read-only backup metadata and critical data-path signals. It gives an operator evidence about freshness before an incident forces a restore. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

A connected data provider, the backup locations or tables to inspect, and a recovery objective.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Connect the provider, define the freshness expectation, run the check, and record the restore verification or follow-up when the result is stale.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

Evidence includes last successful backup, age, protected scope, and the check time. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

A recent timestamp alone does not prove a restore works. Treat missing objects, permission errors, and schema drift as separate recovery risks.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Use Backup integrity with Health, Activity, and Trust reports when customers ask about operational resilience. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.