> 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/rdm/fr/knowledge-base/how-to-articles/sqlite-and-xml-local-backup.md).

# Sauvegarde locale SQLite et XML

Sauvegarder les espaces de travail SQLite ou XML dans un fichier RDM local chiffré qui peut être stocké chez un fournisseur infonuagique synchronisé.

La fonctionnalité ***Sauvegarde de fichier*** vous permet de sauvegarder vos espaces de travail SQLite ou XML dans un fichier local avec une clé maîtresse. Elle crée un fichier **RDM** qui peut ensuite être stocké chez un fournisseur infonuagique synchronisé (p. ex., OneDrive, Google Drive, Dropbox, etc.).

Vous pouvez la trouver lors de la modification de votre espace de travail dans Remote Desktop Manager dans ***Fichier*** – ***Espaces de travail***. Pour un guide étape par étape et la liste complète des paramètres, voir [Sauvegarde de fichier](/rdm/fr/ribbon-menu-bar/file/backup/file-backup.md).

#### Voir aussi

* [Devolutions Academy – Activer les sauvegardes de données et travailler hors connexion](https://academy.devolutions.net/student/activity/3266687)


---

# 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/rdm/fr/knowledge-base/how-to-articles/sqlite-and-xml-local-backup.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.