Further details on some of the config options #791

New Issue

Closed

opened 2023-11-15 09:00:25 +00:00 by atelszewski · 2 comments

atelszewski commented 2023-11-15 09:00:25 +00:00

Copy Link

Hi,

while configuring borgmatic I found myself needing some more details on the config options.

Here they come:

• store_config_files: In which location in the archive are the config files stored?
• retry_wait: What is the backoff algorithm?
• temporary_directory: What are some examples of the temporary files?
• keep_*: How to disable pruning?

Could you please address those in the documentation?
I wouldn't mind also quick answers here, so that I can finish my config.

Thank you for your support! :-)

--
Best regards,
Andrzej Telszewski

Hi, while configuring `borgmatic` I found myself needing some more details on the config options. Here they come: - `store_config_files`: In which location in the archive are the config files stored? - `retry_wait`: What is the _backoff_ algorithm? - `temporary_directory`: What are some examples of the temporary files? - `keep_*`: How to disable pruning? Could you please address those in the documentation? I wouldn't mind also _quick_ answers here, so that I can finish my config. Thank you for your support! :-) -- Best regards, Andrzej Telszewski

witten referenced this issue from a commit 2023-11-15 17:06:12 +00:00

Documentation clarifications (#791).

witten commented 2023-11-15 17:06:12 +00:00

Owner

Copy Link

store_config_files: In which location in the archive are the config files stored?

They're stored in their original paths. So for instance if your configuration is at /etc/borgmatic/config.yaml, that's where it's stored in the backup archive as well.

retry_wait: What is the backoff algorithm?

After each failure, it waits retry_wait * retry number, where retry number is the number of the next retry.

temporary_directory: What are some examples of the temporary files?

This is for Borg's temporary files. borgmatic doesn't use it. See https://borgbackup.readthedocs.io/en/stable/usage/general.html#resource-usage for details.

keep_*: How to disable pruning?

Wait for the next release of borgmatic and then add the following to your configuration:

skip_actions:
    - prune

Or just specify the actions you want to run on borgmatic's command-line.

Could you please address those in the documentation?

Done! The changes should be live shortly. Thanks for filing this and please let me know if there's anything else!

> store_config_files: In which location in the archive are the config files stored? They're stored in their original paths. So for instance if your configuration is at `/etc/borgmatic/config.yaml`, that's where it's stored in the backup archive as well. > retry_wait: What is the backoff algorithm? After each failure, it waits `retry_wait` * retry number, where retry number is the number of the next retry. > temporary_directory: What are some examples of the temporary files? This is for Borg's temporary files. borgmatic doesn't use it. See https://borgbackup.readthedocs.io/en/stable/usage/general.html#resource-usage for details. > keep_*: How to disable pruning? Wait for the next release of borgmatic and then add [the following](https://torsion.org/borgmatic/docs/how-to/set-up-backups/#skipping-actions) to your configuration: ```yaml skip_actions: - prune ``` Or just [specify the actions you want to run](https://torsion.org/borgmatic/docs/how-to/deal-with-very-large-backups/#a-la-carte-actions) on borgmatic's command-line. > Could you please address those in the documentation? Done! The changes should be live shortly. Thanks for filing this and please let me know if there's anything else!

witten closed this issue 2023-11-15 17:06:12 +00:00

witten added the

question / support

label 2023-11-15 17:06:21 +00:00

atelszewski commented 2023-11-16 10:26:58 +00:00

Author

Copy Link

Thanks! :-)

--
Best regards,
Andrzej Telszewski

Thanks! :-) -- Best regards, Andrzej Telszewski

👍 1

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

No description provided.