Update docs/how-to/backup-your-databases.md #806
No reviewers
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#806
Loading…
Reference in New Issue
No description provided.
Delete Branch "axel/borgmatic:docs-databases-sqlite-info"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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).
In this line and the previous: "sqlite" -> "SQLite".
Edit: Also ")." -> ".)"
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!
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.
Sounds good!
Do you still plan to work on this? If not, just let me know. Thanks!
Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.