50 lines
2.4 KiB
Markdown
50 lines
2.4 KiB
Markdown
# Kubernetes Volume Snapshots
|
|
|
|
It is possible to backup persistent volumes through volume snapshots. This is especially handy if you don't want to stop the database to create an [offline backup](../neo4j-offline-backup/README.md) thus having a downtime.
|
|
|
|
Kubernetes announced this feature in a [blog post](https://kubernetes.io/blog/2018/10/09/introducing-volume-snapshot-alpha-for-kubernetes/). Please make yourself familiar with it before you continue.
|
|
|
|
## Create a Volume Snapshot
|
|
|
|
There is an example in this folder how you can e.g. create a volume snapshot for the persistent volume claim of the database `volume-claim-ocelot-neo4j`, or for the uploads of the backend `volume-claim-ocelot-uploads`.
|
|
|
|
Replace `YYYY-MM-DD` in the `metadata.name` entry in the yaml files with the actual date before you enter the following commands:
|
|
|
|
```bash
|
|
# in folder deployment/volumes/volume-snapshots/
|
|
kubectl apply -f neo4j-data-snapshot.yaml
|
|
# in case the images are stored on backend and not in S3 storage
|
|
kubectl apply -f backen-uploads-snapshot.yaml
|
|
```
|
|
|
|
If you are on DigitalOcean the volume snapshot should show up in the Web UI:
|
|
|
|
|
|
|
|
## Provision a Volume based on a Snapshot
|
|
|
|
Edit your persistent volume claim configuration and add a `dataSource` pointing
|
|
to your volume snapshot. [The blog post](https://kubernetes.io/blog/2018/10/09/introducing-volume-snapshot-alpha-for-kubernetes/) has an example in section "Provision a new volume from a snapshot with
|
|
Kubernetes".
|
|
|
|
There is also an example in this folder how the configuration could look like. If you apply the configuration new persistent volume claim will be provisioned with the data from the volume snapshot:
|
|
|
|
```bash
|
|
# in folder deployment/volumes/volume-snapshots/
|
|
kubectl apply -f neo4j-data-provision-snapshot.yaml
|
|
```
|
|
|
|
## Data Consistency Warning
|
|
|
|
Note that volume snapshots do not guarantee data consistency. Quote from the
|
|
[blog post](https://kubernetes.io/blog/2018/10/09/introducing-volume-snapshot-alpha-for-kubernetes/):
|
|
|
|
> Please note that the alpha release of Kubernetes Snapshot does not provide
|
|
> any consistency guarantees. You have to prepare your application (pause
|
|
> application, freeze filesystem etc.) before taking the snapshot for data
|
|
> consistency.
|
|
|
|
In case of Neo4J this probably means that enterprise edition is required which
|
|
supports [online backups](https://neo4j.com/docs/operations-manual/current/backup/).
|
|
|