borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
14
57
Fork 41
Code Issues 53 Pull Requests 2 Actions Packages Releases 122 Activity

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.
This commit is contained in:
axel simon 2023-12-30 23:41:02 +00:00
parent 9d6025e902
commit b1d3534d17
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/how-to/backup-your-databases.md
View File

@ -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