Borgmatic evaluates exclude patterns wrong #149

New Issue

Closed

opened 2019-03-11 21:13:10 +00:00 by skorokithakis · 5 comments

skorokithakis commented 2019-03-11 21:13:10 +00:00

Copy Link

I have an exclude_patterns pattern of */dirname/*. Borgmatic evaluates it to misc/dirname/log.log because the rest of the directories under there require root access, so it can't read them, but that causes Borg to try to archive them and fail (because they require root access), and the entire backup fails.

Why is Borgmatic trying to evaluate my patterns? Why not just pass them to Borg as I entered them?

I have an `exclude_patterns` pattern of `*/dirname/*`. Borgmatic evaluates it to `misc/dirname/log.log` because the rest of the directories under there require root access, so it can't read them, but that causes Borg to try to archive them and fail (because they require root access), and the entire backup fails. Why is Borgmatic trying to evaluate my patterns? Why not just pass them to Borg as I entered them?

witten commented 2019-03-11 21:31:26 +00:00

Owner

Copy Link

What version of borgmatic are you using? You can tell with borgmatic --version or pip3 show borgmatic. Current versions of borgmatic do not monkey with the exclude patterns except to expand tildes (which Borg doesn't do).

Also, can you include the following on this ticket to aide in debugging? The contents of your borgmatic config file (secrets redacted), and the output of your borgmatic command invocation with --verbosity 2?

Thanks!

What version of borgmatic are you using? You can tell with `borgmatic --version` or `pip3 show borgmatic`. Current versions of borgmatic do not monkey with the exclude patterns except to expand tildes (which Borg doesn't do). Also, can you include the following on this ticket to aide in debugging? The contents of your borgmatic config file (secrets redacted), and the output of your borgmatic command invocation with `--verbosity 2`? Thanks!

skorokithakis commented 2019-03-11 21:35:15 +00:00

Author

Copy Link

Sorry, you are correct. I thought I upgraded Borgmatic yesterday but I forgot the --user option along with -U and ended up running 1.2.14. 1.3.0 works, sorry for the bother.

Sorry, you are correct. I thought I upgraded Borgmatic yesterday but I forgot the `--user` option along with `-U` and ended up running 1.2.14. 1.3.0 works, sorry for the bother.

skorokithakis closed this issue 2019-03-11 21:35:15 +00:00

witten commented 2019-03-11 21:43:10 +00:00

Owner

Copy Link

No worries. Glad that's all it was!

No worries. Glad that's all it was!

witten added the

question / support

label 2019-03-11 21:43:15 +00:00

skorokithakis commented 2019-03-11 21:46:40 +00:00

Author

Copy Link

Thank you, and thanks for Borgmatic! By the way, can I plug an OSS project I created to make sure my backups ran? It's called Caduceus and it lets you curl a URL as an after_backup action. If the URL isn't loaded once every X days, it emails you that your backups aren't running. Maybe you'll find it useful.

Thank you, and thanks for Borgmatic! By the way, can I plug an OSS project I created to make sure my backups ran? It's called [Caduceus](https://gitlab.com/stavros/caduceus) and it lets you `curl` a URL as an `after_backup` action. If the URL isn't loaded once every X days, it emails you that your backups aren't running. Maybe you'll find it useful.

witten commented 2019-03-11 22:46:22 +00:00

Owner

Copy Link

Cool! Looks handy.. I may have to try that out for my own backups!

Cool! Looks handy.. I may have to try that out for my own backups!

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

2 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#149

No description provided.