From b1d3534d170e5f132711e7b5aca823a0049bfa8e Mon Sep 17 00:00:00 2001 From: axel simon Date: Sat, 30 Dec 2023 23:41:02 +0000 Subject: [PATCH] Update docs/how-to/backup-your-databases.md Make it clearer that sqlite databases are dumped and therefore require as much extra disk space available than the target database takes. --- docs/how-to/backup-your-databases.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/how-to/backup-your-databases.md b/docs/how-to/backup-your-databases.md index f4508356..dee19b61 100644 --- a/docs/how-to/backup-your-databases.md +++ b/docs/how-to/backup-your-databases.md @@ -58,10 +58,13 @@ mariadb_databases: As part of each backup, borgmatic streams a database dump for each configured database directly to Borg, so it's included in the backup without consuming -additional disk space. (The exceptions are the PostgreSQL/MongoDB "directory" -dump formats, which can't stream and therefore do consume temporary disk -space. Additionally, prior to borgmatic 1.5.3, all database dumps consumed -temporary disk space.) +additional disk space. + +⚠️ The exceptions are the PostgreSQL/MongoDB "directory" dump formats, which +can't stream, as well as sqlite databases which are dumped. These therefore do +consume temporary disk space. (As much as the target database, for sqlite). +(Additionally, prior to borgmatic 1.5.3, all database dumps consumed temporary +disk space.) To support this, borgmatic creates temporary named pipes in `~/.borgmatic` by default. To customize this path, set the `borgmatic_source_directory` option -- 2.40.1