Better explain where to find the dump file when doing a manual restore (#510).
Reviewed-on: https://projects.torsion.org/borgmatic-collective/borgmatic/pulls/510
This commit is contained in:
commit
cd88f9f2ea
1 changed files with 12 additions and 3 deletions
|
@ -210,9 +210,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
|
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
|
[extract](https://torsion.org/borgmatic/docs/how-to/extract-a-backup/) an
|
||||||
archive containing a database dump, and then manually restore the dump file
|
archive containing a database dump.
|
||||||
found within the extracted `~/.borgmatic/` path (e.g. with `pg_restore`,
|
|
||||||
`mysql`, or `mongorestore`, commands).
|
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
|
## Preparation and cleanup hooks
|
||||||
|
|
Loading…
Reference in a new issue