Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow customization of archive_name_format and include match_archives #123

Open
agross opened this issue Apr 18, 2023 · 0 comments
Open

Comments

@agross
Copy link

agross commented Apr 18, 2023

I mostly use files in /etc/borgmatic.d that inherit from /etc/borgmatic/config.yaml. Those inherited configs share the {hostname} prefix of the hard-coded archive_name_format but append an application-specific token.

Default config: host-<timestamp>
App1 config: host-app1-<timestamp>
App2 config: host-app2-<timestamp>

One issue I see is that when the default config is run (I run all of those configs at night) it starts pruning data from App1 and App2, but according to retention rules of the default config.

I think this is because borgmatic considers the timestamp part of host-<timestamp> to be ephemeral and matches all host-* archives, including e.g. host-app1-*.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant