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

Better explain where to find the dump file #510

Merged
witten merged 1 commits from gerdneuman/borgmatic:gerdneuman-patch-1 into master 2022-05-20 16:33:23 +00:00
Conversation 0 Commits 1 Files Changed 1 +12 -3
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -209,9 +209,18 @@ to exclude are `/dev` and `/run`, but that may not be exhaustive.
If you prefer to restore a database without the help of borgmatic, first
[extract](https://torsion.org/borgmatic/docs/how-to/extract-a-backup/) an
archive containing a database dump, and then manually restore the dump file
found within the extracted `~/.borgmatic/` path (e.g. with `pg_restore`,
`mysql`, or `mongorestore`, commands).
archive containing a database dump.
The dump file can then be found in the extracted destination path within the
`~/.borgmatic/` directory. The `~` here corresponds to the HOME directory of
the user with whom you created the backup. For example, if you created the
backup with the `root` user, then the dump will be in
`EXTRACTED_DESTINATION_PATH/root/.borgmatic`. This also means you will have
to backup the HOME directory of that user you use to run `borgmatic create`
(otherwise there the dump file will not be available).
witten commented 2022-04-23 21:40:07 +00:00
Review
Copy Link

Thanks for taking the time to submit this PR! Generally looks good! However, the last sentence of this paragraph isn't correct; when you have databases configured in borgmatic's configuration file and run borgmatic create, borgmatic automatically adds the appropriate ~/.borgmatic paths containing the database dumps to the created Borg archive. There's no need to add it manually.

Thanks for taking the time to submit this PR! Generally looks good! However, the last sentence of this paragraph isn't correct; when you have databases configured in borgmatic's configuration file and run `borgmatic create`, borgmatic automatically adds the appropriate `~/.borgmatic` paths containing the database dumps to the created Borg archive. There's no need to add it manually.
gerdneuman commented 2022-04-24 05:10:47 +00:00
Review
Copy Link

OK, I had no idea. Could you then just change the last sentence with this regards? This would be the easiest.

I have set up borgmatic a few weeks ago (for the first time) and have problems "thinking" into it again (understanding). Also, I did not fully understand your last sentence fully yet - I would have to run it first - and I do not have access at the moment to my server.

So, it would be nice if you could just change the last paragraph and then commit/merge it. Thank you.

OK, I had no idea. Could you then just change the last sentence with this regards? This would be the easiest. I have set up borgmatic a few weeks ago (for the first time) and have problems "thinking" into it again (understanding). Also, I did not fully understand your last sentence fully yet - I would have to run it first - and I do not have access at the moment to my server. So, it would be nice if you could just change the last paragraph and then commit/merge it. Thank you.
witten commented 2022-05-20 16:32:41 +00:00
Review
Copy Link

Sure thing! Thanks again.

Sure thing! Thanks again.
You can then use the dump file to manually restore it using the native database
commands like `pg_restore`, `mysql`, `mongorestore` or similar.
## Preparation and cleanup hooks