> For the complete documentation index, see [llms.txt](https://docs.tipo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tipo.io/backup-and-restore-tipo/reference/how-it-works/how-backups-work.md).

# How backups work

Learn how scheduled, manual and pre-restore backups are created, why later backups only copy changes, and what each backup status means.

A backup is a saved copy of your store data at a point in time. This page explains when backups start, what each one copies, and how to read their statuses.

## What starts a backup

| Trigger         | When it happens                                                                                                                                                                          |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Scheduled**   | Automatically, using the frequency, time and time zone you set in [Backup schedule](/backup-and-restore-tipo/settings/settings/backup-schedule.md). Automatic backups are on by default. |
| **Manual**      | When you select **Back up now** or **Take a snapshot** on Home. See [Back up now](/backup-and-restore-tipo/backups/backups/back-up-now.md).                                              |
| **Pre-restore** | Automatically, right before a restore overwrites data. It is a safety copy. See [Safety backups and undoing a restore](/backup-and-restore-tipo/restore/restore/safety-backups.md).      |

{% hint style="info" %}
Backups are never triggered by changes in your store. They are not real time. Anything you change between two backups is picked up by the next backup.
{% endhint %}

## First backup is full, later ones copy changes

The first backup of each data type copies everything. After that, each backup copies only what was created or changed since the previous one. This is called an incremental backup. It makes backups faster and keeps your stored size small.

In the **Backups** list, the number in the **Changes/Deletions Items** column counts the items added or changed in that run. It is not the total number of items in your store. A run where nothing changed shows `0`.

## Every backup is a complete restore point

Even though a backup only copies changes, every backup still represents your whole store as it was at that backup's date and time (its cutoff). You can restore from any completed backup, or download it, without needing the earlier ones. The item counts on the export page show the full store state as of that backup.

## Full re-scan every 30 days

Every 30 days, the app automatically re-scans each data type in full. A full re-scan is the most reliable way to notice items that were deleted from your store.

Some data types are scanned in full on every run, because they are small or cannot be tracked by change date. These are Files, Themes (the list of themes), Blogs, Menus, Policies, Shipping zones, Locations, Metaobjects, Metafield definitions and Saved searches. Theme files are different: only new or changed theme files are downloaded again on each run.

## Deleted items

When an item disappears from your store, the app keeps its last backed-up version. How long it is kept depends on your plan (the **Deleted items kept for** value in [Storage and retention](/backup-and-restore-tipo/settings/settings/storage-and-retention.md)). You can bring such items back with [Restore deleted items](/backup-and-restore-tipo/restore/restore/restore-deleted-items.md).

## Backup statuses

A backup moves through these statuses.

| Status                      | Meaning                                                                                                                        |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Pending**                 | The backup was created and is about to start.                                                                                  |
| **Running**                 | The app is copying data from your store.                                                                                       |
| **Finalizing**              | The data is copied and the app is wrapping up the backup.                                                                      |
| **Completed**               | Every data type was backed up. You can restore from it and download it.                                                        |
| **Completed with warnings** | The backup finished, but a non-critical part failed or some items were skipped. You can still restore from it and download it. |
| **Failed**                  | A required part of the backup failed. You can't restore from it or download it.                                                |
| **Cancelled**               | The backup was stopped.                                                                                                        |

To see which items were skipped, select the number in **Changes/Deletions Items** for that backup. See [View your backups](/backup-and-restore-tipo/backups/backups/view-your-backups.md).

## Rules the scheduler follows

* **One backup at a time.** If a backup is still running when the next scheduled one is due, the scheduled one is skipped.
* **No backup during a restore.** If a restore is running when a scheduled backup is due, the backup waits and tries again a little later. This avoids saving a half-restored store.
* **Plan limits.** If your store is over what your plan includes, new backups and restores pause. Nothing you already backed up is deleted. They resume once you are back within the limits. See [Usage and plan limits](/backup-and-restore-tipo/plans-and-billing/plans/usage-and-limits.md).
* **Faster than your plan allows.** If you choose a frequency that your plan does not allow, the option is disabled. If you move to a plan with a slower fastest frequency, your saved setting is kept, but backups run at the plan's pace.

## Next steps

* [What we back up](/backup-and-restore-tipo/reference/how-it-works/what-we-back-up.md)
* [Choose what to back up](/backup-and-restore-tipo/settings/settings/what-we-back-up.md)
* [Back up now](/backup-and-restore-tipo/backups/backups/back-up-now.md)
* [How restore works](/backup-and-restore-tipo/reference/how-it-works/how-restore-works.md)