Question: consistency.prefix #91

New Issue

Closed

opened 2018-08-27 06:07:30 +00:00 by borgos · 3 comments

borgos commented 2018-08-27 06:07:30 +00:00

Copy Link

I see this message with journalctl:

borgmatic[3164]: Since version 1.1.16, if you provide archive_name_format, you should also specify consistency.prefix.

What does this mean? What is consistency.prefix and how do I specify it?

I see this message with journalctl: borgmatic[3164]: Since version 1.1.16, if you provide `archive_name_format`, you should also specify `consistency.prefix`. What does this mean? What is `consistency.prefix` and how do I specify it?

witten commented 2018-08-27 15:11:37 +00:00

Owner

Copy Link

It means that, since you're using the archive_name_format borgmatic configuration option, you should also supply the prefix option in the consistency section of the configuration file. Here's the comment on that option:

    # When performing the "archives" check, only consider archive names starting with
    # this prefix. Borg placeholders can be used. See the output of
    # "borg help placeholders" for details. Default is "{hostname}-".
    prefix: sourcehostname

The reason for this warning is so that your consistency checks only consider archives with a prefix that matches your archive_name_format. If you didn't specify a prefix, then borgmatic would consistency check all archives, even ones that it didn't create.

Hope that helps.

It means that, since you're using the `archive_name_format` borgmatic configuration option, you should also supply the `prefix` option in the `consistency` section of the configuration file. Here's the comment on that option: ```yaml # When performing the "archives" check, only consider archive names starting with # this prefix. Borg placeholders can be used. See the output of # "borg help placeholders" for details. Default is "{hostname}-". prefix: sourcehostname ``` The reason for this warning is so that your consistency checks only consider archives with a `prefix` that matches your `archive_name_format`. If you didn't specify a `prefix`, then borgmatic would consistency check all archives, even ones that it didn't create. Hope that helps.

👍 1

witten closed this issue 2018-08-27 15:11:38 +00:00

witten added the

question / support

label 2018-08-27 15:11:43 +00:00

witten commented 2018-08-27 15:13:43 +00:00

Owner

Copy Link

By the way, the same goes for the prefix option in the retention section of borgmatic's configuration. It's even more important to specify in your case, because doing so ensures that borgmatic only prunes archives with a particular prefix (ideally matching your archive_name_format) instead of all archives.

By the way, the same goes for the `prefix` option in the `retention` section of borgmatic's configuration. It's even more important to specify in your case, because doing so ensures that borgmatic only prunes archives with a particular `prefix` (ideally matching your `archive_name_format`) instead of all archives.

👍 1

borgos commented 2018-08-27 15:26:45 +00:00

Author

Copy Link

The option and the comment weren't in my config. I have added them now. In the retention section the prefix was already there.
Thanks!

The option and the comment weren't in my config. I have added them now. In the retention section the prefix was already there. Thanks!

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

No description provided.