simplysraka.blogg.se - Duplicacy vs restic

#DUPLICACY VS RESTIC FULL#
#DUPLICACY VS RESTIC PASSWORD#

BACKUP_CRON - A cron expression to run the backup.

RESTIC_REPOSITORY must remain it's default value! To tag the images created by the container. Will also be used for restic init during first start when the repository is not initialized.

#DUPLICACY VS RESTIC PASSWORD#

RESTIC_PASSWORD - the password for the restic repository.

RESTIC_REPOSITORY - the location of the restic repository.

The container is setup by setting environment variables and volumes. If you mount /restore you should set -target /restore and data will end up in /restore/data/path/to/files. The target is / since all data backed up should be inside the host mounted /data dir. abcdef12 docker exec -ti restic-backup-var restic restore -include /data/path/to/files -target / abcdef12 Get your snapshot ID with docker exec -ti restic-backup-var restic snapshotsĮ.g. restore to not override existing data while restoring. You might want to mount a separate hostvolume at e.g. To execute a backup manually independent of the CRON run: docker exec -ti restic-backup-var /bin/backupīackup a single file or directory docker exec -ti restic-backup-var restic backup /data/path/to/dir -tag my-tag You can execute restic with docker exec -ti restic-backup-var restic Backup Use the running containerĪssuming the container name is restic-backup-var

#DUPLICACY VS RESTIC FULL#

If configured, you can find the full output of the mail notification in /var/log/mail-last.log. When the backup fails the log is copied to /var/log/restic-error-last.log. docker logsĪdditionally you can see the the full log, including restic output, of the last execution in /var/log/backup-last.log. If needed you can create volumes for them. try to run restic snapshots to list all your snapshots. Now you can use restic as documented, e.g. To enter your container execute docker exec -ti backup-test /bin/sh If you'd like to change the arguments passed to restic init, you can do so using the RESTIC_INIT_ARGS env variable. The repository is initialized automatically by the container. The container will backup ~/test-data to a repository with password test at ~/test-repo every minute. Existing containers with that names are completly removed automatically. This will run the container backup-test with the name backup-test. Please don't hesitate to report any issue you find. You need to add your hook script in the container folder /hooks: -v ~/home/user/hooks:/hooksĬall your pre backup script pre-backup.sh and post backup script post-backup.sh If you need to execute a script before or after each backup,

Latest (experimental) docker pull lobaro/restic-backup-docker:latest Stable docker pull lobaro/restic-backup-docker:1.2-0.9.4

Support restic mount inside the container to browse the backup files.

Support for different targets (tested with: Local, NFS, SFTP, AWS).

This container runs restic backups in regular intervals. A docker container to automate restic backups