From 92354a77eeebf101c83b6077789037d93577c97e Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Mon, 9 May 2022 16:08:47 -0700 Subject: [PATCH] Mention that database dumps consumed disk space prior to borgmatic 1.5.3. --- docs/how-to/backup-your-databases.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/how-to/backup-your-databases.md b/docs/how-to/backup-your-databases.md index 297cf4002..5677a08ff 100644 --- a/docs/how-to/backup-your-databases.md +++ b/docs/how-to/backup-your-databases.md @@ -33,7 +33,8 @@ 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.) +space. 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