Run a pre backup hook only once when working with multiple configuration files #353

New Issue

Closed

opened 2020-08-12 07:35:38 +00:00 by hk · 3 comments

hk commented 2020-08-12 07:35:38 +00:00

Copy Link

I push the same backup to two different places, one onsite and one externally. However I need completely different settings for retentions, repo url and even executable name so I use two configuration files in /etc/borgmatic.d.

This works as intenteded. However, I also need to dump a large and complex application to disk using its own backup utility. This is done using a pre backup hook. This also works as intended. However, this backup is very demanding, and because it is run once for every configuration it is very inefficient.

What I am asking for is the possibility to configure a hook to only run once before all the backups. E.g. some kind of additional hook that is always interpreted as a global hook, regardless of which config file it is found in.

I push the same backup to two different places, one onsite and one externally. However I need completely different settings for retentions, repo url and even executable name so I use two configuration files in /etc/borgmatic.d. This works as intenteded. However, I also need to dump a large and complex application to disk using its own backup utility. This is done using a pre backup hook. This also works as intended. However, this backup is very demanding, and because it is run once for every configuration it is very inefficient. What I am asking for is the possibility to configure a hook to only run once before all the backups. E.g. some kind of additional hook that is always interpreted as a global hook, regardless of which config file it is found in.

witten commented 2020-08-12 17:11:53 +00:00

Owner

Copy Link

Check out the before_everything hook in the configuration. I think it'll do exactly what you're looking for! Either way, please do let me know. Thanks!

Check out the `before_everything` hook in the [configuration](https://torsion.org/borgmatic/docs/reference/configuration/). I think it'll do exactly what you're looking for! Either way, please do let me know. Thanks!

witten added the

question / support

label 2020-08-12 17:12:00 +00:00

hk commented 2020-08-12 18:55:50 +00:00

Author

Copy Link

Sorry for wasting your time! For some reason I thought the "hooks" part of the configuration documentation stopped at the postgresql part. My mistake!

It worked like a charm!

Sorry for wasting your time! For some reason I thought the "hooks" part of the configuration documentation stopped at the postgresql part. My mistake! It worked like a charm!

hk closed this issue 2020-08-12 18:55:55 +00:00

witten commented 2020-08-12 20:51:26 +00:00

Owner

Copy Link

I'm really glad to hear it worked! I only had to travel back in time to implement the feature before you asked for it. ;)

I've also updated the schema so that these hooks are easier to find.

I'm really glad to hear it worked! I only had to travel back in time to implement the feature before you asked for it. ;) I've also updated the schema so that these hooks are easier to find.

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

No description provided.