> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeper-connection-manager/installation/backup-and-recovery.md).

# Backup & Recovery

Backup and recovery options

Keeper Connection Manager is packaged and installed in your environment. As such, backups should be taken in order to recover the environment if required.

It is highly recommended to perform backups of the following components:

1. [Server backup](#server-backup-instructions)
2. [Database snapshots](#database-snapshots)
3. [Docker compose](#docker-compose) and other critical files

### Server Backup Instructions

* We recommend performing daily snapshots of your Keeper Connection Manager instances.
* In most installations, a database running locally or within the Docker containers includes the connection and user data. When backing up the instance, ensure that the database is included.
* When using the Advanced Linux Install method, ensure that the /etc/guacamole/ folder is included in the snapshot.

### Database Snapshots

* For Docker and Auto Docker install methods, the `kcm-setup.run backup` command will run a backup locally.
* For other installation methods, please use the database platform's backup features, for example `mysqladmin` on MySQL-backed installs.

### Docker compose

* Back up and protect the files located in `/etc/kcm-setup/` which include `docker-compose.yml` and any other files which are being utilized by your container.


---

# 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.keeper.io/keeper-connection-manager/installation/backup-and-recovery.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.