Selfhosted

I'm using crestic to make backups easier to configure.
It makes configuring different backup targets very easy with a simple ini-style config file.

https://fedoramagazine.org/automate-backups-with-restic-and-systemd

Pretty much followed it word for word to set up backups for my systems.

two repos, one local one remote, alternating between them manually, using https://gitlab.com/stormking/resticguigx/ (I wrote that)

Here's mine:

shared.sh

#!/bin/bash

# Sources to be backed up
SOURCES=(
    "/srv/dev-disk-by-uuid-a57d5696-00fk-4d1c-9885-095ad5cf71ba/Stuff/"
)

# Restic configurations
RESTIC_CONFIG_LOCATION="/srv/dev-disk-by-uuid-a77de696-04f9-4d1c-9875-055advcf71ba/Stuff/Projects/Setup/Backups/restic-config"
RESTIC_REPO="/srv/dev-disk-by-uuid-25EE65533BB23C37/restic/repo"
RESTIC_PASSWORD_FILE="${RESTIC_CONFIG_LOCATION}/config/password.txt"
RESTIC_EXCLUDE_FILE="${RESTIC_CONFIG_LOCATION}/config/excludes.txt"
RESTIC_LOG_LOCATION="${RESTIC_CONFIG_LOCATION}/logs"
RESTIC_LOCK_LOCATION="${RESTIC_REPO}/locks"
RESTIC_MOUNT_LOCATION="/srv/dev-disk-by-uuid-28EE65538BB23J37/restic/mount"

# RClone configurations
RCLONE_CONFIG="${RESTIC_CONFIG_LOCATION}/config/rclone.conf"
RCLONE_REPO="bucket:restic-backup"

function unlock-repo() {
    if [[ $(ls -A ${RESTIC_LOCK_LOCATION}) ]] ; then
        restic -r ${RESTIC_REPO} unlock --password-file=${RESTIC_PASSWORD_FILE}
    fi
}

backup.sh

#!/usr/bin/env bash

# Get the directory this script is from, and then source the
# shared.sh shell script for the environment variables and
# functions
BASEDIR=$(dirname "$0")
source "${BASEDIR}/shared.sh"

RESTIC_LOG_FILE="${RESTIC_LOG_LOCATION}/log-backup.txt"

# Backs up the sources to the local Restic repository
function backup() {
    # Get the latest saved parent snapshot ID
    local short_id=$(restic -r ${RESTIC_REPO} --password-file=${RESTIC_PASSWORD_FILE} --json snapshots | jq -r 'max_by(.time) | .short_id')
    # Back up and log the results
    (
        echo
        echo
        date
        echo
        echo
        restic -r ${RESTIC_REPO} backup ${SOURCES[@]} --exclude-file=${RESTIC_EXCLUDE_FILE} --password-file=${RESTIC_PASSWORD_FILE} --parent ${short_id} --compression max
    ) >>${RESTIC_LOG_FILE}
}

function main() {
    unlock-repo
    backup
}

main $@

validate.sh

#!/usr/bin/env bash

BASEDIR=$(dirname "$0")
source "${BASEDIR}/shared.sh"

RESTIC_LOG_FILE="${RESTIC_LOG_LOCATION}/log-validate.txt"

# Validates the local Restic repository.
function validate-locally() {
    (
        echo
        echo
        date
        echo
        echo
        restic -r ${RESTIC_REPO} check --read-data --password-file=${RESTIC_PASSWORD_FILE}
    ) >>${RESTIC_LOG_FILE}
}

function main() {
    unlock-repo
    validate-locally
}

main $@

sync.sh

#!/usr/bin/env bash

BASEDIR=$(dirname "$0")
source "${BASEDIR}/shared.sh"

RESTIC_LOG_FILE="${RESTIC_LOG_LOCATION}/log-sync.txt"

# Syncs the local Restic repository to the cloud provider, under the 'Restic' folder.
function cloud-sync() {
    (
        echo
        echo
        date
        echo
        echo
    ) >>${RESTIC_LOG_FILE}
    rclone -v sync ${RESTIC_REPO} ${RCLONE_REPO} --config=${RCLONE_CONFIG} --log-file=${RESTIC_LOG_FILE} --b2-hard-delete
    rclone cleanup ${RCLONE_REPO} --config=${RCLONE_CONFIG} --log-file=${RESTIC_LOG_FILE}
}

function main() {
    cloud-sync
}

main $@

After jumping between duplicati, duplicacy, borg backup, kopia I finally settled on Restic a couple of weeks ago.

Using it with resticprofile (https://github.com/creativeprojects/resticprofile) on Linux and Windows which does all the heavy lifting converting the setup from a simple configuration file to restic commands and adding a few options like calling webhooks on specific conditions etc. It is running rock stable so far.

https://creativeprojects.github.io/resticprofile/configuration/getting_started/index.html