Skip to content
Docs
strackt.io Open app
How To Updated 26 Sep 2026

Check that your backups ran

See each recent off-server backup run, what its status means, and what to do when one fails.

Check that your backups ran

A backup schedule tells you when copies are meant to happen. The run history shows you what actually happened: when each run happened, how it ended, and what to do about a failure.

Where to find it

  1. Open your application (or your service) and go to Protection.
  2. Find the Backups panel, headed Off-server protection. It has a row for each kind of off-server copy:
    • Cloud backup: copies to your own object storage.
    • Server backup: copies to a server you own.
  3. Under a row that's turned on, read the summary line:
    • Last copy … shows when the last successful copy finished, and Next … shows when the next run is due.
    • First copy pending means no copy has finished yet.
    • Last copy failed means the most recent run didn't finish. The reason and what to do follow it.
  4. Choose View activity to see the individual runs. The number beside it is how many runs are listed. Choose Hide activity to close the list.

The list shows your five most recent runs for that backup, newest first. Each run shows its status and the date and time it ran, in your own timezone. Finished runs also show the size of the copy and how long the run took.

What each status means

Status What it means
In progress The run has started and hasn't finished yet.
Copied The run finished and the copy was written to your destination.
Failed The run didn't finish, so no copy was taken at that point in time. The reason is shown beside it.
Expired The run finished, but its copy has since been removed under your retention settings. It's history only; you can't restore from it.

Copied means the copy was taken. It doesn't mean anyone has tested a restore from it. To see which copies you can restore from right now, look at your restore points. Every off-server copy that still exists appears there.

A run that stays In progress far longer than it should, for example because the server restarted partway through, is eventually marked Failed. The reason shown is "The backup did not complete".

When a run fails

A failed run means that point in time wasn't captured. One failed run doesn't stop the schedule: the next run still happens as planned.

Each failed run shows one of these reasons, together with what to do:

Reason shown What to do
Another backup or maintenance task was using this backup set. Wait a few minutes. If later runs keep failing with this reason, contact support.
The backup destination did not accept the saved access details. Check your backup credentials and update them. See Backups.
The backup destination could not be reached. Check that the destination is online. That means the server you back up to, or your bucket.
There is not enough available storage to finish the backup. Free space or increase backup storage at the destination.
The source was not available when the backup ran. Make sure the application or service is running.
The backup did not complete. Wait for the next run. If it fails again, contact support.

Once you've fixed the cause, check View activity after the next scheduled run (the Next … time) to confirm it shows Copied. For the most common causes and how they show up, see When a scheduled backup fails.

Will you be told about failures?

A single failed run doesn't send you an email or a webhook. It shows up here, on the Protection page. That's why this page is worth checking.

If an application's backups fail twice in a row, its page also shows Recent backups haven't completed, along with the date of your latest restore point. strackt's team is notified at the same time. If the failed run names something only you can fix, such as your access details or your storage space, fix it there; the next scheduled backup tries again.

Was this helpful?