> 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/cloud/concepts/advanced-concepts/recovery-options.md). # Recovery options Recover Devolutions Cloud data through backups, rekeying, cached offline access, and vault restoration after incidents. Recovery options describe how to regain access to data in Devolutions Cloud after user loss, configuration issues, or major incidents. The disaster recovery guide explains how to back up entries, while cached offline mode in tools like Remote Desktop Manager or Devolutions Password Manager provides read-only access when Devolutions Cloud is temporarily unavailable. Rekeying procedures enable you to regenerate encryption keys and re-encrypt configuration files when necessary. Administrators can also restore deleted vaults, convert a departed user’s vault into a shared vault, and follow documented steps to recover from serious outages. In practice, these options are usually combined with the emergency kit so owners can regain administrative access even when primary credentials or identity providers are unavailable. #### Related topics * [Backup and recovery steps for Devolutions Cloud entries](/cloud/knowledge-base/knowledge-base-articles/backup-and-recovery-steps-for-devolutions-cloud-entries.md) * [Delete and restore vaults](/cloud/web-interface/administration/management/vaults/delete-and-restore-vaults.md) * [Restore a user vault](/cloud/knowledge-base/how-to-articles/restore-a-user-vault.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/cloud/concepts/advanced-concepts/recovery-options.md?ask=&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.