Clarify manual database extraction documentation.
This commit is contained in:
parent
cd88f9f2ea
commit
fbd381fcc1
1 changed files with 6 additions and 8 deletions
|
@ -212,15 +212,13 @@ 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.
|
archive containing a database dump.
|
||||||
|
|
||||||
The dump file can then be found in the extracted destination path within the
|
borgmatic extracts the dump file into the *`username`*`/.borgmatic/` directory
|
||||||
`~/.borgmatic/` directory. The `~` here corresponds to the HOME directory of
|
within the extraction destination path, where *`username`* is the user that
|
||||||
the user with whom you created the backup. For example, if you created the
|
created the backup. For example, if you created the backup with the `root`
|
||||||
backup with the `root` user, then the dump will be in
|
user and you're extracting to `/tmp`, then the dump will be in
|
||||||
`EXTRACTED_DESTINATION_PATH/root/.borgmatic`. This also means you will have
|
`/tmp/root/.borgmatic`.
|
||||||
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
|
After extraction, you can manually restore the dump file using native database
|
||||||
commands like `pg_restore`, `mysql`, `mongorestore` or similar.
|
commands like `pg_restore`, `mysql`, `mongorestore` or similar.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue