docs: update disaster recovery chapter#2310
Conversation
bruno-at-bareos
left a comment
There was a problem hiding this comment.
First round of lecture, a few details might be to adjusted.
Nice improvements.
I will redo it step by step, and we might want to discuss a bit more in depth about restoring the configuration.
When we do the bextract, we normally get it from the same jobs.
bruno-at-bareos
left a comment
There was a problem hiding this comment.
see suggestions for postgres
|
After a full real testing, there's an issue of chicken and eggs. We first state but then we have two paragraph later 🙄 Which means from my understanding and experiments that we have to deeply insist to have a copy of the configuration outside of the volume, otherwise you can't access it from the volume, and replace formulation like by something more imperious like To be done: |
6390b06 to
5606bef
Compare
pstorz
left a comment
There was a problem hiding this comment.
Please see my comments :)
d7ec09b to
63f218d
Compare
bruno-at-bareos
left a comment
There was a problem hiding this comment.
Nice improvement, great work.
- global improvements removing obsoleted instructions - use correct syntax for titles - use ``su postgres`` call for db scripts - use code-block to separate command from result - add preliminary step to reinstall the software - add warning about keeping a separated copy of configuration - fix bextract and bls requirement (sd configuration is needed) - improve code block in restore steps - change ``Bareos uses the same data format for all data carriers`` as is no more strictly correct for dedupable backend. However, the API stays the same that is spoken to the backends. Co-authored-by: Philipp Storz <philipp.storz@bareos.com>
Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
746b93d to
9a19192
Compare
This PR aims to improve the Disaster Recovery chapter
Please check
If you have any questions or problems, please give a comment in the PR.
Helpful documentation and best practices
Checklist for the reviewer of the PR (will be processed by the Bareos team)
Make sure you check/merge the PR using
devtools/pr-toolto have some simple automated checks run and a proper changelog record added.General
Source code quality