Skip all checks doesn't work. #1008

New issue

Closed

opened 2025-02-25 20:45:38 +00:00 by overgrow · 3 comments

overgrow commented 2025-02-25 20:45:38 +00:00

Copy link

What I'm trying to do and why

Using

skip_actions:
    - check

in a config file produces an error.

Steps to reproduce

skip_actions:
- check

Actual behavior

Using

skip_actions:
    - check

in a config file produces an error:

At the top level: Additional properties are not allowed ('skip_actions' was unexpected)
Configuration validation failed

Expected behavior

Should validate OK syntax and when executed it should skip all checks,

Other notes / implementation ideas

No response

borgmatic version

1.8.2

borgmatic installation method

pip install

Borg version

No response

Python version

No response

Database version (if applicable)

No response

Operating system and version

Ubuntu 20.04

### What I'm trying to do and why Using ``` skip_actions: - check ``` in a config file produces an error. ### Steps to reproduce skip_actions: - check ### Actual behavior Using ``` skip_actions: - check ``` in a config file produces an error: ``` At the top level: Additional properties are not allowed ('skip_actions' was unexpected) Configuration validation failed ``` ### Expected behavior Should validate OK syntax and when executed it should skip all checks, ### Other notes / implementation ideas _No response_ ### borgmatic version 1.8.2 ### borgmatic installation method pip install ### Borg version _No response_ ### Python version _No response_ ### Database version (if applicable) _No response_ ### Operating system and version Ubuntu 20.04

witten commented 2025-02-25 21:43:08 +00:00

Owner

Copy link

Time to upgrade! 😄 skip_actions: was added in borgmatic 1.8.5.

If you can't upgrade right now, there is an alternate way to skip checks in older versions of borgmatic. See the docs for details.

Time to upgrade! 😄 `skip_actions:` was added in borgmatic 1.8.5. If you can't upgrade right now, there is an alternate way to skip checks in older versions of borgmatic. See [the docs](https://torsion.org/borgmatic/docs/how-to/deal-with-very-large-backups/#disabling-checks) for details.

👍 1

witten added the

question / support

label 2025-02-25 21:43:18 +00:00

overgrow commented 2025-02-25 21:52:49 +00:00

Author

Copy link

Thanks for message! I wasn't not able to find that part of docs.. Thanks!
I have a remote storage which has a slow connection. That's why I need to disable checks.
I'd like to run them locally.. Is there a recommended way to run just checks from another machine on a different schedule and avoid privilege issues?

Thanks!

Thanks for message! I wasn't not able to find that part of docs.. Thanks! I have a remote storage which has a slow connection. That's why I need to disable checks. I'd like to run them locally.. Is there a recommended way to run just checks from another machine on a different schedule and avoid privilege issues? Thanks!

witten commented 2025-02-25 22:00:35 +00:00

Owner

Copy link

The docs could certainly be better organized.

To run checks from another machine, you'd need a separate borgmatic configuration file there where (at minimum) checks are enabled. Also see these docs. To avoid privilege issues, just make sure you're accessing the repository as the same Unix user. And you'll also probably want to schedule your checks to run at a different time than your backups so that you don't run into any repository lock contention issues. If you do run into lock contention, you'll see that one or the other borgmatic process will fail to acquire a lock and therefore error out.

The docs could certainly be [better organized](https://projects.torsion.org/borgmatic-collective/borgmatic/issues/942). To run checks from another machine, you'd need a separate borgmatic configuration file there where (at minimum) checks are enabled. Also see [these docs](https://torsion.org/borgmatic/docs/how-to/deal-with-very-large-backups/#running-only-checks). To avoid privilege issues, just make sure you're accessing the repository as the same Unix user. And you'll also probably want to schedule your checks to run at a different time than your backups so that you don't run into any repository lock contention issues. If you do run into lock contention, you'll see that one or the other borgmatic process will fail to acquire a lock and therefore error out.

👍 1

witten closed this issue 2025-02-27 06:41:29 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

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   

blocked

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

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

No description provided.