> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/configuration/bindplane/backup-and-disaster-recovery/bolt-store.md).

# Bolt Store

How to backup and recover Bindplane when using Bolt Store

When Bindplane is configured to use Bolt Store as the storage backend, a [bbolt](https://github.com/etcd-io/bbolt) database on the filesystem is created. Bbolt is deprecated in favor of PostgreSQL. This documentation can be used when backing up your Bbolt based Bindplane installation.

### Backup

The Bolt Store database file is constantly written to. In order to guarantee consistency and avoid corruption of the backup file, Bindplane must be stopped before the database file can be copied.

```bash
sudo systemctl stop bindplane

sudo cp \
    /var/lib/bindplane/storage/bindplane.db \
    /var/lib/bindplane/storage/bindplane-$(date '+%Y-%m-%d_%H:%M:%S').db

sudo systemctl start bindplane
```

After copying the database file, the storage directory will look something like this:

```
/var/lib/bindplane/storage
├── bindplane-2023-08-03_15:04:31.db
└── bindplane.db
```

It is recommended that the copied database files be moved to a remote system, such as a backup server or a secure object storage service like Google Cloud Storage or Amazon S3.

### Restore

To restore a backup of Bolt Store, use the following process:

1. Stop the server: `sudo systemctl stop bindplane`
2. Backup the current database file
3. Copy a previous database backup file to `/var/lib/bindplane/storage/bindplane.db`
4. Start Bindplane: `sudo systemctl start bindplane`


---

# 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.bindplane.com/configuration/bindplane/backup-and-disaster-recovery/bolt-store.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.