check --repair for an specific repository #446

New Issue

Closed

opened 2021-09-06 06:55:16 +00:00 by hrv231 · 11 comments

hrv231 commented 2021-09-06 06:55:16 +00:00

Copy Link

What I'm trying to do and why

I deleted some of my files of one repo by mistake, was able to restore them, but for some reason the repo has some problems.
I wanted to do something like "borgmatic check --repository /mnt/myrepo --repair" but obviously it doesn't work.

Steps to reproduce (if a bug)

I would like this feature on the cli to be added if possible please.

Expected behavior (if a bug)

Expected to be able to do a check --repair to one specific repository.

Other notes / implementation ideas

On the documentation I don't see a way to run borgmatic check for an specific repo, supposed I have more than repo, using the guide "Make per-application backups".

Is there any way to include a way to specify on the cli with borgmatic an specific repository?
If not, can you add that as a feature?

Environment

borgmatic version: [1.5.12]

borgmatic installation method: [Docker container]

Borg version: [1.1.15]

Python version: [3.8.10]

#### What I'm trying to do and why I deleted some of my files of one repo by mistake, was able to restore them, but for some reason the repo has some problems. I wanted to do something like "borgmatic check --repository /mnt/myrepo --repair" but obviously it doesn't work. #### Steps to reproduce (if a bug) I would like this feature on the cli to be added if possible please. #### Expected behavior (if a bug) Expected to be able to do a check --repair to one specific repository. #### Other notes / implementation ideas On the documentation I don't see a way to run borgmatic check for an specific repo, supposed I have more than repo, using the guide "Make per-application backups". Is there any way to include a way to specify on the cli with borgmatic an specific repository? If not, can you add that as a feature? #### Environment **borgmatic version:** [1.5.12] **borgmatic installation method:** [Docker container] **Borg version:** [1.1.15] **Python version:** [3.8.10]

ams_tschoening commented 2021-09-07 06:22:31 +00:00

Copy Link

How do you maintain your multiple, per-app backups? If using individual YAML files, like in my case, you should be able to 1. make BorgMatic run with that config file and hence repo only and 2., issue arbitrary Borg commands as well. Look at the following example:

borgmatic --config ~/.config/borgmatic.d/[...].yaml --verbosity 2 borg info
borgmatic --config ~/.config/borgmatic.d/[...].yaml --verbosity 2 borg delete --first 1 --stats

How do you maintain your multiple, per-app backups? If using individual YAML files, like in my case, you should be able to 1. make BorgMatic run with that config file and hence repo only and 2., issue arbitrary Borg commands as well. Look at the following example: ```bash borgmatic --config ~/.config/borgmatic.d/[...].yaml --verbosity 2 borg info borgmatic --config ~/.config/borgmatic.d/[...].yaml --verbosity 2 borg delete --first 1 --stats ```

hrv231 commented 2021-09-08 00:56:55 +00:00

Author

Copy Link

Thanks for your example.

I tried to do it but it gives me this error, maybe it is because I'm running it on a docker container ?

So, after seeing the error with borgmatic --config location/.yaml borg info , I decided to try it without the "borg" and it is working.

Can you tell me why I'm not able to run arbitrary Borg commands ? is it because of the version I'm running?

Thanks for your example. I tried to do it but it gives me this error, maybe it is because I'm running it on a [docker container](https://hub.docker.com/r/b3vis/borgmatic/) ? So, after seeing the error with `borgmatic --config location/.yaml borg info` , I decided to try it without the "borg" and it is working. Can you tell me why I'm not able to run arbitrary Borg commands ? is it because of the version I'm running? 

image.png

293 KiB

ams_tschoening commented 2021-09-08 07:10:39 +00:00

Copy Link

Can you tell me why I'm not able to run arbitrary Borg commands ? is it because of the version I'm running?

Would have been of help if you had provided the version your are running. :-) But yes, to me it looks like your version is simply too old. borg is not part of the valid arguments printed in your screenshot.

(No borg action in borgmatic? Time to upgrade!)

https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/

> Can you tell me why I'm not able to run arbitrary Borg commands ? is it because of the version I'm running? Would have been of help if you had provided the version your are running. :-) But yes, to me it looks like your version is simply too old. `borg` is not part of the valid arguments printed in your screenshot. > (No borg action in borgmatic? Time to upgrade!) https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/

hrv231 commented 2021-09-08 16:46:37 +00:00

Author

Copy Link

Version of borgmatic and borg is on the ticket, at the beginning :-)
version 1.5.12

That version is like 8 months old, do you think that it, or it might be something with the docker from https://hub.docker.com/r/b3vis/borgmatic/

Version of borgmatic and borg is on the ticket, at the beginning :-) version 1.5.12 That version is like 8 months old, do you think that it, or it might be something with the docker from https://hub.docker.com/r/b3vis/borgmatic/

ams_tschoening commented 2021-09-08 17:11:41 +00:00

Copy Link

Seems to have been introduced with 1.5.15:

#425: Run arbitrary Borg commands with new "borgmatic borg" action. See the documentation
for more information: https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/

cf8882f2bc

Seems to have been introduced with 1.5.15: > #425: Run arbitrary Borg commands with new "borgmatic borg" action. See the documentation > for more information: https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/ https://projects.torsion.org/witten/borgmatic/commit/cf8882f2bcde934119c375997e2cbefe5f35f96a

👍 1

witten commented 2021-09-09 03:30:19 +00:00

Owner

Copy Link

Can confirm! The borgmatic borg action was added in borgmatic 1.5.15. So upgrading would certainly be a decent work-around right now. But I agree that a --repository flag to the check action would be helpful.

And thanks @ams_tschoening for jumping in on this ticket.

Can confirm! The `borgmatic borg` action was added in borgmatic 1.5.15. So upgrading would certainly be a decent work-around right now. But I agree that a `--repository` flag to the `check` action would be helpful. And thanks @ams_tschoening for jumping in on this ticket.

hrv231 commented 2021-09-09 03:40:18 +00:00

Author

Copy Link

Thank you both, I'll upgrade asap.

Thank you both, I'll upgrade asap.

👍 1

hrv231 closed this issue 2021-09-09 03:40:18 +00:00

witten commented 2021-09-09 03:54:02 +00:00

Owner

Copy Link

Reopening for the --repository flag on check! That still seems useful to me, even if there's a work-around.

Reopening for the `--repository` flag on `check`! That still seems useful to me, even if there's a work-around.

witten reopened this issue 2021-09-09 03:54:02 +00:00

witten commented 2023-02-04 17:45:17 +00:00

Owner

Copy Link

Related/overlapping ticket: #564.

Related/overlapping ticket: #564.

witten added the

good first issue

label 2023-02-04 17:45:36 +00:00

diivi commented 2023-03-21 19:37:07 +00:00

Collaborator

Copy Link

@witten so this can be closed now that #564 is closed?

@witten so this can be closed now that #564 is closed?

witten commented 2023-03-21 19:57:56 +00:00

Owner

Copy Link

Yes, thank you!

Yes, thank you!

witten closed this issue 2023-03-21 19:57:56 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

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

4 Participants

Notifications

Subscribe

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#446

No description provided.