Different states of a backup

We have renamed a couple of things in the list of repository backups and introduced a new differentiation between archived backups with upstream to the original repository at GitHub and archived backups without upstream.

Let me explain in detail what these different states mean and how they look like:

Repositories without Backups

basic_backup-list-without

This section contains all repositories you have at GitHub that do not have any backups. Depending on whether you have automatic backups activated or not, you will either see “Backup scheduled” or a button “Backup”. “Backup scheduled” means automatic backups has just been activated, but backups are not yet created. This usually happens between 2:00 – 6:00 am CET.

Active

basic_backup-list-active

This section contains all repositories with active recurring backups. “active recurring” means we are updating the backup for this repository once a day between 2:00 – 6:00 am CET.

Archived

basic_backup-list-archived

This section contains all repositories with backups that have been archived. Archiving means, the backup is not being updated on a daily basis. On the right side of each repository you will find the information, when the last backup has been made.

Now there are two different cases for archived backups. Firstly, a backup for a repository that is still existing at GitHub and secondly, a backup for a repository that has been removed from GitHub. When a repository at GitHub with an active backup at BackHub is being deleted at GitHub, BackHub automatically archives the backups since the upstream is no longer available.

Archived Backups with upstream to the original repository at GitHub

basic_backup-with-upstream--open Backups with upstream to the original repository at GitHub do have a solid border and a link to the repository at GitHub as well as an option to reactivate recurring backups.

Archived Backups without upstream to the original repository at GitHub

basic_backup-without-upstream--open Backups without upstream to the original repository at GitHub do have a dashed border without link to GitHub since the original repository is no longer available.

Author
Integrations covered
  • GitHub
Newsletter

Your monthly data news retrospective.

Subscribe to Retro for access to the top stories and conversations you need to be a part of—all from the perspective of Rewind’s data experts.

Keep reading

Related posts

Title card reading SaaS backup alternatives: what to check before you choose, with the Rewind logo

SaaS backup alternatives: what to check before you choose

If you are weighing SaaS backup alternatives, you are probably really asking a bigger question: does the way you protect...

Title card reading AI agent debugging tools: what they fix and what they can't, with the Rewind logo

AI agent debugging tools: find the bug, then fix the data

AI agent debugging tools help you see what an autonomous agent did, step by step, so you can find the...

A Jira Admin's Guide to ScriptRunner Backup and Restore

A Jira Admin’s Guide to ScriptRunner Backup and Restore

ScriptRunner admins open Rewind for two very different reasons. One is routine. The other is the kind of incident that...

Deploy AI boldly.
Recover fast.