restic-systemd-automatic-backup | Automatic restic backup using Backblaze B2 storage | Continuous Backup library

Depending on your system, the setup will look different. Choose one of.
Linux + Systemd
macOS + LaunchAgent
Windows + ScheduledTask
Cron - for any system having a cron daemon. Tested on FreeBSD and macOS.
Create B2 credentials as instructed below
Install config and scripts: $ sudo make install-systemd ☝ Note: sudo is required here, as some files are installed into system directories (/etc/ and /usr/bin). Have a look to the Makefile to know more.
Fill out configuration values (edit with sudo): /etc/restic/pw.txt - Contains the password (single line) to be used by restic to encrypt the repository files. Should be different than your B2 password! /etc/restic/_global.env.sh - Global environment variables. /etc/restic/default.env.sh - Profile specific environment variables (multiple profiles can be defined by copying to /etc/restic/something.env.sh). /etc/restic/backup_exclude.txt - List of file patterns to ignore. This will trim down your backup size and the speed of the backup a lot when done properly!
Initialize remote repo as described below
Configure how often back up should be made. Edit if needed OnCalendar in /usr/lib/systemd/system/restic-backup@.timer.
Enable automated backup for starting with the system (enable creates symlinks): $ sudo systemctl enable --now restic-backup@default.timer
And run an immediate backup if you want (if not, it will run on daily basis): $ sudo systemctl start restic-backup@default
Watch its progress with Systemd journal: $ journalctl -f --lines=50 -u restic-backup@default
Verify the backup $ sudo -i $ source /etc/restic/default.env.sh $ restic snapshots
(optional) Define multiple profiles: just make a copy of the default.env.sh and use the defined profile name in place of default to run backups or enable timers. Notice that the value after @ works as a parameter.
(optional) Enable the check job that verifies that the backups for the profile are all intact. $ sudo systemctl enable --now restic-check@default.timer
(optional) Setup email on failure as described here
LaunchAgent is the modern service scheduler in in macOS that uses Launchd. Launchd is the modern built-in service scheduler in macOS. It has support for running services as root (Daemon) or as a normal user (Agent). Here we set up an LauchAgent to be run as your normal user for starting regular backups.
This is one of may ways you can get restic and this backup script working on Windows:.
Install scoop
Install dependencies from a PowerShell with administrator privileges: powershell> scoop install restic make git
In a non-privileged PowerShell, start git-bash and clone this repo powershell> git-bash git-bash$ mkdir ~/src && cd ~/src/ git-bash$ git clone https://github.com/erikw/restic-systemd-automatic-backup.git && cd $(basename "$_" .git)
Install scripts, conf and the ScheduledTask git-bash$ make install-schedtask
Edit configs and initialize repo according to TL;DR section above git-bash$ vim /etc/restic/* git-bash$ source /etc/restic/default.env.sh git-bash$ restic init git-bash$ restic_backup.sh Note that you should use cygwin/git-bash paths e.g. in default.env.sh you can have export RESTIC_BACKUP_PATHS='/c/Users/<username>/My Documents'
Inspect the installed tasks and make a test run Open the app "Task Scheduler" (taskschd.msc) Go to the local "Task Scheduler Library" Right click on one of the newly installed tasks e.g. restic_backup and click "run". If the tasks are not there, maybe you opended it up before make install-schedtask: just close and start it again to refresh. Now a git-bash window should open running restic_backup.sh, and the next time the configured schedule hits!
With taskschd.msc you can easily start, stop, delete and configure the scheduled tasks to your liking.
If you want to run an all-classic cron job instead, do like this:.
Follow the main setup from Step-by-step and manual setup but skip the systemd parts.
etc/cron.d/restic: Depending on your system's cron, put this in /etc/cron.d/ or similar, or copy the contents to $(sudo crontab -e). The format of this file is tested under FreeBSD, and might need adaptions depending on your cron.
You can use $ make install-cron to copy it over to /etc/cron.d.
(Optional) bin/cron_mail: A wrapper for running cron jobs, that sends output of the job as an email using the mail(1) command.