Multiple profile configuration (#45)

Adds possibility to have multiple profiles with different backup paths, retention etc.

Co-authored-by: Matt Feifarek <matt.feifarek@gmail.com>
Co-authored-by: Erik Westrup <erik.westrup@gmail.com>

.gitignore

@@ -1,3 +1,10 @@
 # Prevent check-in of these sensitive files. Instead they are generated from the corresponding *.template file.
-/etc/restic/b2_pw.txt
+etc/restic/pw.txt
-/etc/restic/b2_env.sh
+etc/restic/_global.env
+etc/restic/default.env
+
+# IntelliJ
+.idea/
+*.iml
+# VSCode
+.vscode/

CHANGELOG.md

@@ -5,6 +5,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
+### Added
+- Extract all variables from `restic_backup.sh` to allow for having multiple backup profiles.
+
+### Fixed
+- `restic_backup.sh` now finds `.backup_exclude` files on each backup path as intended.
 
 ## [1.0.1] - 2021-12-03
 ### Fixed

Makefile

@@ -7,14 +7,14 @@ SRCS_SCRIPTS	= $(filter-out %cron_mail, $(wildcard usr/local/sbin/*))
 SRCS_CONF	= $(sort $(patsubst %.template, %, $(wildcard etc/restic/*)))
 SRCS_SYSTEMD	= $(wildcard etc/systemd/system/*)
 
-# Just set PREFIX in environment, like
+# To change the installation root path, set the PREFIX variable in your shell's environment, like:
-# $ PREFIX=/tmp/test make
+# $ PREFIX=/usr/local make install
+# $ PREFIX=/tmp/test make install
 DEST_SCRIPTS	= $(PREFIX)/usr/local/sbin
 DEST_CONF	= $(PREFIX)/etc/restic
 DEST_SYSTEMD	= $(PREFIX)/etc/systemd/system
 
-INSTALLED_FILES = $(addprefix $(PREFIX)/, $(SRCS_SCRIPTS) $(SRCS_CONF) $(SRCS_SYSTEMD)) \
+INSTALLED_FILES = $(addprefix $(PREFIX)/, $(SRCS_SCRIPTS) $(SRCS_CONF) $(SRCS_SYSTEMD))
-			$(DEST_CONF)/b2_env.sh $(DEST_CONF)/b2_pw.txt
 
 ### Targets ###
 # target: all - Default target.
@@ -35,16 +35,16 @@ install-scripts:
 
 # Copy templates to new files with restricted permissions.
 # Why? Because the non-template files are git-ignored to prevent that someone who clones or forks this repo checks in their sensitive data like the B2 password!
-etc/restic/b2_env.sh etc/restic/b2_pw.txt:
+etc/restic/_global.env etc/restic/default.env etc/restic/pw.txt:
 	install -m 0600 $@.template $@
 
 # target: install-conf - Install restic configuration files.
 # will create these files locally only if they don't already exist
-# | means that dependencies are order-only i.e. only created if they don't already exist.
+# `|` means that dependencies are order-only, i.e. only created if they don't already exist.
 install-conf: | $(SRCS_CONF)
 	install -d $(DEST_CONF)
 	install -b -m 0600 $(SRCS_CONF) $(DEST_CONF)
-	$(RM) etc/restic/b2_env.sh etc/restic/b2_pw.txt
+	$(RM) etc/restic/_global.env etc/restic/default.env etc/restic/pw.txt
 
 # target: install-systemd - Install systemd timer and service files.
 install-systemd:

README.md

@@ -7,7 +7,7 @@
 [![Open issues](https://img.shields.io/github/issues/erikw/restic-systemd-automatic-backup)](https://github.com/erikw/restic-systemd-automatic-backup/issues)
 [![Closed issues](https://img.shields.io/github/issues-closed/erikw/restic-systemd-automatic-backup?color=success)](https://github.com/erikw/restic-systemd-automatic-backup/issues?q=is%3Aissue+is%3Aclosed)
 [![Closed PRs](https://img.shields.io/github/issues-pr-closed/erikw/restic-systemd-automatic-backup?color=success)](https://github.com/erikw/restic-systemd-automatic-backup/pulls?q=is%3Apr+is%3Aclosed)
-[![License](https://img.shields.io/badge/license-BSD--3-blue)](LICENSE.txt)
+[![License](https://img.shields.io/badge/license-BSD--3-blue)](LICENSE)
 [![OSS Lifecycle](https://img.shields.io/osslifecycle/erikw/restic-systemd-automatic-backup)](https://github.com/Netflix/osstracker)
 [![Latest tag](https://img.shields.io/github/v/tag/erikw/restic-systemd-automatic-backup)](https://github.com/erikw/restic-systemd-automatic-backup/tags)
 <br>
@@ -25,7 +25,6 @@ Unfortunately restic does not come pre-configured with a way to run automated ba
 
 Here follows a step-by step tutorial on how to set it up, with my sample script and configurations that you can modify to suit your needs.
 
-
 Note, you can use any of the supported [storage backends](https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html). The setup should be similar but you will have to use other configuration variables to match your backend of choice.
 
 # Requirements
@@ -33,7 +32,51 @@ Note, you can use any of the supported [storage backends](https://restic.readthe
 * (recommended)  `make` if you want an automated install
   * Arch: part of the `base-devel` meta package, Debian/Ubuntu: part of the `build-essential` meta package, macOS: preinstalled make works)
 
-# Set up
+# TL;DR Setup
+1. Create B2 credentials as instructed [below](#1-create-backblaze-b2-account)
+1. Install config and scripts:
+   ```console
+   $ sudo make install
+   ```
+   ☝ **Note**: `sudo` is required here, as some files are installed into system directories (`/etc/`
+   and `/usr/sbin`). Have a look to the `Makefile` to know more.
+1. 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` - Global environment variables.
+   * `/etc/restic/default.env` - Profile specific environment variables (multiple profiles can be defined by copying to `/etc/restic/something.env`).
+   * `/etc/restic/backup_exclude` - List of file patterns to ignore. This will trim down your backup size and the speed of the backup a lot when done properly!
+1. Initialize remote repo as described [below](#3-initialize-remote-repo)
+1. Configure [how often](https://www.freedesktop.org/software/systemd/man/systemd.time.html#Calendar%20Events) back up should be made.
+   * Edit if needed `OnCalendar` in `/etc/systemd/system/restic-check@.timer`.
+1. Enable automated backup for starting with the system (`enable` creates symlinks):
+   ```console
+   $ sudo systemctl start restic-backup@default.timer
+   $ sudo systemctl enable restic-backup@default.timer
+   ```
+1. And run an immediate backup if you want (if not, it will run on daily basis):
+   ```console
+   $ sudo systemctl start restic-backup@default
+   ```
+1. Watch its progress with Systemd journal:
+   ```console
+   $ journalctl -f --lines=50 -u restic-backup@default
+   ```
+1. Verify the backup
+   ```console
+   $ sudo -i
+   $ source /etc/restic/default.env
+   $ restic snapshots
+   ```
+1. (optional) Define multiple profiles: just make a copy of the `default.env` 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.
+1. (optional) Enable the check job that verifies that the backups for the profile are all intact.
+   ```console
+   $ sudo systemctl start restic-check@default.timer
+   $ sudo systemctl enable restic-check@default.timer
+   ````
+1. (optional) Setup email on failure as described [here](#8-email-notification-on-failure)
+
+# Step-by-step and manual setup
+This is a more detailed explanation than the TL;DR section that will give you more understanding in the setup, and maybe inspire you to develop your own setup based on this one even!
 
 Tip: The steps in this section will instruct you to copy files from this repo to system directories. If you don't want to do this manually, you can use the Makefile:
 
@@ -48,59 +91,83 @@ $ yaourt -S restic-systemd-automatic-backup
 ````
 
 ## 1. Create Backblaze B2 account
+First, see this official Backblaze [tutorial](https://help.backblaze.com/hc/en-us/articles/4403944998811-Quickstart-Guide-for-Restic-and-Backblaze-B2-Cloud-Storage) on restic, and follow the instructions ("Create Backblaze account with B2 enabled") there on how to create a new B2 bucket. In general, you'd want a private bucket, without B2 encryption (restic does the encryption client side for us) and without the object lock feature.
 
-First, see this official Backblaze [tutorial](https://help.backblaze.com/hc/en-us/articles/115002880514-How-to-configure-Backblaze-B2-with-Restic-on-Linux) on restic, and follow the instructions ("Create Backblaze account with B2 enabled") there on how to create a new B2 bucket.
+Take note of the your account ID and application key for the next steps. It's a good idea to create a separate application key that has access only to the newly created b2 bucket you created.
-
-Take note of the your account ID, application key and password for the next steps.
 
 
 ## 2. Configure your B2 account locally
+> **Attention!** Going the manual way requires that most of the following commands are run as root.
+
 Put these files in `/etc/restic/`:
-* `b2_env.sh`: Fill this file out with your B2 bucket settings etc. The reason for putting these in a separate file is that it can be used also for you to simply source, when you want to issue some restic commands. For example:
+* `_global.env`: Fill this file out with your global settings including B2 accountID & accountKey. A global exclude list is set here (explained in section below).
+* `default.env`: This is the default profile. Fill this out with bucket name, backup paths and retention policy. This file sources `_global.env` and is thus self-contained and can be sourced in the shell when you want to issue some manual restic commands. For example:
    ```console
-$ source /etc/restic/b2_env.sh
+   $ source /etc/restic/default.env
    $ restic snapshots    # You don't have to supply all parameters like --repo, as they are now in your environment!
    ````
-* `b2_pw.txt`: This file should contain the restic repository password. This is a new password what soon will be used when initializing the new repository. It should be unique to this restic backup repository and is needed for restoring from it. Don't re-use your B2 login password, this should be different.
+* `pw.txt`: This file should contain the restic password used to encrypt the repository. This is a new password what soon will be used when initializing the new repository. It should be unique to this restic backup repository and is needed for restoring from it. Don't re-use your B2 login password, this should be different. For example you can generate a 128 character password (must all be on one line) with:
+   ```console
+   $ openssl rand -base64 128 | tr -d '\n' > /etc/restic/pw.txt
+   ```
 
 ## 3. Initialize remote repo
 Now we must initialize the repository on the remote end:
 ```console
-$ source /etc/restic/b2_env.sh
+$ sudo -i
+$ source /etc/restic/default.env
 $ restic init
 ```
 
 ## 4. Script for doing the backup
 Put this file in `/usr/local/sbin`:
-* `restic_backup.sh`: A script that defines how to run the backup. Edit this file to respect your needs in terms of backup which paths to backup, retention (number of backups to save), etc.
+* `restic_backup.sh`: A script that defines how to run the backup. The intention is that you should not need to edit this script yourself, but be able to control everything from the `*.env` profiles.
 
-Copy this file to `/etc/restic/backup_exclude` or `~/.backup_exclude`:
+Restic support exclude files. They list file pattern paths to exclude from you backups, files that just occupy storage space, backup-time, network and money. `restic_backup.sh` allows for a few different exclude files.
-* `.backup_exclude`: A list of file pattern paths to exclude from you backups, files that just occupy storage space, backup-time, network and money.
+* `/etc/restic/backup_exclude` - global exclude list. You can use only this one if your setup is easy. This is set in `_global.env`. If you need a different file for another profile, you can override the envvar `RESTIC_BACKUP_EXCLUDE_FILE` in this profile.
+* `.backup_exclude` per backup path. If you have e.g. an USB disk mounted at /mnt/media and this path is included in the `$BACKUP_PATHS`, you can place a file `/mnt/media/.backup_exclude` and it will automatically picked up. The nice thing about this is that the backup paths are self-contained in terms of what they shoud exclude!
 
-
+## 5. Make first backup
-## 5. Make first backup & verify
+Now see if the backup itself works, by running as root
-Now see if the backup itself works, by running
 
 ```console
+$ sudo -i
+$ source /etc/restic/default.env
 $ /usr/local/sbin/restic_backup.sh
-$ restic snapshots
 ````
 
-## 6. Backup automatically; systemd service + timer
+## 6. Verify the backup
+As the `default.env` is already sourced in your root shell, you can now just list the snapshos
+```console
+$ sudo -i
+$ source /etc/restic/default.env
+$ restic snapshots
+```
+
+Alternatively you can mount the restic snapshots to a directory set `/mnt/restic`
+```console
+$ restic mount /mnt/restic
+$ ls /mnt/restic
+```
+
+## 7. Backup automatically; systemd service + timer
 Now we can do the modern version of a cron-job, a systemd service + timer, to run the backup every day!
 
-
 Put these files in `/etc/systemd/system/`:
-* `restic-backup.service`: A service that calls the backup script.
-* `restic-backup.timer`: A timer that starts the backup every day.
 
+* `restic-backup@.service`: A service that calls the backup script with the specified profile. The profile is specified
+  by the value after `@` when running it (see below).
+* `restic-backup@.timer`: A timer that starts the former backup every day (same thing about profile here).
+   * If needed, edit this file to configure [how often](https://www.freedesktop.org/software/systemd/man/systemd.time.html#Calendar%20Events) back up should be made. See the `OnCalendar` key in the file.
 
 Now simply enable the timer with:
 ```console
-$ systemctl start restic-backup.timer
+$ systemctl start restic-backup@default.timer
-$ systemctl enable restic-backup.timer
+$ systemctl enable restic-backup@default.timer
 ````
 
+ ☝ **Note**: You can run it with different values instead of `default` if you use multiple profiles.
+
 You can see when your next backup is scheduled to run with
 ```console
 $ systemctl list-timers | grep restic
@@ -115,20 +182,20 @@ $ systemctl status restic-backup
 or start a backup manually
 
 ```console
-$ systemctl start restic-backup
+$ systemctl start restic-backup@default
 ```
 
 You can follow the backup stdout output live as backup is running with:
 
 ```console
-$ journalctl -f -u restic-backup.service
+$ journalctl -f -u restic-backup@default.service
 ````
 
 (skip `-f` to see all backups that has run)
 
 
 
-## 7. Email notification on failure
+## 8. Email notification on failure
 We want to be aware when the automatic backup fails, so we can fix it. Since my laptop does not run a mail server, I went for a solution to set up my laptop to be able to send emails with [postfix via my Gmail](https://easyengine.io/tutorials/linux/ubuntu-postfix-gmail-smtp/). Follow the instructions over there.
 
 Put this file in `/usr/local/sbin`:
@@ -140,10 +207,17 @@ Put this files in `/etc/systemd/system/`:
 As you maybe noticed already before, `restic-backup.service` is configured to start `status-email-user.service` on failure.
 
 
-## 8. Optional: automated backup checks
+## 9. Optional: automated backup checks
 Once in a while it can be good to do a health check of the remote repository, to make sure it's not getting corrupt. This can be done with `$ restic check`.
 
-There are some `*-check*`-files in this git repo. Install these in the same way you installed the `*-backup*`-files.
+There is companion scripts, service and timer (`*check*`) to restic-backup.sh that checks the restic backup for errors; look in the repo in `etc/systemd/system` and `usr/local/sbin` and copy what you need over to their corresponding locations.
+
+```console
+$ sudo -i
+$ systemctl start restic-check@default.timer
+$ systemctl enable restic-check@default.timer
+````
+
 
 
 # Cron?

etc/restic/_global.env.template

@@ -0,0 +1,20 @@
+# Global envionment variables
+# These variables are sourced FIRST, and any values inside of *.env files for
+# specific configurations will override if also defined there.
+
+
+# Official instructions on how to setup the restic variables for Backblaze B2 can be found at
+# https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#backblaze-b2
+
+
+# The restic repository encryption key
+export RESTIC_PASSWORD_FILE="/etc/restic/pw.txt"
+# The global restic exclude file
+export RESTIC_BACKUP_EXCLUDE_FILE="/etc/restic/backup_exclude"
+
+# Backblaze B2 credentials
+export B2_ACCOUNT_ID="<b2-account-id>"   # TODO fill with your account info
+export B2_ACCOUNT_KEY="<b2-account-key>" # TODO fill with your account info
+
+# How many network connections to set up to B2. Default is 5.
+export B2_CONNECTIONS=10

etc/restic/b2_env.sh.template

@@ -1,8 +0,0 @@
-# B2 credentials.
-# Extracted settings so both systemd timers and user can just source this when want to work on my B2 backup.
-# See https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html
-
-export RESTIC_REPOSITORY="b2:<b2-repo-name>"
-export RESTIC_PASSWORD_FILE="/etc/restic/b2_pw.txt"
-export B2_ACCOUNT_ID="<b2-account-id>"
-export B2_ACCOUNT_KEY="<b2-account-key>"

etc/restic/b2_pw.txt.template

@@ -1 +0,0 @@
-<b2-password>

etc/restic/default.env.template

@@ -0,0 +1,34 @@
+# This is the default profile. Fill it with your desired configuration.
+# Additionally, you can create and use more profiles by copying this file.
+
+# This file (and other .env files) has two purposes:
+# - being sourced by systemd timers to setup the backup before running restic_backup.sh
+# - being sourced in a user's shell to work directly with restic commands e.g.
+#  $ source /etc/restic/default.env
+#  $ restic snapshots
+#  Thus you don't have to provide all the arguments like
+#  $ restic --repo ... --password-file ...
+
+source /etc/restic/_global.env
+
+# Below envvar will override those in _global.env
+
+export RESTIC_REPOSITORY="b2:<b2-repo-name>"   # TODO fill with your repo name
+
+# What to backup (paths our mountpoints) e.g. "/ /boot /home /mnt/media".
+# To backup only your home directory, set "/home/your-user"
+export BACKUP_PATHS=""  # TODO fill conveniently with one or multiple paths
+
+# Example below of how to dynamically add a path that is mounted e.g. external USB disk.
+# restic does not fail if a specified path is not mounted, but it's nicer to only add if they are available.
+#test -d /mnt/media && BACKUP_PATHS+=" /mnt/media"
+
+# A tag to identify backup snapshots.
+export BACKUP_TAG=systemd.timer
+
+# Retention policy - How many backups to keep.
+# See https://restic.readthedocs.io/en/stable/060_forget.html?highlight=month#removing-snapshots-according-to-a-policy
+export RETENTION_DAYS=14
+export RETENTION_WEEKS=16
+export RETENTION_MONTHS=18
+export RETENTION_YEARS=3

etc/restic/pw.txt.template

@@ -0,0 +1 @@
+<restic-encryption-password>

etc/systemd/system/restic-backup.service

@@ -1,11 +0,0 @@
-[Unit]
-Description=Backup with restic to Backblaze B2
-OnFailure=status-email-user@%n.service
-Requires=nm-unmetered-connection.service
-
-[Service]
-Type=simple
-Nice=10
-ExecStart=/usr/local/sbin/restic_backup.sh
-# $HOME or $XDG_CACHE_HOME must be set for restic to find /root/.cache/restic/
-Environment="HOME=/root"

etc/systemd/system/restic-backup@.service

@@ -0,0 +1,13 @@
+[Unit]
+Description=Backup with restic to Backblaze B2
+OnFailure=status-email-user@%n.service
+Requires=nm-unmetered-connection.service
+
+[Service]
+Type=simple
+Nice=10
+# $HOME or $XDG_CACHE_HOME must be set for restic to find /root/.cache/restic/
+Environment="HOME=/root"
+# The random sleep (in seconds) is in the case of multiple backup profiles. Many restic instances started at the same time could case high load or network bandwith usage.
+# `systemd-cat` allows showing the restic output to the systemd journal
+ExecStart=bash -c 'sleep $(shuf -i 0-300 -n 1) && source /etc/restic/%I.env && /usr/local/sbin/restic_backup.sh | systemd-cat'

etc/systemd/system/restic-check@.service

@@ -7,4 +7,5 @@ Requires=nm-unmetered-connection.service
 [Service]
 Type=simple
 Nice=10
-ExecStart=/usr/local/sbin/restic_check.sh
+# `systemd-cat` allows showing the restic output to the systemd journal
+ExecStart=bash -c 'source /etc/restic/%I.env && /usr/local/sbin/restic_check.sh | systemd-cat'

usr/local/sbin/restic_backup.sh

@@ -1,9 +1,15 @@
 #!/usr/bin/env bash
-# Make backup my system with restic to Backblaze B2.
+# Make a backup with restic to Backblaze B2.
-# This script is typically run by: /etc/systemd/system/restic-backup.{service,timer}
+#
+# This script is typically run (as root user) either like:
+# - from restic service/timer: $PREFIX/etc/systemd/system/restic-backup.{service,timer}
+# - from a cronjob: $PREFIX/etc/cron.d/restic
+# - manually by a user. For it to work, the environment variables must be set in the shell where this script is executed
+#   $ source $PREFIX/etc/default.env
+#   $ restic_backup.sh
 
-# Exit on failure, pipe failure
+# Exit on error, unset var, pipe failure
-set -e -o pipefail
+set -euo pipefail
 
 # Clean up lock if we are killed.
 # If killed by systemd, like $(systemctl stop restic), then it kills the whole cgroup and all it's subprocesses.
@@ -15,39 +21,20 @@ exit_hook() {
 }
 trap exit_hook INT TERM
 
-# How many backups to keep.
+# Set up exclude files: global + path-specific ones
-RETENTION_DAYS=14
+# NOTE that restic will fail the backup if not all listed --exclude-files exist. Thus we should only list them if they are really all available.
-RETENTION_WEEKS=16
+##  Global backup configuration.
-RETENTION_MONTHS=18
+exclusion_args="--exclude-file ${RESTIC_BACKUP_EXCLUDE_FILE}"
-RETENTION_YEARS=3
+## Self-contained backup files per backup path. E.g. having an USB disk at /mnt/media in BACKUP_PATHS,
-
+# a file /mnt/media/.backup_exclude will automatically be detected and used:
-# What to backup, and what to not
+for backup_path in ${BACKUP_PATHS[@]}; do
-BACKUP_PATHS="/ /boot /home"
+	if [ -f "$backup_path/.backup_exclude" ]; then
-# Example below of how dynamically add a path that is mounted e.g. external USB dis.
+		exclusion_args+=" --exclude-file $backup_path/.backup_exclude"
-[ -d /mnt/media ] && BACKUP_PATHS+=" /mnt/media"
-
-# Set up exclude files: global + path-specific ones.
-BACKUP_EXCLUDES="--exclude-file /etc/restic/backup_exclude"
-for dir in /home/*
-do
-	if [ -f "$dir/.backup_exclude" ]
-	then
-		BACKUP_EXCLUDES+=" --exclude-file $dir/.backup_exclude"
 	fi
 done
 
-BACKUP_TAG=systemd.timer
-
-
-# Set all environment variables like
-# B2_ACCOUNT_ID, B2_ACCOUNT_KEY, RESTIC_REPOSITORY etc.
-source /etc/restic/b2_env.sh
-
-# How many network connections to set up to B2. Default is 5.
-B2_CONNECTIONS=50
-
 # NOTE start all commands in background and wait for them to finish.
-# Reason: bash ignores any signals while child process is executing and thus my trap exit hook is not triggered.
+# Reason: bash ignores any signals while child process is executing and thus the trap exit hook is not triggered.
 # However if put in subprocesses, wait(1) waits until the process finishes OR signal is received.
 # Reference: https://unix.stackexchange.com/questions/146756/forward-sigterm-to-child-in-bash
 
@@ -64,7 +51,7 @@ restic backup \
 	--one-file-system \
 	--tag $BACKUP_TAG \
 	--option b2.connections=$B2_CONNECTIONS \
-	$BACKUP_EXCLUDES \
+	$exclusion_args \
 	$BACKUP_PATHS &
 wait $!
 

usr/local/sbin/restic_check.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
-# Check my backup with  restic to Backblaze B2 for errors.
+# Check the backups made with restic to Backblaze B2 for errors.
-# This script is typically run by: /etc/systemd/system/restic-check.{service,timer}
+# See restic_backup.sh on how this script is run (as it's analogous for this script).
 
 # Exit on failure, pipe failure
 set -e -o pipefail
@@ -15,12 +15,6 @@ exit_hook() {
 }
 trap exit_hook INT TERM
 
-
-source /etc/restic/b2_env.sh
-
-# How many network connections to set up to B2. Default is 5.
-B2_CONNECTIONS=50
-
 # Remove locks from other stale processes to keep the automated backup running.
 # NOTE nope, don't unlock like restic_backup.sh. restic_backup.sh should take precedence over this script.
 #restic unlock &