The reason is that we might want to independently retry the offsite backup in case it fails but not rerun the primary backup in that case.
This isn't possible with the current setup and so we'll have to split this up into two oneshot services.
The way it works is that borg-backup.service will schedule borg-backup-offsite.service to run after it which ensures that
no two backups are running at the same time and also that they can be indendently retried if one of them fails.

Sven-Hendrik Haase authored Dec 23, 2020 and Frederik Schwan committed Dec 25, 2020

The perl script is currently breaking and there's not really an advantage to keeping it around.
We've never used it.

Use Gitlab's official backup tool for dumping the database, git
repositories and other data with a wrapper script similiar to the
postgres and mysql backup scripts.

Signed-off-by: Jelle van der Waa <jelle@archlinux.org>

Remove the leftover artifact from the time we used xtrabackup.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

The discovery script now uses a regex and no longer cares where exactly
accounting is enabled. Follow systemd upstream by enabling it by
default.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

When using when: on ansible, it already checks if the variable is
set or not. But the variable must still be defined.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

I've had mode=755 create garbage already...

This allows to call borg commands without having to provide the backup
destination each time.

Signed-off-by: Florian Pritz <bluewind@xinu.at>