Update docs/how-to/backup-your-databases.md #806

Open
axel wants to merge 1 commits from axel/borgmatic:docs-databases-sqlite-info into main
Contributor

Make it clearer that sqlite databases are dumped and therefore require as much extra disk space available than the target database takes. Not that this bit me or anything with a silly large 43 Gb sqlite database that shouldn't even exist in the first place.

Make it clearer that sqlite databases are dumped and therefore require as much extra disk space available than the target database takes. Not that this bit me or anything with a silly large 43 Gb sqlite database that shouldn't even exist in the first place.
axel added 1 commit 2023-12-30 23:48:13 +00:00
b1d3534d17 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.
witten requested changes 2023-12-30 23:59:48 +00:00
witten left a comment
Owner

Thanks for doing this one as well. I actually don't think there's any good reason for the borgmatic SQLite hook to dump to an intermediate file. I'd be happy to merge this for now (after the requested capitalization changes!), but I've filed #807 to encompass the work of making SQLite dumps stream directly to Borg.

Thanks for doing this one as well. I actually don't think there's any good reason for the borgmatic SQLite hook to dump to an intermediate file. I'd be happy to merge this for now (after the requested capitalization changes!), but I've filed #807 to encompass the work of making SQLite dumps stream directly to Borg.
@ -65,0 +62,4 @@
⚠️ 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).
Owner

In this line and the previous: "sqlite" -> "SQLite".

Edit: Also ")." -> ".)"

In this line and the previous: "sqlite" -> "SQLite". Edit: Also ")." -> ".)"
Owner

Some good news and some bad news. The bad news is I implemented #807, so this PR is now out of date. The good news is I implemented #807, so SQLite dumps will no longer use an intermediate file and fill up your disk!

Some good news and some bad news. The bad news is I implemented #807, so this PR is now out of date. The good news is I implemented #807, so SQLite dumps will no longer use an intermediate file and fill up your disk!
Author
Contributor

Sorry, slow reply.
Ah ha, excellent. Well that just good news for everyone really (and the other piece of good news for me is that i no longer need to backup a 43 GB sqlite database, which is really a lot nicer).
I'll try to update the PR.

Sorry, slow reply. Ah ha, excellent. Well that just good news for everyone really (and the other piece of good news for me is that i no longer need to backup a 43 GB sqlite database, which is really a lot nicer). I'll try to update the PR.
Owner

Sounds good!

Sounds good!
Owner

Do you still plan to work on this? If not, just let me know. Thanks!

Do you still plan to work on this? If not, just let me know. Thanks!
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b axel-docs-databases-sqlite-info main
git pull docs-databases-sqlite-info

Step 2:

Merge the changes and update on Gitea.
git checkout main
git merge --no-ff axel-docs-databases-sqlite-info
git push origin main
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#806
No description provided.