> For the complete documentation index, see [llms.txt](https://docs.human-connection.org/human-connection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.human-connection.org/human-connection/deployment/volumes.md).

# Volumes

At the moment, the application needs two persistent volumes:

* The `/data/` folder where `neo4j` stores its database and
* the folder `/nitro-backend/public/uploads` where the backend stores uploads.

As a matter of precaution, the persistent volume claims that setup these volumes live in a separate folder. You don't want to accidently loose all your data in your database by running

```bash
kubectl delete -f human-connection/
```

or do you?

## Create Persistent Volume Claims

Run the following:

```bash
# in folder deployments/
$ kubectl apply -f volumes
persistentvolumeclaim/neo4j-data-claim created
persistentvolumeclaim/uploads-claim created
```

## Backup and Restore

We tested a couple of options how to do disaster recovery in kubernetes. First, there is the [offline backup strategy](/human-connection/deployment/volumes/neo4j-offline-backup.md) of the community edition of Neo4J, which you can also run on a local installation. Kubernetes also offers so-called [volume snapshots](/human-connection/deployment/volumes/volume-snapshots.md). Changing the [reclaim policy](/human-connection/deployment/volumes/reclaim-policy.md) of your persistent volumes might be an additional safety measure. Finally, there is also a kubernetes specific disaster recovery tool called [Velero](/human-connection/deployment/volumes/velero.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.human-connection.org/human-connection/deployment/volumes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.