{"id":92534,"date":"2019-04-25T08:00:36","date_gmt":"2019-04-25T08:00:36","guid":{"rendered":"https:\/\/fedoramagazine.org\/?p=27506"},"modified":"2019-04-25T08:00:36","modified_gmt":"2019-04-25T08:00:36","slug":"automate-backups-with-restic-and-systemd","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2019\/04\/25\/automate-backups-with-restic-and-systemd\/","title":{"rendered":"Automate backups with restic and systemd"},"content":{"rendered":"

Timely backups are important. So much so that backing up software<\/a> is a common topic of discussion, even here on the Fedora Magazine<\/a>. This article demonstrates how to automate backups with restic<\/strong> using only systemd unit files.<\/p>\n

For an introduction to restic, be sure to check out our article Use restic on Fedora for encrypted backups<\/a>. Then read on for more details.<\/p>\n

<\/span> <\/p>\n

Two systemd services are required to run in order to automate taking snapshots and keeping data pruned. The first service runs the backup<\/em> command needs to be run on a regular frequency. The second service takes care of data pruning.<\/p>\n

If you’re not familiar with systemd at all, there’s never been a better time to learn. Check out the series on systemd here at the Magazine<\/a>, starting with this primer on unit files:<\/p>\n

\n
\n

systemd unit file basics<\/a><\/p><\/blockquote>\n<\/div>\n<\/figure>\n

If you haven’t installed restic already, note it’s in the official Fedora repositories. To install use this command with sudo<\/a>:<\/p>\n

$ sudo dnf install restic<\/pre>\n
Backup<\/h2>\n
First, create the ~\/.config\/systemd\/user\/restic-backup.service<\/em> file. Copy and paste the text below into the file for best results.<\/p>\n
[Unit]
Description=Restic backup service
[Service]
Type=oneshot
ExecStartPre=restic unlock
ExecStart=restic backup --verbose --one-file-system --tag systemd.timer $BACKUP_EXCLUDES $BACKUP_PATHS
ExecStartPost=restic forget --verbose --tag systemd.timer --group-by \"paths,tags\" --keep-daily $RETENTION_DAYS --keep-weekly $RETENTION_WEEKS --keep-monthly $RETENTION_MONTHS --keep-yearly $RETENTION_YEARS
EnvironmentFile=%h\/.config\/restic-backup.conf
<\/pre>\n
This service references an environment file in order to load secrets (such as RESTIC_PASSWORD<\/em>). Create the ~\/.config\/restic-backup.conf<\/em> file. Copy and paste the content below for best results. This example uses BackBlaze B2 buckets. Adjust the ID, key, repository, and password values accordingly.<\/p>\n
BACKUP_PATHS=\"\/home\/rupert\"
BACKUP_EXCLUDES=\"--exclude-file \/home\/rupert\/.restic_excludes --exclude-if-present .exclude_from_backup\"
RETENTION_DAYS=7
RETENTION_WEEKS=4
RETENTION_MONTHS=6
RETENTION_YEARS=3
B2_ACCOUNT_ID=XXXXXXXXXXXXXXXXXXXXXXXXX
B2_ACCOUNT_KEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
RESTIC_REPOSITORY=b2:XXXXXXXXXXXXXXXXXX:\/
RESTIC_PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<\/pre>\n
Now that the service is installed, reload systemd: systemctl –user daemon-reload<\/em>. Try running the service manually to create a backup: systemctl –user start restic-backup<\/em>.<\/p>\n
Because the service is a oneshot<\/em>, it will run once and exit. After verifying that the service runs and creates snapshots as desired, set up a timer to run this service regularly. For example, to run the restic-backup.service<\/em> daily, create ~\/.config\/systemd\/user\/restic-backup.timer<\/em> as follows. Again, copy and paste this text:<\/p>\n
[Unit]
Description=Backup with restic daily
[Timer]
OnCalendar=daily
Persistent=true
[Install]
WantedBy=timers.target
<\/pre>\n
Enable it by running this command:<\/p>\n
$ systemctl --user start restic-backup.timer<\/pre>\n
Prune<\/h2>\n
While the main service runs the forget<\/em> command to only keep snapshots within the keep policy, the data is not actually removed from the restic repository. The prune<\/em> command inspects the repository and current snapshots, and deletes any data not associated with a snapshot. Because prune<\/em> can be a time-consuming process, it is not necessary to run every time a backup is run. This is the perfect scenario for a second service and timer. First, create the file ~\/.config\/systemd\/user\/restic-prune.service<\/em> by copying and pasting this text:<\/p>\n
[Unit]
Description=Restic backup service (data pruning)
[Service]
Type=oneshot
ExecStart=restic prune
EnvironmentFile=%h\/.config\/restic-backup.conf
<\/pre>\n
Similarly to the main restic-backup.service<\/em>, restic-prune<\/em> is a oneshot service and can be run manually. Once the service has been set up, create and enable a corresponding timer at ~\/.config\/systemd\/user\/restic-prune.timer<\/em>:<\/p>\n
[Unit]
Description=Prune data from the restic repository monthly
[Timer]
OnCalendar=monthly
Persistent=true
[Install]
WantedBy=timers.target
<\/pre>\n
That’s it! Restic will now run daily and prune data monthly.<\/p>\n
\n
Photo by <\/em>Samuel Zeller<\/em><\/a> on <\/em>Unsplash<\/em><\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
Timely backups are important. So much so that backing up software is a common topic of discussion, even here on the Fedora Magazine. This article demonstrates how to automate backups with restic using only systemd unit files. For an introduction to restic, be sure to check out our article Use restic on Fedora for encrypted […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[45,61,46,47],"class_list":["post-92534","post","type-post","status-publish","format-standard","hentry","category-fedora-os","tag-fedora","tag-fedora-project-community","tag-magazine","tag-news"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/92534","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=92534"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/92534\/revisions"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=92534"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=92534"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=92534"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}