Better explain where to find the dump file

I really had problem finding the dump file with the explanation as give before. I thought that the `~/.borgmatic/` would be my current user. So looked into `/home/gerd/.borgmatic` (wrong). Then I looked into `<EXTRACTED_DESTINATION_PATH/.borgmatic` (again wrong). Then finally (1h later and after having already prepared a bug ticketI figured out that the dump file is within `<EXTRACTED_DESTINATION_PATH/root/.borgmatic`. Hard to find because of course I d not only have `root` within `<EXTRACTED_DESTINATION_PATH/` but also all other backup'ed directories (including /etc/, /home/ on so on...)
This commit is contained in:
gerdneuman 2022-03-17 04:51:47 +00:00
parent 5b3cfc542d
commit 6f3accf691
1 changed files with 12 additions and 3 deletions

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).
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