borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 53 Pull Requests 1 Actions Packages Releases 121 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
gerdneuman commented 2022-03-17 04:52:26 +00:00
Contributor
Copy Link

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

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...)
gerdneuman added 1 commit 2022-03-17 04:52:27 +00:00
continuous-integration/drone/pr Build is passing Details
6f3accf691 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...)
witten requested changes 2022-04-23 21:40:28 +00:00
docs/how-to/backup-your-databases.md
@ -215,0 +217,4 @@
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
Owner
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
Author
Contributor
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
Owner
Copy Link

Sure thing! Thanks again.

Sure thing! Thanks again.
witten merged commit cd88f9f2ea into master 2022-05-20 16:33:23 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
witten
Labels
Clear labels   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#510
No description provided.
Delete Branch "gerdneuman/borgmatic:gerdneuman-patch-1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?