Skip to content

Follow runs and read the run console

3 min · Screen: /runs · Needs: Permissions.Backups.ViewHistory

Backups › Backup history lists runs newest first. Filter by plan, server, environment, status, trigger, date range, With warnings or Without warnings, and include Test runs when you need them. Running rows update live.

Click a run to open its console. The header shows its status, attempt, times and correlation id; while it runs you see bytes read and stored, the ETA and the compression ratio.

Stage timeline

Three lanes - Control, each Source, Finalise - with a chip per stage. Hover a chip for its message.

Log

Everything the run said, as it said it. Secrets never appear here.

Steps

Every stage with source, status, start, duration, bytes, exit code and message.

Artifacts

The files this run stored, with size and output.

Warnings

What was skipped or dropped - read these on a Succeeded with warnings run.

  1. Find the first red chip in the stage timeline

    That stage’s message says what went wrong; many failures also show What to do.

  2. Open the Steps tab for the exit code and full message

  3. Fix the cause

    See Fix common problems for the usual ones.

  4. Run it again

    Temporary failures are retried automatically; otherwise start the plan with Run now.