> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/help-center/workflows-and-recovery/backup-coverage-and-restore.md).

# Backup coverage and restore

Tell database downloads from verified full-site backups, and restore safely.

**Back up my site** always makes a verified **database-only** archive. It does not include uploads, themes, plugins or WordPress core. With UpdraftPlus active, it also requests a full-site set and waits up to 30 minutes for UpdraftPlus to confirm a new, complete one. Other backup plugins are detected but not triggered.

Open **History > Backups** and read **Coverage**:

* **Database verified**: download or restore it here.
* **Full site confirmed by UpdraftPlus**: restore files from UpdraftPlus (**Open in UpdraftPlus**).
* **Full-site archive pending** or **Files and uploads not confirmed**: only the database is covered.

**Restoring the database** overwrites content changed since the archive. During the restore visitors can read the site, but orders, forms, comments and other visitor writes get a 503 and should retry; administrators are not blocked. A safety backup is made first, and **Revert last restore** is available for 24 hours. Task history is kept.

**Retention:** **Settings > Advanced > Backups to keep** (default 5, up to 50). Archives also expire after 7 days. The archive needed for a revert is always kept.

Keep a separate, tested full-site backup before production recovery. See [Backups and restore](https://docs.3techagency.com/documentation/reference-and-help/backups-and-restore).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.3techagency.com/help-center/workflows-and-recovery/backup-coverage-and-restore.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.