geirgp/rpi-docker-backup repository overview

Forked from https://github.com/boombatower/docker-backup⁠ and adapted for RPi

⁠Assumptions

This tool assumes that the data container it is to operate on exists. In the event of a catastrophic failure this means the data container must be initialized before this tool can restore the data into it.

Typically that will look something like the following.

$ docker run --name data-container -v /some/volume hypriot/rpi-node /bin/true

⁠Usage

Backups are placed in the /backup directory which is exposed as a volume so that other containers may access the tarballs after they are created. The backup can either be transported directly from the container to remote storage or using Docker bind mount can be extracted onto the host.

⁠Backup

To dump backup archive from data-container into current directory:

$ docker run --rm \
  --volumes-from data-container \
  -v $(pwd):/backup \
  geirgp/rpi-docker-backup backup```

#### Restore

To restore

```sh
$ docker run --rm \
  --volumes-from data-container \
  -v $(pwd):/backup \
  geirgp/rpi-docker-backup restore```

### Amazon S3
For storing backups in Amazon S3 see [geirgp/rpi-docker-backup-s3](https://hub.docker.com/r/geirgp/rpi-docker-backup-s3/)