> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/web-interface/administration/backup/backup-history.md).

# Backup history

Review the Devolutions Server backup history log, showing start and end times, filenames, notes, and success or failure status for each backup.

The ***Backup History*** section displays the list of the backups that have been run with messages related to their success or failure.

<table><thead><tr><th width="178">Column</th><th>Description</th></tr></thead><tbody><tr><td>Start date/time</td><td>Date and time when the backup process was started.</td></tr><tr><td>End date/time</td><td>Date and time when the backup process was stopped.</td></tr><tr><td>Notes</td><td>Message to inform the completion or the fail of the backup.</td></tr><tr><td>Filename</td><td>Path and name of the web application backup file.</td></tr><tr><td>Database filename</td><td>Path and name of the SQL database backup file.</td></tr><tr><td>Success</td><td>A check mark will indicate a successful backup, while an X will indicate that the backup has failed.</td></tr></tbody></table>

#### See also

* [Devolutions Academy – Configuring backups](https://academy.devolutions.net/student/path/2942210/activity/4493538)


---

# 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.devolutions.net/server/web-interface/administration/backup/backup-history.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.
