Docker image to initialize, backup to, and restore from a Restic repository on AWS S3.
- Create an S3 bucket to hold your backups
- Supply all appropriate environment variables
- Initialize the Restic repository on S3 to hold the backups (one-time only)
- Run a backup and check your bucket for that backup
-
AWS_ACCESS_KEY_ID- used for S3 interactions -
AWS_SECRET_ACCESS_KEY- used for S3 interactions -
AWS_DEFAULT_REGION- AWS default region for S3 bucket -
FSBACKUP_MODE=[init|backup|restore]-initinitializes the Restic repository at$RESTIC_REPOSITORY(only do this once);backupperforms a backup;restoreperforms a restoration. -
RESTIC_BACKUP_ARGS- additional arguments to pass to 'restic backup' command -
RESTIC_FORGET_ARGS- additional arguments to pass to 'restic forget --prune' command (e.g., --keep-daily 7 --keep-weekly 5 --keep-monthly 3 --keep-yearly 2) -
RESTIC_HOST- hostname to be used for the backup -
RESTIC_PASSWORD- password for the Restic repository -
RESTIC_REPOSITORY- Restic repository location (e.g., 's3:s3.amazonaws.com/bucketname/restic') -
RESTIC_TAG- tag to apply to the backup -
SOURCE_PATH- full path to the source directory to be backed up -
TARGET_PATH- full path to the target directory to be restored to (usually the same as the SOURCE_PATH)
It's recommended that your S3 bucket NOT have versioning turned on. Old versions of Restic's repository files are not useful.