hosting/mash-playbook
1
0
Fork 0
Code Pull requests Activity

Update backup-borg documentation with regard to external servers

Browse source 
Fixes https://github.com/mother-of-all-self-hosting/mash-playbook/issues/56
This commit is contained in:
Slavi Pantaleev 2023-05-12 07:09:22 +03:00
parent debfd9c1aa
commit 4eb71df91a
1 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/services/backup-borg.md
View file

@ -8,8 +8,14 @@ You will need a remote server where borg will store the backups. There are hoste
The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day.
By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)) or MariaDB as MySQL server, Borg backups will also include dumps of your databases. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for Borg using the `backup_borg_postgresql_enabled` variable.
By default, Borg backups will include a dump of your database if you're using the [integrated Postgres server](postgres.md) or the [integrated MariaDB server](mariadb.md). An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md).
If you decide to go with another solution:
- you can disable Postgres-backup support for Borg using the `backup_borg_postgresql_enabled` variable.
- you can disable MariaDB-backup support for Borg using the `backup_borg_mysql_enabled` variable.
If you're using an external database server (regardless of type), you may point borgbackup to it. See the `backup_borg_postgresql_*` or `backup_borg_mysql_*` variables.
## Prerequisites