> 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/concepts/advanced-concepts/recovery-options.md).

# Recovery options

Recovery options in Devolutions Server describe backing up the SQL database and web application, generating a recovery kit, and restoring an instance.

Recovery options in Devolutions Server describe how to back up critical components and restore the platform after an incident. Administrators configure backups of the SQL database and web application folder in Backup manager and generate a recovery kit that contains the settings and encryption material required to rebuild an instance on new infrastructure.

In a disaster, documented recovery steps guide you through deploying a new server, restoring the backup, and applying the recovery kit so vaults, permissions, and recordings are recovered. Testing this process regularly in a staging environment helps validate that recovery objectives can be met.

#### Related topics

* [Backup manager](https://docs.devolutions.net/server/web-interface/administration/backup/backup-manager.md)
* [Recovery kit generation](https://docs.devolutions.net/server/devolutions-server-console/recovery-kit-generation.md)
* [Restore a Devolutions Server instance](https://docs.devolutions.net/server/knowledge-base/how-to-articles/restore-a-devolutions-server-instance.md)


---

# 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/concepts/advanced-concepts/recovery-options.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.
